20491053 Volvo.Penta Pinion

Table 1
J1939 Code and Description CDL Code and Description Comments
639-9
J1939 Network #1 : Abnormal Update Rate 247-9
J1939 Network #1 : Abnormal Update Rate Communication has been lost to one or more of the devices on the datalink. If multiple devices are not communicating, there is likely a problem with the data link wiring, power, or ground circuits.
639-14
J1939 Network #1 : Special Instruction 247-14
J1939 Network #1 : Special Instruction The affected Electronic Control Module (ECM) is missing expected parameters.
1231-9
J1939 Network #2 : Abnormal Update Rate 2348-9
J1939 Network #2 : Abnormal Update Rate Communication has been lost to one or more of the devices on the datalink. If multiple devices are not communicating, there is likely a problem with the data link wiring, power, or ground circuits.
1231-14
J1939 Network #2 : Special Instruction 2348-14
J1939 Network #2 : Special Instruction The affected ECM is missing expected parameters.
1235-9
J1939 Network #3 : Abnormal Update Rate 5856-9
J1939 Network #3 : Abnormal Update Rate Communication has been lost to one or more of the devices on the datalink. If multiple devices are not communicating, there is likely a problem with the data link wiring, power, or ground circuits.
1235-14
J1939 Network #3 : Special Instruction 5856-14
J1939 Network #3 : Special Instruction The affected ECM is missing expected parameters.
Table 2
Associated Codes
J1939 Code CDL Code
5965-5 3838-5
5965-6 3838-6
5966-6 3965-6 If the Cat® Electronic Technician (ET) will not communicate with the ECM, refer to Troubleshooting, "Electronic Service Tool Does Not Communicate" before you begin this procedure. The procedure verifies that electrical power is being supplied to the ECM and to the service tool connector.
Table 3
Cat® ET Diagnostic Code Cross Reference to Wiring Schematic
Code Description Data Link
J1939 Network #1 Can A
J1939 Network #2 Can B
J1939 Network #3 Can C -9 Detected Problems:Device 1 is unable to communicate on the data link.
Device 1 cannot communicate with other devices on the data link, but can communicate with the service tool, indicating a problem with the data link wiring.Device 1 is unable to communicate with Device 2 on the data link.
Device 1 cannot communicate with Device 2, indicating a problem with the data link wiring, power or ground circuit, or Device 2.Note: If a 639-9 or 247-9 code is active and the "System Communication Status" indicates a communication problem with the "Aftertreatment #1 DEF Sensor", confirm that the "Aftertreatment #1 DEF Quality Sensor Installation Status" configuration parameter is programmed properly.The "Aftertreatment #1 DEF Quality Sensor Installation Status" parameter must be programmed to "Not Installed", if equipped with a DEF header having a 3-pin connector without an internal DEF quality sensor.-14 Detected Problems:Device 1 is unable to obtain a network address on the data link.
Device 1 is trying to claim the same address as another Device. An example of this is 2 devices being configured the same.Device 1 detects a failed address claim from Device 2 on the data link.
Device 1 detects that Device 2 is trying to claim the same address as another device.Device 1 is not receiving all expected parameters from Device 2 on the data link.
A component is configured as installed in the device, but is not installed on the application.
The incorrect component is installed.
The incorrect software file has been installed.The A6 ECM uses a 100 Mbps Ethernet data link for various service and application functions. Depending upon the application, the Ethernet may be used for flashing, retrieving product status reports, and other various data communications.Reference: For Ethernet troubleshooting assistance, refer to Special Instruction, M0080663.Reference: Refer to the Schematic for locations of connectors and pins for electrical check outs.
Illustration 1 g06380985Recommended Actions
Table 4
Troubleshooting Test Steps Values Results
1. Check for Associated Codes
A. Establish communication between Cat ET and the ECM. Refer to Troubleshooting, "Electronic Service Tools", if necessary.
B. Download the "Warranty Report" from the ECM before performing any troubleshooting or clearing trouble codes.
C. Troubleshoot any associated codes that are present before continuing with this procedure.
Associated Codes
Result: An associated trouble code is not active or logged.
Proceed to Test Step 2.
Result: An associated code is active or logged.
Repair: Troubleshoot the associated codes before continuing with this procedure. Refer to Troubleshooting, "Diagnostic Trouble Codes" to troubleshoot the associated diagnostic code.
2. Use the "System Communication Status" to Determine the Communication Issue
A. In Cat ET, click the "Diagnostics" tab on the tool bar.
B. Select the "System Communication Status" option from the drop-down list.
Note: The "Aftertreatment #1 Intake NOx Level Sensor" is displayed as "Aftertreatment #1 Information #1" in some versions of software.
Component Identified
Result: A -9 code is active.
Repair: Refer to the above -9 detected problems for more information.
Proceed to Test Step 6.
Result: A -14 code is active.
Repair: Refer to the above -14 detected problems for more information.
If the NOx sensors are listed as ECM 2, proceed to Test Step 3.
For all other components, proceed to Test Step 4.
3. Check the Part Number of the Component
A. Locate the part number of the component that was identified by the "System Communication Status". Check to see if the part number is correct for the application.
Part Number
Result: The part number is correct for the application.
Proceed to Test Step 4.
Result: The part number is incorrect for the application.
Repair: Replace the component with the correct part number. Refer to Special Instruction, REHS8151 for special handling instructions if replacing a NOx sensor.
Proceed to Test Step 11.
4. Check the Programmable Parameters
A. Navigate to the configuration screen in Cat ET.
B. Identify the component that logged the -14 code.
C. Determine if the component is configured correctly for the application.
Configuration