Advanced Search

Some interesting suggestions on latency improvement here:
dantalion.nl/2024/09/29/linuxcnc-latency...arameter-tuning.html

But don't get too obsessed with it.
50k jitter is fine with a Mesa card. Though I would be a bit unhappy with 250k.
Try running the latency test without a base thread, you won't need one with a Mesa card.

The download links will all work if you take out the "s" in "https://..."
There is a problem with the wiki certificate. We keep trying to fix it, but without much luck.

When we had a similar problem with stringy chips, drilling holes with carbide drill with trough coolant in CrMo4, a modified G83 cycle solved that. Only retracting by 0.2mm after 2mm. Continue this 2.2mm / retract 0.2mm  steps until 
final depth, we made all the 120 holes without interruption and big loss of time. I think feed was about 0.12/rev

Can you describe what you want to happen? I have a feeling that the AI might be over-complicatiing things. But without knowing your requirements it is hard to tell.

Does the MPG connect to a Mesa counter, or only to GPIO?

Darium wrote:

Remapping is way way over my head and messing around with it can crash my machine
 

The simplest case of remapping is fairly straightforward. It starts off looking a lot like a subroutine in its own file (which is also a possibility) 

See section 2.6 here: linuxcnc.org/docs/stable/html/remap/rema...xample_remapped_code

Your ngc file would probably just contain the usual G83 but wrapped with a spindle reversal, and passing-through the XYZRQ etc parameters. 
 

What happens if you just wire selected-pocket directly in HAL?

Unfortunately a problem has been found with the 2.9.5 release with the touch-off dialog in Axis. 
It will not accept values other than zero. 
If you don't use Axis or always touch-off to zero then you can use 2.9.5 without problems. 
If you do need to use Axis and non-zero touch-off then you can either revert temporarily to 2.9.4 or MDI G10 to achieve the same effect as the touch-off dialog (which actually does use G10) 

I hope to release a 2.9.6 with this problem fixed rather more quickly than the usual "measured" cadence. 

Now believed to be fixed: forum.linuxcnc.org/29-forum-announcement...xcnc-v2-9-6-released
 

Basically what the original m10 from probe basic does. It tells the carousel comp the pocket number

What does M120 do?

So you are saying that you commented out the HOME_SEQUENCE  lines
in the ini file and then got:

1. Individual axis check boxes for homing in the GUI (Axis)
2. When you selected an axis and pressed the Home Axis
button, the selected axis did not move?

Other questions:

What version of LinuxCNC are you running?

(not that this is likely an issue with an official release since there are probably more than 100000 LinuxCNC installations
using home switches)

So the real question is what is different about your configuration?