View Single Post
  #928  
Old 06-22-2009, 08:33 AM
longassname's Avatar
longassname longassname is offline
Just some dude.
 
Join Date: Sep 2002
Location: Miami, FL
Posts: 3,986
Significant Technical Input
Re: Memory dump of ECU

The bitmaps are for switches which can be i/o or just used internally. Actually, there are a few loop flags included in these bitmaps but I didn't include them in the documentation.

Here, I'll explaint he first one:

(FA0 78105A00):FA0 is the select monitor label for this bitmap. 78105A00 is the command sent to the ECU to read the memory location of the bitmap.
(IG=ignition 08): IG is the select monitor label for the bit indicating the ignition switch is on or off. 08 is the hexidicimal number matching the bit. In binary it is 00001000
(AC 02): Is the bit for the AC being on. In hex it is 02. In binary it is 00000010
(ID=idle 80): Is the bit indicating that the throttle is fully closed. In hex it is 80. In binary it is 10000000.
(AP=AC Pressure 20): Is the bit indicating that the pressure threshold for the trinary switch has been met. In hex it is 20. In binary it is 00100000
(NT=neutral 01): Is the bit indicating the selector lever is in neutral. In hex it is 01. In binary it is 00000001.
(PS=Power steering 10): Is the bit indicating that the power steering is under load. In hex it is 10. In binary it is 00010000.


So the bitmap we are calling FA0 is a single hex byte being read from the ECU. A byte is 8 bits, any or all of which can be 0 or 1. By looking for where they are read or set in the code you can find the code blocks that do things of interest. Sometimes they are copied and is the copy that is checked but usually bitmaps are checked directly and more importantly you look for where they are set with bit sets and exclusive ors.
Reply With Quote