Maybe a bug around door and parking

[Klippert]

Hello,

I've noticed a couple of odd things around using the Door switch (and parking) as a "pause" to intervene when things sometimes does not go to my liking... And that happens more than it should...

So here is first thing that happens:

I have a simple program that runs with two tools.

1. I home the machine
2. I do a M61Q70 (first tool) and probe using the probing tap on my tool probe.
3. I run the program, and it starts and runs beautifully...
4. I press my door switch, and trigger a pause and park maneuver - Z goes up and spindle stops.
5. I stop my program
6. I move my X-coordinate to get better material usage (first tool was just facing)
7. I rewind the program and his start.
8. It starts over and runs the first tool all good.
9. I goes to the toolprobe and ask for the second tool
10. I change tool
11. $tpw and tool is probed
12. It now proceeds to dig a 7mm deep hole in my spoilboard before i catch it with the emergency stop.

I've had this same scenario happen on a couple of cases. If i use the door and move things around, things usually go pearshaped later in the process. Unless i do a full reset and re-home. (i've no idea if that actually is necessary.)

The second situation is same scenario - a program with tool changes.

1. I home the machine
2. I do a M61Q70 (first tool) and probe using the probing tap on my tool probe.
3. I run the program, and it starts and runs beautifully...
4. I press my door switch, and trigger a pause and park maneuver - Z goes up and spindle stops.
5. I stop my program
6. I make some changes to workholding...
7. To get out of the "door" mode, i hit start - spindle goes down to where it was. (as I guess it shold) and door mode disappear.
8. Now to move the spindle to a safe position i hit the jog button up 10mm once - spindle goes up 10mm.
9. I hit jog button up again, and nothing happens.
10. I have to reset and start everything over - it seems like it's all locked up....

Please let me know what you think?`

Best
Kristoffer

[terjeio]

This will have to wait until I am back home in a couple of weeks since I do not have access to a machine.

[Klippert]

No problem. Im intrigued to see if there is an actual issue or its just me tor. 24. okt. 2024 kl. 07.53 skrev Terje Io ***@***.***>:

…

This will have to wait until I am back home in a couple of weeks since I do not have access to a machine. — Reply to this email directly, view it on GitHub <#610 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM3JUEEVHQ2BYHWH6OLMMZLZ5CDMNAVCNFSM6AAAAABQBIC6JSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZUGM3DAOJWGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Klippert]

Ping?

[terjeio]

The first issue is likely due to the tool offset beeing reset when the Stop command is sent. I have changed this in the last commit. Both the tool offset and the last selected offset (G54...) is now preserved over a stop. I may have to add a setting to enable this...
I am not able to reproduce the second issue (jog lock up), can you provide a minimal gcode file that fails that I can use for testing?

[Klippert]

Hello terje,

thanks for looking into the issue and thanks for the fix.

Now it’s me that is away - but I’ll be back after Christmas, then I’ll find an example where the lockup occurs. I think all my g code files would reproduce the error - but let me test again

best