M6/Tool Change BTN783 causes erratic motion if interrupted

[DanStory]

I have found if I interrupt a tool change (cycle stop) that was initiated by button 783, the next time motion is called, it moves erratically before continuing normally. Additionally cycle stop becomes unresponsive and typically won't stop movement until that line of g-code (be it in a program or submitted via exec.Code[list]) is finished.

Executing M6 via g-code or MDI does not seem to have this effect and behaves as I would expect, stops nearly immediately (decel) and doesn't erratically jerk around on the next call of motion. If I change the button to a custom macro (20000), it also seems to behave normally.

I have recorded this behavior in action:
https://www.youtube.com/watch?v=ge-G9buTXsU

here is the M6/M20000 macro code:

Code: Select all

while(exec.IsMoving()){
    exec.Wait(25);
}

exec.Code("G90 G01 F50 G53 G0 Z0.0");
exec.Code("G90 G01 F50 G53 G0 X-8.0 Y-8.0");

while(exec.IsMoving()){
    exec.Wait(25);
}


Software version: 1.2115
Firmware version: 1.0370
Hardware version: 1.0000
API version: 2.1900
Device type: UC300ETH_UB1

[ger21]

A workaround is to create your own tool change button, that just runs a line of g-code with M6 in it. That's what I do.

[DanStory]

Yeah, was the initial plan. Just want to make sure it is addressed and gets fixed. I haven't tried yet but makes me wonder if other specialty buttons that execute a macro underneath behave the same. i.e. button 196 for tool length probe that executes M31.

[cncdrive]

Dezsoe, could you please test this issue?
Thanks.

[Delco]

I have had the same erratic issues when interupting a probing cycle.

[cncdrive]

The issue is probably in your screenset macroloops.
Could you try to disable all macroloops to see if the issue goes away or not.
If it does then it is something to do with the macroloops, then you will have to contact the creator of the screenset.

[Delco]

The issue is probably in your screenset macroloops.
Could you try to disable all macroloops to see if the issue goes away or not.
If it does then it is something to do with the macroloops, then you will have to contact the creator of the screenset.

I have the std screenset on my system with no macroloops active and it has exhibited the same behaviour . I have since changed the probe button to active a macro running M31 and the problem has not reappeared.

[DanStory]

Is this addressed for next pending software release?

[dezsoe]

I don't remember what happened in January, so I'll have to test it again. However, these lines are absolute invalid:

Code: Select all

exec.Code("G90 G01 F50 G53 G0 Z0.0");
exec.Code("G90 G01 F50 G53 G0 X-8.0 Y-8.0");


You must not have G0 and G1 in one sentence.

I'll test it when I get to my machine.

[Battwell]

i have had this- in fact its just popped its ugly head up again this week
read my post in ask a question from support just posted.