Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 601
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
Communication Reference
The communication reference is a locally unique identifier for the communication
relationship.
Max FMA7 PDU Sending Low Prio
This attribute contains the maximum possible length of the FMA7 PDU for sending
with low priority which shall be handled on this communication relationship.
Max FMA7 PDU Receiving Low Prio
This attribute contains the maximum possible length of the FMA7 PDU for receiv-
ing with low priority which shall be handled on this communication relationship.
FMA7 Services Supported
This attribute gives information about which optional FMA7 services may be exe-
cuted on this communication relationship. Two bits for every optional remote
FMA7 service (service group) are used in a bit string to specify whether these
services are supported as a request or as a response, respectively. If the cor-
responding bit is set, the services are supported as a request or as a response,
respectively.
Table 1. Attribute FMA7 Services Supported
+---------------------------------+--------------+--------------+
! Service ! Primitive ! Primitive !
! ! bit[n] ! bit[m] !
+---------------------------------+--------------+--------------+
! reserved *) ! .req,.con 0 ! .ind,.res 8 !
! InitiateLoad-CRL-Rem ! .req,.con 1 ! .ind,.res 9 !
! Load-CRL-Rem, ! .req,.con " ! .ind,.res " !
! TerminateLoad-CRL-Rem ! .req,.con " ! .ind,.res " !
! Read-CRL-Rem ! .req,.con 2 ! .ind,.res 10 !
! SetValueRem ! .req,.con 3 ! .ind,.res 11 !
! ReadValueRem ! .req,.con 4 ! .ind,.res 12 !
! LSAP-StatusRem ! .req,.con 5 ! .ind,.res 13 !
! IdentRem ! .req,.con 6 ! .ind,.res 14 !
! reserved *) ! .req,.con 7 ! .ind,.res 15 !
! reserved *) ! 16 to 31 ! 32 to 47 !
+---------------------------------+-----------------------------+
! Explanation: !
! *) reserved bits shall be set to 0 !
! n = 0 to 7, 16 to 31 !
! m = 8 to 15, 32 to 47 !
+---------------------------------------------------------------+
Symbol
The symbolic name of the communication reference. The existence and the length
are specified in the CRL header.
CREL State
This attribute contains the state of the communication relation-ship.
The following states are permissible:
- CONNECTION-NOT-ESTABLISHED
- CONNECTION-ESTABLISHING (CALLING)
- CONNECTION-ESTABLISHING (CALLED)
- CONNECTION-ESTABLISHED
Outstanding FMA7 Services Counter Req
This attribute specifies how many confirmed services (remote FMA7 services) are
currently pending at the requester on this communication relationship.
Page 602
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
Outstanding FMA7 Services Counter Res
This attribute specifies how many outstanding confirmed services (remote FMA7
services) are being handled at the responder on this communication relationship.
Attributes
Object: FMA7 Communication Relationship List
Key Attribute: implicit
Attribute: FMA7 CRL Header
Attribute: List of FMA7 CRL Entry
Attribute: CRL Loader State
Attribute: CRL Upload State
Object: FMA7 CRL Header
Key Attribute: Communication Reference
Attribute: Number of FMA7 CRL Entries
Attribute: Symbol Length
Object: FMA7 CRL Entry
Key Attribute: Communication Reference
Attribute: Max FMA7 PDU Sending Low Prio
Attribute: Max FMA7 PDU Receiving Low Prio
Attribute: FMA7 Services Supported
Attribute: Symbol
Attribute: CREL State
Attribute: Outstanding FMA7 Services Counter Req
Attribute: Outstanding FMA7 Services Counter Res
Page 603
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
4.4.3 Services
4.4.3.1 FMA7 Initiate
The FMA7 user shall use the FMA7 Initiate service to establish a management con-
nection.
Table 2. FMA7 Initiate Service
+--------------------------------------+-----+-----+-----+-----+
! ! ! ! ! !
! Parameter Name !.req !.ind !.res !.con !
! ! ! ! ! !
+--------------------------------------+-----+-----+-----+-----+
! Argument ! M ! M= ! ! !
! Communication Reference ! M ! M ! ! !
! Max FMA7 PDU Sending Low Prio *) ! ! ! ! !
! Max FMA7 PDU Receiving Low Prio *) ! ! ! ! !
! FMA7 Services Supported *) ! ! ! ! !
! ! ! ! ! !
! Result(+) ! ! ! S ! S= !
! Communication Reference ! ! ! M ! M !
! ! ! ! ! !
! Result(-) ! ! ! S ! S= !
! Communication Reference ! ! ! M ! M= !
! Error Code ! ! ! M ! M !
! Max FMA7 PDU Sending Low Prio **) ! ! ! ! M !
! Max FMA7 PDU Receiving Low Prio **)! ! ! ! M !
! FMA7 Services Supported **) ! ! ! ! M !
+--------------------------------------+-----+-----+-----+-----+
! Explanation: !
! *) Calling !
! **) Called !
+--------------------------------------------------------------+
Argument
The argument contains the parameters of the FMA7 Initiate.req primitive and the
FMA7 Initiate.ind primitive.
Communication Reference
This parameter specifies the identifier of the associated management connection
in the CRL.
Max FMA7 PDU Sending Low Prio (Calling)
This parameter contains the maximum permissible length of the FMA7 PDU for send-
ing with low priority which shall be handled on this communication relationship.
It is transmitted by the calling FMA7 and is not a part of the interface primi-
tives.
Max FMA7 PDU Receiving Low Prio (Calling)
This parameter contains the maximum permissible length of the FMA7 PDU for re-
ceiving with low priority which shall be handled on this communication relation-
ship. It is transmitted by the calling FMA7 and is not a part of the interface
primitives.
FMA7 Services Supported (Calling)
This parameter specifies which FMA7 services may be executed by the client (see
FMA7 CRL). It is transmitted by the calling FMA7 and is not a part of the inter-
face primitives.
Result(+)
The Result(+) parameter indicates that the Initiate service was executed suc-
Page 604
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
cessfully.
Result(-)
The Result(-) parameter indicates that the Initiate service failed.
Error Code
This parameter contains information about the reason the service failed.
- Other
The error code could not be assigned to any of the error codes specified
below.
- Max PDU Size Insufficient
The specified maximum PDU length is not sufficient for the requested commu-
nication.
- Service Not Supported
The requested service is not supported by the server.
- User Initiate Denied
The FMA7 user rejects the FMA7 Initiate.
Max FMA7 PDU Sending Low Prio (Called)
This parameter contains the maximum permissible length of the FMA7 PDU for send-
ing with low priority which shall be handled on this communication relationship.
It is transmitted by the called FMA7 and is a part only of the interface primi-
tive initiate.con.
Max FMA7 PDU Receiving Low Prio (Called)
This parameter contains the maximum permissible length of the FMA7 PDU for re-
ceiving with low priority which shall be handled on this communication relation-
ship. It is transmitted by the called FMA7 and is a part only of the interface
primitive initiate.con.
FMA7 Services Supported (Called)
This parameter specifies which FMA7 services may be executed by the server (see
FMA7 CRL). It is not a part of the interface primitive initiate.res.
4.4.3.2 FMA7 Abort
The FMA7 user shall use this service to release an existing connection.
Table 3. FMA7 Abort Service
+---------------------------------+-----+-----+
! ! ! !
! Parameter Name !.req !.ind !
! ! ! !
+---------------------------------+-----+-----+
! Argument ! M ! M !
! Communication Reference ! M ! M !
! Locally Generated ! ! M !
! Abort Identifier ! M ! M= !
! Reason Code ! M ! M= !
! Abort Detail ! U ! C !
+---------------------------------------------+
Argument
The argument contains the parameters of the FMA7 Abort.req primitive and the
FMA7 Abort.ind primitive.
Communication Reference
This parameter specifies the identifier of the associated management connection
in the CRL.
Page 605
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
Locally Generated
This parameter indicates whether the abort was initiated locally or by the com-
munication partner.
TRUE - The abort was initiated locally.
FALSE - The abort was initiated remotely.
Abort Identifier
This parameter indicates where the reason for the connection abort was identi-
fied.
Valid values
- User
- LLI User ( FMA7 )
- LLI
- Layer 2
Reason Code
This parameter specifies the reason for the connection abort.
If the parameter Abort Identifier has the value LLI or Layer 2, then the parame-
ter Reason Code is generated in LLI and shall be found in the description of
LLI.
If the parameter Abort Identifier has the value User, the following value is
specified:
- ABT_RC1 <=> DISCONNECT
User releases the connection
If the parameter Abort Identifier has the value FMA7, the following values are
specified:
- ABT_RC1 <=> FMA7-CRL-Error
FMA7 CRL Entry incorrect
- ABT_RC2 <=> User Error
Invalid, unknown or faulty service primitive received by the FMA7 user
- ABT_RC3 <=> FMA7-PDU-Error
Invalid or unknown FMA7 PDU received by LLI
- ABT_RC4 <=> Connection-State-Conflict-LLI
Invalid LLI service primitive
- ABT_RC5 <=> LLI-Error
Faulty or unknown LLI service primitive
- ABT_RC6 <=> PDU-Size
PDU length > maximum PDU length
- ABT_RC7 <=> FMA7-Service-Not-Supported
FMA7 service.req received by the FMA7 user and the service is not supported as
client
or
FMA7_SERVICE_REQ_PDU received by LLI and the service is not supported as ser-
ver
(see attribute FMA7 Services Supported of the FMA7 CRL)
- ABT_RC8 <=> Response-Error
FMA7 service.res received by the FMA7 user and Outstanding FMA7 Service Coun-
ter Res = 0
or
Page 606
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
FMA7-SERVICE_RES_PDU received by LLI and Outstanding FMA7 Service Counter Req
= 0
- ABT_RC9 <=> Max-Services-Overflow
Number of allowed parallel services exceeded
- ABT_RC10 <=> Connection-State-Conflict-FMA7
FMA7-INITIATE_REQ_PDU received by LLI
- ABT_RC11 <=> Service-Error
The service in the response does not correspond to the service in the indica-
tion.
or
The service in the confirmation does not correspond to the service in the re-
quest.
- ABT_RC12 <=> Loading CRL
The CRL is currently loaded.
If the parameter Abort Identifier has the value LLI or Layer 2, the Reason Code
is generated in LLI.
The coding of the Abort_PDU is specified in LLI.
Page 607
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
4.4.4 Context Test in FMA7
Upon receiving a FMA7_INITIATE_REQ_PDU the FMA7 of the responder tests the FMA7
context of the communication partner (remote context) for compatibility to its
own FMA7 context (local context) for this connection entered in the CRL. The lo-
cal FMA7 context is assumed to be correctly configured. The compatibility of the
FMA7 contexts may be deduced from the following matrix (see Fig. 196). For pa-
rameters of different meaning (e.g. the FMA7 Services Supported parameter in the
local context and the FMA7 Outstanding Services Parameter in the remote context)
a test is not required. The corresponding entries in the matrix remain empty.
+---------------------------+----------------------------------+
! ! Local Context FMA7 !
! +----------------------------------+
! ! Max FMA7 PDU ! FMA7 !
! Remote ! Sending ! Receiving ! Services !
! Context ! Low Prio ! Low Prio ! Supported!
! FMA7 ! ! !.req .res !
! ! ! ! [n] [m] !
! !.req,.res !.ind,.con ! 0 1 0 1 !
+===========================+===========+===========+==========+
! Max FMA7 ! ! ! ! !
! PDU Sending !.req,.res! ! • ! !
! Low Prio ! ! ! ! !
! !---------+-----------+-----------+ !
! Max FMA7 ! ! ! ! !
! PDU Receiving !.ind,.con! • ! ! !
! Low Prio ! ! ! ! !
+-----------+---------------+-----------+-----------+----------+
! FMA7 .req [n] 0 ! ! X X !
! Services .req [n] 1 ! ! - X !
! Supported .res [m] 0 ! ! X - !
! .res [m] 1 ! ! X X !
+---------------------------+-----------------------+----------+
! Explanation: !
! X : compatible !
! - : not compatible (Error case) !
! • : local value smaller than or equal to remote value !
! • : local value larger than or equal to remote value !
!.req 0 : Service was not supported as requester !
!.req 1 : Service was supported as requester !
!.res 0 : Service was not supported as responder !
!.res 1 : Service was supported as responder !
! [n] : 0 to 7, 16 to 23 !
! [m] : 8 to 15, 24 to 47 !
+--------------------------------------------------------------+
Figure 6. Compatibility of the local FMA7 Context to the remote FMA7 Context
4.4.5 State Machine of a Management Connection
4.4.5.1 State Machine Description
CONNECTION-NOT-ESTABLISHED
No FMA7 context is established. Only the service primitives FMA7 Initiate.req,
ASS.ind, FMA7 Abort.req and ABT.ind are permitted. All other services are re-
jected.
Page 608
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
CONNECTION-ESTABLISHING (CALLING)
The local FMA7 user wishes to establish a connection. Only the service primi-
tives ASS.con(+), ASS.con(-), FMA7 Abort.req and ABT.ind are permitted. All
other services are rejected. In the following this state is abbreviated with
CON-ESTABLISHING-CALLING.
CONNECTION-ESTABLISHING (CALLED)
The remote FMA7 user wishes to establish a connection. Only the service primi-
tives FMA7 Initiate.res(+), FMA7 Initiate.res(-), ABT.ind and FMA7 Abort.req are
permitted. All other services are rejected. In the following this state is ab-
breviated with CON-ESTABLISHING-CALLED.
CONNECTION-ESTABLISHED
The communication relationship is established. The service primitives FMA7 Ini-
tiate.req, FMA7 Initiate.res(+), FMA7 Initiate.res(-) are not allowed and are
rejected. No parallel remote FMA7 services are allowed. Only the LLI service
primitives DTC.ind, DTC.con and ABT.ind are allowed. All other are rejected.
ASS.ind shall be rejected with the separate error message "Connection State Con-
flict FMA7".
2-8,10-12
+---+
! V
22-27 +------------------+ 14-20
+--------------->! CONNECTION- !<---------------+
! 9 ! NOT-ESTABLISHED ! 1 !
! +-------! !-------+ !
! ! +------------------+ ! !
! V ^ V !
+--------------+ ! +--------------+
! CON- ! ! 29-33,35-42, ! CON- !
! ESTABLISHING-! ! 44-46,48-50 ! ESTABLISHING-!
! CALLED ! ! ! CALLING !
+--------------+ ! +--------------+
! 21 +------------------+ 13 !
+----------->! CONNECTION- !<-----------+
! ESTABLISHED !
! !
+------------------+
! ^
+----------+
28,34,43,47
Figure 7. State Machine
For the reset of a communication reference (CREF reset) the following actions
shall be executed:
- clearing of memory content
- in the dynamic part of the FMA7 CRL the fields 'Outstanding FMA7 Service Coun-
ter Req' and 'Outstanding FMA7 Service Counter Res' are set to 0.
- the CREL State is set to 'CONNECTION-NOT-ESTABLISHED'
Page 609
PROFIBUS-Specification-Normative-Parts-7:1997
Copyright by PNO 1997 - all rights reserved
4.4.5.2 State Transitions
Connection Establishment and Release
Current State Transition Next State
Event
\Exit Condition
=> Action Taken
CONNECTION-NOT-ESTABLISHED 1 CON-ESTABLISHING-CALLING
FMA7 Initiate.req received from FMA7 user
\FMA7 CRL entry valid
=> send FMA_INITIATE_REQ_PDU, (ASS.req) to LLI
CONNECTION-NOT-ESTABLISHED 2 CONNECTION-NOT-ESTABLISHED
FMA7 Initiate.req received from FMA7 user
\FMA7 CRL entry invalid
=> FMA7 Abort.ind to FMA7 user <reason code = ABT_RC1>
CONNECTION-NOT-ESTABLISHED 3 CONNECTION-NOT-ESTABLISHED
FMA7 Abort.req received from FMA7 user
=> ignore
CONNECTION-NOT-ESTABLISHED 4 CONNECTION-NOT-ESTABLISHED
unknown, unallowed or faulty service
primitive received from FMA7 user
=> FMA7 Abort.ind to FMA7 user <reason code = ABT_RC2>
CONNECTION-NOT-ESTABLISHED 5 CONNECTION-NOT-ESTABLISHED
ABT.ind from LLI received
=> ignore
CONNECTION-NOT-ESTABLISHED 6 CONNECTION-NOT-ESTABLISHED
unknown or faulty service primitive received from LLI
=> ABT.req to LLI <reason code = ABT_RC5>
CONNECTION-NOT-ESTABLISHED 7 CONNECTION-NOT-ESTABLISHED
unknown or unallowed LLI service primitive
received from LLI
=> ABT.req to LLI <reason code = ABT_RC4>
CONNECTION-NOT-ESTABLISHED 8 CONNECTION-NOT-ESTABLISHED
not allowed or faulty FMA7 PDU (ASS.ind) received
=> ABT.req to LLI <reason code = ABT_RC3>
CONNECTION-NOT-ESTABLISHED 9 CON-ESTABLISHING-CALLED
FMA7_INITIATE_REQ_PDU(ASS.ind) received from LLI
\FMA7 CRL entry is valid
AND FMA7 context test positive
=> FMA7 Initiate.ind to FMA7 user
CONNECTION-NOT-ESTABLISHED 10 CONNECTION-NOT-ESTABLISHED
FMA7_INITIATE_REQ_PDU(ASS.ind) from LLI received
\FMA7 CRL entry is invalid
=> ABT.req to LLI <reason code = ABT_RC1>
CONNECTION-NOT-ESTABLISHED 11 CONNECTION-NOT-ESTABLISHED
FMA7_INITIATE_REQ_PDU (ASS.ind) received from LLI
\FMA7 CRL entry is valid
AND max FMA7 PDU length test negative
=> send FMA7_INITIATE_ERROR_PDU, (ASS.res(-)) to LLI
<error code = 1>
Page 610
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-NOT-ESTABLISHED 12 CONNECTION-NOT-ESTABLISHED
FMA7_INITIATE_REQ_PDU (ASS.ind) received from LLI
\FMA7 CRL entry is valid
AND max FMA7 PDU length test positive
AND FMA7 services supported test negative
=> send FMA7_INITIATE_ERROR_PDU, (ASS.res(-)) to LLI
<error code = 2>
CON-ESTABLISHING-CALLING 13 CONNECTION-ESTABLISHED
FMA7_INITIATE_RES_PDU (ASS.con(+)) received from LLI
=> FMA7 Initiate.con(+) to FMA7 user
CON-ESTABLISHING-CALLING 14 CONNECTION-NOT-ESTABLISHED
INITIATE-ERROR_PDU (ASS.con(-) from LLI)
=> FMA7 Initiate.con(-) to FMA7 user, reset CREF
CON-ESTABLISHING-CALLING 15 CONNECTION-NOT-ESTABLISHED
ABT.ind received from LLI
=> FMA7 Abort.ind to FMA7 user <reason code
out of ABT.ind>, reset CREF
CON-ESTABLISHING-CALLING 16 CONNECTION-NOT-ESTABLISHED
FMA7 Abort.req received from FMA7 user
=> ABT.req to LLI <reason code as given by user>
reset CREF
CON-ESTABLISHING-CALLING 17 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-CALLING 18 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-CALLING 19 CONNECTION-NOT-ESTABLISHED
unknown, unallowed or faulty FMA7 PDU (ASS.con)
received from LLI
=> ABT.req to LLI <reason code = ABT_RC3>
FMA7 Abort.ind to FMA7 user <reason code = ABT_RC3>
reset CREF
CON-ESTABLISHING-CALLING 20 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