Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 761
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Flag New_Prm to False and the user data exchange mode to the DP-Slave will
be continued.
In case of a DDLM_Act_Param.ind the user has to clear or to set the Active-Flag
in accordance with the parameter Activate in the corresponding DP-Slave
parameter set. A new DP-Slave parameter set which contains the Active-Flag can
only be loaded with a cleared Active-Flag. For this it is necessary that the
User-Interface is in the operation mode Clear or Operate. In the operation mode
Stop DP-Slave parameter sets can be loaded regardless of the state of the
Active-Flag.
The data sets Prm_Data and Cfg_Data will be transferred directly from the DP-
Slave parameter set to the DP-Slave during parametrization and configuration.
The Add_Tab contains the relation between the in- and output data interface of
the User-Interface and the in- and output data regions of the DP-Slaves.
c) Diagnostic_Data:
In this area the diagnostic information of the DP-Slaves, the system diagnostic,
the Data_Transfer_List and the Master_Status will be stored by the User-
Interface.
d) Input, Output Data:
In this area the input data of the DP-Slaves and the output data of the user
will be stored. The length of this area is manufacturer specific. The
arrangement of the in- and output data depends on how the user designs his DP-
system. This arrangement is given in the Add_Tab region of the DP-Slave
parameter set.
10.1.2 Service Interface
The shaping as a service interface gives the user the possibility to call
acyclic functions asynchronously to the cyclic operation of the User-Interface.
They are subdivided in local and remote functions. The local functions are
handled by the Scheduler or the Service-Handler. The remote functions are
handled by the Scheduler. The User-Interface provides no additional error
handling for these functions. At this interface the service calls shall be
called sequentially. A parallel handling is only allowed in the case that a
Mark.req was passed to the interface and a Global_Control.req is made.
Page 762
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
10.1.2.1 Set Operation Mode
By means of this function the user can set the operation mode (USIF_State) of
the User-Interface. The user can read the given operation mode of the User-
Interface with the function DDLM_Get_Master_Diag. With the function
DDLM_Download the operation mode can also be changed by the DP-Master (class 2).
Table 36. Set_Mode (local)
+------------------------------+-----+-----+
! Parameter Name !.req !.con !
! ! ! !
+------------------------------+-----+-----+
! USIF_State ! M ! !
! ! ! !
! Status ! ! M !
+------------------------------+-----+-----+
USIF_State:
The User-Interface provides four operation modes for the user:
- Offline:
Communication to all DP participants (DP-Master and DP-Slave) is
stopped. Local FDL control will be taken out of the token ring. The
User-Interface waits for a signal to start.
- Stop:
The bus parameter set is loaded in the FDL. The FDL control is active.
The responder functions for communication with the DP-Master (class 2)
are processed. DP-Slaves are not polled.
- Clear:
In this operation mode the DP-Master (class 1) tries to parameterize,
check configuration and performs user data exchange with its
associated DP-Slaves. The inputs of the DP-Slaves are read and passed
to the user at the in- and output data interface. The outputs from the
User will be ignored; data equal to zero will be transferred to the
DP-Slaves.
- Operate:
The DP-Master (class 1) is in the user data exchange mode with the
dedicated DP-Slaves. The inputs from the DP-Slaves are transferred to
the user and the outputs from the user are passed to the DP-Slaves. If
the User-Interface leaves the operation mode Operate, the outputs of
all DP-Slaves will be cleared by means of the function Global_Control
(Control_Command = Clear_Data, Group_Select = 0).
Status:
The parameter Status indicates success or failure of the function.
Possible values: OK,NO,IV
Page 763
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
10.1.2.2 Message upon Change of Operation Mode
With this function the User-Interface indicates the change of its operation
mode. This indication will not occur if the user has initiated the change of the
operation mode through the function Set_Mode. If the Error_Action_Flag is set
the User-Interface remains in the operation mode Operate as long as the user
data exchange to the activated DP-Slaves takes place successfully. The User-
Interface changes the operation mode to the state Offline if a serious error
happens at the local interface. This will occur independent of the
Error_Action_Flag.
Table 37. Mode_Changed (local)
+------------------------------+-----+
! Parameter Name !.ind !
! ! !
+------------------------------+-----+
! USIF_State ! M !
+------------------------------+-----+
USIF_State:
See function Set_Mode in section "Set Operation Mode".
10.1.2.3 Load Bus Parameter Set
With this function the user can load a new bus parameter set. The User-Interface
transfers the new loaded bus parameter set in the current one and passes the
changed FDL operational parameters to FDL control. In the operation mode Clear
and Operate of the User-Interface it is not allowed to load a bus parameter set
with changed FDL parameters Baud_rate or FDL_Add.
Table 38. Load_Bus_Par (local)
+------------------------------+-----+-----+
! Parameter Name !.req !.con !
! ! ! !
+------------------------------+-----+-----+
! Bus_Para ! M ! !
! ! ! !
! Status ! ! M !
+------------------------------+-----+-----+
Bus_Para:
This parameter contains the bus parameter set which shall be loaded. The
structure is similar to the current bus parameter set (see section "Coding of
the Bus Parameter Set").
Status:
The parameter Status indicates success or failure of the function.
Possible values: OK,NO,IV
Page 764
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
10.1.2.4 Synchronize Data Transfer
By means of this function the user can operate synchronously with the User-
Interface. After the user has passed this function to the User-Interface, the
user will receive an acknowledgement from the User-Interface after all activated
DP-Salves where polled at least once.
Table 39. Mark (local)
+------------------------------+-----+-----+
! Parameter Name !.req !.con !
! ! ! !
+------------------------------+-----+-----+
! Status ! ! M !
! Dia ! ! C !
+------------------------------+-----+-----+
Dia:
This parameter indicates that at least one activated DP-Slaves was not in the
user data exchange mode.
Possible Values: True, False
Status:
The parameter Status indicates success or failure of the function. The value NO
will be signalled if the User-Interface is in the operation mode Offline or
Stop, or a Mark.req is still active.
Possible Values: OK,NO
10.1.2.5 Control Commands to DP-Slave
This function makes it possible to send the control commands Sync and Freeze to
one (single) or several (multicast) DP-Slaves. This can be necessary to
synchronize DP-Slaves.
Table 40. Global_Control (remote)
+------------------------------+-----+-----+
! Parameter Name !.req !.con !
! ! ! !
+------------------------------+-----+-----+
! Rem_Add ! M ! M !
! Control_Command ! M ! !
! Group_Select ! M ! !
! ! ! !
! Status ! ! M !
+------------------------------+-----+-----+
Rem_Add:
The parameter Rem_Add (Remote_Address) fixes the FDL address of the remote
participant.
Range: 0 to 126,127 (global address)
Page 765
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Control_Command:
This parameter specifies the command or the commands which has to be performed.
The DP-Master (class 1) sets the flag Clear_Data according to his operation
mode.
Possible commands:
Sync
Unsync
Freeze
Unfreeze
Group_Select:
This parameter determines which group or groups has to be addressed. The command
becomes effective when the logical AND between the Group_Ident (will be sent at
parametrization) and the Group_Select has a result not equal to zero. All DP-
Slaves will be addressed if the parameter Group_Select has the value zero.
Status:
The parameter Status indicates only whether the request telegram could be sent
or not. The case NO indicates that the Control_Command is not allowed.
Possible values: OK,DS,NO
10.1.2.6 Read Statistic Counters
This function makes it possible to read the statistic counters.
Table 41. Read_Value (local)
+------------------------------+------+------+
! Parameter Name ! .req ! .con !
+------------------------------+------+------+
! Variable ! M ! !
! ! ! !
! Status ! ! M !
! Value ! ! C !
+------------------------------+------+------+
Variable:
The parameter Variable selects the FDL Variable whose current value has to be
read.
Value:
This parameter contains the read value of the FDL parameter.
Status:
The parameter Status indicates success or failure of the function.
Possible values: OK,NO,IV
Page 766
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
10.1.2.7 Clear Statistic Counter
With this function the statistic counters can be cleared.
Table 42. Delete_SC (local)
+------------------------------+------+------+
! Parameter Name ! .req ! .con !
+------------------------------+------+------+
! Address ! M ! !
! ! ! !
! Status ! ! M !
+------------------------------+------+------+
Address:
This parameter specifies the FDL address of the statistic counters that have to
be cleared.
Allowed values:
0 to 126: FDL address
All: All statistic counters
Status:
The parameter Status indicates success or failure of the function.
Possible values: OK,NO,IV
10.1.3 Server Behaviour at DP-Master (Class 1)
At the DP-Master (class 1) the functions for the master-master communication
have to be passed by the user to the data and/or service interface of the User-
Interface.
a) DDLM_Get_Master_Diag: data interface: Diagnostic_Data
Identifier (0 to 125): Diag_Data from the corresponding
DP-Slave (read)
Identifier (126): System_Diagnostic (read)
Identifier (127): Master_Status (read)
Identifier (128): Data_Transfer_List (read)
b) DDLM_Start_Seq: no mapping onto the User-Interface
c) DDLM_End_Seq: no mapping onto the User-Interface
Page 767
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
d) DDLM_Upload: data, service interface
Area_Code (0 to 125): DP-Slave parameter set (read)
(data interface: master parameter set)
Area_Code (127): bus parameter set (read)
(data interface: master parameter set)
Area_Code (129): Statistic counter (read)
(Service: Read_Value)
Area_Code (255): no mapping onto the User-Interface
e) DDLM_Download: data, service interface
Area_Code (0 to 125): DP-Slave parameter set (write)
(data interface: master parameter set)
Area_Code (127): bus parameter set in the temporary memory of
the user (write)
(no mapping onto the User-Interface)
Area_Code (129): Statistic counter (delete)
(Service: Delete_SC)
Area_Code (255): no mapping onto the User-Interface
f) DDLM_Act_Para_Brct: service interface
Area_Code (127): bus parameter set (load and activate)
(Service: Load_Bus_Par)
g) DDLM_Act_Param: data, service interface
Area_Code (0 to 125): DP-Slave parameter set (de-, activate)
(data interface: master parameter set)
Area_Code (127): bus parameter set (load and activate)
(Service: Load_Bus_Par)
Area_Code (128): Operation mode (set)
(Service: Set_Mode)
10.2 DP-Master (class 2)
At the DP-Master (class 2) the User-Interface is not existent. The user of the
DP-Master (class 2) mapps his functions directly onto the DDLM-Interface.
10.3 DP-Slave
At the DP-Slave the interface between User and User-Interface is created as a
data interface. This interface is described in section "Communication Model of
the DP-Slave".
Page 768
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
11 Coding
11.1 Coding Rules for Additional Information
11.1.1 General
In the case of Master-Master communication the coding information of the
different functions is transferred in the layer 2 Data_Unit. The coding
instructions for this additional information are optimized for short messages,
taking into account the special fieldbus sector requirements and security of the
transferred data.
For communication with DP-Slaves additional information is not used. The
distinction of the functions will be made, without exception, by means of
different Service Access Points.
11.1.2 Coding Rules
The structure and the use of the additional information depends on the used DP-
Master function. In this case the additional information will be part of the
Data_Unit.
The structure of a Data_Unit is given through the insertion of additional
information or through the kind of function itself.
Structure of a Data_Unit (L_sdu) with additional information:
+-----------------------+--------------------------+
!additional information ! user data !
+-----------------------+--------------------------+
The additional information contains no information about the length, but is
given through the used function. The sequence of the parameters in the Data_Unit
depends on the sequence of the parameters in the function call. After the
additional information follows the user data depending on the used function.
Structure of a Data_Unit (L_sdu) without additional information:
+--------------------------------------------------+
! user data !
+--------------------------------------------------+
The maximum length of the Data_Unit is 246 octets according to the Data Link
Layer Service Protocol Specifications. If additional information has to be
transferred, the possible length of the user data is reduced.
Page 769
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
11.1.3 Structure of Additional Information
The first octet of the additional information is the Function_Num.
The Function_Num has the following format:
MSB LSB
+--+--+--+--+--+--+--+--+
Bit No !7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
! ! ! ! ! ! ! ! Meaning:
! ! ! ! ! ! ! !
! ! ! +--+--+--+--+---- function code/
! ! ! error code
! ! !
! ! +------------------- fixed to 0 (PROFIBUS-DP-PDU)
! !
! +---------------------- fixed to 1 (PROFIBUS-DP-PDU)
!
!
+----------------- request/response or error frame
0 request/response (okay)
1 response error frame
Function_Num will be transferred in the request and response frame. If the
function is correctly processed, bit 7 of Function_Num in the response frame is
set to zero. In case of an error an error frame will be transferred. In this
frame Function_Num contains an error code with bit 7 set to one.
In the following there is a list of the parameter Function_Num for the
particular DP-Master functions.
function code (Bit 0 to 4 of Function_Num):
0 reserved
1 Get_Master_Diag
2 Start_Seq
3 Download
4 Upload
5 End_Seq
6 Act_Para_Brct
7 Act_Param
8 to 31 to be defined
Page 770
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
error code:
0 reserved
1 FE
2 NE
3 AD
4 EA Meaning of the error codes
5 LE see table 7.
6 RE
7 IP
8 SC
9 SE
10 NE
11 DI
12 to 31 to be defined
These error codes will be directly transferred by means of a response error
frame. All other error codes are implicitly part of the FC of the response frame
or are generated from the local FDL.
The transferred error codes in the response error frame will be delivered from
the DDLM in the parameter Status to the User-Interface.
Table 43. Coding of the PDU (without address extension)
+--------------------+--------------------------------------------+
! Function ! Parameter !
+--------------------+--------------------------------------------+
!Get_Master_Diag.req ! Function_Num,Identifier, !
!Get_Master_Diag.res ! Function_Num,Identifier,Diagnosic_Data !
+--------------------+--------------------------------------------+
! Start_Seq.req ! Function_Num,Area_Code,Timeout !
! Start_Seq.res ! Function_Num,Area_Code,Timeout, !
! ! Max_Len_Data_Unit !
+--------------------+--------------------------------------------+
! Download.req ! Function_Num,Area_Code,Add_Offset, Data !
! Download.res ! Function_Num,Area_Code,Add_Offset !
+--------------------+--------------------------------------------+
! Upload.req ! Function_Num,Area_Code,Add_Offset, Data_Len!
! Upload.res ! Function_Num,Area_Code,Add_Offset, Data !
+--------------------+--------------------------------------------+
! End_Seq.req ! Function_Num !
! End_Seq.res ! Function_Num !
+--------------------+--------------------------------------------+
! Act_Para_Brct.req ! Function_Num,Area_Code !
! ! !
+--------------------+--------------------------------------------+
! Act_Param.req ! Function_Num,Area_Code,Activate !
! Act_Param.res ! Function_Num,Area_Code,Activate !
+--------------------+--------------------------------------------+
Example:
The coding of the PDU of the function DDLM_Download will clarify the coding.
Download(Area_Code 1, Add_Offset 3800 hex, Data (220 Octets))
Download.req PDU:
43H, 01H, 38H, 00H, Octet1, Octet2, .. Octet220