- Joined
- May 4, 2015
- Messages
- 2,134
- Reaction score
- 820
- Age
- 62
As everyone knows 3DR is battling a GPS issue that they attempted to band-aid with the last firmware.
In my case it just slowed down the time it takes to get to Fly GPS mode.
This week I had a tiny issue which I would not have ruled out as pilot error. Basically, upon landing it was dancing around more than normal and when I tried to set it down it caught a leg and flipped over. It basically had landed but when it flipped over it spun the props on concrete which destroyed them before I could AB - Pause.
I looked at log file and everything looked fine except the GPS location on the final second or two showed Solo about 50' from actual.
So just for the heck of it and to test the tech support submit log function I submitted the log.
I got an initiation repression asking for complete details, proof of purchase, was anything damaged, etc.
The second response was this.
Hi Rich,
I went through your logs.
Apparently, you experienced a GPS glitch.
The GPS horizontal position didn't match the real position of the drone for an instant.
This made the Solo move to that incorrect position.
The new update release, that you already have (1.0.5), handles the GPS glitch better by switching to Fly: manual mode when there's inconsistent GPS data.
That mode is not GPS-dependent, so it there's a GPS error, the Solo's position will not be affected.
You probably will not experience anything like that now that you've updated your system.
Let me know if you have any questions, Rich.
Best regards,
Diego
[Technical support engineer]
I was a little confused by his response, so I replied that this was my replacement (#2) Solo and that it actually was shipped back to me with the new firmware. It was running the new firmware when this happened.
His response back was.
HI Rich,
Thanks for the info.
I'll share your log with my colleagues and have a second look at it.
Were the propellers the only damage to the Solo?
Best regards,
Diego
[Technical support engineer]
So either the glitch problem continues with the new firmware or tech support is not paying attention and really evaluating logs.
I did find it odd the logs showed the aircraft moved 50' in the final 2 seconds when it really did not.
In my case it just slowed down the time it takes to get to Fly GPS mode.
This week I had a tiny issue which I would not have ruled out as pilot error. Basically, upon landing it was dancing around more than normal and when I tried to set it down it caught a leg and flipped over. It basically had landed but when it flipped over it spun the props on concrete which destroyed them before I could AB - Pause.
I looked at log file and everything looked fine except the GPS location on the final second or two showed Solo about 50' from actual.
So just for the heck of it and to test the tech support submit log function I submitted the log.
I got an initiation repression asking for complete details, proof of purchase, was anything damaged, etc.
The second response was this.
Hi Rich,
I went through your logs.
Apparently, you experienced a GPS glitch.
The GPS horizontal position didn't match the real position of the drone for an instant.
This made the Solo move to that incorrect position.
The new update release, that you already have (1.0.5), handles the GPS glitch better by switching to Fly: manual mode when there's inconsistent GPS data.
That mode is not GPS-dependent, so it there's a GPS error, the Solo's position will not be affected.
You probably will not experience anything like that now that you've updated your system.
Let me know if you have any questions, Rich.
Best regards,
Diego
[Technical support engineer]
I was a little confused by his response, so I replied that this was my replacement (#2) Solo and that it actually was shipped back to me with the new firmware. It was running the new firmware when this happened.
His response back was.
HI Rich,
Thanks for the info.
I'll share your log with my colleagues and have a second look at it.
Were the propellers the only damage to the Solo?
Best regards,
Diego
[Technical support engineer]
So either the glitch problem continues with the new firmware or tech support is not paying attention and really evaluating logs.
I did find it odd the logs showed the aircraft moved 50' in the final 2 seconds when it really did not.