EMR 4

CAN BUS specification

Customer
Version 02_34
©Deutz AG
 EMR 4 CAN BUS Specification
Overview

1. SAE J1939-Standard CAN Messages 4

2. Engine Send Messages 4
2.1. EEC1:.................................................................................................................. 4
2.2. EEC2:.................................................................................................................. 6
2.3. EEC3 ................................................................................................................... 7
2.4. EEC4 ................................................................................................................... 8
2.5. Engine Temperature: .......................................................................................... 9
2.6. Engine Fluid Level / Pressure:............................................................................ 9
2.7. Inlet / Exhaust Conditions ................................................................................ 10
2.8. Ambient Conditions .......................................................................................... 11
2.9. Vehicle Electrical Power .................................................................................. 11
2.10. Fuel Economy ............................................................................................... 12
2.11. Fuel Consumption......................................................................................... 12
2.12. Engine Hours/Revolutions ............................................................................ 13
2.13. Cruise Control / Vehicle Speed .................................................................... 14
2.14. Software ID................................................................................................... 15
2.15. Engine Configuration ................................................................................... 17
3. Engine Receive Messages 21
3.1. TSC1TE Message and derivatives .................................................................... 21
3.2. Engine Protection ............................................................................................. 25
3.3. Engine Stop request .......................................................................................... 27
3.4. Function mode control ...................................................................................... 29
4. Diagnostic Messages 30
4.1. Diagnostic Readiness (DM5) / Number of faults ............................................ 30
4.2. Active faults ( DM 1 )....................................................................................... 32
4.3. Passive Faults (DM2) ....................................................................................... 34
5. Proprietary EMR4 Specific CAN Messages based on SAE - J1939 41
5.1. Send messages .................................................................................................. 41
5.1.1. Measured Data 1 ....................................................................................... 41
5.1.2. Measured Data 2 ....................................................................................... 42
5.1.3. Measured Data 3 ....................................................................................... 43
5.1.4. Measured Data 4 ....................................................................................... 44
5.1.5. Measured Data 8 ....................................................................................... 45
5.1.6. Measured Data 9 (fan data) ..................................................................... 47
5.1.7. Limitation ................................................................................................. 48
5.1.8. State of Inputs 1 ........................................................................................ 51
5.1.9. State of Outputs1 ...................................................................................... 52
6. Exhaust After Treatment Send Messages: 53
6.1. AT1TI1 Urea Tank ........................................................................................... 53
6.2. AT1S Aftertreatment 1 Service ........................................................................ 53
6.3. AT1IG2 Catalyst Upstream Temperature......................................................... 53
6.4. AT1OG2 Catalyst Downstream Temperature .................................................. 54
6.5. DPFC 1 ............................................................................................................. 54
6.6. AT1IMG ........................................................................................................... 57
6.7. AT1DOC .......................................................................................................... 57
6.8. DPF Burner Pressure and Temperature ............................................................ 58
6.9. DPF Test Monitor (optional) ............................................................................ 58

Page 2 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
6.10. DPF History Data ......................................................................................... 60
6.11. EPA1 ............................................................................................................. 61
6.12. EPA2 ............................................................................................................. 61
7. Exhaust After Treatment Receive Messages: 63
7.1. CM1 – Receive Message .................................................................................. 63
7.2. DPF Control Receive message ......................................................................... 64
8. CAN Bus Error Diagnostics 64
8.1. Setpoint sources ................................................................................................ 65
9. Appendix 1: Multipacket Transport 68
10. Appendix 2: Lamp status 70
11. Appendix 3: Error codes, SPN, DTC 71
12. Appendix 4: Acknowledgment 73
13. Appendix 5: Hardware Information CAN 73

Page 3 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

1. SAE J1939-Standard CAN Messages

The following messages are described in the standard SAE J1939.

SAE-J1939/21
SAE-J1939/71
SAE-J1939-73
DIN ISO 11898

All send messages are available on the Bus also after switching Ignition Key off till
EMR4 resets itself.
This document describes the overall can functionality, however not all of these are
available in every application.

Message IDs if named explicitly are common to SAE J1939 Standard Message IDs,
special applications may vary.

2. Engine Send Messages

2.1. EEC1:

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Engine 3 0 0 (18) F0 04 00 20ms 0C F0 04 00
Electronic
Control 1

Byte Data Comment

Byte 1 Status EEC1 Bits 1 to 4 Engine / Retarder torque mode
Bits 5 to 8 not defined
Byte 2 Requested engine torque in % 1% /Bit, Offset -125%, indicated torque,
related to Mdmax i.e. 0xCDh means 205-125 = 80% of Mdmax
Byte 3 Actual Engine torque in % 1% /Bit, Offset -125%, indicated torque,
related to Mdmax i.e. 0xCDh means 205-125 = 80% of Mdmax
Byte 4-5 Engine speed 0,125 rpm /Bit
Byte 6 Source address of the controlling 0x00h if EMR4 controls the engine torque
device for engine torque else the source address of the TSC1message
identifier which is controlling the torque
Byte 7 Engine starter mode s. separate list
Byte 8 Engine demand percent The limiting torque of the gearbox is used.
torque TSC1-TE message is the source.
1% /Bit Offset -125%
i.e. 0xCDh means 205-125 = 80% of Mdmax

Page 4 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Byte 1: Engine torque mode:
Output Value
Active Mode Comment
Bits 1-4
0x0 Low Idle Governor / Overrun Overrun means no injection
0x1 Accelerator Pedal
0x6 Transmission Control / TSC1 Torque Speed control / torque control
Control Speed / torque limit control
0x8 Torque Limitation not for fuel limitation (s. 0xC)
engine is working at limited torque (max.
torque curve)
0xC Fuel Limitation

Byte 3:
The value of Byte 3 is the actual engine torque in percent of the reference engine torque
of the message engine configuration.
The torque values of Byte 3, TSC1 and the points 1 to 5 of the message engine
configuration are directly comparable to each other because of the same reference value
Mdmax.

Byte 7: Engine starter mode values:

Output value Start Status
0xF0 start not requested
0xF1 cranking active, gear not engaged
0xF2 cranking active, gear engaged
0xF3 cranking finished
0xF4 cranking inhibited due to engine is already running
0xF6 cranking inhibited due to drive train engaged
0xFC cranking inhibited due to unknown reason (blind meshing, max. duration is over etc.)
0xFF crank control is not available

If there is no "gear engaged switch" information available, the value 0xF2h will not be
sent. Instead of the value 0xF1h will be sent if cranking is active.
0xF6h, "drive train engaged" is the clutch state for EMR4.

Page 5 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.2. EEC2:

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Engine 3 0 0 (18) F0 03 00 50ms 0C F0 03 00
Electronic
Control 2

Byte Data Comment

Byte 1 Status EEC2
Byte 2 Accelerator Pedal Position 0,4 % / Bit,
0xFEh if pedal is in error state,
0xFFh if pedal is not available
Byte 3 Percent Load at current speed 1% / Bit, indicated torque,
= Engine torque related to 0xFEh if percent load cannot be calculated,
max. engine torque at engine speed i,e. because of injection path errors.
Byte 4 Hand Gas Position 0,4 % / Bit,
0xFEh if pedal is in error state,
0xFFh if pedal is not available
Byte 5-8 = 0xFFh - not available

Byte 1: Status EEC2:

Output Value
Status Comment
Bits
Bits 8, 7 Not defined = 11
Bits 6, 5 Road Speed Limit State 00 = not active, 01 = active
Bits 2, 1 Low idle switch 00 = not active, 01 = active,
10 = error,
11= not available

Byte 3
The value of Byte 3 is the actual engine torque in percent of the maximal available
engine torque at the actual engine speed. The maximal available engine torque depends
on the limiting torque curve and engine protection values. Notice that the limiting torque
curves are selectable by switches or CAN (protection messages). This includes the
influence of the boost pressure.TSC1 limits are not considered in this Byte!

The maximal available engine torque is like considered in torque points 1 to 5 of the
engine configuration message.

Page 6 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.3. EEC3

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Engine 6 0 0 (18) FE DF 00 250ms 18 FE DF 00
Electronic
Control 3

Byte Data Comment

Byte 1 Nominal friction 1% / Bit, Offset = –125%, range 0 to 125 %
percent torque
Bytes Exhaust Gas Mass Flow 0,2 Kg/h/bit
6,7
Byte 8 Exhaust After Treatment 00 - Not exceeded the dew point
Bit 1,2 Bank 1 Intake Dew Point 01 - Exceeded the dew point
Bit 3,4 Bank 1 Exhaust Dew Point 10 - Error
Bit 5,6 Bank 2 Intake Dew Point 11 - Not available (If SCR control is not
Bit 7,8 Bank 2 Exhaust Dew Point available in the system)
Byte 1
This data is a percentage value related to reference max. torque value Mdmax defined in
the message engine configuration.
The nominal friction depends on the engine speed and the engine temperature.

Page 7 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.4. EEC4

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Engine 6 0 0 (18) FE BE 00 On Request 18 FE BE 00
Electronic
Control 4

Byte Data Comment

Byte 1,2 Rated engine power 0,5 kW / Bit, Offset = 0
Byte 3, 4 Rated engine speed 0,125 rpm / Bit
Bytes = 0xFFh - not available
5,6,7,8

How to request an EEC4 Message from the ECU

Send a request Message with 3 Bytes Payload stating the Programm Group Number of
EEC4, which is FE BE 00 in hex. You have to switch the first 2 bytes according to Little
Endian standard, e.g. BE FE 00. The request will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18EA0003 8 BE FE 00 FF FF FF FF FF

or

ID DLC Byte1 Byte2 Byte3

18EA0003 3 BE FE 00

The Answer of the ECU will be an EEC4 Message like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8
18FEBE00 8 64 01 A0 41 FF FF FF FF

e.g. 178kw at 2100RPM (Note: both are Little Endian)

Page 8 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.5. Engine Temperature:

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Engine 6 0 0 (18) FE EE 00 1000 18 FE EE 00
Temperature

Byte Data Comment

Byte 1 Coolant temperature 1°C /Bit, Offset -40 °C
Byte 2* Fuel temperature 1°C /Bit, Offset -40 °C
Byte 3, 4* Engine Oil Temperature 0,03125°C, Offset –273°C
Byte 5, 8 = 0xFFh - not available
*: depending on application, filled with FF if not available

2.6. Engine Fluid Level / Pressure:

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Engine Fluid 6 0 0 (18) FE EF 00 500 18 FE EF 00
Level and
Pressure

Byte Data Comment

Byte 1 Fuel delivery pressure 4 kPa/Bit, 1/25bar /Bit
Byte 2,3 not available = 0xFFh - not available
Byte 4 Oil pressure 4 kPa/Bit, 1/25bar /Bit
Byte 5 - 7 not available = 0xFFh - not available
Byte 8 Coolant level 0.4%/Bit, Offset 0%

Byte 1:
The fuel delivery pressure is measured by the low fuel pressure sensor which is located
between the main fuel filter and the Fuel Control Unit (FCU).

Page 9 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.7. Inlet / Exhaust Conditions

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Inlet / Exhaust 6 0 0 (18) FE F6 00 500 18 FE F600
Conditions

