Open greener1 opened 7 years ago
By looking at how the Chilipeppr app handles feedhold/resume, successfully. I see that on resume, in addition to the cycle start command:
~
it also sends a queue request:
{"qr":""}
When I do that too, the resume works as expected, stopping at the initially requested position.
So maybe the documentation just needs to be updated to show that the resume command is actually a combination of two commands. As shown in line 691 of the Chilipeppr code it's really:
'~\n{"qr":""}\n'
I'm running : Firmware Version : 0.97, Firmware Build : 446.19, Hardware Version : 8 I'm using the edge branch because I need the transaction IDs.
After sending a G-code fragment for a relative move, then sending a feedhold (causing the motion to stop as expected), and then sending a cycle start, the movement resumes (as expected) but often goes past the point requested in the original G-code, and in fact just keeps going. For example:
... continues to ever larger posy, even though it should have stopped at posy ~= 20
Likewise on the Z axis:
... again it continues even though only a change in Z by only -10 units was requested.
Am I doing something wrong here? Sometimes the cycle start after the feedhold does result in the resumed movement only continuing to the requested position.