CAB500 CAN MODIFICATION

210319/1

www.lem.com

Table of Contents:
1.
Introduction ............................................................................................................................
2.
ECUReset Service : ...............................................................................................................
2.1
ECUReset Service Description : ......................................................................................
2.2
ECUReset Service example: ............................................................................................
3.
ReadDataByIdentifier Service: ...............................................................................................
3.1...................................................
3.1.1
ReadDataByIdentifier Service request ........................................................................
3.2
ReadDataByIdentifer Service response: ...........................................................................
3.3
sub-function:....................................
3.4-function: ..................
3.4.1
ReadDataByIdentifier Service request ......................................................................
3.4.2
ReadDataByIdentifier Service response : .................................................................
3.5-function : ..................... 1
3.6-function:........................ 1
3.6.1
ReadDataByIdentifier Service request ...................................................................... 1
3.6.2
ReadDataByIdentifier Service response ................................................................... 1
3.7-function:............................ 1
3.8
function: 15
3.8.1
ReadDataByIdentifier Service request ...................................................................... 1
3.8.2
ReadDataByIdentifier Service response ................................................................... 1
3.9-function: ............ 1
4.
WriteDataByIdentifer Service : ............................................................................................. 1
4.1-function: .............................. 1
4.2-function:..................................
4.3
WriteDataByIdentifer Service description for-function: ................... 2
4.4-function:...................... 2
4.5
WriteD-function: ........................ 2
4.6-function : .......................... 2
4.7-function: ... 2
4.8-function:.... 2
Table 1 : Filter frequencies values versus CAN frame values ......................................... 1
Table 2 : CAN speed parameters versus CAN frame values............................................ 1
Table 3 : CAB500_Ip frame period versus CAN frame values.......................................... 1

210319/1

www.lem.com

1. Introduction
This documentation allows modifying the parameters inside the CAB500-C-SP5 for all versions
superior to PR06.
The customer shall not be used the CAN frame ID 0x68d in his CAN network. The ID 0x3C2
and 0x68d will be booked for CAB500 sensor by default.
The parameters modifiable are:* Sensor IDs (CAB500_Ip frame ID, UDS_CLIENT frame ID and UDS_SERVER frame ID)* IIR Filters frequency used to measure the current* CAN speed* Period of the CAB500_Ip frame (current frame)
The communication protocol uses:* DoCAN ISO 15765 (2011)* UDS ISO 14229 (2013)
To execute these modifications you need a CAN 2.0 interface which is able to send a CAN frame.
. This interface should be connected to thesensor with CANHigh and CANLow pins (See the datasheet).
If you want to read a parameter saved in the sensor, use the ReadDataByIdentifier Service.
If you want to modify a parameter in the sensor, use the WriteDataByIdentifier Service thenexecute an ECUReset service in order to update this new function.
The default parameters are :- Sensors ID:
Frame Name
Default CAN ID-

CAB500_Ip
frame
0x3C2

UDS_CLIENTUDS_SERVER

0x68D

0x68E

Filter frequency : the sensor does not have a IIR filter, it computes an average on 10ms
CAN speed : 500kbauds
Period of the CAB500_Ip frame is 10ms

The IDs ranges available are between 0x221 to 0x3FF and between 0x40B to 0x7F0.

210319/1

www.lem.com

3 4

1. ECUReset Service :1.1 ECUReset Service Description :ECUReset service with two sub-functions:- HardReset- SoftReset

Message
CAN ID
Description

ECUReset
servicerequest to
reset thesoftware

0x68D

Message
CAN ID
Description

Name

Data
Length(Nbbytes)UDS_
CLIENT

Name

3

Data
Length(Nbbytes)

Messagelaunchtype

Signal Description

SignalValues

Start
Bit

End
Bit

Single frame composedby 2 data

0x02

0

7

0x11

8

15

16

31

no cyclic
ECUReset service
message,send bySub-functions available :the- hardResetexternal
application- SoftReset

