Tree: 094e284737

AP_Periph-1.3

Copter-4.2

Copter-4.2-BW

apm_2208

apm_2208-rover

apm_2208-rover-debug

c421

copter407

gps-1.3.1

main

master

master_rangefinder

mission-4.1.18

periph-1.3.1

release-4.2.3

rover_4.3

zr-sdk-4.3.1

zr-v5.0

zr-v5.1

zr/Rover-4.3

zr/main-4.3

zr_rover4.2

数字绿土/zr-v5.0

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '094e284737'

${ noResults }

Commit Graph

4 Commits (094e284737c42bf896f0fdfe162375d257ea72d1)

Author	SHA1	Message	Date
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