Hi everyone, I've noticed what I think is a regression, but before filing an issue I wanted to see if anyone else is affected. This is not an unexpected e-stop condition - the e-stop is operating correctly.
When I have a volatile home joint configured, I can e-stop the machine when the planner mode is in automatic (running a program) and the expected axis is unhomed and no error message is emitted from command.c. However, if I jog the machine and simultaneously press the emergency stop the error message is emitted and the joint fails to unhome (see: https://github.com/machinekit/machinekit/blob/master/src/emc/motion/command.c#L1367). In my hal file, the motion-command handler function comes before the motion-control function, which I thought was standard practice. I *think* this means that the manual jog handler does not set the InPosition flag before the unhome command (issued via the ESTOP handler) is invoked, causing the problem. Any thoughts? Thanks, Devin -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
