- Posts: 19306
- Thank you received: 0
ESC in axis 2.9.0 is that a proper behaviour
4 years 4 months ago #244352
by andypugh
Replied by andypugh on topic ESC in axis 2.9.0 is that a proper behaviour
github.com/LinuxCNC/linuxcnc/blob/master...sk/taskintf.cc#L1901
Looks likely, and calls:
github.com/LinuxCNC/linuxcnc/blob/master...tion/command.c#L1631
Though that all looks OK. Possibly the issue is that ESC is not calling spindleAbort?
Looks likely, and calls:
github.com/LinuxCNC/linuxcnc/blob/master...tion/command.c#L1631
Though that all looks OK. Possibly the issue is that ESC is not calling spindleAbort?
Please Log in to join the conversation.
4 years 4 months ago #244379
by radom
from source,
I don't know how to use git bisect
if you can tell me what to type at the terminal I will do it
Replied by radom on topic ESC in axis 2.9.0 is that a proper behaviour
Are you building LinuxCNC from source, or using packages?
(If from source, do you have the time to do a git bisect to find when the issue was introduced?)
from source,
I don't know how to use git bisect
if you can tell me what to type at the terminal I will do it
Please Log in to join the conversation.
4 years 4 months ago #244439
by andypugh
Replied by andypugh on topic ESC in axis 2.9.0 is that a proper behaviour
The bisect process is fairly simple, but it needs a "good" and a "bad" git tag, and finding the "good" one is something that I can't do until I get back to my LinuxCNC machines next week.
Please Log in to join the conversation.
4 years 4 months ago #244550
by cmorley
My next thought is that the interpreter state is not changed from m3 to m5
I see a delay in AXIS update of the active gcodes but entering an s either way will start the spindle.
Replied by cmorley on topic ESC in axis 2.9.0 is that a proper behaviour
Yes that seems right.andypugh post=244352 userid=723https://github.com/LinuxCNC/linuxcnc/blob/master/src/emc/task/taskintf.cc#L1901
Looks likely, and calls:
github.com/LinuxCNC/linuxcnc/blob/master...tion/command.c#L1631
Though that all looks OK. Possibly the issue is that ESC is not calling spindleAbort?
My next thought is that the interpreter state is not changed from m3 to m5
I see a delay in AXIS update of the active gcodes but entering an s either way will start the spindle.
Please Log in to join the conversation.
Time to create page: 0.043 seconds
