Compile Operations
112
NetLinx Studio (v2.4 or higher)
String constant expected
A string is required for the particular operation. This error
occurs if a string literal enclosed in single quotes does not fol-
low the PROGRAM_NAME keyword.
String constant never ends,
EOF encountered
A string literal is started but never ends. Add a closing single
quotation mark (') to the end of the string.
String literal expected
A string is required for the particular operation. This error
would occur if a string literal enclosed in single quotes does
not follow the #WARN keyword.
Subroutine may not call
itself
A subroutine cannot call itself. It can, however, call a different
subroutine.
Syntax error
A syntax error is found in an expression. In most cases, this
error means that a character is out of place or something is
misspelled.
SYSTEM_CALL name not
same as PROGRAM_NAME
in <file>
This error occurs when a library file is compiled and the name
of the subroutine in the library file does not match the
PROGRAM_NAME string on the first line of the file.
This variable type not allowed
This error occurs when an attempt is made to use an array
variable with DEFINE_LATCHING, DEFINE_TOGGLING, or
DEFINE_MUTUALLY_EXCLUSIVE.
To not allowed within
DEFINE_START
To not allowed within MAINLINE
To not allowed within RELEASE
To not allowed within WAIT
These errors occur if the TO keyword is found in an erroneous
location. The TO keyword can only be associated directly with
a PUSH statement.
Too few parameters in CALL
There are not enough parameters being passed to the sub-
routine.
Too many Include files
A program may only contain up to 20 Include files.
Too many parameters in
CALL
There are too many parameters being passed to the subrou-
tine.
Type mismatch in function
CALL
A function was called with a parameter of the wrong type. For
instance, attempting to use ITOA with an array as a parameter
will result in an error.
Undefined identifier
An attempt was made to reference an identifier that has not
been defined previously in the program.
Unmatched #END_IF
An #END_IF keyword was found, but no #IF_DEFINED or
#IF_NOT_DEFINED was previously compiled.
Unrecognized character in
input file
An invalid character was found during compilation.
Use SYSTEM_CALL
[INSTANCE] 'NAME'
This error occurs if a SYSTEM_CALL statement is written
incorrectly as SYSTEM_CALL 'NAME' [INSTANCE NUM-
BER].
Variable assignment not
allowed here
Variables may not be assigned a value when they are defined
in the DEFINE_VARIABLE section.
WAIT not found
A statement references a WAIT by a name that does not exist.
For example, CANCEL_WAIT 'CASS' will produce this error if
there is no WAIT named CASS.
Summary of Contents for NETLINX STUDIO V2.4
Page 1: ...instruction manual Software NetLinx Studio v2 4 or higher ...
Page 16: ...NetLinx Studio v2 4 or higher 4 NetLinx Studio v2 4 or higher ...
Page 32: ...The NetLinx Studio v2 4 Work Area 20 NetLinx Studio v2 4 or higher ...
Page 44: ...Working With Workspace Files 32 NetLinx Studio v2 4 or higher ...
Page 88: ...Working With Systems and System Files 76 NetLinx Studio v2 4 or higher ...
Page 118: ...Programming 106 NetLinx Studio v2 4 or higher ...
Page 152: ...Working With Online Devices 140 NetLinx Studio v2 4 or higher ...