Спецификация протокола Profibus

Page 211

PROFIBUS-Specification-Normative-Parts-5:1997

Access Groups (Called)

This parameter shall specify the server's membership in specific access groups.

The membership shall be used for the access to all objects of the client on this

communication relationship.

Result(-):

The Result(-) parameter shall indicate that the service request failed.

Error Code:

This parameter shall provide the reason for the failure.

- Max PDU Size Insufficient

The maximum PDU length is not sufficient for the communication.

- Feature Not Supported

The requested service or option is not supported by the server.

- User Initiate Denied

The FMS user refuses to establish the connection.

- Version OD incompatible

The versions of the Object Dictionaries (Source OD and Remote OD) of the

communication partners are not compatible.

- Password Error

There is already a communication relationship established with the same

password.

- Profile Number incompatible

The client's profile is not supported by the server.

- Other

Reason other than any of those identified above.

Max PDU Sending High Prio (Called)

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 called FMS and shall only be part of the Initiate.con

primitive.

Max PDU Sending Low Prio (Called)

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 called FMS and shall only be part of the Initiate.con primi-

tive.

Max PDU Receiving High Prio (Called)

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 called FMS and shall only be part of the Initi-

ate.con primitive.

Max PDU Receiving Low Prio (Called)

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 called FMS and shall only be part of the Initi-

ate.con primitive.

FMS Features Supported (Called)

This parameter shall identify the optional FMS services and the options sup-

ported by the server (see FMS CRL). It shall be transmitted by the called FMS

and shall only be part of the Initiate.con primitive.

Page 212

PROFIBUS-Specification-Normative-Parts-5:1997

4.4.4.2 Abort

This service shall be used to release an existing communication relationship be-

tween two communication partners. Both client and server may release the connec-

tion.

Table 15. Abort

+---------------------------------+-----+-----+

! ! ! !

! Parameter Name !.req !.ind !

! ! ! !

+---------------------------------+-----+-----+

! Argument ! M ! M !

! Locally Generated ! ! M !

! Abort Identifier ! M ! M= !

! Reason Code ! M ! M= !

! Abort Detail ! U ! C !

+---------------------------------+-----+-----+

Argument

The argument shall convey the service specific parameters of the service re-

quest.

Locally Generated

This parameter shall indicate whether the abort was generated locally or by the

communication partner.

The value false is not allowed, if the Abort Identifier parameter has the value

FMS and the Reason Code parameter has the value FMS CRL Error.

Abort Identifier

This parameter shall indicate, where the reason for the abort has been detected.

0 <=> USER

1 <=> FMS

2 <=> LLI

3 <=> LAYER2

Reason Code

This parameter shall specify the reason for the abort.

If the Abort Identifier parameter has the value USER, the following values shall

apply:

- ABT_RC1 <=> Disconnect

The connection is released by the FMS user.

- ABT_RC2 <=> Version OD incompatible

The versions of the Object Dictionaries (Source OD and Remote OD) of the com-

munication partners are not compatible.

- ABT_RC3 <=> Password Error

There is already a communication relationship established with the same pass-

word.

- ABT_RC4 <=> Profile Number incompatible

The server's profile is not supported by the client.

- ABT_RC5 <=> Limited Services Permitted

The VFD is in the Logical Status LIMITED-SERVICES-PERMITTED.

- ABT_RC6 <=> OD-loading-interacting

The PutOD Service which is not free of interaction is currently active.

Page 213

PROFIBUS-Specification-Normative-Parts-5:1997

If the Abort Identifier parameter has the value FMS, the following values shall

apply:

- ABT_RC1 <=> FMS CRL Error

Faulty FMS CRL Entry

- ABT_RC2 <=> User Error

Improper, unknown or faulty service primitive received from the FMS user

- ABT_RC3 <=> FMS PDU Error

Unknown or faulty FMS PDU received from the LLI

- ABT_RC4 <=> Connection State Conflict LLI

Improper LLI service primitive

- ABT_RC5 <=> LLI Error

Unknown or faulty LLI service primitive

- ABT_RC6 <=> PDU Size

PDU length exceeds maximum PDU length

- ABT_RC7 <=> Feature Not Supported

SERVICE_REQ_PDU received from the LLI and service or option not supported as a

server (see FMS Features Supported attribute in the FMS CRL)

- ABT_RC8 <=> Invoke ID Error Response

Confirmed service.res received from the FMS user and Invoke ID does not exist

or CONFIRMED-SERVICE_RES_PDU received from the LLI and Invoke ID does not

exist

- ABT_RC9 <=> Max Services Overflow

