DCT Antares SB, Руководство пользователя

Страница: 114 / 238

5.2. ADDING SMS REPORTING
Now Destination Address
5
holds Destination Points
00
and
10
. We can
point any event to
DA 5
making any report generated by the event to be
routed to our AVL server an to the Telephone Number 912345678 at the
same time.
5.2.3 Change the Input report event definition
Our previously input report event was defined on event
05
. We are going
to use the same definition but as you will notice we are going to change on
the event’s routing options the selected
DA
from
4
to
5
:
>
SED05NV5;IP3+
<
Now any time input 3 goes high (
IP3+
) an event report is going to be
generated to both the AVL server and the Phone Number 912345678 .
5.2.4 Create a SMS custom message
The only thing left to do is create a user-defined text to be sent to the
Phone-Number-type destination whenever event
03
occurs. For this we use
the
XATM
message which allows to create up to 50 user-messages, one for
each event. Refer to the
XATM
message on the TAIP reference for more in-
formation. Let’s use the text
Input 3 has been activated!
:
>
SXATM05Input 3 has been activated!
<
The underlined
05
indicates that the message we are defining is for event
05
.
5.2.5 Check the reported message
The following text message should be arriving to the Phone Number
912345678
any time input 3 goes high:
Antares:EXAMPLE
Event:05
Input 3 has been activated!
If no user-message is defined with the
XATM
message the following message
is sent:
Antares:EXAMPLE
Event:05
-----
If on the Destination Point we change the underlined “
1
” for a “
0
” we
receive an
EV
message on the Phone Number instead of the user-defined
text, something like:
>REV050000000000000000001;ID=EXAMPLE<
At the same time input 3 goes high an
EV
message is also sent to the remote
AVL server. Notice that we did not change the definition of the periodic
report event (event
37
), so the periodic report is still being sent to the AVL
server only.
112