Messagelaunch
type

0x01
0x03

-

Other : noactionSignal Description

SignalValues

Start
Bit

End
Bit

Single frame composedby 2 data

0x02

0

7

- positive response

0x51

8

15

- negative response

0x7F

0x01
0x03
Other : noaction

16

23

0x00

24

56

ECUReset service :ECUReset
service
response
to reset thesoftware

0x68E

UDS_
SERVER

8no cyclic
message,send by the
CAB500sensorSub-functions available :- hardReset-SoftReset-

Unused210319/1

www.lem.com

4 4

1.2 ECUReset Service example:
The external application is the client and wants to reset the sensor with the HardReset subfunction: 0x01.

Figure 1 : ECUReset Service frames to reset the sensor

This external application send the UDS_CLIENT (ID= 0x68D) frame in which :- 0x02 defined a single frame composed of 2 usable data
- 0x11 defined the ECUReset service- 0x01 defined the HardReset sub-function.
The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x02 defined a single frame composed of 2 usable data
- 0x51 defined the positive response of ECUReset service- 0x01 defined the HardReset sub-function.

210319/1

www.lem.com

5 4

2. ReadDataByIdentifier Service:
ReadDataByIdentifier Service with three sub-functions:
CAN ID : 0xF010
Filter frequency : 0xF011
CAN Speed : 0xF012
CAN frame period : 0xF013

2.1 ReadDataByIdentifer Service:

2.1.1 ReadDataByIdentifier Service request
For all these sub-functions, the external application sends this request frame:

Message
Description

CAN
ID

Name

Data
Length(Nbbytes)

Messagelaunchtype

SignalValueSingle frame composedby 3 data

0x03

0

7

0x22

8

15

16

31

ReadDataByIdentifier

ReadDataBy

Identifier
servicerequest to
readparameter ofthe software

Signal Description

no cyclic

0x68D

UDS_CLIENT

4

message,send by theexternal
application

serviceStart End
Bit BitSub-functions available :- CAN ID

0xF0102.2 ReadDataByIdentifer Service response:
For the CAN ID sub-function response, the process of 2 consecutive frames is used :- First consecutive frame- Flow control frame- Second consecutive frame

210319/1

www.lem.com

6 4

The first consecutive frame is composed of:

Message
Description

ReadData
ByIdentifier
service
response toread CAN ID
sub-function

CAN ID

0x68E

Name

Data
Message
Length(Nblaunch typebytes)UDS_SERVER

8no cyclic
message,send by thesensorSignal Description

SignalValues

Start
Bit

End
Bit

First consecutive frame

0x10

0

7

composed of 9 usable
data

0x09

8

15

16

23

24

39

40

55

56

63

ReadDataByIdentifier
service :- positive response

0x62- negative response

0x7F

Sub- function : CAN ID

0xF010
0x3C2

CAB500_Ip frame ID
MSB byte of
UDS_CLIENT frame ID(Default
values)

0x06(Default
values)

The flow control frame sends by external application to validate the reception of the first
consecutive frame receiving:

Message
Description

ReadData
ByIdentifier
service flow
control frametoacknowledge
the first
consecutive
frame
receiving(CAN ID subfunction)

210319/1

CAN ID

0x68D

Name

UDS_
CLIEN
T

Data
Length(Nbbytes)

3

Messagelaunch typeno cyclic
message,send by theexternal
applicationwww.lem.com

Signal Description

Signal
Value

Start
Bit

End
Bit

Flow control frameand FS

0x30

07

BS (no managed)

0

8

15

STmin (no managed)

0

16

23

7 4

The second consecutive frame is composed of:
Message
Description

ReadData
ByIdentifier
service
response
to readCAN IDCAN ID

0x68E

Name

UDS_
SERVER

Data
Length(Nbbytes)

8

Messagelaunch typeno cyclic
message,send by thesensorSignal Description

Signal Start
End
Values Bit
Bit

Second consecutive
frame

0x21

LSB byte of
UDS_CLIENT frame
ID

0x8D(Default
values)UDS_SERVER frame 0x068E
ID(Default

0

7

8

15

16

31

32

63

values)

Unused0x00

Note : Please send the first and second consecutive frames without waiting the flow control
frame (bug known).

2.3 ReadDataBy-function:

The external application is the client and wants to read the sensor identifiers (CAN ID).

Figure 2 : ReadDataByIdentifier service frames to read CAN frames identifiersThis external application send the UDS_CLIENT (ID= 0x68D) frame in which :- 0x03 defined a single frame composed of 3 usable data
- 0x22 defined the ReadDataByIdentifier service- 0xF010 defined the Sensor frames identifiers
The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x10 followed by 0x09 defined a first consecutive frame composed of 9 usable data
- 0x62 defined the positive response of ReadDataByIdentifier service- 0xF010 defined the Sensor identifiers sub-function- 0x03 followed by 0xC2 defined the CAB500_Ip frame ID : 0x3C2- 0x06 is the fisrt highest byte of the UDS_CLIENT ID.
This external application send the UDS_CLIENT (ID= 0x68D) frame in which :-0x30 defined the flow control frame in response to the first consecutive frame (BS and STmin are
not managed)
The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x21 the second consecutive frame

210319/1

www.lem.com

8 4

- 0x8D is the lowest byte of the Client request identifier. So the UDS_CLIENT identifier is equal to0x68D- 0x06 followed by 0x8E defined the Server response ID ( UDS_SERVER= 0x68E).

-

2.4 ReadDataByIdentifier Service
function:
2.4.1 ReadDataByIdentifier Service request
For all these sub-functions, the external application sends this request frame:

Message
Description

CAN
ID

Name

Data
Length(Nbbytes)

Messagelaunchtype

Single frame composedby 3 data
ReadDataByIdentifier

ReadDataBy

Identifier
servicerequest to
readparameter ofthe software

Signal Description

no cyclic

0x68D

UDS_CLIENT

4

message,send by theexternal
application

service

SignalValue

Start End
Bit Bit

0x03

0

7

0x22

8

15

16

31

Sub-functions available :- Filter frequency

0xF0112.4.2 ReadDataByIdentifier Service response :For the filter frequency sub-function response, the process is just composed of 1 single response
frame:

210319/1

www.lem.com

9 4

Message
Description

CAN
ID

Name

Data
Message
Lengthlaunch(Nb
type
bytes)

Signal Description

Single frame composedof 4 data
ReadDataBy
Identifier
service
UDS_
response to 0x68E
SERVER
read thefilterfrequency

Signal Start
Values Bit

End
Bit

0x04

0

7

8

15

16

31

32

39

39

63

ReadDataBy Identifier
service:8

no cyclic
message,send bythesensor- positive response

0x62- negative response

0x7F

Sub-function : filter
frequency

0xF011

filter frequency value
UnusedSee
theTable10x00

2.5 ReadDataByfunction :-An external application is the client and wants to read the filter frequency.

Figure 3 : ReadDataByIdentifier service frames to read the filter frequency

This external application send the UDS_CLIENT (ID= 0x68D) frame in which :- 0x03 defined a single frame composed of 3 usable data
- 0x22 defined the ReadDataByIdentifier service- 0xF011 defined the filter frequency sub-function
The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x04 defined a single frame composed of 4 usable data
- 0x62 defined the positive response of ReadDataByIdentifier service- 0xF011 defined the filter frequency sub function- 0x01 defined that the filter frequency is 10Hz (function = ValueReceived *10 )210319/1

www.lem.com

0 4

Table 1 : Filter frequencies values versus CAN frame values
Frequency filter
10Hz
20Hz
30Hz
40Hz
50Hz
60Hz
70Hz
80Hz
90Hz
100Hz
110Hz
120Hz
130Hz
140Hz
150Hz
160Hz
Average every 10ms
whitout filter

