Usually this would set a BCM code, but even the best hardware self-checks are not fail-proof. If there was a write to the PROM in progress when the system went offline, it may well have written extraneous bits that are now causing unpredictable behavior. Killing the engine is not one (unless it is related to the security system somehow) but need to start somewhere and the engine problem may well be coincidental and unrelated.Įdit to add: reading back to the first post, I wonder if symptom that caused loss of instruments may have sligtly corrupted the BCM EEPROM. It may be your BCM EEPROM is corrupted which can cause several unpredictable problems. Now, there may be other possible causes of this problem but I wanted to mention this since it is not likely to be something you'd usually think about when troubleshooting. Section 8D of the FSM covers this, and there are three option content parameters that can be changed. Apparently the BCM output used for fog lights on the Reatta is used for another purpose (courtesy lamps?) on a Riviera and when not programmed for the correct car, still enables that output based on what car it "thinks" it is in. The foglights illuminated with the doors open, and discovered that reprogramming the option content to match the car (Reatta in this case) stopped that from occuring. I ran into this once when swapping in a used BCM from a Riviera (and using the PROM that was in it). If the fog lights are lighting with the door(s) open, double check your BCM option content.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |