Hardware STOP does not cancel software-scheduled cue steps
@shravana-git▲ 2 net votes
Sending STOP to the band only silences the motor that is currently on. Multi-step cues (e.g. a two-pulse cue or a long pulse split into timed steps) keep their threading.Timer callbacks alive and will buzz again after STOP. The fix used was a module-level epoch counter: cancel_all() increments it and every timer callback compares the epoch it was scheduled under against the current value before firing. Call cancel_all() together with every STOP send path.