You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix direction not being correctly calculated (#15)
There were several issues when calculating/detecting the direction
of movement with DirectionalOdometer. Specifically, the first problem
was that the interrupt was triggered to be invoked on pin state change
instead of a rising edge which was the initial intention.
Additionally, determining the distance should only be done within the
interrupt, since the state of the direction pin is only meaningful when
the pulse pin is on a falling or rising edge.
0 commit comments