f09b60ad9e
lis3mdl : several fixes and enhancements
2017-02-12 13:52:41 +01:00
089e50c574
px4fmu-v4pro : board configuration
2017-02-12 13:52:41 +01:00
62ea471ae7
ms5611: support MS5611/MS5607 autodetection
...
From their registers it's not possible to differentiate MS5611 from
MS5607. Here we use a little heuristic that people won't likely be
flying (or starting to fly) on very high altitude, greater than 5300m.
Even on these altitudes the error would be much lower using the MS5611
calculations for MS5607 than it is on MSL.
2017-02-09 21:30:19 +01:00
08f0524b58
camera_trigger: remove unused fields _gpio_fd and _p_pin
2017-02-07 13:36:16 +01:00
507e3b0263
camera_trigger: add TRIG_INTERFACE=3 for Mavlink forwarding
2017-02-07 13:36:16 +01:00
212502b2b1
camera_trigger: make sure it builds for SITL & add to SITL cmake
2017-02-07 13:36:16 +01:00
882146785c
camera_trigger: rename info command to status
...
to be consistent with the rest of the system
2017-02-07 13:36:16 +01:00
d6c54e4240
camera_trigger: remove params from build
2017-02-07 13:36:16 +01:00
602279ad56
zubaxgnss-v1 bootloader uses mfguid for hw_version unique_id
2017-02-04 22:27:04 +01:00
29888659f2
s2740vc-v1 bootloader uses mfguid for hw_version unique_id
2017-02-04 22:27:04 +01:00
c52a8544c1
px4flow-v2 bootloader uses mfguid for hw_version unique_id
2017-02-04 22:27:04 +01:00
050b909b20
px4esc-v1 bootloader uses mfguid for hw_version unique_id
2017-02-04 22:27:04 +01:00
23ecb78552
px4cannode-v1 bootloader uses mfguid for hw_version unique_id
2017-02-04 22:27:04 +01:00
278d6bb717
esc35-v1 bootloader uses mfguid for hw_version unique_id
2017-02-04 22:27:04 +01:00
7600aa51f7
Remove fmu id command as it is redundant to ver uid
...
This command was redudnat to "fmu uid|all" However it
printed the leading zeros.
2017-02-04 22:27:04 +01:00
bc8b117e85
common board idenity cleanup and add mfguid to api
...
Remove the notion of legacy from the api. The board level code
will perform the traslation to lecacy format on the STM32.
new targets will not need to do this as there is no case
where the serial number were used by mfg for tracking.
Extend board common api to get mfguid and mfguid formatted
This adds an api that return the MFGUID as an array of bytes
or a string.
The data is returned with the MSD at index 0 and the LSD at
index PX4_CPU_MFGUID_BYTE_LENGTH-1.
Removed all reodering defines from the api and hal
2017-02-04 22:27:04 +01:00
6bd29b24f6
POSIX: Avoid missing prototype warning on some POSIX platforms
2017-02-04 21:06:21 +01:00
82fa9a8d43
Update return type for power management call
2017-02-04 21:06:21 +01:00
4f1842c9c4
TAP v1 config: Add support for external power management calls
2017-02-04 21:06:21 +01:00
1ad03ed8ef
Common: Add support for power management (on / off) from the flight controller side
2017-02-04 21:06:21 +01:00
565a43dee0
Aero FC v1: Remove unused power management file
2017-02-04 21:06:21 +01:00
f7fa374656
Implement default board power control to allow software switch-off
2017-02-04 21:06:21 +01:00
384e3bb693
meas_airspeed status aspd_com_err
2017-02-04 08:47:37 +01:00
0d000173b5
l3gd20 selftest: don't check for 0 offset
...
If temperature compensation is enabled, the offset will be 0
2017-02-03 13:57:48 +01:00
345123bb04
clang-tidy readability-static-definition-in-anonymous-namespace
2017-02-01 22:15:50 -05:00
be5764db48
clang-tidy misc-suspicious-missing-comma
2017-02-01 22:15:50 -05:00
96e51f7c59
clang-tidy remove redundant
2017-02-01 22:15:50 -05:00
6631e72d6f
clang-tidy modernize-redundant-void-arg
2017-02-01 22:15:50 -05:00
e927f3e040
clang-tidy modernize-use-nullptr
2017-02-01 22:15:50 -05:00
253683af5f
drivers: Don't require driver level gyro offsets to be non-zero
2017-02-01 08:40:23 +01:00
c00c638b77
Remove IMU calibration parameter checks
2017-02-01 08:40:23 +01:00
f746141afe
mpu6000: add & check for the device_type on driver startup
...
Fixes the following case: a board that has several bus_options enabled,
and wants to start a specific device (eg mpu6000 -T 20608 start). In that
case the given device_type is never actually checked, and since the start
routine iterates over all bus_options, several can match, and thus start
multiple instances of the driver (note that the whoami check is performed
against the value provided with -T and thus the check will pass).
This happens on Pixracer (PX4_SPIDEV_MPU and PX4_SPIDEV_ICM_20608 are both
set).
2017-01-31 23:38:50 +01:00
7c47991504
px4fmu-v4 board config: use PX4_SPIDEV_ICM_20608 instead of PX4_SPIDEV_ICM_20602
...
This is what's used according to https://pixhawk.org/modules/pixracer .
2017-01-31 23:38:50 +01:00
d1372ddb67
Snapdragon RC driver: Move RC struct out of main loop to preserve channel values. Initialize raw rc count.
2017-01-30 08:28:59 +01:00
2c24900b9d
FMU: Initialize raw RC count
2017-01-30 08:27:49 +01:00
e7a0089340
9250: Fill device ID for mag correctly
2017-01-29 16:24:47 +01:00
a9a31bc745
MPU6K: Device ID should come from the main instance, not interface
2017-01-29 16:24:47 +01:00
be2c73e9c3
HMC driver: Device ID should come from the main instance, not the interface
2017-01-29 16:24:47 +01:00
a520c62d1a
Allow setting the device ID in device driver
2017-01-29 16:24:47 +01:00
d0d1a8e04f
MS5611: Add missing bus identifier
2017-01-29 16:24:47 +01:00
0ee68071fc
9250: Add missing bus identifier
2017-01-29 16:24:47 +01:00
af4e9b668b
MPU6K: Add missing bus identifier
2017-01-29 16:24:47 +01:00
40e5d25196
LPS25H: Add missing bus identifier
2017-01-29 16:24:47 +01:00
19d4c65a70
LIS: Add missing bus identifier
2017-01-29 16:24:47 +01:00
6c7a8b594e
HMC: Add missing bus identifier
2017-01-29 16:24:47 +01:00
f80a1df133
Sensor header: Add previously unknown device identifiers
2017-01-29 16:24:47 +01:00
33f6316d3c
Device: Also allow to read bus type
2017-01-29 16:24:47 +01:00
ec78830657
BMP280: Fix device ID setup
2017-01-29 16:24:47 +01:00
8f77d55b8c
BMA180: Fix device ID setup
2017-01-29 16:24:47 +01:00
e88bb4cc09
MPU6K: Correctly register sub-type, remove magic numbers.
...
Before this change the MPU6K driver would register only the MPU6K family, but not the sub-type, which prevented telling individual sensors apart. This is a breaking change because users will have to perform their accel and gyro calibration again. However, it is unavoidable since right now the different sensors can end up with the same ID and the wrong offsets can be applied to the wrong sensor.
2017-01-29 16:24:47 +01:00
klopezal