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
eb8bce4825
sdlog2: fix PARAM name truncation
...
if a parameter name was 16 characters long (which is valid), the last
character got truncated due to 0-terminated string.
This raises the param name to 64 chars, which is quite wasteful, but there
is no other length in between.
2017-03-04 18:27:25 +08:00
54c8e3b26b
commander: fix excessive orb_advertise calls for vehicle_status_flags
...
vehicle_status_flags_pub passed to publish_status_flags() was always null,
thus orb_advertise() was called each time.
Note that it did not produce a memory leak.
2017-03-04 17:44:47 +08:00
2bbe04c3d6
mavlink_receiver: don't publish sensor_combined for MAVLINK_MSG_ID_HIL_SENSOR
...
In hil mode, sensors is responsible for publishing this topic.
2017-03-04 05:59:10 +08:00
881f2d2d36
sensors: add 'sensors start -hil' parameter
...
This does the following if given:
- don't initialize the sensors (the sensor drivers are not started)
- publish sensor_combined even in hil mode
- do not apply or publish thermal corrections
2017-03-04 05:59:10 +08:00
3f6783fce7
mc_att_control: make sure to update the polling fd when the selected gyro changes
2017-03-04 05:59:10 +08:00
ec33607912
mc_att_control_main: make sure to initialize at least one gyro sensor
...
in HIL mode, gyros are published after mc_att_control started.
2017-03-04 05:59:10 +08:00
f5ae90a7cb
mavlink_main: add POSITION_TARGET_LOCAL_NED to mavlink stream
2017-03-03 07:23:02 +01:00
9ef87f1311
VTOL QuadChute Maximum roll and pitch angles ( #6665 )
2017-03-02 10:34:04 -05:00
e892a51afb
mc_pos_control: delta_t needs to be positive
2017-03-01 11:46:23 +01:00
2b90224075
land_detector: added parameter for manual position stick takeoff threshold
2017-02-28 13:05:33 +01:00
9c2dd48814
landdetector: m/s to m
2017-02-27 22:54:19 +01:00
7f54f891c1
land_detector: set max height to 100
2017-02-27 22:54:19 +01:00
6939583650
mc_pos_control: _run_altitude if close to max altitude
2017-02-27 22:54:19 +01:00
3d4e7819a0
landdetector: delete function update_alt_max
2017-02-27 22:54:19 +01:00
1774e01c00
rtl: keep rtl altitude below max altitude
...
land_detector: delete unused class enum
2017-02-27 22:54:19 +01:00
b887654d69
mc_pos_control: fix limit_altitude function
2017-02-27 22:54:19 +01:00
ca84cc7439
mc_pos_control: delete max altitude, which is not set by landdetector
2017-02-27 22:54:19 +01:00
a1982e0392
land_detector: battery level status to adjust maximum altitude possible
2017-02-27 22:54:19 +01:00
c8690fd072
mc_pos_control: limit altitude
...
mc_pos_control: delete spaces
mc_pos_control: cleanup and threshold for velocity control to altitude control when close to max altitude
2017-02-27 22:54:19 +01:00
5c524e15f8
Battery params: Enforce system reboot
2017-02-27 16:37:08 +01:00
3961c46d68
UAVCAN: Incorporate manual loackdown
...
This flag is triggered when the manual kill switch is activated. The motors
did not stop when the kill switch was engaged before adding this check.
2017-02-27 12:48:30 +01:00
16530e15db
Commander: Differentiate between emergency battery level and critical battery level
2017-02-27 09:03:20 +01:00
029c6de4a9
Battery estimator: Warn on dangerously low levels.
...
We need to differentiate between a level where the user should act and where we are about to fall out of the sky (emergency). This helps performing more suitable failsafe actions.
2017-02-27 09:03:20 +01:00
7710b64d27
Navigator: Re-initialize RTL every time it gets re-enabled
2017-02-26 13:26:52 +01:00
6ce5807240
mavlink: Send message to control onboard camera as broadcast
...
The target was it self.
2017-02-25 19:03:45 +01:00
fe4ea6dd63
VTOL mc_pos reset internal state during FW mode
2017-02-25 17:57:05 +01:00
1b2973f602
VTOL fw_att don't reset integrators during transition
2017-02-25 17:57:05 +01:00
8fd27fddcd
mc_pos_control: moved responsibility of the x,y stick deadzone to a mathematical function
...
to prevent a setpoint step when moving the stick over the border of the deadzone
and to enable very small inputs even from a control stick that needs a big deadzone
2017-02-25 11:05:53 +01:00
ad3d0391ab
Navigator: Only update params as they change
2017-02-25 11:04:52 +01:00
ecb2511a7b
add matrix copyTo
2017-02-25 11:04:02 +01:00
f43f3baa02
ATT_VIBE_THRESH param: move the definition of this param to sensors
...
since it's only used in sensors module (otherwise it could get pruned)
2017-02-25 11:02:15 +01:00
cfa84954ea
param_get: add null-pointer check
...
If param_find() returned PARAM_INVALID, and this was directly passed to
param_get(), param_get_value_ptr() returned null and we read garbage data
(or segfaulted on systems with virtual memory).
On px4fmu-v2, this happened for the param ATT_VIBE_THRESH in sensors.
Because of the recently added parameter scoping, this param got pruned, as
it's defined in attitude_estimator_q.
credits for finding this go to Jeyong Shin (jeyong).
2017-02-25 11:02:15 +01:00
3e88b2f2b1
Rate-limit navigator update rate
2017-02-24 08:52:10 +01:00
80e1064523
mavlink : fix legacy vision interface attitude timestamps
2017-02-24 08:51:05 +01:00
058bc97c83
commander preflight calibration: accept param6 == 2 for airspeed calibration as well
...
This is according to the updated mavlink spec to deconflict the definition
with APM.
2017-02-24 08:24:53 +01:00
3a358422c4
mc_pos_control: change sign for close to ground + style fix
2017-02-23 23:26:17 +01:00
de9d05c292
mc_pos_control: uorb home_postition subscription
2017-02-23 23:26:17 +01:00
e6031a97fa
land_detector: added a parameter for the manual land detection stick throshold
...
because it is definitely something that needs to be allowed to tune or disable for different application scenarios
2017-02-23 13:18:49 +01:00
4bffb1478f
ekf2: added parameter for range sensor pitch offset
...
Signed-off-by: Roman <bapstroman@gmail.com >
2017-02-22 22:21:41 +01:00
3183cbda90
land_detector: manual land detection stick throshold less strict
...
Even for well calibrated RC sticks 5% stick movement is a too small margin for the end user that might not land because of this.
15% is still clearly restricting the stick far down.
2017-02-22 21:56:41 +01:00
cbc54c9917
mc_pos_control: only swithc to velocity control from hold_engaged when user moves stick
2017-02-22 20:48:40 +01:00
d7683e97a3
MC pos control: More landing handling
2017-02-22 09:33:12 +01:00
Beat Küng