- Joined
- Dec 7, 2013
- Messages
- 1,206
- Reaction score
- 136
Re: Preventing & Recovering a lost Phantom from a fly away
Many people on these threads are under the impression DJI has been "silent" on fly away issue. Well that's not entirely true as here's a video featuring DJI CIO Colin Guinn specifically addressing fly away issues, causes and steps they've taken to help prevent and stop them as they occur.
http://www.youtube.com/watch?v=2bxjL7wFyb8
So to sum it up many fly aways are not "crashes" as you put it but communication errors, interference related problems or combination of factors. During said fly aways dropping the flight mode to Atti and if that's not sufficient then Manual mode reduces cross talk between interfering components such as GPS, Compas, IMU, PMU, as it begins reducing flight control down to the lowest common denominator. For myself I only have GPS and Atti mode available and not Manual. I'd hate to accidentally switch to manual or a friend flying and switching to manual and crash my $1,200 Phantom.
Ton4 said:Migmon said:Doing a compas config sets the declination so the compas knows where is at for true and magnetic north, you only need to set it up if you move a hundred or so miles away
I suppose you mean calibration by "config" ?
Maybe true if the Naza has a database with inclinations from all over the world, but then a gps location would be enough.
I don't think the Naza cares about the true north. I think it will always use the magnetic north to navigate. (Therefore always navigates in "circles" in places with a high inclination)
I saw a guy on internet setting the compass of a naza (not mounted on Phantom, on other copter, hex if i remember well, with the naza gps/compass on top) in alignment with the true north, therefore eliminating the inclination.
Afaik the Wookong of DJI has a function where it notices navigation errors related to inclination, and adjusts the north reference accordingly, automatically. Don't think Phantoms have this.
True fly aways are Naza software crashes imho. A series of unexpected values (or some hardware fault) and kaboom. And without a brain, the Phantom just takes off, maybe just stuck in the last command it recieved. Probably the naza reboots after the crash, but does not find itself in a usual boot up situation, motors off, with little movement, and may crash again.
Any sudden unexpected changes in input could be detected imho. If its a "strange" gps signal, large change in air pressure, magnetic field, radio interference or whatever.
For instance, if the compass suddenly changes 45 degrees in direction without a good "navigation reason" it should be considered suspect. Its of outside origin.
Sent from my SM-T311 using Tapatalk
Many people on these threads are under the impression DJI has been "silent" on fly away issue. Well that's not entirely true as here's a video featuring DJI CIO Colin Guinn specifically addressing fly away issues, causes and steps they've taken to help prevent and stop them as they occur.
http://www.youtube.com/watch?v=2bxjL7wFyb8
So to sum it up many fly aways are not "crashes" as you put it but communication errors, interference related problems or combination of factors. During said fly aways dropping the flight mode to Atti and if that's not sufficient then Manual mode reduces cross talk between interfering components such as GPS, Compas, IMU, PMU, as it begins reducing flight control down to the lowest common denominator. For myself I only have GPS and Atti mode available and not Manual. I'd hate to accidentally switch to manual or a friend flying and switching to manual and crash my $1,200 Phantom.