Beginning yesterday my abs and brake light in inst cluster are stuck on. Fuses are good. Is the problem still more than likely the speed sensor on rear axle, even if speedometer was working most of the time until late today when it seems to have quit completely. Any input on this would be greatly appreciated. 

If the cruise control or the speedometer is acting goofy then I would replace the rear speed sensor.

I would be thinking front speed sensor or wheel bearing maybe if you have 4 wheel ABS.

Like I know my problem is the front wheel bearing and the tone rings are screwed. My sensors, ABS module and everything else checks out fine.

I replaced both front wheel bearings and my abs/brake lights are always on and were when i bought the truck. 

Speedo,cruise etc all work fine.

I have it on the list to figure it out but it's way down on the list. 

 

8 hours ago, BIG-BLACK-DODGE said:

replaced both front wheel bearings and my abs/brake lights are always on and were when i bought the truck. 

Speedo,cruise etc all work fine.

 

Front sensor problem.

2 hours ago, Mopar1973Man said:

 

Front sensor problem.

What sensor? Like where is it?

Mounted to the front wheel bearing. You have to remove the tire, caliper and rotor and right on top of the bearing is a sensor. One on each axle.

You should have seen the wires in the new wheel bearings. If there were no wires then you got non ABS wheel bearings. Hence the light.

Perhaps he has the (KELSEY-HAYES EBC 2) 2 wheel drive ABS system.
I believe all wheel drive ABS system was optional in 99 year model of the truck.

 

Now this is all wheel drive ABS system:
Kelsey-Hayes EBC 325 Antilock Brake System (ABS) 
The EBC 325 system is a three channel, three sensor, four wheel antilock brake system. 

 

Now this is slightly off topic but I was reverse engineering the CCD bus network for the past 6 months trying to develop my own Overhead Console (Message Center Display)  which is already capable of reading ABS codes and AirBag codes.

 

The idea is to develop overhead console (Message Center Display) with 3D printed case that is a direct replacement for the Dodge RAM OEM (Message Center Display) overhead console.
Of course the progress is very slow mainly because of the two kids on board, full-time job, it seems like life is always getting in the way ):
 

Here I got a short YouTube video preview:
Dodge RAM 99~02 Prototype overhead console message center display ABS testing.

https://youtu.be/yCJrg9OZzWE

Now before anyone asks, the instrument cluster and the PCM and ABS is actually from Dodge Durango 2000 scrap yard SUV.

Edited July 6, 20168 yr by Chris O.

Would be willing to share the CCD data info with us. I'm wanting to figure out more CCD data and gain access to it. Like reading the error codes of the ABS as well. Would you be willing to make an article of your findings?

I am very interested also.

Well guys i'm just a bit too busy today, but I am going to point you to the jeep forums i was hanging out for a while for a good read about the ccd bus.

http://thespeedfreaks.net/showthread.php?12585-CCDuino-A-ZJ-Databus-Project

been through that one before I need to read the updates.  I am curious to hear about your project.  I am assuming the ccd bus protocol is the same in a jeep vs cummins?  

Edited July 7, 20168 yr by Me78569

CCD bus protocol is the same in all Chrysler vehicles from 1988 to about 2002.

Chrysler Collision Detection, CCD, was one of the first widely used vehicle-wide multiplexing protocols used in the US.
Introduced in 1988 on the Dodge Dynasty and Chrysler New Yorker, CCD was originally used for transmission controller to engine controller communications and data sharing.
Soon thereafter, body control functions were added to the CCD bus.

 

Usually the data is send in either 3 bytes, 4 bytes, 5 bytes or 6 bytes pockets.

The first byte is the ID byte,  then follows the data bytes and the last one is the (CRC) cyclic redundancy check byte.

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.

6 byte msg.example=(ID 12, DATA 112 107 129 69, CRC 173)

ID 12,DATA:Voltage, Oil, Coolant, Battery, CRC Checksum

 

The catch is the meaning of some ID and the remaining data various from module to module on each vehicle.

 

Edited July 7, 20168 yr by Chris O.

Chris could we get you move a new thread with the study and information on your CCD project. That way we can let the this thread continue without hijacking...

Sure thing you guys need a DIY sub-menu ):

we tend to more DIY stuff to articles once the path has been laid out.

 

 

On July 6, 2016 at 0:48 PM, Mopar1973Man said:

Mounted to the front wheel bearing. You have to remove the tire, caliper and rotor and right on top of the bearing is a sensor. One on each axle.

But i have brand bew bearings on both wheels. 

It's a 4x4. The plugs are pluged in good and tight etc. Light still on but i never messed with it at all.

Like for example. I've got a reman'ed ABS module and tested on another vehicle works fine. Traded another module on to my truck and lights pop. So changed the front sensors 4 different times now. I know that I've got good sensors. My tone rings are creating the issue some how. Every time the ignition key is cycled off and back on it self resets and re-checks for errors. If errors are found then the light are set again. So basically you have to resolve the error.

I don't like ABS brakes. Any proper way to disable them?