00191134-03 - 第114页
GEM for SIPLACE V5.01 Page 114 of 252 ©Siemens AG, all rights reserved 6)5HTX HVW6SRROHG'DWD$ FNQRZOHGJH S6F24 * H <- E <B [1] RSDA> . Equipment ac knowledges the Hos t's request to ei…
GEM for SIPLACE V5.01
©Siemens AG, all rights reserved page 113 of 252
6) 5HTXHVW$QQRWDWHG5HSRUW'DWD
S6F22 * H<-E, Multiblock
<L
<L [2]
<U4 VID> * VID - Variable ID
<V>
>
...
> .
The Equipment sends the Annotated Report.
If no Report is defined for the RPTID in S6F21, S6F22 has the following special error
format:
S6F22 * H<-E
<L> .
6)5HTXHVW6SRROHG
S6F23 W * H -> E
<U1 RSDC> .
The Host sends this message to start the transfer of spooled messages from the
Equipment to the Host, or to delete the contents of the spool file, depending on the value
of RSDC.
When the Host requests the spooled messages (RSDC is zero), the Equipment will send
messages according to EC "MaxSpoolTransmit". All messages are sent from oldest to
newest, and once the message is successfully sent, it is removed from the spool. If
MaxSpoolTransmit is zero, all messages will be sent one at a time until the last message
has been delivered. If MaxSpoolTransmit is set to a non-zero value, the Equipment will
send the lesser of MaxSpoolTransmit or messages left in spool. If in this case the
Equipment sends MaxSpoolTransmit messages, and messages remain in the spool, the
Equipment will wait for another S6F23 to deliver the next messages.
If the Host sends S6F23 with RSDC set to one, this will be interpreted by the Equipment
as a request to purge the spool.
RSDC Description
0 Transmit spooled messages.
1 Purge spooled messages
GEM for SIPLACE V5.01
Page 114 of 252 ©Siemens AG, all rights reserved
6)5HTXHVW6SRROHG'DWD$FNQRZOHGJH
S6F24 * H <- E
<B [1] RSDA> .
Equipment acknowledges the Host's request to either purge spooled messages or send
spooled messages to the Host.
RSDA Description
0x00 Normal. Equipment will start to send spooled
data or optionally purge the spool. Action
performed will depend on value for RSDC in
S6F23.
0x02 Denied. Spooled data does not exist.
GEM for SIPLACE V5.01
©Siemens AG, all rights reserved page 115 of 252
6WUHDP
6)3URFHVV3URJUDP/RDG,QTXLUH
S7F1 W * H<->E
<L [2]
<A PPID> * Process Program ID
<U4 LENGTH> * Length of text
> .
The Sender requests permission to send a Process Program. The Process Program may
be either a Load Recipe, Process Recipe, or Parameter Table.
The Equipment always sends this Inquire/Grant transaction before sending any multi-
block S7F3. LENGTH specifies the number of bytes in the following S7F3 message,
excluding SECS-I block-length bytes, block headers, and checksums.
For Host-to-Equipment transfers, this Inquire/Grant is optional. The Equipment accepts it,
but ignores it, commits no resources, and initiates no Conversation timeout. The
Equipment will accept a multi-block S7F3 even if not preceded by the Inquire/Grant.
6)3URFHVV3URJUDP/RDG
S7F2 * H<->E
<B [1] 00> . * PPGNT
The Receiver grants permission to send a Process Program. The Receiver sends
PPGNT value 0x00 to indicate it will accept the Process Program, and the Sender should
send S7F3. If the Receiver sends any other value in S7F2, it refuses the Grant, and the
Sender should not send S7F3.
The Process Program may be either a Load Recipe, Process Recipe, or Parameter Table.
When the Equipment sends S7F2, PPGNT may contain the following codes:
PPGNT Description
0x00 Normal. Permission granted.
When the Host sends S7F2, the Equipment interprets PPGNT as follows:
PPGNT Description
0x00 Normal. The Equipment sends S7F3.
Other Refusal. The Equipment does not send S7F3
and the upload operation fails.
6)3URFHVV3URJUDP
S7F3 W * H<->E, Multiblock
<L [2]
<A PPID> * PPID - Process Program ID
<B [n] PPBODY> * PPBODY - Process Program Body