Bad Engine Computer Data
Thread Starter
|
New Member
Joined: May 2016
Posts: 2
From: Provo, UT
Bad Engine Computer Data
Hey everyone,
Whilst driving a long distance drive, the dash was showing random different engine light errors. There were two that I observed but was unable to replicate.
1. The ABS and E-brake lights were on, and the green "D" (drive gear as opposed to "N", "S", or "P") light was flashing indicating I was driving with the e-brake engaged. I checked the e-brake and pulled it up slightly then down to see if it was engaged. It wasn't engaged at all. I pulled over as well and exercised the E-brake a few times to see if it would clear. It didn't. Even when I switched the car from Drive into Park, it still indicated that it was in Drive and the green "D" continued to flash even after pulling over and coming to a complete stop.
2. on two occasions, the speedo dropped out completely while the car was moving. This also led to a check engine light coming on (I was unable to get the engine light as I was driving at the time). And the cold engine light came back on. None of these were true as the engine was warm because we'd been driving it for 6 hours at that point on the highway.
3. I do use an UltraGuage that is wired and plugs direct into the OBD2 port. I've noticed for the past week that sometimes going over bumps will cause the Ultraguage to lose connection to the engine computer despite the connector not coming lose. When the E-brake lights came on, the UltraGuage lost connection and was never able to reconnect, despite the UltraGuage plug being properly connected to the ODB port still.
Also note: I didn't notice any change in engine performance. ie didn't hear any changes in how the engine was running, so there was no initial indication that the computer wasn't getting O2 data or other sensor data to cause it to run too rich/ lean. Once the utraguage did reconnect, all the data it was showing me seemed good. Throttle positions, O2's etc. They basically tracked what i expected. O2's changed with acceleration/ deceleration, throttle positions were tracking as well.
My initial thoughts are that there may be a bad circuit or relay, which I plan on checking in the next day or so.
However, I would guess a short in the system or an aging/ dying computer could also be at play.
Any other thoughts of what to check?
Thanks.
Whilst driving a long distance drive, the dash was showing random different engine light errors. There were two that I observed but was unable to replicate.
1. The ABS and E-brake lights were on, and the green "D" (drive gear as opposed to "N", "S", or "P") light was flashing indicating I was driving with the e-brake engaged. I checked the e-brake and pulled it up slightly then down to see if it was engaged. It wasn't engaged at all. I pulled over as well and exercised the E-brake a few times to see if it would clear. It didn't. Even when I switched the car from Drive into Park, it still indicated that it was in Drive and the green "D" continued to flash even after pulling over and coming to a complete stop.
2. on two occasions, the speedo dropped out completely while the car was moving. This also led to a check engine light coming on (I was unable to get the engine light as I was driving at the time). And the cold engine light came back on. None of these were true as the engine was warm because we'd been driving it for 6 hours at that point on the highway.
3. I do use an UltraGuage that is wired and plugs direct into the OBD2 port. I've noticed for the past week that sometimes going over bumps will cause the Ultraguage to lose connection to the engine computer despite the connector not coming lose. When the E-brake lights came on, the UltraGuage lost connection and was never able to reconnect, despite the UltraGuage plug being properly connected to the ODB port still.
Also note: I didn't notice any change in engine performance. ie didn't hear any changes in how the engine was running, so there was no initial indication that the computer wasn't getting O2 data or other sensor data to cause it to run too rich/ lean. Once the utraguage did reconnect, all the data it was showing me seemed good. Throttle positions, O2's etc. They basically tracked what i expected. O2's changed with acceleration/ deceleration, throttle positions were tracking as well.
My initial thoughts are that there may be a bad circuit or relay, which I plan on checking in the next day or so.
However, I would guess a short in the system or an aging/ dying computer could also be at play.
Any other thoughts of what to check?
Thanks.
Thread
Thread Starter
Forum
Replies
Last Post
