M03 Sub Routine File Location
- Quail
-
Topic Author
- Offline
- New Member
-
Less
More
- Posts: 8
- Thank you received: 4
14 Nov 2025 01:21 #338335
by Quail
M03 Sub Routine File Location was created by Quail
Currently working on a machine using the QTPlasmaC GUI, and I was wondering if there was any way to access the M03 sub routine file anywhere? I would like to edit it to disable the homing of the Z-axis that it does.
Right now the machine fires the torch using a regular output pin, which works fine when everything is going perfectly, but when a limit is triggered or the E-stop is pressed, it doesn't quite understand that it needs to disable the torch as well.
I was able to almost work around this by messing with the hal file and using an and function to turn off the the torch when the e-stop is pressed, but the problem is when the machine is reset it has a memory of last being told to turn on, and so the torch fires.
My thinking is that if I can go in and mess with the M03 instructions I can just completely disable the Z-homing because all of this has been a work around for that, because my machine has no z-axis.
Thanks!
Right now the machine fires the torch using a regular output pin, which works fine when everything is going perfectly, but when a limit is triggered or the E-stop is pressed, it doesn't quite understand that it needs to disable the torch as well.
I was able to almost work around this by messing with the hal file and using an and function to turn off the the torch when the e-stop is pressed, but the problem is when the machine is reset it has a memory of last being told to turn on, and so the torch fires.
My thinking is that if I can go in and mess with the M03 instructions I can just completely disable the Z-homing because all of this has been a work around for that, because my machine has no z-axis.
Thanks!
Please Log in or Create an account to join the conversation.
- Quail
-
Topic Author
- Offline
- New Member
-
Less
More
- Posts: 8
- Thank you received: 4
14 Nov 2025 01:47 #338337
by Quail
Replied by Quail on topic M03 Sub Routine File Location
I may not be asking the right question. Is there a way to ensure that when the estop is pressed or a limit switch is triggered, to tell the torch to come off and not come back on?
I thought maybe by editing the M3 g-code, I could get it to work for my machine and also get the estop and limits to turn off the torch.
Is there any way to link the output pin 00 to the estop and limits, in such a way that it wont turn back on even when the machine is reset, and stay off until it gets a new command to turn on?
My next idea is to make my own M code that has my needs in it, but i feel that i will still run into the same issues where the estop either doesnt turn off the torch, or if it does, the machine "remembers" it was firing and immediately arc.
I thought maybe by editing the M3 g-code, I could get it to work for my machine and also get the estop and limits to turn off the torch.
Is there any way to link the output pin 00 to the estop and limits, in such a way that it wont turn back on even when the machine is reset, and stay off until it gets a new command to turn on?
My next idea is to make my own M code that has my needs in it, but i feel that i will still run into the same issues where the estop either doesnt turn off the torch, or if it does, the machine "remembers" it was firing and immediately arc.
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
Less
More
- Posts: 20924
- Thank you received: 7132
14 Nov 2025 03:30 #338340
by tommylight
Also it would not turn on until F9 is pressed or an M3 is issued from MDI or gcode.
That is basic plasma behavior, so i doubt something was changed there.
Replied by tommylight on topic M03 Sub Routine File Location
Have not tested QtPlasmaC in quite some time, but for sure it did disable/shut off the torch on any of those, and also on program stop and program pause and when hitting ESC.
Right now the machine fires the torch using a regular output pin, which works fine when everything is going perfectly, but when a limit is triggered or the E-stop is pressed, it doesn't quite understand that it needs to disable the torch as well.
Also it would not turn on until F9 is pressed or an M3 is issued from MDI or gcode.
That is basic plasma behavior, so i doubt something was changed there.
Please Log in or Create an account to join the conversation.
Time to create page: 0.088 seconds