I would use a completely different approach; it wouldn't be HAL based.
I would provide signals that could be output from gcode to HAL and those
that could be read by gcode from HAL. They would be used to sense
microswitches, command relays, etc. Reading a switch would be done like
probing already
Is this the way we should approach sequences of motions for toolchanging
and the like? Comments, please.
HAL-BASED MOTION CONTROL
Often, it's desirable to command a sequence of motions outside of g-code.
For instance, a number of movements may be required during a tool
c
