ForeverCar
Senior Member
- Thread starter
- #106
Besides software and hardware, I think it's important to have a pretty good foundational understanding of the mechanical aspects, the physics, and control system theory as well.
The software side is also likely very different than what you are used to (speculating on my end from what you have listed). At the highest level, you might get to work with C-like programming languages. However, syntax is just a minor aspect. The concepts usually are much lower level and close to the hardware.
On the hardware side, getting comfortable with the basics of how binary code executes on a simple architecture is a good place to start.
To get a taste of this, I would suggest looking into the CAN bus and understanding how 2 wires can communicate data between modules. From there, see if you are comfortable figuring out how to go from raw CAN captures to meaningful messages.
Granted, I am still very early in my own journey so this is my own speculations at this point. I have only started to look at the binary file with WinOLS. Just looking at raw binary file and using pattern recognition to identify "maps" is pretty basic and suboptimal for what I want to accomplish so I might jump down the reverse engineer the code route to see if I can get a more comprehensive understanding of the control code.
The software side is also likely very different than what you are used to (speculating on my end from what you have listed). At the highest level, you might get to work with C-like programming languages. However, syntax is just a minor aspect. The concepts usually are much lower level and close to the hardware.
On the hardware side, getting comfortable with the basics of how binary code executes on a simple architecture is a good place to start.
To get a taste of this, I would suggest looking into the CAN bus and understanding how 2 wires can communicate data between modules. From there, see if you are comfortable figuring out how to go from raw CAN captures to meaningful messages.
Granted, I am still very early in my own journey so this is my own speculations at this point. I have only started to look at the binary file with WinOLS. Just looking at raw binary file and using pattern recognition to identify "maps" is pretty basic and suboptimal for what I want to accomplish so I might jump down the reverse engineer the code route to see if I can get a more comprehensive understanding of the control code.
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.
Sponsored