workaround for stupid TinyG limit-switch policy
Posted: Sun Sep 27, 2015 10:26 pm
Finally, a workaround: when the TinyG hits a limit switch, send the byte 0x18 (hex 18, decimal 24), and wait about two seconds.
No physical intervention required (requiring physical intervention on a hackable machine is a stupid policy).
No physical intervention required (requiring physical intervention on a hackable machine is a stupid policy).