Byte Data Comment

Byte 1 Diesel Particulate Filter Inlet 0.5 kPa/bit
Pressure
Byte 2 Boost pressure 2 kPa/Bit = 1/50 bar/Bit
Byte 3 Intake manifold temperature 1°C /Bit, Offset -40 °C
i.e. boost temperature
Byte 5 Air filter differential pressure 0,05 kPa / Bit, range 0 to 12.5 kPa
Byte 6,7 Exhaust gas temperature not used / don't care
Byte 4,8 = 0xFFh - not available

Page 10 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.8. Ambient Conditions

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Ambient 6 0 0 (18) FE F5 00 1000 18 FE F500
Conditions

Byte Data Comment

Byte 1 Barometric pressure (absolute) 0,5 kPa/Bit = 1/200 Bar/Bit
Byte 4, 5 Ambient air temperature (SCR 0,03125 °C / Bit, Offset –273°C
Applications) /
Air Intake Temperature (DPF
Applications)
Bytes = 0xFFh - not available
2, 3 ,6, 7, 8

2.9. Vehicle Electrical Power

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Vehicle 6 0 0 (18) FE F7 00 1000 18 FE F700
Electrical Power

Byte Data Comment

Byte 3, 4 = 0xFFh - not available
Byte 7, 8 Battery potential (voltage) , 0,05 V /Bit
supplied through switched device
Bytes = 0xFFh - not available
1, 2, 5, 6

Page 11 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.10. Fuel Economy

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Fuel Economy 6 0 0 (18) FE F2 00 100 18 FE F200

Byte Data Comment

Byte 1, 2 Fuel rate 0,05 L/h /Bit
Byte 3, 4 Instantaneous fuel economy km/l 1/512 km/L /Bit
Bytes = 0xFFh - not available
5, 6, 7, 8

2.11. Fuel Consumption

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Fuel 6 0 0 (18) FE E9 00 On Request 18 FE E900
Consumption

Byte Data Comment

Byte Total fuel Consumption 0,5 L /Bit
5,6,7,8

How to request a Fuel Consumption Message from the ECU

Send a request Message with 3 Bytes Payload stating the Programm Group Number of
Fuel Consumption, which is FE E9 00 in hex. You have to switch the first 2 bytes
according to Little Endian standard, e.g. E9 FE 00. The request will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18EA0003 8 E9 FE 00 FF FF FF FF FF

or

ID DLC Byte1 Byte2 Byte3

18EA0003 3 E9 FE 00

The Answer of the ECU will be a Fuel Consumption Message like this:
ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8
18FEE900 8 FF FF FF FF 04 03 02 01

e.g. 01020304hex = 8454530L

Page 12 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.12. Engine Hours/Revolutions

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Engine Hours / 6 0 0 (18) FE E5 00 On Request 18 FE E5 00
Revolutions

Byte Data Comment

Byte 1to 4 Total engine hours 0,05h /Bit; Byte1 is LSB, Byte 4 is MSB
Byte 5 to 8 Total engine revolutions 1000r/bit, 0 offset
(Crankshaft)

Total engine hours are only be accumulated when the engine is running!

How to request an Engine Hours/Revolutions Message from the ECU

Send a request Message with 3 Bytes Payload stating the Programm Group Number of
Engine Hours/Revolutions, which is FE E5 00 in hex. You have to switch the first 2
bytes according to Little Endian standard, e.g. E5 FE 00. The request will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18EA0003 8 E5 FE 00 FF FF FF FF FF

or

ID DLC Byte1 Byte2 Byte3

18EA0003 3 E5 FE 00

The Answer of the ECU will be an Engine Hours/Revolutions Message like this:
ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8
18FEE500 8 04 03 02 01 44 33 22 11

e.g. 01020304hex = 8454530Hours, 11223344hex = 287454020000RPMs

Page 13 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.13. Cruise Control / Vehicle Speed

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Cruise Control / 6 0 0 (18) FE F1 00 100 18 FE F1 00
Vehicle Speed

Byte Data Comment

Byte 1 Measured SW1
Byte 2, 3 Wheel based vehicle speed 1 / 256 km/h = 1 / 412 mph
Byte 4 Measured_CC_SW1
Byte 5 Measured_CC_SW2
Byte 6 Cruise Control set speed 1km/h / Bit
Byte 7 State CC not available
Byte 8 Measured idle SW1 Not available

The binary value 11, indicating not available for a switch state will also be sent, when the
switch is disabled by configuration parameters for a special application.
Gray displayed information are actually not available – ignore these data!
If no Wheel Speed Sensor is available, 0 will be send.

Byte 1: Measured SW1:

Output Value
Status Comment
Bits
Bits 4, 3 Parking brake switch 00 = not active, 01 = active,
10 = error, 11= not available
Bits all set to 1= not available
8 ,7 ,6 ,5 ,2 ,1

Byte 4: Measured CC_SW1:

Output Value
Status Comment
Bits
Bits 8, 7 Clutch switch 00 = not active, 01 = active,
10 = error, 11= not available
Bits 6, 5 Brake switch 00 = not active, 01 = active,
10 = error, 11= not available
Bits 4, 3 Cruise control enable switch
00 = CC not enabled by parameter
11 = not available
Bits 2, 1 Cruise control active 00 = CC is not active

Byte 5: Measured CC_SW2:

Output Value
Status Comment
Bits
Bits 8, 7 Cruise control accelerator switch 00 = not active, 01 = active,
10 = error, 11= not available
Bits 6, 5 Cruise control resume /hold switch 00 = not active, 01 = active,
10 = error, 11= not available
Bits 4, 3 Cruise control coast switch (decelerate) 00 = not active, 01 = active,
10 = error, 11= not available
Bits 2, 1 Cruise control set switch not available >> 3 Button Logic

Page 14 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.14. Software ID

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Software ID 6 0 0 (18) FE DA 00 On Request 18 FE DA 00

Byte Data Comment

Byte 1 Number of software identification fields = 01h
Byte 2-8 Software Identification ASCII formatted

How to request a Software ID Message from the ECU

Send a request Message with 3 Bytes Payload stating the Programm Group Number of
Software ID, which is FE DA 00 in hex. You have to switch the first 2 bytes according to
Little Endian standard, e.g. DA FE 00. The request will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18EA0003 8 DA FE 00 FF FF FF FF FF
or
ID DLC Byte1 Byte2 Byte3
18EA0003 3 DA FE 00

Prior to 01.08.2012, the Answer of the ECU will be a Software ID Message like this:
ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8
18FEDA00 8 01 50 38 30 32 35 37 30

Byte 2-8:
The format is PXXXYYY
XXX = Main software identifier.
YYY = Software version identifier.
e.g. Software ID = P802570

Since 01.08.2012, the Format has been changed due to an additional Version Number:
ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8
18FEDA00 8 01 38 30 32 36 34 30 04

Byte 2-8:
The format is XXXYYYZ :
XXX = Main software identifier.
YYY = Software version identifier
Z = Variant version identifier
e.g. Software ID 8026404

Page 15 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Translation of Hex-Code to ASCII Code

Page 16 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

2.15. Engine Configuration

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Engine 6 0 0 (18) FE E3 00 Through 18 FE E3 00
Configuration Multipackage
Message

EMR4 uses mode 2 of the engine configuration message, defined in SAE-J1939-71

chapter 5..4.1

Byte Data Comment

Byte 1,2 Engine speed at idle ( point 1) 0,125 rpm /Bit
point 1 = idle
Byte 3 Percent torque at idle ( point 1) 1% /Bit, Offset = –125%
Byte 4, 5 Engine speed ( point 2) 0,125 rpm /Bit
point 2 = rated speed
Byte 6 Percent torque ( point 2) 1% /Bit, Offset = –125%
Byte 7, 8 Engine speed (point 3) 0,125 rpm /Bit
point 3 = maximal engine torque
Byte 9 Percent torque (point 3) 1% /Bit, Offset = –125%
Byte 10, 11 Engine speed ( point 4) 0,125 rpm /Bit
Byte 12 Percent torque ( point 4) 1% /Bit, Offset = –125%
Byte 13, 14 Engine speed ( point 5) 0,125 rpm /Bit
Byte 15 Percent torque ( point 5) 1% /Bit, Offset = –125%
Byte 16, 17 Engine speed at high idle 0,125 rpm /Bit
engine torque = 0 (point 6) point 6 = high idle
Byte 18, 19 Droop 0,0122% /Bit
Byte 20, 21 Reference engine torque 1 Nm /Bit
(maximum torque of engine torque map) This is a configuration parameter in EMR4
Byte 22, 23 Maximum momentary engine override 0,125 rpm /Bit
speed
Byte 24 Maximum momentary engine override 0.1s /Bit
time limit
Byte 25 Requested speed control range lower limit 10 rpm /Bit
Min. engine speed value for TSC1 messages
Byte 26 Requested speed control range upper limit 10 rpm /Bit
Max. engine speed value for TSC1 messages
Byte 27 Requested torque control range lower limit 1% /Bit, Offset = –125%
Min. engine torque value for TSC1 messages
Byte 28 Requested torque control range upper limit 1% /Bit, Offset = –125%
Max. engine torque value for TSC1 messages

Byte 18,19 Droop:

Droop = (nmax - nrated) / nrated * 100 % n = speed, resolution droop 0,0122% /Bit

Page 17 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Bytes 20, 21: Reference torque
This parameter is the 100% reference value for all defined indicated engine torque
parameters. It's only defined once and doesn't change if a different engine torque map
becomes valid.

Data update
The values will be modified in following cases
- the torque map has been changed
- Gain has been modified / a new droop is selected
- power reduction (engine protection) is active.

Boost pressure (smoke limiter), road speed limits or limits set in TSC1 will not modify
the data values.

This message uses more than 8 data bytes, therefore the Multipacket Transport
(Appendix 1) will be used.

The message will be transmitted periodically.

How to use the Engine Configuration Message with TSC1 or Engine Protection:

First you wait for the Engine Configuration Message to be sent, typically every 3
seconds.

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18ECFF00 8 20 1C 00 04 FF E3 FE 00
18EBFF00 8 01 50 14 BC F0 41 C4 E0
18EBFF00 8 02 2E E1 80 25 D4 40 38
18EBFF00 8 03 D0 F0 41 99 01 73 04
18EBFF00 8 04 F0 41 14 41 D3 7D E1

Low Idle Point P1:

Speed @ P1: 1450 => 650 rpm
Percent Torque @ P1: BC => 63 %

Rated Power Point P2:

Speed @ P2: 41F0 => 2110 rpm
Percent Torque @ P2: C4 => 71 %

Rated Torque Point P3:

Speed @ P3: 2EE0 => 1500 rpm
Percent Torque @ P3: E1 => 100 %

Immediate Points P4–P5:

Speed @ P4: 2580 => 1200 rpm
Percent Torque @ P4: D4 => 87 %

Page 18 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Speed @ P5: 3840 => 1800 rpm
Percent Torque @ P5: D0 => 83 %

High Idle Point P6:

Speed @ P6: 41F0 => 2110 rpm

Droop Percent @ P6: 0199 => 5%

Reference Torque for 100 % Value :

Md_Max: 0473 => 1139 Nm

Momentary Over Speed Point P7:

Speed @ P7: 41F0 => 2110 rpm

Momentary Over Speed Time between P6 and P7:

Time P6 > P7: 14 => 2 seconds

Reqest Speed Limit Low: 41 => 650 rpm

Reqest Speed Limit Up: D3 => 2110 rpm

Reqest Torque Low Percentage: 7D => 0 %

Reqest Torque Up Percentage: E1 => 100 %

Based on this Information, the Engine’s Inner Torque Curve can be calculated.

To calculate the specific torque at the current speed, you need the current speed and the
current torque percentage information from EEC1 Message.

Page 19 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

For Example: 1500 rpm and 100% Torque

At this point the inner torque curve has 100% Reference Torque, e.g. 1139 Nm.

Calculation of inner torque at a specific point is a simple linear interpolation between two
points.

Page 20 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

3. Engine Receive Messages

3.1. TSC1TE Message and derivatives

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Torque Speed 3 0 0 (18) 00 00 03 20 0C 00 00 03
Control 1 /
Transmission to
Engine

Byte Data Comment

Byte 1 Control Bits SAE J1939/71, Parameter 3.3.1
Bit 1, 2 Override control mode
Bit 3, 4 Requested speed control condition = 00
Bit 5, 6 Override control priority
Bit 7, 8 Not defined = 00
Byte 2,3 Requested speed / speed limit 0,125 rpm /Bit
Byte 4 Requested torque / torque limit 1% /Bit, Offset –125%
Byte 5-8 Not defined

Byte 1 Bits 1, 2 Override Control Mode:

00 Override disabled – disable any existing control

commanded by the source of this command.
01 speed control, no limits will be changed
Bytes 2 and 3 for requested speed
Byte 4 will be ignored
10 torque control, no limits will be changed
Bytes 2 and 3 will be ignored
Byte 4 for requested torque
11 set limits
´ Bytes 2 and 3 are the limit of speed control.
Byte 4 contents the limit for torque control

Byte 1 Bits 5, 6 Priority Bits

00 Highest Priority
01 High Priority
10 Low Priority
11 Lowest Priority

Page 21 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Byte 4
Torque ranges are shown in the following table:

Message Torque Torque

set point range limit range
TSC1_TE 0% to 125% 0% to 125 % incoming Values < 0 set to 0

How to do a TSC1 Speed Request to the ECU:

Byte 1 should be 01h to choose Mode 1 Engine Speed Request. Byte 2 and 3 are the
requested engine speed multiplied by 8 in little endian format. Byte 4 should be less than
Fah, e.g. you want 1000RPM from the engine multiply with 8, gives you 8000 decimal,
1F40 in hex (big endian). Flip these Bytes to get little endian format, result is 401Fh.
The message will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

0C000003 8 01 40 1F 00 FF FF FF FF

How to do a TSC1 Torque Request to the ECU:

Byte 1 should be 02h to choose Mode 2 Engine Torque Request. Byte 2 and 3 should be
less than FFFAh. Byte 4 is the requested torque percentage with an 125d offset, e.g. you
want 80% Torque from the engine, add 125 dezimal, gives you 205 dezimal, CD in hex.
The message will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

0C000003 8 02 00 00 CD FF FF FF FF

How to do a TSC1 Limitation Request to the ECU:

Byte 1 should be 03h to choose Mode 3 Engine Speed and Torque Request. Like in the
Examples above 1000RPM and 80% Torque Limitation.
The message will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

0C000003 8 03 40 1F CD FF FF FF FF

Note: This Limitation will be active unless the limits are reset / changed to max values
again. The corresponding message will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

0C000003 8 03 FF FA FA FF FF FF FF

Note: These are the highest values judged to be valid by the acceptance filter.They are
unrealistic though FAFF = 8031RPM, 125% Torque.

Page 22 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Normal Operation/Temporary Operation:

We advise our Customers to send TSC1 Request periodically but temporary TSC1
Requests are possible with special function datasets.

In the least case, it is essentially the TSC1 Message does an ordinary hand-shake with the
ECU to state that it has no intention to control the engine any further. This is done by
sending Mode 0, e.g.:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

0C000003 8 00 00 00 00 FF FF FF FF

After this message has been received by the ECU, the message transmission can be
halted without effect on the running engine, although a timeout error may be written to
error memory.

If the TSC1 Message was a Limitation of Speed and Torque with Mode 3, these Limits
have to be reset by the TSC1 Message prior to doing the above mentioned handshake.

In this case the hand shake would look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

0C000003 8 03 FF FA FA FF FF FF FF
0C000003 8 00 00 00 00 FF FF FF FF

Changing between different Control Modes:

A change from Torque Control to Speed Control is possible if there is load on the engine,
e.g. it will not switch in overrun mode to counter a sudden torque gain.
A change from Speed Control to Torque Control is always possible. In general the
requesting device is responsible for a safe and smooth controller mode transition. As the
ECU transmits the current load and speed, it is recommended to use these values initially
when changing the controller mode.

Request Priority:
The data process regarding to the priority bits of TSC1 messages is shown in Fig. 7 of
the SAE-J1939/71 document, i.e. a message with priority 0 will be preferred to a
message with priority 1, 2 or 3. EMR4 uses the standard priority control method.

Request Validation / Acceptance Filter:

All incoming TSC1 messages must pass an Acceptance Filter where the contents are
checked for validity, they will be declared invalid and discarded otherwise.
This check includes the physical value check of requested Torque and Speed .
If ether requested torque is greater then FA or requested Speed is greater then FAFF
(FFFA little endian respective), neither engine speed request nor engine torque request
are valid. Do not exceed these Limits otherwise the engine may idle without any error
message concerning this issue.

Page 23 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Request Evaluation / Combining Limits:

With multiple requests of a kind, i.e. 2 different Speed Requests, the maximum value
will win or the message with the higher Priority. Same with 2 torque Requests.
With multiple requests of other kinds, i.e. 1 Speed Request and 1 Torque Request, the
winner will be selected by a message type depending priority chain. TSC1AE will win
over TSC1TE which will win over TSC1TR (distinguished by their message ID).

With multiple limit requests the lower limits will win over the others.

Limp Home Behaviour:

Timeout Errors can be set 10 Seconds after engine start. If a timeout occurs it can be
ether passive (no TSC1 request while timeout occured) or active (TSC1 Speed or Torque
Request while timeout occured). Passive Errors have no effect, means a valid TSC1
Request will be accepted after a passive timeout. Active Timeouts turn TSC1 invalid as
both speed and torque source thus depending on application Foot Throttle, Hand Throttle
or Limp Home Speed will be used instead. The Governor Mode, e.g. Speed or Torque
Governor will not change in the process. With special application datasets this behaviour
can be changed that TSC1 Requests will be accepted again even after an Active Timeout.
Limitation Requests are accepted regardless of previous timeouts anyways.

Responsibility:
In general when doing requests to the ECU via TSC1 the responsibility lies with the
requesting device. There is no further check if the request is plausible in the current
situation thus the requesting device has to check if the request is plausible.

Page 24 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

3.2. Engine Protection

Name DLC Specific Identifier Repetition Identifier
Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Engine 3 0 0 (18) FF 03 03 100 0C FF 03 03
Protection

This is a Deutz Proprietary Message.

Byte Data Comment

Byte 1 Power reduction 1% /Bit, range 0% to 100%
0% = engine stop
Byte 2 Start Lock Lock status (Engine Start Lock 1):
0x00h = no engine start prohibition
0x01h = engine stops and engine start
prohibition will be active
0xFFh = not defined ( no protection)
Byte 3 to 8 not defined, value is 0xFFh

Depending on the application, ignition key has to be switched of and after run time has to
be exceeded to release start prohibition.

Not all engine protection functions are available in every applications, i.e. engine
shutdown is not allowed for some applications.

Byte 1: Power reduction:

Reduces the max. engine torque.
The base for the percentage value is the max. torque curve 1

0% causes the EMR4 to switch off the engine.

100% means no power reduction.

If there is more than one source for power reduction active, i.e. internal power protection
by temperature and this message, the lowest value (= the highest reduction) will be used.
If there is a timeout of a message the last valid data will be used furthermore for the
calculation.

Byte 2 Start Lock

As long as the start is forbidden, the value 0x01h has to be send. Sending the 0x00h will
release the start lock. This value is used for normal operation with no start prohibition.
It cannot release a start prohibition which is caused by other sources, i.e. internal engine
protection functions or other CAN bus messages.

Start lock Actuators

If the starter is controlled by EMR4 then start prevention means also not cranking, else
cranking is possible. The injection fuel mass will be set to zero

Page 25 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
How to do an Engine Protection Request to the ECU:
Under normal conditions Byte 1 should be 64h which equals 100% engine torque
The message will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

0CFF0303 8 64 00 FF FF FF FF FF FF

Engine Stop and Start Lock will be requested the following way:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

0CFF0303 8 00 01 FF FF FF FF FF FF

while the condition is reset this way:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

0CFF0303 8 64 00 FF FF FF FF FF FF

Note: If the engine has been shut off with Byte 2 set to 1, the engine won't start any more
until Terminal 15 has been switched off and on again.

A 50% torque limitation will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

0CFF0303 8 32 00 FF FF FF FF FF FF

Page 26 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

3.3. Engine Stop request

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Engine Stop 2 0 0 (8) FF 16 ignored 100 08 FF 16 xx
Request

This is a Deutz Proprietary Message.

Byte Data Comment

Byte 1 Engine stop demand 0x00h = no engine stop request
0x01h = engine will be stopped immediately
0x02h = engine will be stopped normally
Byte 2 Start Lock Lock status (Engine Start Lock 2 ):
0x00h = no engine start prohibition
0x01h = engine stops and engine start
prohibition will be active
Byte 3-8 Not Defined = 0xFFh

Byte 1 Engine stop demand

This message allows an engine shutoff additional to the message engine protection. Each
CAN-bus node is able to stop the engine independent from the source address of the
message. This message should not be send periodically.

If at least one engine stop demand has been received the engine will be stopped.

Immediate Shut Off 0x01h will switch off all electrical loads attached to the ECU thus
causing these peripherals to raise fault messages in result. This should not be used
except in case of Emergency. The injection fuel mass will be set to zero until T15 is
toggled.

Normal Shut Off 0x02h will switch off the engine similar to the Engine Stop Switch or
Terminal 15. This is recommended.

Byte 2 Start Lock

This data is as defined in the engine protection message. Here each CAN-bus node is
able to set the start prohibition.
When EMR4 has received a start lock command, it stores the source address of the node
which has activated the start lock, because only the same can bus node can release the
start lock. If more than 1 node has forced a start lock, then all these nodes has to release
the start lock to allow EMR4 to reset the engine start lock 2.
The value 00h is used on two ways. The first way is to use normal operation with no start
prohibition and the other way is to release a start lock which was caused by this
command (byte 2).
It cannot release a start prohibition which is caused by other sources, i.e. internal engine
protection functions or other CAN bus messages.

Page 27 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Start lock actuators
If the starter is controlled by EMR4 then start prevention means also not cranking, else
cranking is possible. The injection fuel mass will be set to zero.

How to do an Engine Stop Request to the ECU:

A normal engine stop request message will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

08FF1603 8 02 00 FF FF FF FF FF FF

An engine stop request with start lock will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

08FF1603 8 00 01 FF FF FF FF FF FF

A reset to both conditions is issued by a message like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

08FF1603 8 00 00 FF FF FF FF FF FF

Note: If the engine has been shut off with Byte 2 set to 1, the engine won't start any more
until Terminal 15 has been switched off and on again.

Page 28 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

3.4. Function mode control

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Function Mode 6 0 0 (18) FF 02 03 100 18 FF 02 03
Control

This is a Deutz Proprietary Message.

This message allows switching to different modes without using external switches.
It depends on the application which options are enabled by configuration parameters.
Each single value for selection can be disabled (i.e. number of selectable constant
speeds).

Byte Data Comment

Byte 1 Number of engine torque map 0= no modification of torque map
1= switch to torque map 1
2= switch to torque map 2
Byte 2 Droop selection, number of droop 0 = no modification of droop
engine speed governor 1 = selects engine speed droop 1
2 = selects engine speed droop 2
Byte 3-8 not used, must be 00x

Default status
Default values are speed droop 1 and torque map 1.

Limp home status

If the primary setpoint source fails (i.e TSC1 Message due to timeout) then the secondary
one (depending on priority order i.e. accelerator pedal or constant speed) will be used for
setpoint calculation. In that case it depends on the application which droop will be used.

How to do a Function Mode Control Request to the ECU:

A request with Torque Map 2, and droop 2 will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18FF0203 8 02 04 00 00 00 00 00 00

Page 29 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

4. Diagnostic Messages

These messages are specified in SAE-J1939-73. There are 12 messages described, but
not all messages are supported from EMR4. A request for non-available messages will be
answered by EMR4 with a negative acknowledgment (NACK). The negative and
positive acknowledgment is shown in Appendix 3.

Messages that require more than 8 data bytes have to be transferred with the
„Multipacket Transport Protocol“ (SAE-J1939-21 ) - see Appendix 1.

4.1. Diagnostic Readiness (DM5) / Number of faults

The number of faults is transmitted on request. There are two kind of faults displayed in
this message - active and previously active faults ( = passive faults).
Active faults are faults that are currently active. Passive faults ( = previously active
faults) are faults which have been active in the past and are not currently active.

Request for reading DM5 (Standard Request)

EMR4 receives this message as a request to send the number of faults, which have
occurred at least once and are active or passive at that moment.

Defaults values for transmission rate and CAN Identifier s. CAN Code Specification.

Data Length: 3 Bytes

Data Page: 0
PDUF : 234
PDUS : EMR4 Device Nr
Parameter group number: 00EA00

Byte Data Comment

Byte 1-3 00 FE CE PGN-Nr. Of message DM5, LSB first

Answer DM5

Data Length: 8 Bytes

Data Page: 0
PDUF: 254
PDUS: 206
Parameter group 65230 (00 FE CE)
number:

Byte Data Comment

Byte 1 Number of active faults
Byte 2 Mode1: Count of passive faults Deutz standard is Mode1
stored in the error memory of EMR4 Applications which have to be compatible
Mode2: Count of all faults (active with EMR2 Controllers use Mode2
faults + passive faults) stored in

Page 30 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
the error memory
Byte 3 OBD Compliance Identifies the OBD compliance of the
responding controller
= 05hex, no OBD
Byte 4-8 not defined don’t care

How to request a DM5 Message from the ECU

Send a request Message with 3 Bytes Payload stating the Programm Group Number of
DM5, which is FE CE 00 in hex. You have to switch the first 2 bytes according to Little
Endian standard, e.g. CE FE 00. The request will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18EA0003 8 CE FE 00 FF FF FF FF FF
or
ID DLC Byte1 Byte2 Byte3
18EA0003 3 CE FE 00

The Answer of the ECU will be a DM5 Message like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8
18FECE00 8 02 01 05 00 00 00 00 00

e.g. 2 Active Faults, 01 Passive Fault, No OBD Compliance

Page 31 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

4.2. Active faults ( DM 1 )

The transmission rate is according to SAE-J1939.

That means:
1. The standard update rate is 1s, if at least one active fault exists.
2. The message will be transmitted immediately, if a fault becomes active or inactive.
3. Within one second only the first change of state of the fault will be transmitted
immediately. If the fault changes his state (active / passive) more than one time
within a second, the DM1-message will be transmitted at the end of the second with
the actual state of the fault.

The following messages will be transmitted if there is only one active fault.

DM1:
Transmission rate: see above
Data Length: variable
Data Page: 0
PDUF: 254
PDUS: 202
Priority: s. Appendix 3
Parameter group 65226 (00FECA)
number:

Byte 1 Lamp state (LS)

Byte 2 Lamp state (LS) reserved =FF
Byte 3, 4 Suspect Parameter Number (SPN)
Byte 5 Bit 6 to 8 SPN
Bit 1 to 5 Failure mode identifier (FMI)
Byte 6 Bit 8 not defined
Bit 1 to 7 Occurrence counter (OC)
Byte 7, 8 = 0xFFh - not defined

LS: see Appendix 2

SPN: see Appendix 3 Error codes
FMI: see Appendix 3 Error codes
OC: The Occurrence Counter displays how often a fault got active since the fault
memory has been cleared the last time.

The following data will be sending once, if the last active fault switched passive and
there is no active fault in the error memory left:
(According to standard SAE-J1939/21 Juli94)
LS=0, SPN= 0, FMI = 0, OC = 0

The Multipackage Transport (SAE-J1939/21 July 94) will be used if there is more than
one active fault. The data stream is:
LS, SPN, FMI, OC, SPN, FMI, OC, SPN, FMI, OC .....etc.

Page 32 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

Single DM1 and Multipackage DM1

Depending on the number of active errors the DM1 is ether send as a single Message or
within the multipackage stream. A single Error will trigger the Single DM1 message to
be sent while anything above will trigger the multipackage method.

A Single DM1 will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18FECA00 8 04 FF 00 54 8B 81 FF FF

A Multipackage DM1 with 2 Errors will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18ECFF00x 8 20 0A 00 02 FF CA FE 00
18EBFF00x 8 01 04 FF 00 54 8B 81 00
18EBFF00x 8 02 9A 6E FB FF FF FF FF

Note: Broadcast Announce Message 18ECFF00 announces the DM1 message.

0A = 10 Bytes to send, 02 = 2 Messages. 18EBFF00 is the message containing the
information

Packet 1:
Byte 2 Lamp Status >> 04 >> warning lamp is on
Byte 4-7: Error Code 1 >> 00 54 8B 81 >> 0101 0100 100 >> SPN 676, FMI 11, OC 1

Byte8+Packet2Byte 2-4: Error Code2 >> 009A6EFB

>> 1001 1010 011 >>SPN 1235, FMI 14, OC 3

How to split these Error Codes into SPN/FMI refer to appendix.

Page 33 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

4.3. Passive Faults (DM2)

Passive faults ( = previously active faults) are faults which have been active in the past
and are not currently active. They are transmitted on request.

Request for reading DM2 (Standard Request)

Data Length: 3 Bytes

Data Page: 0
PDUF : 234
PDUS : EMR4 Device Nr
Parameter group number: 00EA00

Byte Data Comment

Byte 1-3 00 EA 00 PGN-Nr. Of message DM2, LSB first

Answer passive Faults ( Standard DM2 )

If there is only one fault stored:
Data length: 8 Bytes
Data Page: 0
PDUF: 254
PDUS: 203
Parameter group 65227 (00FECB)
number:

Byte 1 Lamp state (LS)

Byte 2 Lamp state (LS) reserved = FF
Byte 3, 4 Suspect Parameter Number (SPN)
Byte 5 Bit 6 to 8 SPN
Bit 1 to 5 Failure Mode Identifier (FMI)
Byte 6 Bit 8 = CM = 1
Bit 1 to 7 Occurrence counter (OC)
Byte 7, 8 not defined, value is 0xFFh

LS: see Appendix 2

SPN: see Appendix 3 Error codes 304
FMI: see Appendix 3 Error codes
CM: SPN Conversation Method
OC: The Occurrence Counter displays how often a fault got active since the fault
memory has been cleared the last time.

The Multipackage Transport (SAE-J1939/21 July 94) is used, if the count of passive
faults in the error memory is higher than one. The format of the data stream is:
LS, SPN, FMI, CM, OC, SPN, FMI, CM, OC, SPN, FMI, CM, OC, SPN, FMI, CM, OC, ...

The following data will be send, if there is no fault stored

SPN = 0, FMI = 0, OC= 0, LS according to actual lamp state.

Page 34 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
How to request a DM2 Message from the ECU

Send a request Message with 3 Bytes Payload stating the Programm Group Number of
DM2, which is FE CB 00 in hex. You have to switch the first 2 bytes according to Little
Endian standard, e.g. CB FE 00. The request will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18EA0003 8 CB FE 00 FF FF FF FF FF
or
ID DLC Byte1 Byte2 Byte3
18EA0003 3 CB FE 00

The Answer of the ECU will be a DM2 Message like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8
18ECFF00x 8 20 0A 00 02 FF CB FE 00
18EB0300x 8 01 04 FF 00 54 8B 81 00
18EB0300x 8 02 9A 6E FB FF FF FF FF

Note: Broadcast Announce Message 18ECFF00 announces the DM2 message.

0A = 10 Bytes to send, 02 = 2 Messages. 18EB0300 is the message containing the
information, which ID 03 (you) has requested previously thus addressed to you with
Message ID 18EB0300.

Packet 1:
Byte 2 Lamp Status >> 04 >> warning lamp is on
Byte 4-7: Error Code 1 >> 00 54 8B 81 >> 0101 0100 100 >> SPN 676, FMI 11, OC 1

Byte8+Packet2Byte 2-4: Error Code2 >> 009A6EFB

>> 1001 1010 011 >>SPN 1235, FMI 14, OC 11

How to split these Error Codes into SPN/FMI refer to appendix.

Page 35 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

4.4. Freeze Frame Parameters (DM4)

A Freeze Frame is defined as the list of parameters recorded at the time a diagnostic
trouble code was captured. They are also described in the error memory specification.
Due to its size on every request only one Freeze Frame will be transmitted. For the first
request for DM4, ECU transmits the freeze frame parameters of the first fault entry of the
error memory. On the second request for DM4, the freeze frame parameters for the
second fault entry will be transmitted and so on.

Freeze Frames aren't available for all kind of faults.

Request for reading DM4 (Standard Request)

Data Length: 3 Bytes

Data Page: 0
PDUF : EAh = 234d
PDUS : EMR4 Device Nr (00)
Parameter group number: 00EA00

Byte Data Comment

Byte 1-3 00 EA 00 PGN-Nr. Of message DM4, LSB first

Answer DM4 : Freeze Frame Parameter

A Freeze Frame contains more than 8 data bytes, therefore the Multipacket
Transport will be used.

Data length
Data Page: 0
PDUF: 254
PDUS: 205
Parameter group number: 65229 (00FECD)
Source Address: EMR2 Device Nr. (00)

Page 36 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Byte Data Comment
Byte 1 Number of the following data bytes 0x10h
Byte 2 DTC (Diagnostic trouble code) Suspect parameter number SPN
Byte1
Byte 3 DTC (Diagnostic trouble code) Suspect parameter number SPN
Byte2
Byte 4 DTC (Diagnostic trouble code) Bits 6 to 8: SPN
Byte3 Bits 1 to 5 Failure Mode (FMI) Bit5 MSB
Byte 5 DTC (Diagnostic trouble code) Bit 8 Conversion Method
Byte4 Bits 1 to 7 Occurrence counter (OC)
Byte 6 =FF not available
Byte 7 Boost pressure 2 kPa/Bit = 1/50 bar/Bit
Bytes 8, 9 Engine Speed 0,125 rpm / Bit
Byte 10 Engine % Load at current speed Actual Engine load indicated 1% / Bit
Byte 11 Engine coolant temperature 1°C /Bit, Offset –40 °C
Byte 12, 13 Vehicle speed 1/256 km/h/ Bit
if data is not available 0xFFh will be
transmitted

Bytes 2 to 5: DTC
DTC and SPN are described in the appendix

If no fault present:
The message above is used too, if there are no fault entry and freeze data available. In
that case the 8 data bytes( no Multipackage Transport necessary then) filled as follow:
Number = 0, DTC = 0, Bytes 6 to 8 = 0xFFh.

Byte Data Comment

Byte 1 Number of the following data bytes Byte 1 = 0x00h if no fault is present
Byte 2 to 5 DTC DTC = 0
Byte 6 to 8 = 0xFFh

Page 37 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
How to request a DM4 Message from the ECU

Send a request Message with 3 Bytes Payload stating the Programm Group Number of
DM4, which is FE CD 00 in hex. You have to switch the first 2 bytes according to Little
Endian standard, e.g. CD FE 00. The request will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18EA0003 8 CD FE 00 FF FF FF FF FF
or
ID DLC Byte1 Byte2 Byte3
18EA0003 3 CD FE 00

Depending on the number of errors, the ECU will answer with the corresponding
Number of DM4 Messages like this:
ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8
18ECFF00x 8 20 1D 00 05 FF CD FE 00
18EB0300x 8 01 10 00 54 8B 81 FF 81
18EB0300x 8 02 9A 6E FB CD EF CC DD
18EB0300x 8 03 10 20 30 40 50 60 70
18EB0300x 8 04 80 90 A0 B0 C0 D0 E0
18EB0300x 8 05 9A FF FF FF FF FF FF

Note: Broadcast Announce Message 18ECFF00 announces the DM4 message.

1D = 29 Bytes to send, 05 = 5 Messages. 18EB0300 is the message containing the
information, which ID 03 (you) has requested previously thus addressed to you with
Message ID 18EB0300.
The Freeze Frame Data Example above is randomized except the SPN FMI OC.

Page 38 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

4.5. Diagnostic Data Clear ( DM3, DM11)

DM3:
Request for DM3 (Standard Request)

Defaults values for transmission rate and CAN Identifier s. CAN Code Specification.

On request for DM3 all passive faults (and the depending Freeze Frames) stored in the
error memory will be cleared.

Request message:

Data Length: 3 Bytes

Data Page: 0
PDUF : 234
PDUS : EMR4 Device Nr
Parameter group number: 00EA00

Byte Data Comment

Byte 1-3 00 FE CC PGN-Nr. Of message DM3, LSB first

Answer for DM3 request

The answer of EMR4 will be a positive Acknowledgment.

How to request a DM3 Message from the ECU

Send a request Message with 3 Bytes Payload stating the Programm Group Number of
DM3, which is FE CC 00 in hex. You have to switch the first 2 bytes according to Little
Endian standard, e.g. CC FE 00. The request will look like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18EA0003 8 CC FE 00 FF FF FF FF FF
or
ID DLC Byte1 Byte2 Byte3
18EA0003 3 CC FE 00

The Answer of the ECU will be an DMACK Message like this:

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8
18E8FF00 8 00 FF FF FF FF CC FE 00

Byte 1 states 00 = Passive Errors deleted

Page 39 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

4.6. DM11:
Request for reading DM11 (Standard Request)

Defaults values for transmission rate and CAN Identifier s. CAN Code Specification.

When the EMR4 receives the standard request message, using the PGN of the diagnostic
message DM11 in the data area, only the active errors will be cleared in the error
memory 1, including their freeze frame parameters. The entries of the passive faults will
be left untouched

Data Length: 3 Bytes

Data Page: 0
PDUF : 234
PDUS : EMR4 Device Nr
Parameter group number: 00EA00

Byte Data Comment

Byte 1-3 00 FE D3 PGN-Nr. Of message DM11, LSB first

Answer for DM11 request

The answer of EMR4 will be a positive Acknowledgment.

Note: It does not make sense to delete active errors as they are set immediately again

Page 40 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

5. Proprietary EMR4 Specific CAN Messages based on SAE -

J1939

There is only a small range available in the standard for proprietary messages. Therefore
the receivers of the messages should use the complete identifier including the source
address as a filter for the input buffers of the CAN controller.

5.1. Send messages

5.1.1. Measured Data 1

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Measure Data 1 6 0 0 (18) FF 04 00 100ms 18 FF 04 00

Byte Data Comment

Byte 1 Preheat information
Byte 2-3 Engine speed 0,125 rpm /Bit
Byte 4 Boost pressure 2 kPa/ Bit = 1/50 Bar/ Bit
Byte 5 Pedal position 0 to 100% 0,4% / Bit
Byte 6 Coolant temperature 1°C /Bit, -40°C Offset
Byte 7 Oil pressure 4 kPa/ Bit = 1/25 Bar /Bit
Byte 8 Can set point status

Byte 1: Preheat information

Bit t<0°C, n=0 cranking n>700 t>0°C, n=0 n>0

1 Preheat active x - - - - - - - -
2 Ready for start - - x - - x - x -
3 Post heat active - - - - - x - - -
4 Glow plugs active x x - x - x - - -
5 Flame glow plugs active x x - x - - - - -
6 Flame fuel valve active - - - - - - - - -
7 Push button active (not used – set to 0) - - - - - - - - -
8 Status preheat sense line (1= preheat - - - - - - - - -
active, 0 = preheat not active)

Byte 8: Can set point status

Value Can set point status
0 Initialization after power on

Page 41 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
3 engine starts (is cranking)
6 CAN messages for speed or torque demand failed (timeout) - EMR uses substitute
input source for setpoint i.e. accelerator pedal
7 Engine start protection / Engine shutdown request is active

5.1.2. Measured Data 2

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Measure Data 2 6 0 0 (18) FF 12 00 100ms 18 FF 12 00

Byte Data Comment

Byte 1 Droop 1% / bit
Bytes 2-3 Speed set point with droop 0,125 rpm /Bit
Byte 4 not available
Byte 5, 6 engine speed, sensor 1 (crank 0,125 rpm /Bit
shaft)
Byte 7, 8 engine speed, sensor 2 (cam shaft) 0,125 rpm /Bit
calculated as crank shaft speed
Gray displayed information are actually not available – ignore these data!

Byte 1: Droop
Droop = (nmax - nrated) / nrated * 100 %
n = engine speed

Bytes 2, 3: Set point data engine speed, droop calculated ( =engine set point at no load )
This is a data inside EMR4 after selection of the source of requested speed at the input of
the speed governor, calculated with droop .

Page 42 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

5.1.3. Measured Data 3

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Measure Data 3 6 0 0 (18) FF 13 00 100ms 18 FF 13 00

Byte Data Comment

Byte 1 Power reduction 1% / bit
Byte 2 Maximum available engine torque 1% / bit
at current speed
Byte 3, 4 Maximum available engine speed 0,125 rpm /Bit
Byte 5, 6 Hold engine speed 0,125 rpm /Bit
Byte 7, 8 Rail Fuel Pressure 1 Mpa/ Bit, range 0 to 251 Mpa

Power reduction
This is the actual value of the power reduction, calculated by the internal engine
protection functions and the CAN message engine protection. The limits set by the
message TSC1 have no influence on this value.
The value of no power reduction is 100%

Maximum available engine torque at current speed

The maximum available indicated engine torque at current speed in percent of the actual
torque curve.
Engine protection functions and CAN messages, i.e. TSC1, can limit this data to a lower
value. In that case not 100% of the torque is available.
If there are no limitations or power reductions active, the available engine torque is given
by the torque curve. In that case the value of maximum available engine torque at current
speed will be 100%.

Maximal available engine speed

The maximal available engine speed varies because of engine protection functions and
other CAN messages.

Hold engine speed

Is one of the following data, depending on which data is actual used:
• Frozen engine speed (actual engine speed saved)
• Frozen engine speed (set point speed saved)

If none of both data is actual used the value will be 0xFFh.

Page 43 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
5.1.4. Measured Data 4

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Measure Data 4 6 0 0 (18) FF 14 00 100ms 18 FF 14 00

Byte Data Comment

Byte 1 Switch status 1 Bit 1, 2: Water in fuel indicator
Bit 3, 4: Engine break switch
Bit 5, 6: Engine stop switch
Bit 7, 8: Engine start switch
Values:
On = 1, Off = 0
Byte 2 Switch status 2 Bit 1, 2: Low idle switch throttle 2 (hand gas
lever)
On = 1, Off = 0, 11 = Not Available
Byte 3 Throttle 2 (hand gas lever) Range 0 to 100%, 0,4 % / Bit,
0xFEh if throttle is in error state,
0xFFh if throttle is not available
Byte 4 PWM throttle value 0xFFh: PWM throttle is not available
Byte 5 Multiply State Switches Bits 1,2,3: Network speed set point number
Additional Set Point Input Values = 0 to 4
Switches 7: = not available (disabled by
parameter or out of range)
Bits 4,5,6: Network torque/droop line number
0 to 4 = number
7 = not available (disabled by
parameter or out of range)
Bits 7, 8: = 0xFFh = not defined
Bytes 0xFFh
6, 7, 8

Page 44 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
5.1.5. Measured Data 8

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Measure Data 8 6 0 0 (18) FF 1D 00 100ms 18 FF 1D 00

Byte Data Comment

Bytes 1 Lamp commands 1 useful if lamp controller of the dashboard are
controlled by the CAN bus.
It is not an output pin state of EMR4
This information is always available, no matter if
lamps are at the output pins or not.

Bit 1: engine protection lamp demand

(engine limits exceeded )

Bit 2: warning lamp (malfunction lamp)

for all faults, that means system faults i.e. broken
wires, memory problems and so on, and if physical
engine parameter exceed limits

Bit 3: stop lamp

( for engine protection, and systems faults)

Bit 4: don’t care

Bit 5 don’t care

Bit 6 don’t care

Bit 7 Warning Oil Lamp

Bit 8 don’t care

Values on= 1, off or not available= 0

s. also Appendix Lamp Status for details
Byte 2 Lamp commands 2 useful if lamp controller of the dashboard are
controlled by the CAN bus.
It is not an output pin state of EMR4
This information is always available, no matter if
lamps are at the output pins or not.

Bits 1,2 Preheat lamp demand

Values on= 01, off = 00
blinking = 10,

Bits 3 to 8 = 0

Page 45 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

Bytes 3, 4 Actual limp home status / The actual limp home 1 /2 status bits show the actual
Engine protection valid status
( only for monitoring functions, not for s. also DM4 for freezing in fault condition
system faults) Bit 3,4 power reduction,
Bit 11,12 don’t care
Bit 13,14 don’t care
Bit 15,16 Boost pressure estimating
Values active =01, off = 00
Byte 5 Status of engine protection override Bit 1 power reduction override
( only for monitoring functions, not for Bit 2 force low idle timer override
system faults) Bit 3 forced low idle override
Bit 4 engine shutdown timer override
Bit 5 engine start protection override
Values: active =1, passive = 0,
Bytes 6 Engine protection phase values see separate list
Byte 7 Engine running status Bits 1 to 4, values:
0h = engine is not running
1h = engine is cranking
2h = engine is running
Bit 8: active fault indicator
Bits 5 to 7 = 0, not used.
Bytes 8 Controller status not available

Byte 6 Engine protection phase:

Engine not running Engine running
12 = engprt shutdown initiated
13 = shutdown timer triggered

Page 46 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

5.1.6. Measured Data 9 (fan data)

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Measure Data 9 6 0 0 (18) FF 19 00 100ms 18 FF 19 00

Byte Data Comment

Byte 1, 2 Fan speed 1 rpm / bit
Byte 3 Fan speed clutch value 0.4 %, range 0 to 100 %
only if PWM is sent to clutch else 0xFFh
This is the clutch input value.
Byte 4, not available not available, value is 0xFFh
5,6,7,8

Page 47 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

5.1.7. Limitation

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Limitation 6 0 0 (18) FF 15 00 100ms 18 FF 15 00

In this section the possibility will describe for limitation or engine shut off. If an
limitation will be send depends on the Function of he engine

Byte Data Comment

Byte 1 Active limitation 1
Byte 2 Active limitation 2
Byte 3 Actual torque map
Byte 4 Engine speed limit
Byte 5 Engine torque limit
Byte 6 Source of power reduction
Byte 7 Engine stop
Byte 8 Reserved
Gray displayed information are actually not available – ignore these data!

Active limitation 1
Bit 8 Max. Torque curve reached
Bit 7 Max. Engine speed limit reached (Engine speed limit)
Bit 6 Engine speed limit TSC1 reached ( TSC1 Engine speed limit)
Bit 5 Engine torque limit TSC1 reached (TSC1 Engine torque limit)
Bit 4 Power reduction active
Bit 3 engine shutdown protection / start prevention active
Bit 2 limp home function active
Bit 1 Road speed limitation active (configured limit reached)

A bit will only be set, when the depending function is limiting the engine at this moment.
If there is a limit set, but the engine is working at a point below this limit, the
corresponding bit will not be set.

Active Limitation 2
Bit 1,2,7, 8 reserved = 1
Bit 6 Rail limp home
Bit 5 overrun condition
Bit 4 smoke limitation
Bit 3 limitation by barometric pressure

Actual torque map

This is the number of the selected max. Torque curve, even when the engine is actually
not working at this limit
1 = max. torque curve 1

Page 48 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
2 = max. torque curve 2
3 = max. torque curve 3
4 = max. torque curve 4
5 = max. torque curve 5

Engine speed limit

1 normal speed limit (configuration parameter)

This is the number of the actual lowest engine speed limit, even when the engine is
actually not working at this limit

Engine torque limit

1 Normal limitation by max. torque curve
2 Smoke limitation/ boost temperature too high
3 TSC1.TE
4 Reserved

This is the number of the actual lowest engine torque limit, even when the engine is
actually not working at this limit.

Source of power reduction

0 = no power reduction
1 = Boost Air Temperature Monitoring
2 = Coolant Temperature Monitoring
28 = Engine Protection

The number of the signal that sets the highest reduction will be send in this byte.
The engine mustn't work at the limit to get a value different from zero. It is sufficient that
a limit is set.

Page 49 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Example:
Power reduction 20% of max. Torque curve because of coolant temperature is too high,
that means 80% of power is available. The engine may work at 10% of max. Power, but
the value of the byte will be 2.

Engine stop

1 = no special engine stop, normal engine stop

2 = Engine shutdown for engine protection
3 = CAN Message Engine Stop Request

The value of this byte shows the reason, why EMR4 has shut off the engine.

Page 50 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
5.1.8. State of Inputs 1

These data give information about the input pins, regardless for what they used for, that
means independent from the output pin assignment.

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
State of Inputs 6 0 0 (18) FF 0A 00 1000ms 18 FF 0A 00

Byte Data Comment

Byte 1 Digital Input Pins 1 Bit 1: override switch input
Measured at the hardware inputs Bit 2: droop choice input
Bit 3: Controler Mode Switch (Speed/Torque)
Bit 4: power boost input switch (option with
agriculture type engines)
Bit 6: tip up / speed switch (+)
Bit 7: tip down / speed switch (-)
Values: 1 = on, 0 = off

Byte 2 Digital Input Pins 2 Bit 1: Input water in fuel indicator

Measured at the hardware inputs Bit 2: Input engine break switch
Bit 3: Input engine stop switch
Bit 4: Input engine start switch T50

Values: 1 = on, 0 = off

Byte 3 not available
Byte 4 Torque Map Selection Switch 0,05 V / Bit, 0 to 5V
Voltage
Byte 5 Speed Setpoint Selection Switch 0,05 V / Bit, 0 to 5V
Voltage
Byte 6,7, 8 Reserve Pulse Input (EMR4-E) not available

Page 51 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

5.1.9. State of Outputs1

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
State of Outputs 6 0 0 (18) FF 0B 00 1000ms 18 FF 0B 00

Byte Data Comment

Byte 5 Torque PWM / Switch
Byte 6 Fan Control PWM / Switch
Byte 7 Digital outputs1 Bit 1,2: engine running output
Bit 3,4: Diagnostics Lamp
Bit 5,6: Starter output

Values: on = 01, off = 00,

10 = error of output, 11 = disabled output
Byte 8 Digital outputs 2 Bit 1,2: Coolant Temperature and
Level Warning Lamp
Bit 3,4: Oil Warning Lamp
Bit 5,6: Preheat / Coldstart Lamp

Values: on = 01, off = 00,

10 = error of output, 11 = disabled output

Note: The Lamp Outputs of Byte 7,8 mirror the Outputs of the respective ECU Pins

Data format for PWM / Switch Outputs

if PWM: 0% to 100%, 1% / Bit
if Switch: on =100, off = 0
Error = 0xFEh
Disabled by parameter = 0xFFh

Page 52 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

6. Exhaust After Treatment Send Messages:

6.1. AT1TI1 Urea Tank

Name DLC J1939 Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
After Treatment 6 0 0 (18) FE 56 3D 1000ms 18 FE 56 3D
1 Tank
Information

Byte Data Comment

Byte 1 Urea Tank Level 0,4 %/Bit; No Offset
Byte 2 Urea Temperature 1 deg C, Offset -40
Byte 3 to 8 not defined = 0xFFh

6.2. AT1S Aftertreatment 1 Service

Name DLC J1939 Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
After Treatment 6 0 0 (18) FD 7B 00 1000ms 18 FD 7B 00
1 Service

Byte Data Comment

Byte 1 DPF Soot Load Percent 1% / Bit, 0 to 250%, SPN 3719
Byte 2 DPF Ash Load Percent 1% / Bit, 0 to 100%, SPN 3720

Bytes Time since last active 1s / Bit, SPN 3721

3,4,5,6, regeneration
Byte 7, 8 not available FFh

6.3. AT1IG2 Catalyst Upstream Temperature

Name DLC J1939 Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
After Treatment 6 0 0 (18) FD B4 3D 500ms 18 FD B4 3D
1 Inlet Gas 2

Page 53 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

Byte Data Comment

Byte 1, 2 Catalyst Upstream Temperature 0,03125 °C/Bit, Offset –273°C
Byte 3 to 8 not defined = 0xFFh

6.4. AT1OG2 Catalyst Downstream Temperature

Name DLC J1939 Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
After Treatment 6 0 0 (18) FD B3 3D 500ms 18 FD B3 3D
1 Outlet Gas 2

Byte Data Comment

Byte 1, 2 Catalyst Downstream Temperature 0,03125 °C/Bit, Offset –273°C
Byte 3 to 8 not defined = 0xFFh

6.5. DPFC 1

Name DLC J1939 Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Diesel Particle 6 0 0 (18) FD 7C 00 1000ms 18 FD 7C 00
Filter Control 1

Byte Data Comment

Byte 1 Diesel Particulate Filter Lamp 000 Off
Bit 1-3 Command SPN 3697 001 On – solid
100 On – fast blink (1 Hz)
101 On – slow blink (0.5 Hz)
111 not available
Byte 2 Diesel Particulate Filter Passive 00 not active
Bit 1,2 Regeneration Status SPN 3699 01 active
11 not available (passive regeneration
with DPF CRT)

Bit 3,4 Diesel Particulate Filter Active 00 not active

Regeneration Status SPN 3700 01 active
10 Regeneration needed - automatically
initiated active regeneration imminent
11 not available (active regeneration
with DPF Burner)

Page 54 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

Bit 5-7 Diesel Particulate Filter Status 000 Regeneration not needed
SPN 001 Reg. needed – lowest level
3701 010 Reg. needed – moderate level
(or CRT Standstill needed)
011 Reg. needed – highest level
(Regeneration urgently needed)
111 not available
Byte 3 00 not active
Bit 1,2 Diesel Particulate Filter Active 01 active
Regeneration Inhibited Status SPN 11 not available
3702

Bit 3,4 Diesel Particulate Filter Active 00 not active

Regeneration Inhibited Due to 01 active
Inhibit Switch SPN 3703 11 not available

Bit 5,6 Diesel Particulate Filter Active 11 not available

Regeneration Inhibited Due to
Clutch Disengaged SPN 3704

Bit 7,8 Diesel Particulate Filter Active 11 not available

Regeneration Inhibited Due to
Service Brake Active SPN 3705
Byte 4
Bit 1,2 Diesel Particulate Filter Active 11 not available
Regeneration Inhibited Due to
PTO Active SPN 3706

Bit 3,4 Diesel Particulate Filter Active 00 not active

Regeneration Inhibited Due to 01 active
Accelerator Pedal Off Idle 11 not available
SPN3707 (only for passive regeneration)

Bit 5,6 Diesel Particulate Filter Active 00 not active

Regeneration Inhibited Due to Out 01 active
of Neutral SPN 3708 11 not available
(only for passive regeneration)

Bit 7,8 Diesel Particulate Filter Active 00 not active

Regeneration Inhibited Due to 01 active
Vehicle Speed Above Allowed 11 not available
Speed SPN 3709 (only for passive regeneration)

Page 55 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Byte 5
Bit 1,2 Diesel Particulate Filter Active 00 not active
Regeneration Inhibited Due to 01 active
Parking Brake Not Set SPN 3710 11 not available
(only for passive regeneration)
Bit 3,4 Diesel Particulate Filter Active
Regeneration Inhibited Due to 00 not active
Low Exhaust Gas Temperature 01 active
SPN 3711 11 not available

Bit 5,6 Diesel Particulate Filter Active 00 not active

Regeneration Inhibited Due to 01 active
System Fault Active SPN 3712 11 not available

Bit 7,8 Diesel Particulate Filter Active 11 not available

Regeneration Inhibited Due to
System Timeout SPN 3713
Byte 6 Diesel Particulate Filter Active 00 not inhibited
Bit 1,2 Regeneration Inhibited Due to 01 inhibited
Temporary System Lockout SPN 11 not available
3714
(Filter load too low for
regeneration)

Bit 3,4 Diesel Particulate Filter Active 00 not inhibited

Regeneration Inhibited Due to 01 inhibited
Permanent System Lockout SPN 11 not available
3715
(Filter fully loaded)

Bit 5,6 Diesel Particulate Filter Active 00 not inhibited

Regeneration Inhibited Due to 01 inhibited
Engine Not Warmed Up SPN 3716 11 not available

Bit 7,8 Diesel Particulate Filter Active 11 not available

Regeneration Inhibited Due to
Vehicle Speed Below Allowed
Speed
SPN 3717

Page 56 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Byte 7
Bit 1,2 Diesel Particulate Filter Automatic 00 not enabled
Active Regeneration Initiation 01 enabled
Configuration SPN 3718 11 not available

Bit 3-5 Exhaust System High Temperature 111 not available

Lamp Command SPN 3698

Bit 6-8 Diesel Particulate Filter Active 111 not available

Regeneration Forced Status SPN
4175

Byte 8 not available FFh

6.6. AT1IMG

Name DLC J1939 Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Aftertreatment 1 6 0 0 (18) FD B2 00 500ms 18 FD B2 00
Immediate Gas

Byte Data Comment

Byte 1-2 not available FFh
Byte 3-4 not available FFh
Byte 5-6 Aftertreatment 1 Diesel Particulate 0.1 kPa/bit, 0 offset
Filter Differential Pressure SPN
3251
Byte 7-8 not available FFh

6.7. AT1DOC

Name DLC J1939 Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Aftertreatment 1 6 0 0 (18) FD 20 00 500ms 18 FD 20 00
Diesel
Oxidation
Catalyst

Page 57 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Byte Data Comment
Byte 1-2 Aftertreatment 1 Diesel Oxidation 0.03125 deg C/bit, -273 deg C offset
Catalyst Intake Gas Temperature
SPN 4765
Byte 3-4 Aftertreatment 1 Diesel Oxidation 0.03125 deg C/bit, -273 deg C offset
Catalyst Outlet GasTemperature
SPN 4766
Byte 5-8 not available FFh

6.8. DPF Burner Pressure and Temperature

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
DPF Burner 6 0 0 (18) FF 41 00 100ms 18 FF 41 00
Pressure and
Temperature

Byte Data Comment

Byte 1, 2 Burner Temperature 0.03125 deg C/bit, -273 deg C offset
Byte 3, 4 Burner supply air pressure 0,1 kPa / bit, 0 to 6,425.5 kPa SPN3485

Byte 5 fuel temperature at input 1 deg C/bit, -40 deg C offset

burner system -40 to 210 deg C,
Byte 6 fuel pressure at input 4 kPa / bit, 0 to 1000 kPa SPN
burner system
Byte 7 fuel pressure for burner 4 kPa / bit, 0 to 1000 kPa SPN
Byte 8 fuel pressure for HCI 4 kPa / bit, 0 to 1000 kPa SPN

6.9. DPF Test Monitor (optional)

Message data bytes 1 and 2 are set after test start request. After test ended data
is send with 2 second delay. Then data bytes 1 and 2 are set to 0 until new start
of test.
Test request via CAN (see also DPF Control Receive message) has to be reset
(byte 3 = 0x00). Otherwise the test will start again.
Activation of EOL Test must not coincide with other Service/EOL tests via
KWP2000.

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
DPF Test 6 0 0 (18) FF 48 00 1000ms 18 FF 48 00
Monitor

Page 58 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

Byte Data Comment

Byte 1, 2 DPF EOL Test Status see below
Byte 3 Status of Fuel Shut Off 00 not enabled
Bit 1,2 Valve 01 enabled
10 error
11 not available

Bit 3-8 not available 111111

Byte 4 not available FFh
Byte 5 CRT remaining standstill 1 Minute/bit
regeneration time
Byte 6-8 not available FFh

Status and Data of EOL Test Response:

Byte 1 Byte 2
00 test finished or not yet started 00
01 test not allowed -
02 conditions not met 01 Faults before Test started [see fault memory]
02 Engine not running
04 Soot load too high – remove filter
08 Regeneration or burner start not possible
11 Vehicle not stationary
16 supply release not in range
03 test completed with data 09 DOC Temperature Increase not properly
10 Error occurred (see Fault memory)
17 supply release not in range during test
18 Vehicle not stationary during test
04 test in progress 32 regeneration adsorption mode
33 regeneration light off
34 regeneration dry
35 regeneration particulate filter regeneration
30 no information
06 test completed successfully

Status and Data of Deflate Pipes Response:

Byte 1 Byte 2
00 test finished or not yet started 00
01 test not allowed -
02 conditions not met 01 Faults before Test started [see fault memory]
02 Engine not running
16 supply release not in range
03 test completed with data 05 Pressure DV1 not in range
06 Pressure DV2 not in range
10 Error occured (see Fault memory)
15 pressure upstream not in range
17 supply release not in range during test
04 test in progress 30 no information

30 no information
06 test completed successfully

Page 59 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

6.10. DPF History Data

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
DPF History 6 0 0 (18) FF 49 00 1000ms 18 FF 49 00
Data

Byte Data Comment

Byte 1-4 Total Disabled Time SPN 3524 1 s/bit, 0 offset
Total time an automatic regeneration is
requested but is manually inhibited by
the
operator. Total time is over the lifetime
of
the device.
Byte 5-8 Total Number of Active 1 count/bit, 0 offset
Regenerations SPN 3525 Total number of active regenerations
over
the lifetime of the device.

Page 60 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

6.11. EPA1

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Environment 6 0 0 (18) FF 4E 00 100ms 18 FF 4E 00
Protection
Agency 1

Byte Data Comment

Byte 1 Bits 0, 1 The value is a number:
Restriction level 0: no restriction
according to AddBlue 1: Level 1 (i.e. Warning < 5% AddBlue Level,
tank level power reduction after a delay time possible)
2: Level 2 after delay time 1 – power reduction 1
(early inducement)
3: Level 3 after delay time 2 – power reduction 2
(severe inducement)

Bits 2,3 0: Level ≥ Threshold 1 (15%)

AdBlue Tank level 1: Threshold 1 >Level ≥ Threshold 2 (10%)
These Bits can disabled by 2: Threshold 2 >Level ≥ Threshold 3 (5 %)
setting them to zero (DEUTZ
Application) 3: Threshold 3 > Level
Thresholds are application parameters set by DEUTZ
Bits 4 to 7 not used, set to zero
Byte 2,3 Time counter (count running time to next restriction level
down) for tank level 1 min / Bit, counter not running value = 0
FF means no time counter available
Byte 4 Restriction level of The value is a number:
incorrect Reducing Agent 0: no restriction
(AdBlue) 1: Level 1, Warning, power reduction after a delay
time possible
2: Level 2 after delay time 3 – power reduction 3
(early inducement)
3: Level 3 after delay time 4 – power reduction 4
(severe inducement)

Byte 5,6 Time counter (count running time to next restriction level
down) for incorrect 1 min / Bit
Reducing Agent , counter not running value = 0
(AdBlue) FF means no time counter available
Byte 7,8 actual SCR engine speed actual engine speed limit caused by the SCR functions
limit, based on AdBlue 0,125 rpm /Bit, not available yet, FFFFh
Level, anti tamper and
incorrect Reducing Agent

Page 61 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

6.12. EPA2

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Environment 6 0 0 (18) FF 4F 00 100ms 18 FF 4F 00
Protection
Agency 2

Byte Data Comment

Byte 1 Restriction level 0: no restriction
according to SCR 1: Level 1 Warning, power reduction after a delay
efficiency rate time possible
2: Level 2 after delay time 7 – power reduction 7
(early inducement)
3: Level 3 after delay time 8 – power reduction 8
(severe inducement)
Byte 2,3 Time counter (count running time to next restriction level
down) for restriction 1 min / Bit, counter not running value = 0
level according to SCR FF means no time counter available
efficiency rate
Byte 4 SCR fault status Bits 0 to 3, system status, the content is a number ,
higher numbers have more priority
0: System is working without problems
1: SCR System faults but SCR is working
(details see error codes), Derating level 2.
2: SCR System faults but SCR works in limp home
mode (details see error codes), derating level 2
3: SCR System fatal error, SCR function disabled
because of faults (details see error codes), derating
level 2
4: SCR System disabled by application

Byte 5 Restriction level 0: no restriction

according to anti tamper 1: Level 1 Warning, power reduction after a delay
time possible
2: Level 2 after delay time 5 – power reduction 5
(early inducement)
3: Level 3 after delay time 6 – power reduction 6
(severe inducement)
SCR Engine start stop Bits 4 to7, scr engine start stop counter. The number
counter shows how often the engine was started consecutively
with active SCR failures.
After exceeding a limit the engine is not allowed to
start anymore. Service is necessary then.
Byte 6,7 Time counter (count running time to next restriction level
down) for restriction 1 min / Bit, , counter not running value = 0

Page 62 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
level according to anti FF means no time counter available
temper
Byte 8 actual SCR Power actual power reduction caused by the SCR functions
reduction value, based on 1% /Bit, range 0% to 100%
AdBlue Level, anti 0% = engine stop or start protection
tamper incorrect
Reducing Agent and
insufficient efficiency
rate

7. Exhaust After Treatment Receive Messages:

7.1. CM1 – Receive Message

Name DLC J1939 Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
Carb Message 1 6 0 0 (18) E0 00 03 1000ms 18 E0 00 03

Byte Data Comment

Byte 1-5 not available FFh
Byte 6 Diesel Particulate Filter also used for CRT standstill
Bits 1,2 Regeneration Inhibit Switch regeneration
00 not enabled
01 enabled
11 not available

Bits 3,4 Diesel Particulate Filter also used for CRT standstill
Regeneration Force Switch regeneration
00 not enabled
01 enabled
Bits 5-8 not available 11 not available
1111

Byte 7-8 not available FFh

Note: Source Address is applicable.

Page 63 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

7.2. DPF Control Receive message

Name DLC Specific Identifier Repetition Identifier

