EMIS Interface Description - Measurement Solutions
EMIS Interface Description - Measurement Solutions
EMIS Interface Description - Measurement Solutions
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Sening®<br />
Innovative Tank Truck Systems<br />
3 Implementation<br />
Specification<br />
Euro <strong>Interface</strong> <strong>EMIS</strong><br />
<strong>Interface</strong> <strong>Description</strong><br />
Communication between <strong>EMIS</strong> and the OBC is based on telegrams exchanges. Each telegram<br />
consists of an OpCode, a node and possibly with one or several sub-nodes and from variables<br />
with the related variable values.<br />
� The OBC requests variables through a REQUEST telegram.<br />
� The answer comes from the <strong>EMIS</strong> as one or several REPORT telegrams.<br />
� The OBC can set variables using a SET telegram.<br />
3.1 General Remarks<br />
Figure 3: Data Flow<br />
• Following being switched on, <strong>EMIS</strong> scans all the CAN addresses to localize connected<br />
participants. This takes approx. 20 seconds. During this time <strong>EMIS</strong> in the regular operating<br />
mode can still not be "talked to". The OBC should then send a "Ping" (SET,ADMIN,PRPTOCOL,<br />
Ping=“e.g. test“) as the first telegram to the <strong>EMIS</strong> to check on commuication.<br />
• The variables for the <strong>EMIS</strong> description are organized under the ADMIN node. It is also<br />
established here as to which other nodes were implemented.<br />
(see ADMIN,PROTOCOL,OPTION).<br />
MNF19002EUS / DOK-411E Rev. 2.00 / MB / jp / Juli 2008 9<br />
1<br />
2<br />
3<br />
4<br />
5<br />
6<br />
7<br />
8<br />
9<br />
A<br />
Implementation
Change language