The diagnostic code for the special instruction is logged in order to report the configuration status of the data link. The diagnostic code for the special instruction does not check the physical condition of the data link.
- Incorrect personality module code
- Incorrectly programmed configuration parameter
- Incorrect module or display on the data link
- Damaged data link wiring
Use this procedure in order to troubleshoot a diagnostic code for a special instruction. Use this procedure if one of the following diagnostic codes are active.
Diagnostic Trouble Codes | ||
---|---|---|
J1939 Code and Description | Conditions that Generate the Code | System Response |
5576-14 Aftertreatment #1 Identification Number Module : Special Instruction | The Electronic Control Module (ECM) has identified a communication problem with the aftertreatment identification device. | The code is logged. |
5577-14 Aftertreatment #2 Identification Number Module : Special Instruction | The ECM has identified a communication problem with the aftertreatment identification device. | The code is logged. |
Test Step 1. Check for an Associated -9 Code
- Establish communication between the Caterpillar Electronic Technician (ET) and the ECM.
- Download the "Product Summary Report" from the engine ECM before performing any troubleshooting or clearing diagnostic trouble codes.
- Check the report for a -9 code that is associated to the special instruction that is logged.
Expected Result:
A -9 code is not logged.
Results:
- OK - An associated -9 code is not logged. Proceed to Test Step 2.
- Not OK - An associated -9 code is logged.
Repair: Repair all associated -9 codes before continuing with this procedure. Refer to Troubleshooting, "Data Link - Test".
If a -14 code is still present after resolving the -9 code, proceed to Test Step 2.
Test Step 2. Check the Personality Module Code for Compatibility with the Application
- Connect the appropriate ECM to Cat ET.
- Select the ECM connection that is related to the logged code.
- Check if the personality module code is valid for the application.
Results:
- The code is valid for the application. - Proceed to Test Step 3.
- The code is not valid for the application. -
Repair: Obtain the correct flash file and update the ECM. Clear all logged codes and return to service.
STOP
Test Step 3. Check the Configuration Parameters
Check the configuration parameters in order to ensure that the parameters are programmed correctly.
Results:
- OK - The parameters are programmed correctly. Proceed to Test Step 4.
- Not OK - The parameters are not programmed correctly.
Repair: Program the parameters to function with the other modules on the data link. Clear all logged codes and return to service.
STOP
Test Step 4. Check for Incompatible Control Groups on the Data Link
- Obtain the engine's "As Shipped" data in TMI.
- Check the parts breakdown for the part numbers of the control groups and the monitor groups that are on the data link.
- Confirm that the control groups that are installed on the data link are compatible with the part numbers from the parts breakdown in TMI.
Expected Result:
At least one control group is incompatible.
Results:
- OK - One or more control groups are incompatible.
Repair: Replace the control group with a control module that is compatible. Verify that the problem has been resolved.
STOP