Siemens SIMATIC S5 Manual page 167

S5-95U, SINEC L2
Figure 8-13 shows the request and confirmation structures for the RUP_MULTIPLE service.
Request
Byte
0 com_class
FDL_Request=00
1 user_id
User-definable ID
2 service_code
Type of service requested:
RUP_MULTIPLE=07
3
irrelevant
4 Bits 4 to 7
service_class
Priority of
send frame
low=0 or
H
high=1
H
5
irrelevant
6
irrelevant
7 rem_add_segment
Logical segment address;
always enter FF
8 .
Send data
. .
(0 to 242 bytes)
249
Must be specified by the user in the request header
Figure 8-13. Request and Confirmation Structures for the RUP_MULTIPLE Service
link_status Message in the Confirmation Header
Table 8-8. link_status Messages for the RUP_MULTIPLE Service
Value of Abbreviation
link_status (PROFIBUS)
00
H
06
H
14
H
15
H
EWA 4NEB 812 6112-02
H
H
Bits 0 to 3
0
H
ok Positive acknowledgement; data area loaded
no Receive SAP not activated; receive SAP not equal to send SAP
lr Response resource being used at the moment by MAC
(temporary fault)
iv Illegal parameters in the request header
Data Transmission by Accessing Layer 2 Services
Confirmation
Byte
0 com_class
Confirmation=01
1 user_id
ID assigned in connection with
a request
2 service_code
Type of service:
RUP_MULTIPLE=07
3 link_status
( Table 8-8 )
4 Bits 4 to 7
service_class
Priority of the
send frame
low=0 or
H
high=1
H
5
irrelevant
6
irrelevant
7 rem_add_segment
Logical segment address;
is always FF
Meaning
H
H
Bits 0 to 3
0
H
8-27