Serious compass Bug with Phantom 2 / Vision +

Yes true, the suspicion even with some DJI dealers is that was due in many cases to compass/GPS issues, DJI generally blame the users, it should be noted for example Arducopter won't allow you to take off (unless you deliberately select a non-GPS mode) if there's an error including a poor GPS lock. The suggestion with this latest bug is that it'll cause a Phantom to drift off rather than fly-away but at least one Flytrex user (a third party tracker) has argued otherwise with a fly-away recently recorded:

http://www.flytrex.com/mission/quadcopter-bamf-gurtu-clan-25019/

Over a year on from the release of the Phantom, the Naza still doesn't enforce a strict pre-arm set of checks with meaningful error messages, I'm beginning to think this is deliberate so that users can always be blamed for fly-aways, the first accusation is always that the pre-arm checks weren't followed, I'm puzzled why the iOSD mini isn't used to relay decent, human understandable errors.

It's almost as difficult to diagnose a Naza issue as it is to diagnose a PC bios fault, only the LED is used where it wouldn't be difficult to display messages in clear English via the iOSD or a smart phone using the Bluetooth app for example.

Arducopter pre-arm checks make sure you can't take off with a problem and many error messages are displayed with a text description in English:
 
Last edited:
You must log in or register to reply here.
Back
Top