beautypg.com

2 info/log task information display – Rockwell Automation 47C626 AutoMax Programming Executive V4.2 User Manual

Page 170

background image

13Ć4

13.2

Info/Log Task Information Display

If you select a task using the Enter or before selecting

Info/Log, AutoMax will display the task status and the error log, if any,

for the AutoMax or UDC task. A sample display is shown in

figure 13.4.

ON LINE direct

C: \LIB\SYS\RACK

Info/Log

SLOT

NAME

TYPE

PRI

STATUS

5

APP1B

Blk

B

Stop

NUMBER

STATEMENT

DATE

TIME

ERROR SPECIFIC

EscăExit

F1ăHelp

ERROR LOG

SOURCE DATE

08Ć31Ć1993 02:08:18p

49ă = ă31 HEX

0

No date

00:00

0 =

0 HEX

774 = 306 HEX

0

No date

00:00

0 =

0 HEX

Precision lost in integer control variable to real conversion

775 = 307 HEX

0

No date

00:00

0 =

0 HEX

Real to integer overflow in FOR statement TO value

Error 31:

Slot=0

Bit=0 (Reg based on type of card in slot)

Net: drop=0,ą reg=0

Remote I/O:drop=0,

slot=0,

reg=0

Modbus: reg=n/a AutoMate: reg=n/a AĆB: file= n/a, reg=n/a Local I/O: reg=0

Figure 13.4 Ć Info/Log Task Information Display

The status line for the task displays the slot of the Processor or UDC

module on which the task is loaded in the SLOT field. The task name

is shown in the NAME field. The task type (.BAS, .BLK, or .PC) is

shown in the TYPE field. The priority of AutoMax Processor tasks,

assigned when the task is added to the rack, is shown in the PRI

field. For UDC tasks, the drive (A or B) the task is assigned to will be

shown. The status of the task, either Running, Stopped or in Error, is

shown in the STATUS field. The date that the source file was last

edited is shown in the SOURCE DATE field. In the sample display, the

.PC task FRCS1LAD loaded on the Processor in slot 1 is designated

as priority 7 and is currently running.
If any errors occurred while the task was running, the STATUS field

will display Error. An error log is generated and shown on the screen

along with the task information. A maximum of three error log entries

are saved, in the order of occurrence, for each task. Only the first,

second, and last errors that occur will be stored. Any other errors will

not be stored.
For each error, the error log displays the statement number where the

error occurred (STATEMENT) if it is relevant and can be determined.

The DATE and TIME fields will be blank; these functions are not