a5485c97e0
mavlink: remove _log_enabled flag
...
It's obsolete since we removed the mavlink log file
2017-06-04 04:35:21 +08:00
e2fa5c2857
MAVLink: Remove status text output
...
The MAVLink app was logging the status to a file on the SD card, however, this has been integrated into the ulog format since. Having these in multiple locations is unnecessarily confusing to the user and induces load to the system.
2017-06-04 04:35:21 +08:00
64ed96d81a
clang-tidy readability-simplify-boolean-expr
2017-06-02 19:35:18 -04:00
723a6bf6ac
mavlink: new MAV_CMD_IMAGE_START_CAPTURE spec
...
The spec of the mavlink command MAV_CMD_IMAGE_START_CAPTURE has changed.
2017-06-03 02:53:58 +08:00
74b0e485e7
MAVLink stream: Ensure the message is not sent again if it was already dispatched.
2017-05-19 10:34:43 +02:00
c84611f0f5
MAVLink: Fix rate handling for camera trigger messages
2017-05-19 10:34:43 +02:00
3d77102653
mavlink_main: remove MISSION_ITEM from streams configuration
2017-05-18 09:48:14 +02:00
2a79ddd621
MavlinkLogHandler: increase MAX_BYTES_SEND to 256kb
...
It increases the throughput on UDP (from around 2Mb to 2.5Mb), while the
rate via USB & telemetry stay the same.
2017-05-18 09:48:14 +02:00
a89980f440
MavlinkParametersManager: update sending rate
...
This is an adjustment due to the changed calling frequency of send()
(was 300 Hz, is now 100 Hz)
2017-05-18 09:48:14 +02:00
cfa61c5841
MavlinkReceiver: add mission manager, param manager, ftp and log handler
...
This makes also a slight stack size increase necessary (was 284 bytes left)
2017-05-18 09:48:14 +02:00
d70caeb24b
MavlinkParametersManager: remove MavlinkStream inheritance
2017-05-18 09:48:14 +02:00
a761c4189e
MavlinkMissionManager: remove MavlinkStream inheritance
2017-05-18 09:48:14 +02:00
99b29777ba
MavlinkLogHandler: remove MavlinkStream inheritance
2017-05-18 09:48:14 +02:00
e6c3b29aa6
MavlinkFTP: remove MavlinkStream inheritance
2017-05-18 09:48:14 +02:00
78c1f51f11
mavlink main: remove mission_manager, param manager, ftp & log handler
...
Will be moved to the receiver thread
2017-05-18 09:48:14 +02:00
4105394234
mavlink_receiver: check for allocation failure
...
Also remove the start() declration (there's no definition of that)
2017-05-18 09:48:14 +02:00
2c548f84a7
refator mavlink: prefix class members with _
2017-05-18 09:48:14 +02:00
ad5fe5f44a
Add support for SET_CAMERA_MODE command; Not used yet.
2017-05-12 22:11:17 +02:00
192e8b48d1
mavlink : send camera_image_captured message
2017-05-12 22:11:17 +02:00
2e92a3946d
camera_trigger : completely refactor state handling
2017-05-12 22:11:17 +02:00
7af7c86384
mavlink : send camera capture information
2017-05-12 22:11:17 +02:00
1b7838c2fe
Implement Mavlink PLAY_TUNE
2017-04-27 14:48:25 +02:00
21f409366a
MAVLink app: Warn sender if a command has been rejected
2017-04-23 19:23:09 +02:00
f8e291dab1
mavlink VFR_HUD throttle use first 2 groups ( #7106 )
...
- fixes #6974
2017-04-22 16:08:27 -04:00
96458d3184
Support for RTL and Delay mission commands
2017-04-18 08:56:01 +02:00
34058cbc21
mavlink EXTENDED_SYS_STATUS add takeoff and landing ( #7064 )
2017-04-17 09:31:49 -04:00
3fda79ef8b
set battery warning for MAVLink battery status ( #6890 )
2017-04-13 12:37:19 -04:00
c7d9a7a6d1
mavlink_log_handler: fix potential buffer overflow
2017-04-06 11:48:35 +02:00
3c1d785d86
mavlink_mission: set INT frame correctly
...
Also when formatting malvink mission items from internal mission items,
the INT flag should be obeyed.
2017-04-01 20:07:55 +02:00
80ce1b6dd8
mavlink_mission: support INT altitude frames
...
The relative altitude flag was not set correclty when waypoints are sent
using the INT protocol.
2017-04-01 20:07:55 +02:00
79d15ad2f0
mavlink stream camera trigger broadcast DO_DIGICAM
2017-03-26 14:05:38 +02:00
8a6b6f9be5
Send MAVLink DO_DIGICAM_CONTROL on camera trigger ( #6815 )
2017-03-24 13:24:09 -04:00
7695b65b7f
MAVLink app: Default to MISSION, not MISSION_INT
...
In order to ensure correct transmission the mission system needs to default to the legacy protocol and switch to the new implementation when these conditions are met:
* If the GCS sends a MISSION_REQUEST_INT - it will do this based on the AUTOPILOT_VERSION flag indicating int mission support
* If the autopilot sends a MISSION_REQUEST and has the AUTOPILOT_VERSION flag for 2.0 set, the GCS should NACK it, which will make the autopilot retry a MISSION_REQUEST_INT
* If the autopilot sends a MISSION_REQUEST_INT and the GCS does not support it, the GCS will ignore and time out. The autopilot could retry now opportunistically with the old protocol, but this is not great for lossy links.
* If the GCS sends a MISSION_ITEM_INT - this is a fallback
2017-03-16 23:16:39 +01:00
45af77a543
mavlink parameters: try to send 5 params at once on USB & UDP connections
...
This further speeds up param loading.
On Pixracer via USB, it's possible to send up to 11 at once before the TX
buffer gets full, so there is still enough free bandwidth left.
2017-03-14 21:30:04 +01:00
2873d973de
mavlink: increase parameter rate from 120 to 300Hz
...
This speeds up parameter loading. Slow links like telemetry are unaffected,
since the mavlink loop runs only with ~100Hz.
Tested on various links, like:
- telemetry link
- pixracer WiFi
- pixracer USB
- SITL
2017-03-14 21:30:04 +01:00
2af5d1b929
Mission transfer: Fix retry logic
...
Previously the retry would not actually have been sent if nothing had been received in time.
2017-03-13 21:51:21 +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
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
f5ae90a7cb
mavlink_main: add POSITION_TARGET_LOCAL_NED to mavlink stream
2017-03-03 07:23:02 +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
ecb2511a7b
add matrix copyTo
2017-02-25 11:04:02 +01:00
80e1064523
mavlink : fix legacy vision interface attitude timestamps
2017-02-24 08:51:05 +01:00
e4ca10363b
mavlink MAV_CMD_IMAGE_START_CAPTURE message: send request for highest resolution
2017-02-17 23:01:25 +01:00
7659402fdb
WIP: valgrind runtime analysis and fixes ( #6521 )
...
* Fix several valgrind identified mem leaks
* Added callgrind target.
* px4_posix_tasks use nullptr
2017-02-17 12:36:52 -05:00
44c8857354
MAVLink app: Update incorrect comment
2017-02-17 10:00:11 +01:00
0d61e22d9b
mavlink: Buffer UAVCAN parameter re-requests
...
We buffer the mavlink messages and don't forward them directly
via uORB. This solves an issue where many requests are dropped and
QGC does not start properly in combination with UAVCAN devices.
2017-02-17 09:15:56 +01:00
ea5caf258f
mavlink : fix vision debug stream attitude update
2017-02-16 09:53:15 +01:00
48e7b94162
mavlink : track time offset faster
2017-02-15 21:48:33 +01:00
d831c262d0
mavlink : fix code style
2017-02-15 21:48:33 +01:00
bdcc626f29
mavlink : correct stream name for vision message
2017-02-15 21:48:33 +01:00
Beat Küng