Envirover
Envirover
The status report message size increased beyond 50 bytes after the move to MAVLink 2 and HIGH_LATENCY2 message - it will consume twice as much credit as before. That happened...
Adding support for TCP autopilot connection looks pretty straightforward. You can try it if you have time. Here are a few tips: - RadioRoom already has class MAVLinkTCP in mavio...
- Add STL files and bill of materials for the RadioRoom enclosure - Update the pictures in READMEs and docs to use the 3D printed enclosure.
Set HIGH_LATENCY2.custom2 to 0 for TCP channel and to 1 for ISBD.
HIGH_LATENCY2 message sometimes has sysid=255 instead of 1. ``` [32muvhub_1 |[0m 2021-03-18 04:04:07 WARN System ID of the autopilot (255) does not match system ID of UV Hub (1). [32muvhub_1...
We have an issue when sending (both from MissionPlanner or QGCS connected to UVHUB) GUIDED command. RadioRoom returns the following error: "Ignored mission item from rejected mission" See http://disq.us/p/2fn9cwk
The current implementation of MAVLinkTCP::receive_message() uses complex logic to determine MAVLink message size. Adding support for MAVLink 2 complicated it even more. The implementation should be simplified to just read...
HIGH_LATENCY ( #234 ) MAVLink messages was deprecated and replaced by [HIGH_LATENCY2](https://mavlink.io/en/messages/common.html#HIGH_LATENCY2) (2020-10).
Radioroom uses currently deprecated MAVLink 1.0 C library that was not updated for 3 years.
radioroom.log file is not rotated, thought the log file rotation is configured in /etc/logrotate.d/radioroom_lr.conf.