- Joined
- Aug 20, 2014
- Messages
- 289
- Reaction score
- 104
Flew my P3P yesterday. All was good for multiple flights, until one flight when things went bad:
Compass MOD was OK, around 1480. I took off in front of a church at night, and was going straight up.
Then, when it was high up, it suddenly started drifting without me moving the sticks. The app showed a red alert "compass error". I tried to get it back but it was going further away, missing a building and at that point I really got scared as there were people in the area and I did not have control over it.
I had just planned going up and down and was not ready for the elevated heartbeats, especially as a person next to me shouted: " if that thing scratches my car, I'm going to kill you..."
The p3p was still high up, and seconds looked as minutes. I think I switched it to Attitude mode, and after getting my orientation, I was able to get it back and land it without hitting anything. It felt like navigating a boat in a huge storm. When I regained the phantom, I looked at the controller and it was in Attitude mode and I was wondering- did I send it like that, or did I switch it in midair when the problem occurred? I will need to check the logs to see what exactly happened, was it instinct, user error or a p3p issue.
Now is the time I wish there was a sticky post with direction how to pull the logs and analyze them....
[UPDATE 7/29/2015]
II got the following information from the log file:
1. There is no compass error - even though the app alerted me there was....
2. The bird switches to using VISION at the time 00:29.5 until 01:02.5 ?!?!?!!!
3. For the same period as above the unit gets a YAW_ERROR_LARGE for nonGPScause
4. Throughout the flight, imuInitFailReason is set to MonitorError, but imuInitFailReason.raw is 0, so does not seem like a problem
Compass MOD was OK, around 1480. I took off in front of a church at night, and was going straight up.
Then, when it was high up, it suddenly started drifting without me moving the sticks. The app showed a red alert "compass error". I tried to get it back but it was going further away, missing a building and at that point I really got scared as there were people in the area and I did not have control over it.
I had just planned going up and down and was not ready for the elevated heartbeats, especially as a person next to me shouted: " if that thing scratches my car, I'm going to kill you..."
The p3p was still high up, and seconds looked as minutes. I think I switched it to Attitude mode, and after getting my orientation, I was able to get it back and land it without hitting anything. It felt like navigating a boat in a huge storm. When I regained the phantom, I looked at the controller and it was in Attitude mode and I was wondering- did I send it like that, or did I switch it in midair when the problem occurred? I will need to check the logs to see what exactly happened, was it instinct, user error or a p3p issue.
Now is the time I wish there was a sticky post with direction how to pull the logs and analyze them....
[UPDATE 7/29/2015]
II got the following information from the log file:
1. There is no compass error - even though the app alerted me there was....
2. The bird switches to using VISION at the time 00:29.5 until 01:02.5 ?!?!?!!!
3. For the same period as above the unit gets a YAW_ERROR_LARGE for nonGPScause
4. Throughout the flight, imuInitFailReason is set to MonitorError, but imuInitFailReason.raw is 0, so does not seem like a problem
Last edited: