Roboclaw shuts down and needs power cycle
Posted: Sat Mar 02, 2019 6:49 pm
I'm using a Roboclaw 2x15A with the ROS driver and of course, in turn, it uses the python driver. I'm sending commands over USB from a Raspberry Pi3.
Sometimes (I think) one of the two sides will detect an overcurrent and shut down. After that sending more command does nothing. The side not shut down still responds to commands from USB.
Currently, I can correct this by power cycling the Roboclaw. Then I'm up and running again.
Question: The manual says the this resets when the overcurrent is corrected. But I find a power cycle is needed.
Question: Is there a way to reset the board over the USB cable? If not perhaps a pin?
I wrote about this before and said I never see a red LED. Should I see a red LED if only one side is nonresponsive?
Sometimes (I think) one of the two sides will detect an overcurrent and shut down. After that sending more command does nothing. The side not shut down still responds to commands from USB.
Currently, I can correct this by power cycling the Roboclaw. Then I'm up and running again.
Question: The manual says the this resets when the overcurrent is corrected. But I find a power cycle is needed.
Question: Is there a way to reset the board over the USB cable? If not perhaps a pin?
I wrote about this before and said I never see a red LED. Should I see a red LED if only one side is nonresponsive?