CAN-Specification EMR2 Engl

Specification for EMR2 Date: 29.01.
2004 17:14
CAN-Specification for EMR2
Page:1 of 50
Author: J.Brardt
Dept.: EK-E2
File: D:\Datensaetze\CAN\can_spec_emr2_6_engl.doc
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
CAN-Specification for EMR2 Date: 29.01.2004 17:14
1 GENERAL REQUIREMENTS 5
1.1 Standards and Additional Specifications 5
1.2 Baud Rate 5
1.3 Configuration Parameter of CAN Identifier and Transmission Rates 5
1.4 Configuration Parameter of the Messages 6
1.5 Not Available or not Valid Data Bytes 6
1.6 Diagnostic Functions 6

1.6.1 General 6
1.6.2 Set Point Data 7
1.6.3 Engine Protection Message 7
1.7 Set Point Data 7
1.8 Engine Protection 9
2 SAE J1939-CAN MESSAGES 10
2.1 EEC1: 10
2.2 EEC2 11
2.3 Engine Temperature 11
2.4 Engine Fluid Level/Pressure 12
2.5 Inlet / Exhaust Conditions 13
2.6 Fuel Economy 13
2.7 Engine Hours 14
2.8 TSC1.a to TSC1.d 15
2.9 Engine Configuration 17
2.10 Ambient Conditions 18
2.11 Vehicle Electrical Power 19
2.12 Cruise Control / Vehicle Speed 19
3 EMR2 SPECIFIC CAN-MESSAGES BASED ON SAE J1939 20
Page 2 of 50
Author: J.Brardt
Dept.: TK-EV
File: can_spec_emr2_6_engl.doc
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
3.1 Function Mode Control 20
3.2 Engine Protection 21
3.3 Engine Stop Request 22
3.4 Measured Data 23

3.4.1 Measured Data 1 23
3.5 State of Inputs 1 28
3.6 State of Inputs 2 29
3.7 State of Digital Outputs 30
3.8 Controller Configuration 31
3.9 Limitation 33
4 DIAGNOSTIC MESSAGES 36
4.1 Number of faults (DM5) 37
4.2 Active faults ( DM 1 ) 38
4.3 Passive Faults (DM2) 39
4.4 Freeze Frame Parameter (DM4) 41
4.5 Diagnostic Data Clear ( DM3, DM11) 42
5 APPENDIX 43
5.1 Appendix 1: Multipacket Transport 43
5.2 Appendix 2: Lamp status 45
5.3 Appendix 3: Acknowledgment 46
5.4 Appendix 4: Error codes and SPN 46
5.5 Appendix 5: Overview CAN-Messages 48
Page 3 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
5.6 Appendix 6: Configuration of Available Set Point Sources

and Their Substitute in Case of Faults 49
Page 4 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
1 General Requirements
The CAN Bus is a communication port to exchange data between diagnostic systems and
other controllers.
EMR2 receives all necessary data for engine operation.
On the other hand EMR2 sends diagnostic information, measured data and calculated data via
CAN Bus
The Software should be so modular, that the CAN software part can be replaced to a new one,
i.e. for CAN open applications.
1.1 Standards and Additional Specifications

The CAN-Interface is based on following standards :
SAE-J1939/21 1994-07.
SAE-J1939/71 1996-05
SAE-J1939-73 1996-02
DIN ISO 11898 August 1995
Additional Specifications
[1] EMR2 Error Codes, Error Handling, Blink Codes, Fault Lamp, Diagnosis Lamp
1.2 Baud Rate

Baud rate: 250 K Bit/s and 100 K Bit /s
1.3 Configuration Parameter of CAN Identifier and Transmission Rates

The messages are corresponding to the standards see above.
Additional EMR2 specific proprietary messages are defined (s. Appendix 5).
The following parameter are configuration parameters for each send and transmit message:
1. Transmit rate
2. The complete identifiers consisting of:
Priority
PDU (for EMR2 specific messages)
Device-Nr. EMR2 , default: 0
Destination-Address (EMR2 is sender) = External Device Nr., default 3
Source-Address (EMR2 is receiver) = External Device Nr., default 3
Source Address (EMR2 is sender) = Device- Nr. EMR2
Destination Address (EMR2 is receiver) = Device-Nr. EMR2
Page 5 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
1.4 Configuration Parameter of the Messages

- For each data is selectable, whether it is a receive or a send value.
- Each send and each transmit message can be switched off separately by an configuration
parameter.
- The priorities and the source addresses of the receive messages are not in every application
of interest. The mask of the comparison bits, which defines the bits of the receive messages to
be compared can be configured by DEUTZ.
1.5 Not Available or not Valid Data Bytes

If data of a messages are foreseen but not available or not used, then these data have to be
marked as „not defined“ by setting value to FFh, as defined in the standard.
Not valid data, i.e. recognized as defective by an diagnostic function, have to be set to the
value FExx.
1.6 Diagnostic Functions
1.6.1 General
When the system is switched on, the diagnostic functions start after a configurable waiting
time. If receive data not received at the end of that time, error messages will be generated and
stored into the error memory. There are timeout limits for each receive message, which are
configurable as a multiply factor to the expected transmit rate.
Depending on the kind and on the status of the fault the system will be set in a safe position.
Not valid data, i.e. recognized by a diagnostic function as an open wire or a short circuit of a
sensor, have to be set to the value FExx according to the standard SAE-J1939.
Faults of the CAN-bus are transmitted via CAN-Bus, the ISO9141 Bus and via SAE
J1708/J1587 communication lines and will be stored into the error memory of EMR2.
The diagnostic lamp will be activated.
The reason for a fault must be unambiguously determinable.
If there is a timeout of a message, EMR2 has to inform, which message is missing.
Missing data of a CAN-Bus will be replaced by error values inside the EMR2. These error
values are configuration parameters, which can be normal error values in the normal
operation range or max. error values outside the operation range like FE00 or FFFF
There error values of sensor faults are listed in document [1].
Error values in the normal operation range are used like valid data for the other functions of
EMR2, but error messages will be generated.
EMR functions shall not work with data set to error values outside the normal operation
range. Alternative function should be used to get a proper operation of the system, i.e. limp
home function.
Page 6 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
If a data becomes valid again, this valid value will be used again for normal operation, with
the exception of set point values and values documented in [1] with self locking faults .
If an input data of an engine protection functions is missing by time out failure and a max
error value is configured for this data, it can be selected by an configuration parameter,
whether the engine shall be stopped after a warning time or not. Therefore an error message
must be generated too, to show, which missing data caused the engine shutdown.
1.6.2 Set Point Data

Missing set point data are treated as before in EMR, that means TSC1 messages get the phase
concept and the emergency functions as realized in EMR. Attention must be paid to the fact,
that in EMR2 TSC1 messages can be configured in that way, that they will only be used for
limitation of engine speed or torque. In that case these messages doesn’t carry any set point
values.
With configuration parameter engine speed and /or engine torque can be limited, if a TSC1
message is missing by time out monitoring.
The data which will be used in case of missing set point data is specified in a priority order
list: CAN (highest priority, pedal input, fixed speed 2, fixed speed 1(lowest priority) see
Appendix 6.
1.6.3 Engine Protection Message

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

There are different sources for the set point values. This can be communication ports or inputs
of EMR2. A priority is set for each set point source (Appendix 6). The byte „active source of
set point value“ of the special CAN message Measured Data shows, which set point data
sources exist, see the description of that message. Each source can be disabled.
Set Point Values via TSC1 Message

There are more than one TSC1 message EMR2 is able to receive, but only the data of TSC1.a
will be accepted for set point values like engine speed and engine torque and for switching
over the set point mode from speed governor to torque control governor. The other TSC1
messages can only set limits to engine speed or engine torque.
If the control mode byte of a TSC1 message is 0, then this is a sign, that this message don’t
want to have access to EMR2 This message will be excluded from data processing, without
paying attention to the priority bits of this message.
Is TSC1.a configured as set point source and EMR2 receives the control mode 0 in this
message, the limp home function (error handling) with a substitute source for set point data
will be used (Appendix 6).This error handling is necessary because only one TSC1 message
Page 7 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
can set the set point value and this TSC1 message doesn’t give any set point data while
control mode is zero.
A configuration parameter can be set (by DEUTZ) in that way, that the previous set point
value, that means the set point value of the TSC1 message which has been valid before the
TSC1.a message with control mode set to zero arrives, will be used.
In this case no limp home function (error handling) will be activated and no substitute set
point source will be used.
The data process regarding to the priority bits of TSC1 messages is shown in Fig. 7 of the
SAE-J1939/71 document.
Default status: The engine speed governor is active, not the torque control mode.
The EMR2 only accepts a turn over to engine torque control, if engine speed is low idle speed
± 100 1/min and engine torque value is less than 10%.
The condition for turning over to speed governor is, that the engine speed is low idle speed
±100 1/min.
The reaction of EMR2 can be seen at the data of the message EEC1.
With configuration parameters can be selected, if engine speed governor or torque control
mode or a turn over to these modes is allowed for TSC1.a.
Limit values given by TSC1

For each TSC1 message (EMR2 only for TSC1.a) can be selected by configuration
parameters, that only the limitation of engine speed and engine torque will be accepted, not
the set point values. That means with EMR2 it is allowed and configurable, that the set point
values are given by the accelerator pedal hardware input and the limitations are made by
TSC1 messages, i.e. by TSC1.a, too.
The priorities of the limitation values of TSC1 messages are dynamically set by the senders of
the messages as described in the standard SAE-J1939 Fig.7, see also Fig.1 of this
specification.
The valid limits and their priorities are stored in a tabular form This table contains the engine
speed limit, the torque limit and the priority of each TSC1 message source, that means of
TSC1.a to TSC1.d.
The incoming TSC1 limits in between a scan period are proofed for validity and only valid
data are their priority value are stored into the table.
This table is necessary to search for the limit with the higher priority than the other limits
have. If the higher priority is assigned to more than one limit, EMR2 will use the lowest limit
of them.
This procedure will be repeated for each scan period.
If a TSC1 message with new valid limit has been received, the corresponding memory place
in the table will be overridden. If a TSC1 message fails, goes to time out error, doesn’t give
new valid limits or includes control mode set to zero, then the previous valid data (limits and
priority) are used for searching the lowest limit of messages with highest priority.
Page 8 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
1.8 Engine Protection

The engine protection function is available by internal protection functions and by the special
CAN message engine protection.
If more than one source give data to the engine protection function, the lowest value, that
means the highest reduction of engine power, will be used.
If there is a time out fault of a send message which includes a data for engine protection, the
value (last valid value) of this data will be used furthermore for the comparison to get the
lowest value.
Fig. 1 shows the calculation of the limits.
Engine protection source 1 Minimum selection

Engine protection source 2 for engine
protection
...
Engine protection source n
Minimum Limit
selection
TSC1.a Engine Protection

limits
TSC1.b Priority processing s.
standard
TSC1.c
TSC1.d
Fig. 1 Calculation of the limits

to use for engine speed limit and engine torque limit separately
Page 9 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
2 SAE J1939-CAN Messages
The following messages are described in the standard SAE J1939.
The parameter which are defined in the standard but not available in EMR2 are named as
„not defined“. The same string is also used for bytes which are not used in standard messages.
2.1 EEC1:
Transmission rate:
Data Length: 8 Bytes
Data Page: 0
PDUF: 240
PDUS: 4
Priority: s. Appendix 5
Parameter group number: 61444 (00F004H)
Source Address: Device-Nr. EMR2
ID:
Byte 1 Status
8 =engine is working at limited torque (max.
torque curve)
3 = engine speed governor is active
14 = engine torque control ( min. max.
governor) is active
10 = brake system is controlling the torque 1)
Byte 2 Requested engine torque in % 1%/Bit, -125% Offset

