Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 131
PROFIBUS-Specification-Normative-Parts-4:1997
Copyright by PNO 1997 - all rights reserved
In order to manage the security sequence, the initiator shall carry a FCB for
each responder. When an action frame (request or send/request frame) is trans-
mitted to a responder for the first time or again to a responder currently
marked as "non operational", the associated FCB shall be set definitely. The
initiator achieves this by an action frame with FCV=0 and FCB=1. The responder
shall classify such a frame as first message cycle and store FCB=1 together with
the initiator's address (SA and optional SAE[b7=1]) (see table 3b). This message
cycle is not repeated by the initiator.
If a responder supports the Region/Segment addressing and the request frame con-
tains a source Region/Segment address (SAE[b7=]) which is unequal to the own
Region/Segment address (DAE[b7=1]), then the responder shall store the SAE[b7=1]
together with the SA.
In the following action frames to the same responder the initiator shall set
FCV=1 and toggle FCB with each new action frame. The responder shall evaluate
FCB when receiving an action frame addressed to itself with FCV=1. A FCB changed
in comparison with the same initiator's (same SA and optional same SAE[b7=1])
preceding action frame is considered as confirmation of the preceding message
cycle's correct completion. If the action frame originates from a different
initiator (different SA or optionaldifferent SAE[b7=1]), there is no evaluation
of the FCB. In both cases the responder shall store the FCB with the source ad-
dress (SA and optional SAE[b7=1]) until it receives a new frame addressed to it-
self.
If an acknowledgement or response frame is missing or corrupted, the FCB shall
not be changed by the initiator in the retry; this indicates the faulty preced-
ing message cycle. If a responder receives an action frame with FCV=1 and the
same FCB as in the same initiator's (same SA and optional same SAE[b7=1]) imme-
diately preceding action frame, a retry is being carried out. As a result the
responder shall again transmit the acknowledgement or response frame kept in
readiness.
The responder shall keep ready the preceding acknowledgement or response frame
for a potential retry, until it gets the above mentioned confirmation, or until
it receives a Hd4-faultless frame with changed address (SA or DA or optional
SAE[b7=1] or DAE[b7=1]), or a Send Data with No Acknowledge (SDN), or a token
frame.
For "Send Data with No Acknowledge", "Request FDL Status", "Request Ident" and
"Request LSAP Status", FCV and FCB are = 0; the responder does not analyze FCB.
Page 132
PROFIBUS-Specification-Normative-Parts-4:1997
Copyright by PNO 1997 - all rights reserved
Table 3b. FCB, FCV in Responder
+---------------------------------------------------------------+
! b6 b5 <-- Bit Position !
! !
! FCB FCV! Condition ! Meaning ! Action !
! ! ! ! !
+--------+------------+----------------------+------------------+
! ! ! ! !
! 0 0 ! DA = TS/127! Request with No Ack ! last Ack or !
! ! ! Request FDL-Status/ ! delete Reply !
! ! ! Ident/ LSAP-Status ! !
! ! ! ! !
! 0/1 0/1! DA # TS ! Request to other !last Ack or Reply !
! ! ! Responder ! may be deleted !
! ! ! ! !
! 1 0 ! DA = TS ! First Request ! FCBM := 1 !
! ! ! ! SAM := SA
*)
!
! ! ! ! last Ack or !
! ! ! ! delete Reply !
! ! ! ! !
! 0/1 1 ! DA = TS ! New Request ! last Ack or !
! ! SA = SAM ! ! delete Reply !
! ! FCB # FCBM ! ! FCBM := FCB !
! ! ! ! have Ack or !
! ! ! ! Reply ready for !
! ! ! ! Retry !
! ! ! ! !
! 0/1 1 ! DA = TS ! Request Retry ! FCBM := FCB !
! ! SA = SAM ! ! repeat Ack or !
! ! FCB = FCBM ! ! Reply and keep !
! ! ! ! it ready !
! ! ! ! !
! ! ! ! !
! 0/1 1 ! DA = TS ! New Initiator ! FCBM := FCB !
! ! SA # SAM ! ! SAM := SA
*)
!
! ! ! ! have Ack or !
! ! ! ! Reply ready for !
! ! ! ! Retry !
! ! ! ! !
! -- -- ! Token- ! --- !last Ack or Reply !
! ! Frame ! ! may be deleted !
! ! ! ! !
! ! ! ! !
+--------+------------+----------------------+------------------+
! !
! FCBM stored FCB !
! SAM stored SA !
! !
+---------------------------------------------------------------+
4.7.4 Check Octet (FCS)
The check octet FCS which is required for Hamming distance 4 in a frame always
immediately precedes the end delimiter. It is structured as follows:
b8 b1
+---+---+---+---+---+---+---+---+
! 2
7
! ! 2
0
!
+---+---+---+---+---+---+---+---+
Figure 19. FCS Octet Coding
In frames of fixed length with no data field (see subclause 4.6.1) the check
octet shall be calculated from the arithmetic sum of DA, SA and FC without start
and end delimiter and without taking the carry-overs into consideration.
Page 133
PROFIBUS-Specification-Normative-Parts-4:1997
Copyright by PNO 1997 - all rights reserved
In frames of fixed length with data field (see subclause 4.6.2) and in frames
with variable data field length (see subclause 4.6.3) the check octet shall
additionally include the DATA_UNIT.
4.7.5 Data Field (DATA_UNIT)
The data field consists of an address field and the user data of the FDL/FMA1/2
user. The address field contains from 0 to at most 4 address extension octets
(see subclause 4.7.2). The user data without address extension comprises a
maximum of 246 octets. The definition and interpretation of the user data
(L_sdu) for the data transmission services (see Part 3, clause 4.1) are
described in Part 6 of this specification.
Data Field (DATA_UNIT)
+<--------------------------------------------->+
! !
--+-----+------//-------+--------------/ /--------------+-----
! FC I DAE/SAE I I
--+-----+------//-------+--------------/ /--------------+-----
! ! !
! Address ! User Data !
+<------------->+<----------------------------->+
Figure 20. Data Field
The following user data are defined for the remote management services "Request
Ident" and "Request LSAP Status" (see Part 3, clause 4.2):
Page 134
PROFIBUS-Specification-Normative-Parts-4:1997
Copyright by PNO 1997 - all rights reserved
Ident User Data:
The Ident user data contains the station's Ident_List with vendor name
(Vendor_name), PROFIBUS controller type (Controller_type) and hardware and soft-
ware release (HW/SW_release). It comprises a maximum of 200 octets:
----+-------+-------+-------+-------+---------------+//
! LE_VN ! LE_CT ! LE_HR ! LE_SR ! Vendor_name !
----+-------+-------+-------+-------+---------------+//
!
! Ident Data
+<----------------------------------------------//
//------------------+--------------+--------------+-----
Controller_type ! HW_release ! SW_release !
//------------------+--------------+--------------+-----
!
!
//----------------------------------------------->+
LE_VN, LE_CT, LE_HR, LE_SR:
1 octet each. Length of corresponding Data Field in octets;
dual coding, significance as in Fig. 19.
Vendor_name, VN:
Name of Manufacturer as ASCII String (ISO 7 Bit Code, b8=0).
Controller_type, CT:
Hardware Controller Type as ASCII String (ISO 7 Bit Code, b8=0).
HW_release, HR:
Hardware Release of Controller as ASCII String (ISO 7 Bit Code, b8=0).
SW_release, SR:
Software Release of Controller as ASCII String (ISO 7 Bit Code, b8=0).
Figure 21. Ident User Data
Page 135
PROFIBUS-Specification-Normative-Parts-4:1997
Copyright by PNO 1997 - all rights reserved
LSAP Status User Data:
The LSAP Status user data contains the configuration of a service access point
at the remote station and has the following octets:
b8 b5 b4 b1
+---+---+---+---+---+---+---+---+
Octet 1 ! Access !
+---+---+---+---+---+---+---+---+
! Address-Extension !
+---+---+---+---+---+---+---+---+
!Role_in_service! Service_type !
+---+---+---+---+---+---+---+---+
! !
+-- - " - --+
! !
+---+---+---+---+---+---+---+---+
Octet 6 !Role_in_service! Service_type !
+---+---+---+---+---+---+---+---+
Access:
b8 b1 <-- Bit Position
0 1 1 1 1 1 1 1 = All
EXT 0 0 0 0 0 0 0 )
to > 0 to 126 (FDL Address,
EXT 1 1 1 1 1 1 0 ) Station Address)
EXT = 0: Address Extension invalid
EXT = 1: Address Extension valid
Address Extension:
b8=0, b7=1, b1 to b6: Region/Segment Address
(Significance: see Fig. 17)
Service_type:
b4 b1 <-- Bit Position
0 0 0 0 Send Data with Acknowledge (SDA)
0 0 0 1 Send Data with No Acknowledge (SDN)
0 0 1 1 Send and Request Data with Reply (SRD)
0 1 0 1 Cyclic Send and Request Data
with Reply (CSRD)
Role_in_service:
b8 b5 <-- Bit Position
0 0 0 0 Initiator
0 0 0 1 Responder
0 0 1 0 Both
0 0 1 1 Service not activated
Note: For Service_type SRD and CSRD the Role_in_service is
identical for Responder
Figure 22. LSAP Status User Data
Page 136
PROFIBUS-Specification-Normative-Parts-4:1997
Copyright by PNO 1997 - all rights reserved
4.8 Transmission Procedures
Permissible frame sequences (message cycles) are described in the following. Er-
ror sequences, broadcast/multicast messages and "Send Data with No Acknowledge"
are excluded.
+--/ /--+----+----+----+----+----+----+
! SYN !SD1 ! DA ! SA ! FC !FCS ! ED !
+--/ /--+----+----+----+----+----+----+
!
!
!
______________________________________!
!
V
+----+
! SC ! Short Acknowledgement (E5H) positive (ACK) or
+----+ negative (no Response Data)
or
+----+----+----+----+----+----+
!SD1 ! DA ! SA ! FC !FCS ! ED ! Acknowledgement
+----+----+----+----+----+----+ (positive/negative)
or Response Frame:
+----+----+----+----+-----------+----+----+
!SD3 ! DA ! SA ! FC ! DATA_UNIT !FCS ! ED ! fixed length
+----+----+----+----+-----------+----+----+
or
+----+----+----+----+----+----+----+-------/ /-----+----+----+
!SD2 ! LE ! LEr!SD2 ! DA ! SA ! FC ! DATA_UNIT !FCS ! ED !
+----+----+----+----+----+----+----+------/ /------+----+----+
variable length
Figure 23. Send/Request Frame of fixed Length with no Data
Page 137
PROFIBUS-Specification-Normative-Parts-4:1997
Copyright by PNO 1997 - all rights reserved
+-/ /-+----+----+----+
! SYN !SD4 ! DA ! SA ! Token
+-/ /-+----+----+----+
!
_____________________!
!
!
V
+-/ /-+----+----+----+----+--------------+----+----+
! SYN !SD3 ! DA ! SA ! FC ! DATA_UNIT !FCS ! ED ! fixed length
+-/ /-+----+----+----+----+--------------+----+----+
!
!
!
___________________________________________________!
!
V
+-----+
! SC ! Short Acknowledgement (E5H) positive or negative
+-----+ (no Response Data)
or
+----+----+----+----+----+----+
!SD1 ! DA ! SA ! FC !FCS ! ED ! Acknowledgement
+----+----+----+----+----+----+ (positive/negative)
or Response Frame:
+----+----+----+----+--------------------+----+----+
!SD3 ! DA ! SA ! FC ! DATA_UNIT !FCS ! ED ! fixed length
+----+----+----+----+--------------------+----+----+
or
+----+----+----+----+----+----+----+-----/ /-----+----+----+
!SD2 ! LE ! LEr!SD2 ! DA ! SA ! FC ! DATA_UNIT !FCS ! ED !
+----+----+----+----+----+----+----+-----/ /-----+----+----+
variable length
!
!
___________________________________________________________!
!
!
V
+-/ /-+----+----+----+
! SYN !SD4 ! DA ! SA ! Token
+-/ /-+----+----+----+
Figure 24. Token Frame and Send/Request Frame of fixed Length with Data
including Address Extension
Page 138
PROFIBUS-Specification-Normative-Parts-4:1997
Copyright by PNO 1997 - all rights reserved
+-//-+----+----+----+----+----+----+----+-----/ /-----+----+----+
!SYN !SD2 ! LE ! LEr!SD2 ! DA ! SA ! FC ! DATA_UNIT !FCS ! ED !
+-//-+----+----+----+----+----+----+----+-----/ /-----+----+----+
!
!
________________________________________________________________!
!
V
+-----+
! SC ! Short Acknowledgement (E5H) positive or negative
+-----+ (no Response Data)
or
+----+----+----+----+----+----+
!SD1 ! DA ! SA ! FC !FCS ! ED ! Acknowledgement
+----+----+----+----+----+----+ (positive/negative)
or Response Frame:
+----+----+----+----+-----------+----+----+
!SD3 ! DA ! SA ! FC ! DATA_UNIT !FCS ! ED ! fixed length
+----+----+----+----+-----------+----+----+
or
+----+----+----+----+----+----+----+-----/ /-----+----+----+
!SD2 ! LE ! LEr!SD2 ! DA ! SA ! FC ! DATA_UNIT !FCS ! ED !
+----+----+----+----+----+----+----+-----/ /-----+----+----+
variable length
Figure 25. Send/Request Frame with variable Data Field Length
Page 139
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
PROFIBUS Specification - Normative Parts
Part 5
Application Layer Service Definition
Page 140
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
CONTENTS
Page
1 Scope.............................................................. 146
2 Normative References and additional Material....................... 146
3 General............................................................ 147
3.1 Terms and Apprevations............................................. 147
3.2 Architecture and Placement in the ISO/OSI Layer Model.............. 150
3.2.1 Application Layer.................................................. 151
3.2.1.1 Fieldbus Message Specification (FMS)............................... 151
3.2.1.2 Lower Layer Interface (LLI)........................................ 151
3.2.2 Fieldbus Management Layer 7 (FMA7)................................. 151
3.3 PROFIBUS Communication Model (FMS)................................. 151
3.3.1 Relationship between Application Process and Communication......... 153
3.3.1.1 Fieldbus Message Specification (FMS) Services...................... 154
3.3.1.2 Virtual Fieldbus Device (VFD) Model................................ 155
3.3.2 Relationship between Client and Server............................. 155
3.3.2.1 Service Primitives................................................. 156
3.3.2.2 Service Sequences.................................................. 157
3.3.2.3 Parallel Services.................................................. 158
3.3.2.4 Mutual Services.................................................... 158
3.3.3 Communication Relationships between Applications................... 159
3.3.3.1 Communication Relationship between Master and Master as well as
Master and Slave................................................... 159
3.3.3.2 Types of Communication Relationships............................... 160
3.3.3.3 Communication Relationship List (CRL).............................. 162
3.3.4 Communication Objects.............................................. 163
3.3.4.1 Static and dynamic Communication Objects........................... 163
3.3.4.2 Object Addressing.................................................. 164
3.3.5 Object Description Model of Communication.......................... 165
3.3.5.1 Description........................................................ 166
3.3.6 Protection Mechanisms.............................................. 167
3.4 Model of Fieldbus Management Layer 7 (FMA7)........................ 167
3.4.1 Local Management................................................... 168
3.4.2 Remote Management.................................................. 168
3.4.3 Default Management Connection...................................... 168