-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AMC-BLDC: the supervisor needs to manage the motor-hal errors #40
Comments
Hi @valegagge Just for clarification, in which manner the Is there a low-level check? |
There's also a connection to #15. |
Hi @pattacini!
The driver calls this callback in case of faults and here sets the overcurrent flag. For this, I'm referring to an hardware-overcurrent, while in the supervisor, we check if the filtered current goes beyond the configured limit. |
Checking the current code of the AMCBLDC board, the External fault is managed by polling instead of on ISR. So I think to implement the same solution for the hardware over current. Moreover, I verified that in the 2FOC fw, the hardware over current and software over current are notified to the EMS using the same bit in the status message. Therefore I'll adopt the same solution. In the future, if we want to distinguish the two faults we need to change the can protocol. I suppose that the callback |
I just write down some notes how to address this issue:
|
Following the work done here robotology/icub-firmware#360 (comment), we want to update the supervisor in order to manage the motor-hal errors:
hardware-overcurrent
and hall-sequence-error.Dod
Note: the test is not simple because this error are hw-related, so we need to find a way to simulate them.
The text was updated successfully, but these errors were encountered: