Limp Mode and 4WD Issues

[dcmdon]

This may or may not apply to you:

There are two different types of codes you should be aware of. There are the CEL codes (your Check Engine Light codes) which are picked up by common OBD-II scanners. Beyond that, each of your vehicle's modules store their own per-module trouble codes. An everyday OBD-II scanner won't pull those. If you want to see those, you'd need something designed to do it. (And if you do, DO NOT CLEAR THEM.)

But the underlying point here is that just because your OBD-II scanner did not record a code does not mean that one or more of your modules may have recorded evidence that the dealer can use to substantiate your issue.

As a reminder, if you are having a weird issue, always try to remember to record some video of it. Dealers love it when you can show them something is wrong even if you're giving them a vehicle where everything looks right.

Unless you're sure your modules recorded nothing, if you're under warranty, I'd take the issue to your dealer. Even if you're afraid they'll find nothing.

Will a Chrysler specific computer like a Tazer or AlfaOBD be able to read these module level codes??

Sponsored

 

[ShadowsPapa]

Will a Chrysler specific computer like a Tazer or AlfaOBD be able to read these module level codes??

There are many scanners that will access other modules. I had a forum member come over with his to check the ABS codes in my WJ - the only problem is that up through 2004 Jeep ABS codes were unique and few readers handle them - but he could read such codes on newer than 2005 Jeeps and other vehicles.
It's just that your basic scanners many parts stores use do "check engine" only, nothing else, but some do have the ability.
You don't need anything special, just a good scanner that handles the other modules.
JSCAN will AlfaOBD will, but so will many other hand-held dedicated scanners.
I suspect even free software like Torque may do it.

 

[dcmdon]

Got it. My OBD2 scanner only reads OBD2 standard codes.

It won't read the manufacturer specific codes that are outside of the OBD2 spec. So far the only codes my jeep has thrown are standard OBD2 codes. Which my Tazer handled perfectly.

I wonder if the Tazer will read some of the other modules. (Are these chassis modules?)

Back when I had a VW and an Audi, I purchased the VagCom software. God it was amazing. It was a reverse engineered version of the VAG software that dealers used. I could program anything a dealer could and read any codes a dealer could. It was great. I suspect something like Alfa OBD does the same thing.

 

[jmccorm]

Will a Chrysler specific computer like a Tazer or AlfaOBD be able to read these module level codes??

Tazer can (when kept up-to-date with a recent firmware), yes.
I know JScan will do per-module scans under Advanced Scan.
I'm afraid I'm not an AlfaOBD user (no Android devices here).

 

[ShadowsPapa]

Tazer can (when kept up-to-date with a recent firmware), yes.
I know JScan will do per-module scans under Advanced Scan.
I'm afraid I'm not an AlfaOBD user (no Android devices here).

AlfaOBD will do it all and more. It's been around for years for FCA vehicles. It's the "go-to" for RAM owners.
Body, ABS, engine, whatever.
You can do things besides just looking for codes in ABS.

Sponsored