2.9.3 - Stuck in wrong state and stops
- rodw
-
Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 11216
- Thank you received: 3744
24 Mar 2025 05:04 #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
Not sure about the sim
Please Log in or Create an account to join the conversation.
- phillc54
-
- Offline
- Platinum Member
-
Less
More
- Posts: 5723
- Thank you received: 2095
24 Mar 2025 05:59 #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:I cannot get it to fire by activating the float switch though.
[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
The following user(s) said Thank You: rodw
Please Log in or Create an account to join the conversation.
- rodw
-
Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 11216
- Thank you received: 3744
25 Mar 2025 02:57 #324851
by rodw
Replied by rodw on topic 2.9.3 - Stuck in wrong state and stops
Attached is the clients full config.
As I thought, runstep.hal is not loaded in the .INI file (ie commented out) so keep looking!
It is appreciated.
As I thought, runstep.hal is not loaded in the .INI file (ie commented out) so keep looking!
It is appreciated.
Please Log in or Create an account to join the conversation.
- phillc54
-
- Offline
- Platinum Member
-
Less
More
- Posts: 5723
- Thank you received: 2095
28 Mar 2025 03:12 #325135
by phillc54
Replied by phillc54 on topic 2.9.3 - Stuck in wrong state and stops
I made a sim from your config and after lots of testing I was unable to replicate the issue.
It should be noted that I did not test pendant, ohmic, or step boost, I commented these out and also replaced my_Plasma.hal with sim_no_stepgen.tcl which is the standard QtPlasmaC sim hal file. I am only able to test in a sim as I have no hardware. If you can replicate it in a sim then could you post the sim and the workflow that causes it.
I did note that in showstopper.ini the relationship between the MAX_VELOCITY and MAX_ACCELERATION settings for the X, Y, and A axes and their corresponding joints are incorrect.
It should be noted that I did not test pendant, ohmic, or step boost, I commented these out and also replaced my_Plasma.hal with sim_no_stepgen.tcl which is the standard QtPlasmaC sim hal file. I am only able to test in a sim as I have no hardware. If you can replicate it in a sim then could you post the sim and the workflow that causes it.
I did note that in showstopper.ini the relationship between the MAX_VELOCITY and MAX_ACCELERATION settings for the X, Y, and A axes and their corresponding joints are incorrect.
The following user(s) said Thank You: rodw
Please Log in or Create an account to join the conversation.
- rodw
-
Topic Author
- Offline
- Platinum Member
-
Less
More
- Posts: 11216
- Thank you received: 3744
28 Mar 2025 07:52 #325144
by rodw
Replied by rodw on topic 2.9.3 - Stuck in wrong state and stops
Thanks for trying. The hal files you bypassed are all well tested and are all for specific hardware so you could not implement them.
When you say that the velocity and acceleration is incorrect, I think you are expecting to see the axes values higher than the joints to allow for external offset ratio. But in practice, that is not necessary. I have them set as I always have since before external offsets was pushed to master 7-8 years ago. After all, I was the one who worked out that we can double velocity and acceleration and use a 0.5 ratio because THC is mutually exclusive with gcode motion. The author of external offsets had not thought of this at the time. This was a major discovery that enabled THC control and ultimately qtplasmac without compromising velocity and acceleration.
I might add that there were a lot of constraints due to the machine design that we retrofitted with showstopper but the owner is happy as one job that took 2 hours now only takes 20 minutes because of QTplasmac.
Its little things like this that prevents him walking away from the machine on his lunch break! Hopefully, we will find a solution one day.
When you say that the velocity and acceleration is incorrect, I think you are expecting to see the axes values higher than the joints to allow for external offset ratio. But in practice, that is not necessary. I have them set as I always have since before external offsets was pushed to master 7-8 years ago. After all, I was the one who worked out that we can double velocity and acceleration and use a 0.5 ratio because THC is mutually exclusive with gcode motion. The author of external offsets had not thought of this at the time. This was a major discovery that enabled THC control and ultimately qtplasmac without compromising velocity and acceleration.
I might add that there were a lot of constraints due to the machine design that we retrofitted with showstopper but the owner is happy as one job that took 2 hours now only takes 20 minutes because of QTplasmac.
Its little things like this that prevents him walking away from the machine on his lunch break! Hopefully, we will find a solution one day.
Please Log in or Create an account to join the conversation.
- snowgoer540
-
- Offline
- Moderator
-
Less
More
- Posts: 2431
- Thank you received: 802
29 Mar 2025 13:49 #325245
by snowgoer540
Replied by snowgoer540 on topic 2.9.3 - Stuck in wrong state and stops
How self-righteous must one be to ask the component creator for help, only to turn around and explain why he's wrong? You’re always quick to highlight your own contributions; maybe it's worth pausing to genuinely consider the input provided.
In addition to what Phill said, when I looked at the config, I noticed that JOINT_3 STEPGEN_MAXVEL is not set to the recommended value of 25% larger than MAX_VELOCITY. Instead it's set only 4.16% greater than MAX_VELOCITY.
For Joints 0, 1, 2, STEPGEN_MAXACCEL is 50% greater than MAX_ACCELERATION (recommended is 25%).
For Joint 3 STEPGEN_MAXACCEL is 87.5% greater than MAX_ACCELERATION (recommended is 25%).
To highlight Joint 3 (the joint associated with the axis you're having trouble with) inconsistencies:
These inconsistencies stand out, and regardless of how long you’ve been using these settings, the values for both the axes and joints are still not aligned with best practices/recommendations. It's difficult to predict the exact repercussions because, generally speaking, most configurations follow these minimum recommendations. Yours is definitely the outlier.
In addition to what Phill said, when I looked at the config, I noticed that JOINT_3 STEPGEN_MAXVEL is not set to the recommended value of 25% larger than MAX_VELOCITY. Instead it's set only 4.16% greater than MAX_VELOCITY.
For Joints 0, 1, 2, STEPGEN_MAXACCEL is 50% greater than MAX_ACCELERATION (recommended is 25%).
For Joint 3 STEPGEN_MAXACCEL is 87.5% greater than MAX_ACCELERATION (recommended is 25%).
To highlight Joint 3 (the joint associated with the axis you're having trouble with) inconsistencies:
- STEPGEN_MAXVEL is only ~4% greater than MAX_VELOCITY
- STEPGEN_MAXACCEL is 87.5% greater than MAX_ACCELERATION
These inconsistencies stand out, and regardless of how long you’ve been using these settings, the values for both the axes and joints are still not aligned with best practices/recommendations. It's difficult to predict the exact repercussions because, generally speaking, most configurations follow these minimum recommendations. Yours is definitely the outlier.
Please Log in or Create an account to join the conversation.
Moderators: snowgoer540
Time to create page: 0.291 seconds