OPEN ECU Hardware Specifications - aeonSolutions/AeonLabs-AI-Volvo-MKII-Open-Hardware GitHub Wiki
Main Page >> ECU >> OPEN ECU Hardware Specifications
Last update 12-12-2023
This page describes all hardware specifications for the 12-2023 revision. To goto to the Smart DAQ repository where the KiCad Files are, click here.
To run the main electronics and engine management I'll be using EspressIF Systems ESP32 C3 microcontroller a single core Xtensa LX7 Core Processor running at 160MHz with 400Kb RAM and of 4MB PSRAM. This microcontroller serves the purpose of CAN communications with other hardware electronics in a vehicle and relays validated data to the main microcontroller. It has wireless radio capabilities that are disabled on the hardware electronics itself for safety concerns. Instead, the hardware include an optional chip for wireless connectivity that needs to be enabled first, for instance, by a mechanic, to enable wireless communications directly with the ECU. The main MCU, the MK64FX512VMD12 from NXP, is a Kinetis® K64 MCU, Based on Arm® Cortex®-M4 Core, running at 120 MHz and it has 256KB of SRAM (also found on the Teensy 3.5). This is the main MCU that is responsible to do real-time engine management of a vehicle. The first hardware revision will be made to fit engines with up to 8 cylinders with an option to run bi-fuel systems such as LPG, each with its own engine map configuration. In regards to safety against theft the electronics will include a cryptographic IC that will be used to match the car owner VIN number and with all other open hardware electronic components installed on a vehicle. In practical terms this means, in the event of theft, to make a specific open hardware work on another vehicle, it will require replacement of the main microcontroller processing unit without the need of specialized tools and equipment.
-
BGA MK64FX512VMD12 from NXP for the Engine Management System
- Kinetis® K64 MCU, Based on Arm® Cortex®-M4 Core, running at 120 MHz
- 256KB of SRAM
-
QFN Xtensa LX7 Single Core Processor running up to 160MHz for CAN BUS communications
- RISC V ultra-low power co-processor
- 400Kb RAM
- 4MB PSRAM;
- wireless connectivity disabled on the hardware;
- Authentication & Security:
- SOIC-8 ATSHA204A SHA-256 high-security hardware authentication IC for secure and unique data exchange among CAN BUS devices
- Power management
- DFN-6 AUR9718/ST1S09 high efficiency step-down 3.3V 1.5A DC converter;
- Onboard sensors used mainly for secure CAN BUS data communications
- BMP280 Atmospheric Pressure Sensor
- ENS160 TrueVOC sensor;
- DFN-8 AHT20; temperature sensor with a precision of 0.1 C;
- DFN-8 AHT20 humidity sensor;
- LGA-14 LSM6DS3 a 6-axis accelerometer and gyroscope;
- Connectivity
- CAN BUS
- USB-C serial communication, standard 5.0V DC USB-C connector, max 1A
- Serial UART communication
🟢 Fully tested and working
A green circle means the hardware electronics or the programming code was fully tested, each of its functionalities and capabilities. And it can be installed in a vehicle. Keep in mind this does not mean errors won't happen. As in everything related to electronics and software, there are revisions and updates. This open hardware is no different.
💯 Fully tested & working, no improvements necessary - already being sold online
🆓 Fully Open hardware \ source code
🤪 There's better than this. don't use it
🔐 Fully closed hardware \ source code
⚡️ fully tested and working, however, it is a dangerous solution to deploy
🟡 Not tested. Working capability is unknown, it may work or not.
A yellow circle means the hardware electronics or the programming code was not fully tested, each of its functionalities and capabilities. This does not mean it not working, it simply means testing is needed before giving a green circle of approval.
🔴 Fully tested but not working.
A red circle means the hardware electronics or the programming code was fully tested, and found some kind of critical error or fault. This means the electronics or firmware code cannot be used in a vehicle.
⌛ Not started.
The hourglass means the hardware electronics or the programming hasn't started. Most likely because is waiting for the necessary test components needed for reverse engineering and also engineering of the new open solution.
🆕 New updated contents
The new icon means the link next to it was recently updated with new contents
💬 Comments on the Discussion page
The comments icon means there are useful and even new comments on the discussions page of the repository important for what you are seeing or reading.
Join the beta program to test and debug to provide feedback, ideas, modifications, suggestions, and improvements. And in return, write your own article blog, or post on social media about it. See participation conditions on the Wiki.
The Beta Participant Agreement is a legal document being executed between you and AeonLabs that outlines the conditions when participating in the Beta Program.
Bug reports and pull requests are welcome on any of AeonLabs repositories. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the code of conduct.
- Contributing
Please make sure tests pass before committing, and add new tests for new additions.
You can get in touch with me on my LinkedIn Profile:
You can also follow my GitHub Profile to stay updated about my latest projects:
The PCB design Files I provide here for anyone to use are free. If you like this Smart Device or use it, please consider buying me a cup of coffee, a slice of pizza or a book to help me study, eat and think new PCB design files.
Make a donation on PayPal and get a TAX refund*.
Did you like any of my PCB KiCad Designs? Help and Support my open work to all by becoming a GitHub sponsor.
Before proceeding to download any of AeonLabs software solutions for open-source development and/or PCB hardware electronics development make sure you are choosing the right license for your project. See AeonLabs Solutions for Open Hardware & Source Development for more information.