CONFIRMED-SERVICE_REQ_PDU received from the LLI and Outstanding Services Coun-

ter Server ≥ Outstanding Services Server

- ABT_RC10 <=> Connection State Conflict FMS

INITIATE_REQ_PDU or INITIATE_RES_PDU received from the LLI

- ABT_RC11 <=> Service Error

The service in the response does not match the service in the indication

or

the service in the confirmation does not match the service in the request

- ABT_RC12 <=> Invoke ID Error Request

CONFIRMED-SERVICE_REQ_PDU received from the LLI and Invoke ID already exists.

- ABT_RC13 <=> FMS disabled

FMS is not ready for data transmission.

If the Abort Identifier parameter has the value LLI or LAYER2, the Reason Code

parameter shall be supplied by the LLI.

Abort Detail

This parameter contains additional information about the abort reason (max. 16

octets). In case of error reports from the application, the meaning is defined

in the profile.

Page 214

PROFIBUS-Specification-Normative-Parts-5:1997

4.4.4.3 Reject

The Reject service is used by the FMS to reject an improper PDU or an improper

FMS-Service_Request or _Response from the FMS user.

Table 16. Reject

+---------------------------------+-----+

! ! !

! Parameter Name !.ind !

! ! !

+---------------------------------+-----+

! Argument ! !

! Detected Here ! M !

! Original Invoke ID ! C !

! Reject PDU Type ! M !

! Reject Code ! M !

+---------------------------------+-----+

Argument

The argument shall convey the service specific parameters of the service re-

quest.

Detected Here

This parameter shall indicate if the error has been detected locally (true). The

value false is allowed only if the Reject PDU Type parameter has the value Con-

firmed-Response-PDU and the Reject Code parameter has the value PDU Size.

Original Invoke ID

The original Invoke ID of the rejected PDU or the rejected FMS Service.

Reject PDU Type

This parameter shall indicate the type of the rejected PDU or of the PDU which

would have been resulted from the rejected FMS Service. The permissible values

are as follows:

1 <=> Confirmed-Request-PDU 3 <=> Unconfirmed-PDU

2 <=> Confirmed-Response-PDU 4 <=> Unknown type of PDU

Reject Code

This parameter shall secify the reason for the reject.

1 <=> Invoke-ID-Exists

Confirmed service.req received from the FMS user and Invoke ID

already exists

2 <=> Max-Services-Overflow

Confirmed service.req received from the FMS user and Out-standing Services

Counter Client ≥ Outstanding Services Client

3 <=> Feature-Not-Supported-Connection-Oriented

Service.req received from the FMS user and service or option not supported as

a client (see FMS Features Supported attribute in the FMS CRL)

4 <=> Feature-Not-Supported-Connectionless

Unconfirmed service.req received from the FMS user and service or option not

supported as a client (see FMS Features Supported attribute in the FMS CRL)

or confirmed service.req received from the FMS user

5 <=> PDU-Size

PDU length exceeds maximum PDU length

6 <=> User-Error-Connectionless

Improper or faulty service primitive received from the FMS user

0 <=> Other

Reason other than any of those identified above.

Page 215

PROFIBUS-Specification-Normative-Parts-5:1997

4.4.5 Tests at Connection Establishment

4.4.5.1 Context Test in FMS

Upon receipt of an INITIATE_REQ_PDU the server's FMS shall check the FMS Context

of the communication partner (remote Context), if it is compatible with its own

FMS Context (local Context) as defined for this connection in the FMS CRL. The

local FMS Context is assumed to be correct. The compatibility of the local with

the remote context is defined by the following table (see figure below). In this

table, meaningless fields are left blank (e.g. the combination of local Context

"Max PDU Sending High Prio" with remote Context "FMS Features Supported"). Those

combinations shall not be checked.

+-----------------------+---------------------------------------+

! ! local Context !

! +---------------------------------------+

! ! Max PDU ! FMS Features !

! remote !Sending !Receiving ! Supported !

! Context !High !Low !High !Low ! .req ! .ind !

! ! ! ! ! ! [n] ! [m] !

! !Prio !Prio !Prio !Prio ! 0 1 ! 0 1 !

+=======================+=====+=====+=====+=====+=======+=======+

! Max PDU Sending ! ! ≥ ! !

! High Prio ! ! ! !

+-----------------------+ ! ! !

! Max PDU Sending ! ! ≥ ! !

! Low Prio ! ! ! !

+-----------------------+-----------+-----------+---------------+

! Max PDU Receiving ! ≤ ! ! !

! High Prio ! ! ! !

+-----------------------+ ! ! !

