BasicMicro

With a microcontroller(like an arduino) you could potetnially setup somethign like that. You would need to run slowly when doing this "homing" from current readings to be safe. As for using a limit switch, you misunderstand it a little. It will move for UP TO 3 seconds(before timing out) to get out ...

All of them stopping at the same time seems to be pointing to an E-Stop problem. Disable the E-Stop inputs on all the Roboclaws and see if the problem goes away. If it does you have narrowed down the cause. If it doesn't, then the next step would be to look at your coding on the Jetson. You will nee...

How have you wired up your encoders? Have you checked the output from your encoders on an oscilloscope? Some encoders require external pullup resistors(usually to 5v) to operate properly.

We have an Arduino library you can use to communicate with the Roboclaw. Your question is way to general to be answered directly. We cant possibly write your code for you. You will need at least some experience writing programs on an Arduino.

The first answer in the link below, I believe will let you do what you want.

https://askubuntu.com/questions/49910/h ... l-adapters

email support@basicmicro.com. Please include screen shots of all your settings, a description of the motors and encoders being used. Any more details you think important from this thread. I will have to setup a similar system so please be detailed. Most likely I will not be able to test this until t...

This indicates opening the virtual comport failed. Make sure you used the proper name of the comport. Windows and Linux use completely different naming conventions.

1. You need your encoders to work correctly before anything else.
2. No, this is not normal. You should be able to manually move the motors extremely slowly and STILL get clean encoder readings. My guess is you need to add 5v pullups to the encoder lines on your motors.

If the autotuner fails it will not update the PID values. The autotuner first moves back and forth slowly. This is to get an approximate QPPS. Then it will oscillate back and forth fast. When this second stage does not happen(or appears not to happen) it usually indicates an encoder problem. What is...

That is clearer. Thank you. The default accel commands are documented in the manual. The default speed commands were just added and havent been updated in the manual yet. The command numbers are: SETM1DEFAULTSPEED 70 SETM2DEFAULTSPEED 71 Send: addr, cmd, speed (2bytes), CRC16(2 bytes). Receive: 0xFF