Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 71
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
SAP Deactivate FMA1/2 (optional)
The FMA1/2 user employs this service to cause the FMA1/2 to deactivate a Local
LSAP. The management returns a confirmation thereof.
4.2.2 Overview of Interactions
The services mentioned in subclause 4.2.1 are described by the following
primitives (FMA1/2_...):
Service Primitive Possible for the
following stations
Reset FMA1/2 FMA1/2_RESET.request Master and Slave
FMA1/2_RESET.confirm - " -
Set Value FMA1/2 FMA1/2_SET_VALUE.request Master and Slave
FMA1/2_SET_VALUE.confirm - " -
Read Value FMA1/2 FMA1/2_READ_VALUE.request Master and Slave
FMA1/2_READ_VALUE.confirm - " -
Service Primitive Possible for the
following stations
Event FMA1/2 FMA1/2_EVENT.indication Master and Slave
Ident FMA1/2 FMA1/2_IDENT.request Local : Master and Slave
Remote: Master
FMA1/2_IDENT.confirm Local : Master and Slave
Remote: Master
LSAP Status FMA1/2_LSAP_STATUS.request Local : Master and Slave
FMA1/2 Remote: Master
FMA1/2_LSAP_STATUS.confirm Local : Master and Slave
Remote: Master
Live-List FMA1/2_LIVE_LIST.request Master
FMA1/2 FMA1/2_LIVE_LIST.confirm - " -
SAP Activate FMA1/2_SAP_ACTIVATE.request Master and Slave
FMA1/2 FMA1/2_SAP_ACTIVATE.confirm - " -
RSAP Activate FMA1/2_RSAP_ACTIVATE.request Master and Slave
FMA1/2 FMA1/2_RSAP_ACTIVATE.confirm - " -
SAP Deactivate FMA1/2_SAP_DEACTIVATE.request Master and Slave
FMA1/2 FMA1/2_SAP_DEACTIVATE.confirm - " -
Temporal Relationships of Service Primitives:
Master/Slave Master/Slave
Station 1 Station n
User ! FMA1/2 ! !
! ! !
FMA1/2_XXXXX.req ! ! !
---------------->!-- ! !
! ) ! !
FMA1/2_XXXXX.con ! ) ! !
<----------------!<- ! !
! ! !
Figure 7. Reset, Set Value, Read Value, Ident(Local), LSAP Status(Local),
(R)SAP Activate, SAP Deactivate FMA1/2 Service
Page 72
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
Master/Slave Master/Slave
Station 1 Station n
User ! FMA1/2 ! !
! ! !
! ! !
FMA1/2_Event.ind ! ! !
<----------------!-- ! !
! ! !
Figure 8. Event FMA1/2 Service
Master Master/Slave
Station 1 Station n
User ! FMA1/2 ! !
! ! !
FMA1/2_XXXXX.req ! ! !
---------------->!- _ ! !
! - _ ! !
! !- _ !
! ! - _ !
! ! _ -!
! ! _ - !
! _ !- !
FMA1/2_XXXXX.con ! _ - ! !
<----------------!- ! !
! ! !
Figure 9. Ident(Remote), LSAP Status(Remote), Live List FMA1/2 Service
4.2.3 Detailed Specification of Services and Interactions
4.2.3.1 Reset FMA1/2
The service "Reset FMA1/2" is mandatory.
The FMA1/2 user passes a FMA1/2_RESET.request primitive to the FMA1/2 causing it
to reset Layers 1 and 2. As a result the FMA1/2 passes a FDL_RESET.request
primitive to Layer 2 (FDL) and a PHY_RESET.request primitive to Layer 1 (PHY)
(see subclauses 5.2.3.1 and 5.3.3.1). After the confirmations of FDL and PHY by
means of the respective confirmation primitives FMA1/2 resets itself and passes
a FMA1/2_RESET.confirm primitive to the user.
Parameter of the primitives
FMA1/2_RESET.request
(MSAP_0)
- The parameter MSAP_0 (Management Service Access Point_0) specifies the serv-
ice access point of the Local FMA1/2 User. This MSAP is activated and config-
ured depending on the implementation.
FMA1/2_RESET.confirm
(MSAP_0, M_status)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive.
Page 73
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
- The parameter M_status contains a confirmation about the execution of the
service. The following values are specified:
Table 12. Reset, Values of M_status
+----+--------------------------------------------+-----------+
!Code! Meaning ! temporary/!
! ! ! permanent !
+----+--------------------------------------------+-----------+
! OK ! The Reset function was carried out ! - !
! ! successfully. ! - !
! NO ! The Reset function was not carried out ! !
! ! successfully. ! t/p !
! IV ! Invalid parameters in request. ! - !
+----+--------------------------------------------+-----------+
4.2.3.2 Set Value FMA1/2, Read Value FMA1/2
Set Value FMA1/2
The service "Set Value FMA1/2" is optional.
The FMA1/2 user passes a FMA1/2_SET_ VALUE. request primitive to the FMA1/2 to
assign a desired value to one or more specified variables of Layers 1 and/or 2.
The management passes the corresponding FDL_SET_VALUE.request and/or PHY_SET_
VALUE.request primitives to the respective Layers and passes a FMA1/2_SET_VALUE.
confirm primitive to the user after receiving all the corresponding confirmation
primitives.
Parameters of the primitives
FMA1/2_SET_VALUE.request
(MSAP_0, Variable_name 1 to z, Desired_value 1 to z)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive.
- The parameter Variable_name contains a list of one or more variables of the
FDL and/or PHY. The selectable variables are specified in subclauses 5.2.3.2
and 5.3.3.2.
- The parameter Desired_value contains a list of one or more values for the
specified variables. The permissible values or ranges of values are specified
in subclauses 5.2.3.2 and 5.3.3.2.
FMA1/2_SET_VALUE.confirm
(MSAP_0, M_status 1 to z)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive.
- The parameter M_status contains a confirmation about the execution of the
service. The following values are specified:
Page 74
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
Table 13. Set Value, Values of M_status
+----+--------------------------------------------+-----------+
!Code! Meaning ! temporary/!
! ! ! permanent !
+----+--------------------------------------------+-----------+
! OK ! The Variable has the new value. ! - !
! NO ! The Variable does not exist or could not ! !
! ! be set to the new value. ! t/p !
! IV ! Invalid parameters in request. ! - !
+----+--------------------------------------------+-----------+
Read Value FMA1/2
The service "Read Value FMA1/2" is optional.
The FMA1/2 user passes a FMA1/2_READ_ VALUE.request primitive to the FMA1/2 to
read the current value of one or more variables of the FDL or PHY, respectively.
After receipt of this primitive the FMA1/2 creates the corresponding FDL_READ_
VALUE.request and/or PHY_READ_VALUE.request primitives and passes a FMA1/2_READ_
VALUE.confirm primitive to the FMA1/2 user after receipt of all corresponding
confirmation primitives. This primitive contains as a parameter one or more of
the requested variable values.
Parameters of the primitives
FMA1/2_READ_VALUE.request
(MSAP_0, Variable_name 1 to z)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive.
- The parameter Variable_name specifies one or more variables whose values
shall be read. The variables that may be chosen are specified in subclauses
5.2.3.2 and 5.3.3.2.
FMA1/2_READ_VALUE.confirm
(MSAP_0, Current_value 1 to z, M_status 1 to z)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive.
- The parameter Current_value contains the actual value of the variables that
were specified in the preceding FMA1/2_READ_VALUE.request. The permissible
values or ranges of values are specified in subclauses 5.2.3.2 and 5.3.3.2.
- The parameter M_status contains a confirmation about the execution of the
service. The following values are specified:
Table 14. Read Value, Values of M_status
+----+--------------------------------------------+-----------+
!Code! Meaning ! temporary/!
! ! ! permanent !
+----+--------------------------------------------+-----------+
! OK ! The Variable could be read. ! - !
! NO ! The Variable does not exist or could not ! !
! ! be read. The corresponding value of ! !
! ! Current_value is not defined. ! t/p !
! IV ! Invalid parameters in request. ! - !
+----+--------------------------------------------+-----------+
Page 75
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
4.2.3.3 Event FMA1/2
The service "Event FMA1/2" is mandatory.
After receipt of a PHY_EVENT.indication or FDL_Fault.indication primitive the
FMA1/2 passes a FMA1/2_EVENT.indication primitive to the FMA1/2 user to inform
it about important events or error conditions in the respective Layers.
Parameters of the primitives
FMA1/2_EVENT.indication
(MSAP_1, Event/Fault, Add_info)
- The parameter MSAP_1 specifies the service access point of the local FMA1/2
user. This MSAP is activated and configured depending on the implementation.
- The parameter Event/Fault specifies the event that took place or the reason
for the error and may take the values of the parameter "Variable_name" (see
subclause 5.3.3.3) or "Fault_type" (see subclause 5.2.3.3), respectively.
- The parameter Add_info contains additional information concerning the respec-
tive event and may take the values of the parameter New_value of the PHY_
EVENT.indication primitive (see subclause 5.3.3.3).
4.2.3.4 Ident FMA1/2
The service "Ident FMA1/2" is optional.
By means of a FMA1/2_IDENT.request primitive the FMA1/2 user requests the FMA1/2
to carry out a station identification. The FMA1/2 then passes a FDL_IDENT.
request primitive to the FDL. If the user requests the identification of a
remote station, the FDL Layer shall send a corresponding request to this station
by means of a Request Ident with Reply (see Part 4, Table 3a, b7=1, Code No 14)
and return the result to the FMA1/2 by means of a FDL_IDENT.confirm primitive
(see Part 4, Table 3a, b7=0, Code No 1/8/9). If the identification refers to the
local FDL Layer, the FDL shall immediately reply with a FDL_ IDENT.confirm
primitive. After receipt of a FDL_IDENT.confirm primitive the FMA1/2 returns the
requested data to the user with a FMA1/2_IDENT.confirm primitive.
Parameters of the primitives
FMA1/2_IDENT.request
(MSAP_0, Rem/Loc_add)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive. In the case of remote requests the value of the parameters
is not transferred in the frame.
- The parameter Rem/Loc_add contains in the case of a remote request the FDL
address of the remote station. The global address is not permissible. In the
case of local requests the parameter contains the own FDL address (TS).
FMA1/2_IDENT.confirm
(MSAP_0, Rem/Loc_add, Ident_list, M_status)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive.
Page 76
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
- The parameter Rem/Loc_add has the same meaning as described for the FMA1/2_
IDENT.request primitive.
- The parameter Ident_list specifies a list of values for the identification of
a station:
Vendor_name : Name of the vendor
Controller_type : Type of the PROFIBUS interface
HW/SW_release : Version number of the hardware and software
- The parameter M_status contains a confirmation concerning the execution of
the service. The following values are specified:
Table 15. Ident, Values of M_status
+----+--------------------------------------------+-----------+
!Code! Meaning ! temporary/!
! ! ! permanent !
+----+--------------------------------------------+-----------+
! OK ! The Identification could be carried out. ! - !
! LR ! Resources of the local FDL controller not ! !
! ! available or not sufficient. ! t !
! NA ! No or no plausible reaction (Ack./Res.) ! !
! ! from remote station. ! t !
! DS ! Local FDL/PHY controller not in logical ! !
! ! token ring or disconnected from line. ! p !
! NR ! Negative acknowledgement for Ident data, as! !
! ! not available to the remote FDL controller.! p !
! IV ! Invalid parameters in request. ! - !
+----+--------------------------------------------+-----------+
4.2.3.5 LSAP Status FMA1/2
The service "LSAP Status FMA1/2" is optional.
The FMA1/2 user passes a FMA1/2_LSAP_STATUS. request primitive to the FMA1/2 to
request the configuration of a LSAP with respect to the FDL services. The FMA1/2
then generates a corresponding FDL_LSAP_ STATUS.request primitive for the FDL.
If the user requests the LSAP status of a remote station, the FDL Layer issues a
corresponding request by means of a Request LSAP Status with Reply (see Part 4,
Table 3a, b7=1, Code No 15) to this station and passes the response (see Table
3a, b7=0, Code No 1/3/8/9) by means of a FDL_LSAP_STATUS.confirm primitive to
the FMA1/2. If the LSAP status refers to the local FDL Layer, the FDL
immediately responds by means of a FDL_LSAP_STATUS.confirm primitive. After
receipt of a FDL_LSAP_STATUS.confirm primitive, the FMA1/2 passes the parameter
values to the FMA1/2 user by means of a FMA1/2_LSAP_STATUS.confirm primitive.
Parameters of the primitives
FMA1/2_LSAP_STATUS.request
(MSAP_0, LSAP, Rem/Loc_add)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive. In the case of remote requests the value of the parameter
is not transferred in the frame.
- The parameter LSAP specifies the remote/local LSAP whose configuration is
requested. The LSAP values 0 to 63 and NIL are permitted. If the configura-
tion of the default LSAP is to be determined, the parameter LSAP shall have
Page 77
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
the value NIL. In this case no DAE with b7=0 exists in the request frame for
a remote request.
- The parameter Rem/Loc_add contains the FDL address of the remote station in
the case of a remote request. The global address is not permissible. In the
case of a local request the parameter contains the own FDL address (TS).
FMA1/2_LSAP_STATUS.confirm
(MSAP_0, LSAP, Rem/Loc_add, Access, Service_type 1 to z, Role_in_service 1 to z,
M_status)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive.
- The parameters LSAP and Rem/Loc_add have the same meaning as described for
the FMA1/2_LSAP_STATUS.request primitive.
- The parameter Access with the values All/0 to 126 [EXT] specifies the access
protection. "All" means that all remote stations have access to this LSAP.
Apart from that only the specified remote station (address 0 to 126 and if
applicable region/segment address [EXT]) has access.
- The parameter Service_type contains the FDL services that are activated at
the remote/local LSAP. The following values are specified:
SDA, SDN, SRD and CSRD
- The parameter Role_in_service specifies the configuration for the activated
service. The following values are specified:
Initiator: The station initiates the respective service exclusively.
Responder: The station responds to the service exclusively.
Both: The station initiates and responds to the service.
- The parameter M_status contains a confirmation about the execution of the
service. The following values are specified:
Table 16. LSAP Status, Values of M_status
+----+--------------------------------------------+-----------+
!Code! Meaning ! temporary/!
! ! ! permanent !
+----+--------------------------------------------+-----------+
! OK ! The LSAP Status could be read. ! - !
! LR ! Resources of the local FDL controller not ! !
! ! available or not sufficient. ! t !
! LS ! The local LSAP is not activated. ! d !
! RS ! The LSAP is not activated in the remote ! !
! ! FDL controller. ! p !
! NA ! No or no plausible reaction (Ack./Res.) ! !
! ! from remote station. ! t !
! DS ! Local FDL/PHY controller not in logical ! !
! ! token ring or disconnected from line. ! p !
! NR ! Negative acknowledgement for LSAP data, as ! !
! ! not available in the remote FDL controller.! p !
! IV ! Invalid parameters in request. ! - !
+----+--------------------------------------------+-----------+
Page 78
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
4.2.3.6 Live List FMA1/2
The service "Live List FMA1/2" is optional.
The FMA1/2 user requests by means of a FMA1/2_ LIVE_LIST.request primitive an
up-to-date list of all stations that may be currently reached on the bus. The
FMA1/2 passes this request to the FDL with a FDL_LIVE_LIST.request primitive.
After this request the FDL Layer performs a Request FDL Status with Reply for
every possible station address (see Part 4, subclause 4.1.4, Table 3a, b7=1,
Code No 9) and passes the result of this survey (see Part 4, Table 3a, b7=0,
Code No 0) to the FMA1/2 with a FDL_LIVE_LIST.confirm primitive. The FMA1/2
passes this list to the user with a FMA1/2_LIVE_LIST.confirm primitive.
Parameters of the primitives
FMA1/2_LIVE_LIST.request
(MSAP_0)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive. The value of the parameter is not transferred in the
request frames.
FMA1/2_LIVE_LIST.confirm
(MSAP_0, Live_list, M_status)
- The parameter MSAP_0 has the same meaning as described for the FMA1/2_RESET.
request primitive.
- The parameter Live_list corresponds to the Live List described in Part 4,
subclause 4.1.4.
- The parameter M_status contains a confirmation about the execution of the
service. The following values are specified:
Table 17. Live List, Values of M_status
+----+--------------------------------------------+-----------+
!Code! Meaning ! temporary/!
! ! ! permanent !
+----+--------------------------------------------+-----------+
! OK ! The live list is complete. ! - !
! LR ! Resources of the local FDL controller not ! !
! ! available or not sufficient. ! t !
! DS ! Local FDL/PHY controller not in logical ! !
! ! token ring or disconnected from line. ! p !
! IV ! Invalid parameters in request. ! - !
+----+--------------------------------------------+-----------+
4.2.3.7 (R)SAP Activate FMA1/2, SAP Deactivate FMA1/2
SAP Activate FMA1/2
The service "SAP Activate FMA1/2" is optional.
This service provides the FMA1/2 user with the possibility to activate and to
configure a local LSAP for the individual FDL services. An exception to this is
the responder function for the Reply services (SRD, CSRD) that are activated by
means of the RSAP Activate service.
After receipt of the FMA1/2_SAP_ACTIVATE.request primitive from the user the
FMA1/2 passes a FDL_SAP_ACTIVATE.request primitive to the FDL. After receipt of
Page 79
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
the corresponding Confirmation primitive the FMA1/2 passes a FMA1/2_SAP_ACTI-
VATE.confirm primitive to the user.
Parameters of the primitives
FMA1/2_SAP_ACTIVATE.request
(MSAP_2, SSAP, Access, Service_list)
- The parameter MSAP_2 specifies the service access point of the local FMA1/2
User. This MSAP is activated and configured depending on the implementation.
- The parameter SSAP specifies the local LSAP that is to be activated and con-
figured. The SSAP values 0 to 63 and NIL are permissible.
- The parameter Access with the values All/0 to 126 [EXT] is used for access
protection and specifies whether all remote stations (All) or only an indi-
vidual remote station (0 to 126 and if applicable Region/Segment address
[EXT]) may have access to the LSAP (Send/Request Data). The parameter is only
valid for the responder function(s), i. e. Role_in_service = Responder/Both.
- The parameter Service_list is a list containing further parameters:
Table 18. SAP Activate Service_list
+-------+------------------------------------+
! Entry ! Name !
+-------+------------------------------------+
! 1 ! Service_list_length (1 + 3
.
z) !
! 2 ! Service_activate 1 !
! 3 ! Role_in_service 1 !
! 4 ! L_sdu_length_list 1 !
! 5 ! Service_activate 2 !
! 6 ! Role_in_service 2 !
! 7 ! L_sdu_length_list 2 !
! . ! . . . !
! . ! . . . !
! . ! . . . !
! k ! Service_activate z !
! k+1 ! Role_in_service z !
! k+2 ! L_sdu_length_list z !
+-------+------------------------------------+
! z = maximum 4 !
+--------------------------------------------+
- The parameter Service_activate contains the FDL service that shall be acti-
vated for this Access Point (SDA, SDN, SRD or CSRD).
- The parameter Role_in_service specifies the configuration for the service to
be activated. The following values are specified:
Initiator: The station initiates the respective service exclusively.
Responder: The station responds to the service exclusively. Not permissi-
ble for SRD and CSRD.
Both: The station initiates and responds to the service. Not permis-
sible for SRD and CSRD.
- The parameter L_sdu_length_list is a list of Max_L_sdu lengths. For the
services SDA, SDN and SRD the list has the following fixed structure:
Page 80
PROFIBUS-Specification-Normative-Parts-3:1997
Copyright by PNO 1997 - all rights reserved
Table 19. SAP 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/con_low !
! 4 ! Max_L_sdu_length_ind/con_high !
+-------+------------------------------------+
- The parameter Max_L_sdu_length_req_low or _high specifies the maximum length
of the low or high priority L_sdu to be sent that is passed to the initiator
by means of the Request primitive for the services SDA, SDN, and SRD. For the
Indication of the services SDA and SDN at the Responder and for the Confirma-
tion of the service SRD at the Initiator, the maximum length of the L_sdu to
be received is specified by the parameter Max_L_sdu_length_ind/con_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).
Depending on the service and Role_in_service the following lengths > 0 octets
("x": > 0; "-": = 0) are permissible:
Table 20. SAP Activate, L_sdu Lengths for SDA and SDN
+---------------------------------------------------------+
! Service: SDA and SDN !
+------+----------+-----------+---------------------------+
!Length! Initiator! Responder ! Both !
+------+----------+-----------+---------------------------+
! 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 x - x !
! 4 ! - - - ! - x x ! - x x - x x - x x !
+------+----------+-----------+---------------------------+
! 1 to 4 denote the lengths as in Table 19 !
+---------------------------------------------------------+
Table 21. SAP Activate L_sdu Lengths of SRD
+-------------------------------------------+
! Service: SRD !
+------+------------------------------------+
!Length! Initiator
*)
!
+------+------------------------------------+
! 1 ! - - - x - - x x x x - x !
! 2 ! - - - - x x - x x - x x !
! 3 ! x - x x - x - x - x x x !
! 4 ! - x x - x - x - x x x x !
+------+------------------------------------+
! 1 to 4 denote the lengths as in Table 19.!
! *) Responder only with RSAP Activate, !
! Both not allowed !
+-------------------------------------------+