After spending many hours troubleshooting and waiting days for responses from support I finally took back my first Solo the was eventually deemed defective by 3DR for a number of issues. It took another 2.5hrs at the retailer to perform the exchange and a 5 day wait with a 3 hour commute to pick up Solo #2 at the nearest retailer with inventory.
I will say that I was quite excited when unboxing #2 as the whole process was extremely smooth compare the previous one. in less then 10 minutes #2 was updated to 1.05 and fully calibrated. It had 12-13 satelites registered and locked in seconds from startup. #1 took a minimum of 4-5 minutes if I was lucky to lock 6 for auto fly. Not to mention the controller showed full bars for solo connectivity and telemtry readings in the app were dead on.
With such good flight conditions before packing up the kids in the car to head over the field I decided to take #2 up and down just to confirm flight first. here is #2's first flight video 10 mins from coming out of the box.
Solo - $999
Gimbal(still haven't recieved) - $399
GoPro 4blk - $499
Xtra batterys - $597
spare parts - $80
40+hrs invested in troubleshooting/support and exchange of 1st Solo - $3000
Capturing this majestic first flight on video - Priceless!
I really think Solo is a great design aside from GPS location. yeah they crammed copper under it, so they knew there was an issue, But do you not agree that coding can solve the issues I described as far as not allowing GPS to make corrections of flight and being able to kill the motors when a crash or bad landing is detected. Seriously as a developer, its not that much code to put if solo = 180 degrees on its head set throttle zero and disarm.
I agree, with the code is impossible isolate these interferences, new U-Blox are very susceptible to these things.
In the "Spark" project we had similar problems with M8N unit, but we solved them with hardware changes before selling the product.
Having come from another brand who's customer service and backing of their products was complete utter crap I have to say I've been pretty happy with the Solo after flying a friends teaching him how to fly and now finally getting mine. I had tried to help him fly with several different models and the Solo sent his confidence and flight skills through the roof. It's been a blast to watch and be a part of!
Forget the 'bag of rice' trick to dry electronics that gets wet. The best way to dry anything is to push hot air through it at speed. Use a hair dryer. It works great is a much faster and effective way to dry things out. After all, drying something requires evaporating the water and then removing the water molecules. In other words, push hot air through it.
If its Open Source, then why are you violating GPL, by not releasing the full code?
GPL requires it, in fact you're currently only releasing bits and pieces.
As far as i can tell the companion computer is passing wifi command and pushing G Streamer... Not exactly groundbreaking dual computer processing.
But back to the matter of Solo code. Where is the next firmware that addresses the issues currently experienced... GPS loss, GPS drift. Props running after crash, Random bounces on landing?
Im tired of being a BETA tester for your overhyped product that cant even meet its release schedule.
Where are the backpacks that Colin Promised to hit the shelves last week? The Gimbal at the end of July?
Where is Solo 1.1 Final, or Solo1.2 Final.
Are we just going to continue to ignore the GPS being in the worst position possible, and the fact that since GoPro was first put on FPV flights there was known interference from its RF and recommendation of shielding the GoPro with Copper and placing it 13 inches away, Yet youve decided to set GPS right above it.
There is so much going on in the area of the GPS:
GoPro under emitting RF
Battery Blocking one entire GPS horizon
Battery Power wires directly beside
PC board also emitting RF under it
Oh and you run the wifi antenna under to the front leg.
Go ahead boot it up and set the controller down beside it so you can watch. Power on GoPro and watch it drop satellites.
Then turn on a wifi analyzer app and watch sololink when you turn on a GoPro. it loses 3-6 dbi that at minimum is halfing or leaving you with a quarter of the original signal.
Effectively nulling the 2-3dbi nub antennas on the controller.
There ya go, thats my R&D, done BETA testing... fix it, recall it, or refund it.
ETA: i have 62 flights on SOLO
Hi Bob, i'm sorry to contradict you, but i fly over a year with this DJI S1000 installing Pixhawk board and i never had a single problem.
I know very well A2, WKM, Naza and all the other DJI products because i have used and configured them many times.
This big bird has to his credit more than 1500 automatic mission without single issue.
And as you can see there's about $ 13,000 installed in the 3 axis gimbal (multispectral and thermal cam "combo").
It always depends on how you configure it, most of the causes of crashes are related to a wrong setup, wrong wiring, bad tuning and newbie pilot.
So said that APM:Copter doesn't work well perhaps means not knowing how to configure it properly.
The Solo is another product, i can't leave my feedback about it because i never tried.
About the connector: what is clear, i hate DF13, the new "Pixhawk 2" will have a special molex, much better.
Nice copter. (Bob's flying his Naza right now though, so he will not appreciate your fine machine)
APM:Copter is a great code, but you also know how to configure it properly.
IMHO many times people don't appreciate it means that may not know what is flying... ;-)
I think the Solo-specific code is not open source.
But yes, your technical comments are very worrying for 3DR. I have read a lot of credible analysis to the same effect. It is not something that can be swept under the carpet. This smells of recall...not sure poor GPS location has a firmware fix.