2.9.3 - Stuck in wrong state and stops
20 Mar 2025 06:09 #324339
by rodw
2.9.3 - Stuck in wrong state and stops was created by rodw
Reported by a customer. Sometimes, QTP freezes. Moving the float switch by hand seems to clear the error and the cut proceeds.
Any ideas or feedback? I have never experienced this.
I wanted to write a script that updates APT to look at the new Buildbot for 2.10 instead of the Linuxcnc.org 2.94 repo so it looks like I need to do that now....
Any ideas or feedback? I have never experienced this.
I wanted to write a script that updates APT to look at the new Buildbot for 2.10 instead of the Linuxcnc.org 2.94 repo so it looks like I need to do that now....
Please Log in or Create an account to join the conversation.
22 Mar 2025 21:35 #324587
by snowgoer540
Rants don't usually help ... however configuration backups (made from the settings tab) sometimes do. It's hard to diagnose otherwise since Phill, nor I, nor a guy who cut so much plate with QtPlasmaC he was able to sell his plasma table and buy a large fiber laser have seen this issue.
Also, adding the following to your postgui.hal file might help see where it gets stuck as well:
Lastly, it's worth noting that plasmac, plasmac2, and qtplasmac all use the same plasmac component at least to the extent where anything fixed in the original PlasmaC was carried forward to the same PlasmaC component today.
If there's a bug, no one wants to find it more than me, but it’s really challenging to identify a bug without being able to reproduce it. Can't squish a bug I can't see
Replied by snowgoer540 on topic 2.9.3 - Stuck in wrong state and stops
The same thing happened on PlasmaC and Phill fixed it, so it is strange that it happens on QTP but not on PlasmaC....well it did happen on PlasmaC, about once in 6-9 months of daily use, while on QTP it would happen daily, several times a day sometimes, then it would not happen for months, then happen again.....
Hence i do not use it on production machines.
-
I wrote a rant here and deleted it...
Rants don't usually help ... however configuration backups (made from the settings tab) sometimes do. It's hard to diagnose otherwise since Phill, nor I, nor a guy who cut so much plate with QtPlasmaC he was able to sell his plasma table and buy a large fiber laser have seen this issue.
Also, adding the following to your postgui.hal file might help see where it gets stuck as well:
setp plasmac.debug-print 1Lastly, it's worth noting that plasmac, plasmac2, and qtplasmac all use the same plasmac component at least to the extent where anything fixed in the original PlasmaC was carried forward to the same PlasmaC component today.
If there's a bug, no one wants to find it more than me, but it’s really challenging to identify a bug without being able to reproduce it. Can't squish a bug I can't see
Please Log in or Create an account to join the conversation.
22 Mar 2025 22:19 #324589
by rodw
Replied by rodw on topic 2.9.3 - Stuck in wrong state and stops
More feedback here. Customer has an IT savvy brother. His brother told him to lift the torch to clear the stall after reviewing the code and it worked!
It goes without saying, I have asked for a line number reference.
I think this implies the bug lurks in the plasmac.comp state machine somewhere.
I've already found my plasmac bug for the day. Maybe someone elses turn!
It goes without saying, I have asked for a line number reference.
I think this implies the bug lurks in the plasmac.comp state machine somewhere.
I've already found my plasmac bug for the day. Maybe someone elses turn!
Please Log in or Create an account to join the conversation.
23 Mar 2025 02:05 #324604
by snowgoer540
Provided the works was not completely locked up, float activation, torch breakaway, ohmic detection, or arc ok lost will always result in a program pause which should break up any state hangs.
That check (during a running program) begins at line 691. What would be more useful would be to know what state it was in when it "freezes".
That could be seen by running QtPlasmaC from a terminal, and either using Halshow to change plasmac.debug-print True, or having already addedto the postgui.hal file. Watch the terminal for the state it freezes in.
A backup of the config from the Settings tab may help too.
Replied by snowgoer540 on topic 2.9.3 - Stuck in wrong state and stops
More feedback here. Customer has an IT savvy brother. His brother told him to lift the torch to clear the stall after reviewing the code and it worked!
It goes without saying, I have asked for a line number reference.
I think this implies the bug lurks in the plasmac.comp state machine somewhere.
I've already found my plasmac bug for the day. Maybe someone elses turn!
Provided the works was not completely locked up, float activation, torch breakaway, ohmic detection, or arc ok lost will always result in a program pause which should break up any state hangs.
That check (during a running program) begins at line 691. What would be more useful would be to know what state it was in when it "freezes".
That could be seen by running QtPlasmaC from a terminal, and either using Halshow to change plasmac.debug-print True, or having already added
setp plasmac.debug-print 1A backup of the config from the Settings tab may help too.
Please Log in or Create an account to join the conversation.
23 Mar 2025 13:44 #324665
by snowgoer540
Replied by snowgoer540 on topic 2.9.3 - Stuck in wrong state and stops
Here is what it looked like:
For reference:
So it missed:
4 - ZERO_HEIGHT
14 - SAFE_HEIGHT
16 - END_CUT
17- END_JOB
For reference:
# plasmac states
self.IDLE = 0
self.PROBE_HEIGHT = 1
self.PROBE_DOWN = 2
self.PROBE_UP = 3
self.ZERO_HEIGHT = 4
self.PIERCE_HEIGHT = 5
self.TORCH_ON = 6
self.ARC_OK = 7
self.PIERCE_DELAY = 8
self.PUDDLE_JUMP = 9
self.CUT_HEGHT = 10
self.CUT_MODE_01 = 11
self.CUT_MODE_2 = 12
self.PAUSE_AT_END = 13
self.SAFE_HEIGHT = 14
self.MAX_HEIGHT = 15
self.END_CUT = 16
self.END_JOB = 17
self.TORCH_PULSE = 18
self.PAUSED_MOTION = 19
self.OHMIC_TEST = 20
self.PROBE_TEST = 21
self.SCRIBING = 22
self.CONS_CHNG_ON = 23
self.CONS_CHNG_OFF = 24
self.CUT_REC_ON = 25
self.CUT_REC_OFF = 26
self.DEBUG = 27So it missed:
4 - ZERO_HEIGHT
14 - SAFE_HEIGHT
16 - END_CUT
17- END_JOB
Attachments:
Please Log in or Create an account to join the conversation.
Moderators: snowgoer540
Time to create page: 0.522 seconds