Bosch LTC 8850 Series, Instruction Manual

Page: 53 / 72

EN
| 53
Bosch Security Systems | 02 April 2004
LTC 8850 | Instruction Manual | Allegiant Server
A script can be invoked with parameters by typing the
parameters (separated by spaces) on the command line
following the name of a script. These parameters are
available to the script as argument macros. The various
macros are listed below. Argument macros can also be
used to access the value of a variable that was defined
in a .FOR or .FOREACH command. An argument
macro may only be used as a parameter to a CCL
command or script.
Numbers that appear in arguments in a script can be
interpreted as either decimal or hex. The default is
decimal. To specify a hex number, prefix it with
0x . To
guarantee that a number is interpreted as decimal
(even if the default radix has been changed to
something else), prefix it with
0m .
The following synonyms are provided for backward
compatibility with old
boot screen scripts. These
commands should not be used in new command
scripts.
• BOOT - means BEGIN @BOOT
• START-STAR - interpreted as BREAK
followed by BEGIN
@STAR"
• END-STAR - represents BREAK
If a script has the same name as a native (built-in)
CCL command, the Allegiant will execute the script
(instead of the built-in command) whenever the
command is invoked. To force the Allegiant to execute
a native command without first checking to see if there
is a script that overrides it, precede the name of the
CCL command with
CCL: followed by a space.
The Allegiant normally executes the CCL commands
in a script one at a time. It will not execute the next
command until the previous one has finished. Also,
whichever
task invoked the script (e.g., the console
port, the time-event system, or the alarm system) will
not be able to do anything else until the script has
completely finished. To indicate that a command
should execute in its own task, precede the name of
the command with
SPAWN: followed by a space. The
script will immediately proceed to the next command
while the
Spawned command executes in a separate
task.
To view scripts that are in the Allegiant, you can
upload the Command Script Table and view the table
in the Allegiant Server Application. You can also enter
the CCL command
BOOTSCREEN directly on the
Console port. This will list the table on the Console
port and display a line number for each line. To debug
a script, enter the CCL command
SCRIPT-DEBUG 1
on the Console. Then enter the name of the script that
you want to debug. The Allegiant will execute the
script as normal, but it will also display each command
that is executed on the Console port. Enter
SCRIPT-DEBUG 0 to turn off debugging.
%n nth element on arg stack
%0 all elements on arg stack
%0n all elements, starting at nth
%@ all elements, local args only
%@n all local args, starting at nth
'n nth element on stack, stringized
`n nth element on stack, stringized
'0 all elements on stack in single string
'0n all from nth in single string
`0 all elements on stack, individually stringized
`0n all from nth, individually stringized
'@ all local args, single string
'@n all local args from nth, single string
`@ all local args, individual strings
`@n all local args from nth, individual strings
%var value of variable "var"
'var value of variable "var" in quotes
`var value of variable "var" in quotes
#text remove "#" and do not expand macros in "text"