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
When testing the drivetrain, we can to be looking at the current reading over time (how much current the odrives are supplying to the motors), monitoring them (maybe graphically, just to know how much current the odrives are supplying to the motor).
Maybe this can be made as a python script that is graphing current values over time using the odrive python interface.
We should also think about how that would be used when we are running the full drivetrain on the real ground. We can't assume that a laptop will be hooked up via usb to an odrive.
The text was updated successfully, but these errors were encountered:
When testing the drivetrain, we can to be looking at the current reading over time (how much current the odrives are supplying to the motors), monitoring them (maybe graphically, just to know how much current the odrives are supplying to the motor).
It definitely should be possible based on the odrive native commands: https://discourse.odriverobotics.com/t/reading-current-and-voltage/1068/2.
Maybe this can be made as a python script that is graphing current values over time using the odrive python interface.
We should also think about how that would be used when we are running the full drivetrain on the real ground. We can't assume that a laptop will be hooked up via usb to an odrive.
The text was updated successfully, but these errors were encountered: