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
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.
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.
Speak to your car with Google Assistant - almost like K.I.T.T. from Knight Rider
Wouldn’t it be cool if you could speak to your car and give it commands? We remember our childhood in the last millennium where Michael Knight (David Hasselhoff) and his intelligent Pontiac Trans Am named K.I.T.T. solved crime together. While we may not be able to have a meaningful conversation with our car just yet, it’s now a possibility to talk to your car and give it commands to execute. We are here giving a short introduction to how this can be accomplished using the AutoPi.io system and Google Assistant.