FAQ ‐ Frequently Asked Questions - aeonSolutions/AeonLabs-AI-Volvo-MKII-Open-Hardware GitHub Wiki

Main Page >> Frequently Asked Questions

Change language
Last update 16-12-2023

Which cars do you plan to develop code for first? by David Cherry
I'm starting with a Volvo MKII . However, this is an open solution, meaning the pcb layout can be redesigned to fit any other car.

Where do you find the protocols to send messages to other modules (like the ignition control module)? by David Cherry
If you Google "EOBD protocols" you will find them all... or , alternatively, write ✍️ your own ... The requirements are ability to exchange messages and more importantly do it safely ... for the latter I have to recommend reading all EOBD protocols from any car brand and also google any other clue on how to increase the safety in communications among devices in a vehicle. On my repository you will find one or two ....

How will you go about insuring the vehicle, surly any insurer will view this like the worst kind of modification. Should you have an accident couldn’t a third party insurer blame the none stock electronics, being most of these updates cut right across the safety aspects of the vehicle design? Without the manufacturers ultra expensive safety checks done on the standard modules and vehicle. by Paul de Luca
You are all correct 💯 except in one key assumption. That this open ECU is intended for modifying a car. It can be , however , the main motivation for this project is to prototype open hardware electronics capable of replacing proprietary , original electronics from a manufacturer with the exact same functionality. Insurance will love it. So will the vehicle owners! With cheaper , repairable hardware electronics.

even with the same functionality programmed in, would that still need to be proven to be the case in order for insurers to accept that position? Also how could you prove it is the same, just playing devils advocate on how the insurers will view this. In a world run on rules and regulations. You would likely have more of a chance of them accepting it if the hardware was fixed rather than open to modification once installed, and you had the hardware and code proven to offer a verbatim level of performance v the original part, also let’s not forget reliability playing a part. by Paul de Luca
That's the main advantage of an open solutions over closed 🔒 , with IP protection devices, on this case the device is an open ECU. And since the hardware electronics and also the firmware source code is openly availability on GitHub, it can be used and viewed not only by insurers but also it can be viewed , and used, by the authorities on they daily work patrolling the roads ... In the end, safer driving conditions and safer policing.


Have a question to ask and in need of an answer?
You can do it here on GitHub, on the discussions page , on Twitter and on LinkedIn on any of my publications about this open project.

⚠️ **GitHub.com Fallback** ⚠️