Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 611
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
Connection Establishment and Release
Current State Transition Next State
Event
\Exit Condition
=> Action Taken
CON-ESTABLISHING-CALLED 21 CONNECTION-ESTABLISHED
FMA7 Initiate.res(+) received from FMA7 user
=> send FMA7_INITIATE_RES_PDU, (ASS.res(+)) to LLI
CON-ESTABLISHING-CALLED 22 CONNECTION-NOT-ESTABLISHED
FMA7 Initiate.res(-) received from FMA7 user
=> send FMA7_INITIATE_ERROR_PDU, (ASS.res(-)) to LLI
reset CREF
CON-ESTABLISHING-CALLED 23 CONNECTION-NOT-ESTABLISHED
FMA7 Abort.req received from FMA7 user
=> ABT.req to LLI <reason code as given by user>
reset CREF
CON-ESTABLISHING-CALLED 24 CONNECTION-NOT-ESTABLISHED
ABT.ind received from LLI
=> FMA7 Abort.ind to FMA7 user <reason code
out of ABT.ind>, reset CREF
CON-ESTABLISHING-CALLED 25 CONNECTION-NOT-ESTABLISHED
unknown or faulty service primitive received from LLI
=> ABT.req to LLI <reason code = ABT_RC5>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC5>
reset CREF
CON-ESTABLISHING-CALLED 26 CONNECTION-NOT-ESTABLISHED
unallowed LLI service primitive received from LLI
=> ABT.req to LLI <reason code = ABT_RC4>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC4>
reset CREF
CON-ESTABLISHING-CALLED 27 CONNECTION-NOT-ESTABLISHED
unknown, unallowed or faulty service primitive
received from FMA7 user
=> ABT.req to LLI <reason code = ABT_RC2>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC2>
reset CREF
CONNECTION-ESTABLISHED 28 CONNECTION-ESTABLISHED
FMA7 service Rem.req received from FMA7 user
\outstanding FMA7 service counter req= 0
AND PDU length • max FMA7 PDU sending low prio
AND FMA7 services supported test(Client) positive
=> FMA7_SERVICE_REQ_PDU with DTC.req to LLI
outstanding FMA7 service counter req := 1
CONNECTION-ESTABLISHED 29 CONNECTION-NOT_ESTABLISHED
FMA7 service Rem.req received from FMA7 user
\outstanding FMA7 service counter req • 1
=> ABT.req to LLI <reason code = ABT_RC9>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC9>
reset CREF
Page 612
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
Connection Establishment and Release
Current State Transition Next State
Event
\Exit Condition
=> Action Taken
CONNECTION-ESTABLISHED 30 CONNECTION-NOT_ESTABLISHED
FMA7 service Rem.req received from FMA7 user
\outstanding FMA7 service counter req = 0
AND PDU length > max FMA7 PDU sending low prio
=> ABT.req to LLI <reason code = ABT_RC6>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC6>
reset CREF
CONNECTION-ESTABLISHED 31 CONNECTION-NOT_ESTABLISHED
FMA7 service Rem.req received from FMA7 user received
\outstanding FMA7 service counter req = 0
AND PDU length ≤ max FMA7 PDU sending low prio
AND FMA7 services supported test (Client) negative
=> ABT.req to LLI <reason code = ABT_RC7>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC7>
reset CREF
CONNECTION-ESTABLISHED 32 CONNECTION-NOT-ESTABLISHED
FMA7 Abort.req received from FMA7 user received
=> ABT.req to LLI <reason code as given by user>
reset CREF
CONNECTION-ESTABLISHED 33 CONNECTION-NOT-ESTABLISHED
unknown, faulty or unallowed service primitive
received from FMA7 user
=> ABT.req to LLI <reason code = ABT_RC2>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC2>
reset CREF
CONNECTION-ESTABLISHED 34 CONNECTION-ESTABLISHED
FMA7_SERVICE_REQ_PDU (DTC.ind) received from LLI
\PDU length • max FMA7 PDU receiving low prio
AND outstanding FMA7 service counter res = 0
AND FMA7 services supported test (Server) positive
=> FMA7 service Rem.ind to FMA7 user
outstanding FMA7 service counter res := 1
CONNECTION-ESTABLISHED 35 CONNECTION-NOT-ESTABLISHED
FMA7_SERVICE_REQ_PDU (DTC.ind) received from LLI
\PDU length > max FMA7 PDU receiving low prio
=> ABT.req to LLI <reason code = ABT_RC6>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC6>
reset CREF
CONNECTION-ESTABLISHED 36 CONNECTION-NOT-ESTABLISHED
FMA7_SERVICE_REQ_PDU (DTC.ind) received from LLI
\PDU length • max FMA7 PDU receiving low prio
AND outstanding FMA7 service counter res ≥ 1
=> ABT.req to LLI <reason code = ABT_RC9>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC9>
reset CREF
Page 613
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
Connection Establishment and Release
Current State Transition Next State
Event
\Exit Condition
=> Action Taken
CONNECTION-ESTABLISHED 37 CONNECTION-NOT-ESTABLISHED
FMA7_SERVICE_REQ_PDU (DTC.ind) received from LLI
\PDU length • max FMA7 PDU receiving low prio
AND outstanding FMA7 service counter res = 0
AND FMA7 services supported test (Server) negative
=> ABT.req to LLI <reason code = ABT_RC7>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC7>
reset CREF
CONNECTION-ESTABLISHED 38 CONNECTION-NOT-ESTABLISHED
ABT.ind received from LLI
=> FMA7 Abort.ind to FMA7 user <reason code
out of ABT.ind>
reset CREF
CONNECTION-ESTABLISHED 39 CONNECTION-NOT-ESTABLISHED
FMA7_INITIATE_REQ_PDU (ASS.ind) received from LLI
=> ABT.req to LLI <reason code = ABT_RC10>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC10>
reset CREF
CONNECTION-ESTABLISHED 40 CONNECTION-NOT-ESTABLISHED
unknown or faulty service primitive received from LLI
=> ABT.req to LLI <reason code = ABT_RC5>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC5>
reset CREF
CONNECTION-ESTABLISHED 41 CONNECTION-NOT-ESTABLISHED
unallowed LLI service primitive received from LLI
=> ABT.req to LLI <reason code = ABT_RC4>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC4>
reset CREF
CONNECTION-ESTABLISHED 42 CONNECTION-NOT-ESTABLISHED
unknown, unallowed or faulty FMA7 PDU (DTC.ind/
DTC.con/ASS.ind) received from LLI received
=> ABT.req to LLI <reason code = ABT_RC3>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC3>
reset CREF
CONNECTION-ESTABLISHED 43 CONNECTION-ESTABLISHED
FMA7 service Rem.res received from FMA7 user
\outstanding FMA7 service counter res =1
AND service of .res is identical with
service of .ind
AND PDU length • max FMA7 PDU sending low prio
=> FMA7_SERVICE_RES_PDU with DTC.res to LLI
outstanding FMA7 service counter res := 0
CONNECTION-ESTABLISHED 44 CONNECTION-NOT-ESTABLISHED
FMA7 service Rem.res received from FMA7 user
\outstanding FMA7 service counter res = 0
=> ABT.req to LLI <reason code = ABT_RC8>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC8>
reset CREF
Page 614
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
Connection Establishment and Release
Current State Transition Next State
Event
\Exit Condition
=> Action Taken
CONNECTION-ESTABLISHED 45 CONNECTION-NOT-ESTABLISHED
FMA7 service Rem.res received from FMA7 user
\outstanding FMA7 service counter res = 1
AND service of .res is not identical with
service of .ind
=> ABT.req to LLI <reason code = ABT_RC11>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC11>
reset CREF
CONNECTION-ESTABLISHED 46 CONNECTION-NOT-ESTABLISHED
FMA7 service Rem.res received from FMA7 user
\outstanding FMA7 service counter res = 1
AND service of .res is identical with
service of .ind
AND PDU length > max FMA7 PDU sending low prio
=> ABT.req to LLI <reason code = ABT_RC6>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC6>
reset CREF
CONNECTION-ESTABLISHED 47 CONNECTION-ESTABLISHED
FMA7_SERVICE_RES_PDU (DTC.con) received from LLI
\PDU length ≤ max FMA7 PDU receiving low prio
AND outstanding FMA7 service counter req = 1
AND service of .con is identical with
service of .req
=> FMA7 service Rem.con to FMA7 user
outstanding FMA7 service counter req := 0
CONNECTION-ESTABLISHED 48 CONNECTION-NOT-ESTABLISHED
FMA7_SERVICE_RES_PDU (DTC.con) received from LLI
\PDU length> max FMA7 PDU receiving low prio
=> ABT.req to LLI <reason code = ABT_RC6>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC6>
reset CREF
CONNECTION-ESTABLISHED 49 CONNECTION-NOT-ESTABLISHED
FMA7_SERVICE_RES_PDU (DTC.con) received from LLI
\PDU length • max FMA7 PDU receiving low prio
AND outstanding FMA7 service counter req = 0
=> ABT.req to LLI <reason code = ABT_RC8>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC8>
reset CREF
CONNECTION-ESTABLISHED 50 CONNECTION-NOT-ESTABLISHED
FMA7_SERVICE_RES_PDU (DTC.con) received from LLI
\PDU length • max FMA7 PDU receiving low prio
AND outstanding FMA7 service counter req >= 1
AND service of .con is identical with
service of .req
=> ABT.req to LLI <reason code = ABT_RC11>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC11>
reset CREF
Page 615
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
4.5 Configuration Management
4.5.1 CRL Management
4.5.1.1 Model Description
The CRL management services are required to read and write the CRL of the
PROFIBUS stations. For writing, FMA7 divides a complete CRL entry into the FMS
or the FMA7 CRL entry and the LLI CRL entry and loads the parts into the corre-
sponding instances. For reading, FMA7 combines the FMS or the FMA7 CRL entry and
the LLI CRL entry to a complete CRL entry and delivers this to the FMA7 user.
4.5.1.2 The CRL Object
The CRL contains the description of all communication relation-ships of a device
independent of the time of use. The CRL contains one CRL header and one CRL en-
try for each configured communication relationship. The CRL header and every CRL
entry are addressed by the communication reference (CREF). The entries of the
CRL shall be entered in ascending order without gaps. Every CRL entry contains
the complete description of the corresponding communication relationship.
+--------------------------------+
! CRL Header !
+--------------------------------+
! CRL Entry !
+--------------------------------+
: ... :
+--------------------------------+
! CRL Entry !
+--------------------------------+
Figure 8. Structure of the CRL
The CRL Header Object
Information about the structure of the CRL is entered in the CRL header. The CRL
header is entered under the communication reference 0.
+------+-------------+-----------+--------+-------+------------+
! CREF ! Number of ! Poll LIST !ASS/ABT !Symbol !VFD Pointer !
! (=0) ! CRL Entries ! SSAP ! CI !Length ! Supported !
+------+-------------+-----------+--------+-------+------------+
Figure 9. Structure of the CRL Header
Communication Reference
The CRL header is addressed with the communication reference = 0.
Number of CRL Entries
Specifies the number of entries in the CRL additional to the CRL header.
Poll List SSAP
Specifies the local Service Access Point which contains the Poll List of Layer
2.
Valid values
(0, 2..62) - SAP values
(128) - NIL
(255) - No Poll List SSAP used in current CRL
Page 616
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
ASS/ABT CI
Contains the length of the time interval for the control of the connection es-
tablishment and the connection release. The value of ASS/ABT CI shall be multi-
plied by 10 ms to determine the control interval for the idle control.
Range of values: 0 ms to 10
.
(2**32 - 1) ms.
Symbol Length
This attribute specifies the length of symbols in the CRL and may only take the
values 0 to 32. If this attribute has the value 0, then the attribute "Symbol"
does not exist in the CRL entry.
VFD Pointer Supported
This attribute specifies whether several VFDs are supported in the CRL.
FALSE - Only one VFD is supported.
TRUE - Several VFDs are supported.
The CRL Entry Object
Every CRL entry is addressed by the communication reference. Every CRL entry
consists of a static and a dynamic part. The static part consists of 20 attrib-
utes and contains the complete description of the associated communication rela-
tionship. Only this part is loaded and therefore configured. The optional User
Extension can only be loaded and read remotely and contains CREF related con-
figuration information for the FMA7-user.
The dynamic part of a CRL entry consists of 8 attributes and can be optionally
transferred in addition to the static part when the CRL is read.
+--------------------+---------------------+
! CRL entry static ! CRL entry dynamic !
+--------------------+---------------------+
Figure 10. Structure of a CRL Entry
Page 617
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
+======+========================================+===+==//==+===+
! ! Communication Reference (CREF) ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Local LSAP ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Remote Address ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Remote LSAP ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Type ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! LLI SAP ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Connection Attribute ! ! ! !
! +----------------------------------------+---+--//--!---!
! S ! max SCC ! ! ! !
! +----------------------------------------+---+--//--!---!
! T ! max RCC ! ! ! !
! +----------------------------------------+---+--//--!---!
! A ! max SAC ! ! ! !
! +----------------------------------------+---+--//--!---!
! T ! max RAC ! ! ! !
! +----------------------------------------+---+--//--!---!
! I ! CI ! ! ! !
! +----------------------------------------+---+--//--!---!
! C ! Multiplier ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Max PDU Sending High Prio ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Max PDU Sending Low Prio ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Max PDU Receiving High Prio ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Max PDU Receiving Low Prio ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Services Supported ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! Symbol ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! VFD Pointer ! ! ! !
! +----------------------------------------+---+--//--!---!
! ! User Extension (optional) ! ! ! !
+======+========================================+===+==//==+===+
Figure 11. Structure of a static CRL Entry
Page 618
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
+======+========================================+===+==//==+===+
! ! Status ! ! ! !
! D +----------------------------------------+---+--//--!---!
! Y ! Actual Remote Address ! ! ! !
! N +----------------------------------------+---+--//--!---!
! A ! Actual Remote LSAP ! ! ! !
! M +----------------------------------------+---+--//--!---!
! I ! SCC ! ! ! !
! C +----------------------------------------+---+--//--!---!
! ! RCC ! ! ! !
! O +----------------------------------------+---+--//--!---!
! P ! SAC ! ! ! !
! T +----------------------------------------+---+--//--!---!
! I ! RAC ! ! ! !
! O +----------------------------------------+---+--//--!---!
! N. ! Poll Entry Enabled ! ! ! !
+======+========================================+===+==//==+===+
Figure 12. Structure of a dynamic CRL Entry
The range of values is specified by FMS, LLI or Layers 1/2, if not given here.
Description of the attributes for the static part of a CRL entry:
Communication Reference
The communication reference is a locally unique identifier of the communication
relationship.
Local LSAP
Specifies the local Service Access Point which is used for this communication
relationship.
Valid values
(0..63) - SAP values
(128) - NIL
Remote Address
Specifies the FDL address of the remote station for this communication relation-
ship.
Valid values
(0..127) - station address
(255) - ALL
Remote LSAP
Specifies the Service Access Point of the remote station which is used for this
communication relationship.
Valid values
(0..63) - SAP values
(128) - NIL
(255) - ALL
Type
Specifies the type of this communication relationship.
Valid values
( 0) - MMAC master-master connection for acyclic data transfer
( 1) - MSAC master-slave connection for acyclic data transfer with
no slave initiative
Page 619
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
( 5) - MSAC_SI master-slave connection for acyclic data
transfer with slave initiative
( 3) - MSCY master-slave connection for cyclic data
transfer with no slave initiative
( 7) - MSCY_SI master-slave connection for cyclic data
transfer with slave initiative
( 8) - BRCT broadcast communication relationship
(10) - MULT multicast communication relationship
LLI SAP
This attribute specifies the configured LLI user for this communication rela-
tionship.
Valid values
(0) - FMS
(1) - FMA7
Connection Attribute
Contains further information on the connection type for connection-oriented com-
munication relationships.
Valid values
(0) - D defined connection (master-master or master-slave connection)
(1) - I open connection at the requester (master-master connection)
(2) - O open connection at the responder (master-master or master-slave connec-
tion)
max SCC (maximum value Send Confirmed Request Counter)
This attribute specifies the maximum permitted number of parallel confirmed
services to the communication partner. The attribute Outstanding Services Client
in the FMS CRL shall be set equal to this attribute in case of a connection for
acyclic data transfer. In case of a connection for cyclic data transfer the FMA7
shall assign the value 1 to the attribute Outstanding Services Client in the FMS
CRL.
max RCC (maximum value Receive Confirmed Request Counter)
This attribute specifies the maximum permitted number of parallel confirmed
services from the communication partner. The attribute Outstanding Services
Server in the FMS CRL shall be set equal to this attribute in case of a connec-
tion for acyclic data transfer. In case of a connection for cyclic data transfer
the FMA7 shall assign the value 1 to the attribute Outstanding Services Server
in the FMS CRL.
max SAC (maximum value Send Acknowledged Request Counter)
This attribute specifies the maximum permitted number of parallel unconfirmed
services to the communication partner.
max RAC (maximum value Receive Acknowledged Request Counter)
This attribute specifies the maximum permitted number of parallel unconfirmed
services from the communication partner.
CI (Control Interval)
This attribute specifies the length of the time interval for the connection con-
trol on connection-oriented communication relationships. The value of CI shall
be multiplied by 10 ms to determine the control interval. For connections for
acyclic data transfer it includes the interval of the idle control (ACI) and for
connections for cyclic data transfer the interval of the connection control
(CCI). Range of values: 0 ms to 10
.
(2**32 - 1) ms.
Page 620
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
Multiplier
This attribute specifies for connections for cyclic data transfer on the master
side how often the Layer 2 address of this communication relationship shall be
entered into the poll list. Thereby the poll interval may be shortened.
Max PDU Sending High Prio
This attribute contains the maximum permissible length of a FMS PDU for sending
with high priority which may be handled on this communication relationship.
Max PDU Sending Low Prio
This attribute contains the maximum permissible length of a FMS PDU for sending
with low priority which may be handled on this communication relationship.
Max PDU Receiving High Prio
This attribute contains the maximum permissible length of a FMS PDU for receiv-
ing with high priority which may be handled on this communication relationship.
Max PDU Receiving Low Prio
This attribute contains the maximum permissible length of a FMS PDU for receiv-
ing with low priority which may be handled on this communication relationship.
Services Supported
This attribute contains the content of FMA7 Services Supported in the case of a
management connection. In the case of a FMS connection, this attribute contains
the content of FMS Features Supported.
- FMS Features Supported
This attribute specifies which FMS services and options are supported on this
communication relationship. Two bits for each of the services are used to
specify the supported service primitives. Two bits for each of the options
are used to specify for which service primitives these options are allowed.
- FMA7 Services Supported
This attribute specifies which FMA7 services may be executed on this communica-
tion relationship. Two bits for each of the services are used to specify the
supported service primitives.
Symbol
This attribute contains the symbolic name of the communication relationship. The
length shall be fixed as specified by the attribute Symbol Length in the CRL
header.
VFD Pointer
This pointer shall refer to the associated VFD. If a VFD pointer is not sup-
ported in the current CRL, as indicated in the CRL header, then the value of
this attribute is irrelevant.
User Extension (optional)
This optional attribute contains CREF related configuration information for the
FMA7-user. It can only be transfered remotly and contains one or more Parameter-
Octets, each in conjunction with 1 or more data octets. The Parameter-Octet is
coded as follows:
+---------------+
!F!P!P!P!P!P!L!L!
+---------------+
F: Flag
This bit shall be set equal „1“ for the first Parameter-Octet of the User Exten-
sion and equal „0“ in case of following Parameter-Octets.