Table of Contents
Advertisement
WG1605-G-E3,WG1605-L-E3,WG1605-GL-E3, DM
[3] SET UP AND PROCEDURE
(1) Overview
This manual is intended to be used as an aid for KUBOTA LSI engine customers. Certain portions of this manual
are only intended for use by the KUBOTA LSI engine customers to understand the fault detection system. This section
of the manual defines the diagnostics and recommended troubleshooting procedures associated with an EControls
Global Control Platform (GCP) engine control module (ECM) for use on industrial and heavy-duty gas engines.
Kubota LSI engines use EControls diagnostic software to make the diagnosis of failure.
(2) Using the GCP Diagnostic Display Tool
Fault Code Broadcast
All diagnostic trouble codes are broadcast through
EDIS for display on a PC. EDIS can acquire the data
from the ECM through a protocol; CAN using the
EControls Inc. Proprietary Protocol (ECIPP).
Faults may also be acquired over the CAN1 network
through CAN J1939-based scan tools or multi-function
display units.
Diagnostic Trouble Codes
The numeric diagnostic trouble codes assigned to
the faults in this manual are cross-referenced to SAE's
"Recommended Practice for Diagnostic Trouble Code
Definitions" (SAE J2012). While these codes are
recommended, customers may define their own codes
by assigning a new number to the flash code in the
diagnostic calibration. This will assign both the DTC as
displayed in EDIS as well as the flash code output on the
MIL output pin. EDIS may be used to connect to the GCP
using either RS232 (serial) or Controller Area Network
(CAN) communication protocols.
Serial Network
Fault code information can only be acquired through
a PC tool compatible with ECIPP.
CAN
The GCP supports SAE J1939 CAN based
diagnostic support. This includes:
• DM1: Active Diagnostic Trouble Codes
• DM2: Previously Active Diagnostic Trouble Codes
• DM3: Diagnostic Data Clear/Reset of Previously
Active DTCs
• DM4: Freeze Frame Parameters
• DM5: Diagnostic Readiness (bytes 1, 2, and 3 are
supported)
• DM11: Diagnostic Data Clear/Reset For Active
DTCs
• DM12: Emissions-Related Active Diagnostic Trouble
Codes
• DM19: Calibration Information
All diagnostic trouble codes broadcast over CAN1
will be according to SAE J1939 DM1 and DM2. MY08
MGCP ECUs are compliant with J1939 OBD-M,
supporting the Diagnostic Messages above as well as
user indicators and CAN data defined in the OBD-M
protocol.
Faults available for broadcast and their respective
SPN/FMI numbers are dependent on the application and
engine calibration. There are 4 CAN SPN/FMI lists
available in the GCP software set, contact EControls for
a list of CAN SPN/FMIs.
The data capture at the occurrence of a fault, known
in the ECM as fault snapshot (FSS), is available upon
DM4 request. The following bytes are supported for DM4
if configured in the ECM software:
• Byte 1: Freeze Frame Length
• Byte 2-6: SPN, FMI, SPN Conversion Method, and
Occurrence
• Byte 7: Manifold Absolute Pressure
• Byte 8-9: Engine Speed
• Byte 10: Engine Load (MAP based estimate)
• Byte 11: Engine Coolant Temperature
• Byte 14: # of starts since fault was last
• Byte 15: Index into FSS_storage table for Fault Snap
Shot retrieval.
Resetting active and previously active DTCs is
handled through DM11 and DM3, respectively. DM1 and
DM2 lamp indicators are assigned to each fault based on
the fault's diagnostic action as defined in the calibration.
The lamps are assigned based on the configuration
outlined in Table 1.
Table 1: J1939 Diagnostic Lamp Configuration
ECM Diagnostic Action
MIL
Soft Warning
Hard Warning, Low Rev Limit,
Shutdown
Power Derate 1 & 2
Forced Idle
1-30
ECM SYSTEM
J1939 Lamp
MIL
Amber
Red Stop
Protect
None (use in combination with
other action)
KiSC issued 12, 2016 A
Hide quick links:
Advertisement
Table of Contents
