semi合集-English.pdf - 第1337页

SEMI E30-1103 © SEMI 1992, 2003 11 Table 3.2 Communications State Transition Table # Current State Trigger New State Action Comment 1 (Entry to COMMUNICA- TIONS) System initialization. System Default None. The system def…

SEMI E30-1103 © SEMI 1992, 2003

NOT COMMUNICATING/EQUIPMENT-INITIATED

CONNECT

This state has two substates, WAIT CRA and

WAIT DELAY. Upon any entry to the NOT

COMMUNICATING state, whenever

EQUIPMENT-INITIATED CONNECT first

becomes active, a transition to WAIT CRA occurs,

the CommDelay timer is set to “expired,” and an

immediate attempt to send S1,F13 is made.

NOT COMMUNICATING/EQUIPMENT-INITIATED

CONNECT/WAIT CRA

An Establish Communications Request has been

sent. The equipment waits for the host to

acknowledge the request.

NOT COMMUNICATING/EQUIPMENT-INITIATED

CONNECT/WAIT DELAY

A connection transaction failure has occurred. The

CommDelay timer has been initialized. The

equipment waits for the timer to expire.

NOT COMMUNICATING/HOST-INITIATED CON-

NECT

This state describes the behavior of the equipment

in response to a host-initiated S1,F13 while NOT

COMMUNICATING is active.

NOT COMMUNICATING/HOST-INITIATED CON-

NECT/WAIT CR FROM HOST

The equipment waits for an S1,F13 from the host.

If an S1,F13 is received, the equipment attempts to

send an S1,F14 with COMMACK = 0.

ENABLED/COMMUNICATING

Communications have been established. The

equipment may receive any message from the host,

including S1,F13. When the equipment is

COMMUNICATING, SECS communications with

a host computer must be maintained. This state

remains active until communications are disabled

or a communication failure occurs. If the

equipment receives S1,F13 from the host while in

the COMMUNICATING substate, it should

respond with S1,F14 with COMMACK set to zero.

If the equipment receives S1,F14 from a previously

sent S1,F13, no action is required.

In the event of communication failure, the

equipment shall return to the NOT

COMMUNICATING substate and attempt to re-

establish communications with the host.

It is possible that the equipment may be waiting for

an S1,F14 from the host in EQUIPMENT-

INITIATED CONNECT/WAIT CRA at the time

an S1,F13 is received from the host in HOST-

INITIATED CONNECT/WAIT CR FROM HOST.

When this situation occurs, both equipment and

host have an open S1,F13/S1,F14 transaction.

Since communications are successfully established

on the successful completion of any S1,F13/S1,F14

transaction, either of these two transactions may be

the first to complete successfully and to cause the

transition from NOT COMMUNICATING state to

COMMUNICATING. In this event, the other

transaction shall remain open regardless of the

transition to COMMUNICATING until it is closed

in a normal manner.

If the equipment has not yet sent

an S1,F14 to a

previously received S1,F13 at the time when

COMMUNICATING becomes active, the S1,F14

response shall be sent in a normal manner. A

failure to send the S1,F14 is then treated as any

other communication failure.

If the equipment-initiated S1,F13/S1,F14 is still

open when the transition to COMMUNICATING

occurs, subsequent failure to receive a reply from

the host is considered a communication fault by

equipment. An S9,F9 should be sent when a

transaction timer timeout occurs

. (See Section 4.9

for definitions of communication faults and

message faults, as well as detail on Stream 9 Error

Messages.)

3.2.5 State Transitions — Table 3.2 contains a full

description of the state transitions depicted in Figure

3.2.1.

When the operator switches from the DISABLED state

to the ENABLED state, no collection event shall occur,

since no messages can be sent until communications

have been established. The process of establishing

communications serves to notify the host that

communications are ENABLED. No other collection

events are defined for the Communications State

Model.

6 This includes transmissions that may have started but not yet

successfully completed at the time that the transition to

COMMUNICATING occurs.

7 The existence of a transaction timer is not a requirement in some

protocols, such as SMS (SEMI E13).

SEMI E30-1103 © SEMI 1992, 2003

Table 3.2 Communications State Transition Table

# Current State Trigger New State Action Comment

1 (Entry to

COMMUNICA-

TIONS)

System initialization. System Default None. The system default

may be set to

DISABLED or

ENABLED.

2 DISABLED Operator switches

from DISABLED to

ENABLED.

ENABLED None. SECS-II

communications are

enabled.

3 ENABLED Operator switches

from ENABLED to

DISABLED.

DISABLED None. SECS-II

communications are

prohibited.

4 (Entry to

ENABLED)

Any entry to

ENABLED state.

NOT

COMMUNICATING

None. May enter from

system initialization

to ENABLED or

through operator

switch to

ENABLED.

5 (Entry to

EQUIPMENT-

INITIATED

CONNECT)

(Any entry to NOT

COMMUNICA-

TING)

WAIT CRA Initialize

communications. Set

CommDelay timer

“expired.” Send