210319/1

Filter frequency value on
CAN frame
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
0x0A
0x0B
0x0C
0x0D
0x0E
0x0F
0x10

0xFF

www.lem.com

1 4

2.6 ReadDataByfunction:-

2.6.1 ReadDataByIdentifier Service request
For all these sub-functions, the external application sends this request frame:

Message
Description

CAN
ID

Data
Length(Nbbytes)

Name

Messagelaunchtype

Signal Description
Single frame composedby 3 data
ReadDataByIdentifier

ReadDataBy

Identifier
servicerequest to
readparameter ofthe software

no cyclic

0x68D

UDS_CLIENT

4

servicemessage,send by theexternal
application

SignalValue

Start End
Bit Bit

0x03

0

7

0x22

8

15

16

31

Sub-functions available :- CAN Speed

0xF012

2.6.2 ReadDataByIdentifier Service response
For the CAN speed sub-function response, the process is just composed of 1 single response
frame:

Message
Description

CAN
ID

Name

Data
Length(Nbbytes)

Message launch
type

Signal Description

SignalValuesSingle frame composed by 5
data

0x05

0

7

- positive response

0x62

8

15

- negative response

0x7F

Sub-function : CAN speed

0xF012

16

31

CAN speed value

See
Table 2

32

47

Unused

0x00

48

63

Start End
Bit
Bit

ReadDataBy Identifier service :ReadDataBy
Identifier
UDS_
service
0x68E
SERVER
response toread theCAN speed

210319/1

8

no cyclic
message,send by thesensorwww.lem.com

2 4

Table 2 : CAN speed parameters versus CAN frame values
CAN speed

CAN speed value on CAN frame

125k

0x007D

250k

0x00FA

500k

0x01F4

2.7 ReadDataByfunction:-

The external application is the client and wants to read the CAN speed.

Figure 4 : ReadDataByIdentifier service frames to read CAN speed

This service uses the single frame to send the data.
This external application send the UDS_CLIENT (ID= 0x68D) frame in which :- 0x03 defined a single frame composed of 3 usable data
- 0x22 defined the ReadDataByIdentifier service- 0xF012 defined the CAN speed sub-functions
The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x05 defined a single frame composed of 5 usable data
- 0x62 defined the positive response of ReadDataByIdentifier service- 0xF012 defined the CAN Speed sub function-0x00 followed by 0x7D defined that the CAN speed is 125kBds

210319/1

www.lem.com

3 4

2.8 ReadDataBy-function:
2.8.1 ReadDataByIdentifier Service request
For all these sub-functions, the external application sends this request frame:

Message CAN
Description ID

Name

Data
Length(Nbbytes)

Messagelaunch type

Single frame composedby 3 data

ReadDataBy

Identifier
servicerequest to 0x68D UDS_CLIENT
readparameter ofthe software

Signal Description

no cyclic
ReadDataByIdentifier
message, send
serviceby the external
application
Sub-functions available :4- CAN frame period

Signal Start End
Value
Bit
Bit

0x03

0

7

0x22

8

15

16

31

0xF0132.8.2 ReadDataByIdentifier Service response
For the CAN CAB500_Ip frame period sub-function response, the process is just composed of 1
single response frame:

Message
Description

ReadDataBy
Identifier
service
response toread theCAN
CAB500_Ip
frame period210319/1

CAN ID

Name

Data
Message
Lengthlaunch type(Nb bytes)

Signal Description

SignalValues

Start
Bit

End
Bit

Single framecomposed by 5 data

0x05

0

7

8

15

0xF013

16

31

CAB500_Ip frame
periodSee
Table 3

32

47

Unused

0x00

48

63

ReadDataBy Identifier
service :

0x68E

UDS_
SERVER

8no cyclic
message,send by thesensorwww.lem.com- positive response

0x62- negative response
Sub-function :CAB500_Ip frame
period

0x7F

4 4

