Previous Thread
Next Thread
Print Thread
2002 dodge dakota pcm issue. #1932745
10/15/15 06:40 PM
10/15/15 06:40 PM
Joined: Jan 2006
Posts: 419
NY
F
F1Scamp Offline OP
mopar
F1Scamp  Offline OP
mopar
F

Joined: Jan 2006
Posts: 419
NY
Usually this sort of problem is what i do well. This thing is throwing me for a loop. 2002 dodge dakota 4.7l auto 4wd 150k. Died while driving. No bus message on instrument cluster. Found where the pcm grounds are supposed to be rotted away. Put new ground wires on, checked all other powers and grounds, everything checked good. Could talk to all other modules with scan tool. Still could not talk to pcm and truck would not run. Got a pcm off ebay all programmed. Put it in, truck runs and i can talk to pcm with scan tool, however cannot-talk to instrument cluster and still get the no-bus, no gauges work. Put the old pcm in and truck does not run, and i cannot talk to pcm, however can talk to instrument cluster. I assume the new pcm is bad somehow, but it doesnt really make sense. Anybody seen anything like this? What the heck am i missing?

Thanks


Work In Progress- 71' Duster F.A.S.T.- 10.36@130 Smallblock Record Holder.
Re: 2002 dodge dakota pcm issue. [Re: F1Scamp] #1932887
10/15/15 11:20 PM
10/15/15 11:20 PM
Joined: Aug 2005
Posts: 5,998
Salem
Grizzly Offline
Moparts Proctologist
Grizzly  Offline
Moparts Proctologist

Joined: Aug 2005
Posts: 5,998
Salem
Does the new PCM need to be set/programmed specific to your VIN?

Does the correct mileage show on the odometer with the new PCM or just "no bus"?


Mo' Farts

Moderated by "tbagger".
Re: 2002 dodge dakota pcm issue. [Re: F1Scamp] #1932903
10/15/15 11:37 PM
10/15/15 11:37 PM
Joined: Dec 2003
Posts: 2,042
Leucadia, Ca.
V
vdriver Offline
top fuel
vdriver  Offline
top fuel
V

Joined: Dec 2003
Posts: 2,042
Leucadia, Ca.
When I had to replace the PCM on my '96 Dak, the guy needed my VIN #. It was an ebay purchase from an outfit in south Florida; can't remember their name.

Re: 2002 dodge dakota pcm issue. [Re: vdriver] #1932999
10/16/15 01:44 AM
10/16/15 01:44 AM
Joined: Mar 2007
Posts: 855
Southeast Pa.
SALEM1912 Offline
super stock
SALEM1912  Offline
super stock

Joined: Mar 2007
Posts: 855
Southeast Pa.
If it helps. From PCM to Data Link connector to the scan tool will use the SCI wires to communicate with the PCM only. All other modules including the PCM share the PCI wiring. So a defective PCM could be pulling down the PCI causing no bus. I recently used a aftermarket PCM on a Jeep and had the same type issues, the third PCM fixed it after lots and lots of hours looking for something other than the pcm as the cause!

Last edited by SALEM1912; 10/16/15 01:45 AM.
Re: 2002 dodge dakota pcm issue. [Re: F1Scamp] #1933002
10/16/15 01:46 AM
10/16/15 01:46 AM
Joined: Mar 2003
Posts: 18,678
Fresno, CA
Jim_Lusk Offline
I Live Here
Jim_Lusk  Offline
I Live Here

Joined: Mar 2003
Posts: 18,678
Fresno, CA
Likely a bad new PCM. I went through two from the "outfit in Florida" before they got it right. First one died on the second start, second had Cal Emissions for a 49-state truck. Third one also died about a year later. My suspicion is that they got something wrong in the program on yours. They are good about returns...

I've got some spare 5.2 and 5.9 computers ('96-99). I can run my 2000 5.9 on any of them, but I get the NO BUS in the cluster...

Re: 2002 dodge dakota pcm issue. [Re: F1Scamp] #1933105
10/16/15 10:28 AM
10/16/15 10:28 AM
Joined: Jan 2006
Posts: 419
NY
F
F1Scamp Offline OP
mopar
F1Scamp  Offline OP
mopar
F

Joined: Jan 2006
Posts: 419
NY
Odometer is correct. I am leaning towards a bad pcm as well. I am very leary of diagnosing as a bad pcm to begin with because very rarely does a pcm go bad. This one came from flordia as well. I sent them an email, hopefully i get a response soon.


Work In Progress- 71' Duster F.A.S.T.- 10.36@130 Smallblock Record Holder.
Re: 2002 dodge dakota pcm issue. [Re: F1Scamp] #1933187
10/16/15 12:49 PM
10/16/15 12:49 PM
Joined: Aug 2005
Posts: 5,998
Salem
Grizzly Offline
Moparts Proctologist
Grizzly  Offline
Moparts Proctologist

Joined: Aug 2005
Posts: 5,998
Salem
Originally Posted By F1Scamp
I am very leary of diagnosing as a bad pcm to begin with because very rarely does a pcm go bad.


You bet, that's my understanding too. Your other one probably got a surge or something because of your wiring. As long as your mileage is still there, I bet another factory PCM from the local autowrecker will get you up and running without issue. twocents


Mo' Farts

Moderated by "tbagger".
Re: 2002 dodge dakota pcm issue. [Re: F1Scamp] #1933277
10/16/15 04:08 PM
10/16/15 04:08 PM
Joined: Jan 2005
Posts: 12,419
Kalispell Mt.
H
HotRodDave Offline
I Live Here
HotRodDave  Offline
I Live Here
H

Joined: Jan 2005
Posts: 12,419
Kalispell Mt.
If you get one from a JY make sure the truck does not need a grey key, if it does your truck will not run with it.


I am not causing global warming, I am just trying to hold off a impending Ice Age!



Re: 2002 dodge dakota pcm issue. [Re: SALEM1912] #1933528
10/16/15 11:25 PM
10/16/15 11:25 PM
Joined: Jan 2003
Posts: 27,421
Balt. Md
3
383man Offline
Too Many Posts
383man  Offline
Too Many Posts
3

Joined: Jan 2003
Posts: 27,421
Balt. Md
Originally Posted By SALEM1912
If it helps. From PCM to Data Link connector to the scan tool will use the SCI wires to communicate with the PCM only. All other modules including the PCM share the PCI wiring. So a defective PCM could be pulling down the PCI causing no bus. I recently used a aftermarket PCM on a Jeep and had the same type issues, the third PCM fixed it after lots and lots of hours looking for something other than the pcm as the cause!


This sounds right. Also make sure they gave you the right year PCM. I do remember some years with Neon's and Dakota's I had to go into the scann tool and turn on internal bus voltage so the scann tool could talk to the other modules other then the PCM so if its the wrong year PCM it may also cause that problem. And thats because the PCM is on the SCI circuit as was said and the other modules are on the PCI bus or which ever bus it used that year. We always went into the PCM and put the VIN in also as we would program it in with the scann tool. If it had skim then I would go into the skim module and program the vin in that module as you could also transfer the vin through the skim module. Ron







Powered by UBB.threads™ PHP Forum Software 7.7.1