S1,F13.

Begin the attempt to

establish

communications.

6 WAIT CRA Connection

transaction failure.

WAIT DELAY Initialize

CommDelay timer.

Dequeue all

messages queued to

send.

If appropriate,

dequeued messages

shall be placed in

spool buffer in the

order generated. Wait

for timer to expire.

7 WAIT DELAY CommDelay timer

expired.

WAIT CRA Send S1,F13 Wait for S1,F14.

May receive S1,F13

from Host.

8 WAIT DELAY Received a message

other than S1,F13.

WAIT CRA Discard message. No

reply. Set

CommDelay timer

“expired”. Send

S1,F13.

Indicates opportunity

to establish

communications.

9 WAIT CRA Received expected

S1,F14 with

COMMACK = 0.

COMMUNICATING None. Communications are

established.

10 (Entry to HOST-

INITIATED

CONNECT)

(Any entry to NOT

COMMUNICA-

TING)

WAIT CR FROM

HOST

None. Wait for S1,F13 from

Host.

14 COMMUNICATING Communication

failure. (See SEMI

E4 or SEMI E37 for

a protocol-specific

definition of

communication

failure.)

NOT

COMMUNICATING

Dequeue all

messages queued to

send.

Dequeued messages

may be placed in

spool buffer as

appropriate.

15 WAIT CR FROM

HOST

Received S1,F13. COMMUNICATING Send S1,F14 with

COMMACK = 0.

Communications are

established.

3.3 Control State Model — The CONTROL state

model defines the level of cooperation between the host

and equipment. It also specifies how the operator may

interact at the different levels of host control. While the

COMMUNICATIONS state model addresses the

ability

for the host and equipment to exchange

messages, the CONTROL model addresses the

equipment’s responsibility

to act upon messages that it

receives.

The CONTROL model provides the host with three

basic levels of control. In the highest level (REMOTE),

the host may control the equipment to the full extent

possible. The middle level (LOCAL) allows the host

full access to information, but places some limits on

how the host can affect equipment operation. In the

lowest level (OFF-LINE), the equipment allows no host

control

and only very limited information.

The control model and communications model (when

implemented) do not interact directly. That is, no action

or state of one model directly causes a change in

behavior of the other. It is true, however, that when the

communication state is NOT COMMUNICATING

then most message transaction are not functional. When

messages cannot be transmitted, the control capabilities

and all other GEM capabilities are affected.

Refer to Figure 3.3 as the CONTROL substates and

state transitions are defined.

OFF-LINE

When the OFF-LINE state is active, operation of the

equipment is performed by the operator at the operator

console. While the equipment is OFF-LINE, message

transfer is possible. However the use of messaging for

any automation purpose is severely restricted. While

the OFF-LINE state is active, the equipment will only

respond to those messages used for the establishment of

communications or a host request to activate the ON-

LINE state.

While OFF-LINE, the equipment will respond with an

Sx,F0 to any primary message from the host other than

S1,F13 or S1,F17. It will process and respond to

S1,F13 and S1,F17. S1,F17 is used by the host to

request the equipment to transition to the ON-LINE

state. The equipment will accept this request and send a

positive response only when the HOST OFF-LINE

state is active (see transition 11 definition below).

8 The host may establish communications. This does not affect

equipment operation and for that reason is not termed a control

operation.

9 The host may determine the equipment identification via the

S1F13/F14 transaction.

While the OFF-LINE state is active, the equipment

shall attempt to send no primary message other than

S1,F13,

S9,Fx,

and S1,F1 (see ATTEMPT ON-

LINE substate). If the equipment receives a reply

message from the host other than S1,F14 or S1,F2, this

message is discarded.

No messages enter the spool when the system is OFF-

LINE. Spooling may be active when the

Communications State of NOT COMMUNICATING is

active. This might occur during OFF-LINE, but since

the equipment will not attempt to send messages except

as mentioned in the previous paragraph

, no messages

will enter the spool.

OFF-LINE has three substates: EQUIPMENT OFF-

LINE, ATTEMPT ON-LINE, and HOST OFF-LINE.

OFF-LINE/EQUIPMENT OFF-LINE

While this state is active, the system maintains the

OFF-LINE state. It awaits operator instructions to

attempt to go ON-LINE.

OFF-LINE/ATTEMPT ON-LINE

While the ATTEMPT ON-LINE state is active, the

equipment has responded to an operator instruction to

attempt to go to the ON-LINE state. Upon activating

this state, the equipment attempts to send an S1,F1 to

the host.

Note that when this state is active, the system does not

respond to operator actuation of either the ON-LINE or

the OFF-LINE switch.

10 Sending of S1,F13 is based upon the COMMUNICATIONS state

model.

11 S9,Fx messages may be issued only in response to the messages to

which the equipment will normally respond while OFF-LINE (i.e.

S1,F13 and S1,F17).

12 The equipment may send S1,F1 or S1,F13, but since Stream 1

messages are not eligible for spooling, they will not enter the spool

either.