Trouble codes P1000, P460
Thread Starter
|
Senior Member
Joined: Feb 2001
Posts: 496
Likes: 0
From: Chicago Burbs
Trouble codes P1000, P460
I scanned my '01 Scab 5.4 for the first time in a while and while the MIL was not on, it did have these codes in memory.
The P1000 was listed as a Manufacturer Specific Powertrain code and the P460 as a Fuel level indicator.
There is nothing wrong with fuel gauge as far as I can tell and other than a slightly rough idle, the powertrain seems fine.
There is a Superchip and TransGo shift kit in it for over a year. Anybody have any ideas?
The P1000 was listed as a Manufacturer Specific Powertrain code and the P460 as a Fuel level indicator.
There is nothing wrong with fuel gauge as far as I can tell and other than a slightly rough idle, the powertrain seems fine.
There is a Superchip and TransGo shift kit in it for over a year. Anybody have any ideas?
Technical Article Contributor
Joined: Dec 1997
Posts: 9,417
Likes: 11
From: Windsor,Ontario,Canada
Chidiver,
Don't worry about the P1000. Did you disconnect the battery receintly? It is stored when the OBDII monitors failed to complete. P1000 - Monitor Testing Not Complete. The DTC does not need to be cleared from the PCM except to pass an inspection/maintenance test.
P0460 - Fuel Level Sensor Circuit Malfunction: The PCM monitors the fuel level input (FLI) circuit for electrical failure. The test fails when the signal moves outside the minimum or maximum allowable calibrated parameters for a specified fuel fill percentage in the fuel tank.
Causes; Empty fuel tank, Fuel pump (FP) module stuck open, Incorrectly installed fuel gauge,
Damaged instrument cluster, CASE GND circuit open, FLI shorted to VPWR, Damaged PCM,
Overfilled fuel tank, Fuel pump (FP) module stuck closed, Damaged fuel gauge, FLI circuit open, FLI circuit shorted to CASE GND or PWR GND, CSE GND shorted to VPWR.
Regards
Jean Marc Chartier
Don't worry about the P1000. Did you disconnect the battery receintly? It is stored when the OBDII monitors failed to complete. P1000 - Monitor Testing Not Complete. The DTC does not need to be cleared from the PCM except to pass an inspection/maintenance test.
P0460 - Fuel Level Sensor Circuit Malfunction: The PCM monitors the fuel level input (FLI) circuit for electrical failure. The test fails when the signal moves outside the minimum or maximum allowable calibrated parameters for a specified fuel fill percentage in the fuel tank.
Causes; Empty fuel tank, Fuel pump (FP) module stuck open, Incorrectly installed fuel gauge,
Damaged instrument cluster, CASE GND circuit open, FLI shorted to VPWR, Damaged PCM,
Overfilled fuel tank, Fuel pump (FP) module stuck closed, Damaged fuel gauge, FLI circuit open, FLI circuit shorted to CASE GND or PWR GND, CSE GND shorted to VPWR.
Regards
Jean Marc Chartier
Thread Starter
|
Senior Member
Joined: Feb 2001
Posts: 496
Likes: 0
From: Chicago Burbs
Thanks JMC,
The P460 code seems to come and go so I'll keep an eye on it. I suspect that it may be tied into the Viper alarm/remote start somehow.
I had not disconnected the battery in months until today when I tried to clear the P1000. P1000 still there but no MIL.
One other thing is the AutoXray got the most recent updates a couple of days ago so it is possible there is a bug in the programming.
E-fans coming from Mike on Monday so the scanner will be out again shortly.
Thanx again,
Larry
The P460 code seems to come and go so I'll keep an eye on it. I suspect that it may be tied into the Viper alarm/remote start somehow.
I had not disconnected the battery in months until today when I tried to clear the P1000. P1000 still there but no MIL.
One other thing is the AutoXray got the most recent updates a couple of days ago so it is possible there is a bug in the programming.
E-fans coming from Mike on Monday so the scanner will be out again shortly.
Thanx again,
Larry
Thread Starter
|
Senior Member
Joined: Feb 2001
Posts: 496
Likes: 0
From: Chicago Burbs
Update
It seems that the scanner is not happy since the updated firmware. It skims over most things now with a "not completed" message. Have to check on possibility of reverting to older firmware.
Maybe the Superchip and AutoXRay just don't get along anymore. I reran the update and got the same resullt. I'll try pulling the Superchip to find out.
Funny that AutoXray just sent me an upgrade offer in the mail for the new CAN software or scan tool 2 days before I run into problems.
Still getting P1000 code but now think it is a firmware problem in scanner. To be continued.
It seems that the scanner is not happy since the updated firmware. It skims over most things now with a "not completed" message. Have to check on possibility of reverting to older firmware.
Maybe the Superchip and AutoXRay just don't get along anymore. I reran the update and got the same resullt. I'll try pulling the Superchip to find out.
Funny that AutoXray just sent me an upgrade offer in the mail for the new CAN software or scan tool 2 days before I run into problems.
Still getting P1000 code but now think it is a firmware problem in scanner. To be continued.
Last edited by ChiDiver; Jul 20, 2003 at 04:38 AM.
Thread Starter
|
Senior Member
Joined: Feb 2001
Posts: 496
Likes: 0
From: Chicago Burbs
Update on the Update.
On the AutoXRay EZ-Link scanner, firmware revision rtv226_2.jcb turned out to be the problem. When I reverted back to the rtv224_2.jcb firmware my trouble(codes) went away.
Just a heads up in case there is one more of these scanners in the western hemisphere.
Now where was that compulsive/obsessive thread at again?
On the AutoXRay EZ-Link scanner, firmware revision rtv226_2.jcb turned out to be the problem. When I reverted back to the rtv224_2.jcb firmware my trouble(codes) went away.
Just a heads up in case there is one more of these scanners in the western hemisphere.
Now where was that compulsive/obsessive thread at again?