User's Manual

This parameter is only relevant if eESPA acts as an input program (so receives external data
from the espa infrastructure.
If the specified data identifier is not present in the available datastream record, than the field
eESPA_Msg_default_str must be used to define a default message.
If the eESPA module acts as input program:
The received espa record must be translated to a valid message request, and sent to the
eKERNEL application.
This field specifies the Data Identifier (normally 2) of the espa record that specifies the
message.
In this authorized, data identifier 2 (display message) is defined as eESPA_DataId_Msg_str.
Table 16: Espa record: SOH1STX1US12345RS2USThe
messageRS3US9RS4US3RS6US3ETXBCC
(SOH) Start of header
STX Start of text
ETX End of text
US Unit separator
RS Record separator
BCC Checksum
The incoming alarm/message, must be translated to a valid message request and sent to the
eKERNEL:
Figure 184: Example: eESPA module acts as input program
If this eESPA module acts as an output program:
in the current release, the data identifiers for the espa records are fixed. Therefore, when a
message request is sent by the eKERNEL to the eESPA module, the data in the <message_xx>
tag is put in data identifier 2 (display message).
In the following authorized, the data in the <message_xx> tag from the message request, must
be translated to data identifier 2 (display message) in the espa record.
Table: eESPA
230 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]