Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 201
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
Result(+)
The Result(+) parameter indicates that the service was executed successfully.
Result(-)
The Result(-) parameter indicates that the service was not executed success-
fully.
ErrorType
This parameter contains information about the reason for the unsuccessful execu-
tion of the service.
4.3.6.2.2 PutOD
With the PutOD service one or several object descriptions are written into the
OD.
Table 11. PutOD
+---------------------------------+-----+-----+
! ! ! !
! Parameter Name !.req !.res !
! !.ind !.con !
+---------------------------------+-----+-----+
! Argument ! M ! !
! List of Object Description ! M ! !
! ! ! !
! Result(+) ! ! S !
! ! ! !
! Result(-) ! ! S !
! ErrorType ! ! M !
+---------------------------------+-----+-----+
Argument
The argument contains the service specific parameters of the service call.
List of object description
One or several object descriptions which shall be entered into the OD. If access
rights are not supported (Access Protection = false), the attributes Password,
Access Groups and Access Rights are meaningless.
An object description may also be deleted with the PutOD service. In this case,
an empty object description with the following structure is transferred:
- Index of the object description to be deleted
- Object Code = Null Object.
+-------+--------------+
! Index ! Object !
! ! Code !
+-------+--------------+
! 246 ! Null Object !
+-------+--------------+
Figure 36. Empty Object Description (Example)
Result(+)
The Result(+) parameter indicates that the service was successfully executed.
Result(-)
The Result(-) parameter indicates that the service was not successfully exe-
cuted. In this case, no object description is written into the OD.
Page 202
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
ErrorType
This parameter contains information about the reason for the unsuccessful execu-
tion of the service.
4.3.6.2.3 TerminatePutOD
The TerminatePutOD service terminates the process of loading of the OD. The ob-
jects with their state machines are generated.
Table 12. TerminatePutOD
+---------------------------------+-----+-----+
! ! ! !
! Parameter Name !.req !.res !
! !.ind !.con !
+---------------------------------+-----+-----+
! Argument ! M ! !
! ! ! !
! Result(+) ! ! S !
! ! ! !
! Result(-) ! ! S !
! ErrorType ! ! M !
! Index ! ! C !
+---------------------------------+-----+-----+
Argument
The Argument contains no service specific parameters.
Result(+)
The Result(+) parameter indicates that the service was successfully executed.
Result(-)
The Result(-) parameter indicates that the service was not successfully exe-
cuted. If an error occurs during the generation of the objects, the old state is
restored.
ErrorType
This parameter contains information about the reason for the unsuccessful execu-
tion of the service.
Index
This parameter gives the index of the object, for which the generation was not
successful.
4.3.7 State Machine
4.3.7.1 State Machine Description
OD-LOADING-NON-INTERACTING
In this state the execution of the service InitiatePutOD is not permitted. In
this state the service PutOD on the DV-OD or the DP-OD is not permitted.
OD-LOADING-INTERACTING
Except for the connection over which the InitiatePutOD service was received, all
connections shall be aborted and the establishment of a further connection
shall be rejected with an abort using Reason Code 6. On this connection only the
following services are allowed:
- Initiate - PhysWrite
- Abort - GetOD
- Reject - InitiatePutOD
Page 203
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
- Status - PutOD
- Identify - TerminatePutOD
- PhysRead
OD-READY
In this state all connections and services may be used normally.
5,6,7,8 6,7,8,10
+---+ +---+
! V ! V
+------+----------+ +------+----------+
! OD-LOADING- ! ! OD-LOADING- !
! NON-INTERACTING ! ! INTERACTING !
! ! ! !
+-----------------+ +-----------------+
^ ! 3,4 ! ^
2 ! ! 9 +---+ 9 ! ! 1
! ! ! V ! !
! ! +-----------------+ ! !
! +----->! !<-----+ !
+----------! OD-READY !----------+
Power Up --->! !
+-----------------+
Figure 37. State Machine
4.3.7.2 State Transitions
-----------------------------------------------------------------
Event
\Exit Condition
=> Action Taken
-----------------------------------------------------------------
1 InitiatePutOD.ind
\consequence >0
=> .res(+)
2 InitiatePutOD.ind
\consequence =0
=> .res(+)
3 PutOD.ind
=> .res(-) object state conflict
4 TerminatePutOD.ind
=> .res(-) object state conflict
5 InitiatePutOD.ind
\consequence >0
=> .res(-) object state conflict
6 InitiatePutOD.ind
\consequence =0
=> .res(-) object state conflict
7 PutOD.ind
=> .res(+)
8 TerminatePutOD.ind
\OD not usable
=> .res(-) operational problem
9 TerminatePutOD.ind
\OD okay
=> .res(+)
10 InitiatePutOD.ind
\consequence >0
=> .res(+)
Page 204
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
4.3.8 EXAMPLE of a PutOD Sequence
User Client Server
InitiatePutOD +----------------+
! Consequence !----->
+----------------+
+---------+
<-----! .res(+) !
+---------+
PutOD +----------------+
! Object !----->
! Descriptions !
+----------------+
+---------+
<-----! .res(+) !
. +---------+
PutOD +----------------+ .
! Object !----->
! Descriptions !
+----------------+
+---------+
<-----! .res(+) !
+---------+
TerminatePutOD +----------------+
! !----->
+----------------+
+---------+
<-----! .res(+) !
+---------+
Figure 38. Example of a PutOD Sequence
4.4 Context Management
4.4.1 Model Description
The context contains all agreements concerning a communication relationship. The
context management services shall be used to establish a connection, to release
a connection and to reject improper services. The data necessary for this are
stored in the OD object description and in the Communication Relationship List
of the FMS. Transaction objects are provided for each communication relation-
ship. The transaction objects are used for the management of confirmed service
primitives.
4.4.2 The FMS CRL Object
The FMS communication relationship list (FMS CRL) contains the FMS specific de-
scriptions of all communication relationships of a device irrespective of the
time of use. The FMS CRL is organized in entries. Each entry can be addressed
with the key index communication relationship (CREF). Each entry consists of a
static and a dynamic part. The entry contains the complete FMS specific descrip-
tion of the associated communication relationship.
The FMS CRL header contains information on the structure of the FMS CRL. The FMS
CRL header is addressed with CREF 0.
Page 205
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
Key ! FMS CRL Header
+-------+-------------------+---------+--------------+
! 0 ! Number of ! Symbol ! VFD Pointer !
! ! FMS CRL Entries ! Length ! Supported !
+-------+-------------------+---------+--------------+
Figure 39. Structure of the FMS CRL Header
Static Part of the FMS CRL Entry
Key ! FMS CRL
+------+-----------+----------+-----------+----------+------------+//
! CREF ! Max PDU Sending ! Max PDU Receiving ! Symbol !
! ! High Prio ! Low Prio ! High Prio ! Low Prio ! (optional) !
+------+-----------+----------+-----------+----------+------------+//
//+---------------+-------------+-------------+-----------+//
! FMS Features ! Max Outstanding Services ! CREL Type !
! Supported ! Client ! Server ! !
//+---------------+-------------+-------------+-----------+//
Dynamic Part of the FMS CRL Entry
//+------------+//---------------+---------------+------------+
! VFD Pointer! Outstanding Services Counter ! CREL State !
! (optional) ! Client ! Server ! !
//+------------+//---------------+---------------+------------+
Figure 40. Structure of a FMS CRL Entry
FMS CRL Header:
Number of FMS CRL entries
This attribute shall specify the number of FMS CRL entries in the FMS CRL.
Symbol Length
This attribute shall specify the length of symbols in the FMS CRL. Only values
of 0..32 are allowed.
0 <=> no symbols
VFD Pointer Supported
This attribute shall indicate, if several VFDs are sup-ported in the FMS CRL.
Static part of the FMS CRL entry:
CREF
The communication reference (CREF) is a locally unique address of the communica-
tion relationship.
Max PDU Sending High Prio
This attribute shall specify the maximum length of the FMS PDU to be sent with
high priority that may be handled on this communication relationship.
Max PDU Sending Low Prio
This attribute shall specify the maximum length of the FMS PDU to be sent with
low priority that may be handled on this communication relationship.
Max PDU Receiving High Prio
This attribute shall specify the maximum length of the FMS PDU to be received
with high priority that may be handled on this communication relationship.
Page 206
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
Max PDU Receiving Low Prio
This attribute shall specify the maximum length of the FMS PDU to be received
with low priority that may be handled on this communication relationship.
FMS Features Supported
This attribute shall identify the optional FMS services and the options sup-
ported on this communication relationship. For each optional service there are
two bits specifying the service primitives supported. For the options there are
two bits specifying for which service primitives the options are permissible.
The definition of the assignment of services to master/slave and to objects, and
the OD object shall be observed when selecting the FMS features.
Table 13. Attribute FMS Features Supported
+---------------------------------+--------------+--------------+
! Service ! Primitive ! Primitive !
! ! bit[n] ! bit[m] !
+---------------------------------+--------------+--------------+
! GetOD (Long form) ! .req,.con 0 ! .ind,.res 24 !
! UnsolicitedStatus ! .req 1 ! .ind 25 !
! InitiatePutOD ! .req,.con 2 ! .ind,.res 26 !
! PutOD ! .req,.con " ! .ind,.res " !
! TerminatePutOD ! .req,.con " ! .ind,.res " !
! InitiateDownloadSequence ! .req,.con 3 ! .ind,.res 27 !
! DownloadSegment ! .ind,.res " ! .req,.con " !
! TerminateDownloadSequence ! .ind,.res " ! .req,.con " !
! InitiateUploadSequence ! .req,.con 4 ! .ind,.res 28 !
! UploadSegment ! .req,.con " ! .ind,.res " !
! TerminateUploadSequence ! .req,.con " ! .ind,.res " !
! RequestDomainDownload ! .req,.con 5 ! .ind,.res 29 !
! RequestDomainUpload ! .req,.con 6 ! .ind,.res 30 !
! CreateProgramInvocation ! .req,.con 7 ! .ind,.res 31 !
! DeleteProgramInvocation ! .req,.con " ! .ind,.res " !
! Start ! .req,.con 8 ! .ind,.res 32 !
! Stop ! .req,.con " ! .ind,.res " !
! Resume ! .req,.con " ! .ind,.res " !
! Reset ! .req,.con " ! .ind,.res " !
! Kill ! .req,.con 9 ! .ind,.res 33 !
! Read ! .req,.con 10 ! .ind,.res 34 !
! Write ! .req,.con 11 ! .ind,.res 35 !
! ReadWithType ! .req,.con 12 ! .ind,.res 36 !
! WriteWithType ! .req,.con 13 ! .ind,.res 37 !
! PhysRead ! .req,.con 14 ! .ind,.res 38 !
! PhysWrite ! .req,.con 15 ! .ind,.res 39 !
! InformationReport ! .req 16 ! .ind 40 !
! InformationReportWithType ! .req 17 ! .ind 41 !
! DefineVariableList ! .req,.con 18 ! .ind,.res 42 !
! DeleteVariableList ! .req,.con " ! .ind,.res " !
! EventNotification ! .req 19 ! .ind 43 !
! EventNotificationWithType ! .req 20 ! .ind 44 !
! AcknowledgeEventNotification ! .req,.con 21 ! .ind,.res 45 !
! AlterEventConditionMonitoring ! .req,.con 22 ! .ind,.res 46 !
+---------------------------------+--------------+--------------+
! Options ! Primitive ! Primitive !
! ! bit[n] ! bit[m] !
! Addressing with Name ! .req 23 ! .ind 47 !
+---------------------------------+--------------+--------------+
! Explanation: !
! [n] : 0 to 23 !
! [m] : 24 to 47 !
+---------------------------------------------------------------+
Page 207
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
Max Outstanding Services Client
This attribute shall specify the maximum number of outstanding confirmed serv-
ices allowed on this communication relationship as a client.
Max Outstanding Services Server
This attribute shall specify the maximum number of outstanding confirmed serv-
ices allowed on this communication relationship as a server.
CREL Type
This attribute shall indicate the type of the communication relationship.
- true : connection-oriented
- false : connectionless
Symbol:
This attribute shall specify the symbolic name of the communication reference.
Existence and length of the symbol are defined in the FMS CRL header.
VFD Pointer
This pointer shall refer to the assigned VFD.
Dynamic part of the FMS CRL entry:
Outstanding Services Counter Client ( OSCC )
This attribute shall specify the number of currently outstanding confirmed serv-
ices on this communication relationship as a client.
Outstanding Services Counter Server ( OSCS )
This attribute shall specify the number of outstanding services that are cur-
rently being processed on this communication relationship as a server.
CREL State
This attribute shall specify the state of the communication relationship. A con-
nection-oriented communication relationship may be in one of the following
states:
- CONNECTION-NOT-ESTABLISHED
- CONNECTION-ESTABLISHING (CALLING)
- CONNECTION-ESTABLISHING (CALLED)
- CONNECTION-ESTABLISHED
A connectionless communication relationship shall always have the state
CONNECTIONLESS-CLIENT or CONNECTIONLESS-SERVER (see context management state ma-
chines).
4.4.3 The Transaction Object
A Transaction Object shall be created upon receipt of a confirmed service indi-
cation primitive. The Transaction Object shall be uniquely related to the corre-
sponding service primitive. The Transaction Object shall be deleted after the
corresponding response primitive has been sent. The Transaction Object shall be
uniquely identified by the combination of Invoke ID and communication reference.
The maximum number of Transaction Objects for each communication relationship of
the server shall be specified by the Max Outstanding Services Server attribute
in the FMS CRL.
The following services act on the Transaction Object:
Page 208
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
- all confirmed services \ +--------------------+
- Abort >------------->! Transaction !
/ ! Object !
+--------------------+
Figure 41. Transaction Object
4.4.3.1 Attributes
Object: Transaction Object
Key Attribute: Invoke ID & CREF
Attribute: Confirmed service indication
Invoke ID
This attribute shall identify the Transaction Object within the communication
relationship.
CREF
This attribute shall identify the communication relationship on which the Trans-
action Object is used.
Confirmed service indication
Service identifier and argument of the pending service.
4.4.3.2 State Machine
State Machine Description
NON-EXISTENT
The Transaction Object does not exist.
PENDING
A confirmed service indication primitive has been received and the corresponding
response primitive has not yet been sent.
2 +------------+ 1 +------------+
+---! NON- !------>! !
! ! EXISTENT ! 3,4 ! PENDING !
+-->! !<------! !
+------------+ +------------+
Figure 42. Transaction Object State Machine
State Transitions
1 Confirmed service.ind (Number of Transaction Objects < max)
2 Confirmed service.ind (Number of Transaction Objects = max)
3 Confirmed service.res
4 Abort.ind
Page 209
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
4.4.4 Context Management Services
The Context Management Services comprise
- Initiate
- Abort
- Reject.
4.4.4.1 Initiate
This service shall be used to establish a connection between two communication
partners and to exchange information regarding the supported services, the sup-
ported options, the maximum PDU length and the current version of the OD.
Table 14. Initiate
+----------------------------------+-----+-----+-----+-----+
! ! ! ! ! !
! Parameter Name !.req !.ind !.res !.con !
! ! ! ! ! !
+----------------------------------+-----+-----+-----+-----+
! Argument ! M ! M= ! ! !
! Version OD *) ! M ! M= ! ! !
! Profile Number *) ! M ! M= ! ! !
! Access Protection Supported *) ! M ! M= ! ! !
! Password *) ! M ! M= ! ! !
! Access Groups *) ! M ! M= ! ! !
! Max PDU Sending High Prio *) ! ! ! ! !
! Max PDU Sending Low Prio *) ! ! ! ! !
! Max PDU Receiving High Prio *) ! ! ! ! !
! Max PDU Receiving Low Prio *) ! ! ! ! !
! FMS Features Supported *) ! ! ! ! !
! ! ! ! ! !
! Result(+) ! ! ! S ! S= !
! Version OD **) ! ! ! M ! M= !
! Profile Number **) ! ! ! M ! M= !
! Access Protection Supported **)! ! ! M ! M= !
! Password **) ! ! ! M ! M= !
! Access Groups **) ! ! ! M ! M= !
! ! ! ! ! !
! Result(-) ! ! ! S ! S= !
! Error Code ! ! ! M ! M !
! Max PDU Sending High Prio **) ! ! ! ! M !
! Max PDU Sending Low Prio **) ! ! ! ! M !
! Max PDU Receiving High Prio **)! ! ! ! M !
! Max PDU Receiving Low Prio **) ! ! ! ! M !
! FMS Features Supported **) ! ! ! ! M !
+----------------------------------+-----+-----+-----+-----+
! Explanation: !
! *) Calling **) Called !
+----------------------------------------------------------+
Argument
The argument shall convey the service specific parameters of the service re-
quest.
Version OD (Calling)
This parameter shall specify the version of the client's Object Dictionary.
Profile Number (Calling)
This parameter shall specify the Profile Number of the client.
Page 210
PROFIBUS-Specification-Normative-Parts-5:1997
Copyright by PNO 1997 - all rights reserved
Access Protection Supported (Calling)
This parameter shall contain the Access Protection Supported attribute of the
client's OD object description.
Password (Calling)
This parameter shall specify the password to be used for the access to all ob-
jects of the server on this communication relationship. If access with password
is not to be used on this communication relationship, the password parameter
shall have the value 0.
Access Groups (Calling)
This parameter shall specify the client's membership in specific access groups.
The membership applies for the access to all objects of the server on this com-
munication relationship.
Max PDU Sending High Prio (Calling)
This parameter shall specify the maximum length of the FMS PDU to be sent with
high priority that may be handled on this communication relationship.
It shall be transmitted by the calling FMS and is not part of the primitive.
Max PDU Sending Low Prio (Calling)
This parameter shall specify the maximum length of the FMS PDU to be sent with
low priority that may be handled on this communication relationship. It shall be
transmitted by the calling FMS and is not part of the primitive.
Max PDU Receiving High Prio (Calling)
This parameter shall specify the maximum length of the FMS PDU to be received
with high priority that may be handled on this communication relationship. It
shall be transmitted by the calling FMS and is not part of the primitive.
Max PDU Receiving Low Prio (Calling)
This parameter shall specify the maximum length of the FMS PDU to be received
with low priority that may be handled on this communication relationship. It
shall be transmitted by the calling FMS and is not part of the primitive.
FMS Features Supported (Calling)
This parameter shall identify the optional FMS services and the options sup-
ported by the client (see FMS CRL). It shall be transmitted by the calling FMS
and is not part of the primitive.
Result(+)
The Result(+) parameter shall indicate that the requested service was executed
successfully.
Version OD (Called)
This parameter shall specify the version of the server's Object Dictionary.
Profile Number (Called)
This parameter shall specify the Profile Number of the server.
Access Protection Supported (Called)
This parameter shall contain the Access Protection Supported attribute of the
server's OD object description.
Password (Called)
This parameter shall specify the password to be used for access to all objects
of the client on this communication relationship. If access with password is not
to be used on this communication relationship, the password parameter shall have
the value 0.