Advanced Search

I would probably use the latest as a lot of improvements have been made both
in LinuxCNC and the configuration utilities for Mesa cards.

The main issue with the latest ISO is not LinuxCNC specific but that newer
kernels have problems with the Realtek Ethernet driver so it needs to be replaced
with the DKMS version. This issue can be avoided if you have a PC with Intel
Ethernet hardware.

I already tried that but it didn't work, even though that pin (spindle.0.on) is connected in my configuration in the .HAL file.

see:
forum.linuxcnc.org/21-axis/51229-spindle...s-not-visible#294567

for your parport input you could use eg 'motion.digital-in-00'
linuxcnc.org/docs/html/man/man9/motion.9.html

in your hal you would connect the two pins like this:

in your ngc remap you would then use M66 P0 .. to interact with your input:
linuxcnc.org/docs/html/gcode/m-code.html#mcode:m66

Why are the spindle control buttons not visible in AXIS?

loadrt or2
addf or2.0 servo-thread
net probe-touchprobe or2.0.in0 <= hm2_7i76e.0.7i76.0.0.input-08
net probe-toolsetter or2.0.in1 <= hm2_7i76e.0.7i76.0.0.input-09-not
net probe-input motion.probe-input <= or2.0.out

this is about the simplest or2 use for two inputs to motion.probe-input, in this method you would want to use a 3pin touch probe connection jack so that when you unplug the touch probe the jack closes the circuit which takes the input out of triggered state.

something like this maybe and jumper when plug is removed the jack closes.

www.amazon.com/MEETOOT-5-5mm-Female-Sock...trical/dp/B09JP19XKP

Hello, I'm new here too, but I've had to deal with the topic intensively recently.
You can create the ethercat_conf.xml very roughly if you run "ethercat xml" and then copy what is displayed into the XML.

You can then load the XML for testing purposes with "halcmd loadusr -W lcec_conf ethercat_conf.xmf". Now run "halcmd lcec" and then you can use "halcmd show" to see whether it is displaying the variables.

As long as the ethercat master is still idle, you will unfortunately not see any content.

To do this, you have to put together a small dummy machine somehow. Then

addf lcec.read-all servo-thread

addf lcec.write-all servo-thread

must appear in the .hal file so that the values ​​are queried. then look for a machine ini from the demos (which also contains your hal file) and

then start linuxcnc **.ini

if that works, "ethercat master" will show you Phase: operation at the top and you can also look at the values ​​with halcmd show.

I hope that helps a little.

Hallo cmorley, große Klasse! Dein Script funktioniert auf Anhieb und ich bin glücklich über diese Vereinfachung! Danke danke!

Thanks for the reply, now I'm trying to do something via remap but I'm not sure I'm doing it right. I can't figure out how to interact with pin 17 on port 0.So far there is this outline of the remap, I would appreciate it if you could point out any errors.Thanks for the links, I'll have a look.

thank you for the guide. i am looking into it and so far it seems promising. i might have some questions down the line when i start building my g-code around the suggested solution.

Hi,

Which version of LinuxCNC is recommended for the MESA 7i96s (for a beginner user) in late 2024 / '25?

Debian 10 (Buster) + 2.8.4 has a few very good youtube beginner tutorials.  Is Buster + 2.8.4 still a reliable and recommended install?

A forum search on 7i96s + 2.9 seems mainly to be posts of people with issues getting 2.9 working reliably ...

I'd just like whichever solution is easiest to get up and running reliably!

Thanks

     

Have a look at the halui.program.* halpins:
linuxcnc.org/docs/html/man/man1/halui.1.html

Depending on the gui you are using it may provide its own hal pins to steer program execution.

You need only to lower the voltage a little bit for the Level-Shifter with a Diode or two Resistors,
the FPGA can handle up to 3.3V input and the Level-Shifter need to detect 1.8V as high.

but after applying G54 on X, it becomes a mess:

This issue is a known limitation of the feature. Please read paragraph 11 the documentation I posted above.

I hope this video will make more clear what is happening, I have no issue with g-code from CAM, machined parts are ok, only display section is a bit off in my case: