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

Page 621

PROFIBUS-Specification-Normative-Parts-7:1997

P:Parameter Code

These bits contain the Parameter-Code and these bits are coded as follows:

00000: Access Protection

00001: Profile Number

00010...01111: reserved for Profiles

10000...11111: vendor specific

L: Length

These bits contain the number of the following data octets and are coded as fol-

lows:

00: lenght is coded in the following octet(4 or more data octets)

01: 1 data octet

10: 2 data octets

11: 3 data octets

The following User Extensions are specified in this specification:

Access Protection

This User Extension contains the Password and the Access Groups which shall be

used for the Initiate Service for this CREF. The coding is as follows:

Parameter Code: 00000

Length: 10

data octet 1: Password (Unsigned8)

data octet 2: Access Groups (Bit String,coding see FMS)

Profile Number

This User Extension contains the Profile Number which shall be used for the Ini-

tiate Service for this CREF. The coding is as follows:

Parameter Code: 00001

Length: 10

data octet 1 and 2: Profile Number (Octet String, coding see FMS)

Description of the attributes for the dynamic part of a CRL entry

The value of attributes which are not needed for the current communication rela-

tionship are irrelevant, but the attributes shall exist.

Status

This attribute contains the status of all LLI state machines of the communica-

tion relationship.

Page 622

PROFIBUS-Specification-Normative-Parts-7:1997

+-------------------------------+-----------+-----------+---//

! CN Estab. / CN Release / Open ! DTC Req.1 ! DTC Req.2 !

+-------------------------------+-----------+-----------+---//

//---+-----------+-----------+-----------+---//

! DTC Req.m ! DTC Res.1 ! DTC Res.2 !

//---+-----------+-----------+-----------+---//

! DTC Res.n ! DTA Req.1 ! DTA Req.2 !

//---+-----------+-----------+-----------+---//

! DTA Req.o ! DTA Ack.1 ! DTA Ack.2 !

//---+-----------+-----------+-----------+---//

//---+-----------+----------+

! DTA Ack.p ! IDLE.req !

//---+-----------+----------+

Estab. = Establishment, m = max SCC, n = max RCC, o = max SAC,

p = max RAC

Figure 13. Structure of the Status Attribute on Connections for Acyclic Data

Transfer (Master)

+-------------------------------+-----------+-----------+---//

! CN Estab. / CN Release / Open ! DTC Res.1 ! DTC Res.2 !

+-------------------------------+-----------+-----------+---//

//---+-----------+-----------+-----------+---//

! DTC Res.n ! DTA Req.1 ! DTA Req.2 !

//---+-----------+-----------+-----------+---//

! DTA Req.o ! DTA Ack.1 ! DTA Ack.2 !

//---+-----------+-----------+-----------+---//

//---+-----------+----------+

! DTA Ack.p ! IDLE.req !

//---+-----------+----------+

Estab. = Establishment, n = max RCC, o = max SAC, p = max RAC

Figure 14. Structure of the Status Attribute on Connections for Acyclic Data

Transfer (Slave)

Page 623

PROFIBUS-Specification-Normative-Parts-7:1997

+-------------------------------+----------+-----------+---//

! CN Estab. / CN Release / Open ! DTC Req. ! DTA Req.1 !

+-------------------------------+----------+-----------+---//

//---+-----------+-----------+-----------+--//---+-----------+

! DTA Req.o ! DTA Ack.1 ! DTA Ack.2 ! ! DTA Ack.p !

//---+-----------+-----------+-----------+--//---+-----------+

Estab. = Establishment, o = max SAC, p = max RAC

Figure 15. Structure of the Status Attribute on a Connection for Cyclic Data

Transfer at the Requester (Master)

+-------------------------------+----------+-----------+---//

! CN Estab. / CN Release / Open ! DTC Res. ! DTA Req.1 !

+-------------------------------+----------+-----------+---//

//---+-----------+-----------+-----------+--//---+-----------+

! DTA Req.o ! DTA Ack.1 ! DTA Ack.2 ! ! DTA Ack.p !

//---+-----------+-----------+-----------+--//---+-----------+

Estab. = Establishment, o = SAC, p = RAC

Figure 16. Structure of the Status Attribute on a Connection for Cyclic Data

Transfer at the Responder (Slave)

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

! DTU Req. !

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

Figure 17. Structure of the Status Attribute of a Broadcast/Multicast Communi-

cation Relationship at the Requester

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

! DTU Rcv. !

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

Figure 18. Structure of the Status Attribute of a Broadcast/Multicast Communi-

cation Relationship at the Receiver

Valid states:

state machines: CN-Establishment / CN-Abort / Open

values - states

( 0) - CLOSED

( 1) - ASS-REQ-SAP-ACTIVATE

( 2) - ASS-SEND-UPDATE

( 3) - ASS-POLL-LIST-ON

( 4) - ASS-REQ-WAIT-FOR-CON

( 5) - ASS-WAIT-FOR-LLI-RES

( 6) - ASS-POLL-LIST-OFF

( 7) - ASS-RES-SAP-DEACTIVATE

Page 624

PROFIBUS-Specification-Normative-Parts-7:1997

( 8) - ASS-RES-SAP-ACTIVATE

( 9) - ASS-WAIT-LOC-RES

(10) - ASS-SEND-RES-PDU

(11) - ASS-REPLY-UPDATE

(12) - ABT-UPDATE

(13) - ABT-POLL-LIST-ON

(14) - ABT-SEND-PDU

(15) - ABT-POLL-LIST-OFF

(16) - ABT-SAP-ACTIVATE

(17) - ABT-SAP-DEACTIVATE

(18) - OPEN

(19) - OP-POLL-LIST-ON

(20) - OP-POLL-LIST-OFF

(21) - ASS-WAIT-FOR-UPDATE-CON

(22) - ABT-WAIT-FOR-UPDATE-CON

state machines: DTC-Req.1 - DTC-Req.m

values - states

( 0) - DTC-WAIT-FOR-REQ

( 1) - DTC-SEND-UPDATE

( 2) - DTC-WAIT-FOR-CON

( 3) - DTC-WAIT-FOR-RES

state machines: DTC-Res.1 - DTC-Res.n

values - states

( 0) - DTC-WAIT-FOR-REQ_PDU

( 1) - DTC-WAIT-FOR-LOC-RES

( 2) - DTC-REPLY-UPDATE

( 3) - DTC-SEND-RES

state machines: DTA-Req.1 - DTA-Req.o

values - states

( 0) - DTA-WAIT-FOR-REQM

( 1) - DTA-SEND-UPDATE

( 2) - DTA-WAIT-FOR-CON

( 3) - DTA-WAIT-FOR-REQS

( 4) - DTA-REPLY-UPDATE

( 5) - DTA-WAIT-FOR-IND

state machines: DTA-Ack.1 - DTA-Ack.p

values - states

( 0) - DTA-WAIT-FOR-REQ-PDU

( 1) - DTA-H-WAIT-FOR-BUFFER-FREE

( 2) - DTA-H-REPLY-UPDATE

( 3) - DTA-H-SEND-ACK

( 4) - DTA-L-WAIT-FOR-BUFFER-FREE

( 5) - DTA-L-UPDATE

( 6) - DTA-L-SEND-ACK

state machine: IDLE.req

values - states

( 0) - IDLE-WAIT-FOR-REQM

( 1) - IDLE-WAIT-FOR-CON

( 2) - IDLE-SEND-UPDATE

( 3) - IDLE-WAIT-FOR-REQS

Page 625

PROFIBUS-Specification-Normative-Parts-7:1997

( 4) - IDLE-REPLY-UPDATE

( 5) - IDLE-WAIT-FOR-IND

state machine: DTU-Req.

values - states

( 0) - CONLS-REQUESTER

( 1) - CONLS-WAIT-FOR-CON

state machine: DTU-Rcv.

values - states

( 0) - CONLS-SERVER

state machine: DTCC-Req:

values - states

( 0) - DTCC-WAIT-FOR-REQ

( 1) - DTCC-SEND-FOR-REQ

( 2) - DTCC-WAIT-FOR-CON

( 3) - DTCC-WAIT-FOR-RES

( 4) - DTCC-WAIT-FOR-CYC-RES

state machine: DTCC-Res:

values - states

( 0) - DTCC-WAIT-FOR-REQ-PDU

( 1) - DTCC-WAIT-FOR-FMS-RES

( 2) - DTCC-REPLY-UPDATE

( 3) - DTCC-SEND-RES

Actual Remote Address

This attribute contains the address of the communication partner which initiated

the connection establishment on this communication relationship.

Valid values

(0..126) - station address

(255) - ALL

Actual Remote LSAP

This attribute contains the Service Access Point of the communication partner

which initiated the connection establishment on this communication relationship.

Valid values

(0..62) - SAP values

(128) - NIL

(255) - ALL

SCC (Send Confirmed Request Counter)

This attribute specifies the current number of parallel confirmed services to

the communication partner.

RCC (Receive Confirmed Request Counter)

This attribute specifies the current number of parallel confirmed services from

the communication partner.

SAC (Send Acknowledged Request Counter)

This attribute specifies the current number of parallel unconfirmed services to

the communication partner.

RAC (Receive Acknowledged Request Counter)

This attribute specifies the current number of parallel unconfirmed services

from the communication partner.

Page 626

PROFIBUS-Specification-Normative-Parts-7:1997

Poll Entry Enabled

This attribute specifies the status of the Poll List entry of this communication

relationship. It is equivalent to the attribute Poll Entry of the LLI CRL.

FALSE - The poll list entry in Layer 2 is locked, i.e. the entered station

(Rem_add/DSAP) is not polled.

TRUE - The poll list entry is unlocked, i.e. the entered station (Rem_add/DSAP)

is polled.

Attributes

Object: Communication Relationship List

Key Attribute: implicit

Attribute: CRL Header

Attribute: List of CRL Entry

Object: CRL Header

Key Attribute: Communication Reference

Attribute: Number of CRL Entries

Attribute: Poll List SSAP

Attribute: ASS/ABT CI

Attribute: Symbol Length

Attribute: VFD Pointer Supported

Object: CRL Entry

Key Attribute: Communication Reference

Attribute: Local LSAP

Attribute: Remote Address

Attribute: Remote LSAP

Attribute: Type

Attribute: LLI SAP

Attribute: Connection Attribute

Attribute: max SCC

Attribute: max RCC

Attribute: max SAC

Attribute: max RAC

Attribute: CI

Attribute: Multiplier

Attribute: Max PDU Sending High Prio

Attribute: Max PDU Sending Low Prio

Attribute: Max PDU Receiving High Prio

Attribute: Max PDU Receiving Low Prio

Attribute: Services Supported

Attribute: Symbol

Attribute: VFD Pointer

Attribute: Status

Attribute: Actual Remote Address

Attribute: Actual Remote LSAP

Attribute: SCC

Attribute: RCC

Attribute: SAC

Attribute: RAC

Attribute: Poll Entry Enabled

4.5.1.3 CRL Management Services

Operations on the CRL are carried out with the following CRL management serv-

ices:

- InitiateLoad-CRL-Loc

- Load-CRL-Loc

Page 627

PROFIBUS-Specification-Normative-Parts-7:1997

- TerminateLoad-CRL-Loc

- InitiateLoad-CRL-Rem

- Load-CRL-Rem

- TerminateLoad-CRL-Rem

- Read-CRL-Loc

- Read-CRL-Rem

The CRL header or one CRL entry is read out with the Read-CRL service.

The CRL is written with the Load-CRL service. The write access to the CRL shall

be started with the InitiateLoad-CRL service and concluded with the Terminate-

Load-CRL service. The CRL entries shall be loaded in the following order:

- CRL Header

- All other CRL entries in ascending order without gaps.

The CRL entry with CREF 1 can be loaded (only locally) if one of the following

conditions is true:

- management connection is closed or

- CREF 1 not existing in the stored CRL.

If no CRL entry with CREF 1 is loaded then the stored CRL entry with CREF 1

shall be used.

A stored CRL shall be deleted by loading a CRL Header with the attribute Number

of CRL Entries equals 0.

The communication does not test the CRL for consistency but only for ability to

be loaded.

The CRL may be read and written locally or remotely. Reading and writing is not

permissible at the same time.

4.5.1.3.1 Read-CRL-Loc

The CRL header or one CRL entry is read with the Read-CRL service.

The communication reference shall be set to 0 for reading the CRL header. FMA7

composes the CRL header out of the FMA7, the FMS and the LLI CRL headers.

The corresponding communication reference shall be set for reading a CRL entry.

In the case of a management connection, FMA7 composes the CRL entry out of the

FMA7 CRL entry and the LLI CRL entry. In the case of a FMS connection it is com-

posed out of the FMS CRL entry and the LLI CRL entry. If this CREF does not ex-

ist, the response to the service is Result(-). The Read-CRL-Loc service shall be

used repeatedly to read out the whole CRL.

Table 4. Read-CRL-Loc

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

! ! ! !

! Parameter Name !.req ! !

! ! !.con !

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

! Argument ! M ! !

! Desired CREF ! M ! !

! ! ! !

! Result(+) ! ! S !

! CRL Entry ! ! M !

! ! ! !

! Result(-) ! ! S !

! Error Type ! ! M !

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

Page 628

PROFIBUS-Specification-Normative-Parts-7:1997

Argument

The argument contains the parameters of the Read-CRL-Loc.req primitive.

Desired CREF

Result(+)

The Result(+) parameter indicates that the service was executed successfully.

CRL Entry

CRL header or one CRL entry.

Result(-)

The Result(-) parameter indicates that the service failed.

Error Type

This parameter contains information on the reason the service failed.

4.5.1.3.2 Read-CRL-Rem

