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

Page 431

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Responder

.

User!FMS LLI FDL BUS FDL LLI FMS!User

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

! ! ! !DTC.ind

! ! ! !<#8,0,

! !*no Data !(FDL_DATA_ !READ_

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

! _REPLY.con) ! ]------->!----> !----->!---->

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

! : ![SRD_RES_PDU]!"recall PDU ! Read.ind

!"store PDU !*DTC_RES_PDU ! : !<#8,IVID1>

! v !**READ_RES_ !*****IDM*****! ---->

!*****IDM*****! PDU !#8: READ_REQ !

!#7: READ_RES ! !*************!

!*************! ! !

! !*no Data ! !

! ![SRD_REQ_PDU]! !

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

! ![<---------/ ! ! Read.res

! ![SRD_RES_PDU]! !<#8,IVID1>

! !*no Data ! ! <----

! ! ! !

! ! ! ![READ_RES_

! ! ! ! PDU]

! ! ! !

! ! ! !DTC.res

! ! ! !<#8,0,

! ! ! !READ_

! ! ! !RES_PDU>

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

! ! !(FDL_REPLY_ !

! ! ! UPDATE.req !

! ! ! <Low>) !

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

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

! ! !(FDL_REPLY_ !

! ! ! UPDATE.con) !DTC.ind

! ! ! !<#8,0,

! !*no Data !(FDL_DATA_ !READ_

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

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

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

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

! REPLY.con) !*DTC_RES_PDU ! : !<#8,IVID1>

! : !**READ_RES_ !*****IDM*****! ---->

!"store PDU ! PDU !#8: READ_REQ !

! v ! !*************!

!*****IDM*****! ! !

!#7: READ_RES ! ! !

!*************! ! !

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

Transfer with no Slave Initiative / no Values from Slave between

SRD_REQ_PDUs

Page 432

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Responder

.

User!FMS LLI FDL BUS FDL LLI FMS!User

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

Read.req ! ! ! !

<#7/IVID1>! ! ! !

----> ! ! ! !

\old IVID ! ! ! !

[READ_REQ_! ! ! !

PDU] ! ! ! !

DTC.req !*****IDM*****! ! !

<#7,0 !#7: IVID1 ! ! !

READ_ !*************! ! !

REQ_PDU>! ! ! !

---->!\IVID ident. ! ! !

! ! ! !

!*****IDM*****! ! !

!#7: READ_RES ! ! !

!*************! ! !

! : ! ! !

!"recall PDU ! ! !

! v ! ! !

<----!<-----+ ! ! !

DTC.con ! ! ! !

<#7,0, ! ! ! !

READ_ ! ! ! !

RES_PDU>! ! ! !

<---- ! ! ! !

Read.con ! ! ! !

<#7/IVID1>! ! ! !

! ! ! !

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

Transfer with no Slave Initiative / nth Read with the same Invoke ID

Write service:

On a connection for Cyclic Data Transfer with no Slave Initiative the Write

service is used for cyclical writing of data into a slave. For each connection

only one write request (Write.req) is permissible at a time. The user marks each

write request with a special identification (Invoke ID). In this way it is pos-

sible to relate the sent write request to the received write confirmation

(Write.con). FMS maps a write request (Write.req) from the user onto the LLI

service primitive DTC.req. The Invoke ID is stored in the IDM in the LLI of the

master. Each write request results in a transmission of the WRITE_REQ_PDU from

the master to the slave. A changed write request shall differ from the old re-

quest in its Invoke ID. Write requests on this connection with the same Invoke

ID cause the write confirmation to be read out of the IDM in the LLI of the mas-

ter after the next FDL_CYC_DATA_REPLY.con. A WRITE_REQ_PDU is sent in this case.

The received write request (WRITE_REQ_PDU) is stored in the IDM of the slave

specific to the connection. Each received WRITE_REQ_PDU overwrites the

WRITE_REQ_PDU stored in the IDM of the slave.

The Layer 2 service CSRD in the master causes a continual sending of

SRD_REQ_PDUs to the slave (polling). For each write request the

FDL_DATA_REPLY.ind contains a WRITE_REQ_PDU. This PDU is stored in the LLI and

the FMS receives a DTC.ind. The FMS maps the DTC.ind onto a Write.ind and passes

it to the user. When the user of the slave has given the Write.res to the FMS,

the FMS generates a WRITE_RES_PDU and passes it to the LLI with a DTC.res. The

LLI writes the WRITE_RES_PDU into 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 WRITE_RES_PDU to the master. After

reading the update memory (FDL_DATA_REPLY.ind) the LLI passes the stored

Page 433

PROFIBUS-Specification-Normative-Parts-6:1997

WRITE_REQ_PDU with a DTC.ind to the FMS. If the user of the slave cannot provide

the WRITE_RES_PDU before a SRD_REQ_PDU arrives, then the SRD_RES_PDU does not

contain a WRITE_RES_PDU (empty polling).

The LLI of the master checks the Invoke ID of a received WRITE_RES_PDU. For a

write request with a changed Invoke ID this PDU is ignored, if the Invoke ID is

not identical with that of the sent write request. For a write request with an

unchanged Invoke ID this leads to a connection release by the LLI. If the Invoke

ID is identical, the received PDU is stored in the IDM. The first PDU received

with the identical Invoke ID is passed to the FMS with a DTC.con. The FMS maps

the DTC.con onto a Write.con.

The proper execution is controlled by the connection monitoring.

Depending on the actualization of the IDM and the frequency of the Write.req re-

quests in the master different communication characteristics arise:

a) If the write confirmations in the IDM are more often actualized than the user

of the master reads it, then the write confirmations in the IDM, which are

not read, will be overwritten.

b) If the write confirmations in the IDM are actualized less often than the user

of the master reads it, then the user is given the same write confirmation

repeatedly.

c) If the user of the master makes the data available between two SRD_REQ_PDUs,

then the data is transmitted within the SRD_REQ_PDU (synchronous update).

If the user of the master can make the data available repeatedly between two

SRD_REQ_PDUs, then the last recorded data is transmitted in the SRD_REQ_PDU,

only if provided for in the realisation of Layer 2 and Layer 7. The necessary

functions are not described here.

d) If the user of the master makes no data available between two SRD_REQ_PDUs,

then the SRD_REQ_PDU is transmitted without any data.

Page 434

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Responder

.

User!FMS LLI FDL BUS FDL LLI FMS!User

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

Write.req ! !*no Data ! !

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

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

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

[WRITE_REQ! ![SRD_RES_PDU]! !

_PDU] ! !*no Data ! !

! ! ! !

DTC.req ! ! ! !

<#7,0, ! ! ! !

WRITE_ !"store IVID1 ! ! !

_REQ_PDU>!*****IDM*****! ! !

---->!#7: IVID1 ! ! !

!*************! ! !

! ! ! !

![DTC_REQ_PDU]! ! !

! ! ! !

!(FDL_SEND_ ! ! !

! UPDATE.req) ! ! !

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

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

!(FDL_SEND_ ! ! !

! UPDATE.con) ! ! !

! ! ! !

! !**WRITE_REQ_ ! !DTC.ind

! ! PDU ! !<#8,0,

! !*DTC_REQ_PDU !(FDL_DATA_ ! WRITE_

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

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

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

!(FDL_CYC_DATA![SRD_RES_PDU]!"store PDU ! Write.ind

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

! ! !*****IDM*****! ---->

! ! !#8: WRITE_REQ!

! !*no Data !*************!

! ![SRD_REQ_PDU]! !

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

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

! ![SRD_RES_PDU]! !

! !*no Data ! !

! ! ! !

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

Transfer with no Slave Initiative / first Write or Write with

changed Invoke ID / Request part

Page 435

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Responder

.

User!FMS LLI FDL BUS FDL LLI FMS!User

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

! ! ! ! Write.res

! ! ! !<#8,IVID1>

! ! ! ! <----

! ! ! !

! ! ! ![WRITE_

! ! ! ! RES_PDU]

! ! ! !

! ! ! !DTC.res

! ! ! !<#8,0,

! ! ! ! WRITE_

! ! ! ! RES_PDU>

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

! ! ! !

! ! !(FDL_REPLY_ !

! ! ! UPDATE.req !

! ! ! <Low>) !

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

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

! ! !(FDL_REPLY_ !

! ! ! UPDATE.con) !DTC.ind

! ! ! !<#8,0,

! !*no Data !(FDL_DATA_ ! WRITE_

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

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

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

DTC.con!(FDL_CYC_DATA![SRD_RES_PDU]!"recall PDU ! Write.ind

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

WRITE_ ! : !**WRITE_RES_ ! : ! ---->

_RES_PDU>! : ! PDU !*****IDM*****!

!"store PDU ! !#8: WRITE_REQ!

<---- ! v ! !*************!

Write.con !*****IDM*****! ! !

<#7,IVID1>!#7: WRITE_RES! ! !

!*************! ! !

! ! ! !

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

Transfer with no Slave Initiative / first Write or Write with

changed Invoke ID / Response part

Page 436

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Responder

.

User!FMS LLI FDL BUS FDL LLI FMS!User

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

! ! ! !DTC.ind

! ! ! !<#8,0,

! !*no Data !(FDL_DATA_ ! WRITE_

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

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

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

!(FDL_CYC_DATA![SRD_RES_PDU]!"recall PDU ! Write.ind

! REPLY.con) !*DTC_REQ_PDU ! : !<#8,IVID1>

! : !**WRITE_RES_ !*****IDM*****! ---->

!"store PDU ! PDU !#8: WRITE_REQ!

! v ! !*************! Write.res

!*****IDM*****! ! !<#8,IVID1>

!#7: WRITE_RES! ! ! <----

!*************! ! !

! ! ! ![WRITE_

! ! ! ! RES_PDU]

! ! ! !

! ! ! !DTC.res

! ! ! !<#8,0,

! ! ! ! WRITE_

! ! ! ! RES_PDU>

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

! ! ! !

! ! !(FDL_REPLY_ !

! ! ! UPDATE.req !

! ! ! <Low>) !

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

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

! ! !(FDL_REPLY_ !

! ! ! UPDATE.con) !DTC.ind

! ! ! !<#8,0,

! !*no Data !(FDL_DATA_ ! WRITE_

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

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

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

!(FDL_CYC_DATA![SRD_RES_PDU]!"recall PDU ! Write.ind

! REPLY.con) !*DTC_RES_PDU ! : !<#8,IVID1>

! : !**WRITE_RES_ !*****IDM*****! ---->

!"store PDU ! PDU !#8: WRITE_REQ!

! v ! !*************!

!*****IDM*****! ! !

!#7: WRITE_RES! ! !

!*************! ! !

! ! ! !

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

Transfer with no Slave Initiative / new Write Response from Slave /

no Request from Master

Page 437

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Responder

.

User!FMS LLI FDL BUS FDL LLI FMS!User

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

! ! ! !DTC.ind

! ! ! !<#8,0,

! !*no Data !(FDL_DATA_ ! WRITE_

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

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

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

!(FDL_CYC_DATA![SRD_RES_PDU]!"recall PDU ! Write.ind

! REPLY.con) !*DTC_RES_PDU ! : !<#8,IVID1>

! : !**WRITE_RES_ !*****IDM*****! ---->

!"store PDU ! PDU !#8: WRITE_REQ!

! v ! !*************!

!*****IDM*****! ! !

!#7: WRITE_RES! ! !

!*************! ! !

! !*no Data ! !

! ![SRD_REQ_PDU]! !

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

! ![<---------/ ! ! Write.res

! ![SRD_RES_PDU]! !<#8,IVID1>

! !*no Data ! ! <----

! ! ! !

! ! ! ![WRITE_

! ! ! ! RES_PDU]

! ! ! !

! ! ! !DTC.res

! ! ! !<#8,0,

! ! ! ! WRITE_

! ! ![DTC_RES_PDU]! RES_PDU>

! ! ! !<----

! ! !(FDL_REPLY_ !

! ! ! UPDATE.req !

! ! ! <Low>) !

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

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

! ! !(FDL_REPLY_ !

! ! ! UPDATE.con) !DTC.ind

! ! ! !<#8,0,

! !*no Data !(FDL_DATA_ ! WRITE_

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

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

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

!(FDL_CYC_DATA![SRD_RES_PDU]!"recall PDU ! Write.ind

! REPLY.con) !*DTC_RES_PDU ! : !<#8,IVID1>

! : !**WRITE_RES_ !*****IDM*****! ---->

!"store PDU ! PDU !#8: WRITE_REQ!

! v ! !*************!

!*****IDM*****! ! !

!#7: WRITE_RES! ! !

!*************! ! !

! ! ! !

Figure 71. Master-Slave Commun. Relationship / Connection for Cyclic Data

Transfer with no Slave Initiative / no Write Response from Slave

between SRD_REQ_PDUs

Page 438

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Responder

.

User!FMS LLI FDL BUS FDL LLI FMS!User

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

Write.req ! ! ! !

<#7,IVID1>! ! ! !

----> ! ! ! !

\old IVID ! ! ! !

! ! ! !

[WRITE_REQ! ! ! !

_PDU] ! ! ! !

! ! ! !

DTC.req! ! ! !

<#7,0, ! ! ! !

WRITE_ ! ! ! !

REQ_PDU>!\IVID ident. ! ! !

---->!*****IDM*****! ! !

!#7: WRITE_RES! ! !

!*************! ! !

! : ! ! !

!"recall PDU ! ! !

! v ! ! !

<----!<-----+ ! ! !

DTC.con! ! ! !

! ! ! !

<#7,0, ![DTC_REQ_PDU]! ! !

WRITE_ ! ! ! !

RES_PDU>!(FDL_SEND_ ! ! !

! UPDATE.req) ! ! !

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

Write.con ! [<------!--) ! !

<#7,IVID1>!(FDL_SEND_ ! ! !

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

! ! PDU ! !<#8,0,

! !*DTC_REQ_PDU !(FDL_DATA_ ! WRITE_

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

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

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

!(FDL_CYC_DATA![SRD_RES_PDU]!"store PDU ! Write.ind

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

! ! !*****IDM*****! ---->

! ! !#8: WRITE_REQ!

! ! !*************!

! ! ! !

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

Transfer with no Slave Initiative / Write with the same Invoke ID /

Request part

Page 439

PROFIBUS-Specification-Normative-Parts-6:1997

Master/Requester . Slave/Responder

.

User!FMS LLI FDL BUS FDL LLI FMS!User

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

! ! ! ! Write.res

! ! ! !<#8,IVID1>

! ! ! ! <----

! ! ! !

! ! ! ![WRITE_RES

! ! ! ! PDU]

! ! ! !

! ! ! !DTC.res

! ! ! !<#8,0,

! ! ! ! WRITE_

! ! ! ! RES_PDU>

! ! ! !<----

! ! ![DTC_RES_PDU]!

! ! ! !

! ! !(FDL_REPLY_ !

! ! ! UPDATE.req !

! ! ! <Low>) !

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

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

! ! !(FDL_REPLY_ !

! ! ! UPDATE.con) !DTC.ind

! ! ! !<#8,0,

! !*no Data !(FDL_DATA_ ! WRITE_

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

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

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

!(FDL_CYC_DATA![SRD_RES_PDU]!"recall PDU ! Write.ind

! REPLY.con) !*DTC_RES_PDU ! : !<#8,IVID1>

! : !**WRITE_RES_ !*****IDM*****! ---->

!"store PDU ! PDU !#8: WRITE_REQ!

! v ! !*************!

!*****IDM*****! ! !

!#7: WRITE_RES! ! !

!*************! ! !

! ! ! !

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

Transfer with no Slave Initiative / Write with the same Invoke ID /

Response part

Page 440

PROFIBUS-Specification-Normative-Parts-6:1997

Unconfirmed FMS services with requester = master:

Unconfirmed FMS services are services which are not confirmed by the user. For

these services low or high priority may be used. The mapping of the unconfirmed

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

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

InformationReport service:

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

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

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

ority chosen by the user of the master is transferred transparently. The LLI

maps a DTA.req with high priority onto the Layer 2 service SRD with high prior-

ity. 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. 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 in 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 was passed to LLI by the Layer 2. The fol-

lowing SRD_REQ_PDU causes the update memory to be read. The SRD_RES_PDU trans-

ports the DTA_ACK_PDU to the LLI of the master. This does not lead to a confir-

mation to FMS.

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

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