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
Subscribe to our newsletter
Don’t worry, we’ll only send you the best stuff - no spam
Or follow us here
Other blog posts for further reading
How to easily add remote theft detection to your car
Your car is a valuable and expensive asset. Even with full insurance a car theft can be a cumbersome and expensive affair. But how can you help prevent theft of your car and possibly avoid an increased insurance premium? In this blog post, we explorer the possibilities to get remote theft detection, using the AutoPi platform.
Discover hidden functions in your car (using CAN bus sniffing)
All modern vehicles today is controlled by multiple Electronic Control Units (ECU), which you can think of as small computers controlling all electrical components in your car. Using the OBD-II port and an AutoPi it is possible to communicate with the ECUs. One of the ECU’s is called the Engine Control Module (ECM). This is responsible for communication with a lot of subsystems, like transmission, power steering, windows and doors. These subsystems communicates on a network bus called Controller Area Network (CAN), by broadcasting messages on the bus.
What is AutoPi and What Does It Do?
Get a short introduction to how AutoPi works and what it does for you. We will cover some of the technical details but also give a brief overview of the use case scenarios for this IoT device, like theft detection and remote safety monitoring. Get a felling of the AutoPi IoT platform and hardware dongle.