You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 3, 2019. It is now read-only.
We had a mishap a last week that killed two of our motors. It happened because I was making the arm move with brushed dc motors for the CDR, so the VESCs were configured for brushed operation. I forgot about this and plugged them into the rover's drive system. Brushless DC motors don't like having two of their windings shorted together under maximum current conditions...
Aside from just being more carefull, it would be nice to have the USBServer read back the settings of each motor and print an error message if they are improperly configured. It could then write the proper configuration if needed. There are VESC commands for this, so it actually isn't that difficult to do as the trickiest implementation details are already there.
We could also run the requestSubscription method in a new threads to get the USBServer starting sooner.
Add read configuration message to PyVESC.
Read configuration from USBServer
Find motor type field in configuration and check if it is correct
Add write configuration message to PyVESC
If motor type is wrong, write proper configuration to VESC.
The text was updated successfully, but these errors were encountered:
We had a mishap a last week that killed two of our motors. It happened because I was making the arm move with brushed dc motors for the CDR, so the VESCs were configured for brushed operation. I forgot about this and plugged them into the rover's drive system. Brushless DC motors don't like having two of their windings shorted together under maximum current conditions...
Aside from just being more carefull, it would be nice to have the USBServer read back the settings of each motor and print an error message if they are improperly configured. It could then write the proper configuration if needed. There are VESC commands for this, so it actually isn't that difficult to do as the trickiest implementation details are already there.
We could also run the requestSubscription method in a new threads to get the USBServer starting sooner.
The text was updated successfully, but these errors were encountered: