Chapter 2 C Language Reference
AutoCode Reference 2-8 ni.com
the comments there and adjust the limits accordingly, then recompile and
relink the sa_utils.c file.
ERROR OPENING THE INPUT FILE
ERROR OPENING THE OUTPUT FILE
A problem was encountered opening the input or output file. Possible
causes include a file protection violation.
UNKNOWN ERROR
A value of the ERROR variable occurred that was not one of those defined
for the switch-case statement. Check any error indications you may have
introduced.
ERROR: Conditions Detected in the Generated CodeThe RT_INTEGER variable ERROR_FLAG is passed if an error occurs in
running the generated code. The following conditions are trapped, not all
of which indicate that an error has occurred.
The following messages might be generated during the execution of the
generated code:
Stop Block encountered in task
n
This is not necessarily an error. This refers to a SystemBuild Stop
Simulation Block encountered in the execution of the generated code.
Math Error encountered in task
n
Check your model for overflows, division by zero, and similar problems.
User code error encountered in task
n
Refer to Chapter 15, UserCode Blocks, of the SystemBuild User Guide
ort he source listing of the USR01 routine for meanings of UCB errors.
Youcan extend the scope of these messages, so it might be one of yours.
Unknown error encountered in task
n
A possible cause is an incorrect user-written error condition in the
generated code.
Time overflow occurred in task
n
This indicates a subsystem (or task) overflow. Refer to the Scheduler
Errors section of Chapter 4, Managing and Scheduling Applications,
of the AutoCode User Guide for timing overflow conditions.