Dronelink Version 4.9.1 actual flight height higher than programmed flight height
We just upgraded to Dronelink Version 4.9.1 (290) Kernel 4.9.1 on March 30, 2024.
The new software was installed on a DJI RC Pro Enterprise controller and we used it to fly our Mavic 3M drone.
We programmed a mission to fly at 50 m AGL. Prior to takeoff, we confirmed the RTK was functioning properly and completed pre-flight checks.
At mission start, the drone went to 53 to 54 m AGL and started the mission. We immediately received a message stating that the drone was too far oof course. We landed the drone.
Winds were low (less than 10 km/h gusts) and we could not determine the issue.
We reset the Motion Error Tolerance (MET) to 1 m and 1 m. This is odd because with the RTK functioning, we typically set the MET to 0.5 m and don't have any issues.
We confirmed the the Home Point elevation was 0 m on the Dronelink App and relaunched. At mission start, the drone rose to 54 m AGL and continued the flight and we immediately received the done too far off course error. We landed the drone again.
We reset the MET to 5 m and 5 m and rechecked the drone and Home Point elevation and started the mission for a 3rd time.
The third time, the drone rose to 54 m AGL and ran the mission at that height. Presumably, we did not get the drone too far off course error because the Vertical Tolerance was not exceeded.
After we ran the mission with the Mavic 3M, we also ran a comparison mission with our DJI Mini 3 Pro using a DJI RC-N1 controller in conjunction with an Android phone. We couldn't proceed until we upgraded the Android App on our phone so we upgraded to Version 4.9.1 (290) Kernel 4.9.1.
We reprogrammed the mission to fly at 35 m AGL to account for the lower camera quality and proceed to complete the mission. The Mini 3 Pro is not capable of RTK flight so this mission was run without the benefit of RTK corrections. The MET was left at 5 m and 5 m.
During the flight with the Mini 3 Pro, the drone flew at 38 to 39 m AGL but the mission was completed successfully.
After the mission, I confirmed that the latest versions of the DJI firmware (drones and RCs) were in use during both flights.
Is this an issue with the drones and controllers or an issue with the recently updated Dronelink Version 4.9.1?
Comments
2 comments
I also have updated to Version 4.9.1 (290) Kernel 4.9.1. on my DJI RC Pro (not enterprise). Today I flew two separate missions flying my Air 2s, one was a map mission and the second was an orbit mission. Both missions were set to 100ft AGL as this was my approved ceiling for the zone I was flying in. During both missions the drone remained between 98 and 99 AGL, so my altitude variation was not quite as wide as yours and within acceptable tolerances for my purposes.
There were no changes from 4.9.0 to 4.9.1 that should have affected this. Please try on a different day / location to see if it is reproducible.
Please sign in to leave a comment.