Byte Priority Reserved Data Page PDUF PDUS Source Address rate Hex
3 Bit 1 Bit 1 Bit 1 Byte 1 Byte 1 Byte (msec)
(P+R+DP)
DPF Control 6 0 0 (18) FF 44 03 100ms 18 FF 44 03
Receive
message
Byte Data Comment
Byte 1 regeneration request Bit 1:
0 = no request,
1= set regeneration request
This command is treated like the HW regeneration
Button. Once set the regeneration request, the
regeneration procedure will run automatically when
the conditions for regenerations are fulfilled.
The EDC will answer the request by setting the DPF
regeneration request bits in the message DPFC1 byte
7, bits 6-8, SPN 4175
Byte 2 regeneration inhibit Bit 1:
command 0 = regeneration not inhibited,
1 = regeneration inhibited,
As long as this bit is set the regeneration will not start
If the inhibit command will be set when a
regeneration procedure is still running, the
regeneration will be stopped and inhibited till the bit
will be set to zero. The EDC will answer the request
by setting the DPF inhibit bits in the message DPFC1
byte 3, bits 3,4, SPN 3703
Byte 3 Deflate pipes & EOL test Deflate pipes & EOL test
request request
Bits 0 to 3
0x00 : no test request
0x1B: Start Deflate Pipes
0x1C : Start EOL Test
0xF0 : Stop All Tests
Once the Start Deflate Pipes or Start EOL Test
request is set, the test procedure will run
Automatically until the test is finished.
Once the Stop All Tests request is set, a running test
Procedure is stopped.
See also test request answers in the message “DPF
Test Monitor”
Byte 4-8 reserved for future
assignments

Note: Source Address is applicable.

Page 64 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

8. CAN Bus Error Diagnostics

The CAN Bus has error diagnostic functionality to control receive and transmit messages
however certain conditions such as ECU power up, engine cranking, low voltage
conditions and after run conditions will disable diagnostics functionality to cope with not
powered customer ECUs on the can bus.

Transmit Messages will be sent immediately after ECU power up, same with their
diagnostics functionality.

Receive Messages (e.g. TSC1TE, Engine Protection, Function Mode Control) must be
present 30 seconds after ECU power on or 10 seconds after Engine start as their
diagnostics functionality will switch on after these timers have expired. Timeout Errors
will be written to Error Memory after another 500ms otherwise and may result in Limp
Home behavior.
In After Run State ( e.g. Terminal 15 is off thus the engine has been stopped, the ECU
finishes after run tasks and will power off afterwards) the diagnostics functionality will
be disabled, too. Receive Messages don't need to be present in After Run State.

8.1. Setpoint sources

If the CAN Bus is the source of the engine speed or torque setpoint and a pedal is
also connected to the EMR4, the CAN setpoint has higher priority and the pedal is
the redundant source. The following functions will be used:

If the CAN Bus message which delivers the setpoint is in the timeout condition, then the
redundant source will be used. Once switched over to the redundant value no return to
the CAN bus setpoint is possible till the engine has been stopped.

CAN BUS stops operation

All members of the CAN Bus must be switched on/ off at the same time, else receive
messages could be missing and faults might be generated.
The DEUTZ experience is, that the fault message "receive message is missing" is not
sufficient if they occur seldom, because nobody knows if this is caused by indeterminate
switch off conditions or by CAN Bus disturbances.
Therefore EMR4 will set a data before it ends stopping the CAN Bus messages.
All other nodes can decide if they need the CAN BUS messages from EMR4
furthermore.

Receive Messages missing, time out

Defaults values for transmission rate, timeout and CAN Identifier s. CAN Code
Specification.

Not valid data

Not valid data, (i.e. caused by a short circuit of a sensor), have to be set to 0xFEh
according to the standard SAE-J1939.

Page 65 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Missing or not valid data of a CAN-Bus will be replaced by error values inside the
EMR4. These error values are configuration parameters, which can be normal error
values in the normal operation range or error values outside the operation range.
Error values in the normal operation range are used like valid data for the other functions
of EMR4, but error messages will be generated.

EMR functions will not work with data set to error values outside the normal operation
range. Alternative function will be used to get a proper operation of the system, i.e. limp
home function.
If a data becomes valid again, this valid value will be used again for normal operation, if
not other specified in the function specification. Set point values for engine speed or
engine torque will not get valid again after a fault detection..

Page 66 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
Error Memory
Faults of the CAN-bus are transmitted via CAN-Bus and the ISO9141 Bus and will be
stored into the error memory of EMR4.
The diagnostic lamp will be activated.
The reason for a fault must be unambiguously determinable.

Engine protection message

If an engine protection message fails, the last valid value will be used and the error
messages will be generated.

Page 67 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

9. Appendix 1: Multipackage Transport

If more than 8 data bytes must be send they have to be separated in different packets. The
first message is the Broadcast Announce Message (BAM), which tells the receiver which
message will be sending in packages. After that the data packets will be sending.

BAM:
Transmission rate: s. below.
Data length: 8
Data Page: 0
PDUF: 236
PDUS: 255
Priority: 6
Parameter group 60416
number:
Source Address: Device- Nr. EMR
ID:

Byte 1 32
Byte 2, 3 Number of used data bytes of all packets
without the byte of packet number
Byte 4 number of Packets
Byte 5 reserved FF
Byte 6 to 8 Parameter group number

Die „parameter group number“ and the transmission rate are the same as in the message
specified, which data are transferred with the Multipacket Transport (i.e. DM 1, DM 2)

The data packets:

Transmission rate: see above
Data length: 8
Data Page: 0
PDUF: 235
PDUS: External Device Nr
Priority: 6
Parameter group 00Ebxxh
number:
Source Address: Device- Nr. EMR
ID:

Byte 1 Packet Nr.

Byte 2 to 8 Data

There may be less than 8 useful data bytes in the last data packet, so the rest of the data
bytes are set to FF. The External Device No. is global (255) if the message is send
cyclically, else it is the Device No. of the device which made a request.

Page 68 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

Example for Multipackage Protocol from DM4 Request Example.

ID DLC Byte1 Byte2 Byte3 Byte4 Byte5 Byte6 Byte7 Byte8

18ECFF00 8 20 1D 00 05 FF CD FE 00
18EB0300 8 01 10 00 54 8B 81 FF 81
18EB0300 8 02 9A 6E FB CD EF CC DD
18EB0300 8 03 10 20 30 40 50 60 70
18EB0300 8 04 80 90 A0 B0 C0 D0 E0
18EB0300 8 05 9A FF FF FF FF FF FF

Note: Broadcast Announce Message 18ECFF00 announces the DM4 message

(PGN FECD00). 20=Control Byte, 1D = 29 Bytes to send, 05 = 5 Messages.
18EB0300 is the message containing the information, which ID 03 (you) has requested
previously thus addressed to you with Message ID 18EB0300. If the message was not
requested this will be 18EBFF00. FF is broadcast address.

Page 69 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

10. Appendix 2: Lamp status

Malfunction Lamp status consist of 2 Bit values:
00 not active (not lightened)
01 active (lightened)
11 not defined

Bit 1,2 Engine Protection Lamp

• is active, if a valid data is out of normal operating range, i.e. in warning
range, power reduction range, engine shutdown demand range, start
protection range or shutdown range.
• is not active, if the data value is coming back out of the warning range
and is below the recovery limit.

Bit 3,4 Warning Lamp

is active, if the diagnostic lamp of EMR is continuously lightened,
otherwise it is inactive. That means it is active not only if a data value is in
the warning range, it is also set, if an electronic part of the EMR System
has a fault which does not causes an automatically shut off of the engine,
i.e. broken wire.
Bit 5,6 Stop lamp (for engine protection)
Active, if the EMR diagnostic lamp is blinking to show an critical fault.
That means an engine shut off is necessary.
Bit 7,8 MIL Lamp (not used)

DM1 and DM2 have a second Byte for Lamp Status, but the contents are not specified
(=FF)

After switching power supply the EMR diagnostic lamp is lightened for a test, but the
bits defined above will not be set active for that reason.

Page 70 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

11. Appendix 3: Error codes, SPN, DTC

The diagnostic trouble code DTC consist on the SPN (suspect parameter number) to see
which parameter is faulty, and the FMI (failure mode identifier), which shows the kind of
error.
DTC consist on 19 Bits SPN, 5 Bits FMI, 1 bit conversation method CM and 7 Bits
Occurrence Counter

The SPN (suspect parameter number) values are the same values as described in the
standard.
For special faults, not defined in the standard, the SPN values are configurable.
Each error message can be enabled separately by a configuration parameter.
The error codes SPN and FMI are listed in a separate document.

There are 4 different ways to interpret the SPN Bytes as defined in SAE-J1939-73
OCT1998. 5.7.1.7

The following example shows how to interpret the received bytes of message DM1,
using version 1, for a test tool connected to EMR4.

NOTE: As current legislation for emission control favors version 4 for future OBD
compliance, DEUTZ intends to switch from version 1 to version 4 with release of
Tier4f engines.

EXAMPLE DM1 Received, Version 1 EMR1 and EMR2 compatible:

DM1 Bytes 3 to 6: 00 17 CB 83

This is binary: 0000 0000 0001 0111 1100 1011 1000 0011

SPN FMI OC

SPN = 0000 0000 0001 0111 110 CM

=000 0000 0000 1011 1110

=0 0 0 B E

= 0x00BE = 190decimal = Engine Speed Error

FMI = 0b01011 = 11decimal

OC = 0b0000011 = 3decimal

So the fault 190 with kind of error 11 has occurred 3 times.

Software routine for SPN: Read Bytes 3 to 5 and shift right 5 times,
Or equivalent: Read Bytes 3 to 5 and divide by 20h = 32d
0017CB / 20h = BE = 190d

Page 71 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification
EXAMPLE DM1 Received, Version 4 EMR4 with Tier4f engines:

DM1 Bytes 3 to 6: 00 17 CB 83

This is binary: 1011 1110 0000 0000 0000 1011 0000 0011

SPN FMI OC

SPN = 1011 1110 0000 0000 000 CM

= 0xBE00 (little endian format, as indicated by CM bit, which is 0 for Version 4)

= 0x00BE (swap bytes to get big endian format)

= 190decimal = Engine Speed Error

FMI = 0b01011 = 11decimal

OC = 0b0000011 = 3decimal

So the fault 190 with kind of error 11 has occurred 3 times.

Page 72 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG
 EMR 4 CAN BUS Specification

12. Appendix 4: Acknowledgment

according to SAE-J1939-21

Transmission rate: Once, after receiving a message

which needs an Acknowledge.
Data length: 8 Bytes
Data Page: 0
PDUF: 232
PDUS: 255
Priority: 6
Parameter group 59647 (E8FF)
number:
Source Address: EMR Device Nr.
ID:

Byte 1 0 for positive Acknowledge

1 for negative Acknowledge
Byte 2 to 5 not defined = 0xFF
Byte 6 to 8 parameter group number of the message,
which needs an Acknowledge

13. Appendix 5: Hardware Information CAN

Terminal Resistor Customer CAN:

On both ends of the CAN Bus terminate resistors are necessary.
They must external of the EMR4 controller, because EMR4 does not provide internal
CAN BUS termination resistors on the Customer Bus.

Terminal Resistor Diagnostic CAN:

The Diagnostic CAN BUS is terminated in EMR4. A Tester Device usually terminates
the other end of the CAN Bus. No additional termination needed.

EMR4 switched off

EMR4 will not influence the CAN BUS data transfer, when EMR4 is switched off by the
power supply.
That means EMR4 will not influence the physical can bus parameter.

Page 73 of 73
File: EMR4_CAN _BUS_Specification_ver02_34.docx © Deutz AG