User's Manual

Than the data identifiers must be separated by a ^ sign. If for instance the beep code (data
identifier 3) in combination with the priority (data identifier 6) must result in the alarm
description, this value must be 3^6.
If the display message (data identifier 2) is a part of the alarm description, you can specify the
first x characters of the message as the alarm description. For authorized the value 2:3, results
in an alarm description equal to the first 3 characters of the display message (data identifier
2). If the message is, for authorized, NURSE CALL ROOM 02, the alarm description is NUR,
so the alarm NUR must be configured in the eKERNEL_ALARM table.
If this eESPA module acts as an input program:
In this authorized, data identifier 3 (beep coding) is defined as
eESPA_DataId_Ala_descr_str.
Table 17: 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 186: 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
<beep_code_xx> tag is put in data identifier 3 (beep coding).
In the following authorized, the data in the <beep_code_xx> tag from the message request,
must be translated to data identifier 3 (beep coding) in the espa record.
Table: eESPA
232 DECT Messenger Installation and Commissioning — Book 2 March 2012
Comments? [e-mail]