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
Saving your car interior on a hot day - Making a cabin overheating protection system using AutoPi
Studies show that on a hot summer day the temperature inside your vehicle will rise dramatically within just 10 minutes after you parked. HeatKill.org reports that with an outside temperature of 27 C (80 F), the inside temperature could rise to as high as 37 C (99 F) after just 10 minutes. The inside of your car becomes an oven roasting your interior. The sun will permanently damage the color and look of everything it touches, thereby degrading the value of your car.
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.
Raspberry Pi Dongle: How to Read and Reset Fault Codes From Your Vehicle
The AutoPi IoT platform is much more than your regular OBD-II dongle. But that doesn’t mean that it isn’t able to perform all of the same things a regular OBD-II dongle does (plus much more). One of the common things you would do is to read out details about fault codes in your vehicle. In this blog we will go over the details on how this is done with the AutoPi and how you can combine fault codes with triggers to make automatic alerts.