FMS-Standard - LogiCom GmbH

Transcription

LogiCom GmbH
FMS-Standard
Definition and description
of the conformance test
Christian Pfaffenzeller
Dokument LC_FMS_001_03_doc_E
03. April 2003
For this underlay and contents become the protection provided by the laws in form of asserted. The use of the
underlay which is going directly against the legal regulations and particularly regulation adverse is pursued with
the legally scheduled means.
LogiCom GmbH, Gautinger Straße 51, 82152 Krailling, Germany
Table of contents
1
OVERVIEW
3
1.1 PURPOSE
1.2 CAN DRIVER
1.2.1 CAN FMS-STANDARD DATA PACKETS
1.2.2 HIGH FMS-STANDARD DATA PACKETS
1.3 TEST ENVIRONMENT
1.3.1 LOGICOM, CAN SIMULATOR
1.3.2 LOGICOM, REFERENCE EQUIPMENT
1.3.3 CUSTOMER, TEST EQUIPMENT
1.3.4 LOGICOM, ANALYSIS SOFTWARE
3
3
3
3
4
4
4
4
5
2
6
CONFORMANCE TEST
2.1 REQUIREMENTS
2.1.1 REQUIREMENTS FOR THE CUSTOMER
2.1.2 REQUIREMENTS FOR THE CONFORMANCE TEST SOFTWARE (CUSTOMER)
2.2 PROCEDURE OF TEST
2.2.1 INSTALLATION
2.2.2 TEST STAGE I
2.2.3 TEST STAGE II
2.2.4 EVALUATION
2.2.5 VALIDATION
2.2.6 CONCLUSION (CONFORMANCE TEST REPORT)
6
6
6
7
7
7
7
8
8
8
3
9
DEFINITIONS
3.1 RECORD FILES
3.1.1 CAN FMS-STANDARD DATA PACKETS (TEST STAGE I)
3.1.2 HIGH FMS-STANDARD DATA PACKETS (TEST STAGE II)
 2003 Copyright LogiCom GmbH
9
9
10
Seite 2 von 12
1 Overview
1.1
Purpose
It is the purpose of the conformance test to check the hard and software of a Onboard unit
regarding the reception of CAN data packets and the interpretation of the FMS-standard
interface.
1.2
CAN driver
1.2.1 CAN FMS-standard data packets
Within a CAN driver different data packets are received. The data packets of the FMSstandard also part of these data packets.
These data packets are described as CAN FMS-standard data packets.
1.2.2 High FMS-standard data packets
The received CAN FMS-standard data packets contain a variety of physical values, for
example speed and revolution. A CAN adapter can interpret these CAN FMS-standard data
packets and arrange the values in a new data packet with another format.
These data packets are described as High FMS-standard data packets.
Seite 3 von 12
1.3
Test environment
LogiCom - Analysis-Software
Test stage Basic:
Check for Requests from Test-E.
“Recv-Data minus Send-Data”
Send-Data
FF
E3
FF
E3
FF
E3
FF
E3
FF
E3
E3
FF
E3
FF
E3
FF
E3
FF
E3
01
EC
01
EC
01
EC
01
EC
01
EC
EC
01
EC
01
EC
01
EC
01
EC
FF
EF
FF
EF
FF
EF
FF
EF
FF
EF
EF
FF
EF
FF
EF
FF
EF
FF
EF
3B
A2
3B
A2
3B
A2
3B
A2
3B
A2
A2
3B
A2
3B
A2
3B
A2
3B
A2
5B
AC
5B
AC
5B
AC
5B
AC
5B
AC
AC
5B
AC
5B
AC
5B
AC
5B
AC
4E
32
4E
32
4E
32
4E
32
4E
32
32
4E
32
4E
32
4E
32
4E
32
7E
3F
7E
3F
7E
3F
7E
3F
7E
3F
3F
7E
3F
7E
3F
7E
3F
7E
3F
Test stage I:
Check CAN-FMS-Standard-Data-Packets
“Compare Reference-E. and Test-E.”
Recv-Data
D2
FF
D2
FF
D2
FF
D2
FF
D2
FF
FF
D2
FF
D2
FF
D2
FF
D2
FF
FF
E3
FF
E3
FF
E3
FF
E3
FF
E3
E3
FF
E3
FF
E3
FF
E3
FF
E3
01
EC
01
EC
01
EC
01
EC
01
EC
EC
01
EC
01
EC
01
EC
01
EC
FF
EF
FF
EF
FF
EF
FF
EF
FF
EF
EF
FF
EF
FF
EF
FF
EF
FF
EF
3B
A2
3B
A2
3B
A2
3B
A2
3B
A2
A2
3B
A2
3B
A2
3B
A2
3B
A2
5B
AC
5B
AC
5B
AC
5B
AC
5B
AC
AC
5B
AC
5B
AC
5B
AC
5B
AC
4E
32
4E
32
4E
32
4E
32
4E
32
32
4E
32
4E
32
4E
32
4E
32
7E
3F
7E
3F
7E
3F
7E
3F
7E
3F
3F
7E
3F
7E
3F
7E
3F
7E
3F
CAN-FMS
D2
FF
D2
FF
D2
FF
D2
FF
D2
FF
FF
D2
FF
D2
FF
D2
FF
D2
FF
FF
E3
FF
E3
FF
E3
FF
E3
FF
E3
E3
FF
E3
FF
E3
FF
E3
FF
E3
01
EC
01
EC
01
EC
01
EC
01
EC
EC
01
EC
01
EC
01
EC
01
EC
FF
EF
FF
EF
FF
EF
FF
EF
FF
EF
EF
FF
EF
FF
EF
FF
EF
FF
EF
3B
A2
3B
A2
3B
A2
3B
A2
3B
A2
A2
3B
A2
3B
A2
3B
A2
3B
A2
5B
AC
5B
AC
5B
AC
5B
AC
5B
AC
AC
5B
AC
5B
AC
5B
AC
5B
AC
4E
32
4E
32
4E
32
4E
32
4E
32
32
4E
32
4E
32
4E
32
4E
32
7E
3F
7E
3F
7E
3F
7E
3F
7E
3F
3F
7E
3F
7E
3F
7E
3F
7E
3F
D2
FF
D2
FF
D2
FF
D2
FF
D2
FF
FF
D2
FF
D2
FF
D2
FF
D2
FF
Test stage II:
Check High-FMS-Standard-Data-Packets
“Compare Reference-E. and Test-E.”
High-FMS
FF
E3
FF
E3
FF
E3
FF
E3
FF
E3
E3
FF
E3
FF
E3
FF
E3
FF
E3
01
EC
01
EC
01
EC
01
EC
01
EC
EC
01
EC
01
EC
01
EC
01
EC
FF
EF
FF
EF
FF
EF
FF
EF
FF
EF
EF
FF
EF
FF
EF
FF
EF
FF
EF
3B
A2
3B
A2
3B
A2
3B
A2
3B
A2
A2
3B
A2
3B
A2
3B
A2
3B
A2
5B
AC
5B
AC
5B
AC
5B
AC
5B
AC
AC
5B
AC
5B
AC
5B
AC
5B
AC
4E
32
4E
32
4E
32
4E
32
4E
32
32
4E
32
4E
32
4E
32
4E
32
7E
3F
7E
3F
7E
3F
7E
3F
7E
3F
3F
7E
3F
7E
3F
7E
3F
7E
3F
D2
FF
D2
FF
D2
FF
D2
FF
D2
FF
FF
D2
FF
D2
FF
D2
FF
D2
FF
CAN-FMS
FF
E3
FF
E3
FF
E3
FF
E3
FF
E3
E3
FF
E3
FF
E3
FF
E3
FF
E3
01
EC
01
EC
01
EC
01
EC
01
EC
EC
01
EC
01
EC
01
EC
01
EC
FF
EF
FF
EF
FF
EF
FF
EF
FF
EF
EF
FF
EF
FF
EF
FF
EF
FF
EF
3B
A2
3B
A2
3B
A2
3B
A2
3B
A2
A2
3B
A2
3B
A2
3B
A2
3B
A2
5B
AC
5B
AC
5B
AC
5B
AC
5B
AC
AC
5B
AC
5B
AC
5B
AC
5B
AC
4E
32
4E
32
4E
32
4E
32
4E
32
32
4E
32
4E
32
4E
32
4E
32
7E
3F
7E
3F
7E
3F
7E
3F
7E
3F
3F
7E
3F
7E
3F
7E
3F
7E
3F
D2
FF
D2
FF
D2
FF
D2
FF
D2
FF
FF
D2
FF
D2
FF
D2
FF
D2
FF
High-FMS
FF
E3
FF
E3
FF
E3
FF
E3
FF
E3
E3
FF
E3
FF
E3
FF
E3
FF
E3
01
EC
01
EC
01
EC
01
EC
01
EC
EC
01
EC
01
EC
01
EC
01
EC
FF
EF
FF
EF
FF
EF
FF
EF
FF
EF
EF
FF
EF
FF
EF
FF
EF
FF
EF
3B
A2
3B
A2
3B
A2
3B
A2
3B
A2
A2
3B
A2
3B
A2
3B
A2
3B
A2
5B
AC
5B
AC
5B
AC
5B
AC
5B
AC
AC
5B
AC
5B
AC
5B
AC
5B
AC
4E
32
4E
32
4E
32
4E
32
4E
32
32
4E
32
4E
32
4E
32
4E
32
7E
3F
7E
3F
7E
3F
7E
3F
7E
3F
3F
7E
3F
7E
3F
7E
3F
7E
3F
D2
FF
D2
FF
D2
FF
D2
FF
D2
FF
FF
D2
FF
D2
FF
D2
FF
D2
FF
LogiCom
LogiCom
Customer
CAN-Simulation
Reference-Equipment
Test-Equipment
Illustration 1.2
CAN-Architecture
1.3.1 LogiCom, CAN simulator
The CAN simulator produces most different data packets. Also different and faulty data
packets are produced besides the data packets of the FMS-standard interface.
1.3.2 LogiCom, Reference equipment
During a test stage the reference device records all received FMS-standard data packets
(see illustration 1.1), interprets these data packets and stores the contained values as High
FMS-standard data packets chronologically (see illustration 1.1) into reference files (format
described chapter 3).
1.3.3 Customer, Test equipment
The test device is attached to CAN bus architecture analogously to the reference device and
therefore receives the same data information as the reference device. The test device must
be able to receive and to store all data packets of the FMS-standard interface (see illustration
1.1) (test stage I). Furthermore the test device must be able to interpret these data packets
Seite 4 von 12
and to store values in form of a High FMS-standard data packet (see illustration 1.1) (test
stage II).
1.3.4 LogiCom, Analysis software
The records of the reference device and the test device in conclusion are transferred to a
PC. The transfer is done by different communication channels (depending on the features of
the test device), e.g. serial interface, exchange of a memory card.
The analysis software compares the data and marks faults and deviations.
Seite 5 von 12
2 Conformance test
2.1
Requirements
2.1.1 Requirements for the customer
Requirements for the customer are:
•
•
•
•
Delivery of a " technical data sheet " of the test device
Delivery of a " technical description of the physical CAN interfaces "
Delivery of a “technical description of the conformance test software"
Delivery of a test device with installed conformance test software
2.1.2 Requirements for the conformance test software (customer)
Requirements for the conformance test software of the test device are:
•
•
•
•
•
Functions for the reception of the CAN FMS-standard data packets
(full CAN FMS-standard driver)
Functions to the interpretation of the CAN FMS-standard data packets
(full CAN FMS-standard adapter)
Functions for the internal storage of the CAN FMS-standard data packets
Functions for the internal storage of the High FMS-standard data packets
Possibility to transmit the record files to a PC for evaluation
Seite 6 von 12
2.2
Procedure of test
2.2.1 Installation
The test surroundings are built up within the installation phase:
•
•
•
•
Setup, installation and putting into operation of CAN architecture
Setup, installation and putting into operation of the CAN simulator
Setup, installation and putting into operation of the reference device
Setup, installation and putting into operation of the test device
2.2.2 Test stage I
Within the test stage I, the API (Application Programming interface) CAN FMS-standard data
packets is checked:
•
•
•
Start of the record of CAN FMS-standard data packets (reference device)
Start of the record of CAN FMS-standard data packets (test device)
Start of the CAN simulation
•
•
Single test run with a duration of 30 seconds
Reception of around 7,800 CAN fms data packets (around 250 Kbytes)
2.2.3 Test stage II
Within the test stage II, the API (Application Programming interface) High FMS-standard data
packets is checked:
•
•
•
Start of the record of High FMS-standard data packets (reference device)
Start of the record of High FMS-standard data packets (test device)
Start of the CAN simulation
•
•
Single test run with a duration of 30 seconds
Reception of 1,500 High fms data packets (around 235 Kbytes)
Seite 7 von 12
2.2.4 Evaluation
These produced record files by the reference device and the test device from test stage I and
test stage II are evaluated by the analysis software:
•
•
•
Transmission of all record files of the test device to the analysis software
Assignment of all record files of the reference device to the analysis software
Run of the analysis software
2.2.5 Validation
The analysis software compares the record files of the test device and the reference device
using the following validation criteria.
Test stage I
•
•
•
•
Record file of the test device contains all received CAN FMS-standard data packets
Record file of the test device doesn't contain any NON CAN FMS-standard data
packets
Record file of the test device doesn't contain any faulty characters
Record file of the test device is equal the record file of the reference device
Test stage II
•
•
•
•
Record file of the test device contains all received High FMS-standard data packets
Record file of the test device doesn't contain any NON High FMS-standard data
packets
Record file of the test device doesn't contain any faulty characters
Record file of the test device is "roughly" identical to the record file of the reference
device (restriction by a possible deviation of the record time)
2.2.6 Conclusion (conformance test report)
•
•
Written documentation of the conformance test
Written evaluation of the conformance test (passed/not passed)
Seite 8 von 12
3 Definitions
3.1
Record files
3.1.1 CAN FMS-standard data packets (test stage I)
Remark
This record file contains all received CAN FMS-standard data packets.
Data packets
Storage interval:
Storage duration:
Storage requirements:
Record:
Length:
End identifier:
Provided by the reception of the data packets
30 seconds
256 Kbytes
Chronologic (as received)
33 characters, incl. end identifier < CR ><LF>
<CR>(0Dh)<LF>(0Ah)
Structure of the record file
Data packet 1:
Data packet 2:
:
Data packet n:
001.0000 00FEF1FF121ABCFFFFF3FF<CR><LF>
001.0500 00F003FFBAFFFFFFFFFFFF<CR><LF>
:
003.1700 00FEE9FFFFFFFFE3E43F7C<CR><LF>
Structure of the data packets
Position
Name
1 until 8
9
10 until 11
12 until 13
14 until 15
16 until 17
18 until 19
20 until 21
22 until 23
24 until 25
26 until 27
28 until 29
30 until 31
32
33
Time stamp, beginning at Zero in Seconds (sss.tttt)
Blank
PGN Byte 1 (Hex)
PGN Byte 2 (Hex)
PGN Byte 3 (Hex)
Data Byte 1 (Hex)
Data Byte 2 (Hex)
Data Byte 3 (Hex)
Data Byte 4 (Hex)
Data Byte 5 (Hex)
Data Byte 6 (Hex)
Data Byte 7 (Hex)
Data Byte 8 (Hex)
<CR> (0Dh)
<LF> (0Ah)
Seite 9 von 12
3.1.2 High FMS-standard data packets (test stage II)
Remark
This record file contains all produced High FMS-standard data packets.
Data packets
Storage interval:
Storage duration:
Storage requirements:
Record:
Length:
Length min.:
Length max:
Length typical:
Separating character:
End identifier:
50 Hertz (every 20 milliseconds)
30 seconds
256 Kbytes
Chronologic (as received)
any with separating character “:” and end identifier < CR ><LF>
:(3Ah)
<CR>(0Dh)<LF>(0Ah)
Structure of the record file
Data packet 1:
Data packet 2:
:
Data packet n:
17:0:1:1:5:... :18.10:82<CR><LF>
18:0:1:1:5:... :18.33:82<CR><LF>
:
19:0:1:1:5:... :20.28:83<CR><LF>
Structure of the data packets
Data field
Name
Unit
Value 1
Value 2
Value 3
Value 4
Value 5
Value 6
Value 7
Value 8
Value 9
Value 10
Value 11a
Value 11b
:
Value 11x
Value 12a
Value 12b
:
Value 12x
Value 13
Value 14:
Wheel based speed
Clutch switch
Brake switch
Cruise control active
PTO
Accelerator pedal position
Total fuel used
Fuel level
Energie speed
Number of axles (na)
Number of wheels on axle 1
Number of wheels on axle 2
:
Number of wheels on axle na
Axle weight on axle 1
Axle weight on axle 2
:
Axle weight on axle na
Total engine hours
Vehicle identification number
km/h
%
l
%
rpm
kg
kg
kg
kg
h
-
minLen maxLen*) Type
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
2.0
3.2
1.0
1.0
1.0
2.0
3.1
10.1
3.1
4.3
2.0
2.0
2.0
2.0
2.0
5.1
5.1
5.1
5.1
9.2
200.0
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
hex
Seite 10 von 12
Value 15:
Value 16:
Value 17:
Value 18:
Value 19:
Value 20:
Value 21:
Value 22:
Value 23:
Value 24:
Value 25:
Value 26:
Value 27:
Value 28:
Value 29:
Value 30:
Value 31:
Value 32:
Value 33:
Requests supported
Diagnostics supported
SW-version supported
High resolution total vhcl. distance
Service distance
Drive recognize
Driver 1 working state
Driver 2 working state
Overspeed
Driver 1 card
Driver 1 time rel. stats
Driver 2 card
Driver 2 time rel. stats
Direction indicator
Tachograph performance
Handling information
System event
Tachograph vehicle speed
Engine coolant temperature
m
km
km/h
°C
1.0
1.0
8.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
1.0
8.0
11.0
7.0
1.0
1.0
1.0
1.0
1.0
2.0
1.0
2.0
1.0
1.0
1.0
1.0
3.2
3.0
dez
dez
hex
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
dez
* x = pre-comma value and y = after-comma value) x.y in which
Validity of the measured values
1st case (Data packet not available):
*(2Ah)
Data field Value x contains the characters *(2Ah), if no necessary data packet was
received since beginning.
2nd case (Measured value not available):
n(6Eh)
Data field Value x contains the characters n(6Eh), if the measured value in the
necessary data packet was received with the flag „not available“ (Byte Indicator = FFh).
3rd case (Measured value not valid):
o(6Fh)
Data field Value x contains the characters o(6Fh), if the measured value in the
necessary data packet carries the Byte Indicator FBh, FCh, FDh, FEh or the measured
value is outside the valid range of values.
Seite 11 von 12
Beispiel zu Datensatz Vehicle Weight (Messwerte 10, 11, 12)
B1a B1b B2B3
High FMS-Standard data packets (Value 10, 11, 12)
Fh
Fh
Fh
1h
1h
0h
0h
1h
2h
0h
1h
0h
0h
1h
2h
2h
2h
2h
0h
1h
2h
1h
2h
0h
0h
5h
4h
3h
2h
1h
:n:
:n:
:n:
:2:*:*:*:0.0:
:2:*:*:*:32127.5:
:2:*:*:o:32127.5:
:2:*:*:0.0:32127.5:
:2:*:*:0.0:o:
:3:*:*:*:0.0:o:32127.5:
:3:*:*:*:n:o:32127.5:
:3:*:*:*:n:16402.5:32127.5:
:3:1:*:*:8192.0:16402.5:32127.5:
:3:2:*:*:8193.0:16402.5:32127.5:
:3:2:*:*:8193.0:12288.0:32127.5:
:3:2:*:1:8193.0:12288.0:16384.5:
:3:2:*:2:8193.0:12288.0:o:
:3:2:*:3:8193.0:12288.0:n:
:3:2:*:4:8193.0:12288.0:16386.0:
:3:2:*:4:8192.0:12288.0:16386.0:
:3:2:1:4:8192.0:8193.0:16386.0:
:3:2:1:4:8192.0:8193.0:12288.0:
:3:2:2:4:8192.0:12290.0:12288.0:
:3:2:2:4:8192.0:12290.0:16384.5:
:3:2:2:4:8320.0:12290.0:16384.5:
:3:2:2:4:8319.0:12290.0:16384.5:
:6:2:2:4:*:*:15:8319.0:12290.0:16384.5:*:*:0.0:
:6:2:2:4:*:1:15:8319.0:12290.0:16384.5:*:n:0.0:
:6:2:2:4:*:1:15:8319.0:12290.0:16384.5:o:n:0.0:
:6:2:2:4:*:1:15:8319.0:12290.0:12288.0:o:n:0.0:
:6:2:2:4:*:1:15:8319.0:16384.0:12288.0:o:n:0.0:
B1a
B1b
B2B3
Fh
Fh
Fh
Fh
Fh
Fh
Fh
Fh
Fh
Fh
Fh
0h
1h
Fh
0h
1h
2h
3h
0h
0h
0h
1h
Fh
0h
1h
Eh
0h
Fh
0h
0h
FFFFh
0101h
FFFFh
0000h
FAFFh
FB00h
0000h
FB00h
FAFFh
FFFFh
8025h
4000h
4002h
6000h
8001h
FB00h
FFFFh
8004h
4000h
4002h
6000h
6004h
8001h
4100h
40FEh
0000h
FFFFh
FFFEh
6000h
8000h
Axle location
Tire location
Axle weight
DataByte 1, Bit 5-8
DataByte 1, Bit 1-4
DataByte 2 and 3
Seite 12 von 12

FMS-Standard - LogiCom GmbH

Transcription

Documents pareils

KATES CO

Bus-FMS-Standard