BasicMicro

To home in an arduino, you set the limit switch to home(user) mode. Then at the beginning of your arduino program you check the limit switch status and it if is set(at home) move the motor forward until the limit switch status is cleared. Then whether the motor was original in the limit or now, you ...

Thank you for all the updates and publishing your code.

Home is by definition position 0. Always. On startup you need to move the motor back into the home switch so it can zero the encoder value. You can do this with the auto homing function(Home(Auto) or you can move the motor after power up using control commands(Home(User).

Unfortunately we do not offer a mode like you describe.

I believe I already answered you in an email but this is for everyone. Manually put your Roboclaw into bootloader mode. Power down. Hold the Mode button pressed, Power back up. Let go of the Mode button. The 3 LEDs should start to cycle. Motion Studio should now recognize the Roboclaw and let you up...

If you are using position control than that is exactly the cause of the motors being hot. Position control holds the position. You can add larger deadzone so you can get to a position where it wont power the motor but that will only work when there is no external force.

When not driving the motor the Roboclaw controller will draw around 30ma. There is no power off option. You must make sure you are not driving the motors to guarantee the low power state. You can do that by sending a duty command with 0 duty to each motor channel.

Yes it will. That is the nature of the beast. There is no example in the python code. We highly recommend setting up PIDs in Motion Studio only. 1. You absolutely must use an acceleration value with any speed command if you enable speed error limits. Other wise you will have an instantaneous error e...

Roboclaw has a 10ms timeout on replies and retries is set to 3 times by default. There is no location in the Roboclaw library that would delay for as long as 1 second. That actually sounds like something someone would add to try debugging a problem.

It most likely is not. Current is measured through a shunt resistor and an A/D pin on the main processor. There is little to nothing that can break. You symptom indicates a false overcurrent at low duty cycles. This can be caused by too low a current blanking percentage. The default is 5.4% which ca...