The CRL header or one CRL entry is read at the remote station with the Read-CRL-

Rem service. For reading the CRL header the communication reference shall be set

to 0. For reading the CRL entry the corresponding communication reference shall

be set. If this CREF does not exist the response to the service is Result(-).

The Read-CRL-Rem service shall be used repeatedly to read out the whole CRL.

Table 5. Read-CRL-Rem

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

! ! ! !

! Parameter Name !.req !.res !

! !.ind !.con !

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

! Argument ! M ! !

! Communication Reference ! M ! !

! Desired CREF ! M ! !

! ! ! !

! Result(+) ! ! S !

! Communication Reference ! ! M !

! CRL Entry ! ! M !

! ! ! !

! Result(-) ! ! S !

! Communication Reference ! ! M !

! Error Type ! ! M !

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

Argument

The argument contains the parameters of the Read-CRL-Rem.req primitive and the

Read-CRL-Rem.ind primitive.

Communication Reference

This parameter specifies the identifier of the associated management connection

in the CRL.

Desired CREF

The value 0 is set for reading the CRL header, otherwise the communication ref-

erence of the CRL entry which is to be read.

Result(+)

The Result(+) parameter indicates that the service was executed successfully.

CRL Entry

CRL header or one CRL entry.

Page 629

PROFIBUS-Specification-Normative-Parts-7:1997

Result(-)

The Result(-) parameter indicates that the service failed.

Error Type

This parameter contains information on the reason the service failed.

4.5.1.3.3 InitiateLoad-CRL-Loc

The local writing into the CRL is performed with a sequence of InitiateLoad-CRL-

Loc, one or several Load-CRL-Loc services and one TerminateLoad-CRL-Loc.

All communication relationships with the exception of the default management

connection are released by FMS and LLI, and stay locked for data communication

until the Terminate-Load-CRL-Loc service was executed successfully. After the

execution of the InitiateLoad-CRL-Loc service the CRL header and the CRL entries

may be loaded with the Load-CRL-Loc service.

Table 6. InitiateLoad-CRL-Loc

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

! ! ! !

! Parameter Name !.req ! !

! ! !.con !

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

! Argument ! M ! !

! ! ! !

! Result(+) ! ! S !

! ! ! !

! Result(-) ! ! S !

! Error Type ! ! M !

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

Argument

The argument contains no parameters.

Result(+)

The Result(+) parameter indicates that the service was executed successfully.

Result(-)

The Result(-) parameter indicates that the service failed.

Error Type: information on the reason the service failed.

4.5.1.3.4 Load-CRL-Loc

The CRL header or the static part of one CRL entry is written locally with the

Load-CRL-Loc service. The CRL header is written as a CRL entry with the communi-

cation reference 0. FMA7 generates out of the CRL header the FMA7, FMS and the

LLI CRL headers and writes these into the corresponding instances.

For writing the static part of a CRL entry the corresponding CREF shall be set.

The FMA7 generates out of the CRL entry the FMA7 CRL entry and the LLI CRL entry

in the case of a management connection. In the case of a FMS connection it gen-

erates the FMS CRL entry and the LLI CRL entry. Then the CRL entries are written

into the corresponding instances.

Page 630

PROFIBUS-Specification-Normative-Parts-7:1997

The Load-CRL-Loc service shall be used repeatedly to write the whole CRL.

Table 7. Load-CRL-Loc

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

! ! ! !

! Parameter Name !.req ! !

! ! !.con !

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

! Argument ! M ! !

! CRL Entry Static ! M ! !

! ! ! !

! Result(+) ! ! S !

! ! ! !

! Result(-) ! ! S !

! Error Type ! ! M !

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

Argument

The argument contains the parameters of the Load-CRL-Loc.req primitive.

CRL Entry Static

CRL header or static part of a CRL entry.

Result(+)

The Result(+) parameter indicates that the service was executed successfully.

Result(-)

The Result(-) parameter indicates that the service failed.

Error Type

This parameter contains information on the reason the service failed.

4.5.1.3.5 TerminateLoad-CRL-Loc

The TerminateLoad-CRL-Loc service concludes the local writing into the CRL. FMS

and LLI are unlocked again for data transfer.

Table 8. TerminateLoad-CRL-Loc

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

! ! ! !

! Parameter Name !.req ! !

! ! !.con !

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

! Argument ! M ! !

! ! ! !

! Result(+) ! ! S !

! ! ! !

! Result(-) ! ! S !

! Error Type ! ! M !

! Error CREF ! ! C !

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

Argument

The argument contains no parameters.

Result(+)

The Result(+) parameter indicates that the service was executed successfully.

Result(-)

The Result(-) parameter indicates that the service failed. If an error occurred

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

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