Hey guys just got back from our first trip in the f350, had a little issue that I can't figure out.

After a couple hours of cruising at high-way speed with the cruise control on the truck had a little hick-up then the ABS light came on??? any ideas as to why?? what does the cruise control have to do with the ABS??? any help would be great, thanks in advance!!!!


By the way--great site for us first time diesel guys!!! Thanks!!!

 

The ABS system keeps track of each wheel's speed & compares the numbers to each other. The system is smart enough to determine sensor failures based on the input from each wheel sensor and the application of a bit of common sense. While not technically accurate, this would be like seeing three tires going a steady 70 MPH and the third keeps fluctuating between 30-60 MPH. If you had applied your brakes, the ABS system would have jumped in to control the braking, as it would think the one tire was skidding.

All of these sensors and various computer components work together to control almost every aspect of the drivetrain. Hence, the hiccup you saw with the cruise control was directly tied to fault that triggered the ABS light. It almost seems counter-intuitive, as the systems seem to be unrelated. But, this is definitely the age of computer-controlled vehicles.


While I cannot guarantee that it is one of these wheel speed sensors, that would be my first guess. You should be able to get the trouble code off of it, and bounce that code off of an OBDII reference to see for sure what it triggered the ABS light for.

 

Ok this is gonna sound stupid but where?how do I get the trouble code and how do I "bounce" it off of a OBDII--and what is that!!! LOL!!

Also the ABS light was not on the next day, and it didn't come on for 3 days of short driving at our destination, but it did come on again on the way home. basically under the same circumstances.

 

The ABS system resets each time you shut the ignition off and it didn't come back on during those three days because you were likely not driving fast enough for the computer to realize something wasn't right. My guess is it is a wheel speed sensor too.

 

OBD stands for On-Board Diagnostics. It is a joint venture between several different motor companies (primarily) to standardize error codes that the computers output. This simplifies troubleshooting...regardless of whether the technician/mechanic is looking at a Ford or a GMC. The II on OBDII indicates revision number 2...it is merely a newer, cleaner, and more expansive set of trouble codes.

There are several online sites that provide the results for a given OBD code. You can Google any number of related terms like OBD, CEL, check engine light, trouble codes, etc. One good place to hit is: http://www.obd-codes.com/

To get the codes, you need some form of scanner to pull the code from the vehicle's primary computer (usually called the PCM or ECM). While most folks do not have one of these floating around, there are a number of auto stores that will pull the codes for free. And, to go a step further, there are some vehicles that you can get the display without a tool. (I know most 2000+ Daimler-Chryslers with a digital odometer display will display any stored error codes by cycling the ignition switch from off-on-off-on-off-on...do not start the vehicle, and finish the sequence with the key in the on position on the third on cycle.)

There are generally only two conditions that clear codes that trigger a CEL (Check Engine Light) or similar "idiot" light, as many people call them.

• The vehicle must lose power (i.e. disconnecting the battery) with some form of drain on the system (leaving the key in the on position). This is commonly done by folks that run chips/tuners, as it forcibly clears the computer & transmission modules of their "learned" strategies.
• The vehicle manufacturer add in a strategy where the codes are erased if the error condition does not re-ocurr anytime during the last 2-5 restart/shutdown cycles.
  • This is done by some folks to forcibly clear bothersome CELs....like the famous "evaporative emissions system leak"...which is fancy talk for loose gas cap.
  • It is intended to clear intermittent or "false" codes from memory. This prevents the codes from "piling up" and complicating troubleshooting efforts for a new & very real problem.

With that having been said, it is likely that one of the wheel speed sensors was providing sporadic input for some unknown reason, but that condition has not happened again in the last couple of times you have driven. There are any number of causes for this including everything from the mundane (mud or debris in/around the hub assembly) to the unusual (sporadic/intermittent failure of the sensor).

 

Thanks for the info guys, I'll go see if my local parts place will run a scan for me(hope so, a friend owns the place!!!)

Taht being said, if it is a wheel sensor is that something that should or could be replaced?? or is it just one of those little annoying things?

 

they can be replaced (the hardest part is getting it out because it is probably corroded in there) and should be replaced because you never know when that ABS will be needed.

 

The code(s) are likely gone. If it were a persistent condition, the ABS light would have stayed lit. As the ABS light has not come back on, I almost have to say that the fault condition has not happened again.



As it is a 2006 F-350, I kind of doubt that a wheel sensor is going out already. Not unheard of, after all the world is very much an imperfect place, but it just seems unlikely.

I would chalk it up to either a piece of road debris or some form of computer brain fart. Either way it was transient in nature, and likely not worth putting significant efforts into troubleshooting.

 

had the same problem with my 06 f-350 truck lost power for about 3 seconds.
c c on 73 mph. did not throw any codes abs light came on than off dealer
can't find any codes stored in computer.said it could be speed od or abs sensor
its ok now but its on record if any problem happens at a latter time