EMIS Interface Description - Measurement Solutions

Sening®
Innovative Tank Truck Systems
Telegrams are represented in accordance with the following rules:
•
•
•
•
•
Specification
Euro Interface EMIS
Interface Description
All characters are represented by printable ASCII alphanumeric characters, so that numbers, for
example, are not transmitted in binary form but rather as a character string. This also applies to
the telegram checksums (BCC).
Example: The value 1A hex is represented by the character string "1A" (31 hex 41 hex)
There is at present no limit on the length of telegrams (although a max. of 500 characters
between and is recommended).
Several REPORT telegrams need to be transmitted when transferring large data quantities (see
event requests Chapter 0 / Page 19).
Capitalization or lowercase is of no relevance in interpreting OpCode, nodes, sub-nodes and
variables.
However, a distinction is made between capitalization and lowercase for variable values.
3.3.1 OpCode
All telegrams begin with a followed by an operation code (OpCode). This is an identifier as
to how the telegram data is to be interpreted.
Following OpCodes are defined:
� REQUEST Recalling one or several variables
� REPORT Answer from the EMIS to a REQUEST telegram
� SET Setting a variable
� Only REQUEST or SET telegrams may be transmitted from the OBC.
� The answer to a REQUEST telegramm is a REPORT telegram.
� Apart from a few exceptions, a feedback in the SET telegrams is only done through an ACK
answer.
� The ongoing variable value can then be requested, if needed, with a REQUEST telegram.
� On setting a number of variables a REPORT telegram will also be transmitted. Its contents
can be examined for assessment purposes.
� Setting a variable can impact on other variables in the EMIS or on the response of the
connected devices.
MNF19002EUS / DOK-411E Rev. 2.00 / MB / jp / Juli 2008 11
1
2
3
4
5
6
7
8
9
A
Implementation