Engine/Transmission (1998.5 - 2002) P1693 but no companion

[dresslered]

Last Friday after fueling up I had a check engine light come on. Toggling the ignition revealed a P1693 code but there was no companion code displayed. After about 50-miles of driving and several engine starts, the check engine light went out and has stayed out. Now after 500-miles of driving (truck runs great), I can still retrieve a P1693 but no other codes. Does anyone have any idea what this might mean? I have always monitored the lift pump pressure and maintained safe levels. TIA

 

[Turbo Tim 1]

I have found that very few codes actually come up on the ODO, go check it with a code reader and you'll find out what it is though.

 

[dresslered]

Thanks TT,

I was looking into the code readers back when I first got the truck but haven't needed one until now. What is the concensus on the best reader these days (other than the fancy high $$$ one that Cummins uses). I would like it to read the truck codes as well as the engine codes.

 

[SBall]

David,
I recently had a P1693 code come up on the odometer, but it took a code reader to display the other ones. These other codes not displayed on the odometer by cycling the key were P0216 "ouch", and P0234. I broke down and bought a good scan tool as part of my VP44 replacement project. I chose an Actron CP9190 for its live data graphing capabilities. Amazon had a very good price.
Steve

 

[blacksheepdiesel]

SMARTY!!!

Code reader AND fun enhancer all in one!

Godspeed,
Trent

 

[dresslered]

Thanks,

Thanks Steve and Trent,



I have a friend bringing in his scanner on Monday to see what we can find out. After that, I will look into both the Actron and Smarty (wife has a Durango which we frequently need the scanner as well). I'm sure hoping that it is not the VP44. Perhaps it is the P6969, "Cummins driver needs another beer". :-laf

 

[CCahill]

I've had the 1693 code on my truck for quite a while now... .comes and go's... the scanner couldn't pull up any companion codes... this all happened since my last VP44, and FASS change over... gettin' used to it now...

 

[rotohead]

I've had the 1693 code on my truck for quite a while now... .comes and go's... the scanner couldn't pull up any companion codes... this all happened since my last VP44, and FASS change over... gettin' used to it now...

Does this include the CEL on at the same time too?

Chuck

 

[CCahill]

well sure... thats how you know if you threw a code or not... the check engine light comes on... at least thats how it works in my truck...

 

[rotohead]

well sure... thats how you know if you threw a code or not... the check engine light comes on... at least thats how it works in my truck...

Well you can get codes set, esp 1693, w/o a CEL accompanying it. Just wondering if that was the case with your situation.

 

[Crash_AF]

1693 is the code that tells the PCM to turn on the CEL because there is a code set in one of the other modules (ECM, TCM). If you do not have a good enough scanner, you will not get the codes from those modules and it will appear that there is no companion code.

In addition, according to the Chrysler FSM, 1693 will always light the CEL.

Later,
Joe

 

[Gary - K7GLD]

I don't remember the specific details, but earlier related threads on this board pointed out that SOME codes are not readable with a typical code reader, and require a type that is available to DC service techs - if I knew what to search on, I might be able to find the threads where that was pointed out.



But in any event, just because you can't find the actual trouble code with regular testers, doesn't mean it doesn't exist...

 

[Bob4x4]

I don't remember the specific details, but earlier related threads on this board pointed out that SOME codes are not readable with a typical code reader, and require a type that is available to DC service techs - if I knew what to search on, I might be able to find the threads where that was pointed out.



But in any event, just because you can't find the actual trouble code with regular testers, doesn't mean it doesn't exist...

:-laf Yup... ... ... The right tools for the job help.



Bob

 

[dresslered]

I remember those same threads as Gary does. The tool that Cummins uses is the "God" of all scanners but somewhat price prohibitive. I believe that Snap On makes a similar tool but also pricey. Speaking in layman's terms, I believe that the engine computer (ECM) reported a fault that the truck's computer (PCM) acknowledged by turning on the 'check engine' light (MIL) and displaying the 1693 error when toggling the ignition three times. After a certain number of starts and possibly mileage, the check engine light went away but the 1693 error is still being held and is only observable when toggling the ignition three times. My MIL light went out after about 10 starts and about 40 miles of driving. The service manual claims "the ECM or PCM cancels the code after 40 warm-up cycles" so perhaps my code will eventually go away if the problem no longer persists. Again, as Gary mentioned, there seems to be a number of scanners available, and each may or may not go deep enough to read the engine's computer. Additionally, the service manual claims that the MIL indicator will only illuminate if it is emissions related. My truck is essentially stock, with the exception of RV275's, DDTTPM (level 2), and boost to 30-psi. This has never been a problem in 108k miles.

 

[dclassens]

I had a 02 CTD 4x4 auto come into the shop I worked at with the dead pedal issue. I was NOT impressed the Snap-On Modis. The key cycle worked better than the snapon, and it was almost $9,000. for the owner to spit out for this tool. Just a FYI.

Dave

 

[dresslered]

no luck

We tried my friend's scanner today (I forget the model but it ran through his laptop) and were unsuccessful at reading any codes. I then drove over the the local Dodge Dealer and they wanted to charge me an hour labor to read the code. I drove away. #@$%!

 

[Bob4x4]

We tried my friend's scanner today (I forget the model but it ran through his laptop) and were unsuccessful at reading any codes. I then drove over the the local Dodge Dealer and they wanted to charge me an hour labor to read the code. I drove away. #@$%!

You have been stressing over this for a week already. I would have thought you would be glad to pay a bit to put it to rest. :-laf Good luck.



Bob

 

[2broke2smoke]

fwiw guys i've had the 1693 since my dtt installation 60k miles ago and it's never set the cel off ...

 

[dresslered]

reduce or increase stress

Bob, I would gladly pay to reduce my stess level. However, throwing $120 at a dealer that 'thought' they might be able to read it just seemed to push the stress level the wrong way. I think that I will pick out a scanner wisely, and if that still doesn't read the code, I will consider it nonixistant.

 

[Bob4x4]

Bob, I would gladly pay to reduce my stess level. However, throwing $120 at a dealer that 'thought' they might be able to read it just seemed to push the stress level the wrong way. I think that I will pick out a scanner wisely, and if that still doesn't read the code, I will consider it nonixistant.

Wow 120 per :{ If you lived closer I would volunteer to read it for you... .....

Sorry

Bob