'Run from here' calls remapped M-code multiple times
- chowderhead
- Offline
- Senior Member
-
Less
More
- Posts: 57
- Thank you received: 11
22 Jul 2023 16:13 #275998
by chowderhead
Replied by chowderhead on topic 'Run from here' calls remapped M-code multiple times
My user name is hardly ironic; I apologize for being thick and I greatly appreciate your insight and help! The application at hand isn't conventional - rule breaking is kind of the point. Consider the coating a tenacious flux; it's not so much a hardware problem as a process reality.
And to complicate things more, the tool path is not simple. A change in direction is likely to occur before arc initiation, which I think means the intervening g-code must be repeated, but with a stable arc. As for tolerance, I would prefer if the path over-ran the arc initiation point.
Everything works to plan if the tool path runs to completion without upset. The problem occurs when recovering from upsets and invoking 'Run from here.'
And to complicate things more, the tool path is not simple. A change in direction is likely to occur before arc initiation, which I think means the intervening g-code must be repeated, but with a stable arc. As for tolerance, I would prefer if the path over-ran the arc initiation point.
Everything works to plan if the tool path runs to completion without upset. The problem occurs when recovering from upsets and invoking 'Run from here.'
The following user(s) said Thank You: tommylight
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 18563
- Thank you received: 6219
22 Jul 2023 16:57 #276004
by tommylight
Replied by tommylight on topic 'Run from here' calls remapped M-code multiple times
Did you try running M55 from MDI before "run from here"?
Please Log in or Create an account to join the conversation.
- chowderhead
- Offline
- Senior Member
-
Less
More
- Posts: 57
- Thank you received: 11
22 Jul 2023 17:47 #276007
by chowderhead
Replied by chowderhead on topic 'Run from here' calls remapped M-code multiple times
Yep. It's counterproductive as it deletes the temporary g-code file same as what the interpreter does...
Please Log in or Create an account to join the conversation.
- chowderhead
- Offline
- Senior Member
-
Less
More
- Posts: 57
- Thank you received: 11
24 Jul 2023 14:15 #276154
by chowderhead
Replied by chowderhead on topic 'Run from here' calls remapped M-code multiple times
I've come up with a workaround, but it it seems kludgy: Rename the temporary g-code file if it exists at the time the arc extinguishes. At initiation of the arc, check if the renamed file exists and rename back to the original name.
I was hoping there existed a flag of some sort to indicate the g-code wasn't actually being executed, just parsed to reestablish state. It seems something like a halui.mode.parsing (or whatever would be the logical pin name) would be useful.
Thanks for the help!
I was hoping there existed a flag of some sort to indicate the g-code wasn't actually being executed, just parsed to reestablish state. It seems something like a halui.mode.parsing (or whatever would be the logical pin name) would be useful.
Thanks for the help!
Please Log in or Create an account to join the conversation.
Time to create page: 0.104 seconds