semi合集-English.pdf - 第4399页
SEMI F97-0305 © SEMI 2005 9 Table 1 State Transition for Watchd og-Toggle Number Previous State Trigge r New State Actions Remark 1 (no state) Start up of FPU. On or Off Timer is set to expire for the next time period. D…
SEMI F97-0305 © SEMI 2005 8
9.2 FPU Requirements
9.2.1 The FPU shall be able to run without a FMCS and shall communicate a minimal amount of status information
to FMCS via the network as described in the next section.
9.3 FMCS Requirements
9.3.1 The FMCS shall be able to support the interface to the FPU and to make the information of this interface
available through the Data Cache of the FMCS. The FMCS shall be able to either monitor and/or control the FPU
depending on the application.
9.4 State Models of Facility Package Unit
9.4.1 State Models are used to describe the status of the FPU. For the definition of the status models see §8. In the
following all status values are specified together with their transitions.
9.4.2 Watchdog-Toggle
9.4.2.1 The Watchdog-toggle shall be used to signal that a FPU still is capable to perform its processing function
and is able to notify this to the FMCS. As long as the toggle mechanism alternates between “on” and “off” the
processing function of the FPU is assumed to be functional. The processing function is assumed to be a
programmed function, e.g. for a PLC. The toggle mechanism shall be linked into the processing function of the FPU
so that if the processing function stops, the toggle mechanism will stop as well. Watchdog-toggle represents a
variable that toggles its value between “0” and “1” within a specified time window. The maximum required cycle
time shall not exceed one minute. The Watchdog-toggle is used to realize a “life-beat monitoring function”.
9.4.2.2 The Watchdog-toggle is always required except
in the case that the underlying communication system of the FPU and the FMCS already provides an integrated
life-beat function, or
the FPU is a very simple device which does not provide any processing function (e.g., a valve, electrical engine
or heater).
Watchdog-Toggle
On Off
2
3
C
1
Figure 4
State Transition Diagram Watchdog-Toggle
SEMI F97-0305 © SEMI 2005 9
Table 1 State Transition for Watchdog-Toggle
Number Previous State Trigger New State Actions Remark
1 (no state) Start up of FPU. On or Off Timer is set to expire for
the next time period.
Dependent on
Implementation.
2 On Timer expired. Off Timer is set to expire for
the next time period.
3 Off Timer expired. On Timer is set to expire for
the next time period.
9.4.3 OP-Mode
9.4.3.1 OP-Mode specifies the operation mode of the FPU. It can assume two values: Manual and Automatic. The
behavior of the FPU with respect to the states Manual and Automatic is out of scope.
Manual: FPU operates in manual mode.
Automatic: FPU operates in automatic mode.
OP-Mode
Manual Automatic
2
3
C
1
Figure 5
State Transition Diagram OP-Mode
Table 2 State Transition Table for OP-Mode
Number Previous State Trigger New State Actions Remark
1 (no state) Start up of FPU. Manual or Automatic None. Dependent on type of FPU.
2 Manual Trigger to switch
to Automatic.
Automatic FPU performs its
automatic
functions.
Trigger may be caused by:
manual operator action
or automatic trigger by a
programmed logic.
3 Automatic Trigger to switch
to Manual.
Manual FPU stops its
automatic
functions.
Trigger may be caused by:
manual operator action
or automatic trigger by a
programmed logic.
9.4.4 Control-Mode
9.4.4.1 Control-Mode specifies the control mode of the FPU with respect to the FMCS. It may assume two values:
Local and Remote. The behavior of the FPU with respect to the states Local and Remote is out of scope. It is
dependent on the type of FPU. Control Mode is intended to be used by the FMCS to identify whether a remote
operation of the FPU is enabled or disabled – by this the FMCS can allow or disallow operator actions on the FMCS
SEMI F97-0305 © SEMI 2005 10
with respect to that particular FPU. On the FPU this control mode may be used to enable or disable remote control
of the FMCS.
Local: FPU operates in local mode, i.e. it can be controlled locally.
Remote: FPU operates in remote mode, i.e. it can be remotely controlled by the FMCS.
Control-Mode
Local Remote
2
3
C
1
Figure 6
State Transition Diagram Control-Mode
Table 3 State Transition Table Control-Mode
Number Previous State Trigger New State Actions Remark
1 (no state) Start up of FPU. Local or Remote FPU disables remote
control from FMCS.
Dependent on type of FPU.
2 Local Trigger to switch to
Remote.
Remote FPU enables remote
control from FMCS.
Trigger may be caused by:
manual operator action
or automatic trigger by a
programmed logic.
3 Remote Trigger to switch to
Local.
Local FPU disables remote
control from FMCS.
Trigger may be caused by:
manual operator action
or automatic trigger by a
programmed logic.
9.4.5 Run-Mode
9.4.5.1 Run-Mode specifies the different running states of the FPU. It assumes three main values: Down, in Stand-
by or Run. The behavior of the FPU with respect to the states of Run-Mode is out of scope. It is dependent on the
type of FPU. The Annex to this Standard (see Related Information 1) provides some examples of the use of Run-
Mode. The Run-Mode provides general information of the FPU, whether it is Down, in Stand-by or in Run:
Down (the FPU is in a fault situation or it may be switched into Down by a pre scheduled function; this is
specified by an optional flag):
o flag set for scheduled down
o flag set for unscheduled down
Stand-by (the FPU is ready to be switched into Run).
Run (the FPU is running).
9.4.5.2 The FPU should assume optionally sub states when in Run or Stand-by. These sub states are:
Run: sub state Locked (the FPU is locked to hold the Run state) or Not_Locked and
Stand-by: sub state Locked (the FPU is locked to hold the Stand-by state) or Not_Locked.