Who can advise the literature on the development of a vehicle under the BC?

Question

Iron

Hello.
The idea came to me to create a digital control panel for a car with my own hands. Perhaps someone can advise literature on decoding signals from car sensors (tachometer, speedometer, oil pressure and fuel level sensors, battery charge)? Or some kind of guide for implementing something similar?

Answer 1

Start with a wiki .

Answer 2

In the general case, there are a lot of different sensors, there are also quite a few protocols. In modern cars, however, it usually comes down to CAN. There are a lot of closed things, the documentation for which cannot be found, and only traffic analysis and reverse engineering will help.
To enter this topic, you will need to shovel just a sea of ​​\u200b\u200binformation from various sources. It would be simply naive to hope for any separate guide.

Answer 3

It’s worth starting with Google the available data in the bus for your car (popular brands such as Ford, Renault, VAZ, etc. have already been opened and blocked a hundred times).
you can start for example with forums dedicated to torquepro, they usually post lists of data for different cars.
Next, you should google ready-made projects, for example, there is a home-made panel for android, you just need to select the appearance and drive in the necessary commands.
If the car is not popular and nothing has been googled, then a long method, sniffer the bus and pick out the data.
As for the control, it’s worth thinking 100 times, the wrong command or the wrong sequence of commands can easily fill up the block, so you have to run on foot for a new expensive block.
PS
In general, there are several options for obtaining data
1. Sniffer the necessary data in the bus and display it on the screen, it is safe, but not all the data is available.
2. interrogation of blocks personally, it is more difficult and dangerous, but you can pull out additional data that just does not fly in the bus.
3. switching blocks to debug mode and requesting data, probably the most dangerous option, since it is easier to break something in debug mode.