Truck wont fire up no bus code on odometer

To do self diag on a pt u need to start with ignition off. Hold trip button in for the odometer keeping trip button held down turn ignition key to run then release trip. This will also run a self test on instrument cluster. Codes will be displayed in the odometer at the end of test

The BUS is not part of the PCM/ECM it is on the body control module (BCM). It effects radio and dash most noticeably. Has no effect on powertrain.

make sure wires to battery are tight and making good contact

Just bought a 2013 dodge avenger, literally yesterday. Test drove fine twice,, drove all over town for license and registration, multiple erands. No problems. I got to work and went to leave for lunch and was introduced to the no bus code. Left me stranded the very day i purchased it,, only 25000 miles. Is this problem simple enough to weather or is this the brightest red flag to take it back?

Check for a faulty crank sensor. Sounds strange, but we found this out the hard way in the dealerships,many years ago. Following the trouble tree usually lead to pcm replacement, and it still wouldn't run.

well :no bus: means that the infomation panell is not getting a signal check the harness below the odometer. I guess the car is running fine, if not then its the ecu itself.

No bus error code has nothing to do with your fuse panel this is a ECM /ECU error code... sorry but get ready to spend some money for a new ECM

fuel pump or ignition module

From the official Durango shop manual......(abbreviated)

Self Diagnosis Test

Vehicle key position is OFF ,or able to pull key out.
Hold in the trip odometer button (dont release yet)
Turn key to the ON position (one notch), but DON'T try to start the engine
Continue holding the trip button for about 10-12 seconds until CHEC appears in the odometer display
Release the trip button.
Series of three digit numeric failure codes may appear.
If no failure message appears, the self diagnostic test will proceed as described in step 6


Code Chart

110- cluster CPU,RAM,EEPROm failure, replace cluster

900-CCD data bus not operational, check CCD data bus connections at cluster, check the cluster fuses,check the CCD data bus bias, cehck the CCD data bus voltage, check the CCD data bus terminations.

920-cluster is not recieving a vehicle speed message from the PCM, check PCM software level and reflash if required, use the ($2500+) DRBIII scan tool to verify the vehicle speed message is being sent by the PCM

921-the cluster is not recieveing a distance pulse message from PCM,check PCM software level and reflash if required, use the ($2500+) DRBIII scan tool to verify the distance pulse message is being sent by the PCM

940-the cluster is not recieving an airbag lamp-on message from the ACM, check the CCD data bus connections at the ACM, check the ACM fuse.

950-cluster not recieving an ABS lamp-on message from the CAB, check CCD data bus connections at the ACM, check the ACM fuse.

960- clsuter not recieving a PRND21 message from the TCM, check the CCD data bus connections at the TCM, check the TCM fuse.

999-An error has been discovered, record the failure message, depress the trip odometer reset button to continue the Self-Diagnostic Test

Step 6
Instrument cluster will test each segment of the odometer (all first, then each one seperately)

Step 7
Bulb test

Step 8
Gauge test

Step 9
test completed

The instrument cluster will return to normal operation at the completion of test, if ignition switch turned off, or a vehicle speed message indicating movement recieved from the PCM on the CCD data bus.

Hope that help you or anyone else in future.

It sounds like it jumped time