Other Open Volvo Projects - aeonSolutions/AeonLabs-AI-Volvo-MKII-Open-Hardware GitHub Wiki
Main Page >> Other Open Volvo Projects
Last change 08-02-2024
Volve by Luuk Esselbrugge
Volvo CAN BUS extender based on ESP32. This code is experimental and contains experimental functionality in the "data and command" serial commands. For example getting speed, rpm or sending car unlock commands might not function as intended on your Volvo right now.
Volvo-CAN-Gauge by Evan Horsley
Reverse engineering the Volvo VIDA protocol to gather diagnostic information not available via OBD2 on Volvo cars. Modified by evy0311 and started by Alfaa123.
Volvo-CAN-Gauge by Alexander Elder
Reverse engineering the Volvo VIDA protocol to gather diagnostic information not available via OBD2 on Volvo cars.
Volvo CANBUS tinkering by Steve's Inventions
The CAN network on a Volvo β part three β request message format by
There are basically two main types of messages: requests and responses. This post will zoom in on request message. And I introduce a new module ID, 000FFFFE. This, in my car, is the generic ID for sending and receiving diagnostic messages, so the ID you will use to query your car on sensor values and other parameters. Very useful, and most likely the ID you will be using most.
S60CAN by AndrΓ©
An adaptation of SardineCAN: The code-base for this is in github.com/hackingvolvo, thanks to Olaf @ hackingvolvo.blogspot.com. The reason I started this version is because of the DPF (soot filter) and regeneration issues. The goal is to provide the driver with a simple feedback whenever the car is regenerating its DPF. The driver can then make the decision to keep on driving and let the process finish, or to cut the process short and run the risk of eventually getting messages such as: "Emissions problem. Service required" "DPF full. Regeneration required"
Volvo-VIDA by Tigo
Reverse engineering Volvo VIDA for retrieving information from the CAN-bus. With the files in this repository, a lot of information buried deep inside VIDA can be easily exported. It's also possible to read Diagnostic Trouble Codes (DTCs)!
SardineCAN-Arduino by Olaf
This is Sardine CAN, an open source J2534 device, which makes it possible to connect various diagnostic programs (eg. VIDA from Volvo) to your car.
SardineCAN-Win32 by Olaf
This is Sardine CAN, an open source J2534 device, which makes it possible to connect various diagnostic programs (eg. VIDA from Volvo) to your car.
π’ 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.