Cut Recovery Not Consistently Triggering
- snowgoer540
- Offline
- Moderator
Less
More
- Posts: 2397
- Thank you received: 787
11 Oct 2024 23:58 - 11 Oct 2024 23:58 #311841
by snowgoer540
Replied by snowgoer540 on topic Cut Recovery Not Consistently Triggering
if you do what i suggested earlier, update and use this pin instead:
qtplasmac.ext_pause_only
Last edit: 11 Oct 2024 23:58 by snowgoer540.
Please Log in or Create an account to join the conversation.
- Uthayne
- Offline
- Premium Member
Less
More
- Posts: 144
- Thank you received: 46
10 Dec 2024 15:10 - 10 Dec 2024 15:11 #316408
by Uthayne
Replied by Uthayne on topic Cut Recovery Not Consistently Triggering
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.
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.
Last edit: 10 Dec 2024 15:11 by Uthayne.
Please Log in or Create an account to join the conversation.
- phillc54
- Offline
- Platinum Member
Less
More
- Posts: 5714
- Thank you received: 2090
10 Dec 2024 22:50 #316436
by phillc54
Replied by phillc54 on topic Cut Recovery Not Consistently Triggering
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.I do have another question on why it can't go back further than the last M03 (or any M-code)
Please Log in or Create an account to join the conversation.
- snowgoer540
- Offline
- Moderator
Less
More
- Posts: 2397
- Thank you received: 787
10 Dec 2024 23:08 - 11 Dec 2024 02:36 #316437
by snowgoer540
Replied by snowgoer540 on topic Cut Recovery Not Consistently Triggering
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.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).
Last edit: 11 Dec 2024 02:36 by snowgoer540.
The following user(s) said Thank You: Uthayne
Please Log in or Create an account to join the conversation.
- gekonko
- Offline
- New Member
Less
More
- Posts: 14
- Thank you received: 2
01 Jan 2025 16:48 #317785
by gekonko
Replied by gekonko on topic Cut Recovery Not Consistently Triggering
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 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.
Please Log in or Create an account to join the conversation.
- phillc54
- Offline
- Platinum Member
Less
More
- Posts: 5714
- Thank you received: 2090
02 Jan 2025 03:54 #317857
by phillc54
Replied by phillc54 on topic Cut Recovery Not Consistently Triggering
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?
Are you by chance using a Wayland desktop and/or a non English locale?
Please Log in or Create an account to join the conversation.
- gekonko
- Offline
- New Member
Less
More
- Posts: 14
- Thank you received: 2
02 Jan 2025 07:50 #317862
by gekonko
Replied by gekonko on topic Cut Recovery Not Consistently Triggering
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.
- 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.
Please Log in or Create an account to join the conversation.
- phillc54
- Offline
- Platinum Member
Less
More
- Posts: 5714
- Thank you received: 2090
03 Jan 2025 00:25 #317888
by phillc54
Replied by phillc54 on topic Cut Recovery Not Consistently Triggering
I can confirm that it misbehaves if I change my location to SK.
I will look into it further.
I will look into it further.
Please Log in or Create an account to join the conversation.
- phillc54
- Offline
- Platinum Member
Less
More
- Posts: 5714
- Thank you received: 2090
03 Jan 2025 06:57 #317900
by phillc54
Replied by phillc54 on topic Cut Recovery Not Consistently Triggering
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.
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:
~scoped_locale() { setlocale(category, oldlocale.c_str()); }
~scoped_locale() { setlocale(category, oldlocale); }
Line 1000 from:
std::string oldlocale;
const char *oldlocale;
The following user(s) said Thank You: gekonko
Please Log in or Create an account to join the conversation.
- gekonko
- Offline
- New Member
Less
More
- Posts: 14
- Thank you received: 2
04 Jan 2025 15:15 #318083
by gekonko
Replied by gekonko on topic Cut Recovery Not Consistently Triggering
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
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
Please Log in or Create an account to join the conversation.
Moderators: snowgoer540
Time to create page: 0.561 seconds