Testing two motors with the ODrive v3.0. These motors are controlled independently by the controller, but they are running the same commands. Maybe i will upload a videos when they are doing different things. odriverobotics.com
The "rotate a little right, then a little left" part of the sequence seen in the video is the encoder calibration which resolves this. It drives a current in the stator and lets the rotor sync to the magnetic field: but it doesn't sync perfectly, so it goes both directions to cancel the lag.
+3D Printwiz the resolution depends on the encoder. In this case, my encoders were 2400 counts per rev. There are many possible interfaces. One of them will be similar to G code, so many different software should be compatible.
OH good, so the board takes care of the encoders, I do not have to process it through arduino? How about torque output, I know it is fast from the videos, but since it is moving on xy plane I could not estimate the torque. I will be using it for a robot arm, and might gear it down to get more torque.
3D Printwiz correct, the odrive takes care of the encoders. To see the expected torque from a range of motors, check this spreadsheet: docs.google.com/spreadsheets/d/12vzz7XVEK6YNIOqH0jAz51F5VUpc-lJEs3mmkWP1H4Y/edit?usp=drivesdk
Sorry but I think that link is not correct you said: "my encoders were 2400 counts per rev." in another comment and the product link is a 600 counts per rev encoder
Just reading through the comments, and I'm not sure where the link you're talking about is, but it is normal for quadrature encoders to quote PPR in terms of a full cycle of quadrature encodings as a single "pulse". With decent hardware each of the transitions of the quadrature encode can be used. This gives an effective encoding of x4 the PPR or, in this case, 2400 counts per revolution from a 600PPR device.
