Forum Menu

2.9.3 - Stuck in wrong state and stops

More
1 year 7 months ago #324664 by snowgoer540
Replied by snowgoer540 on topic 2.9.3 - Stuck in wrong state and stops

Thanks, given that this issue only happens once a week or so, is the output logged anywhere?

Not other than the terminal. I spent 5-10 minutes confirming my suspicion that the mismatch in timing between the GUI and the component is such that catching the state changes at a GUI level is fruitless. Even appending them to a variable and writing that to the log file when the machine goes IDLE again reveals that it misses some state changes. I'd be reluctant to add file based logging to the component.

Not sure where the harm would be in running from the terminal, and turning on debug-print and then having your customer look at the terminal window the next time it "freezes" and report back on the last state displayed.

Please Log in or Create an account to join the conversation.

More
1 year 7 months ago #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:
Code:
        # 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          = 27

So it missed:
4 - ZERO_HEIGHT
14 - SAFE_HEIGHT
16 - END_CUT
17- END_JOB
The following user(s) said Thank You: tommylight, rodw

Please Log in or Create an account to join the conversation.

More
1 year 7 months ago #324720 by rodw
Replied by rodw on topic 2.9.3 - Stuck in wrong state and stops
I received additional detailed information from the customer and have raised an issue in github here
github.com/LinuxCNC/linuxcnc/issues/3382
Hopefully, this can be resolved.

Please Log in or Create an account to join the conversation.

More
1 year 7 months ago #324725 by phillc54
Replied by phillc54 on topic 2.9.3 - Stuck in wrong state and stops
Is there a complete sim config somewhere that can be used to test for this issue?
If so I can probably make a bit time to have a look.

The config posted above is not a sim but a quick glance does show a couple of oddities in runstep.hal:
Code:
# External Program Pause/Resume and Run/Step Buttons # Pause/Resume Section unlinkp halui.program.is-paused unlinkp halui.program.is-running net plasmac:program-is-paused => pr-or2.in0 net ispaused halui.program.is-paused => pr-or2.in1 net plasmac:program-is-running => pr-or3.in0
The two plasma:program-is-... signals seem to have nothing driving them, just two inputs connected together.

Have you thought of using the provided external button pins?

 

Please Log in or Create an account to join the conversation.

More
1 year 7 months ago #324726 by rodw
Replied by rodw on topic 2.9.3 - Stuck in wrong state and stops
I will  get the clients current config.  we may not be using the runstep.hal file any more as we are using the external button pins.
Not sure about the sim

Please Log in or Create an account to join the conversation.

More
1 year 7 months ago #324727 by phillc54
Replied by phillc54 on topic 2.9.3 - Stuck in wrong state and stops
Interestingly if I unlink haul.program.is-paused in a sim I see similar behaviour:
Code:
[b]Actions on the simulator:[/b] Homed the machine and enabled the torch Started a job While the thing was moving to start the cut, I set the ohmic volts right up When it tried to do the ohmic sensing it failed with the message "pierce height would exceed Z axis maximum limit". This stopped the machine Pressed the pulse button. The button shows the countdown timer, but the torch does not fire
I cannot get it to fire by activating the float switch though.
 
The following user(s) said Thank You: rodw

Please Log in or Create an account to join the conversation.

Moderators: snowgoer540
Time to create page: 0.479 seconds
Powered by Kunena Forum