@BlueVista For the sake of clarity, below is a closer view of what occurred. You can see the GPS(0):hDOP spike which cause the actual termination of the mission and the switch to ATTI with the navHealth drop.
[...] You can see the GPS(0):hDOP spike which cause the actual termination of the mission and the switch to ATTI with the navHealth drop.
Let me refer you for a more detailed analysis if possible. Maybe @BudWalker could give you a bit more insight in to the issue.What would be causing this type of GPS problem?
The answer is the same as it was in June. Take a look hereOkay, so... now what?
What would be causing this type of GPS problem?
Is it something wrong with the Phantom itself that could be addressed in some way?
It's also a little bothersome that I couldn't simply re-try the mission, because of that very odd error message.
(thanks again for the analysis)
For some reason I'm unable to PM you But, here is what I tried to send you.True. And per your suggestion I sent a couple of emails to Thunderdrone but never got a reply. Right after that, the problem disappeared for a while and we had no issues whatsoever with the earlier project. I just sent another email to Thunderdrone, and also used their online submission form, so I'm hoping that will work. By all accounts they have a good record, so I expect they were simply busy at the time.
FWIW, I'm not opposed to replacing the GPS myself, but I'd rather have a pro do it if possible.
We use essential cookies to make this site work, and optional cookies to enhance your experience.