(First this initial code needs to be included in the main branch.) Discuss this first with open drone ID project. These are missing for a full implementation. add additional open drone ID messages like ACK and Command message. add support for the Auth messages, Support for MessagePack messages is not planned as current message set already cover full functionality. get this code reviewed and included into the master branch. Perhaps this is due to the 20 Hz update rate.~~ ~~See previous point, there seem to be issues with MAVLink parsing at the transponder.~~ ~~As such, some MAVLink packets are not recognized.~~ If multiple MAVLink messages are sent at the same time, some are skipped. ~~- sim vehicle simulator is too slow to test properly. Now all messages are successful decoded including the system message. I will do more investigation why with the (internal) test MAVLink TX application, all message types are decoded successful by the transponder, whereas with sim_vehicle it doesn't.~~ The issue was an outdated MAVLink library version at the transponder side. Clearly something goes wrong with parsing MAVLink messages at the transponder. Other open drone ID MAVLink messages are detected.~~ ~~If I look to the byte stream, system messages are transmitted by sim_vehicle. ~~- **System messages are not received by the transponder at all.** Cause unsure, perhaps MAVLink library needs to be regenerated? Even on low level the transponder does not detect this system message packet type. The received location values seem to be weird although the location data types are similar to open drone ID. location messages uses location data from ArduPilot (function: void GCS_MAVLINK::send_open_drone_id_location()) It needs review and improvement. current code sets dummy values for most fields in AP_OpenDroneID::init() This implementation supports these MAVLink messages: This command in the ArduPlane folder is used for testing: `sim_vehicle.py -wipe-eeprom -console -map -A -serial1=uart:/dev/ttyUSB1:9600` (and a DroneBeacon MAVLink transponder connected to ttyUSB1) WIP Initial Remote ID (open drone ID) implementation and tested with a Remote ID … MAVLink transponder (DroneBeacon MAVlLnk transponder, ).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |