3DR is proud to announce that today we’re opening the source code for the Solo flight controller. Solo is a consumer product, aimed at simplifying the process of getting great aerial footage. As a development story, true to 3DR’s open spirit, Solo was developed not just by us at 3DR, but in concert with the ardupilot core development team and contributors around the world. Solo’s flight characteristics, performance and robustness are a testament to the power and adaptability of APM:Copter, which is why we’re so pleased today to officially open that source code to the world at large: The repository with full history is now available for download on GitHub, the first of many development doors that we’ll be opening on Solo.
In addition to opening Solo source, we are today publishing the set of guiding principles that went into developing all of Solo’s subsystems--3DR’s Open Source Policy. The policy, developed by the 3DR software engineering team in conjunction with the the community, addresses key questions: How do we do development? What do we choose to open? Why do we do it in the first place? For 3DR, the policy represents a set of guiding principles on how we plan on doing development, and we feel it important to, in turn, open to the broader community for clarity, accountability and, well, because we’re excited to share it!
Solo: Open for development
We placed open source hardware and software at the core of Solo and view it as essential to our development and platform strategy. But it doesn't stop with the source! We strive to put powerful tools in the hands of developers. In some cases this means source code, and we plan on opening other parts of Solo, including much of SoloLink. In all cases this means making Solo the number one development platform, which means great APIs and developer tools. We plan on deepening DroneKit integration into Solo, so that developers can easily add new shots in Python and apps on Android, with new language bindings for other platforms coming soon.
The word ‘platform’ is getting quite a bit of traction these days. However, we believe it’s not enough to call something a platform ahead of building it. A platform isn’t an over-engineered airframe, coincidentally exposed cables or slides in a presentation; it’s a bolt pattern, a pinout, an API and a source code that exists in the real world with engineers to support it. So rather than pay lip service to the term, we chose to place the world’s leading autopilot development platform--APM:Copter--at the heart of Solo, running on the new Pixhawk 2. Connected to the flight controller we have SoloLink, which brings the power and flexibility of Linux computing onboard a consumer vehicle for the first time and appeals to an even broader set of developers. We also added an accessory port, 3DRBUS, on the bottom so that kickstarter projects, academics and businesses can easily integrate their own hardware. We developed DroneKit for use on Solo so that web and mobile developers can build businesses on top of this hardware and software. Most important, we know a great platform gets better with time, and we plan on supporting Solo for years to come.
This is the Solo Developer road map. Let us know what you think. Help us build Solo into the premiere drone platform, and the best home for developers around the world.
Comments
I too would be interested in knowing roughly how much processing bandwidth and memory is available for custom software. Also, what peripherals are on the CPU board? If my next widget can save on size, weight and power because it can piggyback on the Solo, that's a win/win in my book!
Thanks,
Kelly
Hey Rob
When you say it works with a Sony camera, does that including controlling camera settings like shutter/focus over HDMI, or does that just mean you can see live video via wifi? Just to confirm does the onboard iMX CPU control a GoPro over HDMI or over USB/WIfi interface? Also how is the latency with the Sony compared to a GoPRo?
Regards
JB
You can definitely use the HDMI with other cameras. I've used it with a Sony AS100V already.
is ADV7610 pro or industrial variant? (HDPC support only in industrial version).
Wondering why use only 2 antenna to wifi?, card natively support 3.
Very DIY friendly anyway.
From what I can tell the ADV7610 is the HDMI input receiver that connects to the GoPro HDMI port, so that the iMX board can funnel it via wifi to the ground? It should be possible to use another HDMI camera instead. I'm wondering if it uses the same HDMI cable to control the GOpro via CEC. That's if the camera supports CEC of course.
Having a HDMI input converter opens up some possibilities I suppose but also comes at a cost (latency, size and money). In the short term I hope camera manufactures adopt USB C instead. These Legacy standards should all evolve into a single digital interface that can do any data plus power at the rate required. HDMI adapters won't be required then.
I wonder what the RF output of the Atheros wifi module is?
-
Thx John for the links.
From those pictures I think that the iMX CPU and Video conversion are on completely separate PCBs, and is considerably larger than the PXH2 module itself. I was hoping it was a part of the PXH2 module....that would have been a feat. Like this I think it's probably easier to stay with a RPi or odroid board for onboard image/comms processing instead. Looks like it will perform better, be cheaper and be of similar or smaller overall size. The PXH2 is likely to be worth it though, provided they keep the price reasonable.
Might have to wait for Solo 2 then to get what I'd like to have! But I really wanted an excuse to buy one! :-(
The only interesting component inside solo is ADV7610 ... could be nice more info about it and integration to imx6 :)
And use mini pci for connect network based on Atheros chipset .. but is not a dual band ?
Solo tear down - http://www.rcgroups.com/forums/showpost.php?p=31710493&postcoun...
Is that Enrique Iglesias in the picture, adjusting the propellers?
Thx John
I'm familiar with the iMX6 CPu's. Shame they didn't go with something with a bit more grunt. There's barely a noticable pricing difference ($10-20) to get a multicore in there. Would still like to know if that is going to be released DIY and open source as well.
Do you have a link to the teardown pictures please? I can't find it on RCG. Maybe that will provide further clues.
Regards
JB
Thanks Tridge! It's been great working with you, Randy, and the rest of the dev team on things like data logging. Looking forward to making Arducopter even better on Solo and in general! Next on the docket in getting the Solo fork in closer sync with master.
-
1
-
2
-
3
of 3 Next