You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently developing a mission management for an autonomous drone in Python, using MAVSDK's Python bindings. A mission is sent as a string to the drone's companion computer via LTE, gets imported using the command drone.mission.import_qgroundcontrol_mission and is then uploaded to the flight controller.
The inconvenience here is, that the function import_qgroundcontrol_mission only accepts a filename as input, so I have to write the received mission string to a file, Import that file and delete it again afterwards.This is especially inconvenient since most companion computers will use SD cards as their memory, which are notoriously short lived when receiving frequent write operations. Every write operation to disk you can avoid should be avoided.
Could we have an alternative import operation that accepts the plan data directly as string? I attempted integrate this function myself, but been struggling with correctly building everything for some time now. For a developer who has the build environment readily set up and understands the workings of MAVSDK, the effort should be very small.
The text was updated successfully, but these errors were encountered:
Thanks, that was quick!
I don't know if I can test it this year. Like I said, I'm struggling with building everything, but that is problably a story for another thread...
I'm currently developing a mission management for an autonomous drone in Python, using MAVSDK's Python bindings. A mission is sent as a string to the drone's companion computer via LTE, gets imported using the command
drone.mission.import_qgroundcontrol_mission
and is then uploaded to the flight controller.The inconvenience here is, that the function
import_qgroundcontrol_mission
only accepts a filename as input, so I have to write the received mission string to a file, Import that file and delete it again afterwards.This is especially inconvenient since most companion computers will use SD cards as their memory, which are notoriously short lived when receiving frequent write operations. Every write operation to disk you can avoid should be avoided.Could we have an alternative import operation that accepts the plan data directly as string? I attempted integrate this function myself, but been struggling with correctly building everything for some time now. For a developer who has the build environment readily set up and understands the workings of MAVSDK, the effort should be very small.
The text was updated successfully, but these errors were encountered: