Still chasing random cruise control problem
For the last week or so, my cruise control will randomly not respond to any buttons. It will work fine for a while, then nothing. Today while it was not working I was able to connect a bi directional scanner with module checks and I was able to get two codes. U0401-86 and u0429-86. I dont know if I was supposed to be driving while that test was being done, as I was just sitting in park in the driveway. Code U0429 Possible Causes · Faulty Steering Column Control Module · Steering Column Control Module harness is open or shorted. U0401-86
Cause:This DTC sets in continuous memory if the Hill Descent Control™ switch message from the IPC indicates the switch is stuck or held in place for longer than 30 seconds. This can be caused by a short to ground on the Hill Descent Control™ circuit or if there is an internal failure of the Hill Descent Control™ switch.Failure Type:Signal InvalidThis sub type is used for failures where some circuit quantity, reported via serial data, is not plausible given the operating conditions.
Cause:This DTC sets in continuous memory if the Hill Descent Control™ switch message from the IPC indicates the switch is stuck or held in place for longer than 30 seconds. This can be caused by a short to ground on the Hill Descent Control™ circuit or if there is an internal failure of the Hill Descent Control™ switch.Failure Type:Signal InvalidThis sub type is used for failures where some circuit quantity, reported via serial data, is not plausible given the operating conditions.
There are many other things that cause the U401:86. From the Workshop Manual:
This DTC sets in continuous memory if the accelerator pedal position message, brake pedal message, driven wheel torque message, engine status message or transmission gear lever position message from the PCM (sent through the GWM) contains "faulted" or "invalid" instead of the actual information.
This DTC may also be set if SODL or SODR (aka: BLIS modules) receives invalid network data from the PCM.
I suggest running a self-test of the SCCM and see if any more DTCs arise. There could be any number of issues. There are many faults that result in inoperable cruise control.
Hill Descent Control is controlled by the ABS module. A self-test of the ABS module might help as well.
This DTC sets in continuous memory if the accelerator pedal position message, brake pedal message, driven wheel torque message, engine status message or transmission gear lever position message from the PCM (sent through the GWM) contains "faulted" or "invalid" instead of the actual information.
This DTC may also be set if SODL or SODR (aka: BLIS modules) receives invalid network data from the PCM.
I suggest running a self-test of the SCCM and see if any more DTCs arise. There could be any number of issues. There are many faults that result in inoperable cruise control.
Hill Descent Control is controlled by the ABS module. A self-test of the ABS module might help as well.
There are many other things that cause the U401:86. From the Workshop Manual:
This DTC sets in continuous memory if the accelerator pedal position message, brake pedal message, driven wheel torque message, engine status message or transmission gear lever position message from the PCM (sent through the GWM) contains "faulted" or "invalid" instead of the actual information.
This DTC may also be set if SODL or SODR (aka: BLIS modules) receives invalid network data from the PCM.
I suggest running a self-test of the SCCM and see if any more DTCs arise. There could be any number of issues. There are many faults that result in inoperable cruise control.
continHill Descent Control is controlled by the ABS module. A self-test of the ABS module might help as well.
This DTC sets in continuous memory if the accelerator pedal position message, brake pedal message, driven wheel torque message, engine status message or transmission gear lever position message from the PCM (sent through the GWM) contains "faulted" or "invalid" instead of the actual information.
This DTC may also be set if SODL or SODR (aka: BLIS modules) receives invalid network data from the PCM.
I suggest running a self-test of the SCCM and see if any more DTCs arise. There could be any number of issues. There are many faults that result in inoperable cruise control.
continHill Descent Control is controlled by the ABS module. A self-test of the ABS module might help as well.
I ran a test of the sccm and got The following on demand dtc is u2101-00 I ran that one while the truck was running in park. While in acc mode in continuous memory dtcs I got u2101-00, b1380-09 and b137f-09.
Any idea on what that might mean?
U2101:00 Control Module Configuration Incompatible: No subtype information
Description:
This DTC sets if the steering wheel switches do not match the switch function configuration data in the SCCM. CHECK the parts catalog and CONFIRM that the correct SCCM and steering wheel control switches are installed in the vehicle. INSTALL the correct components, as necessary.
Possible Causes:
Description:
Set by the SCCM when the RH lower or RH steering wheel switches are stuck for
more than 2 minutes during normal operation.
Possible Causes:
Description:
A continuous and on-demand DTC that sets when one or more of the cruise control switches are stuck.
Possible Causes:
Could also be a cruise control switch failure. Less common of an issue than the clockspring. Unlikely you would have a failure of both side switches at the same time.
Could be an issue with the SCCM but that would be the next thing I would look at after the clockspring. Any problems with wipers?
Doubt is is anything like a TR sensor or PCM. You would likely be having a lot more issues than just cruise control.
A check of properly working brake lights would eliminate the BPP switch.
Description:
This DTC sets if the steering wheel switches do not match the switch function configuration data in the SCCM. CHECK the parts catalog and CONFIRM that the correct SCCM and steering wheel control switches are installed in the vehicle. INSTALL the correct components, as necessary.
Possible Causes:
- Incomplete PMI procedure on a recently serviced module
- Incompatible As-built data
- Bad SCCM module
Description:
Set by the SCCM when the RH lower or RH steering wheel switches are stuck for
more than 2 minutes during normal operation.
Possible Causes:
- Steering wheel switch
- Wiring, terminals, or connectors
- Clockspring
- SCCM
Description:
A continuous and on-demand DTC that sets when one or more of the cruise control switches are stuck.
Possible Causes:
- Wiring, terminals, or connectors
- Cruise control switch
- Digital TR sensor
- PCM
- SCCM
- BPP switch
Could also be a cruise control switch failure. Less common of an issue than the clockspring. Unlikely you would have a failure of both side switches at the same time.
Could be an issue with the SCCM but that would be the next thing I would look at after the clockspring. Any problems with wipers?
Doubt is is anything like a TR sensor or PCM. You would likely be having a lot more issues than just cruise control.
A check of properly working brake lights would eliminate the BPP switch.
Trending Topics
For codes u 2101 and b 1380 done in Acc mode, you very likely generated those codes falsely, by using the Acc mode as a result.
The b1380 code is the ign. sw position.
The u 2101 is a reaction to that as >>unidentified data. Switching the Ign on and off while the system is reacting to a precious switch position leaves the system "hanging"
I have already creates these reaction and learned from it.
In the Dash in Engineering Mode, there is a data position for codes set. If none are set it says 'none. If any are set, it tells you how many but not their codes because the coded are not for the Engine but the rest of the system.
.
Go with the b 136f code, only. a left switch pack fault.
The more you see, the more confusion until the codes descriptions are considered.
I can't stress enough, these vehicle are way beyond the owners'' ability to trouble shoot unless there is wide experience in computer operation.
Just having FORSCAN to >see things< is not enough, in difficult cases.
That is why your here for help.
Good luck.
The b1380 code is the ign. sw position.
The u 2101 is a reaction to that as >>unidentified data. Switching the Ign on and off while the system is reacting to a precious switch position leaves the system "hanging"
I have already creates these reaction and learned from it.
In the Dash in Engineering Mode, there is a data position for codes set. If none are set it says 'none. If any are set, it tells you how many but not their codes because the coded are not for the Engine but the rest of the system.
.
Go with the b 136f code, only. a left switch pack fault.
The more you see, the more confusion until the codes descriptions are considered.
I can't stress enough, these vehicle are way beyond the owners'' ability to trouble shoot unless there is wide experience in computer operation.
Just having FORSCAN to >see things< is not enough, in difficult cases.
That is why your here for help.
Good luck.
I thought that was a possibility, that is why I mentioned weather it was running or not. Thank you for the clarification. I think my plan will be to remove the steering wheel and check the harness from the cruise buttons for any damage, and move forward from there.







