Run-Time Errors; Using Amx Bug - AMX AXCESS CONTROL SYSTEM PROGRAM Instruction Manual

Run-Time Errors

In many cases, a program is compiled and sent to the Central Controller error-free, but the system
does not act in the way it should. If the program code is correct, you should check for run-time
errors. These errors occur in the Central Controller, usually when it could not perform a particular
operation in the program.

Using AMX BUG

Normally, there is no way to tell if a run-time error occurred, or what type of run-time error
occurred. However, the Central Controller can be placed in a special debugging mode. In this mode,
the Central Controller sends run-time error messages through its RS-232 port as they occur. Using
the terminal emulator in Axcess, you can see what, if any, run-time errors are occurring.
To turn this mode on, type the following command in the terminal emulator while on-line with the
Central Controller:
AMX BUG
The following is a list of some common run-time error messages you may see while the debugging
mode is on. An ellipsis after the message indicates that there is a group of messages that have the
same beginning. For instance, BAD TO... refers to the set of errors BAD TO VARIABLE and BAD
TO CHANNEL.
Run-Time Errors
Bad assign 2dim...
Bad assign Call...
Bad element assign...
Bad Off... Bad On... Bad To... These errors indicate that the device-channel or variable that is being refer-
Bad re-assign Call...
Bad run token
Bad Set_Length...
Bad While
Axcess Programming Language
These errors occur if an attempt is made to assign a two-dimensional array to a
different type (such as a variable or one-dimensional array), and vice versa.
These errors occur if the Central Controller cannot assign a parameter in a
CALL statement to the parameter in the corresponding DEFINE_CALL state-
ment.
These errors occur if an assignment is attempted past the end of an array, or to
the Ø location of an array (for example, ARRAY[Ø]).
enced by a OFF, ON, or TO keyword is out of range.
These errors occur when the Central Controller attempts to re-assign the
parameter variables in a DEFINE_CALL to the parameters in the correspond-
ing CALL statement, and the assignment cannot be made.
This error occurs when the Central Controller does not understand a piece of
data in the program it is executing.
These errors occur if the SET_LENGTH_STRING keyword tries to set the
length value of an array to a value greater than the array's storage capacity.
This error occurs whenever a WHILE loop terminates due to the half-second
time-out imposed on WHILE loops.
Debugging
105