Table 3 : CAB500_Ip frame period versus CAN frame values
CAB500_Ip frame period

CAB500_Ip frame period on CAN frame

10ms

0x000A and all other values

100ms

0x0064

2.9 ReadDataBy
sub-function:
The external application is the client and wants to read the CAN CAB500_Ip frame period.

Figure 5 : ReadDataByIdentifier service frames to read CAB500_Ip frame period

This service uses the single frame to send the data.
This external application send the UDS_CLIENT (ID= 0x68D) frame in which :- 0x03 defined a single frame composed of 3 usable data
- 0x22 defined the ReadDataByIdentifier service- 0xF013 defined the CAN CAB500_ip period sub-function
The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x05 defined a single frame composed of 5 usable data
- 0x62 defined the positive response of ReadDataByIdentifier service- 0xF013 defined the CAN Speed sub function-0x00 followed by 0x7A defined that the CAN CAB500_Ip period is the corresponding decimalvalue: 10ms

210319/1

www.lem.com

5 4

3. WriteDataByIdentifer Service :WriteDataByIdentifier with three sub-functions:
CAN ID : 0xF010
Filter frequency : 0xF011
CAN Speed : 0xF012
CAN frame period : 0xF013
The process is specific for each sub function.
After writing (after using this command), wait at least 1 second before turning off to avoid amemory corruption (error code =0x40).

3.1 WriteDataByfunction:-

For the CAN ID sub-function, the request is composed of :- First consecutive frame sent by the external application- Flow control frame sent by sensor to confirm the receiving of the previous frame- Second consecutive frame sent by the external application

Message
Descriptio
n

CAN
ID

WriteData
By
Identifier
0x68D
servicerequest to
write CAN
ID

Name

UDS_
CLIENT

Data
Length(Nbbytes)

8

Messagelaunchtype

no cyclic
message,send by theexternal
application

Signal Description

Signal
Value

Start
Bit

End
Bit

First consecutive
frame

0x10

0

7

composed of 9 data

0x09

8

15

WriteDataByIdentifier
service

0x2E

16

23

Sub function : CAN ID

0xF01024

39

CAB500_Ip frame ID
value

0x03C2(default value)

40

55

56

63

MSB byte of the
UDS_CLIENT frame ID
value

210319/1

www.lem.com

0x06(default value)

6 4

Message
Description

CAN
ID

Data
Length(Nbbytes)

Name

WriteDataBy
Identifier
service
UDS_
response to 0x68E
SERVER
write CAN
ID
parameters

Message
Description

WriteDataBy
Identifier
servicerequest to
write CAN ID
parameters

Message
Description

WriteDataBy
Identifier
service
response towrite CAN ID
parameters210319/1

CAN
ID

0x68D

CAN
ID

0x68E

Name

UDS_
CLIENTNameUDS_SERVER

8

Data
Length(Nbbytes)

4

Messagelaunchtype

no cyclic
message,send bytheexternal
application

Messagelaunchtype

Signal
Value

Start
Bit

End
Bit

Flow control frameand FS

0x30

07

BS (no managed)

0x00

8

15

STmin (no managed)

0x00

16

23

Unused

0x00

24

63

Signal Description

SignalValue

Start End
Bit
Bit

Second consecutive
frame

0x21

0

7

0x8D

8

15

16

23

no cyclic
message,
LSB of thesend by the UDS_CLIENT frame ID
external
value
application UDS_SERVER frame ID
value

Data
Message
Lengthlaunch(Nb
type
bytes)

8

Signal Description

no cyclic
message,send bythesensor(default value)

0x068E(default value)

Signal Description

SignalValuesSingle frame composedby 3 data

0x03

Start End
Bit
Bit

0

7

8

15

16

31

WriteDataByIdentifier
service:- positive response

0x6E- negative response

0x7F

Sub-function : CAN ID

0xF010www.lem.com

7 4

Unused210319/1

www.lem.com

0x00

32

63

8 4

