Rockwell Automation SA500 Drive Configuration and Programming - Manual (Page 99)

On-Line Operation 5-3
• the PMI Regulator’s operating system has been loaded from the UDC module to the
PMI Regulator (which happens automatically when the PMI Regulator is connected
to the UDC module).
Stopping UDC Tasks
UDC application tasks (both tasks A and B together) must run at least every 10
milliseconds. Once the SCAN_LOOP statement is executed, the UDC module will
cause a Stop All in the rack if the task does not complete its scan within 10
milliseconds.
Deleting UDC Tasks
When a UDC application task is deleted, any local variables which were forced are
removed from the force table. The task’s error log is also cleared.
5.4 UDC Information Log and Error Log
The information log and error log for a UDC task can be displayed by selecting “I” for
Info/Log from the ON LINE menu. Refer to the AutoMax Programming Executive
instruction manual for the procedure.
The information log for a slot containing a UDC module will display the UDC operating
system’s part number, the utilization of the CPU resources in the UDC module, and
various memory and PMI rack statistics. Select “U” from the Info/Log menu to display
the information log. Note that the UDC module’s CPU utilization should not exceed
75%.
Like AutoMax tasks, UDC tasks can access the error log by using the BASIC
statement CLR_ERRLOG@ and BASIC function TST_ERRLOG@. The error log will
display the first, second, and last errors and will maintain them until power is cycled.