zr-v4

Commit Graph

Author	SHA1	Message	Date
Andrew Tridgell	f662cf55e5	AP_UAVCAN: use WITH_SEMAPHORE() and removed usage of hal.util->new_semaphore()	6 years ago
Siddharth Purohit	0125b2cdd2	AP_UAVCAN: remove UAVCAN sensors related code	7 years ago
Siddharth Purohit	f01cc254d3	AP_UAVCAN: add Callback API to link UAVCAN backend callbacks	7 years ago
Francisco Ferreira	3cb8421aa6	AP_UAVCAN: reorganize header and code Also a bit more cleanup	7 years ago
Francisco Ferreira	ee8e2923ae	AP_UAVCAN: cleanup code	7 years ago
Francisco Ferreira	8c382b6904	AP_UAVCAN: adapt to new CANProtocol interface This includes creating own thread Also adapts example	7 years ago
Andrew Tridgell	92cda24659	AP_UAVCAN: efficiency improvements this allows us to support 800Hz main loop rate with UAVCAN ESCs on copter	7 years ago
Andrew Tridgell	b8ae43c30b	AP_UAVCAN: added a servo rate limit parameter this allows for servos at 50Hz while keeping ESCs at higher rates	7 years ago
Tom Pittenger	4c51edfaca	AP_UAVCAN: move UAVCAN code from SRV to UAVCAN files	7 years ago
Eugene Shamaev	1a888c16f4	AP_UAVCAN: Change for servo and ESC interface from RCOutput to SRV_Channels	7 years ago
Lucas De Marchi	1dd14a8aed	AP_UAVCAN: add can driver getter	7 years ago
Andrew Tridgell	f7751ec44a	AP_UAVCAN: reverted UAVCAN PR 7827	7 years ago
Tom Pittenger	1ace5ac534	AP_UAVCAN: changed att and fix send timers to be 32bit	7 years ago
$DOMINATOR\Eugene$ DOMINATOR\Eugene	c49d4aef50	AP_UAVCAN: position and attitude broadcast	7 years ago
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.	7 years ago
$DOMINATOR\Eugene$ DOMINATOR\Eugene	844ed611c6	AP_UAVCAN: UAVCAN battery information added	7 years ago
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.	7 years ago
Tom Pittenger	52589f3c22	AP_UAVCAN: refactor RC Out functions - non-functional change	7 years ago
Eugene Shamaev	c6df13c795	AP_UAVCAN: changes to servo bitmasks to support multiple instances, baro, compass, gps changes for several CAN interfaces	8 years ago
Eugene Shamaev	68a8d8615d	AP_UAVCAN: library for support of UAVCAN protocol	8 years ago

20 Commits (7e8b6709aee1d9155b64ee3c4b766277d9dc1ba5)