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
Looks like my decision made in #5 to use the ENABLE pin over the SLEEP pin in the Pololu examples has caused a certain amount of confusion (#51#67 . Besides the wiring issues, ENABLE is active LOW in most boards but active HIGH in at least one, while SLEEP behavior of active HIGH is more consistent.
Make the enable active state configurable (maybe something like setEnableActiveState(bool))
Default to controlling SLEEP pin (this is a breaking change as it reverses the previous logic)
Add a 1-2µs delay when enabling the driver (exact timing depends on board)
see if that causes any problems with multiple boards hooked to the same SLEEP line.
The text was updated successfully, but these errors were encountered:
Looks like my decision made in #5 to use the
ENABLE
pin over theSLEEP
pin in the Pololu examples has caused a certain amount of confusion (#51 #67 . Besides the wiring issues,ENABLE
is activeLOW
in most boards but activeHIGH
in at least one, whileSLEEP
behavior of active HIGH is more consistent.setEnableActiveState(bool)
)The text was updated successfully, but these errors were encountered: