Open Hardware Design Considerations - aeonSolutions/AeonLabs-AI-Volvo-MKII-Open-Hardware GitHub Wiki
Main Page >> Open Hardware Design Considerations
Last change 11-02-2024
Since these "open automotive" solutions are based on "open hardware" electronics there are some design considerations to make the electronics safer when driving and also make it simple & easy to troubleshoot, debug and repair. When deploying open solutions, one of the major requirements to have, is redundancy. This means in case of failure of a particular electronic component there's a 2nd one (or more) ready to take over the one malfunctioning. Depending on safety requirements, this type of redundancy can be implemented in the same hardware electronics installed in a particular location in a vehicle (see hardware electronics of a Tesla car), or can be in a separate hardware electronics installed on a different location in a vehicle.
Another hardware design consideration is on having a separate microcontroller dedicated exclusively to CAN communication among devices installed in a vehicle and able to communicate directly to the control module's main microcontroller. By having a separate microcontroller one is minimizing the possibility of malfunction of the controller in the event of unauthorized intrusion "hacking" of the CAN bus network. To add to safety and security of all open hardware electronics proposed and available on this repository, it will use many of the functionalities, specifications and characteristics described on this ongoing scientific research paper titled "Validation of Experimental Data Origins: A Swarm of DAQ devices able to Deliver Unique Experimental Data using Blockchainโlike Fingerprint ID to a Data Repository".
๐ข 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.