! Max PDU Receiving ! ≤ ! ! !

! Low Prio ! ! ! !

+-----------------------+-----------+-----------+---------------+

! FMS .req [n] 0 ! ! ! X X !

! Features .req [n] 1 ! ! ! - X !

! Supported .ind [m] 0 ! ! ! X - !

! .ind [m] 1 ! ! ! X X !

+-----------------------+-----------+-----------+---------------+

! Explanation: !

! .req 0 : Feature is not used as Client !

! .req 1 : Feature is used as Client !

! .ind 0 : Feature is not supported as Server !

! .ind 1 : Feature is supported as Server !

! ≤ : local value smaller than or equal remote value !

! ≥ : local value larger than or equal remote value !

! X : compatible !

! - : not compatible (error case) !

! [n] : 0 to 23 [m] : 24 to 47 !

+---------------------------------------------------------------+

Figure 43. Compatibility of the local FMS Context to the remote FMS Context

4.4.5.2 Tests at the FMS User

- Password Test

If the FMS user supports access with password, it shall check if the password

is unambiguous. That means, if there is a password, it shall be different

from the passwords of all other communication relationships.

Page 216

PROFIBUS-Specification-Normative-Parts-5:1997

- If the password is not unambiguous and the FMS user is the server of the

Initiate service, it shall issue an Initiate.response primitive with the

Result(-) parameter and with Error Code "Password Error".

- If the password is not unambiguous and the FMS user is the client of the

Initiate service, it shall release the connection with the Abort service,

with Reason Code "Password Error".

- Test of Version OD

If the FMS user has a remote OD for this connection, it may check if the re-

ceived parameter "Version OD" is compatible with the attribute "Version OD"

of the associated remote OD.

- If they are incompatible and the FMS user is the server of the Initiate

service, it may issue an Initiate.response primitive with the Result(-) pa-

rameter and with Error Code "Version OD incompatible".

- If they are incompatible and the FMS user is the client of the Initiate

service, it may release the connection with the Abort service, with Reason

Code "Version OD incompatible".

- Test of Profile Number

The FMS user may check if the received parameter "Profile Number" is compati-

ble with the attribute "Profile Number" of the VFD.

- If they are incompatible and the FMS user is the server of the Initiate

service, it may issue an Initiate.response primitive with the Result(-) pa-

rameter and with Error Code "Profile Number incompatible".

- If they are incompatible and the FMS user is the client of the Initiate

service, it may release the connection with the Abort service, with Reason

Code "Profile Number incompatible".

4.4.6 State Machine for connection-oriented Communication Relationships

4.4.6.1 State Machine Description

CONNECTION-NOT-ESTABLISHED

The connection is not established. Only the service primitives Initiate.req,

ASS.ind, Abort.req and ABT.ind are allowed. All other services shall be rejected

with the Abort service.

CONNECTION-ESTABLISHING (CALLING)

The local FMS user wishes to establish the connection. Only the service primi-

tives ASS.con(+), ASS.con(-), Abort.req and ABT.ind are allowed. All other serv-

ices shall be rejected with the Abort service. This state is abbreviated as CON-

ESTABLISHING-CALLING.

CONNECTION-ESTABLISHING (CALLED)

The remote FMS user wishes to establish the connection. Only the service primi-

tives Initiate.res(+), Initiate.res(-), Abort.req and ABT.ind are allowed. All

other services shall be rejected with the Abort service. This state is abbrevi-

ated as CON-ESTABLISHING-CALLED.

CONNECTION-ESTABLISHED

The communication relationship is established. The service primitives Initi-

ate.req, Initiate.res(+), Initiate.res(-), DTU.ind are not allowed and shall be

rejected with the Abort service.

The following actions shall be taken to reset a communication reference ( Reset

CREF ) :

- Clear memory contents

- Set attribute "Outstanding Services Counter Client" and attribute "Outstan-

ding Services Counter Server" of the FMS CRL (dynamic part) to 0

- Set state of the communication relationship to "CONNECTION-NOT-ESTABLISHED"

Page 217

PROFIBUS-Specification-Normative-Parts-5:1997

2-8,10-12

+---+

! V

22-27 +------------------+ 14-20

+--------------->! CONNECTION- !<---------------+

! 9 ! NOT-ESTABLISHED ! 1 !

! +-------! !-------+ !

! ! +------------------+ ! !

! V ^ V !

+--------------+ ! +--------------+

! CON- ! ! 39,40,42-45, ! CON- !

! ESTABLISHING-! ! 47,48,50-56, ! ESTABLISHING-!

! CALLED ! ! 58,59,62,63, ! CALLING !

+--------------+ ! 65,66,67 +--------------+

! 21 +------------------+ 13 !

+----------->! CONNECTION- !<-----------+

! ESTABLISHED !

! !

+------------------+

! ^

+----------+

28-38,41,46,49

57,60,61,64,68

Figure 44. State Machine

4.4.6.2 State Transitions

State Transitions at Connection Establishment / Release:

Current State Transition Next State

Event

\Exit Condition

=> Action Taken

CONNECTION-NOT-ESTABLISHED 1 CON-ESTABLISHING-CALLING

Initiate.req from FMS user received

\FMS CRL entry valid

=> send INITIATE_REQ_PDU, (ASS.req) to LLI

CONNECTION-NOT-ESTABLISHED 2 CONNECTION-NOT-ESTABLISHED

Initiate.req from FMS user received

\FMS CRL entry invalid

=> Abort.ind to FMS user <reason code = ABT_RC1>

CONNECTION-NOT-ESTABLISHED 3 CONNECTION-NOT-ESTABLISHED

Abort.req received from FMS user

=> ignore

CONNECTION-NOT-ESTABLISHED 4 CONNECTION-NOT-ESTABLISHED

not allowed, unknown or faulty service

primitive received from FMS user

=> Abort.ind to FMS user <reason code = ABT_RC2>

CONNECTION-NOT-ESTABLISHED 5 CONNECTION-NOT-ESTABLISHED

ABT.ind received from LLI

=> ignore

Page 218

PROFIBUS-Specification-Normative-Parts-5:1997

Current State Transition Next State

Event

\Exit Condition

=> Action Taken

CONNECTION-NOT-ESTABLISHED 6 CONNECTION-NOT-ESTABLISHED

faulty or unknown service primitive

received from LLI

=> ABT.req to LLI <reason code = ABT_RC5>

CONNECTION-NOT-ESTABLISHED 7 CONNECTION-NOT-ESTABLISHED

not allowed LLI service primitive

received from LLI

=> ABT.req to LLI <reason code = ABT_RC4>

CONNECTION-NOT-ESTABLISHED 8 CONNECTION-NOT-ESTABLISHED

not allowed, unknown or faulty FMS PDU

(ASS.ind) received

=> ABT.req to LLI <reason code = ABT_RC3>

CONNECTION-NOT-ESTABLISHED 9 CON-ESTABLISHING-CALLED

INITIATE_REQ_PDU(ASS.ind from LLI)

\FMS CRL entry is valid

AND FMS context test is positive

=> Initiate.ind to FMS user

CONNECTION-NOT-ESTABLISHED 10 CONNECTION-NOT-ESTABLISHED

INITIATE_REQ_PDU(ASS.ind from LLI)

\FMS CRL entry is invalid

=> ABT.req to LLI <reason code = ABT_RC1>

CONNECTION-NOT-ESTABLISHED 11 CONNECTION-NOT-ESTABLISHED

INITIATE_REQ_PDU (ASS.ind) from LLI

\FMS CRL entry is valid

AND max PDU length test is negative

=> send INITIATE_ERROR_PDU (ASS.res(-)) to LLI

CONNECTION-NOT-ESTABLISHED 12 CONNECTION-NOT-ESTABLISHED

INITIATE_REQ_PDU (ASS.ind) from LLI

\FMS CRL entry is valid

AND max PDU length test is positive

AND features supported test is negative

=> send INITIATE_ERROR_PDU (ASS.res(-)) to LLI

CON-ESTABLISHING-CALLING 13 CONNECTION-ESTABLISHED

INITIATE_RES_PDU (ASS.con(+)) from LLI

=> Initiate.con(+) to FMS user

CON-ESTABLISHING-CALLING 14 CONNECTION-NOT-ESTABLISHED

INITIATE_ERROR_PDU (ASS.con(-)) from LLI

=> Initiate.con(-) to FMS user

reset CREF

CON-ESTABLISHING-CALLING 15 CONNECTION-NOT-ESTABLISHED

ABT.ind received from LLI

=> Abort.ind to FMS user <reason code out of ABT.ind>

reset CREF

Page 219

PROFIBUS-Specification-Normative-Parts-5:1997

Current State Transition Next State

Event

\Exit Condition

=> Action Taken

CON-ESTABLISHING-CALLING 16 CONNECTION-NOT-ESTABLISHED

Abort.req received from FMS user

=> ABT.req to LLI <reason code as given by user>

reset CREF

CON-ESTABLISHING-CALLING 17 CONNECTION-NOT-ESTABLISHED