related to Mdmax
Byte 3 Engine torque related to Mdmax 1%/Bit, -125% Offset
Byte 4-5 Engine speed 0,125 rpm /Bit
Byte 6-8 Not defined
1
) Since July 23, 2003
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.
Page 10 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
2.2 EEC2
Transmission rate: s. Appendix 5

Data Page: 0
PDUF: 240
PDUS: 3
Parameter group number: 61443 (00F003 H)
Source Address: Device Nr. EMR2
ID:
Byte 1 Status not defined (FF)

Byte 2 Pedal position 0,4 %/Bit
Byte 3 Engine torque related to max engine 1 %/Bit
torque at engine speed
The value of Byte 3 is the actual engine torque in percent of the maximum available engine
torque at the actual engine speed.
The maximum available engine torque at the engine speed is the value which is given by the
torque points 1 to 5 of the engine configuration message.
2.3 Engine Temperature

Data Page: 0
PDUF: 254
PDUS: 238
Parameter group number: 65262 (00FEEE H)
Source Address:
EMR2 sends Device Nr. EMR2
EMR2 receives External Device Nr.
ID:
Byte 1 Coolant temperature 1°C /Bit, -40 °C Offset

Byte 2 Fuel temperature 1°C /Bit, -40 °C Offset
Byte 3 not available (FF)
Page 11 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
Not in all applications oil temperature or coolant temperature are available.
2.4 Engine Fluid Level/Pressure

Data Page: 0
PDUF: 254
PDUS: 239
Parameter group number: 65263 (00FEEF H)
Source Address:
ID:
Byte 1 Not defined

Byte 2 Not defined
Byte 3 Oil level 0.4%/Bit, 0% Offset
Byte 4 Oil pressure 4 kPa/Bit, 1/25bar /Bit
Byte 5,6 not available (FF)
Byte 8 Coolant level 0.4%/Bit, 0% Offset
Page 12 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
2.5 Inlet / Exhaust Conditions

Data Page: 0
PDUF: 254
PDUS: 246
Parameter group number: 65270 (00FEF6 H)
Source Address:
ID:
Byte 1 Not defined

Byte 2 Boost pressure 2 kPa/Bit = 1/50 bar/Bit
Byte 3 Intake manifold temperature 1°C /Bit, -40 °C Offset
2.6 Fuel Economy

Data Page: 0
PDUF: 254
PDUS: 242
ID:
Byte 1-2 Fuel rate 0,05 L/h /Bit
Byte 3,4 Instantaneous fuel economy km/l
Page 13 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
2.7 Engine Hours

Data Page: 0
PDUF: 254
PDUS: 229
Parameter group number: 65253 (00FEE5 H)
ID:
Byte 1-4 Engine hours 0,05 h/Bit

Page 14 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
2.8 TSC1.a to TSC1.d

Data Page: 0
PDUF: 0
PDUS: Device Nr. EMR2
Parameter group number:
Source Address: External Device Nr.
ID:
Byte 1 Control Bits SAE J1939/71, Parameter 3.3.1

Bit 1, 2 Override control mode
Bit 3, 4 Requested speed control condition ( not used)
Bit 5, 6 Override control priority (not used)
Bit 7, 8 Not defined
Byte 2,3 Requested speed / speed limit 0,125 rpm /Bit
Byte 4 Requested torque / torque limit 1% /Bit, -125% Offset
Override Control Mode:

00 no changes, the last mode will be used
Bytes 2 to 8 will be ignored.
01 set speed control, using bytes 2 and 3 for requested speed
Byte 4 will be ignored
no limits will be changed
10 torque control mode, using byte 4 for requested torque
Bytes 2 and 3 will be ignored
no limits will be changed
11 set limits
Bytes 2 and 3 are the limit of speed control.
Byte 4 contents the limit for torque control
Priority Bits
00 Highest Priority
01 High Priority
10 Low Priority
11 Lowest Priority
The reaction of this message can be read with EEC1
Page 15 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
Set point data for engine speed or engine torque are only accepted from TSC1.a message, not
from any other message.
With configuration parameters can be selected, if engine speed governor (set point source is
engine speed data) or torque control mode (set point source is torque data) or a turn over to
these modes is allowed for TSC1.a.
The requested speed value is a set point data. EMR2 controlls the engine in that way that this
is the engine speed under full load. Without load the engine speed will be higher and
calculated using the droop.
Example
Requested speed 2000 rpm, droop = 5%
then speed without load n = 2000*(1+droop) = 2100 rpm
For each TSC1 message can be selected by configuration parameters, that only the limitation
of engine speed and engine torque will be accepted, not the set point values.
If the control mode byte of a TSC1 message is 0, then this is a sign, that this message don’t
want to have access to EMR2 This message will be excluded from data processing, without
paying attention to the priority bits of this message (see chapter 1.7 set point data).
Page 16 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
2.9 Engine Configuration

Data Page: 0
PDUF: 254
PDUS: 227
Parameter group number: 65251 (00FEE3 H)
Source Address: Device Number EMR2
ID:
Bytes 1-28 according to 3.3.17 of SAE J1939/71
Byte 1,2 Engine speed at idle ( point 1)

Byte 3 Percent torque at idle ( point 1)
Byte 4, 5 Engine speed ( point 2)
Byte 6 Percent torque ( point 2)
Byte 7, 8 Engine speed (point 3)
Byte 9 Percent torque (point 3)
Byte 16, 17 Engine speed at high idle, engine torque = 0 (point 6)
Byte 18, 19 Gain(KP) / droop 1)
Byte 20, 21 Reference engine torque (Nm) (maximum torque of engine torque map)
Byte 22 to 24 not defined
Byte 25 Minimum engine speed value for TSC1 messages
Byte 26 Maximum engine speed value for TSC1 messages
Byte 27 Minimum engine torque value for TSC1 messages
Byte 28 Maximum engine torque value for TSC1 messages
1
) a configuration parameter determines , whether Gain, as defined in the standard, or droop will be send:
Gain = ∆ torque / ∆ speed
Droop = (nmax - nrated) / nrated * 100 % n = speed, resolution droop 1% /Bit
In EMR2 the followings points are fixed at:

Point 2: point of rated speed
Point 3 point of maximum engine torque
Page 17 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
The value of the reference engine torque will not be modified. It is the highest value of torque
map 1 and it is a reference value for engine torques which are expressed as percentage.
The torque map 2 is lower than torque map 1.
The max. engine torque in bytes 20,21 is not equal to a fixed fuel amount, because of
correction of engine torque by temperature.
The values of the points 1 to 5 are percent values with the reference engine torque as its
basis.
They are calculated as the actual torque map value reduced by the actual engine protection
value, i.e. reduction because of engine temperature is too high.
The values are modified in case of selection of another engine torque map,
The values will be modified in following cases

-the torque map has been changed,
-Gain / droop is switched over.
-power reduction is active.
Boost pressure, 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 Protocol (
appendix 1) must be used.
2.10 Ambient Conditions

Data Page: 0
PDUF: 254
PDUS: 245
ID:
Byte 1 barometric pressure 0,5 kPa/Bit = 1/200 Bar/Bit

Byte 2,3 not available (FF)
Byte 4-8 not available (FF)
Page 18 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
2.11 Vehicle Electrical Power

Data Page: 0
PDUF: 254
PDUS: 247
ID:
Byte 1-6 not available (FF)

Byte 7,8 switched battery power at the input of 0,05 V/Bit
EMR2
2.12 Cruise Control / Vehicle Speed

Data Page: 0
PDUF: 254
PDUS: 241
ID:

Byte 2,3 vehicle speed 1 / 256 km/h = 1 / 412 mph
Byte 4 - 8 not available (FF)
Page 19 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
3 EMR2 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 , that means EMR2 too, should use the source address as a filter for
the input buffers of the CAN controller. The source address is part of the ID and for each
receive message configurable.
3.1 Function Mode Control

Data Page: 0
PDUF: 255
PDUS: 02
Parameter group 00FF02
number:
Byte 1 Number of engine torque map

Byte 2 Droop selection, number of droop
Byte 3 Engine speed mode
Byte 4 controller mode
Number of engine torque map: 0= no modification of torque map

1= switch to torque map 1
Droop selection 0 = no modification of droop

1 = selects droop 1
2 = selects droop 2
3 = selects engine speed depended droop
Engine speed mode 0= no modification of speed mode

1= freeze and use the actual engine speed
2= freezes the requested engine speed
3= switches to variable engine speed
4= switches to constant speed 1
5= switches to constant speed 2
Controller mode 0= no modification of controller mode

1= engine speed governor
2= engine torque governor
Page 20 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
Controller mode can only be changed by this command, if there is no TSC1.a message
configured. If there is TSC1.a message configured, then only TSC1.a can change the
controller mode.
Default: torque map 1, droop 1, variable engine speed, engine speed governor.
3.2 Engine Protection

Data Page: 0
PDUF: 255
PDUS: 03
number:
Source Address: external Device Nr.
ID:
Byte 1 Power reduction

Byte 2 Lock status
Power reduction:
Reduces the max. engine torque curve of the torque map
Range: 0 to 100%
Resolution: 1% / Bit
Zero will cause the EMS to switch off the engine.
100% means no power reduction.
Lock status (Engine Start Lock):

00 H = no engine start prohibition
01 H = engine stops and engine start prohibition will be active
FF H = not defined ( no protection)
If there are actually more than one sources for Power reduction, i.e. internal power protection
by temperature and this message, the lowest value, that is the highest reduction will be used.
If there is a timeout of the data the last valid data will be used furthermore for the calculation
of the lowest value. See also chapter 1.8
Page 21 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
3.3 Engine Stop Request

Data Page: 0
PDUF: 255
PDUS: 22
number:
Source Address: external Device Nr.
ID:
Byte 1 Engine stop
Engine stop = 1 the engine will be stopped

Engine stop ≠ 1 the engine will not be stopped by this command
This message allows an engine shutoff additional to the message engine protection.
But this message will be received by buffer 15, the general input for request, which is open
for all senders.
This message should not be send periodically.
If the engine has been stopped new messages can be received for start prevention.
Page 22 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
3.4 Measured Data
3.4.1 Measured Data 1

Data Page: 0
PDUF: 255
PDUS: 4
number:
Source Address: EMR2 Device Nr.
ID:
Byte 1 Preheat information

Byte 2-3 Engine speed 0,125 rpm /Bit
Byte 4 Boost pressure 2kPa/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 status
Preheat information
Bit
1 Preheat active
2 Ready for start
3 Postheat active
4 Glow plugs active
5 Flame glow plugs active
6 Flame fuel valve active
7 Push button active
8 Not defined
Page 23 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
Can status
0 Initialization after power on
1 or 2 engine not started, waiting for start
3 engine starts (is cranking)
4 engine has started, is running, waiting for Can messages
with speed or torque demand
5 engine is running, CAN messages for speed or torque control used.
6 CAN messages for speed or torque demand failed (time-out)
EMR uses another input for set point values as a substitute, i.e. accelerator
pedal
7 Engine start protection is active
Page 24 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16

Data Page: 0
PDUF: 255
PDUS: 18
Parameter group FF12
number:
ID:
Byte 1 Droop
Byte 2-3 set point data engine speed, droop calculated
Byte 4 source of set point data engine speed
Byte 5, 6 engine speed, sensor 1
Byte 7, 8 engine speed, sensor 2
Droop
Droop = (nmax - nrated) / nrated * 100 %
n = engine speed, resolution 1% /Bit
Set point data engine speed, droop calculated

This is a data inside EMR2 after selection of the source of requested speed at the input of the
speed governor, calculated with droop.
0,125 rpm/bit ; 0 rpm offset
range: 0 to 8031,875 rpm
Source of set point data engine speed:

This value shows, which signal is the source of the actual set point data.
0 No set point data
1 Pedal input ( Analog / PWM input)
2 Hand throttle lever
3 Error value used
4 TSC1.a
5 reserved ( for TSC1.b)
6 reserved ( forSAE-J1587 PID 91 accelerator pedal)
7 Constant speed 1
8 Constant speed 2
9 Frozen engine speed (actual engine speed saved)
10 Frozen engine speed (set point speed saved)
11 special function ( hold)
12 special function ( min)
13 special function ( max)
14 reserved (for PTO)
15 idle calibration mode
Page 25 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
16 reserved (for VP2 pedal data)
Engine speed sensor 1, 2

If there is no engine speed sensor 2 available, i.e. a vehicle speed sensor is mounted, then the
value will be FFh.
0,125 rpm/bit ; 0 rpm offset
range: 0 to 8031,875 rpm

Data Page : 0
PDUF : 255
PDUS: 19
number:
ID:
Byte 1 Power reduction

Byte 2 Maximum available engine torque at current
speed
Byte 3, 4 Maximum available engine speed
Byte 5, 6 Hold engine speed
Byte 7, 8 not available
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.
Resolution 1 %.
Range 0 to 100%
The value of no power reduction is 100%
Maximum available engine torque at current speed

The maximum available 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 torque is available.
If there are no actual limitations or power reductions, the available engine torque is given by
the torque curve. The value will be 100%, then.
Page 26 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
Resolution: 1%
Range: 0% to 100%
Maximal available engine speed

The maximum available engine speed varies because of engine protection functions and other
CAN messages.
Resolution: 1/8 rpm
Range 0 to 8000 rpm
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 FFh

Data Page : 0
PDUF : 255
PDUS: 20
number:
ID:
Byte 1, 2 set point value fuel quantity 0,1 mm3 / Stroke / Bit
Byte 3, 4 desired value fuel quantity for drive ability 0,1 mm3 / Stroke / Bit
map
Byte 5, 6 actual rack position 0,01 mm / Bit
Byte 7, 8 desired rack position 0,01 mm / Bit
In mode engine speed governor Bytes 3,4 are not available and set to FFh.
In mode torque governor Bytes 3,4 have the same values as Bytes 1,2.
Page 27 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
3.5 State of Inputs 1

Data Page: 0
PDUF: 255
PDUS: 10
Parameter group 00FF0A
number:
ID:
Byte 1 Digital, PWM 1 Pin F 18

Byte 2 Digital 6, Analog 1 Pin F 24
Byte 3 Digital 2, PWM 2 Pin F 21
Byte 4 Digital 4 Pin F 19
Byte 5 Digital 8, Analog3 Pin F 20
Byte 7 Digital 5 Pin M 6
Byte 8 Digital 7, Analog 2 Pin M24
What is connected to the inputs depends on the respective application.
Digital:
0 = boolish 0
100 = boolish 1
PWM:
range 0 to 100 %
resolution 1% / bit
Analog:
range 0 to 5V = 0 to 100
resolution 0.05V / bit
FF H = Information not available ( Not defined)
Page 28 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
3.6 State of Inputs 2

Data Page: 0
PDUF: 255
PDUS: 23
number:
ID:
Byte 1 Digital 9, analog4 Pin M21

Byte 2 Digital 10/ vehicle speed Pin F7
Byte 3 not available
What is connected to the inputs depends on the respective application.
Digital:
0 = boolish 0
100 = boolish 1
PWM:
range 0 to 100 %
resolution 1% / bit
Analog:
range 0 to 5V = 0 to 100
resolution 0.05V / bit
Page 29 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
3.7 State of Digital Outputs

Data Page: 0
PDUF: 255
PDUS: 11
Parameter group 00FF0B
number:
Source Address: EMR2-Device Nr.
ID:
Byte 1 Diagnostic lamp Pin F 4

Byte 2 Digital 7, engine speed Pin F 16
Byte 3 Digital, PWM 1 Pin F 5
Byte 5 Digital 4 Pin M 3
Byte 6 Digital Output 5 Pin F 15
Byte 7 Digital Output 3 Pin M 2
Byte 8 Digital Output 6/ PWM2 Pin M 7
What is connected to the outputs depends on the respective application.
Digital:
0 = boolish 0
100 = boolish 1
PWM:
range 0 to 100 %
resolution 1% / bit
engine speed: 40rpm / bit
Page 30 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
3.8 Controller Configuration

Data Page: 0
PDUF: 255
PDUS: 12
Parameter group 00FF0C
number:
ID:
Byte 1 governor configuration

Byte 2 engine speed configuration
Byte 3 maximum torque curve configuration
Byte 4 droop configuration
Byte 5 not defined
Byte 6 not defined
Byte 7 configuration of inputs
Byte 8 configuration of outputs
Governor configuration:
0 = all speed governor
1 = torque control governor ( min-max. governor)
2 = selection between all speed governor or torque control governor possible
Engine speed configuration

0 = variable set point 1
1 = selection between constant engine speed 1 or constant engine speed 2 possible
2 = selection between variable set point 1 or constant engine speed 1 possible
3 = selection between variable set point 1 or hold engine speed (actual set point speed
stored)
4 = selection between variable set point 1or hold engine speed (actual engine speed stored)
5 = special engine speed configuration (SAME)
6 = variable set point 2
7 = selection between variable set point MAX or constant engine speed 1 possible
8 = selection between variable set point MAX or hold engine speed (actual set point speed
stored)
9 = selection between variable set point MAX or hold engine speed (actual engine speed
stored)
Variable set point 1 is the actual selected variable set point of CAN, accelerator pedal or set
point input signal.
Page 31 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
Variable set point 2 is the Hand throttle lever

Variable set point MAX = Maximum selection between variable set point 1 and variable set
point 2.
Maximum torque curve configuration

0 = only max. torque curve 1 available
1 = selection between max. torque curve 1 or 2 possible
2 = selection between max. torque curve 1, 2 or 3 possible
3 = selection between max. torque curve 1 and max torque curve 3
Droop configuration
0 = only constant droop 1 available
1 = droop characteristic curve
2 = selection between constant droop 1 or 2 available
3 = selection between droop 1 and droop characteristic curve available.
4 = selection between droop 2 and droop characteristic curve available.
5 = selection between droop 1, droop 2 and droop characteristic curve available.
Configuration of Inputs
If bit = 0 If bit = 1
Bit 1 Digital 1, PWM 1 Pin F 18 Digital PWM
Bit 3 Digital 6, Analog 1 Pin F 24 Digital Analog
Bit 4 Digital 7, Analog 2 M24 Digital Analog
Bit 5 Digital 8, Analog 3 Pin F 20 Digital Analog
Bit 6 Digital 9, Analog 4 Pin M21 Digital Analog
Bit 7 Digital 10 / vehicle speed Pin F7 Digital Vehicle speed
Bit 8 Value set to zero Not available
Configuration of Outputs
Wert = 0 Wert = 1
Bit 2 Digital Ausgang 6 / PWM2 Pin M 7 Digital PWM
Bit 3 Digital 7, Frequency Pin F 16 Digital Frequency
Bit 3 Wert = 0 Not available
Page 32 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
3.9 Limitation

Data Page : 0
PDUF : 255
PDUS: 21
number:
ID:
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 not defined
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 EMR is actually working at the limit.
If there is a limit set, but no operation parameter has reached this limit, the corresponding bit
will not be set.
Page 33 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
Active Limitation 2
Bit 6-8 reserved
Bit 5 overrun condition
Bit 4 smoke limitation
Bit 3 limitation by barometric pressure
Bit 2 reserved (= 0 because limitation of vehicle speed by receive message
SAE-J1587 PID74 not available)
Bit 1 reserved (= 0 because receive message torque limiting SAE-J1587 PID 68
not available)
A Bit will only be set, when EMR is actually working at the limit.
If there is a limit set, but no operation parameter has reached this limit, the corresponding bit
will not be set
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
Engine speed limit

0 normal speed limit (configuration parameter)
1 TSC1.a
2 TSC1.b
3 TSC1.c
4 TSC1.d
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

0 normal limitation by max. torque curve
1 TSC1.a
2 TSC1.b
3 TSC1.c
4 TSC1.d
5 reserved (will not appear, because receive message torque limiting SAE-J1587 PID 68
is not available)
6 smoke limitation
This is the number of the actual lowest engine torque limit, even when the engine is actually
not working at this limit
Page 34 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
Source of power reduction

