Mirrors_Framework/ODrive
1
0
Fork 0
mirror of https://github.com/odriverobotics/ODrive.git synced 2026-09-20 22:55:00 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge pull request #297 from jaredairbusaerial/patch-4

Browse Source 
Added safety notice for PWM input in interfaces doc
This commit is contained in:
Oskar Weigl
2019-01-13 19:29:17 -08:00
committed by GitHub
parent 5abe4d795a 4c00ffc321
commit 9bf4c7e34a
1 changed files with 2 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/interfaces.md
+2
View File
@@ -127,6 +127,8 @@ As an example, we'll configure GPIO4 to control the angle of axis 0. We want the
```
5. With the ODrive powered off, connect the RC receiver ground to the ODrive's GND and one of the RC receiver signals to GPIO4. You may try to power the receiver from the ODrive's 5V supply if it doesn't draw too much power. Power up the the RC transmitter. You should now be able to control axis 0 from one of the RC sticks.
Be sure to setup the Failsafe feature on your RC Receiver so that if connection is lost between the remote and the receiver, the receiver outputs 0 for the velocity setpoint of both axes (or whatever is safest for your configuration). Also note that if the receiver turns off (loss of power, etc) or if the signal from the receiver to the ODrive is lost (wire comes unplugged, etc), the ODrive will continue the last commanded velocity setpoint. There is currently no timeout function in the ODrive for PWM inputs.
## Ports
Note: when you use an existing library you don't have to deal with the specifics described in this section.