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).
workaround for stupid TinyG limit-switch policy
-
WayOutWest
- Posts: 198
- Joined: Thu Jul 16, 2015 12:18 am
- Location: Washington State, USA