Switching from Raspberry Compute to Raspberry Zero
During the design phase of the AutoPi, it was decided to use the Raspberry Compute Module. The Raspberry Compute Module is small, versatile and expandable in a lot of ways, which suited the AutoPi project perfect. All the pinouts from the Broadcom BCM2835 processor is available through the SODIMM DDR2 interface on the Compute Module. This gave us a lot of possibilities during the design phase of the AutoPi and therefore the Compute module was an obvious choice for us as a main processor.
The status of the prototype development at that time, was that the hardware development of the AutoPi was almost done. The prototype consisted of two custom boards for internal components and functions. Together with the Compute Module, the prototype contained 3 separate PCB’s with components on both sides. The Compute Module was connected to the rest of the system through a SODIMM DDR2 connector mounted on one of the custom PCB’s. The complete system was working and we were developing software for the device and backend.
On November 26th 2015 the Raspberry Pi Foundation announced its release of their new Raspberry Zero. While we were almost complete with the design of the AutoPi with the Raspberry Compute Module, this needed further investigation. The Raspberry Zero is priced at only 5$ (4£) and just because of this it was much more interesting than the Compute module priced at 20$. Also a lot of the functions provided by our custom boards were already build into the Zero, such as HDMI and USB connection. A negative side was that the Compute Module used a build in 4GB eMMC RAM for memory, while the Zero relied on an external SD card for memory. A closer look at the specification for the Zero, revealed that all of the needed functions for the AutoPi was covered by the outputs on the Zero. The design changes needed to include the Zero was few, so it was decided to use the Raspberry Zero as main processor for the AutoPi.A full description of the final design of the AutoPi hardware platform, can be seen HERE
Other blog posts for further reading
AutoPi: Using Raspberry Pi as a Parental Control or Teen Driver Mode
Your teenage son or daughter has just received their learners permit and you are worried about them being mature and responsible enough to use your vehicle or maybe you have friends who are irresponsible and terrible drivers. One way to ease your worries is in how AutoPi uses Raspberry Pi to make your car a carputer, basically having a computer within your car, where you can set-up limits and settings in order to control your vehicle in a Teen Driver Mode or as a Parental Control.
How-to build a Raspberry Pi touch screen car computer
Integrated car computers are not only for expensive cars like the Tesla Model X nor is it only for complex car DIY projects that require you to have a degree in engineering. Not many people know how easy it is; by combining a few components it is possible to make it for any car. Follow this guide to see how it can be done.
Fleet Management: Use your AutoPi to manage multiple vehicles
Fleet-sharing is not a new phenomenon, from small and big companies, like UPS, to government and state organizations, like the postal service, have all had corporate vehicles given out to their employees as part of their ‘fleets’. These vehicles are corporate or governmentally owned and thus the fleet of vehicles differs from trucks and vans for the postal service to sleek, electric and modern vehicles for corporations with a variety of options whereas the postal service is all uniformed and equally the same vehicles.