00193786-02 - 第41页

S I P L A C E G EM S W V e r s i on G EM 505 . 03 SP 1 H O S T I n t e r f a c e M anua l ©S i e m en s A G, a ll r i gh t s r e s e r v ed page 41 o f 241 3 . 4 D ata C o ll ect i on 3 . 4 . 1 V ar i a bl es{ XE " …

100%1 / 241
SIPLACE GEM SW Version GEM 505.03 SP1 HOST Interface Manual
Page 40 of 241 ©Siemens AG, all rights reserved
3.3.5 Related Collection Events
The following lists the collection events (CEIDs) which are relevant to the Process State.
For a more complete description of these events, see "Appendix B -- Collection Events"
or the description in this chapter.
Collection Event CEID
{XE „Init2Process“}Init2Process
1000010
{ XE „Process2Init“ }Process2Init
1000011
{ XE Process2SingleFunction
}Process2SingleFunction
1000012
{ XE SingleFunction2Process
}SingleFunction2Process
1000013
{ XE Init2SingleFunction
}Init2SingleFunction
1000016
{ XE FunctionSingle2Init
}FunctionSingle2Init
1000017
SIPLACE GEM SW Version GEM 505.03 SP1 HOST Interface Manual
©Siemens AG, all rights reserved page 41 of 241
3.4 Data Collection
3.4.1 Variables{XE "Variables"}
The SIPLACE has a fixed set of Variables which can be read by the Host. Each Variable
is identified by a unique Variable ID (VID). The Variables which exist are shown in
"Appendix A -- Variables".
There are three types of Variables: {XE "Status Variables"}Status Variables, {XE "Data
Variables"}Data Variables, and {XE "Equipment Constants"}Equipment Constants. The
Host can read Variables of any type, but can set values only for Equipment Constants.
The Host can read values for Status Variables and Equipment Constant whenever the
SIPLACE is On-Line, but values for Data Variables are typically meaningful only
immediately after certain {XE "Collection Events"}Collection Events (CEIDs), and so are
typically reported only in {XE "Event Reports"}Event Reports ({XE "S6F11"}S6F11).
3.4.2 Are You There{XE "Are You There"}
The Host can send {XE "S1F1"}S1F1 at any time to determine if the SECS link is
operational. The SIPLACE responds with {XE "S1F2"}S1F2, if the equipment is in the
ONLINE & COMMUNICATING states. This indicates Model Number ({XE
"MDLN"}MDLN) and Software Revision Number ({XE "SOFTREV"}SOFTREV).
3.4.3 Host Requests Status
The Host can send {XE "S1F3 "}S1F3 when the Equipment is On-Line to read Equipment
Constants from the SIPLACE.
The Host can send {XE "S2F13 "}S2F13 when the Equipment is On-Line to read
Equipment Constants from the SIPLACE.
For this Equipment, S1F3 and S2F13 with a list of VIDs are essentially the same. That
is, either message can return Variables of any type. However, S1F3 with a zero-length
list will return only VIDs of type SV, and S2F13 with a zero-length list will return only
VIDs of type EC.
3.4.4 Setting Equipment Constants
The Equipment Operator can change the value for Equipment Constants. Once the
Operator has changed an EC value, the Equipment will note the {XE "EqConstChange
"}EqConstChange Event (CEID 1000001). The VID for the changed EC will be reported
to the Host in the variable {XE "ECIDCHANGE "}ECIDCHANGE (VID 1002036).
3.4.5 Event Reports{XE "Event Reports"}
The SIPLACE has a fixed set of Events which can occur. Each Event is identified by a
unique Collection Event ID (CEID). The CEIDs which exist are shown in "Appendix B --
Collection Events".
When an Event occurs, the Equipment sends the appropriate {XE "S6F11"}S6F11 Event
Report message to the Host (if that particular event has been enabled). Event Reports
are defined by the Host ({XE "S2F33"}S2F33) and linked to a specific CEID ({XE
"S2F35"}S2F35).
The Equipment allows the Host to enable and disable Event Reports using {XE
"S2F37"}S2F37. If the Host enables a CEID, for which no Event Report is defined, the
Equipment will send a "null" (no data) report when the event occurs.
The Host can "force" Event Reports on the Equipment using the following Event Report
Request messages:
{XE "S6F15"}S6F15 Host Requests an Event Report associated with a CEID.
SIPLACE GEM SW Version GEM 505.03 SP1 HOST Interface Manual
Page 42 of 241 ©Siemens AG, all rights reserved
{XE "S6F17"}S6F17 Host requests an Annotated Event Report associated with a
CEID.
{XE "S6F19"}S6F19 Host requests an Event Report associated with a Report ID.
{XE "S6F21"}S6F21 Host requests an Annotated Event Report associated with a
Report ID.
3.4.6 Time Driven Trace{XE "Time Driven Trace"}
The SIPLACE supports Time Driven Trace initiated from the Host. The Host initializes a
trace using {XE "S2F23"}S2F23. The Equipment will send the data requested after the
specified time interval has expired. The data will be sent using the {XE "S6F1 "}S6F1
({XE "Trace Data Send"}Trace Data Send) message.
The Equipment can handle several concurrent traces. The number of concurrent traces
is determined by the size of the trace data requested. The Equipment can support at
least four concurrent traces to a maximum size (i.e. all variables requested).
The equipment allows Host definition of trace data to exceed the one-block limit when
reported. That is, the SEMI E5 standard states that the S6F1 (Trace Data Send)
message is limited to a single SECS block; but the Equipment will allow this point to be
overlooked at the Host's request. If the Host does define trace data to be larger than one
SECS block, then the Equipment will send the multiple blocks, not preceded by the
S6F5/S6F6 Inquire/Grant scenario.
3.4.7 Limits Monitoring{XE "Limits Monitoring"}
The Host can define limits for various Variables on the SIPLACE. When the appropriate
limits transitions occur, the SIPLACE will report this occurrence by sending an event to
the Host (if the event is enabled). The Host may define limits for a particular Variable
through the {XE "S2F45 "}S2F45 (Define Variable Limit Attributes). Through this
message, the Host may define up to seven limits for each eligible Variable. For each
limit ({XE "LIMITID"}LIMITID), the Host defines an {XE "UPPERDB "}UPPERDB and a
{XE "LOWERDB"}LOWERDB. The SIPLACE generates events when a transition across
these boundaries occurs. The Host may set the rate at which the SIPLACE polls the
Variables to determine if a limit has been crossed by setting the {XE "GEMLIMITSTIMER
"}GEMLIMITSTIMER variable (VID 65).