each time you turn your solo on and off that is considered a log.
and the only go back 3 logs so all the other ones will not be available.
each time you turn your solo on and off that is considered a log.
and the only go back 3 logs so all the other ones will not be available.
Here you go..Actually I believe there are the last 10 logs stored on the controller, only 3 are sent by the support ticket method.
thx i didn't know this.
The motors spun for quite some time in that video after the Solo flew into the foliage... Did you try the emergency stop procedure?
I was wondering this...
@Chip Luck ..If everything els fails trying to figure out the problem at its Source..! I'm thinking that is it possible that your FW has a Glitch..?
How about bringing your Solo and Controler back to its (out of the box original Factory firmware state) then reload the latest FW back into your Solo and Controler again! I don't know if this would correct your problem your having..but mabe its worth a shot!
Mabe someone with more experience than me could shed some light on this ideal?
Had this problem once when landing pretty close to the house 10 or 15 feet awAy or so. Solo landed lost gps and tried to take off again on its own straight into the house but I was pretty high up when holding the fly button now I either catch the solo or make sure it is very low before initiating landing.I have had 7 total low level flyaway's as of the last flight a few days ago. First, let me state I have had NO 'high' altitude flyaway's, ever. Seems to occur a a low altitude around 10 feet or so, and always around the home position. Flight mode is in default GPS mode, no smart shot modes, etc. All flights, Solo started up, GPS fix, etc. all completed before flight. Solo always appeared to be stable after pressing FLY button and would hover within a 1-3 foot pattern. Then I would do the usual flying around, capturing video and everything would be fine.
Now, EVERY TIME this has occurred has been near the HOME position and ALWAYS in a stationary or hover mode, then Solo will just bank, or dive (I have never noticed it turning) and head right into the woods, bushes, trees, etc.
I had no control over Solo with the Controller, it happens really quick. Solo just acted like "I need to be over there, not here" and just took off. Thank God nobody has been hurt, there was one close call while hovering in front of a sound booth, Solo almost entered the sound booth window, and that would have been REAL BAD. Instead, it veered forward (again NO control input from myself was in hover), hit the side of the elevate booth, hit my friends van, then a SUV and landed on the ground. That time = open sky, no trees to interfere with GPS.
I will no longer fly Solo near people again until I can find out what is going here. No, I have not yet sent log files to 3DR, but will today.
Anyway, here is a link to flyaway number 7 on YouTube, the actual flyaway is around the 4:11 mark:
I will have a complete compilation of all 7 flyaway's/crashes up soon on YouTube.
Any one else having this problem?
From personal experience I can tell you that the 3DR Solo is a super unreliable low flying bird if you're flying with GPS lock don't, switch to full manual can't tell you how many times my Solo crashed in a similar way to you're video. Seems to me like the Solo has shitty GPS locks, another word's the stock GPS cards in the Solo are easily thrown off by structures especially trees. I can't say that firmware updates will fix this problem but I do know not to fly my Solo near people or low to the ground at least until they release the optical flow. Just look at what happened at the US Open I bet you a million dollars that dude crashed due to GPS lost.I have had 7 total low level flyaway's as of the last flight a few days ago. First, let me state I have had NO 'high' altitude flyaway's, ever. Seems to occur a a low altitude around 10 feet or so, and always around the home position. Flight mode is in default GPS mode, no smart shot modes, etc. All flights, Solo started up, GPS fix, etc. all completed before flight. Solo always appeared to be stable after pressing FLY button and would hover within a 1-3 foot pattern. Then I would do the usual flying around, capturing video and everything would be fine.
Now, EVERY TIME this has occurred has been near the HOME position and ALWAYS in a stationary or hover mode, then Solo will just bank, or dive (I have never noticed it turning) and head right into the woods, bushes, trees, etc.
I had no control over Solo with the Controller, it happens really quick. Solo just acted like "I need to be over there, not here" and just took off. Thank God nobody has been hurt, there was one close call while hovering in front of a sound booth, Solo almost entered the sound booth window, and that would have been REAL BAD. Instead, it veered forward (again NO control input from myself was in hover), hit the side of the elevate booth, hit my friends van, then a SUV and landed on the ground. That time = open sky, no trees to interfere with GPS.
I will no longer fly Solo near people again until I can find out what is going here. No, I have not yet sent log files to 3DR, but will today.
Anyway, here is a link to flyaway number 7 on YouTube, the actual flyaway is around the 4:11 mark:
I will have a complete compilation of all 7 flyaway's/crashes up soon on YouTube.
Any one else having this problem?
From personal experience I can tell you that the 3DR Solo is a super unreliable low flying bird if you're flying with GPS lock don't, switch to full manual can't tell you how many times my Solo crashed in a similar way to you're video. Seems to me like the Solo has shitty GPS locks, another word's the stock GPS cards in the Solo are easily thrown off by structures especially trees. I can't say that firmware updates will fix this problem but I do know not to fly my Solo near people or low to the ground at least until they release the optical flow. Just look at what happened at the US Open I bet you a million dollars that dude crashed due to GPS lost.
Any way you could post one of your logs here? I'd like to take a look.
Sent from my VS985 4G using Tapatalk
Any way you could post one of your logs here? I'd like to take a look.
Sent from my VS985 4G using Tapatalk
I sure did I recommend you do too they told me it was a GPS error.Still not sure that GPS loss is the correct term - yet. Did you send you log files to 3DR?
We use essential cookies to make this site work, and optional cookies to enhance your experience.