diff options
author | Andrew Tridgell <tridge@samba.org> | 2014-11-06 10:32:21 +1100 |
---|---|---|
committer | Lorenz Meier <lm@inf.ethz.ch> | 2014-11-16 21:01:00 +0100 |
commit | 6406e235d6f5cb37a914442036111f616b4b3839 (patch) | |
tree | 143f622d709d3e5cd2639659c6649222144278b2 /src/drivers | |
parent | 88bae21ce53fc6acadaae4c8271f3d0fce18a721 (diff) | |
download | px4-firmware-6406e235d6f5cb37a914442036111f616b4b3839.tar.gz px4-firmware-6406e235d6f5cb37a914442036111f616b4b3839.tar.bz2 px4-firmware-6406e235d6f5cb37a914442036111f616b4b3839.zip |
px4io: publish pwm values when STATUS_FLAGS_FMU_OK is not set
this allows testing of FMU failure behaviour in px4io by monitoring
the reported PWM output when the vehicle code stops sending
updates. Otherwise testing needs to be done with "px4io status" which
is very tedious.
With this change a GCS can monitor the PWM outputs from the failsafe
mixer using normal mavlink messages
Diffstat (limited to 'src/drivers')
-rw-r--r-- | src/drivers/px4io/px4io.cpp | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/src/drivers/px4io/px4io.cpp b/src/drivers/px4io/px4io.cpp index dc33f7657..6a313b322 100644 --- a/src/drivers/px4io/px4io.cpp +++ b/src/drivers/px4io/px4io.cpp @@ -1657,10 +1657,6 @@ PX4IO::io_publish_raw_rc() int PX4IO::io_publish_pwm_outputs() { - /* if no FMU comms(!) just don't publish */ - if (!(_status & PX4IO_P_STATUS_FLAGS_FMU_OK)) - return OK; - /* data we are going to fetch */ actuator_outputs_s outputs; outputs.timestamp = hrt_absolute_time(); |