3.2 WriteDataByfunction:-In this first example, the external application is the client and wants to modify the sensor IDs
parameters with CAB500_IP = 0x3C0 ; UDS_CLIENT = 0x600 and UDS_SERVER= 0x601.

Figure 6 : WriteDataByIdentifier service frames to modify CAN identifiersThis service uses the consecutive frame to send the data.
This external application send the UDS_CLIENT (ID= 0x68D) frame in which :- 0x10 followed by 0x09 defined a first frame composed of 9 usable data
- 0x2E defined the WriteDataByIdentifier service- 0xF010 defined the Sensor ID identifiers sub-functions- 0x03 followed by 0xC0 defined that the new CAB500_ip frame ID is 0x3c0- 0x06 defined the first high byte of the client request frame ID
The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x30 defined the flow control frame which means that the sensor has read the first frame andwait the next data. (BS and STmin are not managed)This external application send the next data with the UDS_CLIENT (ID= 0x68D) frame in which :- 0x21 defined that this frame is the first consecutive frame- 0x00 is the low byte of the client request ID. So the UDS_CLIENT frame ID is 0x600.
- 0x06 followed by 0x01 defined that the new server response frame ID is 0x601 (UDS_SERVER)
The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x03 defined a single frame composed of 3 usable data
- 0x6E defined the positive response of WriteDataByIdentifier service- 0xF010 defined the Sensor ID identifierThis service modifies the EEPROM memory and this modification will be taken account after areset.

210319/1

www.lem.com

9 4

3.3 WriteDataByfunction:-

For the filter frequency sub-function response, the process is just composed of one request and
one response frames:

Message
Description

WriteDataBy
Identifier
servicerequest to
write filter
frequency
parameters

Message
Description

WriteDataBy
Identifier
service
response towrite filter
frequency
parameters210319/1

CAN
ID

0x68D

CAN
ID

Name

UDS_
CLIENT

Name

UDS_
0x68E
SERVER

Data
Length(Nbbytes)

5

Data
Length(Nbbytes)

0

Messagelaunch typeno cyclic
message,send by theexternal
application

Messagelaunchtype

no cyclic
message,send bythe sensor

Signal Description

SignalValuesSingle frame composedby 4 data

0x04

0

7

WriteDataByIdentifier
service

0x2E

8

15

Sub-function : Filter
frequency

0xF01116

31

Filter frequency value

See theTable 1

32

39

Signal Description

SignalValues

Start
Bit

End
Bit

Single frame composed by
3 data

0x03

0

7

8

15

Start End
Bit
Bit

WriteDataBy Identifier
service:- positive response

0x6E- negative response

0x7F

Sub-function : filter
frequency

0xF011

16

31

Unused

0x00

32

63

www.lem.com

20 4

3.4 WriteDataByfunction:-In this second example, the external application is the client and wants to modify the filter
frequency to set 50Hz. You can see the figure 3 to have the link between frequencies and CAN
frame data.

Figure 7 : WriteDataByIdentifier service frames to modify the filter frequency

This service uses the single frame to send the data.
This external application send the UDS_CLIENT (ID= 0x68D) frame in which :- 0x04 defined a single frame composed of 4 usable data
- 0x2E defined the WriteDataByIdentifier service- 0xF011 defined the filter frequency sub-functions- 0x05 defined that the filter frequency is the corresponding hexadecimal number : 0x05
(ValueSent = frequency /10 )The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x03 defined a single frame composed of 3 usable data
- 0x6E defined the positive response of WriteDataByIdentifier service- 0xF011 defined the filter frequency sub function
This service modifies the EEPROM memory and this modification will be taken account after areset.

-

3.5 WriteDataByfunction:

For the CAN speed sub-function response, the process is just composed of one request and one
response frames:

Message
Description

WriteDataBy
Identifier
servicerequest to
write CAN
speed
parameters210319/1

CAN
ID

0x68D

Name

UDS_
CLIENT

Data
Length(Nbbytes)

6

