This may have already been mentioned. I didn't read every post in the thread.
But...
In the Vision APP, pay attention to the Distance reading at the bottom next to the radar.
N/A means it has not set home point yet.
0 M or 0 Ft means it's on the home point. My checklist includes swiping into the ground station view to verify the home point and current location are on the map where I am.
Usually it's difficult outdoors in bright sunlight to watch the tail lights carefully. IMO it's virtually impossible to keep my eyes on the lights the whole time when I'm trying to go through the checklist and other people are around.
This will be somewhat academic when the next firmware is released as the app will warn you and prevent launch if home point has not been set.
I'm certain this is in direct response to DJI investigating the causes of flyaways and crashes.
They surely know much more about the various causes than we do and they are working on improving the software to help prevent these user errors which I'm sure cost them a lot of money.
When the Inspire 1 had several reported crashes with no pilot error, DJI used the Inspire's logged data to determine the cause was bad IMU calibration so they updated the app to warn the pilot and prevent takeoff if the IMU requires calibration. This update should also make it into the next Phantom 2 Vision/Vision + firmware also, so we benefit from the additional logging and reporting DJI added to the Inspire.
packetlos said:
... I think the phantom is loosing the control signal due to interfrence and then responding incorrectly to rouge commands, ...
That's virtually impossible. The control signal is spread spectrum and bound to a specific transmitter with a unique encryption code.
Any interference might block the control signal but there could be no rogue commands unless someone has captured and is deliberately spoofing your transmitters unique ID.
It would be trivial to capture a transmitters ID code since it is broadcast every time you turn on the transmitter, but I think that scenario is an unlikely cause of any significant number of fly away events.