0 = no power reduction
1 = engine protection
2 = oil pressure
3 = intake manifold temperature
4 = Coolant temperature
5 = barometric pressure
The number of the signal that makes the highest reduction will be send in this byte.
The engine must not actually work at the limit to get a value different from zero. It is
sufficient that a limit is set.
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 4.
Engine stop
0 = no special engine stop, normal engine stop
1 = Engine shutdown for engine protection
2 = CAN Message Engine Stop Request
3 = Oil pressure too low
4 = Oil level too low
5 = Coolant temperature too high
6 = Coolant level too low
7 = Intake manifold temperature
8 = reserved ( SAE-J1587 command
9 = reserved (for VP2 not available)
The value of this byte shows the reason, why EMR2 has shutoff the engine.
If more limitations in EMR2 exist than these bytes represent, than this list will be enlarged.
Page 35 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
4 Diagnostic Messages
These messages are specified in SAE-J1939-73 February 1996

There are 12 messages described, but not all messages available from EMR2.
A request for a non available messages will be answered by EMR2 with an negative
acknowledgment (NACK).
The negative and positive acknowledgment is shown in Appendix 3.
Messages that require more than 8 data bytes must be transferred with the „Multipacket
Transport“ (SAE-J1939-21 July 1994). See Appendix 1
Page 36 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
4.1 Number of faults (DM5)

The number of faults are transmitted on request.
There is a different between active faults and previously active faults.
Previously active faults are faults which have been in the active state for at least more than
one time after the error memory has been cleared and they are not active in that moment.
They are named as passive faults.
Request for reading the number of faults ( Standard Request)

EMR receives this messages as a request to send the number of faults, which have occurred
once at least and are active or passive at that moment.
Transmission rate: If required
Data Page: 0
PDUF : 234
PDUS : EMR2 Device Nr
Parameter group number: 00EA00
ID:
Byte 1 to 3: PGN-Nr. Of message DM5
Answer Number of faults (standard message Diagnostic Readiness DM5)
Transmission rate: on request

Data Page: 0
PDUF: 254
PDUS: 206
Parameter group 65230 (00FECE)
number:
ID:
Byte 1 Number of active faults

Byte 2 Number of faults stored in the error memory of EMR2
(= number of active faults + number of passive faults)
Page 37 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
4.2 Active faults ( DM 1 )
The transmission rate is according to SAE-J1939.

That means :
1.The standard update rate is 1s, if active faults exist.
2. The message will be transmitted immediately, if a fault becomes active or inactive.
3. Only the first change of state of the fault will be transmitted immediately , if the fault
changes more than one time between active and inactive in a second
At the end of the second the actual state of fault will be transmitted.
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
Parameter group 65226 (00FECA)
number:
Source Address: EMR Device Nr.
ID:
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 not defined
LS: see Appendix 2

SPN: see Appendix 4 Failure codes
FMI: see Appendix 4 Failure codes
OC: Occurrence counter is the number of changes between passive and active of a fault
state since the last time the fault memory has been cleared.
The following data will be send on request, if there is no active fault:

(according to standard SAE-J1939/21 Juli94)
LS=0, SPN= 524287, FMI = 31, OC = 127
The Multipacket Transport (SAE-J1939/21 July 94) must be used if there is more then one
active fault. The data stream is:
Page 38 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
LS, SPN, FMI, OC, SPN, FMI, OC, SPN, FMI, OC .....etc.
4.3 Passive Faults (DM2)
Passive faults are faults which have been in the active state for at least more than one time
after the error memory has been cleared and they are not active at that moment.
EMR2 sends the complete entry of the internal error memory in this message, that means all
active and passive faults.
They are transmitted on request.
Request
Transmission rate: On Request
Data Page : 0
PDUF : 234
PDUS : EMR Device Nr.
Parameter group 59904
number:
ID
Byte 1-3 Parameter group number of the requested message,
here PGN of DM2
Answer 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:
ID:
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 (= 1)
Bit 1 to 7 Occurrence counter (OC)
Page 39 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
Byte 7, 8 not defined, value is FF
LS: see Appendix 2

SPN: see Appendix 4 Failure codes
FMI: see Appendix 4 Failure codes
OC: Occurrence counter is the number of changes between passive and active of a fault
state since the last time the fault memory has been cleared.
The Multipacket Transport (SAE-J1939/21 July 94) is used if there is more then one entry in
the error memory. The data stream is:
LS, SPN, FMI, OC, SPN, FMI, OC, SPN, FMI, OC .....etc.
The following data will be send, if there is no fault stored

SPN = 524287, FMI = 31, OC= 127, LS according to actual lamp state.
Page 40 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
4.4 Freeze Frame Parameter (DM4)

Freeze Frame Parameter are data which are recorded at that moment, when the fault becomes
active..
Request message
Transmission rate: If required
Data Page: 0
PDUF: 234
PDUS : EMR Device Nr.
number:
ID
Byte 1-3 Parameter group number of the requested message,

here PGN of DM4
Answer: Freeze Frame Parameter ( Standard message DM4 )

Data length
Data Page: 0
PDUF: 254
PDUS: 205
Parameter group 65229 (00FECD)
number:
ID:
Byte 1 Number of the following data bytes (Length) = 20 = 14h

Byte 2 to 5 Diagnostic Trouble Code (DTC)
Byte 6,7 Not available
Byte 8, 9 Engine speed 1/8 rpm/bit
Byte 10 - 19 Not available
Byte 20, 21 EMR2 specific Engine hours 1 h / Bit
DTC consist on 19 Bits SPN, 5 Bits FMI, 1 bit =1 and 7 Bits Occurrence Counter
Multipacket Transport is used, because there are more than 8 data bytes.
The message above is used too( not the Multipacked Transport), if there are no freeze data
available. In that case the 8 data bytes filled as follow:
Number = 0, DTC = 0, Bytes 6 to 8 = FF.
Page 41 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
4.5 Diagnostic Data Clear ( DM3, DM11)
If the EMR receives the standard diagnostic message DM3, the fault memory and the
fault messages will be cleared, including the freeze frame parameters.
DM3:
Transmission rate: if required
Data Page: 0
PDUF: 254
PDUS: 204
Parameter group 65228 (00FECC)
number:
ID:
The answer of EMR will be a positive Acknowledgment.
2. DM11 is a request to EMR2 to clear the active faults, the non active faults and the freeze
frame parameter
DM11:
Transmission rate: if required
Data Page: 0
PDUF: 254
PDUS: 211
Parameter group 65235 (00FED3)
number:
ID:
The answer of EMR will be a positive Acknowledgment.
Page 42 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
5 Appendix
5.1 Appendix 1: Multipacket Transport
If more then 8 data bytes must be send they have to be separated in different packets. The first
message is the Broadcast Announce Message (BAM). After that the data packets will be send.
BAM:
Transmission rate: s. below.
Data length: 8
Data Page: 0
PDUF: 236
PDUS: 255
Priority: 6
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
Page 43 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
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 44 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
5.2 Appendix 2: Lamp status

Malfunction Lamp status
consist of 2 Bits with
00 not active (not lightened)
01 active (lightened)
11 not defined
Bit 1,2 Engine Protection Lamp
• is active, if a data is out of normal operating range, i.e. in warning 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
active, if the EMR diagnostic lamp is blinking to show an critical fault.
That means an engine shut off is necessary.
Bit 7,8 Emission Related Lamp
not defined in EMR (11)
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 45 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
5.3 Appendix 3: Acknowledgment

according to SAE-J1939-21
Transmission rate: Once, after receiving a message

which needs an Acknowledge.
Data Page: 0
PDUF: 232
PDUS: 255
Priority: 6
Parameter group 59647 (E8FF)
number:
ID:
Byte 1 0 for positive Acknowledge

1 for negative Acknowledge
Byte 6 to 8 parameter group number of the message,
which needs an Acknowledge
5.4 Appendix 4: Error codes and SPN

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 document [1].
There are 4 different ways to interpret the SPN Bytes as defined in SAE-J1939-73 OCT1998.
EMR2 uses Version 1 to be compatible to EMR1.
The following example shows how to interpret the received bytes of EMR2 message DM1.
Page 46 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
EXAMPLE DM1 Received:
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
=000 0000 0000 1011 1110
=0 0 0 B E
= 00BEh = 190d = Engine Speed Error
FMI = 01011 = 11d
OC = 0000011 = 3
So the fault 190 with kind of error 11 has occured 3 times.
Softwareroutine 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 47 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
5.5 Appendix 5: Overview CAN-Messages

Controller message Rate / ms default send receive PDU
Buffer Priority
0 EEC1 20 3 X Standard message F004
EEC2 50 3 X Standard message F003
Fuel Economy 100 6 X Standard message FEF2
Cruise Control /Vehicle Speed 100 6 X Standard message FEF1
Engine Temperature 1000 6 X Standard message FEEE
Inlet Exhaust Condition 500 6 X Standard message FEF6
Engine Fluid Level /Pressure 500 6 X Standard message FEEF
Measured data 1 200 6 X EMR2 specific FF04
Limitation 100 3 X EMR2 specific FF15
1 Vehicle electrical power 1000 6 X Standard message FEF7
Ambient conditions 1000 6 X Standard message FEF5
State of Inputs 1 1000 6 X EMR2 specific FF0A
State of Inputs 2 1000 6 X EMR2 specific FF17
State of outputs 1000 6 X EMR2 specific FF0B
Engine hours Request 6 X Standard message FEE5
Controller Configuration Request 6 X EMR2 specific FF0C
Number of faults (DM5) Request 6 X Standard message FECE
Engine Configuration 5000 6 X Standard message FEE3
Active faults (DM1) s. 4.2 6 X Standard message FECA
Freeze frame data (DM4) Request 6 X Standard message FECD
Stored faults (DM2) Request 6 X Standard message FECB
2 TSC1.a 20 3 X Standard message 00XX
3 TSC1.b 20 3 X Standard message 00XX
4 TSC1.c 20 3 X Standard message 00XX
5 TSC1.d 20 3 X Standard message 00XX
6
7 Engine Temperature 1000 6 X Standard message FEEE
8 Inlet Exhaust Condition 500 6 X Standard message FEF6
9 Engine Fluid Level /Pressure 500 6 X Standard message FEEF
10 Engine Protection 100 3 X EMR2 specific FF03
11 Function mode control 500 6 X EMR2 specific FF02
12 Diagnostic data clear (DM11) When 6 X Standard message FED3
required
13 Diagnostic data clear (DM3) When 6 X Standard message FECC
required
14 Engine stop request When 2 X EMR2 specific FF16
required
15 Request When X Standard message EAXX
required
Page 48 of 50
Author: J.Brardt
Dept.: TK-EV
Version: 29.01.2004 17:14
Print: 29.01.2004 17:16
Specification for EMR2 Date: 29.01.2004 17:14
5.6 Appendix 6: Configuration of Available Set Point Sources and Their Substitute in Case of Faults
Abbreviations
F1 Constant engine speed 1
F2 Constant engine speed 2
HM Frozen engine speed (actual engine speed saved)
HS Frozen engine speed (set point speed saved)
Sync digital synchronizer up and down inputs
FP Pedal input
H Hand throttle lever
CAN CAN TSC1
Available Set Point Sources (only one available at the same time, switchover possible)
Config Same Sync FP H CAN F1 HS HM F2 Order of Substitute
Nr. Sources
0 X F2
1 X X None
2 X X F2
3 X X F2
4 X X F2
5 X None
6 X 1) X 1) X F2
7 X 1) X 1) X F2
8 X 1) X 1) X F2
9 X X FP, F2
10 X X FP, F2
11 X X FP, F2
12 X None, last values used
1) Maximum value of both sources will be used
d:\datensaetze\can\can_spec_emr2_6_engl.doc
Specification for EMR2 Date: 29.01.2004 17:14
List of Modifications
Date Issue Modification Name

