Advanced Search

I think that's exactly what I was looking for, and wish I had known about it years ago

Now to see how well my configuration plays with it...

Thanks!

You could use Halscope to see what the F-error actually is, then set the limit to some arbitrary factor of that. It wants to be high enough not to trip when there isn't a problem, but to trip if something actually is stuck.

The issue indeed did turn out to be related to spindle-at-speed.

Was able to fix it by ensuring spindle-at-speed was set true during tool changes.

You can't use names= and count= at the same time.
if using HAL_TWOPASS then they all need to use names=

In your example the correct syntax is:

Home-made spindle encoders can be as simple as a slotted disc with 3 x opto sensors (like: www.amazon.co.uk/YOUMILE-Optocoupler-Sen...rduino/dp/B07TZ78N8W )

You need to make one slot a bit deeper so that only the index sees it, and arrange the others around the perimiter so that they are N + 0.25 apart. (not N + 0.5 as I once did when making an encoder)

The "play" button, if visible, ought to come to life when the machine is on and homed.

See the "buttons" section:
linuxcnc.org/docs/stable/html/man/man1/x...6.1.html#HAL%20USAGE

The default config is set up just to say "macroN" when you press a button.
If you want to do somethng when you press the button you need to change (debug, macro4) to a bit of G-code (or a call to a subroutine) that has the desired affect.

Does your G-code include a G43 after loading the tool? (do you use the tool table, and are there non-zero Z length entries in there?)

Hi,
What did you use for noise filters on the servos?
I can't find any information anywhere.

The translation (of the application, not of the manual) exists
github.com/LinuxCNC/linuxcnc/blob/master/src/po/pl.po

Try: www.server-world.info/en/note?os=Debian_13&p=locale

Getting stuck on a G1 can often be related to spindle-at-speed being false. How is that driven?

You may be editing the correct files, but maybe you are not running the right files?

If you start from a desktop entry, what is the command-line that it runs?

Time will tell.

I’m going to try that next. I’ve been avoiding it since my English isn't the best, but I've already sent a few emails and haven't received a response yet.

Does anyone know if Mesa is having trouble getting back to people lately?

The USB Ethernet adapter is likely the main issue here

Running:

sudo chrt 99 ping -i .001 -q -c 60000 10.10.10.10

in a terminal window will give you an idea of the latency of the hosts Ethernet interface

( The command will run for 1 minute and then print timing statistics )