2013 CM2250 cranks over no start J1939 failure

[Kingcali111]

Hello all, my 2013 peterbilt 386 have a issue with no start, it cranks over but doesn’t fire up. And the hours and odometer says dash dash dash all over and the DEF gauge is flashing red. I have checked all the fuses outside and inside, checked the batteries and cleaned the terminals. And on the little screen inside it says J1939 failure and for abs it says the same J1939 failure.

Can yall share your experiences on this, Its making me scratch my head bad lol

[Rawze]

is there a red check engine light on in the dash?.

[Kingcali111]

No sir there isn’t no cel, i tried these things
Swapped all the mega fuses, clean the batteries
Swapped the ecm and relays
Checked the fuses inside and outside ones, nothing solved so far

[Rawze]

(01-08-2025 )Kingcali111 Wrote:  No sir there isn’t no cel, i tried these things
Swapped all the mega fuses, clean the batteries
Swapped the ecm and relays
Checked the fuses inside and outside ones, nothing solved so far

use insite software to monitor oil and fuel pressures while cranking.

if there is not enough fuel pressure, then the engine will not even try to fire the injectors.

[Kingcali111]

It doesn’t connect to insite cuz of no power to the diag port either

[Rawze]

(01-08-2025 )Kingcali111 Wrote:  It doesn’t connect to insite cuz of no power to the diag port either

then you need to solve that problem first. Key-on position should provide power to the port, ecm, and everything else.

[tree98]

(01-08-2025 )Kingcali111 Wrote:  It doesn’t connect to insite cuz of no power to the diag port either

That could be just a blown fuse.

[Bengy88]

Had a kw t880 last week with the exact same issue you have and it was a faulty ignition switch. But it could be anything from the ignition switch to one of the fuse boxes being bad. There are also a few threads around where loose connections on the firewall caused issues like this….. especially on peterbilt trucks. Have you verified power at each leg in your fuse panels? You also may want to verify all grounds

[APC]

It sounds like you may have a short on your J1939 datalink wires. the steps i would take to troubleshoot this situation is to use a Nexiq USB Link 2/3 to connect to the truck with your laptop, and use nexiq's device tester app in order to determine what protocol is damaged/disturbed. dont quote me on this, but for a 2013 pete 386 there should only be J1708 and J1939:Channel1... no other datalinks in that truck as far as my knowledge...

once you figure out which datalink is disturbed, then you can try to troubleshoot the problem by measuring your voltage on the datalink wires in your diagnostic plug on the truck... look up a pinout for deustch 9 pin for J1939, and the 2 1939 datalink wires should be somewhere in the area of 2.3-2.8 Volts on each wire of the paired datalink wires (CAN High and Low)...

based on what you see, you can try to either trace wires to find a short/open circuit, or disconnect the modules one by one to see if one of the modules went bad and are disturbing the J1939/1708...

another thing worth mentioning, is that a missing/damaged terminating resistor can cause the same issue...

cant guarantee these steps will 100% fix your issues, but these are worth checking to try and guide yourself in the right situation