EMIS Interface Description - Measurement Solutions

Specification
Euro Interface EMIS
Interface Description
Example from event table:
Event / sensor TYPE VALUE1 VALUE2
API coupling
(Sensor status)
AST CoNo e.g. 3
TDL 42,S,V1,2,(1) (2) >> V2[..]
“L“ = locked
“U“ = unlocked
The API coupling for Compartment 3 was closed at 17:40 on 11/10/2005
Event report line from REQUEST,QAS,EVENT-query:
REPORT,QAS,EVENT,TYPE=“AST“;VALUE1=“3“;VALUE2=“L“;
DATE=“11.10.2005“;TIME=“17:40“
Event report line from REQUEST,TDL,L_FILE-query:
REPORT,TDL,L_FILE=42,20051011174000,3,2,1
Sening®
Economic Tank Truck Systems
A description of how the individual event table information is converted is given in Chapter 4.2.1.3 /
Page 33 Page (Information on converting DOK-411 in TDL data sets).
Not all setup information or events occuring in the system are defined in DIN 26501. For those
missing use is made of the 8xx Sening® identifier to establish specific telegrams.
TDL,L_FILE – Identifier 8xx
Thanks to DIN 26051-2 (TDL-2) non-used identifiers and/or manufacturer-specific data sets can
be used. To allow this identifier to distinguish between differing data set types, the following holds
good for Sening® :
Field index 0 Identifier 8xx (DIN 26051-2)
Field index 1 Time stamp (DIN 26051-1)
Field index 2 CAN node ID of the QAS (DIN 26051-2)
Field index 3 Manufacturer abbreviated identifier „FAS“
Field index 4 .. n: Data
Depending on type, the data (Field index 4 to Field index n) can be differentiated into content,
number and format.
74 Rev. 2.00 / MB / jp / Juli 2008 MNF19002EUS / DOK-411E