17 Commits

Author	SHA1	Message	Date
Francisco Ferreira	3cb8421aa6	AP_UAVCAN: reorganize header and code ... Also a bit more cleanup	2018-08-12 13:35:04 +01:00
Francisco Ferreira	ee8e2923ae	AP_UAVCAN: cleanup code	2018-08-12 13:35:04 +01:00
Francisco Ferreira	8c382b6904	AP_UAVCAN: adapt to new CANProtocol interface ... This includes creating own thread Also adapts example	2018-08-12 13:35:03 +01:00
Andrew Tridgell	92cda24659	AP_UAVCAN: efficiency improvements ... this allows us to support 800Hz main loop rate with UAVCAN ESCs on copter	2018-05-25 13:53:17 +10:00
Andrew Tridgell	b8ae43c30b	AP_UAVCAN: added a servo rate limit parameter ... this allows for servos at 50Hz while keeping ESCs at higher rates	2018-05-25 13:53:17 +10:00
Tom Pittenger	4c51edfaca	AP_UAVCAN: move UAVCAN code from SRV to UAVCAN files	2018-05-25 13:53:17 +10:00
Eugene Shamaev	1a888c16f4	AP_UAVCAN: Change for servo and ESC interface from RCOutput to SRV_Channels	2018-05-25 13:53:17 +10:00
Lucas De Marchi	1dd14a8aed	AP_UAVCAN: add can driver getter	2018-03-10 21:07:47 -08:00
Andrew Tridgell	f7751ec44a	AP_UAVCAN: reverted UAVCAN PR 7827	2018-03-05 14:16:54 +11:00
Tom Pittenger	1ace5ac534	AP_UAVCAN: changed att and fix send timers to be 32bit	2018-03-03 12:59:14 +12:00
DOMINATOR\Eugene	c49d4aef50	AP_UAVCAN: position and attitude broadcast	2018-03-03 12:59:14 +12:00
Nikita Tomilov	a1017fb815	AP_UAVCAN: utilizing equipment.indication.LightsCommand ... This can be used to command multiple devices on the UAVCAN bus to update their LEDs. This will come in handy for status outputs etc. This utilizes equipment.indication.LightsCommand message. This message is not so important and therefore we limit publishing it to avoid bus overflow. The priority of the message is also low.	2018-03-03 10:40:26 +12:00
DOMINATOR\Eugene	844ed611c6	AP_UAVCAN: UAVCAN battery information added	2018-03-02 11:48:00 +12:00
Nikita Tomilov	2a34593ed3	AP_UAVCAN: Magnetic: allow more than one compass on one node ... To do so, we make use of UAVCAN message MagneticFieldStrength2, which has a field describing the sensor_id of the node which measurements were sent, and if a node sends this message we register multiple AP_Compass_UAVCAN backends for this node. The routing of the messages between those backends is also implemented here.	2018-02-10 23:48:23 -08:00
Tom Pittenger	52589f3c22	AP_UAVCAN: refactor RC Out functions ... - non-functional change	2018-02-08 16:57:17 -08:00
Eugene Shamaev	c6df13c795	AP_UAVCAN: changes to servo bitmasks to support multiple instances, baro, compass, gps changes for several CAN interfaces	2017-07-03 11:44:32 +01:00
Eugene Shamaev	68a8d8615d	AP_UAVCAN: library for support of UAVCAN protocol	2017-04-10 22:38:12 +01:00