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
a33bce0d26
Device IDs: List all sub-types of the MPU6K
2017-01-29 16:24:47 +01:00
3f9d79c768
Update GPS
2017-01-29 01:19:48 +01:00
8fbf5cbdaf
astyle src/drivers/device
2017-01-29 01:18:32 +01:00
adbe38e86b
astyle src/drivers/stm32
2017-01-29 01:18:32 +01:00
1261f985d8
astyle src/drivers/bmi160
2017-01-29 01:18:32 +01:00
fc4831d625
astyle src/drivers/mkblctrl
2017-01-29 01:18:32 +01:00
f0cde91220
astyle src/drivers/vmount
2017-01-29 01:18:32 +01:00
e43a8013dd
astyle src/drivers/mpu9250
2017-01-29 01:18:32 +01:00
52c4479e0f
astyle src/drivers/camera_trigger
2017-01-29 01:18:32 +01:00
30587e5669
astyle src/drivers/gps
2017-01-29 01:18:32 +01:00
32da3381f7
astyle src/drivers/bootloaders
2017-01-29 01:18:32 +01:00
8ab79a2c90
astyle src/drivers/test_ppm
2017-01-29 01:18:32 +01:00
ac06d665a3
astyle src/drivers/boards
2017-01-29 01:18:32 +01:00
e63c8ab2a2
astyle src/drivers/ardrone_interface
2017-01-29 01:18:32 +01:00
264589b2cc
Fix motor range
2017-01-28 15:25:00 +01:00
41ff46b557
tap_esc: fixed offset to really keep the range 1200-1900
...
even if the input to the driver is too low or too high.
This prevents motor stalling.
NaN or Inf still stop the motor.
2017-01-28 15:24:45 +01:00
f604b71838
tap-v1 using board common mcu version api
2017-01-26 08:39:12 +01:00
0088d17f4c
px4nucleoF767ZI-v1 using board common mcu version api
2017-01-26 08:39:12 +01:00
59d95cd77b
px4fmu-v5 using board common mcu version api
2017-01-26 08:39:12 +01:00
3dc205f28a
px4fmu-v4pro using board common mcu version api
2017-01-26 08:39:12 +01:00
cd1148f146
px4fmu-v4 using board common mcu version api
2017-01-26 08:39:12 +01:00
Lorenz Meier