GE GFK-1004B user manual Time Command, Trace Command

5

A typical TEST command is shown below:

Page 1 of 1

=test 0800190100fb 100H Test initiated

=
<<< Test Results >>>
Command: test <<08001901001f>> 100H 32H 1H			ALT
Init node: <<08001901001f>> Frames sent :			100H	Nodes responding : 1H
Responding nodes	Response recd	Response w/err		No Response
<<0800190100fb>>	100H	0H		0H

TIME Command

The TIME command has the form:

TIME

This command causes the current system time to be displayed. This time is used in gen- erating time stamps for messages which require them. This time is also used as a time stamp for events in the exception log displayed by the LOG command. The initial value of the time on restart, power up, or load is read from the local PLC CPU. If this is not available, it is set to 00:00:00.0 (midnight). Time values are based on a 24 hour clock. The Modify command CHTIME is used to change the time value.

A typical TIME command is shown below:

> time

Time = 15:46:02.3

TRACE Command

The TRACE command has the form:

TRACE {<task(s)> [<minutes> [<len_ref>]] !}

where <task(s)> is one or more task identifier letters from Table 5±3 or ªzº to add PDU trace.

<minutes>is an optional parameter that specifies how long TRACE will remain active. Default is 10 minutes. This parameter is a character string that specifies an integer which can be 0, or a value from 1 to 32767. If 0 is specified then time out is not enforced. Any non-zero value specifies the duration in minutes after which the trace activity will auto- matically cease. Login will be maintained (automatic logout will be inhibited) until after the trace has terminated.

<len_ref> is an optional parameter that limits the amount of PDU (z) data to be dis- played. The PDU display format is a character string that specifies an integer value ranging from 1 to 32767. If omitted from the command line, the value 48 will be substi- tuted. This parameter provides the flexibility to view the PDU in its entirety or just a portion of it. Since each line of display consists of 16 bytes, and, if truncating of the PDU does take place (always at the end of a line and trailed by '...' on the next line), the actual number of bytes displayed will be rounded up to the next multiple of 16 from <len_ref>. There is, of course, a performance penalty for displaying large PDU's when they occur frequently.

GFK-1004B Chapter 5 The Station Manager 5-43