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

Page 441

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Receiver

.

User!FMS LLI FDL BUS FDL LLI FMS!User

=====!====!=============!======.======!=============!====!=====

INFO.req ! !*no Data ! !

<#7,High> ! ![SRD_REQ_PDU]! !

----> ! ! ]------>]! !

[INFO_REQ_! ![<----------/! !

PDU] ! ![SRD_RES_PDU]! !

! !*no Data ! !

DTA.req ! ! ! !

<#7,0, ! ! ! !

HIGH, ! ! ! !

INFO_ ! ! ! !DTA.ind

REQ_PDU>![DTA_REQ_PDU]!**INFO_REQ_ ! !<#8,0,

---->!(FDL_DATA_ ! PDU !(FDL_DATA_ ! High,

! REPLY.req !*DTA_REQ_PDU ! REPLY.ind ! INFO_

!<High>) ![SRD_REQ_PDU]!<High>) ! REQ_PDU>

! ]------>!------------>!------------>!---->

! [<------!<-----------/! !

!(FDL_DATA_ ![SRD_RES_PDU]! ! INFO.ind

! REPLY.con) !*no Data ! ! <#8,High>

! ! ! ! ---->

! ! ! !

! !*no Data ! !

! ![SRD_REQ_PDU]! !

! ! ]------>]! !

! ![<---------/ ! !

! ![SRD_RES_PDU]! !

! !*no Data ! !

! ! ! \Buffer_free!

! ! !"generate !

! ! ! DTA_ACK_PDU !

! ! ! !

! ! ![DTA_ACK_PDU]!

! ! ! !

! ! !(FDL_REPLY_ !

! ! ! UPDATE.req !

! ! !<High>) !

! ! (--!<------[ !

! ! (--!------>] !

! ! !(FDL_REPLY_ !

! ! ! UPDATE.con) !

! ! ! !

! !*no Data !(FDL_DATA_ !

! ![SRD_REQ_PDU]! REPLY.ind) !

! ! ]------->!--->] !

! [<------!<-----------/! !

!(FDL_CYC_DATA![SRD_RES_PDU]! !

! REPLY.con) !*DTA_ACK_PDU ! !

! v ! ! !

!\Buffer_free ! ! !

! ! ! !

Figure 74. Master-Slave Communication Relationship / Connection for Cyclic

Data Transfer with no Slave Initiative / InformationReport with

high Priority

Page 442

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Receiver

.

User!FMS LLI FDL BUS FDL LLI FMS!User

=====!====!=============!======.======!=============!====!=====

INFO.req ! !*no Data ! !

<#7,Low> ! ![SRD_REQ_PDU]! !

----> ! ! ]------>]! !

[INFO_REQ_! ![<----------/! !

PDU] ! ![SRD_RES_PDU]! !

DTA.req ! !*no Data ! !

<#7,0, ! ! ! !

Low, ! ! ! !

INFO_ ! ! ! !

REQ_PDU>![DTA_REQ_PDU]! ! !

---->!(FDL_SEND_ ! ! !

! UPDATE.req) ! ! !

! ]------>!--) ! !

! [<------!--) ! !DTA.ind

!(FDL_SEND_ ! ! !<#8,0,

! UPDATE.con) ! !(FDL_DATA_ ! Low,

! !*DTA_REQ_PDU ! REPLY.ind ! INFO_

! ![SRD_REQ_PDU]!<Low>) ! REQ_PDU>

! ! ]------->!------------>!---->

! [<------!<-----------/! !

!(FDL_CYC_DATA![SRD_RES_PDU]! ! INFO.ind

! REPLY.con) !*no Data ! ! <#8,Low>

! ! ! ! ---->

! !*no Data ! !

! ![SRD_REQ_PDU]! !

! ! ]------>]! !

! ![<---------/ ! !

! ![SRD_RES_PDU]! \Buffer_free!

! !*no Data !"generate !

! ! ! DTA_ACK_PDU !

! ! ! !

! ! ![DTA_ACK_PDU]!

! ! !(FDL_REPLY_ !

! ! ! UPDATE.req !

! ! !<Low>) !

! ! (--!<------[ !

! ! (--!------>] !

! ! !(FDL_REPLY_ !

! ! ! UPDATE.con) !

! ! ! !

! !*no Data !(FDL_DATA_ !

! ![SRD_REQ_PDU]! REPLY.ind) !

! ! ]------->!--->] !

! [<------!<-----------/! !

!(FDL_CYC_DATA![SRD_RES_PDU]! !

! REPLY.con) !*DTA_ACK_PDU ! !

! v ! ! !

!\Buffer_free ! ! !

! ! ! !

Figure 75. Master-Slave Communication Relationship / Connection for Cyclic

Data Transfer with no Slave Initiative / InformationReport with

low Priority

Page 443

PROFIBUS-Specification-Normative-Parts-6:1997

Connection for Cyclic Data Transfer with Slave Initiative (MSCY_SI)

On a connection for Cyclic Data Transfer with Slave Initiative the mapping of

the confirmed FMS services Read and Write, of the unconfirmed FMS services (re-

quester = master) and of the Reject service is analogous to the mapping for a

connection for Cyclic Data Transfer with no Slave Initiative (see subclause

4.3.4.1.1). The transmission of remote FMA7 services is not permitted on connec-

tions for Cyclic Data Transfer with no Slave Initiative.

Unconfirmed FMS services with requester = slave:

Unconfirmed FMS services are services which are not acknowledged by the user.

For these services low or high priority may be used. The mapping of the uncon-

firmed FMS services onto Layer 2 is described here for the example of the Infor-

mationReport service. All other unconfirmed FMS services are mapped in the same

way.

InformationReport service:

On a connection for Cyclic Data Transfer with Slave Initiative the Information-

Report service is used for a single writing of data into a master. FMS maps each

request (InformationReport.req) onto the LLI service primitive DTA.req. The pri-

ority chosen by the user of the slave is transferred transparently. Correspond-

ing to the priority, the LLI stores a DTA_REQ_PDU into the high or low priority

Layer 2 update memory. The following SRD_REQ_PDU causes the update memory to be

read. The SRD_RES_PDU transports the INFORMATION-REPORT_REQ_PDU to the master.

The resulting FDL confirmation leads to a DTA.ind from the LLI of the master to

FMS. The FMS maps this DTA.ind onto an InformationReport.ind and passes it to

the user.

If there is memory available again (Buffer_free) for the LLI of the master to

receive another DTA_REQ_PDU, the LLI generates a DTA_ACK_PDU to signal this to

the LLI of the slave. Corresponding to the priority with which the DTA_REQ_PDU

was passed to LLI by the Layer 2, LLI maps the DTA_ACK_PDU either onto the Layer

2 service SRD with high priority or onto the Layer 2 service CSRD. The following

SRD_REQ_PDU transports the DTA_ACK_PDU to the LLI of the slave. This does not

lead to a confirmation to FMS.

Page 444

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Receiver . Slave/Requester

.

User!FMS LLI FDL BUS FDL LLI FMS!User

=====!====!=============!======.======!=============!====!=====

! !*no Data ! ! INFO.req

! ![SRD_REQ_PDU]! ! <#8,High>

! ! ]------>]! ! <-----

! ![<----------/! !

! ![SRD_RES_PDU]! ![INFO_REQ_

! !*no Data ! ! PDU]

! ! ! !

! ! ! !DTA.req

! ! ! !<#8,0,

! ! ! ! High,

! ! ! ! INFO_

! ! ! ! REQ_PDU>

! ! ![DTA_REQ_PDU]!<----

! ! ! !

! ! !(FDL_REPLY_ !

! ! ! UPDATE.req !

! ! ! <HIGH>) !

! ! (--!<------[ !

! ! (--!------>] !

! ! !(FDL_REPLY_ !

! ! ! UPDATE.con) !

! ! ! !

! !*no Data !(FDL_DATA_ !

! ![SRD_REQ_PDU]! REPLY.ind) !

! ! ]------->!----->] !

! [<-------!<-----------/! !

!(FDL_CYC_DATA![SRD_RES_PDU]! !

! _REPLY.con) !*DTA_REQ_PDU ! !

! !**INFO_REQ_ ! !

<-----!<---] ! PDU ! !

DTA.ind ! ! ! !

<#7,0, ! ! ! !

High, ! ! ! !

INFO_ ! ! ! !

REQ_PDU>!\Buffer_free ! ! !

!"generate ! ! !

INFO.ind ! DTA_ACK_PDU ! ! !

<#7,High>! ! ! !

<---- ![DTA_ACK_PDU]! ! !

! ! ! !

!(FDL_DATA_ ! !(FDL_DATA_ !

! REPLY.req !*DTA_ACK_PDU ! REPLY.ind !

!<High>) ![SRD_REQ_PDU]!<High>) !

! ]------>!------------>!---->] !

! [<------!<-----------/! ! !

!(FDL_DATA_ ![SRD_RES_PDU]! v !

! REPLY.con) !*no Data !\Buffer_free !

! ! ! !

Figure 76. Master-Slave Communication Relationship / Connection for Cyclic

Data Transfer with Slave Initiative / InformationReport with

high Priority

Page 445

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Receiver . Slave/Requester

.

User!FMS LLI FDL BUS FDL LLI FMS!User

=====!====!=============!======.======!=============!====!=====

! !*no Data ! ! INFO.req

! ![SRD_REQ_PDU]! ! <#8,Low>

! ! ]------>]! ! <-----

! ![<----------/! !

! ![SRD_RES_PDU]! ![INFO_REQ_

! !*no Data ! ! PDU]

! ! ! !DTA.req

! ! ! !<#8,0,

! ! ! ! Low,

! ! ! ! INFO_

! ! ! ! REQ_PDU>

! ! ![DTA_REQ_PDU]!<----

! ! !(FDL_REPLY_ !

! ! ! UPDATE.req !

! ! ! <Low>) !

! ! (--!<------[ !

! ! (--!------>] !

! ! !(FDL_REPLY_ !

! ! ! UPDATE.con) !

! ! ! !

! !*no Data !(FDL_DATA_ !

! ![SRD_REQ_PDU]! REPLY.ind) !

! ! ]------->!----->] !

! [<-------!<-----------/! !

!(FDL_CYC_DATA![SRD_RES_PDU]! !

! _REPLY.con) !*DTA_REQ_PDU ! !

! !**INFO_REQ_ ! !

<----!<---[ ! PDU ! !

DTA.ind ! ! ! !

<#7,0, ! ! ! !

Low, ! ! ! !

INFO_ !\Buffer_free ! ! !

REQ_PDU>!"generate ! ! !

! DTA_ACK_PDU ! ! !

INFO.ind ! ! ! !

<#7,Low> ![DTA_ACK_PDU]! ! !

<---- !(FDL_SEND_ ! ! !

! UPDATE.req) ! ! !

! ]------>!--) ! !

! [<------!--) ! !

!(FDL_SEND_ ! ! !

! UPDATE.con) ! !(FDL_DATA_ !

! !*DTA_ACK_PDU ! REPLY.ind !

! ![SRD_REQ_PDU]!<Low>) !

! ! ]------->!---->] !

! [<------!<-----------/! ! !

!(FDL_DATA_ ![SRD_RES_PDU]! v !

! REPLY.con) !*no Data !\Buffer_free !

! ! ! !

Figure 77. Master-Slave Communication Relationship / Connection for Cyclic Data

Transfer with Slave Initiative / InformationReport with low Priority

Connection for Acyclic Data Transfer with no Slave Initiative (MSAC)

Page 446

PROFIBUS-Specification-Normative-Parts-6:1997

Connections for Acyclic Data Transfer with no Slave Initiative shall be estab-

lished like all other connection oriented communication relationships using a

connection establishment service (Initiate).

During the subsequent data transfer phase all FMS and all remote FMA7 services,

for which the master is requester, are permitted on this connection. Multiple

connections for Acyclic Data Transfer with no Slave Initiative may exist to a

slave at the same time. All these connections shall use the Poll List LSAP in

the master and different LSAPs in the slave.

With the first FMS service (e.g. InformationReport.req) or the first FMA7 serv-

ice (e.g. FMA7-Read-Value.req) the LLI starts the polling of the slave

(FDL_CYC_POLL_ENTRY.req) by the Layer 2 service CSRD on the respective connec-

tion. The Layer 2 service CSRD causes a continual sending of SRD_REQ_PDUs to the

slave (polling). If the master has received the last outstanding LLI PDU, the

polling to the slave is stopped on this connection (FDL_CYC_POLL_ENTRY.req). A

new service request from FMS or FMA7 causes LLI to start the polling of the

slave again until all outstanding LLI PDUs have been transmitted from the slave

to the master.

Optionally the connection may be monitored in the master or the slave.

Connections for Acyclic Data Transfer with no Slave Initiative may be released

with the Abort service.

Confirmed FMS services:

Confirmed FMS services are services which are acknowledged by the user. The map-

ping of the confirmed FMS services onto Layer 2 is described here for the exam-

ple of the Read service. All other confirmed FMS services are mapped in the same

way.

Read service:

On a connection for Acyclic Data Transfer with no Slave Initiative the Read

service is used for reading of data from a slave. The user marks each read re-

quest (Read.req) with a special identification (Invoke ID). In this way it is

possible to relate the sent read request to the received read response. The FMS

maps each read request (Read.req) onto the LLI service primitive DTC.req. The

READ_REQ_PDU is transferred from the master to the slave with a SRD_REQ_PDU. The

resulting FDL_DATA_REPLY.ind leads to a DTC.ind from the LLI of the slave to

FMS. The FMS maps the DTC.ind onto a Read.ind to the user.

The user of the slave passes the Read.res to FMS. The FMS generates the

READ_RES_PDU and passes it with a DTC.res to LLI. The LLI stores the

READ_RES_PDU in the low priority Layer 2 update memory (FDL_REPLY_UPDATE.req

<Low>). The following SRD_REQ_PDU causes the update memory to be read. The

SRD_RES_PDU transports the data to the master. This leads to a DTC.con from LLI

to FMS in the master and then to a Read.con from FMS to the user.

If the user of the slave did not provide the data before a SRD_REQ_PDU arrives,

then the SRD_RES_PDU does not contain any data and does not lead to a DTC.con

(empty polling).

Page 447

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Responder

.

User!FMS LLI FDL BUS FDL LLI FMS!User

=====!====!=============!======.======!=============!====!=====

Read.req ! ! ! !

<#7,IVID1>! ! ! !

----> ! ! ! !

[READ_REQ_! ! ! !

PDU] ! ! ! !

DTC.req! ! ! !

<#7,0, ! ! ! !

READ_ ! ! ! !

REQ_PDU>![DTC_REQ_PDU]! ! !

---->!(FDL_SEND_ ! ! !

! UPDATE.req) ! ! !

! ]------>!--) ! !

! [<------!--) ! !

!(FDL_SEND_ ! ! !

! UPDATE.con) ! ! !

!\no outst. ! ! !

! LLI PDUs ! ! !

!"enable ! ! !

! Polling ! ! !

!(FDL_CYC_POLL! ! !

! _ENTRY.req) ! ! !

! ]------>!--) ! !

! [<------!--) ! !

!(FDL_CYC_POLL! ! !

! _ENTRY.con) !**READ_REQ_ ! !DTC.ind

Read.req ! ! PDU ! !<#8,0,

<#7/IVID2>! !*DTC_REQ_PDU !(FDL_DATA_ ! READ_

----> ! ![SRD_REQ_PDU]! REPLY.ind) ! REQ_PDU>

! ! ]------->!------------>!---->

[READ_REQ_! [<------!<-----------/! !

PDU] !(FDL_CYC_DATA![SRD_RES_PDU]! ! Read.ind

DTC.req! _REPLY.con) !*no Data ! !<#8,IVID1>

<#7,0, ! ! ! ! ----->

READ_ ! ! ! !

REQ_PDU>![DTC_REQ_PDU ! ! !

---->!(FDL_SEND_ ! ! !

! UPDATE.req) ! ! !

! ]------>!--) ! !

! [<------!--) ! !

!(FDL_SEND_ ! ! !

! UPDATE.con) !**READ_REQ_ ! !DTC.ind

! ! PDU ! !<#8,0,

! !*DTC_REQ_PDU !(FDL_DATA_ ! READ_

! ![SRD_REQ_PDU]! REPLY.ind) ! REQ_PDU>

! ! ]------->!------------>!---->

! [<------!<-----------/! !

!(FDL_CYC_DATA![SRD_RES_PDU]! ! Read.ind

! _REPLY.con) !*no Data ! !<#8,IVID2>

! ! ! ! ----->

Figure 78. Master-Slave Communication Relationship / Connection for Acyclic

Data Transfer with no Slave Initiative / parallel Read Services /

Request part

Page 448

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Responder

.

User!FMS LLI FDL BUS FDL LLI FMS!User

=====!====!=============!======.======!=============!====!=====

! ! ! ! Read.res

! ! ! !<#8,IVID1>

! ! ! ! <----

! ! ! ![READ_RES_

! ! ! ! PDU]

! ! ! !DTC.res

! ! ! !<#8,0,

! ! ! ! READ_

! ! ![DTC_RES_PDU]! RES_PDU>

! ! !(FDL_REPLY_ !<----

! ! ! UPDATE.req !

! ! ! <Low>) !

! ! (--!<------[ !

! ! (--!------>] !

! ! !(FDL_REPLY_ ! Read.res

! ! ! UPDATE.con) !<#8,IVID2>

! !*no Data !(FDL_DATA_ ! <----

! ![SRD_REQ_PDU]! REPLY.ind) !

! ! ]------->!----->] ![READ_RES_

<----!<------------!<-----------/! ! PDU]

DTC.con !(FDL_CYC_DATA![SRD_RES_PDU]! !DTC.res

<#7,0, ! _REPLY.con) !*DTC_RES_PDU ! !<#8,0,

READ_ ! !**READ_RES_ ! ! READ_

RES_PDU>! ! PDU ! ! RES_PDU>

<---- ! ! ![DTC_RES_PDU]!<----

Read.con ! ! !(FDL_REPLY_ !

<#7,IVID1>! ! ! UPDATE.req !

! ! ! <Low>) !

! ! (--!<------[ !

! ! (--!------>] !

! ! !(FDL_REPLY_ !

! ! ! UPDATE.con) !

! !*no Data !(FDL_DATA_ !

! ![SRD_REQ_PDU]! REPLY.ind) !

! ! ]------->!----->] !

<----!<------------!<-----------/! !

DTC.con !(FDL_CYC_DATA![SRD_RES_PDU]! !

<#7,0, ! _REPLY.con) !*DTC_RES_PDU ! !

READ_ ! !**READ_RES_ ! !

RES_PDU>!\no outst. ! PDU ! !

<---- ! LLI PDUs ! ! !

Read.con !"disable ! ! !

<#7,IVID2>! Polling ! ! !

!(FDL_CYC_POLL! ! !

! _ENTRY.req) ! ! !

! ]------>!--) ! !

! [<------!--) ! !

!(FDL_CYC_POLL! ! !

! _ENTRY.con) ! ! !

Figure 79. Master-Slave Communication Relationship / Connection for Acyclic

Data Transfer with no Slave Initiative / parallel Read Services /

Response part

Page 449

PROFIBUS-Specification-Normative-Parts-6:1997

Unconfirmed FMS services with requester = master:

Unconfirmed FMS services are services which are not acknowledged by the user.

For these services low or high priority may be used. The mapping of the uncon-

firmed FMS services onto Layer 2 is described here for the example of the Infor-

mationReport service. All other unconfirmed FMS services are mapped in the same

way.

InformationReport service:

On a connection for Acyclic Data Transfer with no Slave Initiative the Informa-

tionReport service is used for a single writing of data into a slave. The FMS

maps each request (InformationReport.req) onto the LLI service primitive

DTA.req. The priority chosen by the user of the master is transferred transpar-

ently. The LLI maps a DTA.req with high priority onto the Layer 2 service SRD

with high priority. The LLI maps a DTA.req with low priority onto the Layer 2

service CSRD. Each request causes a transmission of the INFORMATION-

REPORT_REQ_PDU with a SRD_REQ_PDU from the master to the slave. The resulting

FDL_DATA_REPLY.ind leads to a DTA.ind from the LLI of the slave to FMS. The FMS

maps this indication onto an InformationReport.ind and passes it to the user.

The SRD_REQ_PDU causes the update memory in the slave to be read. If there is

data available (e.g. READ_RES_PDU), this data is transported to the master with

the SRD_RES_PDU. If there is no data available in the update memory, then the

SRD_RES_PDU contains no data and does not lead to a confirmation to FMS.

If there is memory available again (Buffer_free) for the LLI of the slave to re-

ceive another DTA_REQ_PDU, the LLI generates a DTA_ACK_PDU to signal this to the

LLI of the master. The LLI stores the DTA_ACK_PDU into the high or low priority

Layer 2 update memory (FDL_REPLY_UPDATE.req <Low/High>) corresponding to the

priority with which the DTA_REQ_PDU has been passed to LLI by the Layer 2. The

following SRD_REQ_PDU causes the update memory to be read. The SRD_RES_PDU

transports the DTA_ACK_PDU to the LLI of the master. This does not lead to a

confirmation to FMS.

Page 450

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Receiver

.

User!FMS LLI FDL BUS FDL LLI FMS!User

=====!====!=============!======.======!=============!====!=====

INFO.req ! ! ! !

<#7,High> ! ! ! !

----> ! ! ! !

[INFO_REQ_! ! ! !

PDU] ! ! ! !

DTA.req ! ! ! !

<#7,0, ! ! ! !

High,INFO! ! ! !

_REQ_PDU>! ! ! !

---->![DTA_REQ_PDU]! ! !

!\no outst. ! ! !

! LLI PDUs ! ! !

!"enable ! ! !

! Polling ! ! !

!(FDL_CYC_POLL! ! !

! _ENTRY.req) ! ! !

! ]------>!--) ! !

! [<------!--) ! !

!(FDL_CYC_POLL! ! !

! _ENTRY.con) ! ! !DTA.ind

! !**INFO_REQ_ ! !<#8,0,

!(FDL_DATA_ ! PDU !(FDL_DATA_ ! High,

! REPLY.req !*DTA_REQ_PDU ! REPLY.ind ! INFO_

! <High>) ![SRD_REQ_PDU]!<High>) ! REQ_PDU>

! ]------>!------------>!------------>!---->

! [<------!<-----------/! !

!(FDL_DATA_ ![SRD_RES_PDU]! ! INFO.ind

INFO.req ! REPLY.con) !*no Data ! ! <#8,High>

<#7,High> ! ! ! ! ---->

----> ! ! ! !

[INFO_REQ ! ! ! !

PDU] ! ! ! !

DTA.req ! ! ! !

<#7,0, ! ! ! !

High,INFO! ! ! !

_REQ_PDU>! ! ! !

---->![DTA_REQ_PDU]! ! !DTA.ind

! !**INFO_REQ_ ! !<#8,0,

!(FDL_DATA_ ! PDU !(FDL_DATA_ ! High,

! REPLY.req !*DTA_REQ_PDU ! REPLY.ind ! INFO_

! <High>) ![SRD_REQ_PDU]!<High>) ! REQ_PDU>

! ]------>!------------>!------------>!---->

! [<------!<-----------/! !

!(FDL_DATA_ ![SRD_RES_PDU]! ! INFO.ind

! REPLY.con) !*no Data ! ! <#8,High>

! ! ! ! ---->

! ! ! !

Figure 80. Master-Slave Communication Relationship / Connection for Acyclic

Data Transfer with no Slave Initiative / parallel InformationReport

Services with high Priority / Request part

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

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