Advanced Search

@lcvette I have LinucCNC 2.9 running on my computer now, installed using this:
linuxcnc.org/docs/stable/html/getting-st...th_preempt_rt_kernel
If I'm understanding the documentation correctly, the above link installs the Debian Bookworm distribution.

To install Probe Basic, do I start at the very beginning of this which seems to install Debian Bookworm.
kcjengr.github.io/probe_basic/stable_quick_start_apt.html

Or start here?
kcjengr.github.io/probe_basic/quick_start.html

@tiagounderground,
Those are EtherCAT errors, probably better to ask in the EtherCAT section of the forum.

I'm trying to run the last update on ethercat drivers but i have this error
HAL: ERROR: function 'cia402.0.read-all' not found
./cia402.hal:34: addf failed
HAL: ERROR: pin 'lcec.0.3.out-01' not found
shutdown.hal:2: unlink failed
24062
24076

am i missing something?

Alright, I found out that though the error looks identical, this time the MESA card is NOT the problem. The other good news is that the problem has become reproducible and the Joint Amplifier Failure now always happens immediately during the (attempted) homing procedure.

I can see during the homing attempt that the joint that has the amplifier error attempts to move - the other joint does not. In other words, I think that the servo with the alarm is the good one, and it goes into alarm because it fails to drag the other servo along.

It is still a puzzle though. By swapping port/cables/motors it seems that the common denominator is a port/cable:

 

The red path marks the one that has amplifier error in the different scenarios that I tested.

What puzzles me is that the common denominator in all failure scenarios are panel ports 2 and 3. However, I have measured the every wire several times with an ohm meter (as shown by the green lines in the image), and they are all fine. Since they are also not moving cables I cannot imagine it is a flapping connectivity issue.

So I am a little clueless as to what else I could do now. It seems every potential source of the problem was excluded.

Maybe EMI could have something to do with it, but... why would that suddenly become a reliably reproducible problem after running years with no issue?
Anyway, I also measured all the grounds on the shields of each cable, and they also seem fine/low impedance. (star configuration off of the panel, no loops)

Any ideas what else I can check?

I've been doing a bunch of machining on my freshly built mill running QTDragonHD and there's one thing that is absolutely throwing me off. I have a ton of experience running a Tormach on Path Pilot so I have established muscle memory for smacking the space bar to pause (feed hold) when proofing new code. QTDragonHD doesn't appear to have any shortcuts mapped to the space bar when a program is running.

Is it possible to remap the space bar to be pause (feed hold) when running programs?

Thanks!