Cut Recovery Not Consistently Triggering

if you do what i suggested earlier, update and use this pin instead:

Thanks! I was able to get it to work by connecting my components pause-program output to the qtplasmac.ext_pause (I haven't updated yet to try to the ext_pause_only). It appears there was timing issues when I was trying to trigger this by throwing the ohmic signal high.

Side note, I believe when I was first working on this I was occasionally using sudo with halcompile (I'm on a RIP install) so the changes to the comp weren't actually happening.... lessons learned!

Reverse run seems to be working without fault now, but I do have another question on why it can't go back further than the last M03 (or any M-code)? I have some M64/65 set periodically in gcode and it will not reverse past these points. I took a look at the tcq.c file which is where the 200 line limit is set, but cannot find any reference.

Uthayne wrote:

I do have another question on why it can't go back further than the last M03 (or any M-code)

That is a limitation of the reverse run feature that was added to LinuxCNC a few years back. From memory it is in the trajectory planner.

Uthayne wrote:

Thanks! I was able to get it to work by connecting my components pause-program output to the qtplasmac.ext_pause (I haven't updated yet to try to the ext_pause_only).

Worth noting that I added the _only pin with you in mind. It’s because the program can also be resumed if that pin you are currently using is triggered again somehow. I figured having the option to only pause no matter how many times the pin is hit may be handy.

Hello,
I have similiar problem.
I was running latest version of linuxcnc(complete installation from usb drive), and cut recovery function was working correctly.
Because I am in the process of creating localisation for the qtplasmac, I did the RIP install (v2.10-008.054). And now the cut recovery is not working.
The cut recovery window shows up ( when paused or triggered by arc-ok loss), Z goes up, but forward and back buttons are not working. I mean they click "yellow", but axes doesnt move on the contour. directional buttons on the screen are working.

I did two of these RIP installations on different computers, and behaviour is the same.

Even in the qtplasmac-metric simulator it is not working.

M52 P1 is called in the program.
Do you have any idea what can cause this problem? thank you.

I don't see this issue on a current RIP build.
Are you by chance using a Wayland desktop and/or a non English locale?
 

My system is basically :
- installed from linuxcnc usb stick
- removed linuxcnc using synaptic
- installed RIP linuxcnc using documentation.

My locale is SK (Slovak)
i will try to install RIP in new, EN locale.

I can confirm that it misbehaves if I change my location to SK.

I will look into it further.
 

It appears to have been caused by this commit  in July which seems to affect the HAL Python module.
It only affects locales that use commas instead of periods in floating point numbers.

A workaround until we get a permanent solution would be to edit src/emc/rs274ngc/interp_internal.hh and change the following:

Line 998 from:
        to:
     
Line 1000 from:
    to:
    and then recompile.

thank you again @phillc54,
your first post led me to realisation, i was running master branch, and not v2.9.3..
at this point, I did:
-make clean
-deleted whole folder linuxcnc-dev
-git clone
-git checkout tags/v2.9.3
and rest was just RIP install