No actually my 24V lipo is a 6s so the max it can go to is 25.2V, which is why I dont understand why my vbus_voltage shows such a high value as well as the overvoltage error is triggered
Hello, can you give an update on this?
Thanks for following up!
Let’s make sure this isn’t a hardware issue with the ODrive – do you have an adjustable power supply where you can test the ODrive with a few different bus voltages and see what the ODrive reads?
Yes I do, do you want me to test it at specific voltages or give you readings of random that I select?
Random that you select is fine!
ohk sure, ill update u within 24hrs
Hello,
These are the following Voltages versus the Voltages I observed on the vbus_voltage of odrive -
5.7V - 5.75V
11.3V - 11.9V
18.9V - 19.7V
22.1V - 23.09V
13.9V - 14.6V
Hmm, that seems close enough I don’t immediately think the S1 is the issue. If there was an issue with the analog sense circuits, it would be way off.
Do you have a multimeter you can use to test the battery voltage versus the S1’s sensed voltage? You can measure the voltage right on the top of the S1’s green screw terminals.
Yeah I’ll do that
Hello, the previous issue has been resolved — thank you for your help. I’d now appreciate your advice on a new problem I’m encountering.
I’m using a 4260 APS motor rated for a maximum of 65A, controlled by a fully functional ODrive S1. Currently, I’m seeing high current draw when commanding the motor to move from position -4 to -43, with trajectory limits set to acceleration = 100 and deceleration = 120. The motor draws up to 72A during this move. When I set a hard current limit of 80A, it worked for two trials. However, after this when I switch the motor to closed-loop control, it continuously draws 65A — even without any load.
I have two questions:
- What is the safe maximum current limit I can set on the ODrive S1 for this motor?
- Why might the motor be drawing such high current in closed-loop mode despite having no external load? It is working against gravity (as it controls pitch), but previously it operated within current limits without issue. This excessive draw is a recent development.
Hi! This definitely sounds like an issue with the encoder slipping – high current draw in situations that don’t necessitate it is a classic symptom. What encoder are you using?
Normally this would trigger a spinout error, did you change the spinout thresholds?
No there is one factor that can cause the high current draw which is a specific rebound force at the topmost pitch position, so yes that might be it but my concern is it hasnt happened till date and suddenly a few days ago this issue started coming
Im using amt102 incremental encoders
It triggers a current_limit_violation error
also yes the new addition is the rebounding mechanism on it, hence I also want to know are there any ways to compensate for the hgih current being drawn for that flash of a second without damaging existing components
Can you show some pictures of how your encoder is mounted? And can you share your S1 configuration? You can run odrivetool backup-config config.json then paste the config.json here.