Advanced Search

It started when i was editing the .ini for a homing issue. After the restart , EMC2 would always terminate with an error. Somehow it modified the port address , from what i can figure. but with the system password unknown . I cant edit the port address.

Ill give it a try. Thank You for the step by step.

Good evening gentleman,
I am almost done with my new setup (printnc "pro", mesa 7i76eu, probe basic, jianken ATC) and everything seems to be working now, except the tool length measurement.
When I start a measurement with G38.2.... and then press the toolsetter with a finger (just to test it), the system errors out with "probe tripped during non-probe movement".
So it recognizes that the toolsetter is triggered, but for some reason it thinks its the 3d probe...  

This is how my probe and tls signals are linked:

# --- PROBE-IN ---
net probe-in     <=  hm2_7i76e.0.7i76.0.0.input-08
# --- TLS-Normal-IN ---
net tls-in       <=  hm2_7i76e.0.7i76.0.0.input-09-not

addf or.probeortls servo-thread
net probe-in or.probeortls.in0
net tls-in or.probeortls.in1
net probe-tool or.probeortls.out
net probe-tool motion.probe-input

What am I doing wrong ?

Here is my full config...
github.com/SebastianMusser/LinuxCNC/tree/main

regards
Sebastian

Long story short.

The current machine is really not suitable for the most recent version.
Maybe if you elaborate on the issues we maybe able to provide a solution.
Usually if the machine is operating fine and doing the job without any issues there is no real need to upgrade.
There are many machines out there still running early versions of Linuxcnc without any issues.

if my math is right and I am reading ferror right, I am running 36000mm/m which works out to 600mm/s and an ferror of 5 (well 4.94ish, but close enough).

5/600 = .008333333 But I am running my loop at 500000 if I have configured things right so 2 round trips should be .001ish... makes me think that something else is up in that lag....

Does EtherCat time code movements so that multiple axis would all move at the right time to each other and be at the right place regardless of what LinuxCNC sees back as the time delay?

Thanks