Is resolution required to match with dual encoders?

Support ODrive S1 Support
1

Hi all,

I’m looking into using an ODrive S1 controller to drive a BLDC for a telescope mount which requires high resolution. To achieve this, I plan on using a optical encoder with a resolution of approximately 0.2 arcseconds as the load encoder. The load side is connected to the BLDC via a 160:1 reducer, meaning in order to match the resolution of the load encoder, the commutation encoder would need to be 16 bit or higher.

Does the commutation encoder need to have equivalent or higher resolution (after reduction) as the load encoder in order to make use of the load encoder’s high resolution? I imagine if the resolution for the commutation encoder is too low, then the ODrive will not be able to reliably position the BLDC within the precision of the load encoder.

Thank you!

Edit for clarity: I shouldn’t need this level of resolution for positional control (resolution to several arcseconds is fine there), but I do need smooth motion at very low load velocities (i.e. 15 arcseconds / s)

2

Hey there,

Super cool application!

Generally no need for commutation and load encoders to match resolution. It’s true that if the commutation encoder is extremely low precision (e.g. hall sensors), you get some torque ripple and inaccuracy in commutation – but you get diminishing returns quite fast; I don’t think that there would be a measurable difference between a 512 CPR and a 4096 CPR encoder in terms of torque ripple, outside of large transient response, which here would only happen if the telescope falls over :wink:

The main reason you would want a high-resolution commutation encoder is if you plan to run your velocity loop off the commutation encoder, as opposed to the load encoder – that may be a good idea here if your reducer has a lot of backlash. That being said, I think you could probably just use the (14-bit) AMT21 at first and give that a shot.