Hardware Electronics "Car Key" - aeonSolutions/AeonLabs-AI-Volvo-MKII-Open-Hardware GitHub Wiki
Main Page >> Security & Theft >> Hardware Electronics "Car Key"
Last update 24-04-2024
An important feature of all hardware electronics being designed and prototyped is the personal "CAR KEY". This is a customizable and programmable nano sim card that has stored a custom token access key up to 256 bytes. This access key is also present on any other module of the car and is constantly verified and checked for changes.
This security feature allows adding hardware electronics and modules only by the owner of the car and with the access key. A mandatory requirement for those who love their cars and also "Do it Yourself" #DIY type of electronics. The nano sim card can be programmed using the "CAR Key" Device connected to a smartphone, tablet, or Laptop computer. (more information about this soon). All control modules need to have installed a nano sim card with a "Car Key" defined by the owner of the car or else the module won't work. Any installation of unauthorized hardware electronics and modules will not be able to execute commands on the communications network and can disable normal operation and running of the car.
It is not possible to update/ change a "Car Key" remotely or using the vehicle's communications network. The only way possible to update or change a "Car Key" is by physically removing the nano sim card from each module and then programming it using a compatible "Car Key Device" and software App.
Another important function of this "Car Key" is in the ability of a car owner to change, frequently, for instance, it can change every day, how radio frequency operates and wireless access happens to his/her vehicle when using the Key Fob to open or start the car. This nano sim card is also installed on the "Key Fob" that opens and starts the vehicle and is frequently subject to wireless attacks and hacking. By having an easy-to-replace customizable access key, the owner is able to change how the vehicle is wirelessly connected, making life harder for thieves and curious unauthorized people looking to get inside.
- the ability of a car owner to change, at the end of the day, how the radio frequency operates and wireless access is made when using a Key Fob
- Enables installation of custom control modules and even DIY control modules only by the owner of a vehicle
- The "Car Key" cannot be updated, or change, using the control module where is installed
ðĒ 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.