10dcb90d52
Commander: Store last manual stick setpoints only when actually in manual control mode
2017-03-13 21:08:17 +01:00
1a3317ebab
Commander: Do not abort low battery handling due to stick motion.
2017-03-13 08:42:51 +01:00
706464d2eb
Land detector: Fix param meta data
2017-03-12 14:42:19 +01:00
e4c012289f
Logger: Sync setpoints and states to same rates
2017-03-12 11:10:19 +01:00
f7e4d8453d
Logger: Drop position_setpoint_triplet to 5 Hz since its not required at such a high rate in analysis
2017-03-12 11:06:40 +01:00
30841ee6bf
send_event: separate initialization and wait until started for 'send_event start_listening'
2017-03-12 00:08:35 +01:00
1177ec91e5
temperatoru_calibration: reformat comments to use doxygen style
2017-03-12 00:08:35 +01:00
7cb291aa62
temperature_calibration: use a define for error code -110
2017-03-12 00:08:35 +01:00
38156d862f
temperature_calibration: add led indication
...
- starts with yellow blinking
- turns led to solid according to progress
- blink red on error, green on success
2017-03-12 00:08:35 +01:00
95e8e26ae0
commander: use led_control uorb topic
2017-03-12 00:08:35 +01:00
b0439836f6
refactor drv_led.h: rename to drv_board_led.h
...
This makes it clear that it's used to control the board LED's, not external
LED's.
2017-03-12 00:08:35 +01:00
404719953c
commander: fix abs bug / trigger POSCTL both ways
...
The check if stick were touched was only working in one direction (per
axis) because fabsf was used incorrectly.
However, this check is still only a differential check triggered by
fast movement and does not trigger if someone slowly moves a stick to
the side. Also, the sensitivity depends on the rate of the commander
loop and/or the RC update loop. The correct solution would be a proper
filtering and trigger for movement.
2017-03-11 22:41:23 +01:00
0611677ee2
segway move to examples
2017-03-11 11:40:14 +01:00
89ff9f1fe3
cmake fmu-v3 fix and enable more examples
...
- sync posix_sitl_default and px4fmu-v4pro/v5 with fmu-v3
- fixes #6667
2017-03-11 11:40:14 +01:00
4811ab6b13
logger: reduce rate of some topics
...
In SITL, logging rate reduces from 70kB/s to 45kB/s.
2017-03-11 10:30:38 +01:00
e2aae04c95
modules: dataman: Add a ram_flash backend
...
This backend will keep all updated data in RAM and
persist the data between reboots using flash memory.
Using only flash memory would result in a slow backend that
would decrease the lifetime of the flash memory, using both
we can reduce the several cycles of erase & write into flash
and keep the performance of the backend almost as fast
as the RAM only backend.
Note: Do not use this backend on a sector from the same flash memory
bank as the memory bank that STM32 read instructions or it can block
the CPU from fetching instructions from flash during the erase and
write operations and cause your drone crash.
2017-03-10 11:31:07 +01:00
75e7cfcbe8
modules: flashparams: Change size to uint32_t
...
So flash sector of 64Kbyes and 128Kbytes can also be used.
2017-03-10 11:31:07 +01:00
a2670bdbc8
modules: dataman: Move backend specific out of main routines
2017-03-10 11:31:07 +01:00
66d9d56525
modules: dataman: Share memory between backends
...
Also having just a boolean to track if backend is running.
2017-03-10 11:31:07 +01:00
cfcc75d444
mavlink shell: check if there's enough free buffer to send the mavlink message
...
if there is not, the process on the other end of the pipe will just block.
This improves reliability over slow links.
2017-03-10 11:29:09 +01:00
b1e27f4395
simulator: handle ctrl-c during startup correctly
...
This makes sure the px4 process does not hang when Ctrl-C is pressed
during startup.
2017-03-10 11:28:41 +01:00
9597e708df
sensors: remove sensors_init
...
The initialization code is redundant and incomplete (only the first sensor
is done). I verified that all drivers already set this on startup.
For the mags, they all set their maximum supported update rate.
For the baro, the call can silently fail, as for example the MS5611 which
does not support 150Hz update. But it also sets the maximum in
initialization.
Tested on Pixhawk & pixracer.
2017-03-10 11:28:41 +01:00
32995a5bc1
state_machine_helper: remove unneeded code to disable sensor publication
...
In HIL mode we do not start the sensors anymore, so this is not needed.
Also it did not work (I did not try to find the reason, just noticed the
sensors kept publishing in HIL mode)
2017-03-10 09:00:24 +01:00
af1984ac07
sensors: do not warn about baro in HIL mode
2017-03-10 09:00:24 +01:00
bc91005e7a
voted_sensors_update: increase accel & gyro timeout in HIL mode
2017-03-10 09:00:24 +01:00
0c926106f1
param_shmem.c: comment out locking on Snappy
...
The param locking doesn't seem to be working on Snapdragon, so let's
just comment it out again.
2017-03-08 15:44:31 +01:00
24819ce7b1
commander: no datalink failsafe on ground
...
On SITL startup we got a datalink lost failsafe message whenever home
was initialized. The reason that in standalone SITL, there is usually no
datalink connected. However, on ground, we shouldn't really failsafe,
therefore it makes sense not to enter the state in the first place.
2017-03-08 05:33:32 +08:00
c715228b8f
LandDetector: save & initialize total flight time
2017-03-08 04:19:22 +08:00
d67b6efda3
PixHawk Pro: Update mag IDs to have external higher priority
2017-03-07 23:43:28 +08:00
daf668e687
Fixed wing land detector: Fix RTL logic with a temporary altitude limit workaround
2017-03-07 15:48:23 +08:00
e63ee9d8bd
fw_att wheel controller enable param (default off)
2017-03-05 11:41:14 +08:00
ca05e64a9f
replay: update & add some comments
2017-03-04 22:47:54 +08:00
eaa9e6a019
ekf2: set att.timestamp to now in replay mode before ekf is initialized
...
logger will always log this topic, and a 0 timestamp will look worse in
FlightPlot. This will show a period of 0 attitude instead before ekf
is initialized.
2017-03-04 22:47:54 +08:00
01541bb10d
logger: switch from ekf2_replay to ekf2_timestamps topic, enable by default
2017-03-04 22:47:54 +08:00
1d48d7e053
ekf2 replay: add statistics output when replay finished
...
The error counter is an indicator that the logger missed samples or dropped
due to a too small write buffer.
2017-03-04 22:47:54 +08:00
2a11a2bc0b
ekf2 replay: switch from ekf2_replay to ekf2_timestamps topic
2017-03-04 22:47:54 +08:00
aabdc4125b
ekf2: publish ekf2_timestamps topic
2017-03-04 22:47:54 +08:00
473192aa81
replay: some API refactoring & extensions
...
in preparation to the updated ekf2 replay
2017-03-04 22:47:54 +08:00
ba89839f65
replay: make sure ReplayEkf2::handleTopicUpdate is protected, not private
2017-03-04 22:47:54 +08:00
63203625bc
replay: add ekf2 replay method (can be selected with 'export replay_mode=ekf2')
2017-03-04 22:47:54 +08:00
e251c64c5f
refactor replay: add some overrideable methods
2017-03-04 22:47:54 +08:00
df8c1a1489
logger: log ekf2_replay topic if EKF2_REC_RPL is set
2017-03-04 22:47:54 +08:00
9d54f62d37
replay: check if topic timestamp is smaller than logging start
...
This could happen and then the sleep duration would wrap and be huge.
2017-03-04 22:47:54 +08:00
1d5f51e6a4
replay: don't add subscription if formats don't match
2017-03-04 22:47:54 +08:00
4eea89bb42
refactor replay: move topic publication into separate method
2017-03-04 22:47:54 +08:00
45ffb190e3
logger: add -p <topic> option to poll on a topic instead of running at fixed rate
...
this will be needed for fast replay. In addition, this option disables
the orb interval.
It can be removed again once we have time simulation.
2017-03-04 22:47:54 +08:00
2220c3a60d
ekf2: use sensors timestamp for published topics when in replay mode
...
when doing fast replay, hrt_absolute_time() will not match the replayed time
thus we just use the same timestamp as the input sensors.
2017-03-04 22:47:54 +08:00
018846fadf
ekf2_replay.msg: use timestamp instead of time_ref, remove unused time_usec_vel
2017-03-04 22:47:54 +08:00
aa56822f9d
ekf2_replay: fix double/float conversion compile warning
2017-03-04 22:47:54 +08:00
99beb03f83
ekf2_replay: switch to new vision topics
2017-03-04 22:47:54 +08:00
Lorenz Meier