Jump to content
Mopar1973Man.Com LLC

  • Welcome To Mopar1973Man.Com LLC

    We are a privately owned support forum for the Dodge Ram Cummins Diesels. All information is free to read for everyone. To interact or ask questions you must have a subscription plan to enable all other features beyond reading. Please go over to the Subscription Page and pick out a plan that fits you best. At any time you wish to cancel the subscription please go back over to the Subscription Page and hit the Cancel button and your subscription will be stopped. All subscriptions are auto-renewing. 

ABS failure found!

Mopar1973Man
 Share

Recommended Posts

  • Owner
Mopar1973Man

Mopar1973Man

Posted
  • Author
  • Owner
Posted

@dripley ok... Let's work through your problem. So you replaced the front sensors with the new wheel bearings. New rear sensor. Now have you ohm tested the leads from the ABS computer to the sensors? Have you checked and dielectric greased all connectors? Have you checked the tone rings for debris in the teeth? Beyond that I'm going to need to see the truck when you come to Idaho.

Link to comment
Share on other sites
dripley

dripley

Posted
Posted
19 hours ago, Mopar1973Man said:

@dripley ok... Let's work through your problem. So you replaced the front sensors with the new wheel bearings. New rear sensor. Now have you ohm tested the leads from the ABS computer to the sensors? Have you checked and dielectric greased all connectors? Have you checked the tone rings for debris in the teeth? Beyond that I'm going to need to see the truck when you come to Idaho.

I did not check the bearings for any debris. The ABS light was on when I replaced the bearings and I hoped that would solve the problem. I have pulled the connectors off of the computer plugged and unplugged them a few times. greased them and reconnected them. I also did the same to the connector just behind drivers front wheel. Have not ohmed anything as of yet.  

Link to comment
Share on other sites
  • Owner
Mopar1973Man

Mopar1973Man

Posted
  • Author
  • Owner
Posted

Kind of tough to figure out ABS issues without being able to see codes. As you see my thread is based on fighting an ABS issues for over 2 years and spent lots of money on sensors and ABS module rebuild. I'm hoping is a basic issue like broken wire or a sensor that isn't fully plugged in. 

Link to comment
Share on other sites
Chris O.

Chris O.

Posted
Posted (edited)
On 4/22/2017 at 9:07 AM, Mopar1973Man said:

I'm going to have to create a killer write up on ABS diagnostics and how to test for these weird things with and without a DRBIII tool.

Hey Mike in case you do the write-up this could be helpful.

 

- GLOSSARY OF TERMS -
ABS --- antilock brake system
CAB --- controller antilock brake
CCD --- Chrysler Collision Detection
DLC --- data link connector
EBC --- electronic brake controller
EMF --- electromotive force (generated voltage)
HCU --- hydraulic control unit
IC ---- integrated circuit
NVRAM - non-volatile random access memory
PDC --- power distribution center
RAM --- random access memory
RWAL -- rear wheel antilock
ROM --- read only memory
WSS --- wheel speed sensor

 

 

The EBC 325 system can be identified by the
 presence of the controller antilock brake (CAB)
 located directly on the HCU (hydraulic control unit).

EBC 325 (CAB).JPG

Kelsey-Hayes All Wheel EBC 325 (CAB) Antilock Brake System DTCs.
CODE 21 - Right Front Sensor Open.
CODE 22 - No Signal From Right Front Sensor.
CODE 23 - Intermittent Signal From Right Front Sensor.
CODE 25 - Left Front Sensor Open.
CODE 26 - No Signal From Left Front Sensor.
CODE 27 - Intermittent Signal From Left Front Sensor.
CODE 35 - Rear Sensor Open.
CODE 36 - No Signal From Rear Sensor.
CODE 37 - Intermittent Signal From Rear Sensor.
CODE 38 - Wheel Speed Mismatch.

CODE 41 - Right Front Isolation Valve Solenoid Open.
CODE 42 - Right Front Dump Valve Solenoid Open.

CODE 43 - Right Front Isolation Valve Solenoid Shorted.
CODE 44 - Right Front Dump Valve Solenoid Shorted.

CODE 45 - Left Front Isolation Valve Solenoid Open.   
CODE 46 - Left Front Dump Valve Solenoid Open.

CODE 47 - Left Front Isolation Valve Solenoid Shorted.
CODE 48 - Left Front Dump Valve Solenoid Shorted.   
CODE 51 - Rear Isolation Valve Solenoid Open. - EBC 2
CODE 52 - Rear Dump Valve Solenoid Open. - EBC 2
CODE 53 - Rear Isolation Valve Solenoid Shorted. - EBC 2
CODE 54 - Rear Dump Valve Solenoid Shorted. - EBC 2
CODE 65 - Internal Main Relay Open.
CODE 66 - Internal Main Relay Shorted.
CODE 67 - Pump Motor Circuit Open.
CODE 68 - Pump Motor Stalled -  Locked ABS Pump Motor Or Shorted Motor Circuit.
CODE 69 - Excessive Dump Time.
CODE 71 - RAM Read/Write Malfunction.
CODE 72 - ROM Checksum.
CODE 73 - Inoperative Watchdog Inhibit
CODE 74 - System Control Mode Timeout.
CODE 78 - Foundation Brake Partial System Malfunction.
CODE 81 - Brake Lamp Switch Circuit.
CODE 82 - Number of Tone Ring Teeth Out of Range.
CODE 83 - Tire Revolutions Per Mile Out of Range.
CODE 84 - Mismatched VIN.

 

The EBC 2 system can be identified by the
 presence of a separate rear hydraulic control unit HCU.

EBC 2 (CAB).JPG

Kelsey-Hayes Rear Wheel EBC 2 (CAB) Antilock Brake System DTCs.
CODE 35 - Rear Sensor Open.
CODE 36 - No Signal From Rear Sensor.
CODE 37 - Intermittent Signal From Rear Sensor.
CODE 51 - Rear Isolation Valve Solenoid Open.
CODE 52 - Rear Dump Valve Solenoid Open.
CODE 53 - Rear Isolation Valve Solenoid Shorted.
CODE 54 - Rear Dump Solenoid Shorted.
CODE 63 - Shuttled Reset Switch Concern \ Rear Reset Switch Closed
CODE 65 - Internal Main Relay Open.
CODE 66 - Internal Main Relay Shorted.
CODE 69 - Excessive Dump Time.
CODE 71 - RAM Read/Write.
CODE 72 - ROM Checksum.
CODE 73 - Inoperative Watchdog Inhibit
CODE 78 - Foundation Brake Partial System Malfunction.
CODE 81 - Brake Switch Circuit.
CODE 82 - Tone Ring Teeth Factor Out Of Range
CODE 83 - Tire Revolutions Per Mile Factor Out Of Range
CODE 84 - Mismatched VIN

Edited by Chris O.
Oops I was missing 4 diagnostic dtcs: CODE 41, CODE 43, CODE 45, CODE 47.
  • Like 2
Link to comment
Share on other sites
  • 7 months later...
Silverdodge

Silverdodge

Posted
Posted
On 3/19/2017 at 8:56 PM, Chris O. said:

Oh man I don't have all the IDs nicely organized in one place but all over inside the code,  it will take me a while to get it all. 
Some of the messages are unknown even to me.

 

Let's start with brief explanation off the CCD BUS. Messages on the CCD-bus are flowing in a series a bytes. 
Every message starts with an identification byte (ID byte) There’s no way of knowing what every single byte means.
Some messages can be reverse engineered by trial and error. The last byte is a one byte checksum value, inbetween is the message if any. The checksum byte is calulated by summing all the ID and Data Bytes.

256 is then subtracted from that sum. 
The subtraction will end once the checksum falls within 0-255 decimal range.

 

