Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 81
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
For the cyclic service CSRD the L_sdu_length_list has the following structure:
Table 22. SAP Activate L_sdu_length_list
+-------+--------------------------------------------+
! Entry ! Name !
+-------+--------------------------------------------+
! 1 ! List_length (4 to i) !
! 2 ! Confirm_mode !
! 3 ! Poll_list_length (see subclause 4.1.3.4) !
! 4 ! Rem_add (0 to 126 [EXT])/DSAP (0 to 62): !
! ! a) Max_L_sdu_length_con_low !
! ! b) Max_L_sdu_length_con_high !
! ! c) Max_L_sdu_length_req_low !
! 5 ! Rem_add (0 to 126 [EXT])/DSAP (0 to 62): !
! ! a) Max_L_sdu_length_con_low !
! ! b) Max_L_sdu_length_con_high !
! ! c) Max_L_sdu_length_req_low !
! . ! ... !
! . ! ... !
! . ! ... !
! ! !
! i ! Rem_add (0 to 126 [EXT])/DSAP (0 to 62): !
! ! a) Max_L_sdu_length_con_low !
! ! b) Max_L_sdu_length_con_high !
! ! c) Max_L_sdu_length_req_low !
+-------+--------------------------------------------+
- The parameter Confirm_mode with the values All/Data specifies whether for the
CSRD service the FDL_CYC_DATA_REPLY.confirm primitive is generated after
every cyclic SRD (All) or whether it is omitted (Data) only if both in the
received frame (confirmation) and in the corresponding Send Update (data to
be sent) L_sdu = Null and no errors occurred (see subclause 4.1.3.4, FDL_CYC_
DATA_REPLY.confirmation).
- For each individual Poll List entry (specified by Rem_add/DSAP) up to three
L_sdu lengths are permissible. For the confirmation of the CSRD service at
the initiator, the maximum length of the L_sdu to be received is specified by
the parameter Max_L_sdu_length_con_low or _high.
The parameter Max_L_sdu_length_req_low specifies the maximum length of the
low priority L_sdu to be sent, which is passed to the initiator by means of
the Send Update Request primitive of the CSRD service. The length of the
L_sdu may be 0 to 246 octets. When using SSAP, DSAP and Region/Segment
addresses a maximum of 242 octets is permitted (see Part 4, subclause 4.7.5).
FMA1/2_SAP_ACTIVATE.confirm
(MSAP_2, SSAP, M_status)
- The parameter MSAP_2 has the same meaning as described for the FMA1/2_SAP_
ACTIVATE.request primitive.
- The parameter SSAP has the same meaning as described for the FMA1/2_SAP_
ACTIVATE.request primitive.
- The parameter M_status contains a confirmation about the execution of the
service. The following values are specified:
Page 82
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
Table 23. SAP Activate, Values of M_status
+----+--------------------------------------------+-----------+
!Code! Meaning ! temporary/!
! ! ! permanent !
+----+--------------------------------------------+-----------+
! OK ! The SSAP is activated as requested. ! - !
! NO ! The SSAP is not activated ! !
! ! (already activated or resources not avail- ! !
! ! able or not sufficient). ! t/p !
! IV ! Invalid parameters in request. ! - !
+----+--------------------------------------------+-----------+
RSAP Activate FMA1/2
The service "RSAP Activate FMA1/2" is optional.
The FMA1/2 user passes a FMA1/2_RSAP_ACTIVATE. request primitive to the FMA1/2
to activate and to configure a local LSAP for the responder function of the
Reply services (SRD and CSRD). The FMA1/2 passes a corresponding FDL_RSAP_
ACTIVATE.request primitive to the FDL and passes a FMA1/2_RSAP_ACTIVATE.confirm
primitive to the user after receipt of the corresponding Confirmation primitive.
Parameters of the primitives
FMA1/2_RSAP_ACTIVATE.request
(MSAP_2, SSAP, Access, L_sdu_length_list, Indication_mode)
- The parameter MSAP_2 has the same meaning as described for the FMA1/2_SAP_
ACTIVATE.request primitive.
- The parameter SSAP specifies the local LSAP for the data area (shared_data_
area) and the user that receives the Indication primitive if a SRD is
received on this "DSAP". The SSAP values 0 to 62 and NIL are permitted.
- The parameter Access has the same meaning as described for the FMA1/2_SAP_
ACTIVATE.request primitive.
- The parameter L_sdu_length_list is a list of Max_L_sdu length. The list has
the following structure:
Table 24. RSAP Activate, L_sdu_length_list
+-------+-------------------------------+
! Entry ! Name !
+-------+-------------------------------+
! 1 ! Max_L_sdu_length_req_low !
! 2 ! Max_L_sdu_length_req_high !
! 3 ! Max_L_sdu_length_ind_low !
! 4 ! Max_L_sdu_length_ind_high !
+-------+-------------------------------+
- The parameter Max_L_sdu_length_req_low or _high specifies the maximum length
of the low or high priority L_sdu that is to be sent in the SRD response
frame, which is passed with the Reply Update Request primitive at the
responder. For the indication at the responder the maximum length of the
L_sdu to be received is specified by the parameter Max_L_sdu_length_ind_low
or _high. The length of the L_sdu may be 0 to 246 octets. When using SSAP,
DSAP, and Region/Segment addresses a maximum of 242 octets is permissible
(see Part 4, subclause 4.7.5).
Page 83
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
The following lengths > 0 octets ("x": > 0; "-": = 0) are permissible at the
responder:
Table 25. RSAP Activate, L_sdu Length of SRD and CSRD
+-------------------------------------------+
! Service: SRD or CSRD !
+------+------------------------------------+
!Length! Responder !
+------+------------------------------------+
! 1 ! x - x x - - x x x x - x !
! 2 ! - x x - x x - x x - x x !
! 3 ! - - - x - x - x - x x x !
! 4 ! - - - - x - x - x x x x !
+------+------------------------------------+
! 1 to 4 denote the lengths as in Table 24.!
+-------------------------------------------+
- The parameter Indication_mode with the values All/Data/Unchanged specifies
whether in the case of the SRD/CSRD service the FDL_DATA_REPLY. indication
primitive shall be generated (All) or whether it shall be omitted (Data) only
if both in the received frame (request) and in the corresponding Reply Update
(response data) L_sdu = Null.
The overwriting of a local RSAP (changing of the parameter Access) is
informed by the FDL by the parameter Indication_mode contains the value
"Unchanged". In this case only the parameter "Access" is overwritten and all
other parameters are unchanged.
FMA1/2_RSAP_ACTIVATE.confirm
(MSAP_2, SSAP, M_status)
- The parameter MSAP_2 has the same meaning as described for the FMA1/2_SAP_
ACTIVATE.request primitive.
- The parameter SSAP has the same meaning as described for the FMA1/2_RSAP_
ACTIVATE.request primitive.
- The parameter M_status contains a confirmation about the execution of the
service. The following values are specified:
Table 26. RSAP Activate, Values of M_status
+----+--------------------------------------------+-----------+
!Code! Meaning ! temporary/!
! ! ! permanent !
+----+--------------------------------------------+-----------+
! OK ! The SSAP is activated resp. overwritten as ! !
! ! requested. ! - !
! NO ! Indication_mode All/Data: ! t/p !
! ! The SSAP is not activated (already acti- ! !
! ! vated or resources not available or not ! !
! ! sufficient). ! !
! ! Indication_mode Unchanged: ! t/p !
! ! The SSAP is not overwritten, as it was not ! !
! ! activated. ! !
! IV ! Invalid parameters in request. ! - !
+----+--------------------------------------------+-----------+
Page 84
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
SAP Deactivate FMA1/2
The service "SAP Deactivate FMA1/2" is optional.
The FMA1/2 user employs this service to deactivate all FDL services for a local
LSAP. After receipt of a FMA1/2_SAP_DEACTIVATE.request primitive from the user,
the FMA1/2 passes a corresponding FDL_SAP_DEACTIVATE.request primitive to the
FDL controller. The FDL shall test whether a response is still pending and shall
deactivate all services for the specified LSAP either directly (if no response
is pending) or after receipt of the response. Immediately after this the FDL
passes a FDL_SAP_DEACTIVATE.confirm primitive to the FMA1/2. After receipt of
the Confirmation primitive the FMA1/2 passes a FMA1/2_SAP_DEACTIVATE.confirm
primitive to the user.
Parameters of the primitives
FMA1/2_SAP_DEACTIVATE.request
(MSAP_2, SSAP)
- The parameter MSAP_2 has the same meaning as described for the FMA1/2_SAP_
ACTIVATE.request primitive.
- The parameter SSAP contains the Local LSAP that is to be deactivated for all
FDL services.
FMA1/2_SAP_DEACTIVATE.confirm
(MSAP_2, SSAP, M_status)
- The parameter MSAP_2 has the same meaning as described for the FMA1/2_SAP_
ACTIVATE.request primitive.
- The parameter SSAP has the same meaning as described for the FMA1/2_SAP_
DEACTIVATE.request primitive.
- The parameter M_status contains a confirmation about the execution of the
service. The following values are specified:
Table 27. SAP Deactivate, Values of M_status
+----+--------------------------------------------+-----------+
!Code! Meaning ! temporary/!
! ! ! permanent !
+----+--------------------------------------------+-----------+
! OK ! The SSAP is deactivated. ! - !
! NO ! The SSAP has not been activated. ! p !
! IV ! Invalid parameters in request. ! - !
+----+--------------------------------------------+-----------+
Page 85
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
5 Management (FMA1/2)
The management for the Layers 1 and 2 (FMA1/2) organizes the initialization, the
supervision and the error handling between the FMA1/2 User and the logical func-
tions in PHY and FDL.
The PHY/FDL services are either mandatory or optional.
The relations between FMA1/2 and the Layer 7 (APP and FMA7 respectively) are
described in Part 2 of the specification.
5.1 General Description of FMA1/2 Functions
Local FMA1/2 Functions for the Layers 1 and 2:
- reset of the Layers 1 and 2
- reading and setting of parameters
- activation, configuration and deactivation of LSAPs
- event and error messages
- version identification
- determination of LSAP configuration
Remote FMA1/2 Functions for the Layers 1 and 2:
- version identification
- request of LSAP configuration
- determination of the Live List
The FMA1/2 acts as a mediator between the local FMA1/2 user and the Layers 1
and 2. Requests from the FMA1/2 user, modified as required, are transferred to
the FDL and PHY control respectively by the FMA1/2, and acknowledged with a con-
firmation to the local FMA1/2 User. Moreover the FMA1/2 immediately receives
indications from the layers if status changes have occurred within the layers.
Such messages lead to a FMA1/2 user indication.
5.2 FDL - FMA1/2 Interface
User
----------- +---------------------+---------+
!
I
!
Layer 2 !
FDL I
!
!
I
!
----------- +---------------------+
FMA1/2
!
! ! !
Layer 1 ! PHY ! !
! ! !
----------- +--------+---+--------+---------+
---------+ +-------------------
"Layer 0" Physical Media
---------------------------------
Figure 10. Interface between FDL and FMA1/2 in Relation to Layer Model
Page 86
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
5.2.1 Overview of Services
The FDL provides the following services to FMA1/2:
- Reset FDL
- Set Value FDL
- Read Value FDL
- Fault FDL
- Ident FDL
- LSAP Status FDL
- Live List FDL
- SAP Activate FDL
- RSAP Activate FDL
- SAP Deactivate FDL
)
)
)
)
>
)
)
)
)
identical to the homonymous service without suffix
"FDL" in subclause 4.2.1 with the exception, that
the parameters MSAP_0 to _2 and M_status "IV" are
absent.
Reset FDL (mandatory)
The FMA1/2 uses this service to reset the FDL. After the execution the FMA1/2
receives a confirmation.
Set Value FDL (mandatory)
The Set Value FDL service allows the FMA1/2 to set certain parameters of the FDL
to desired values. A confirmation informs the FMA1/2 whether the given parameter
could be set to the value or not.
Read Value FDL (optional)
With this service the FMA1/2 is able to read certain FDL parameters. The current
value of the given parameter is transferred to the FMA1/2 in the response of the
FDL.
Fault FDL (mandatory)
The FDL uses this service to inform the FMA1/2 of faulty conditions and events.
Page 87
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
5.2.2 Overview of Interactions
The services mentioned in subclause 4.2.1 are described by the following primi-
tives (FDL_...):
Service Primitive permissible for
following users
Reset FDL FDL_RESET.request Master and Slave
FDL_RESET.confirm - " -
Set Value FDL FDL_SET_VALUE.request Master and Slave
FDL_SET_VALUE.confirm - " -
Read Value FDL FDL_READ_VALUE.request Master and Slave
FDL_READ_VALUE.confirm - " -
Fault FDL FDL_FAULT.indication Master and Slave
Temporal Relationships of Service Primitives:
Master/Slave Master/Slave
Station 1 Station n
FMA1/2
!
FDL
! !
! ! !
FDL_XXXXX.req ! ! !
-------------->!-- ! !
! ) ! !
FDL_XXXXX.con ! ) ! !
<--------------!<- ! !
! ! !
Figure 11. Reset FDL, Set Value FDL, Read Value FDL Service
Master/Slave Master/Slave
Station 1 Station n
FMA1/2
!
FDL
! !
! ! !
! ! !
FDL_FAULT.ind ! ! !
<--------------!-- ! !
! ! !
Figure 12. Fault FDL Service
Page 88
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
5.2.3 Detailed Specification of Services and Interactions
5.2.3.1 Reset FDL
The service "Reset FDL" is mandatory.
With a FDL_RESET.request primitive the FMA1/2 causes a reset of the FDL Layer.
This is carried out in the same manner as at a Power On ("Offline"-status; FDL
variables [operational parameters/counters] are cleared). Immediately afterwards
a FDL_RESET. confirm primitive is transferred to the FMA1/2 .
Parameters of the Primitives
FDL_RESET.request
FDL_RESET.confirm
- Both primitives have no parameters
5.2.3.2 Set Value FDL, Read Value FDL
Set Value FDL
The service "Set Value FDL" is mandatory.
The FMA1/2 gives a FDL_SET_VALUE.request primitive to the FDL to set a specified
FDL variable to a desired value. After receiving this primitive the FDL tries to
select this variable and to deliver the new value. Subsequently the FMA1/2
receives a FDL_SET_ VALUE.confirm primitive.
Parameters of the Primitives
FDL_SET_VALUE.request
(Variable_name, Desired_value)
- The parameter Variable_name specifies the FDL variable to which a new value
is to be assigned. The variables shown in Table 28 may be selected.
- The parameter Desired_value specifies the new value for the FDL variable. The
selected variable may take the values shown in Table 29.
FDL_SET_VALUE.confirm
- This primitive has no parameters.
Page 89
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
Table 28. FDL Variables
+---------------------------------------------------------------+
! Operating Parameters (mandatory) !
+---------------------+-----------------------------------------+
! Name ! Meaning !
+---------------------+-----------------------------------------+
! TS ! FDL Address of this station !
! Baud_rate ! Data Signalling Rate of this PROFIBUS !
! ! System !
! Medium_red ! Availability of Redundant Media !
! HW-Release ! Hardware Release Number !
! SW-Release ! Software Release Number !
! T
SL
! Slot Time !
! min T
SDR
! smallest Station Delay Time !
! max T
SDR
*) ! largest Station Delay Time !
! T
QUI
*) ! Transmitter fall Time (Line State !
! ! Uncertain Time)/Repeater switch Time !
! T
SET
*) ! Setup Time !
! T
TR
*) ! Target Rotation Time !
! G *) ! GAP Update Factor !
! in_ring_ *) ! Request entry into or exit out of !
! desired ! the logical Token Ring !
! HSA *) ! Highest Station Address on this !
! ! PROFIBUS System !
! max_retry *) ! Maximum Number of Retries !
! limit ! !
+=====================+=========================================+
! Counters (optional) !
+---------------------+-----------------------------------------+
! Name ! Meaning !
+---------------------+-----------------------------------------+
! Frame_sent_count *) ! Number of frames sent !
! Retry_count *) ! Number of frame repeats !
! ! !
! SD_count ! Number of correct Start Delimiters !
! SD_error_count ! Number of defective Start Delimiters !
+---------------------+-----------------------------------------+
! If a counter reaches its maximum value, then both this coun- !
! ter and its comparison counter are stopped. If a counter is !
! reset to zero the related coparative counter is also reset to !
! zero, then this counters are free to count again. !
+---------------------------------------------------------------+
! *) only possible in Master Stations !
+---------------------------------------------------------------+
Page 90
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
Table 29. Values of FDL Variables
+---------------------------------------------------------------+
! Operating Parameters (mandatory) !
+------------------+--------------------------------------------+
! Variable ! Range of Values !
+------------------+--------------------------------------------+
! TS ! 1 Octet Address field, Station Address !
! ! value 0 to 126 and optional Address !
! ! Extension (see Part 4, subclause 4.7.2) !
! Baud_rate ! 9,6; 19,2; 93,75; 187,5; 500; 1500 kbit/s !
! Medium_red ! single; redundant !
! HW-Release !LE_HR; HW_release (see Part 4, Data Field) !
! SW-Release !LE_SR; SW_release (see Part 4, Data Field) !
! ! !
! T
SL
! 52 to 2
16
-1 (Bit Times) !
! min T
SDR
! 2
0
to 2
16
-1 (Bit Times) !
! max T
SDR
! 2
0
to 2
16
-1 (Bit Times) !
! T
QUI
! 0 to 2
8
-1 (Bit Times) !
! T
SET
! 2
0
to 2
8
-1 (Bit Times) !
! T
TR
! 2
0
to 2
24
-1 (Bit Times) !
! ! !
! G ! 1 to 100 !
! in_ring_ ! true; false !
! desired ! !
! HSA ! 2 to 126 !
! max_retry_ ! 1 to 8 (preferably 1) !
! limit ! !
+==================+============================================+
! Counters (optional) !
+------------------+--------------------------------------------+
! Variable ! Value !
+------------------+--------------------------------------------+
! Frame_sent_count ! 0 !
! Retry_count ! 0 !
! ! !
! SD_count ! 0 !
! SD_error_count ! 0 !
+------------------+--------------------------------------------+
Read Value FDL
The service "Read Value FDL" is optional.
The FMA1/2 delivers a FDL_READ_VALUE.request primitive to the FDL to read the
current value of a FDL variable. After receiving this primitive the FDL tries to
select the specified variable and to deliver its current value to the FMA1/2
with a FDL_READ_VALUE.confirm primitive.
Parameters of the Primitives
FDL_READ_VALUE.request
(Variable_name)
- The parameter Variable_name specifies the FDL variable whose current value
shall be read. In addition to the variables described for the FDL_SET_
VALUE.request primitive (see Table 28) the following may be selected: