- Joined
- Aug 24, 2014
- Messages
- 219
- Reaction score
- 75
Here is the last word on flyaways.....
Fear of Flying 2016 - The Last Word on Drone Flyaways! - Drone Flyers
Fear of Flying 2016 - The Last Word on Drone Flyaways! - Drone Flyers
I'm in the camp that believes that calibrating every flight will increase risk of a bad calibration. There is no logical reason to calibrate at every flight location, much less every battery. The exceptions are:
1. If you your flight location is over 100mi from the last flight
2. The sensor mod value is out of range
3. You've just loaded new firmware.
Calibrating every flight location introduces the risk of being in an area that you have NO IDEA what's below you for magnetic anomalies, and if you do have something strange at the area you can get a bad calibration and not know it. If the Mod value is 1450 to 1550, I always fly the same calibration. If it's beyond this value, I'll move the bird about 40-50' to another location and 90% of the time the mod value is within the 1450-1550 range and I fly it. In the 7 months I've been flying my P3P, I've had only one compass error (about 6wks ago) and I had to bring the bird back to recalibrate. I deem that as pretty solid, and I've never had a hint of a fly away. I do know that P2 craft had many reports of fly-aways (pre-lightbridge), however many P2 owners swear by them. That's why I waited until July to buy the P3P, waiting for the reports, or lack of.
More like the latest BS. Consider the source.Here is the last word on flyaways.....
Fear of Flying 2016 - The Last Word on Drone Flyaways! - Drone Flyers
Flyaways are very rare with the Phantom 3. In most (all?) cases, it was probably due to pilot error (e.g. too much wind and/or confusion after auto flipping into ATTI mode). If you take the time to gain a deep understanding of how your Phantom works, this should never happen to you.
This is a point, what happens if I'm two miles out and I get a compass error? I know the craft switches to ATTI automatically, but what about telemetry?I could get into a lengthy conversation with you based on your quoted response here. But I wont and don't plan to. I will repeat some of what I have said in the past which is....most know I'm a dji product and beta tester. We have been told more then once by those that develop the firmware the compass should be calibrate each time prior to start up. It only takes 15 seconds max to do the process. I think if I were on one of my 2 miles out from home point and happen to have a compass error I would probably have heart failure. I do know I would be lighting a cigarette up for sure. Anyway, the last time the engineers mentioned calibrating the compass I asked for an explanation as to why it should calibrated before each start up. And they never did/would give a response.
Like I said I don't want to hash on this subject with you, and don't want you getting upset either. So let's move on.... Thanks!
Fantasmagorico, it sounds like you were flying in ATTI mode during the part of your flight where it seemed you had no control over your Phantom. Please upload your TXT flight log here and post a link back here if you'd like us to review it and help explained what happened.
Thank you. I was never in ATTI mode, but it seems from what I have read after the incident that switching to it and then back to GPS mode, or staying in ATTI mode to fly with the arrow, might have helped. I attach the flight log. You can also access additional flight data from Healthy Drones at this link:
HealthyDrones.com - Innovative flight data analysis that matters
1. The 75% charge is due to the fact I started to fly using VR goggles for the first time using the FPV Camera app. I didn't like the goggles and landed the bird, then took off again using the DJI GO app.I downloaded and converted your flight log and scanned over it briefly for redflags. I saw some things I never seen before which got me interested. I then came back here to see what you may have said in your post. I will now pay more attention to areas of the flight log I haven't really looked at yet.
At this time I feel like the number 1 reason most all of this took place centers around the fact the you started this flight with a 75% charged battery. You only have a short time before the battery starts into set cycles per the remaining charge. Then based on what you have the app set at when it reaches the more critical stages will determine how you will be able to fly the a/c. Btw, the temp on the battery also reached 143.5 degrees. That is close to melt down.
The log shows it was attempting to auto land at its current location.It was attempting to RTH when you were trying to take over.
The log shows it was attempting to auto land at its current location.
Prior to the auto landing, he was flying in home lock mode. Perhaps that's why he noted the odd flight behavior here:My reference was pretty much from the 18.13 point. Even though flight details show "Autolanding", the flight went to a RTH attempting to go up to the 400ft set point in the app. When the user manually over took the controls the climb paused until the controls went to neutral once again. And once that happened it returned to the 400ft climb.
The altitude data shows the a/c increasing altitude to the end, not landing.
I could move it right or left on an arc, or away from me, but not toward me.