CAN communication errors MX-13 epa13

[Notch]

Maybe it's worth mentioning since it's a similar circuit setup, but I've run into a number of red engines that have thrown J1939 communication codes, namely VGT communication codes, stemming from the mechanical VGT veins in the turbo being seized up. What would happen is the ECM would command vein position and the actuator wouldn't be able to move them, which would cause the motor portion of the actuator to pull enough amperage that it would pull power away from the logic/communication part of the actuator, since the logic and motor parts share the same power and ground wires, and this would cause the logic part to momentarily turn off and back on while the key was on. This power cycle of the actuator would cause the ECM to throw J1939 communication VGT codes. I don't remember if there were any corresponding data codes, but it's a possibility if you're power cycling a CAN node that it could corrupt the data line long enough to store other DTC's.

Otherwise, without looking at any wiring diagrams or service info, I wonder if you could go through the other sensors/modules that are throwing DTC's and unplug them individually and then clear codes to see if one of them being unplugged would make all of the other codes go inactive. Thinking along the lines of them all being on the same power sources, grounds, or communication bus, an internally shorted sensor/module can pull down an entire circuit and that would help narrow it down.