Gmoccapy Bug?

Found something weird with both the LCNC 2.7 and 2.8 versions of gmoccapy.....

With a file running press Pause, then press Stop. In both versions the spindle turned off but the axis moved as it was doing so, ala Mach3. I did not expect this so I didn't bother to raise the Z from where it was and the machine dragged the slowing bit through the job until whatever was stored in whatever buffer ran out.

I know this isn't a LinuxCNC thing 'cause Axis and PathPilot don't do it, they just stop the spindle in the above scenario.

Pressing just Stop works "as intended", Spindle stops and the axis' don't move at all.

I will chech as soon as possible,
I have not noticed that.

Norbert

@racedirector,

I could only test with sim, as I destroyed yesterday my spindle and have disarmed my machine
But I may have found a solution. I added a additional command.aboard() even if that command is
called one cycle later from hal_action.

I pushed that to master (gmoccapy 2.2.2).
Please pull and test that one. If the work around solve the isue, I will add that too to 2.7 and 2.6 release.

Norbert

I also have a similar problem. I can pause the machine but if I stop the machine in mid program the machine will skip(move) to a new line sometimes several hundred lines down in the program and then stop.

How do I get gmoccapy 2.2.2? and how do I install it?

newbynobi wrote: @racedirector,

I could only test with sim, as I destroyed yesterday my spindle and have disarmed my machine
But I may have found a solution. I added a additional command.aboard() even if that command is
called one cycle later from hal_action.

I pushed that to master (gmoccapy 2.2.2).
Please pull and test that one. If the work around solve the isue, I will add that too to 2.7 and 2.6 release.

Norbert

Thanks Norbert

I will do that today, too hot to be in the garage today, 35C +

We are at -9 degree celsius?