Messagelaunch typeno cyclic
message, sendby the external
application

Signal Description

SignalValuesSingle frame composedby 4 data

0x04

0

7

WriteDataBy Identifier
service:

0x2E

8

15

Sub-function: CAN
speed

0xF012

16

31

CAN speed value

See
Table 232

47

www.lem.com

Start End
Bit
Bit

2

4

3.6 WriteDataByfunction :Message
Description

CAN
ID

Name

-

Data
Length(Nbbytes)

Messagelaunch type

Signal Description

Single frame composedby 3 data
WriteDataBy
Identifier
service
UDS_
response to 0x68E
SERVER
write CAN
Speed
parameters

8

no cyclic
message,send by thesensorSignal Start End
Values Bit
Bit

0x03

0

7

8

15

WriteDataBy Identifier
service:- positive response

0x6E- negative response

0x7F

Sub-function : CAN
speed

0xF012

16

31

Unused

0x00

32

63

In this third example, the external application is the client and wants to modify the CAN speed to
set 125k/Bds .

Figure 8 : WriteDataByIdentifier service frames to modify CAN speed

This service uses the single frame to send the data.
This external application send the UDS_CLIENT (ID= 0x68D) frame in which :- 0x05 defined a single frame composed of 5 usable data
- 0x2E defined the WriteDataByIdentifier service- 0xF012 defined the CAN speed sub-functions- 0x00 followed by 0x7D defined that the speed is the corresponding decimal number : 125
The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x03 defined a single frame composed of 3 usable data
- 0x6E defined the positive response of WriteDataByIdentifier service- 0xF012 defined the CAN Speed sub function
This service modifies the EEPROM memory and this modification will be taken account after areset.

210319/1

www.lem.com

22 4

3.7 WriteDataBy-function:
For the CAB500_Ip frame period sub-function, the process is just composed of one request and
one response frames:

Message
Description

CAN
ID

Name

WriteDataBy
Identifier
servicerequest to
UDS_
0x68D
CLIENT
write
CAB500_Ip
frame periodparameters

Message
Description

CAN
ID

Name

Data
Length(Nbbytes)

6

Data
Length(Nbbytes)

Messagelaunch typeno cyclic
message,send by theexternal
application

Messagelaunchtype

Signal Description

Single frame composedby 5 data

0x05

0

7

WriteDataBy Identifier
service:

0x2E

8

15

Sub-function: CAB500_Ip
frame period

0xF013

16

31

CAB500_Ip frame period
value

See
Table 332

47

Signal Description

Single frame composed by
3 dataWriteDataBy
Identifier
service
response to
UDS_
0x68E
write
SERVER
CAB500_Ip
frame periodparameters210319/1

8

no cyclic
message,send by thesensorSignal Start End
Values Bit
Bit

Signal Start End
Values Bit
Bit

0x03

0

7

8

15

WriteDataBy Identifier
service:- positive response

0x6E- negative response

0x7F

Sub-function : CAB500_Ip
frame period

0xF01316

31

Unused

0x00

32

63

www.lem.com

23 4

3.8 Writ-function:
In this third example, the external application is the client and wants to modify the CAN CAB500_Ip
frame period to set 100ms.

Figure 9 : WriteDataByIdentifierservice frames to modify CAB500_Ip frame period

This service uses the single frame to send the data.
This external application send the UDS_CLIENT (ID= 0x68D) frame in which :- 0x05 defined a single frame composed of 5 usable data
- 0x2E defined the WriteDataByIdentifier service-function- 0xF013 defined the- 0x00 followed by 0x64 defined that the period is the corresponding decimal number : 100
The sensor response with the UDS_SERVER (ID = 0x68E) frame in which :- 0x03 defined a single frame composed of 3 usable data
- 0x6E defined the positive response of WriteDataByIdentifier service- 0xF013 defined the-function
This service modifies the EEPROM memory and this modification will be taken account after areset.

210319/1

www.lem.com

24 4