faulty or unknown service primitive received from LLI

=> ABT.req to LLI <reason code = ABT_RC5>

Abort.ind to FMS user <reason code = ABT_RC5>

reset CREF

CON-ESTABLISHING-CALLING 18 CONNECTION-NOT-ESTABLISHED

not allowed LLI service primitive received from LLI

=> ABT.req to LLI <reason code = ABT_RC4>

Abort.ind to FMS user <reason code = ABT_RC4>

reset CREF

CON-ESTABLISHING-CALLING 19 CONNECTION-NOT-ESTABLISHED

not allowed, unknown or faulty FMS PDU (ASS.con)

received from LLI

=> ABT.req to LLI <reason code = ABT_RC3>

Abort.ind to FMS user <reason code = ABT_RC3>

reset CREF

CON-ESTABLISHING-CALLING 20 CONNECTION-NOT-ESTABLISHED

not allowed, unknown or faulty service

primitive received from FMS user

=> ABT.req to LLI <reason code = ABT_RC2>

Abort.ind to FMS user <reason code = ABT_RC2>

reset CREF

CON-ESTABLISHING-CALLED 21 CONNECTION-ESTABLISHED

Initiate.res(+) received from FMS user

=> send INITIATE_RES_PDU (ASS.res(+)) to LLI

CON-ESTABLISHING-CALLED 22 CONNECTION-NOT-ESTABLISHED

Initiate.res(-) received from FMS user

=> send INITIATE_ERROR_PDU (ASS.res(-)) to LLI

reset CREF

CON-ESTABLISHING-CALLED 23 CONNECTION-NOT-ESTABLISHED

Abort.req received from FMS 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

=> Abort.ind to FMS user <reason code out of ABT.ind>

reset CREF

CON-ESTABLISHING-CALLED 25 CONNECTION-NOT-ESTABLISHED

faulty or unknown service primitive

received from LLI

=> ABT.req to LLI <reason code = ABT_RC5>

Abort.ind to FMS user <reason code = ABT_RC5>

reset CREF

Page 220

PROFIBUS-Specification-Normative-Parts-5:1997

Current State Transition Next State

Event

\Exit Condition

=> Action Taken

CON-ESTABLISHING-CALLED 26 CONNECTION-NOT-ESTABLISHED

not allowed LLI service primitive

received from LLI

=> ABT.req to LLI <reason code = ABT_RC4>

Abort.ind to FMS user <reason code = ABT_RC4>, reset CREF

CON-ESTABLISHING-CALLED 27 CONNECTION-NOT-ESTABLISHED

not allowed, unknown or faulty service

primitive received from FMS user

=> ABT.req to LLI <reason code = ABT_RC2>

Abort.ind to FMS user <reason code = ABT_RC2>, reset CREF

CONNECTION-ESTABLISHED 28 CONNECTION-ESTABLISHED

confirmed Service.req received from FMS user

\OSCC < max outstanding services client

AND invoke ID not existent

AND PDU length ≤ max PDU sending low prio

AND features supported test (Client) positive

=> confirmed service_REQ_PDU with DTC.req to LLI

OSCC := OSCC + 1

CONNECTION-ESTABLISHED 29 CONNECTION-ESTABLISHED

confirmed Service.req received from FMS user

\OSCC ≥ max outstanding services client

=> Reject.ind to FMS user <reject code = 2>

CONNECTION-ESTABLISHED 30 CONNECTION-ESTABLISHED

confirmed Service.req received from FMS user

\OSCC < max outstanding services client

AND invoke ID already existent

=> Reject.ind to FMS user <reject code = 1>

CONNECTION-ESTABLISHED 31 CONNECTION-ESTABLISHED

confirmed Service.req received from FMS user

\OSCC < max outstanding services client

AND invoke ID not existent

AND PDU length > max PDU sending low prio

=> Reject.ind to FMS user <reject code = 5>

CONNECTION-ESTABLISHED 32 CONNECTION-ESTABLISHED

confirmed Service.req received from FMS user

\OSCC < max outstanding services client

AND invoke ID not existent

AND PDU length ≤ max PDU sending low prio

AND features supported test (Client) negative

=> Reject.ind to FMS user <reject code = 3>

CONNECTION-ESTABLISHED 33 CONNECTION-ESTABLISHED

unconfirmed Service.req <priority = false>

received from FMS user

\PDU length ≤ max PDU sending low prio

AND features supported test (Client) positive

=> unconfirmed Service_REQ_PDU

(DTA.req <priority = low>) to LLI

Спецификация протокола Profibus

Подождите немного. Документ загружается.