optronix
Senior Member
This sounds amazing. Seems like you're at least a step or two ahead of me from a software development/reverse engineering background perspective but I'd love to go down that rabbit hole as well. If you happen to have a good handful of resources that would allow me to catch up on researching automotive software engineering, I've been looking for an opportunity to get into that. I honestly don't even know where to start... I've got a ton of resources for web/full-stack/cloud/ai/data analysis, etc. but car-specific stuff I guess that's just a sphere of influence I'm not plugged in to.Eventually, I will likely play with Hondata. However, I prefer a first principle approach and have start my learning journey. I have a pretty ambitious vision so we will see how far I can get.
Of course, I dream that our platform is open. Imagine being able to get the ECU specifications, download all the firmware code, being able to build new firmware using reasonably high level programming language, and log any parameters at high frequency (limited by hardware only).
I am torn between 2 paths. Path 1 is reverse engineer the CAN bus messages and run Motec M142 with custom firmware build. Path 2 is reverse engineer the Bosch ECU. Of course, path 3 is wait for Motec to release a PnP version and path 4 is use Hondata.
Since my priority is different, my path is likely different than others. I prioritize learning and I enjoy this kind of activities. So far, I am using WinOLS to look at our ECU binary. Next step might be to reverse engineer the code. Of course, this is very much jumping into the deep end. Let's see how it goes!
Sponsored