Rockwell Automation 57C650 AutoMax Programming Executive Version 3.8 - Manual (Page 292)

SĆ2 AutoMax Programming Executive Version 3.x
another rack. Error messages displayed while loading a UDC task
may reference PMI tunables, task tick rates, or a PMI OS." These
error messages indicate a problem in UDC tasks or the UDC
operating system.
S.1.3 Errors that Occur When Loading Tasks
Errors that can occur when loading tasks are usually specific
enough to pinpoint the problem. If a particular task is specified in
the error message, contact your software supplier. Error messages
displayed while loading a parameter object file may reference PMI
tunables, task tick rates, or a PMI OS." These error messages
indicate a problem in UDC tasks or the UDC parameter object file.
Other errors that may occur:
Task not found"
Ć attempting to load a task that does not exist in the specified
directory on the personal computer
Task not installed"
Ć either a task or the rack configuration file has not been
loaded into the rack successfully
Critical task cannot be stopped by itself"
Ć only a STOP ALL command can stop this task, which you are
trying to stop individually
Task already exists in chassis" and Given UDC drive
already contains a task"
Ć warns you that if you continue with the loading operation,
you will overĆwrite an existing task with the same name
Invalid data type in symbol table" or Invalid control type in
symbol table"
Ć there is an error in the configuration file in this rack; it is also
possible that the wrong configuration file has been loaded or
a wrong task has been loaded
Too many tunables"
Ć too many tunable variables defined in a UDC task
No symbol table present" or Array name not found"
Ć error in the configuration file in this rack
S.1.4 Errors that Can Occur in More than One Type of
Loading
If an error message indicates insufficient memory on a Processor,
the configuration and/or tasks are too large for the amount of
memory available on a Processor. Note that this error may occur
even if there is technically enough memory (in kilobytes) on the
Processor. If tasks have been deleted from the rack or loaded to the
rack numerous times individually, the memory available may be
fragmented into many small areas, none of which are large enough
to store the task or configuration file.
If you see the error No common storage allocated," there has
been an error in the sequence of loading. In this case, you must
load (or reĆload) the rack configuration to the Processor module. It is
very important to load the files in this order if you are loading
individual files. Alternately, you can choose the LOAD ALL command