Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 581
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
6.7.4.2 State Diagram for DTU Receiver (Master or Slave)
LLI start routine
DTU_REQ_PDU received
(SDN.ind)
DTU.ind to LLI user
1: FDL primitive AND NOT SDN.ind
2: SDN.ind AND NOT DTU_REQ_PDU
1: LLI Fault.ind
2: i
g
nore
RECEIVER
CONLS-
Figure 124. State Diagram for DTU Receiver (Master or Slave)
Description of State Transitions for DTU Receiver at the Master or Slave
DTU Receiver at the Master or Slave
Current State Transition Next State
Event
\Exit Condition
=> Action Taken
CONLS-RECEIVER CONLS_SE 1 CONLS-RECEIVER
DTU_REQ_PDU received (SDN.ind)
\CONLS
=> DTU.ind to LLI user
CONLS-RECEIVER CONLS_SE 2 CONLS-RECEIVER
FDL primitive AND NOT SDN.ind
\CONLS
=> LLI-Fault.ind <RC = LLI_FMA7_RC7,
AD = code of the primitive>
CONLS-RECEIVER CONLS_SE 3 CONLS-RECEIVER
SDN.ind AND NOT DTU_REQ_PDU
\CONLS
=> ignore data
Page 582
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
This page is intentionally left blank.
Page 583
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
6.7.5 Overview of Layer 2 Services, Primitives and PDUs used by LLI
Depending on the types of communication relationships and LLI services which are
supported by the LLI, the implementation of the related Layer 2 services and
their primitives is mandatory in the Layer 2 protocol. These mandatory services
and primitives are specified in the following tables.
The FMA1/2 services used by LLI do not depend on the types of communication re-
lationships and LLI services supported. The implementation of these FMA1/2 serv-
ices is mandatory in FMA1/2.
Table 24. Send Data with No Acknowledge (SDN)
! Slave ! Master !
! ! !
! service primitive ! service primitive !
+-------------------------------+-------------------------------+
! ! FDL_DATA.req (SDN.req) !
! ! FDL_DATA.con (SDN.con) !
! FDL_DATA.ind (SDN.ind) ! FDL_DATA.ind (SDN.ind) !
+-------------------------------+-------------------------------+
PDU: [ SDN_REQ_PDU ]
Table 25. Send Data with Acknowledge (SDA)
! Slave ! Master !
! ! !
! service primitive ! service primitive !
+-------------------------------+-------------------------------+
! ! FDL_DATA_ACK.req (SDA.req) !
! ! FDL_DATA_ACK.con (SDA.con) !
! ! FDL_DATA_ACK.ind (SDA.ind) !
+-------------------------------+-------------------------------+
PDUs: [ SDA_REQ_PDU ] [ SDA _ACK_PDU]
In the formal descriptions of the LLI state machines, the abbreviations shown in
round brackets are used for the service primitives.
Table 26. Send and Request Data (SRD)
! Slave ! Master !
! ! !
! service primitive ! service primitive !
+-------------------------------+-------------------------------+
! ! FDL_DATA_REPLY.req (SRD.req) !
! ! FDL_DATA_REPLY.con (SRD.con) !
! FDL_DATA_REPLY.ind (SRD.ind) ! !
! FDL_REPLY_UPDATE.req ! !
! (UPDATE.req) ! !
! FDL_REPLY_UPDATE.con ! !
! (UPDATE.con) ! !
+-------------------------------+-------------------------------+
PDUs: [ SRD_REQ_PDU ] [ SRD_RES_PDU ]
Page 584
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
Table 27. Cyclic Send and Request Data (CSRD)
! Slave ! Master !
! ! !
! service primitive ! service primitive !
+-------------------------------+-------------------------------+
! ! FDL_SEND_UPDATE.req !
! ! (S_UPDATE.req)!
! ! FDL_SEND_UPDATE.con !
! ! (S_UPDATE.con)!
! ! FDL_CYC_DATA_REPLY.req !
! ! (CSRD.req)!
! ! FDL_CYC_DATA_REPLY.con !
! ! (CSRD.con)!
! ! FDL_CYC_ENTRY.req (ENTRY.req)!
! ! FDL_CYC_ENTRY.con (ENTRY.con)!
! ! FDL_CYC_DEACT.req (DEACT.req)!
! ! FDL_CYC_DEACT.con (DEACT.con)!
! FDL_DATA_REPLY.ind (SRD.ind)! !
! FDL_REPLY_UPDATE.req ! !
! (UPDATE.req)! !
! FDL_REPLY_UPDATE.con ! !
! (UPDATE.con)! !
+-------------------------------+-------------------------------+
PDUs: [ SRD_REQ_PDU ] [ SRD_RES_PDU ]
Table 28. (R)SAP Activate/SAP Deactivate FMA1/2
! Slave/Master !
! !
! service primitive !
+---------------------------------------------+
! FMA1/2_SAP_ACTIVATE.req (SAP_ACT.req) !
! FMA1/2_SAP_ACTIVATE.con (SAP_ACT.con) !
! FMA1/2_RSAP_ACTIVATE.req (RSAP_ACT.req) !
! FMA1/2_RSAP_ACTIVATE.con (RSAP_ACT.con) !
! FMA1/2_SAP_DEACTIVATE.req (SAP_DEACT.req) !
! FMA1/2_SAP_DEACTIVATE.con (SAP_DEACT.con) !
+---------------------------------------------+
Page 585
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
6.7.6 Mapping of all LLI Services onto Layer 2 Services as a function of Commu-
nication Relationships
Legend for the following four tables:
c : service confirmed
a : service acknowledged by LLI
u : service unconfirmed
L : priority = Low
H : priority = High
The slave is not able to distinct between the CSRD and SRD services.
Table 29. Services on Master-Slave Connections with Slave Initiative
! ! ! Slave ! Master !
! Services!c/a/u!Requester!Responder!Requester!Responder!
+---------+-----+---------+---------+---------+---------+
! DTC ! c ! -- ! (C)SRD ! CSRD ! -- !
+---------+-----+---------+---------+---------+---------+
! ! L ! a ! (C)SRD ! (C)SRD ! CSRD ! CSRD !
! DTA +---+-----+---------+---------+---------+---------+
! ! H ! a ! (C)SRD ! SRD ! SRD ! CSRD !
+---------+-----+---------+---------+---------+---------+
! ASS ! c ! -- ! (C)SRD ! CSRD ! -- !
+---------+-----+---------+---------+---------+---------+
! ABT ! u ! (C)SRD ! (C)SRD ! CSRD ! CSRD !
+---------+-----+---------+---------+---------+---------+
Table 30. Services on Master-Slave Connections with no Slave Initiative
! ! ! Slave ! Master !
! Services!c/a/u!Requester!Responder!Requester!Responder!
+---------+-----+---------+---------+---------+---------+
! DTC ! c ! -- ! (C)SRD ! CSRD ! -- !
+---------+-----+---------+---------+---------+---------+
! ! L ! a ! -- ! (C)SRD ! CSRD ! -- !
! DTA +---+-----+---------+---------+---------+---------+
! ! H ! a ! -- ! SRD ! SRD ! -- !
+---------+-----+---------+---------+---------+---------+
! ASS ! c ! -- ! (C)SRD ! CSRD ! -- !
+---------+-----+---------+---------+---------+---------+
! ABT ! u ! (C)SRD ! (C)SRD ! CSRD ! CSRD !
+---------+-----+---------+---------+---------+---------+
Page 586
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
Table 31. Services on Master-Master Connections
! ! ! Master !
! Services!c/a/u!Requester!Responder!
+---------+-----+---------+---------+
! DTC ! c ! SDA ! SDA !
+---------+-----+---------+---------+
! ! L ! a ! SDA ! SDA !
! DTA +---+-----+---------+---------+
! ! H ! a ! SDA ! SDA !
+---------+-----+---------+---------+
! ASS ! c ! SDA ! SDA !
+---------+-----+---------+---------+
! ABT ! u ! SDA ! SDA !
+---------+-----+---------+---------+
Table 32. Services on connectionless Communication Relationships
! ! ! Slave ! Master !
! Service !c/a/u!Requester!Receiver!Requester!Receiver!
+---------+-----+---------+--------+---------+--------+
! ! L ! u ! --- ! SDN ! SDN ! SDN !
! DTU +---+-----+---------+--------+---------+--------+
! ! H ! u ! --- ! SDN ! SDN ! SDN !
+---------+-----+---------+--------+---------+--------+
6.7.7 Abort Reason Codes
This clause contains definitions for the meaning and generation of the parame-
ters identifier (ID), locally generated (LG), reason code (RC) and additional
detail (AD) for the LLI abort service (ABT).
6.7.7.1 Locally initiated Connection Abort
The reason for a locally generated connection abort may arise at the local user,
the local FMS or FMA7, the local LLI or the local Layer 2. If the local LLI ini-
tiates the connection abort (failure at the local LLI or the local Layer 2), the
parameter LG of the ABT.ind, which is issued to the local user, shall be true.
If the connection abort is initiated by the local user (parameter ID = user), or
from the local FMS or FMA7 (parameter ID = LLI user), the value of the parameter
RC, which is delivered from the LLI user to LLI, shall be encoded by LLI (see
section 4.5) and entered into the ABT_REQ_PDU. If in addition the LLI user de-
livers the parameter AD to LLI, then LLI shall enter this parameter into the
ABT_REQ_PDU.
If the reason for the connection abort is located in LLI (parameter ID = LLI),
the field reason code may take the values defined in Table 110. Depending on the
reason code, the field AD may contain additional information.
If the reason for the connection abort is due to a failure in the local Layer 2,
the parameter ID shall contain the value "Layer 2". In this case the parameter
reason code of the ABT.ind may take the following values:
RR, LR, NA, RDL, RDH, LS, IV, OK, NO, DS, RS, UE.
The meaning of these reason codes is defined in the PROFIBUS Data Link Layer.
The parameter AD shall contain additional information about the service which
failed. The parameter AD may take the following values:
Page 587
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
Table 33. Parameters AD (local)
+==============+===============================================+
! Code ! Meaning !
+==============+===============================================+
! ABT_AD1 ! Error in the loading of the UPDATE buffer !
! ! (S_UPDATE.con/UPDATE.con) !
! ABT_AD2 ! Error in the activation of a Poll List !
! ! entry (Entry.con) !
! ABT_AD3 ! Error in the deactivation of a Poll List !
! ! entry (Entry.con) !
! ABT_AD4 ! Error on transmission (SDA.con) !
! ABT_AD5 ! Error on transmission (CSRD.con) !
! ABT_AD6 ! Error on transmission (SRD.con) !
! ABT_AD7 ! Error on receipt (CSRD.con) !
+==============+===============================================+
6.7.7.2 Remotely initiated Connection Abort
A remotely initiated connection abort may be generated by the remote user (pa-
rameter ID = user), the remote FMS or FMA7 (parameter ID = LLI user), the remote
LLI (parameter ID = LLI) or the remote Layer 2 (parameter ID = Layer 2). In
these cases the local LLI receives an ABT_REQ_PDU from the remote LLI. Then the
local LLI shall assign the value "false" to the parameter LG and enter it into
the ABT.ind to be issued to the local LLI user.
If the connection abort is initiated by the remote user or remote LLI user, the
LLI shall decode the value of the parameter RC (see section 4.5), which is con-
tained in the ABT_REQ_PDU. The LLI shall transfer this value, together with the
parameters ID and AD which are also contained in the ABT_REQ_PDU, to the local
LLI user.
If the connection abort is initiated by the remote LLI, the values for the pa-
rameters RC and AD are defined as in the table below.
Is the reason for the connection abort is due to a failure in the remote Layer
2, the parameter reason code (RC) may take the following values:
RR, LR, NA, RDL, RDH.
The meaning of these reason codes is defined in the PROFIBUS Data Link Layer. In
this case the field AD shall be omitted.
Page 588
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
6.7.7.3 Reason Codes of LLI for the Abort.indication
Table 34. Abort Reason Codes (local and remote) for ABT.ind with Identifier =
LLI
+==========+===================================================+
! ! LG = false -------+!
! Code ! Meaning LG = true -----+ !!
! ! v v!
+==========+===============================================+=+=+
! ABT_RC1 ! LLI-LLI context check negative ! !x!
! ! AD contains the remote LLI context ! ! !
! ABT_RC2 ! Unallowed LLI PDU received in the connec- !x!x!
! ! tion establishment phase or release phase ! ! !
! ABT_RC3 ! Unallowed LLI PDU received in the data !x!x!
! ! transfer phase ! ! !
! ABT_RC4 ! Unknown or faulty LLI PDU received !x!x!
! ABT_RC5 ! DTA_ACK_PDU received and SAC = 0 !x!x!
! ABT_RC6 ! Number of parallel services exceeded !x!x!
! ! (LLI PDU received) ! ! !
! ABT_RC7 ! Invoke ID unknown !x!x!
! ABT_RC8 ! Priority error !x!x!
! ABT_RC9 ! Local error in the remote Station !x!x!
! ABT_RC10 ! Timer T1 expired (connection establishment) !x!x!
! ABT_RC11 ! Timer T3 expired (connection monitoring) !x!x!
! ABT_RC12 ! RTimer expired !x!x!
! ABT_RC13 ! Error in the LSAP activation (.con(-)) !x! !
! ! AD contains the error status ! ! !
! ABT_RC14 ! Unallowed FDL primitive in the connection !x! !
! ! establishment phase or release phase ! ! !
! ! AD contains the code of the primitive ! ! !
! ABT_RC15 ! Unallowed FDL primitive in the data !x! !
! ! transfer phase ! ! !
! ! AD contains the code of the primitive ! ! !
! ABT_RC16 ! Unknown FDL primitive !x! !
! ABT_RC17 ! Unknown LLI primitive !x! !
! ABT_RC18 ! Unallowed LLI primitive in the connection !x! !
! ! establishment phase or release phase ! ! !
! ! AD contains the code of the primitive ! ! !
! ABT_RC19 ! Unallowed LLI primitive in the data !x! !
! ! transfer phase ! ! !
! ! AD contains the code of the primitive ! ! !
! ABT_RC20 ! CRL entry not OK !x! !
! ABT_RC21 ! Conflict case in the connection establishment !x! !
! ! phase: local address > remote address ! ! !
! ABT_RC22 ! Execution error in cyclic data transfer !x!x!
! ABT_RC23 ! Number of parallel services exceeded !x! !
! ! (Request from FMS) ! ! !
! ABT_RC24 ! CRL is being loaded by FMA7, LLI disabled !x!x!
! ABT_RC25 ! Confirm / indication mode error !x! !
! ABT_RC26 ! Unallowed FMA1/2 primitive received !x! !
! ABT_RC27 ! Unallowed FMS service on connection for !x!x!
! ! cyclic data transfer ! ! !
! ABT_RC28 ! FMS PDU size exceeded on connection for !x!x!
! ! cyclic data transfer ! ! !
+==========+===============================================+=+=+
Page 589
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
6.7.8 Reason Codes for the LLI-Fault.indication
Table 35. Reason Codes for LLI-Fault.ind
+===============+===============================================+
! Code ! Meaning !
+===============+===============================================+
! LLI_FMA7_RC1 ! FMA1/2_(R)SAP_ACTIVATE.con (NO/IV) !
! ! AD contains the M_status !
! LLI_FMA7_RC2 ! FMA1/2_SAP_DEACTIVATE.con (NO/IV) !
! ! AD contains the M_status !
! LLI_FMA7_RC3 ! FDL_SEND_UPDATE.con (LS/LR/IV)/ !
! ! FDL_REPLY_UPDATE.con (LS/LR/IV) !
! ! AD contains the L_status !
! LLI_FMA7_RC4 ! FDL_CYC_ENTRY.con (LS/IV/NO) (activation) !
! ! AD contains the L_status !
! LLI_FMA7_RC5 ! FDL_CYC_ENTRY.con (LS/IV/NO) (deactivation) !
! ! AD contains the L_status !
! LLI_FMA7_RC6 ! Unallowed FDL primitive in the connection !
! ! establishment phase or release phase !
! ! AD contains the code of the primitive !
! LLI_FMA7_RC7 ! Unallowed FDL primitive in the data transfer !
! ! phase, AD contains the code of the primitive !
! LLI_FMA7_RC8 ! unknown FDL primitive !
! LLI_FMA7_RC9 ! unknown LLI primitive !
! LLI_FMA7_RC10 ! Unallowed LLI primitive in the connection !
! ! establishment phase or release phase !
! ! AD contains the code of the primitive !
! LLI_FMA7_RC11 ! Unallowed LLI primitive in the data transfer !
! ! phase, AD contains the code of the primitive !
! LLI_FMA7_RC12 ! FDL_DATA_ACK.con (LS/LR/IV) !
! ! AD contains the L_status !
! LLI_FMA7_RC13 ! Error on transmission !
! ! FDL_CYC_DATA_REPLY.con (LS/LR/IV/OK/NO) !
! ! AD contains the L_status !
! LLI_FMA7_RC14 ! FDL_DATA_REPLY.con (LS/LR/IV) !
! ! AD contains the L_status !
! LLI_FMA7_RC15 ! FDL_DATA.con (LS/LR/DS/IV) !
! ! AD contains the L_status !
! LLI_FMA7_RC16 ! Error on receipt !
! ! FDL_CYC_DATA_REPLY.con (LS/LR/IV/OK/NO) !
! ! AD contains the L_status !
! LLI_FMA7_RC17 ! Error on transfer of the Poll List !
! ! FDL_CYC_DATA_REPLY.con (LS/LR/IV/NO) !
! ! AD contains the L_status !
! LLI_FMA7_RC18 ! Timer T1 expired (connection establishment) !
! LLI_FMA7_RC19 ! Timer T2 expired (connection release) !
! LLI_FMA7_RC20 ! Time out during Poll List activation/ !
! ! deactivation !
! LLI_FMA7_RC21 ! LLI service primitive could not be assigned !
! ! to the CRL !
! LLI_FMA7_RC22 ! Unallowed FMA1/2 primitive received !
! ! AD contains the code of the primitive !
! LLI_FMA7_RC23 ! Unallowed FDL primitive received at start-up !
! ! AD contains the code of the primitive !
! LLI_FMA7_RC24 ! Confirm / indication mode error !
+===============+===============================================+
Page 590
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
This page is intentionally left blank.