DCT Antares SB, User Manual

Page: 116 / 238

5.3. ADDING SMS INTERACTION
#signal definition
>STD80300<
#Event triggered by T&D signal
>SED37NV4;TD8+<
#Input report event
>SED05NV5;IP3+<
#User text message for event 05
>SXATM05Input 3 has been activated!<
#end
5.3 Adding SMS interaction
Once a Phone-Number-type destination has been created it is possible to
interact with the unit via SMS messages generated from that phone number,
as long as the
Destination configuration allows TAIP console access to the
configured DP.
This means taking care of the Access parameter on the Destination Point
definition. Continuing with our previous example. We defined the Phone-
Number-type DP 10 as:
>
SXADP1010912345678
<
Refer to the
XADP
message for more information. The underlined value
indicates the access parameter for this DP, indicating that the Phone Num-
ber 912345678 has TAIP console access via SMS messages.
Now that we are clear on the access level of the Phone-Number-type DP,
interacting with the unit is a matter of sending TAIP commands through
SMS messages and waiting for response as incoming SMS texts.
5.3.1 Query the unit with a SMS
To ask for the current position-velocity solution of the unit, sent a from the
Phone Number 912345678 an SMS with the query:
>
QPV
<
The unit will respond with an SMS containing the text:
>
R0000000000112012
<
5.3.2 Set an output with a SMS
Driving outputs is achieved by using the Set form of the
SS
message. To
set output 2 high via a SMS message, send to the unit from the authorized
114