fe85841a1d
commander: remove counter
...
The counter variable in system status wasn't used anywhere.
2016-04-11 18:01:47 +02:00
32c3135788
commander: move battery calculations to systemlib
...
The commander used to consume the battery_status topic and write the
contents after some calculations into the system state. Instead, the
calculations now happen in library calls in systemlib/battery.
This moves the battery fields out of the vehicle_status message into the
battery_status topic.
This brought quite some changes in all modules that need battery
information. The current state is compiling but untested.
2016-04-11 18:01:47 +02:00
699b08c9fd
commander: move battery warning
...
The battery warning is not consumed anywhere, therefore scrap it from
the vehicle_status message.
2016-04-11 18:01:47 +02:00
74072dbe74
vehicle_status.msg: delete unused mavlink stuff
...
The MAV_TYPE enum was not in sync with the mavlink specs anymore. It
makes therefore sense to remove the duplication and include the correct
mavlink header file where it is needed.
Also, error counts which are not populated, can be scrapped.
2016-04-11 18:01:47 +02:00
5f3a23a253
commander: remove circuit breakers from status msg
...
Since the circuit breaker bools are not actually used anywhere else than
in the commander, it is safe to remove them and replace them with local
bools.
2016-04-11 18:01:47 +02:00
8b876e6497
MAVLink command feedback: Do only report command status and not additional string
2016-04-10 11:15:18 -07:00
91d4e129f4
Change to normal cal message
...
This way QGC can respond to it and show good ui
2016-04-10 10:58:37 -07:00
ad3ca2a9d2
Commander: Indicate low battery
2016-04-10 10:57:38 -07:00
e3d6bad3fe
Revert "report sensor init failure"
...
This reverts commit 407f467b456a393a891a936c79cc90e64e52fd45.
2016-04-10 10:37:03 -07:00
b66967a8a5
Revert "add low battery warning and comment out the "resolved" messages"
...
This reverts commit 221e259d01b32f23d14270af78d0996b728bf9d1.
2016-04-10 10:36:48 -07:00
34a9449df9
Include cal status data for mag
2016-04-09 18:00:38 -07:00
224aaeddfe
Harden calibration experience on master
2016-04-09 13:44:53 -07:00
d9b32221e7
Commander: Reduce mag output
2016-04-09 11:53:44 -07:00
275fe8ee2d
Play safe with calibration done messages
2016-04-09 11:50:50 -07:00
9fdbaa5a22
Mag cal
2016-04-06 14:30:51 -07:00
6d24e33819
Commander: Space out mag feedback further
2016-04-06 14:23:49 -07:00
43e0186eb3
Commander: Space out MAVLink log messages more
2016-04-05 21:33:40 -07:00
817c0eafbc
add low battery warning and comment out the "resolved" messages
2016-04-05 19:13:49 -07:00
b4520f538e
report sensor init failure
2016-04-05 19:13:49 -07:00
8707cfe9f2
commander: use macro with wait in all calibrations
2016-04-05 15:36:03 -07:00
f583f51027
commander: add macros for log messages and wait
...
As a current workaround we need to wait some time after publishing a
mavlink log message in order for it to arrive in QGC.
2016-04-05 15:36:02 -07:00
7352dc6f2e
commander: workaround to wait 1s before param save
...
Without this wait, we end up saving the old parameters on Snapdragon.
2016-04-05 13:02:53 +02:00
94aaf0d298
increase sleep time in accel calibration routine to make accel calibration work on snapdragon
2016-04-04 11:17:26 +02:00
f4f1f5f027
commander: raise stack of low prio thread
...
The accel calibration sometimes lead to a crash. Raising the stack size
resolved the issue.
2016-04-01 15:12:08 +02:00
bd580e09bf
supports MindPXv2 borad which is a product from AirMind.
2016-03-30 19:45:39 +02:00
9a5aa4f112
commander: pass PreflightCheck on Snapdragon
...
The tests don't work properly on Snapdragon yet, so just report happy
for now. Otherwise users get messages such as "No Gyro found" which is
wrong.
2016-03-30 10:00:22 +02:00
3981f06d42
Reject arming timeout
2016-03-29 22:42:57 +02:00
f718c25dbe
commander: remove QURT workaround
...
Timestamps didn't exist when commander was run on the Linux side.
However, commander is now always run on the QURT side, so the hack is no
longer needed.
2016-03-27 12:40:10 +02:00
38c40d5601
fixing var change after rebase, setting min mission takeoff altitude to 10m for safety
2016-03-27 12:10:57 +02:00
dfc2d9b5e0
more clean up
2016-03-27 12:10:57 +02:00
bbc8eaefd7
Adding new follow target navigation and main states. New follow target
...
topic added. New follow fsm added to the navigator
2016-03-27 12:10:57 +02:00
26bb2fd22f
capitalize param values
2016-03-25 20:38:08 -04:00
6888545037
remove @unit enum
2016-03-25 20:33:25 -04:00
bee39d93d9
battery param add units
2016-03-25 20:27:48 -04:00
70a68def83
params correct boolean tag
2016-03-25 20:25:17 -04:00
13866400fa
commander: workaround to get calibration status
...
If mavlink_log calls follow close after each other a later one will
replace the previous one. Therefore do a quick usleep to get the
calibration status out the door.
2016-03-24 13:10:02 +01:00
1fc9b99307
commander: some rebase fixes
2016-03-24 13:10:02 +01:00
bba0d0384d
drivers/modules: changes after mavlink_log change
...
The mavlink_log API changes lead to changes in all drivers/modules using
it.
2016-03-24 13:10:02 +01:00
790fa7667c
commander: cherry-pick fixes
2016-03-24 13:08:31 +01:00
88a812618c
commander: fix the calibration for NuttX.
...
This fixes some regressions on the calibration using NuttX, especially
considering the PRIME param and the device ids.
2016-03-24 13:08:31 +01:00
d0e9ec0c67
commander: get PRIME parameter back
...
The PRIME param got lost on the way of the refactoring.
2016-03-24 13:08:31 +01:00
e949d6d18a
commander: get PRIME parameter back
...
The PRIME param got lost on the way of the refactoring.
2016-03-24 13:08:31 +01:00
10ce1c19a2
mag_calibration: small fix for non QURT
2016-03-24 13:08:31 +01:00
1b5210ca13
sensors/calibration: use params in DF wrappers
...
Instead of using a uORB topic with the calibration values published in
sensors and consumed by the DriverFramework driver wrappers, let's just
use the the params directly. This is quite a rough change and needs
definitely some cleanup and refactoring.
2016-03-24 13:08:31 +01:00
b9cc0b74e2
drivers: re-use calibration topic
...
E.g. instead of defining a gyro_scale struct in drv_gyro.h, use the
gyro_calibration message.
2016-03-24 13:08:30 +01:00
98e407696e
commander: whitespace only
...
Trailing whitespace all over.
2016-03-24 13:08:30 +01:00
7a9427bc34
param remove empty @unit
2016-03-14 09:12:34 +01:00
13932103ba
commander param @unit
2016-03-14 09:10:29 +01:00
d81d0c21ed
More debug output in commander shell
2016-03-13 19:49:18 +01:00
36a8f3f45a
Commander: Ignore speed commands
2016-03-13 18:09:04 +01:00
Julian Oes