firmware issue that prevents the aircraft from executing Return-to-Home (RTH) on RC signal loss

Anyone got this in their e-mail box also , is it also affecting mappilot ? :

Here is the email from AutoFlightLogic:
"We discovered a DJI firmware issue that prevents the aircraft from executing Return-to-Home (RTH) on RC signal loss when any third-party app is connected via the SDK. Our testing does show that RTH will activate when the critical battery level is reached (configured in DJI GO), but this may result in the loss of your aircraft if the home location is too distant.

DJI indicated that this issue will be resolved in the next firmware update, but they have not given us a timeline. Until then, we strongly recommend that you do not operate Autopilot (or any third-party app) near the edge of signal range"

Bert Bosman 28. Januar 2016 09:23

Offizieller Kommentar

This is the warning they are showing at the top of their page:
" Critical Issue (01/25/16) We discovered a DJI firmware issue that prevents the aircraft from executing Return-to-Home (RTH) on RC signal loss when a third-party app is connected via the SDK and using this API function in Flight Mode F. Learn More"

The function they are talking about is for virtual stick control which is what they use to do their freeform flights. We do not use those functions since our flights are more structured and rely on the waypoint functionality which is not affected.

Map Pilot is not affected by this issue and will continue to operate as expected.

Tudor 28. Januar 2016 15:55

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

4 Kommentare

I had something similar happen to me yesterday. Not sure if its related to your issue above? I executed a mission and when the battery reached 20-19% it headed towards home point as expected but it didn't go all the way and started to descend into the trees about 200m from home point. At that time the battery was close to 10%. I'm not sure if that was part of a built in emergency landing procedure of the system, ie to land before bat is dead or firmware issue as mentioned above? I quickly switched the PAF to P and manually directed it up and to an open field where it landed itself safely. Thankfully everything ended up OK but concerns me that I should perhaps set my mission max time to something around 15 min instead of 17. And/or initiate a RTH manually instead of waiting form the app to initiate the RTH.

Upland 28. Januar 2016 15:38 0 Stimmen

Thanks !

Bert Bosman 28. Januar 2016 16:00 0 Stimmen

Upland: Your issue is 100% related to battery calibration. We have come across this a couple of times too since we do a lot of testing.

We have seen the battery jump from 25% to 0% instantly and the aircraft tries to make it to the ground safely wherever it is instead of coming home. It is certainly disconcerting. It sounds like you took the appropriate actions and we are glad there wasn't any damage.

It is VERY important to calibrate your batteries every 20 flights or so (per DJI). Calibrating your battery consists of running it down below 10% (we go to 8%) and then doing a full recharge on the STOCK CHARGER. We emphasize the use of the "stock charger" because there are documented issues using 3rd party chargers or even DJI's own charging hubs. There have been firmware updates to the charging hubs to make them capable of doing the calibration charge properly but we still just use the stock charger to be sure.

We will be posting an article on this soon.

Tudor 28. Januar 2016 16:01 0 Stimmen