Did you disconnect your battery before doing all that work? OR Did you plug back everything before you plug in battery?
You might have triggered a DTC (diagnostic trouble code) while you were playing around with the stereo. You can try to reset the computers in the car by disconnecting the battery for a few mins. Disconnect BOTH battery (POSITIVE AND NEGATIVE)...then contact both of them for 2 mins or so.....MAKE SURE THAT BATTERY IS COMPLELETY DISCONNECTED OR HELL MIGHT HAPPEN! BOTH WIRES OUT! Good Luck! If not, you can come by my place and i'll clear the code for you..i have a OBD 2 scanner.
Hi guys,
I hope the stereo installer did not tap into any of the security wires from the stock system.
I doubt that this will problem register within the OBD2 system. You can try to scan it, but I am doubtful, you will see any codes.
There is only 4 codes:
B2795, B2796, B2797, B2798 related to the security light. If you are able to scan these in an OBD2 code reader.
If the old stereo system, was in place, it reads out its own diagnostic codes on the actual stereo display LCD.
The security light is part of the immobilizer system, and constant "On" means to check a few areas.
The best advise is to try and reset the ECM, by disconnecting the battery. If the light returns to a constant on, then check to ensure unplugged wiring harness's are not grounding out on the frame. This can occur at the Amp, ECM or the old stereo harness.
This Security light warning symptom can also indicate a problem with the key transponder coil and how it communicates with the ECM.
This is not a check engine light, it is the security light...correct?
This may require a special scan tool, from the dealer to properly diagnose it. Kind of like airbag codes - a standard OBD2 tool will not read these.
Hope it is something simple, that unplugging the battery will solve. Let us know the result, for future people that encounter the same issue.
Digger08
Oh yeah...check all of your vehicles entry points, Trunk, doors and hood, as well as interior light...as this could potentially cause a code fault as well.