Advanced Search

May be the driver has a setting to set the repetition rate ?
My one reakts with a long touch like preesing the right mouse button. So I was also forced to set that time longer to be able to hold down the touch buttons for longer.

Norbert

M1 will pause a program if optional stop is on.

in 2.9 you would have to add the language folder and the script to automate the making of the .ts file.
And strings defined in the handler file will not be translatable but most of the buttons are done in designer and that should work. (though I have not tried it)

It's possible just more work. (You could also modify the 2.9 handler to add translatable strings, it's pretty straight forward.)

If your interested I can give more detail.

I can get a new in box motherboard of the same model and make that was in the machine on eBay
190 dollars

The answer is always "it depends". In some kernel traces we did, at 1 kHz, the servo thread was done in around 200 usec and it slept for the remaining 800 usec. On a 2 Khz servo thread, it must be done in 500 usec so in theory, the hardware we had would meet the requirements.

Say 200 uS after 10 minutes or so:

chrt 99 ping -i .0005 -c 600000 -q 10.10.10.10
 

But this supported in 2.9.4 or needs master?

For 2khz servo thread what max ping must have?

Ah! Looks like the "Reload" button on the panel with the Opt Block button is indeed the trick.

For clarity in case someone finds this, Opt Block ON, with green light, actually seems to turn "off" whatever follows the "/"

Thanks!

What then, does "Opt Stop" do?

Might easier to just have a few configurations with different settings in their .ini files

You can change ini settings with LinuxCNC running (but interpreter idle) but setting up a GUI to
do this is outside my area of expertise.
 

Thanks for the tip about safety relays--never knew they were a thing. I'm converting an existing mill (Emco concept mill 55) that uses a three-relay combo (K1/K2/K3). And the PLC file for the mill has a check to ensure that when the relays are commanded "on" that their outputs are "on" and vice-versa, so I'm just trying to add in that extra level of safety to LinuxCNC as well.

FWIW, I do all of my development work (mainly QtPlasmaC) in VirtualBox, running MX Linux 23, which is derived from Debian Bookworm, and I've never seen these graphical anomalies. Same with the BM hardware at the plasma table.

Generally speaking, when these sort of things come up, it's almost always driver related.

I don't run the stock ISO of, in favor of MX Linux as I find it 10x easier to use. It might be worth making a MX Linux 23 VirtualBox and see if you can get it to show up there?