Autopilots

Autopilots

Paparazzi Autopilots Hardware support for Autopilot versions currently in use. One of the great advantages of Paparazzi is support for multiple hardware designs. Historically, Paparazzi was based around ATMega MCUs, while current autopilots are designed around two primary processors: STM32 series microcontrollers LPC21xx series microcontrollers There are active and current autopilots designs using both architectures. Not all autopilots have the same capabilities, peripherals or features, but each has advantages in different applications. The STM32 architecture is relatively new. Currently, boards are designed around the STM32F1 series, but there is future upgrade path capabilities to the F2 and F4 series, giving way to feature rich processors with a variety of peripherals and speeds. Architecture-dependent firmware code is supported in part by libopencm3. The Lisa autopilots use the STM32. The LPC21xx based boards use the LPC2148. This architecture is more mature, but also more limited in peripherals and speed. The Tiny series, Booz, TWOG, YAPA and Umarim autopilots all use the LPC2148. Some autopilots have also been designed for close integration with small single-board computers, particularly those based on OMAP processors such as the Gumstix Overo series. The Lisa/L and Classix boards are designed with this in mind, though other autopilots can be easily interfaced. Further information can be found here. When will the Schematics, CAD files, Gerber files, BOM be released? The hardware development and release process. 8 June 2011 13:25:47 Antoine Drouin wrote on the mailing list: Schematics will be released ASAP, CAD files will come later. When ? I don't know.... Worst case would be when Joby Robotics releases a new version of the board, but I hope it will be sooner than that. Lisa/L CAD files have been released (http://svn.savannah.nongnu.org/viewvc/paparazzi-hardware/trunk/lisa/v1.1/?root=paparazzi ) 3 month ago. (...) I've started this project together with Pascal 8 years ago and since then I have dedicated my time to try and make it successful. I'm utterly convinced of the benefits of open source, but observing how Paparazzi grew over time, I came to the conclusion that hardware is a bit different than software... "gcc tiny.brd" is not going to make a board magically appear on your desktop. I'll list here some of my arguments in favor of releasing CAD files after the board is mature. Unlike software, where an unskilled user can type make and get a piece of complex software to successfully build, assembling hardware requires tools and skills. Providing gerbers and BOM have lured a bunch of new users into believing otherwise and has created tons of frustration. I've myself fixed a number of badly assembled boards and I even recall that while helping debugging a board (so after assembly), discovering that the person had manufactured two layers PCBs instead of four layers. As the technology of the autopilot increases, this problem becomes more and more important. The success of the project depends on the availability of affordable hardware. The price of hardware is directly and exponentially dependent on the number of manufactured units. If ten persons manufacture 10 boards each, the cost will be much higher than if one person manufactures 100. Last and not least, the quality of assembly also depends very much on the number of manufactured units. Good quality can only be achieved through the use of automated placing and soldering, and those processes can only be used if the number of units reach a certain amount.