AMX NETLINX STUDIO V2.4 Instruction Manual page 184

Table of Contents

Advertisement

Setting Program Preferences
When building with source, only the files needed for the compilation process are
compressed. Though the APW may contain many files, if the source file only uses
one axi file, then only 2 files will be compressed.
172
• Assigning a two-dimensional array to a one-dimensional array, or vice versa.
• Assigning the result of a function that returns an array type to a non-array variable or
to a two-dimensional array variable (for example, X = ITOA(12), where X is a non-
array variable or two-dimensional array variable).
• Assigning the result of a function that returns a non-array type to a one- or two-
dimensional array variable (for example, X = ATOI('AMX'), where X is a one- or two-
dimensional array variable).
This message is a warning and not an error, because X = ITOA(12) works correctly when
X is a simple variable, since the result is a single value between Ø and 65,535.
Variable not used - This warning occurs at the end of compilation for each variable
that was declared but never used.
Define_Call not used - This warning occurs at the end of program compilation for
each DEFINE_CALL subroutine that was declared but never used.
Too many nested levels - This warning appears if there is a large amount of nesting
in the program. This can happen with a long chain of IF...ELSE IF statements. The
solution is to use the SELECT...ACTIVE set of statements.
Long_While in While - This warning occurs if the compiler finds a LONG_WHILE
or MEDIUM_WHILE inside a block of code following a WHILE keyword. This
warning exists because the WHILE command has a 1/2 second timeout period, and
the LONG_WHILE and MEDIUM_WHILE keywords do not. This could create a
hard-to-find logic error. The solution is to change the WHILE to a LONG_WHILE
to fix this problem.
Separate Define Call list - Check to store all DEFINE_CALL subroutines in a separate
section of the Master Controller memory than the DEFINE_PROGRAM section. This
effectively allows the code size of a program to reach 128K (64K for the
DEFINE_CALLS and 64K for the DEFINE_PROGRAM section).
Source Options - Click these checkboxes to enable the following build (compile)
options:
Build with Source - Check to compile the source code with the executable code so that
you may later retrieve the source code from the device you send the compiled code to. If
Build with Source is disabled, only the executable code is sent when the file is transferred
to the master.
Build With Password Protection - Select this option to apply a password to the Source
file. Once applied, you cannot retrieve the source code from the Master Controller unless
you provide the correct password. Select the Change button to edit the password (via the
Change Password dialog). A password must be at least 6 characters in length (maximum
of 20 characters).
Directories - Click to open the directories menu, where you select the directories to point
the compiler to, by file type. Once a directory type is selected, the directory list is
NetLinx Studio (v2.4 or higher)

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents