Building and Debugging Source Code
108
NetLinx Studio - Instruction Manual
Compiler Errors (Cont.)
PUSH/RELEASE not allowed
within PUSH/RELEASE
A PUSH or RELEASE statement was found within a block of code headed by a
PUSH or RELEASE statement.
PUSH/RELEASE not allowed
within WAIT
PUSH_CHANNEL not allowed
within WAIT
RELEASE_CHANNEL not
allowed within WAIT
PUSH_DEVICE not allowed
within WAIT
RELEASE_DEVICE not allowed
within WAIT
These keywords are not allowed in a section of code which will be executed due to a
WAIT keyword.
String constant expected
A string is required for the particular operation.
This error occurs if a string literal enclosed in single quotes does not follow 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 subroutine.
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 subroutine.
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 NUMBER].
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
Page 40: ...Working with Projects 28 NetLinx Studio Instruction Manual...
Page 148: ...Communication Settings 136 NetLinx Studio Instruction Manual...
Page 160: ...Working with Online Devices 148 NetLinx Studio Instruction Manual...
Page 178: ...File Transfer Operations 166 NetLinx Studio Instruction Manual...
Page 208: ...Tools Menu Options 196 NetLinx Studio Instruction Manual...
Page 229: ...Setting Program Preferences 217 NetLinx Studio Instruction Manual...