4.7. SETTING
SPEED LIMITS
Note: It is assumed that you already have ACT communicating with the
unit, see the
Operation
chapter.
1. Create or edit an existing script file as stayed on the
Using Scripts
section of the
Configuration chapter with all of the unit’s configuration
except any regions’ definition messages. However, include any regions’
signals-related information, like for example any event that uses
Rxx
signals. This means leave any
>
SGR....
<
command out of the script.
Save the script on a .tmf file and have it ready to be used. This is
out main configuration script.
2. Create the region(s) on ACT making sure the region(s) index(es) cor-
responds to the
Rxx
signals defined on the main configuration script.
Follow the instructions on the ACT’s Manual or the
Operation
chap-
ter for managing regions.
3. Once you are done creating/editing regions on ACT the next step
is passing the configuration to an
Antares SB
TM
. This is different
than passing an script to the unit as described on the
Using Scripts
section. Here we are not going to pass a script to a unit, we are
going to pass the configuration shown on the ACT’s interface which
contains our region(s) definition. This is a partial definition and it is
not going to be of any use to the unit we are using in this step, this is
a temporal configuration that has to be passed to the unit so the ACT
can then read it and generate an script file (next step). To pass this
configuration go to the
Antares
menu and select
Write configuration to
antares
, DO NOT USE THE
Write configuration to antares from file
ON THIS STEP.
4. Now the unit has the regions’ configuration done with the ACT’s
interface. No special knowledge on the
GR
message’s rules had to
be followed. But the unit only has the region’s information and it
is missing from the main configuration script configuration.
This
step reads the unit’s configuration so ACT generates an script with
the
GR
messages. For this we follow the instructions on the
Using
Scripts
section and select
Read configuration from antares to file
from
the
Antares
menu and save this temporal script.
5. Now we have two scripts, the main configuration script and the tem-
poral regions’ script. The next thing is extracting the
GR
messages’
from the temporal region an place them on the main configuration
script. Simply copy all of the
GR
messages from the temporal script
and paste them into the main one. Only copy the
GR
messages. Save
the main script and that is it, we have the main configuration script
that includes regions’ definitions.
6. Pass the main configuration script to the unit as stayed on the
Using
Scripts
section.
4.7
Setting
Speed Limits
Speed limits are created with the
GS
TAIP message. When creating an speed
limit we are telling the unit to activate the corresponding speed signal
Sxx
whenever the vehicle’s speed is greater than the defined limit and to get
88
Summary of Contents for Antares SB
Page 1: ......
Page 2: ...Antares SB TM GSM User s Manual FW 5 21 Digital Communications Technologies April 15 2008...
Page 37: ...2 1 POWER SUPPLY 35...
Page 38: ...2 1 POWER SUPPLY 36...
Page 42: ...2 5 CONNECTION DIAGRAMS 40...
Page 141: ...6 Unit s TAIP reference...
Page 191: ...6 32 XADM DIAGNOSTIC MESSAGE 189...
Page 228: ......
Page 229: ......