Forgive my insolence if it sounds like i dont know what im talking about/not using the right terminology. i apologise and welcome corrections.

I am looking for any kind of documentation to help with ECU interrogation via K-Line. i understand there is `Alfaobd` and `MultiECUScan` for reading this particular ECU. i have built a K-line Sniffer, and documented areas of interest.

The golden unicorn egg would be to find Bosch documents for the above ECU. outlining hex addresses and what those addresses hold. I think this is called a DAMOS/A2L file?

heres what i would like to find.
- Info that marries Hex request/return to human readable "actual values", along with how the Hex is structured and what min/max values would be valid for any given string.
for instance
This is RAW hex request for RPM value and a return from the ECU. in this case it is reporting 0RPM

Code: Select all

Request frame (6bytes): 1F 07 07 6F 06 05
Return frame (8bytes): 0F 07 07 4F 06 00 00 3A

i believe the last 3 are "RPM Values" as these change dependant on engine speed... an idle of approx 690RPM gives `3F 04 01` at the end of the return frame. id like to marry these up with exact numbers.

- Info regarding plausible DTCs for the ECU and the description/state of the DTC

- Info on how to find hex codes that may/may not hold other component states over & above what the 2 pieces of software (mentioned above) can see.
in particular i would like to find the actual "on/off" status of the VIS Solenoid, AC Compressor, Stage 1 and Stage 2 fan speeds. these are available as "Actuations" but not "actual values" in the above software.


I hope this makes sense

Bosch P/N 0 261 204 271
Fiat P/N 46753404