19f2a7bff0
Only publish battery if we can measure something, initialize battery topic in commander correctly
2016-04-23 14:29:25 +02:00
1b7319d2e5
adding the position control mode change for accel control back to the commander
2016-04-22 10:31:52 +02:00
95faba391a
accel control in pos controller
2016-04-22 10:31:52 +02:00
ce810542e2
simple NED acceleration control interface
2016-04-22 10:31:52 +02:00
851b5d02a9
Fix potential string overflow corner case
2016-04-22 09:36:07 +02:00
4077616264
Significantly reduce stack size needed for calibration in commander
2016-04-22 09:03:57 +02:00
37bd291446
fix regression which broke rattitude mode
2016-04-22 08:40:40 +02:00
8e5091703c
commander: no message due to LED/buzzer not found
...
The LED init and Buzzer init messages were only annoying and not helpful
on Snapdragon and SITL. Therefore they are replaced with only developer
printfs.
2016-04-21 21:22:52 +02:00
835ee4d709
Commander: Better status feedback about power status
2016-04-21 10:36:14 +02:00
776c7f5d60
Updated commander to take free-fall into account
...
Added free-fall status in vehicle_status topic
2016-04-18 22:27:11 +02:00
0adb4d8e8c
Commander: Fix single channel mode switching
2016-04-18 18:29:07 +02:00
717c90eab4
enable commander hil option when hils mode
...
test for merge...
recover modification part
2016-04-18 11:10:02 +02:00
f164500580
Commander: optimize text for voice output
2016-04-17 19:06:00 +02:00
967e4dd127
Modified cmake to use STACK_MAX and STACK_MAIN
2016-04-14 13:36:36 -04:00
c9ac9c7dbd
commander: fixes after rebase
2016-04-11 18:01:49 +02:00
3c9f9540dc
commander: add failsafe flag back in
2016-04-11 18:01:49 +02:00
974223bdd1
commander: pass battery status to preflight check
...
A low battery check was recently added to the preflight check, therefore
we need to pass on the information about the battery.
2016-04-11 18:01:49 +02:00
e91f587438
commander; various compile fixes after rebase
2016-04-11 18:01:49 +02:00
be2fe78c82
commander: publish internal state
2016-04-11 18:01:48 +02:00
2cd05dea4d
commander: try different mavlink include
2016-04-11 18:01:48 +02:00
5ca5af5fcd
commander: take main_state out of vehicle_status
...
This state is only commander internal. Therefore it doesn't need to be
in vehicle_status. Instead it is now in the commander_state message.
2016-04-11 18:01:48 +02:00
1ad0ee0fae
mc_att_control: don't use main state for RATTITUDE
...
Instead of the state use the boolean flags.
2016-04-11 18:01:48 +02:00
5c9713f05b
commander: try to get the travis include right
2016-04-11 18:01:48 +02:00
70cff975cc
commander: move some flags out of vehicle_status
...
All the removed flags were not used anywhere else than inside the
commander.
2016-04-11 18:01:48 +02:00
0988fef831
commander: forgot to close fd
2016-04-11 18:01:48 +02:00
23df992cc5
commander: moved offboard bools into status_flags
...
The offboard status bools were not used anywhere but in the commander.
Therefore they are now moved to the local status_flags topic.
2016-04-11 18:01:48 +02:00
1f44fb1efd
commander: internalize system status bools
...
Most condition bools in the commander are not used anywhere but in the
commander. It therefore makes sense to move them to a different internal
struct and remove them from the vehicle_status message.
Also, the land_detected should be used by all the modules instead of
getting it through the commander and system_status.
2016-04-11 18:01:47 +02:00
141b984d5b
commander: take previous main state out of status
2016-04-11 18:01:47 +02:00
181eb49da8
commander: remove calibration_enabled
...
This flag is not used anywhere, it therefore doesn't need to be in
vehicle_status.
2016-04-11 18:01:47 +02:00
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
Lorenz Meier