PDA

View Full Version : Default Cadillac SRX 2006 Theft Deterrent Module problem



aassfour
1st October, 2013, 09:36 PM
need help with this one,
it was a lost key situation when the owner of this Cadillac took the car to an electrician donno wt he did but he didnt manage to do anything. after a while the owner found the lost key when he went to run the car it didnt run, the electrician told the owner to do these normal procedures manual learn key which takes about 30 minutes , the car runs after this process only once.
so he brought the car to me and i thought it was transponder problem so i programmed his key plus a new one which took 12 minutes on MVP pro and the same the car runs only once ,after it shows u on the screen : Starting Disabled Remove Key (33)
i checked the theft deterrent module on my scanner it gave me this FAULT : B1007 EEPROM WRITE ERROR.
I ve searched a lot about that DTC and i found nothing . wt is this fault and why did it happen ? is the module corrupted ? anyway to fix this issue without changing the module ?
cheers thx

qubits
1st September, 2015, 07:54 PM
This is probably too late, but for other people who are having the same problem, This is from the manual:
Conditions for Running the DTCThe module runs the program to detect an EEPROM write error. The only requirements are battery positive voltage and ground. This program runs even if the battery positive voltage is out of the valid operating range.
Conditions for Setting the DTCThe module writes information to a data block in the EEPROM. The module then reads the data and compares it to what was sent to the data block. If the data does not match after 3 consecutive attempts, the module sets the DTC.
Action Taken When the DTC SetsThe module writes to another area of the EEPROM, this becomes the new permanent area to store the data. The data location is allowed to change until all of the available EEPROM is used. If a DTC B1004 is also set, the module reverts to base operation values programmed for those blocks of data that have failed. The blocks of data that have not failed the checksum test are not affected.
Conditions for Clearing the DTC

A current DTC clears when the malfunction is no longer present.
A history DTC clears when the module ignition cycle counter reaches the reset threshold, without a repeat of the malfunction

qubits
1st September, 2015, 07:57 PM
Basically if scanner doesn't clear the code, then you're supposed to replace the module.
I would make sure the battery has a good charge, then disconnect the module and reconnect. And try to erase the code.
If that doesn't work, replace the eeprom if you don't want to replace the whole module.

Meat-Head
1st September, 2015, 08:04 PM
Cool, try filling EEPROM with 00 then try code key .

tgen cut and cut into orginal dump, see if she do run run or not