18.03.2002 All Document revised Brardt
12.12.2002 Appendix SPN EPN Bytes and routines explained Brardt
01.04.2003 DM2 Complete error memory, not only passive faults Brardt
23.07.2003 EEC1 Engine Brake System added to byte1 Brardt
29.01.2004 DM4 Engine hours 1h/bit Brardt
d:\datensaetze\can\can_spec_emr2_6_engl.doc

CAN-Specification EMR2 Engl

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CAN-Specification EMR2 Engl

Uploaded by

Copyright:

Available Formats

Specification for EMR2 Date: 29.01.

CAN-Specification for EMR2

1.1 Standards and Additional Specifications 5

1.2 Baud Rate 5

1.3 Configuration Parameter of CAN Identifier and Transmission Rates 5

1.4 Configuration Parameter of the Messages 6

1.5 Not Available or not Valid Data Bytes 6

1.6 Diagnostic Functions 6

1.7 Set Point Data 7

1.8 Engine Protection 9

2 SAE J1939-CAN MESSAGES 10

2.3 Engine Temperature 11

2.4 Engine Fluid Level/Pressure 12

2.5 Inlet / Exhaust Conditions 13

2.6 Fuel Economy 13

2.7 Engine Hours 14

2.8 TSC1.a to TSC1.d 15

2.9 Engine Configuration 17

2.10 Ambient Conditions 18

2.11 Vehicle Electrical Power 19

2.12 Cruise Control / Vehicle Speed 19

3 EMR2 SPECIFIC CAN-MESSAGES BASED ON SAE J1939 20

3.1 Function Mode Control 20

3.2 Engine Protection 21

3.3 Engine Stop Request 22

3.4 Measured Data 23

3.5 State of Inputs 1 28

3.6 State of Inputs 2 29

3.7 State of Digital Outputs 30

3.8 Controller Configuration 31

4.1 Number of faults (DM5) 37

4.2 Active faults ( DM 1 ) 38

4.3 Passive Faults (DM2) 39

4.4 Freeze Frame Parameter (DM4) 41

4.5 Diagnostic Data Clear ( DM3, DM11) 42

5.1 Appendix 1: Multipacket Transport 43

5.2 Appendix 2: Lamp status 45

5.3 Appendix 3: Acknowledgment 46

5.4 Appendix 4: Error codes and SPN 46

5.5 Appendix 5: Overview CAN-Messages 48

5.6 Appendix 6: Configuration of Available Set Point Sources

1.1 Standards and Additional Specifications

1.2 Baud Rate

1.3 Configuration Parameter of CAN Identifier and Transmission Rates

1.4 Configuration Parameter of the Messages

1.5 Not Available or not Valid Data Bytes

1.6 Diagnostic Functions

1.6.2 Set Point Data

1.6.3 Engine Protection Message

1.7 Set Point Data

Set Point Values via TSC1 Message

Limit values given by TSC1

1.8 Engine Protection

Engine protection source 1 Minimum selection

TSC1.a Engine Protection

Fig. 1 Calculation of the limits

2 SAE J1939-CAN Messages

The following messages are described in the standard SAE J1939.

Byte 2 Requested engine torque in % 1%/Bit, -125% Offset

Transmission rate: s. Appendix 5

Byte 1 Status not defined (FF)

2.3 Engine Temperature