aboutsummaryrefslogtreecommitdiff
path: root/src/modules/uavcan/actuators
Commit message (Collapse)AuthorAgeFilesLines
* Removing extra UAVCAN perfcountersPavel Kirienko2015-01-212-8/+0
|
* Revert "Intrusive changes made for UAVCAN profiling. Will be reverted in the ↵Pavel Kirienko2015-01-211-5/+5
| | | | | | next commit (this one is needed to keep the changes in history)" This reverts commit 4c301d9dcf180e39186fa6753c7a3d3215b3cfa7.
* Intrusive changes made for UAVCAN profiling. Will be reverted in the next ↵Pavel Kirienko2015-01-211-5/+5
| | | | commit (this one is needed to keep the changes in history)
* UavcanEscController broadcasting percounterPavel Kirienko2015-01-212-0/+15
|
* uavcan: prevent crash in ESC driverAndrew Tridgell2014-11-261-1/+3
| | | | | | passing in more than 8 actuators would crash the ESC driver. We need to check again the array size of the _esc_status.esc, which is CONNECTED_ESC_MAX
* uavcan: don't force motors to keep spinning at zero throttleAndrew Tridgell2014-11-261-4/+9
| | | | | | | | | | Forcing motors to keep spinning when armed should be a policy decision up at the vehicle type level, not hard coded down in the ESC driver. It isn't appropriate for fixed wing or ground vehicles for example. We could add an ioctl to enable "spin when armed" if just setting a small value in the vehicle code is inconvenient
* code style, warningsHolger Steinhaus2014-11-121-6/+7
|
* UAVCAN: implemented motor testingHolger Steinhaus2014-11-031-1/+0
|
* UAVCAN: allow to arm single ESCsHolger Steinhaus2014-11-032-6/+29
|
* ESC status - supporting negative RPMPavel Kirienko2014-10-151-1/+1
|
* Publishing esc_setpoint_raw from the UAVCAN driverPavel Kirienko2014-10-131-0/+2
|
* Update ORB topic 'esc_status'Pavel Kirienko2014-10-131-8/+6
|
* ESC status feedbackPavel Kirienko2014-10-122-11/+33
|
* ESC scaling fixPavel Kirienko2014-10-122-10/+7
|
* UAVCAN: Refactored and generalized sensor bridge supportPavel Kirienko2014-08-222-0/+245