Uploading .plan to ArduPilot using import_qgroundcontrol_mission corrupts parameter

[matthieu-db]

For the DIGICAM_CONTROL message, when uploading the .plan (attached as a .json) parameter 5 comes back when downloaded as 1.28e-5 instead of 1. The drone also doesn't take a picture (which it should because I am setting it to 1)

What could cause this? Is there a workaround?

before upload to drone: testpretty.json

after being downloaded from the drone: testdownloaded.json

Script I used to upload to the drone:

import asyncio

from mavsdk import System
import mavsdk.mission_raw


async def run():
    drone = System()
    await drone.connect(system_address="udp://0.0.0.0:14555")

    print("Waiting for drone to connect...")
    async for state in drone.core.connection_state():
        if state.is_connected:
            print(f"-- Connected to drone!")
            break

    out = await drone.mission_raw.import_qgroundcontrol_mission(
        "testpretty.plan")

    print(f"{len(out.mission_items)} mission items and "
          f"{len(out.rally_items)} rally items imported.")

    await drone.mission_raw.upload_mission(out.mission_items)

    print("Mission uploaded")


if __name__ == "__main__":
    # Run the asyncio loop
    asyncio.run(run())

[matthieu-db]

I noticed this when testing our software (using MAVSDK-Java) with a real drone running ArduPilot 4.4.4. Then reproduced it with this minimal example using the Mission Planner SITL. and the above python script.

[julianoes]

Not optimal, thanks for the issue.

Any chance you can make a unit test that shows it and fails?
https://github.com/mavlink/MAVSDK/blob/main/src/mavsdk/plugins/mission_raw/mission_import_test.cpp

[julianoes]

Fix coming: #2560.