00192402-01 - 第39页
GEM for SIPLACE V7.01 ©Siemens AG, all rights r eserved page 39 of 251 Variable Nam e VID PPCHANGENAME 1002024 PPEXECNAME 1002027 PPCHANGESTAT US 1002025 5HODWHG(YHQWV The f ollowing lists the collect ion events …
GEM for SIPLACE V7.01
Page 38 of 251 ©Siemens AG, all rights reserved
Variable Name VID
CONFIGALARMS 1002018
WBITS5 1002019
ALARMID 1002013
ALARMSERIAL 1002015
ALARMSENABLED 1002020
ALARMSSET 1002021
ALARMSTATE 1002014
5HODWHG&ROOHFWLRQ(YHQWV
Each alarm defined on the SIPLACE has two unique collection events associated with it, a
"Going-On" event, and a "Going-Off" event. The CEIDs are listed in "Appendix B --
Collection Events".
3URFHVV3URJUDP0DQDJHPHQW
Processing on the SIPLACE is controlled by Process Programs. The Equipment requires
selection of a Process Program for each process. The SIPLACE supports the use of
unformatted process programs.
Equipment Management of Process Programs
The SIPLACE provides a Process Program Library, implemented as a set of ASCII files
maintained on a hard disk. Each Process Program is identified by a unique Process
Program ID (PPID). A PPID consists of ASCII characters
The Equipment Operator may modify any one of the Process Programs stored on the
Equipment. The host will be notified via the GemPPChangeEvent (CEID 1000016)
Collection Event if the Operator creates, changes, or deletes a Process Program. The
Equipment Operator can also select a PPID to be uploaded to the Host (S7F3), or
download from the Host (S7F5).
Host Management of Process Programs
Process Programs are saved to disk on the equipment. Process Programs are typically
created and updated at the SIPLACE. However, the SIPLACE provides complete facilities
for the Host to manage the storage and use of Process Programs. This allows the
SIPLACE to operate cooperatively Host-implemented systems. The Host has the
following capabilities.
The Host can upload a Process Program from the SIPLACE Library by using S7F5
(Process Program Request). The equipment operator can also initiate a Process
Program Upload through the SIPLACE's user interface.
The Host can download a Process Program to the SIPLACE library by using S7F3
(Process Program Send). The Host may send S7F1 (Multi-block Inquire) to the
equipment before sending a multi-block Process Program. The equipment operator can
also initiate a Process Program Download through the SIPLACE's user interface.
The Host can delete one or more Process Programs from the SIPLACE library by using
S7F17 (Process Program Delete).
The Host can determine which Process Programs are currently stored in the SIPLACE
library by using S7F19 (Process Program Directory).
5HODWHG9DULDEOHV
The following table lists the variables (SV's, EC's, or DVVALS) which are relevant to
process program management. For a more complete description of these variables, see
"Appendix A -- Variables".
GEM for SIPLACE V7.01
©Siemens AG, all rights reserved page 39 of 251
Variable Name VID
PPCHANGENAME 1002024
PPEXECNAME 1002027
PPCHANGESTATUS 1002025
5HODWHG(YHQWV
The following lists the collection events (CEIDs) which are relevant to process program
management. For a more complete description of these events, see "Appendix B --
Collection Events" or the description in this chapter.
Collection Event CEID
GemPPChangeEvent 1000016
GemBadDownloadEvent 1000017
GEM for SIPLACE V7.01
Page 40 of 251 ©Siemens AG, all rights reserved
5HPRWH&RPPDQGV
Setup and processing on the SIPLACE machines can be driven by either a local operator
or by a Host computer. This section describes the remote commands available at the
Host.
Much of the behavior of SIPLACE and its acceptance of remote commands is directed by
requirements of the Control State. For a complete description of the Control State, please
see section 4.2, "Control States".
The SIPLACE will accept remote commands only when the Control State is Remote.
While in the Local state, the Host can not put the Equipment into Remote, this must be
done by an operator at the Equipment.
The Host has the ability to configure whether the Equipment will enter the Remote or local
state as a default upon entering the On-Line state from Off-Line. This is done by setting
The ONLINESUBSTATE Equipment Constant (VID 1002009) to 4 (Local) or 5 (Remote).
Once in the Remote state, the Host has the authority to issue any of these remote
commands and they will not be rejected because of an invalid control state. Commands
may be rejected for other reasons (trying to start a process with no material loaded, etc.).
While in Remote state, the Operator still has the ability to issue commands and change
the control state. If the operator issues a command while in Remote state, the SIPLACE
will send the OPERATORCMDINREMOTESTATE collection event if enabled (CEID
1002056). When the Operator "grabs" control away from the Host by changing the
Control State to local, the SIPLACE will send either the GemControlStateLOCAL (CEID
1000003) or GemEquipmentOFFLINE (CEID 1000005) event to the Host.
6)&RPPDQGV
The general format for remote commands using the S2F41 message is:
6)>:@ +!(
/>@
$5&0'! 5HPRWHFRPPDQGVWULQJ
/
/>@
$&31$0(! &RPPDQG3DUDPHWHU1DPH
&39$/! &RPPDQG3DUDPHWHUDOXH
!
!
!
The following commands may be sent by the Host to the SIPLACE.
67$57
This command starts processing on the SIPLACE assuming all proper initialization has
taken place and material is present.
6)>:@
/>@
$67$57!
/!
!