Make: Detroit
Engine: DD15 GHG17 (2017 & Newer)
PID: N/A
SPN: 191
FMI: 19
Description: Transmission Output Speed Shaft Signal is Erratic
Troubleshooting:
DESCRIPTION:
Transmission output shaft speed signal is erratic.
MONITORED PARAMETER:
Controller Area Network (CAN) communication.
TYPICAL ENABLING CONDITIONS:
Always enabled
MONITOR SEQUENCE:
None
EXECUTION FREQUENCEY:
Always enabled
TYPCIAL DURATION:
Two seconds
DASH LAMPS:
MIL
VERIFICATION:
Engine idle: one minute.
POSSIBLE CAUSES:
1. Faulty Controller Area Network (CAN) line.
2. CPC needs reprogramming.
Make: Detroit
Engine: DD15 GHG17 (2017 & Newer)
PID: N/A
SPN: 247
FMI: 1
Description: Motor Control Module Engine Hours Data Lower than Expected
Troubleshooting:
NOTE: The common powertrain controller (CPC) digital outputs have the SPN as some motor
control module (MCM) faults. The diagnostic service tool makes the distinction between the
MCM and CPC when diagnosing a fault.
POSSIBLE CAUSES:
1. MCM engine hours data higher than expected.
2. After reprogramming MCM.
3. After reprogramming CPC.
4. CPC or MCM internal clocks not matching
Make: Detroit
Engine: DD15 GHG17 (2017 & Newer)
PID: N/A
SPN: 247
FMI: 9
Description: Motor Control Module Engine Hours Data Not Received or Stopped Arriving
Troubleshooting:
NOTE: The common powertrain controller (CPC) digital outputs have the SPN as some motor
control module (MCM) faults. The diagnostic service tool makes the distinction between the
MCM and CPC when diagnosing a fault.
POSSIBLE CAUSES:
1. MCM engine hours data higher than expected.
2. After reprogramming MCM.
3. After reprogramming CPC.
4. CPC or MCM internal clocks not matching.
Make: Detroit
Engine: DD15 GHG17 (2017 & Newer)
PID: N/A
SPN: 247
FMI: 10
Description: Motor Control Module Engine Hours Data Increasing at an Implausible Rate
Troubleshooting:
NOTE: The common powertrain controller (CPC) digital outputs have the SPN as some motor
control module (MCM) faults. The diagnostic service tool makes the distinction between the
MCM and CPC when diagnosing a fault.
POSSIBLE CAUSES:
1. MCM engine hours data higher than expected.
2. After reprogramming MCM.
3. After reprogramming CPC.
4. CPC or MCM internal clocks not matching.