ID36 Vehicle Speed
/***************************************************************
[0] = 36 = Vehicle Speed
[1] = SPD_MPH
[2] = SPD_KMH
[3] = CRC

 

Example: 36 15 24 75
SPD_MPH = 15(DEC) mph
SPD_KMH = 24(DEC) km/h
CRC: 36+15+24 = 75; 
***************************************************************/

ID109

/***************************************************************
[0] = 109 = Vehicle Identification Number (VIN)
[1] = VIN_POSITION
[2] = VIN_VALUE (ASCII DEC)
[3] = CRC
Notes: the messages are ~3 seconds away from each other so the
reading of the full VIN will take ~1 minute

 

Example:

109 Pos.1   ASCII.49 159 
109 Pos.2   ASCII.66 177 
109 Pos.3   ASCII.52 164 
109 Pos.4   ASCII.xx CRC 
109 Pos.5   ASCII.xx CRC 
109 Pos.6   ASCII.xx CRC 
109 Pos.7   ASCII.xx CRC 
109 Pos.8   ASCII.xx CRC 
109 Pos.9   ASCII.xx CRC 
109 Pos.10  ASCII.xx CRC 
109 Pos.11  ASCII.xx CRC 
109 Pos.12  ASCII.xx CRC 
109 Pos.13  ASCII.xx CRC 
109 Pos.14  ASCII.xx CRC 
109 Pos.15  ASCII.55 179 
109 Pos.16  ASCII.52 177 
109 Pos.17  ASCII.50 176 

VIN: 1B4xxxxxxxxxxx742

***************************************************************/

Edit:
When you select ID in USB Log Settings it will show up a brief explanation in the Message box.

Can u turn on and off high idle with it 

Link to comment
Share on other sites
Chris O.

Chris O.

Posted
Posted
Quote

Can u turn on and off high idle with it 

Currently NO.

Will it be possible in the future?

I'm not sure maybe... I'm having a hard time accessing the ECU with CCD bus in diagnostic mode.

Just to be clear there is no issues reading the data in-coming from ECM on the CCD bus.

On top of all this the older 1998.5-2000? 2nd gen Cummins trucks ECM may need to be reflash for high idle feature anyway.

Link to comment
Share on other sites
  • Staff
01_Cummins_4x4

01_Cummins_4x4

Posted
  • Staff
Posted

@Chris O. - Congrats on making an awesome tool for troubleshooting our Dodge diesels and other OBDII vehicles!!!

 

I just got back into diesels last Friday when I got a 99 Dodge Ram 2500 quad cab short box Cummins 4x4 pickup, otherwise I'd have been all over beta testing your tool for you before now.

 

My Dodge is having a delayed wait to start issue and I just replaced the AIT sensor, but no change in the wait to start issue.

My ABS and brake lights will come on every once in a while, and I just put in a new rear ABS sensor in the rear end, but it's still happening. It doesn't have the bad ECM code, but I'm still leery that it could be the ECM.

 

My auto transmission is painted gold with a blue pan, so someone must have been through it, but when it shifts from 1st to 2nd, then it shifts up to 3rd and then it shifts again really quick and disrupts the normal acceleration, and then it shifts into OD. It's not slipping at all, but it is annoying as hell.

 

Would you by chance need another tester to help improve your tester tool by providing all the data that I can get from it?

 

I was the person on the Toyota forums that did all the testing and diagnosis for the Limited 4Runner multi mode 4x4 system, and I helped saved many Toyota owners thousands of dollars by testing the sensors of the 4wd system, instead of replacing the transfer case that the Toyota dealers were quoting them at $2k a pop.

 

I'm an IT guy anyway, (network administrator) so I enjoy the data logging, diagnosis, and resolution of issues.

 

Please let me know ASAP if I can be of assistance in helping improve your testing tool.

 

Thanks,

 

Doug

Link to comment
Share on other sites
Chris O.

Chris O.

Posted
Posted
13 minutes ago, 99_Cummins_4x4 said:

Would you by chance need another tester to help improve your tester tool by providing all the data that I can get from it?

Well currently the beta testing is almost over as i am working on the final design.

There might be a brief short beat test for the new tool.

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...