- set measurement of first sample to -1 to indicated that the data
is not valid
- give an estimate of the sensor variance based on the sensor resolution
and experiments
Signed-off-by: Roman <bapstroman@gmail.com>
Move RC and DL failsafe actions handling from navigator to commander (credits to @AndreasAntener)
Separate manual kill switch handling via manual_lockdown to prevent override and release of software lockdown by RC switch
Other changes:
Add failsafe tune
Fix LED blinking for Pixracer
Return back support for rc inputs in simulator but now it is configurable via cmake
- Other channels are irrelevant since they aren't physically
connected. Avoid the I2C transaction to get invalid data
- Port the driver to use only one address, as it should be
- Minor changes here and there
- Add test() method to read the latest value - helpful during
debugging.
Measure the battery voltage of Aero RTF kit will be done by FPGA
and read by AeroFC using I2C bus.
The protocol is a little bit odd, it have different I2C slave
address for each "register", in future the FPGA RTL will
have a protocol more similar to other I2C sensors.
Also Aero RTF don't have a ADC line to measure current consumption.
This allows a ICM20xxxx with an unkown product ID to be used
with the mpu6000 driver.
This change will issues a warning for any part with an unknown product ID.
For mpu6000 parts (-T 6000 or not specified) it will then exit.
For any ICM20xxxx part with an unknown product ID it will accept the ID
and run with it.
N.B. This fix expecte the value in the product ID register to be
a per chip constant. (Not changing during operations)
boards define BOARD_NAME, so board_name() is not necessary. HW_ARCH was
just a wrapper around board_name().
This patch simplifies to having only one common method px4_board_name().
This is the fixes https://github.com/PX4/Firmware/issues/5710
by adding 2 concepts.
1) Allowing a board to define BOARD_HAS_SHARED_PWM_TIMERS
in this case the io_timeris will be initalized as the
led_pwm_timers - there is an assumptionm that the
number of io_timers == the number of led_pwm timers
2) Allowing a board to define BOARD_LED_PWM_RATE
To set an alternate frequency
Future expansion will require:
1) The ability to have a config with both the I2C RGB LED and
PWM RGB LED drivers loaded.
2) The higher level driver to create multiple instances of the
/dev/rgbld, to support internal and external User facing
RGB LED as supported in FMUv5
