DCT Antares SB, User Manual

Page: 113 / 238

5.2. ADDING SMS REPORTING
# server destination
>SDA4;P00<
#Time-only Time And Distance
#signal definition
>STD80300<
#Event triggered by T&D signal
>SED37NV4;TD8+<
#Input report event
>SED05NV4;IP3+<
#end
You can copy and paste this script to a new empty text file and have it save
with a .tmf extension so ACT software can pass it to a unit. See the
Using
Scripts section of the Operation chapter for information on creating, editing
and downloading scripts.
5.2 Adding SMS reporting
Based on the Getting Started example, SMS reporting is added.
On this example we are going to make the unit report the previously defined
Input report (
IP3
) to a Phone Number as well as to the remote AVL server
with a custom text message.
5.2.1 Create the SMS Destination Point
The first step is configuring the destination Phone Number on one of the
unit’s Phone-Number-Type
Destination Point (
DPs 10
to
14
). For no par-
ticular reason we choose
DP 10
. The number we are going to configure on
DP
10
is 912345678 . See an special note about some Phone Numbers’ variations
on the Over The Air section of the Operation chapter.
>
SXADP1010912345678
<
Refer to the
XADP
message for more information on the command.
Notice the underlined “
1
”: With this, we are indicating that events’ mes-
sages sent to DP 10 are always going to be user-defined texts (not TAIP
EV
messages). The “
0
” next to the underlined “
1
” is not relevant for this
example but it is going to be important for the next one as we would like
the Phone Number to have TAIP-console and voice access.
5.2.2 Create a new Destination Address
For now we only have
DA 4
that associates only
DP 00
. We need to create
another
DA
that includes our AVL server (
DP 00
) and the recently created
Phone Number (
DP 10
). For no particular reason we choose
DA 5
to do the
job:
>
SDA5;P00,P10
<
111