Jump to content
  • Welcome Guest To Mopar1973Man.Com

    We are a Dodge Ram Cummins Turbo Diesel forum. We are very friendly and helpful group of Dodge Ram Cummins owners. We will try to keep your truck running the best we can and provide information for diagnostics, repairs and even guide you on the best replacement parts to use. 

     

    Registration is free. Registering on the site will provide access to many more things like...
     

    • Contribute to the Forum being able to ask questions and get support for your Dodge Ram Cummins.
    • Contribute to Article Database adding your ideas and suggestions.
    • Classified Ads posted by the members. Post up your used parts and vehicles.
    • Member Garage where you can proudly display your vehicles and modifications that you have done to them.
    • Download files, documents, and Quadzilla Adrenaline tunes for your truck.
    • 911 Support Network. We've got a group of members will to aid you if your truck breaks down on the road.
    • Reduced Advertisements displayed to you.

Recommended Posts

Hi all, pardon me for what may turn out to be a stupid question.

 

1999 Dodge 2500 Cummins with an embarrassing amount of money dumped into it.

 

I used to have an Edge Juice tuner but had to switch to Quadzilla so I could change timing.  Edge won't change timing.  The Edge tuner does, however, connect to the ODB2 port so you can set read and reset engine codes.  Very Handy.  Quadzilla does not.  I bought a $100 bluetooth ODB2 scanner and hooked that up.  I get RPM, temperature, TPS etc from it but NEVER any engine codes.  

 

About a month ago my PCM and transmission fulfilled a long planned suicide pact and that set me back a serious amount of money.  Check engine light was never lit.  Mechanic pulled the codes for me in the shop (check engine light wasn't lit for him either).

 

I called tech support for my bluetooth scanner and they say the scanner won't report anything, ever, unless the check engine light is lit.  But my Edge tuner DID.  Many, many times.

 

What am I missing here?  I sure don't want to shell out that kind of $ again.

 

Thanks in advance for your wisdom.

Share this post


Link to post
Share on other sites

Bluedriver made what I have connected now.  I stopped in at the oriely's up the street and borrowed their bosch reader.  It said "no errors" but the kid that was running it also commented that if the check engine light is't lit you'll see nothing.

Share this post


Link to post
Share on other sites

I know the edge unit detected them.  Many, many times.  Like the one that's kicked up when there's a vacuum leak for cruise control.  Didn't light the cel, but did throw codes.

Share this post


Link to post
Share on other sites

Not to Hi-Jack this  thread but.  What will read the ECM Engine codes?  It is my understanding that the cheaper ones will not read the ECM codes?

 

Thanks!

Michael

Edited by int3man

Share this post


Link to post
Share on other sites

Verified... Works fully and reads PCM, ECM and live data.

 

http://www.obdlink.com/lxbt/

 

http://www.obdlink.com/mxbt/

 

Rare time, I've seen OBDII tools hang up and not read any codes even though the CHECK ENGINE light is on. I've found if you pull the ECT sensor lead and create a fresh code then the rest of the codes show up.

 

NOTE: 98.5 to 2002 Dodge Cummins are NOT ODBII compliant. If you check PID 1C (Hex) it will report 05 back in response. Which means Dodge Cummins not ODBII compliant.

https://en.wikipedia.org/wiki/OBD-II_PIDs

 

Share this post


Link to post
Share on other sites

Yeah, I went a bit technical. Basically if you have OBDLink LX or MX dongle you can use a bluetooth terminal app on your device. Now log into the dongle and issue commands to the bus. The PID list is the manual way of looking at information on the bus. Most apps do this for you but skip things like the address 1C which is ODBII compliance. Funny when you see the result from that address on the bus is a 5 and the Cummins is NOT OBDII compliant. 

 

As for the code hang up it just weird burp or hiccup you might run into sometimes. I posted that to hopefully help anyone out with a hung OBDII error code that won't report. I think it was more so the ScanGauge II that I have that did this hang up. Right now @Me78569 has my ScanGauge II.

 

 

 

 

Edited by Mopar1973Man

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×