Help! What do all these trouble codes mean?
12-22-2004, 08:05 AM
#29
Registered
Join Date: Aug 2003
Location: Brisbane, Australia
Posts: 1,459
Likes: 0
Received 0 Likes
on
0 Posts
Did the CEL/MIL occur when you had CAN Scan plugged in? If so, and you can reproduce it, you should raise this with Dan Harrison.
It is possible for a scan tool problem to cause the CAN bus errors to be logged. I can do it with my interface on demand for testing purposes - it saves me doing something like yanking the MAF/IAT connector to cause a CEL, but I do something deliberately to interfere with the bus to cause this. It shouldn't happen under normal circumstances.
Are you getting more trouble codes now they have been reset? If not, I'd be putting it all down to the flooding and low battery voltage as you tried to restart. If there is a problem with the MAF, you'll soon get another CEL and you'd really notice the lumpiness.
It is possible for a scan tool problem to cause the CAN bus errors to be logged. I can do it with my interface on demand for testing purposes - it saves me doing something like yanking the MAF/IAT connector to cause a CEL, but I do something deliberately to interfere with the bus to cause this. It shouldn't happen under normal circumstances.
Are you getting more trouble codes now they have been reset? If not, I'd be putting it all down to the flooding and low battery voltage as you tried to restart. If there is a problem with the MAF, you'll soon get another CEL and you'd really notice the lumpiness.
Last edited by sco; 12-22-2004 at 08:13 AM.
12-22-2004, 11:41 AM
#30
Evolution of REvolution
Join Date: Feb 2004
Location: Germany
Posts: 356
Likes: 0
Received 0 Likes
on
0 Posts
I don't know how after market scan tools work, but the PCM probably detects them on the network, tries to communicate with them, and can't, resulting in your communication (U) trouble codes. Makes sense to me, but I too think you should consult your tool supplier for details.
12-22-2004, 11:57 AM
#31
Registered
Join Date: Sep 2003
Location: Diamond Bar, Ca
Posts: 1,473
Likes: 0
Received 0 Likes
on
0 Posts
I dont think it's an issue with the CANScan because I can reproduce the CEL without it being plugged in. Matter of fact, this is usually the case. When I get home I plug in my CANScan to see what the trouble codes are. Thats how I know it's a P0100.
12-23-2004, 05:09 AM
#32
Registered
Join Date: Aug 2003
Location: Brisbane, Australia
Posts: 1,459
Likes: 0
Received 0 Likes
on
0 Posts
Hmm.. I'd have the dealer clear the DTC, then reproduce the problem with them there and have them re-read the DTC. This will soon clear up any confusion around CAN Scan causing the problem.
06-21-2005, 02:52 PM
#35
THREAD KILLER
Join Date: Sep 2003
Location: San Jose, California
Posts: 1,342
Likes: 0
Received 0 Likes
on
0 Posts
bump*
Whatever happened to this issue dave? I am having the same trouble codes now along with the misfire. This is the second time it has happened to me and the dealership only dealt with the misfire issue (as if they didnt see the P0003 and P0100 codes).
My CELs with these codes happened without using CANscan.
Whatever happened to this issue dave? I am having the same trouble codes now along with the misfire. This is the second time it has happened to me and the dealership only dealt with the misfire issue (as if they didnt see the P0003 and P0100 codes).
My CELs with these codes happened without using CANscan.
Thread
Thread Starter
Forum
Replies
Last Post
Shankapotamus3
Series I Trouble Shooting
28
03-14-2021 03:53 PM
TotalAutoPerformance
Vendor Classifieds
12
10-17-2018 09:00 AM
jamespond24
RX-8 Parts For Sale/Wanted
11
12-01-2015 11:11 PM
