- Joined
- May 26, 2015
- Messages
- 1,351
- Reaction score
- 417
Looks like TBE = bad calibration. Always double check compass mod after calibration and before every flight . Hopefully you can get back up in the air soon!! Good luck !!
X and Y should be orthogonal, so between the two calibrations I think one of them had the Phantom face down/up and the other had it with the rightside/leftside down....I need to check when I get home...I think x is forward and y is to the right....or it is swapped in the data between Luap and I....I used Bud's latest datconverter. When I checked the charts I only made sure that the values started and ended at the same point going through the same range and that on step 2 x or y went to a value close what z was during step 1....
Watching Luap's video it seems to look like @TmoneyF had it right side down....I am not sure what this would do.
@TmoneyF,
Does that match your recollection for part 2 of the compass calibration?
didn't hit the power lines. no tumbling until it hit the ground
Are you going to post the full video then? I find the lack of video from close to the powerlines not very coincidental.
@TheRealNick, @TmoneyF There is an issue when the internal representation of the orientation is converted to the roll, pitch, and yaw numbers that you see. It's called gimbal lock if you're interested. It's apparent in the pitch where the value jumps from -90 to +90. That's physically impossible. The same happens with yaw and roll.I've recorded how calibration was logged for this thread's flight, bottom video, and another user calibrating his P3, top video.
If you watch the 3 Phantoms in the top video calibration looks like how it should be done. But the bottom looks very odd?
To check how a calibration looks like on the 3 Phantom Gauges in Dashware I taped myself doing a calibration procedure (1st 30secs in the video). Then did some wild stuff. Then synched the Dashware render to the video.
With FLY013.DAT I rendered the calibration procedure starting and ending as per the ticks of the log file.
Step 1 of calibration, the anticlockwise yaw is correct. Then there is a 20 second interval before step 2 is performed. And instead of pitch being applied its clearly roll.
Why would there be roll? Is it due to a magnetic source or is it an incorrect manipulation? Whichever reason, could this be the reason of the drift? Anyone want to try calibrating using roll instead of pitch and see whether calibration reports as successful (be warned this could lead to a crash)?
Nice video and dashware, all your hard work helps everyone understand! Also, perfect compass calibration!
I am pretty sure it was calibrated with roll (side downward) instead of pitch (front downward), you can check the accelerometers and the y goes to -1 during the second part of the calibration, I have no idea what this would do....graph below...you can see Z accelerometer goes from -1 to 0 and Y accelerometer goes from 0 to -1 and Mag Y goes to value Z was before (I took Mag Z off for clarity, but it is in an earlier chart I posted)....
View attachment 40636
I've recorded how calibration was logged for this thread's flight, bottom video, and another user calibrating his P3, top video.
If you watch the 3 Phantoms in the top video calibration looks like how it should be done. But the bottom looks very odd?
I fly within feet of power lines nearly every single flight, for over 100 flights... never had an issue. I really do not think power lines will cause an issue for a phantom, unless you hit them, additionally, on the way to taking my phantom out nearly every flight i have to fly over these because i get the best distance in that direction: see photo below. Never had an issue.My take on that first video is it got close to the power lines and the P3 freaked out, they put out a lot of juice, and the magnetic field on them power lines is quite a spread out..
@TmoneyF - Did you ever get the video off the SD card? I would suspect the video is not cut in two like the videos you got off the transmitter. Sitting here thinking about it, perhaps the RC signal was lost which caused the video to split and the Phantom was not quite yet in Return to Home (RTH) but also not holding....that would match the 3 second timeframe of the drift...
Anyone know exactly what happens during the 3 seconds before a Phantom starts RTH? Does it stop? Does it drift? I know a lot of people fly it out until it loses signal and then it RTH, does it keep going forward for those 3 seconds?
It stops & waits for input, then initiates the RTH.
@TmoneyF - Did you ever get the video off the SD card? I would suspect the video is not cut in two like the videos you got off the transmitter. Sitting here thinking about it, perhaps the RC signal was lost which caused the video to split and the Phantom was not quite yet in Return to Home (RTH) but also not holding....that would match the 3 second timeframe of the drift...
Anyone know exactly what happens during the 3 seconds before a Phantom starts RTH? Does it stop? Does it drift? I know a lot of people fly it out until it loses signal and then it RTH, does it keep going forward for those 3 seconds?
We use essential cookies to make this site work, and optional cookies to enhance your experience.