Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 861
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
RUN INI11 RUN
FMA1/2_SAP_ACTIVATE.con(OK)
=> ignore
RUN INI12 RUN
FMA1/2_SAP_DEACTIVATE.con(OK)
=> ignore
RUN INI13 RUN
FMA1/2_RSAP_ACTIVATE.con(IV/NO)
=> DDLM_Fault.ind
RUN INI14 RUN
FMA1/2_SAP_ACTIVATE.con(IV/NO)
=> DDLM_Fault.ind
RUN INI15 RUN
FMA1/2_SAP_DEACTIVATE.con(IV/NO)
=> DDLM_Fault.ind
RUN DIAG1 RUN
DDLM_Slave_Diag_Upd.req(Diag_Data)
=> FDL_REPLY_UPDATE.req(SSAP=60, L_sdu=Diag_Data,
Serv_Class=Low, Transmit=Multiple)
RUN DIAG2 RUN
FDL_DATA_REPLY.ind(DSAP=60)
=> DDLM_Slave_Diag.ind(Req_Add=Loc_add)
RUN DATA1 RUN
DDLM_Data_Exchange_Upd.req(Diag_Flag, Inp_Data)
\Diag_Flag = False AND Prev_Diag_Flag = False
AND Inp_Data.len > 0
=> FDL_REPLY_UPDATE.req(SSAP=NIL, L_sdu=Inp_Data,
Serv_Class=Low, Transmit=Multiple)
RUN DATA2 RUN
DDLM_Data_Exchange_Upd.req(Diag_Flag, Inp_Data)
\Diag_Flag = False AND Prev_Diag_Flag = False
AND Inp_Data.len = 0
=> ignore
RUN DATA3 RUN
DDLM_Data_Exchange_Upd.req(Diag_Flag, Inp_Data)
\Diag_Flag = False AND Prev_Diag_Flag = True
AND Inp_Data.len > 0
=> Prev_Diag_Flag = False
FDL_REPLY_UPDATE.req(SSAP=NIL, L_sdu=Inp_Data,
Serv_Class=Low, Transmit=Multiple)
FDL_REPLY_UPDATE.req(SSAP=NIL, L_sdu.len=0,
Serv_Class=High, Transmit=Single)
RUN DATA4 RUN
DDLM_Data_Exchange_Upd.req(Diag_Flag, Inp_Data)
\Diag_Flag = False AND Prev_Diag_Flag = True
AND Inp_Data.len = 0
=> FDL_REPLY_UPDATE.req(SSAP=NIL, L_sdu.len=0,
Serv_Class=High, Transmit=Single)
Prev_Diag_Flag = False
Page 862
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
RUN DATA5 RUN
DDLM_Data_Exchange_Upd.req(Diag_Flag, Inp_Data)
\Diag_Flag = True AND Inp_Data.len > 0
=> FDL_REPLY_UPDATE.req(SSAP=NIL, L_sdu=Inp_Data,
Serv_Class=High, Transmit=Multiple)
Prev_Diag_Flag = True
RUN DATA6 RUN
DDLM_Data_Exchange_Upd.req(Diag_Flag, Inp_Data)
\Diag_Flag = True AND Inp_Data.len = 0
=> FDL_REPLY_UPDATE.req(SSAP=NIL, L_sdu.len=1, L_sdu[1] = 0,
Serv_Class=High, Transmit=Multiple)
Prev_Diag_Flag = True
RUN DATA7 RUN
FDL_DATA_REPLY.ind(DSAP=NIL)
=> DDLM_Data_Exchange.ind(Outp_Data=L_sdu)
RUN INP1 RUN
DDLM_RD_Inp_Upd.req(Inp_Data)
\Inp_Data.len > 0
=> FDL_REPLY_UPDATE.req(SSAP=56, L_sdu=Inp_Data,
Serv_Class=Low, Transmit=Multiple)
RUN INP2 RUN
DDLM_RD_Inp_Upd.req(Inp_Data)
\Inp_Data.len = 0
=> ignore
RUN INP3 RUN
FDL_DATA_REPLY.ind(DSAP=56)
=> ignore
RUN OUTP1 RUN
DDLM_RD_Outp_Upd.req(Outp_Data)
\Outp_Data.len > 0
=> FDL_REPLY_UPDATE.req(SSAP=57, L_sdu=Outp_Data,
Serv_Class=Low, Transmit=Multiple)
RUN OUTP2 RUN
DDLM_RD_Outp_Upd.req(Outp_Data)
\Outp_Data.len = 0
=> ignore
RUN OUTP3 RUN
FDL_DATA_REPLY.ind(DSAP=57)
=> ignore
RUN SPRM1 RUN
FDL_DATA_REPLY.ind(DSAP=61)
=> DDLM_Set_Prm.ind(Req_Add=Loc_add, Prm_Data=L_sdu)
RUN SCFG1 RUN
FDL_DATA_REPLY.ind(DSAP=62)
=> DDLM_Chk_Cfg.ind(Req_Add=Loc_add, Cfg_Data=L_sdu)
Page 863
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
RUN GCFG1 RUN
DDLM_Get_Cfg_Upd.req(Real_Cfg_Data)
=> FDL_REPLY_UPDATE.req(SSAP=59, L_sdu=Real_Cfg_Data,
Serv_class=Low, Transmit=Multiple)
RUN GCFG2 RUN
FDL_DATA_REPLY.ind(DSAP=59)
=> ignore
RUN GCTR1 RUN
FDL_DATA.ind(DSAP=58)
\L_sdu.len = 2
=> DDLM_Global_Control.ind(Req_Add=Loc_add,
Control_Command=L_sdu[1], Group_Select=L_sdu[2])
RUN GCTR2 RUN
FDL_DATA.ind(DSAP=58)
\L_sdu.len # 2
=> ignore
RUN SADR1 RUN
FDL_DATA_REPLY.ind(DSAP=55)
\L_sdu.len = 4
=> DDLM_Set_Slave_Add.ind(New_Slave_Add=L_sdu[1],
Ident_Number=L_sdu[2-3], No_Add_Chg=L_sdu[4])
RUN SADR2 RUN
FDL_DATA_REPLY.ind(DSAP=55)
\L_sdu.len > 4
=> DDLM_Set_Slave_Add.ind(New_Slave_Add=L_sdu[1],
Ident_Number=L_sdu[2-3], No_Add_Chg=L_sdu[4],
Rem_Slave_Data=L_sdu[5-L_sdu.len])
RUN SADR3 RUN
FDL_DATA_REPLY.ind(DSAP=55)
\L_sdu.len < 4
=> ignore
RUN RUN1 RUN
FDL_REPLY_UPDATE.con(OK)
=> ignore
RUN RUN2 RUN
FMA1/2_EVENT.ind
=> ignore
RUN ERR1 RUN
FDL_REPLY_UPDATE.con(LS/LR/IV)
=> DDLM_Fault.ind
RUN ERR2 RUN
FDL_DATA_REPLY.ind
\0 <= DSAP <= 54
=> DDLM_Fault.ind
Page 864
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
RUN ERR3 RUN
FDL_DATA.ind
\DSAP # 58
=> DDLM_Fault.ind
RUN ERR4 RUN
inadmissible FDL-primitive
=> DDLM_Fault.ind
RUN ERR5 RUN
unknown FDL-primitive
=> DDLM_Fault.ind
Page 865
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
14 Characteristic Features of a Device
14.1 General
The features described in the following section define the characteristic
features and the performance of a PROFIBUS-DP device.
A vendor of DP-Slaves and DP-Masters (class 1) shall offer the Device data base
(DDB) as a device data sheet and a device data file to the user. Using the
Device data base enables checks of device data in the configuration phase of a
PROFIBUS-DP system. This way, errors can be avoided during the configuration.
Because of the defined file format of the Device data base, it is possible to
realize vendor independent configuration tools for PROFIBUS-DP systems. The
configuration tool uses the DDB for testing the data that were entered regarding
the observance of limits and validity related to the performance of the
individual device.
The distinction of the DDB data sets is achieved by the vendor- and device-
identifiers.
In the case of composite-devices, PROFIBUS-FMS specific Device data base
information is inserted directly at the beginning of the Device data base file.
The section "Format of the Device Data Base File" fixes the format of the
description of the device data for a PROFIBUS-DP device.
14.2 Format of the Device Data Base File
The Device data base file is an ASCII-file. It may be created with every
applicable ASCII text editor. The DP-specific part begins always with the
identifier "#Profibus_DP". The device data base will be specified respectively
as parameter of a key word. At the evaluation of the key words the kind of
letters, capital or small, will be don't care. The sequence of the parameters
may be in any order. The data medium which the vendor of the DP-device uses for
the delivery of the Device data base is not defined in this specification.
The file format is line oriented. Each line contains statements for exactly one
parameter. If a semicolon is detected during the interpretation of the line, it
is assumed that the rest of the line is a comment. The maximum number of
characters per line is fixed to 80. If it not possible to describe the
information in one line then it is allowed to use continuation lines. A "\" at
the end of a line indicates that the following line is a continuation line. It
is distinguished between number-parameters and text-parameters. No special end-
identifier is defined. But it is to be ensured that the file ends after a
complete line. Parameters which are not used for a DP-Master or a DP-Slave shall
be omitted.
Page 866
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
14.3 Meaning and Coding of the Key Words
14.3.1 General
The type-identifier which is specified with the key words refers to the
parameter with the same name. The parameters are distinguished between:
- Mandatory (M)
- Optional (O)
- Optional, with default=0 if the parameter is not present (D)
- at least one out of the group (G) suitable for the
corresponding baud rate
14.3.2 General DP-Key words
Vendor_Name: (M)
Name of the vendor of the DP-device.
Type: Visible String (32)
Model_Name: (M)
Controller-Type of the DP-device.
Type: Visible String (32)
Revision: (M)
Revision of the DP-device.
Type: Visible String (32)
Ident_Number: (M)
Type number of the DP-device (see section "Manufacturer Identifier").
Type: Unsigned16
Protocol_Ident: (M)
Protocol-identifier of the DP-device.
Type: Unsigned8
0: PROFIBUS-DP,
16 to 255: Vendor specific
Station_Type: (M)
Type of the DP-device.
Type: Unsigned8
0: DP-Slave,
1: DP-Master (class 1)
FMS_supp: (D)
This device is a FMS/DP-composite device.
Type: Boolean (1: True)
Hardware_Release: (M)
Hardware release of the DP-device.
Type: Visible String (32)
Software_Release (M)
Software release of the DP-device.
Type: Visible String (32)
9.6_supp: (G)
The DP-device supports the baud rate 9.6 kBaud.
Type: Boolean (1: True)
Page 867
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
19.2_supp: (G)
The DP-device supports the baud rate 19.2 kBaud.
Type: Boolean (1: True)
93.75_supp: (G)
The DP-device supports the baud rate 93.75 kBaud.
Type: Boolean (1: True)
187.5_supp: (G)
The DP-device supports the baud rate 187.5 kBaud.
Type: Boolean (1: True)
500_supp: (G)
The DP-device supports the baud rate 500 kBaud.
Type: Boolean (1: True)
1.5M_supp: (G)
The DP-device supports the baud rate 1.5 MBaud.
Type: Boolean (1: True)
MaxTsdr_9.6: (G)
This is the time that a responder at the baud rate 9.6 kBaud requires at maximum
to answer after a request has been received (see Part 4).
Type: Unsigned16
Time base: bit time
MaxTsdr_19.2: (G)
This is the time that a responder at the baud rate 19.2 kBaud requires at
maximum to answer after a request has been received (see Part 4).
Type: Unsigned16
Time base: bit time
MaxTsdr_93.75: (G)
This is the time that a responder at the baud rate 93.75 kBaud requires at
maximum to answer after a request has been received (see Part 4).
Type: Unsigned16
Time base: bit time
MaxTsdr_187.5: (G)
This is the time that a responder at the baud rate 187.5 kBaud requires at
maximum to answer after a request has been received (see Part 4).
Type: Unsigned16
Time base: bit time
MaxTsdr_500: (G)
This is the time that a responder at the baud rate 500 kBaud requires at maximum
to answer after a request has been received (see Part 4).
Type: Unsigned16
Time base: bit time
MaxTsdr_1.5M: (G)
This is the time that a responder at the baud rate 1.5 MBaud requires at maximum
to answer after a request has been received (see Part 4).
Type: Unsigned16
Time base: bit time
Page 868
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Redundancy: (D)
This parameter specifies if the device supports redundant transmission
technology.
Type: Boolean
0: not supported, 1: redundancy supported
Repeater_Ctrl_Sig: (D)
This parameter specifies the signal-type of the CNTR-P signal at the connector.
Type: Unsigned8
0: Not connected, 1: RS485, 2:TTL
24V_Pins: (D)
This parameter specifies the function of the signals M24V and P24V at the
connector.
Type: Unsigned8
0: Not connected, 1:Input, 2:Output
14.3.3 DP-Master (Class 1) related Key words
Download_supp: (D)
The DP-device supports the functions Download, Start_seq and End_seq.
Type: Boolean (1: True)
Upload_supp: (D)
The DP-device supports the functions Upload, Start_seq and End_seq.
Type: Boolean (1: True)
Act_Para_Brct_supp: (D)
The DP-device supports the function Act_Para_Brct.
Type: Boolean (1: True)
Act_Param_supp: (D)
The DP-device supports the function Act_Param.
Type: Boolean (1: True)
Max_MPS_Length: (M)
Maximal size of memory (in Byte) that a DP-device provides for the storage of
the master parameter set.
Type: Unsigned32
Max_Lsdu_MS: (M)
This parameter specifies the maximal L_sdu length for all master-slave
communication relationships.
Type: Unsigned8
Max_Lsdu_MM: (M)
This parameter specifies the maximal L_sdu length for all master-master
communication relationships.
Type: Unsigned8
Min_Poll_Timeout: (M)
This parameter specifies the maximal time interval that a DP-Master (class 1)
needs for the execution of a master-master function.
Type: Unsigned16
Time base: 10 ms
Page 869
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Trdy_9.6: (G)
This parameter specifies the time interval at the baud rate 9.6 kBaud that a DP-
Master (class 1) needs to be prepared to receive a reply frame after sending a
request PDU (see Part 4).
Type: Unsigned8
Time base: bit time
Trdy_19.2: (G)
This parameter specifies the time interval at the baud rate 19.2 kBaud that a
DP-Master (class 1) needs to be prepared to receive a reply frame after sending
a request PDU (see Part 4).
Type: Unsigned8
Time base: bit time
Trdy_93.75: (G)
This parameter specifies the time interval at the baud rate 93.75 kBaud that a
DP-Master (class 1) needs to be prepared to receive a reply frame after sending
a request PDU (see Part 4).
Type: Unsigned8
Time base: bit time
Trdy_187.5: (G)
This parameter specifies the time interval at the baud rate 187.5 kBaud that a
DP-Master (class 1) needs to be prepared to receive a reply frame after sending
a request PDU (see Part 4).
Type: Unsigned8
Time base: bit time
Trdy_500: (G)
This parameter specifies the time interval at the baud rate 500 kBaud that a DP-
Master (class 1) needs to be prepared to receive a reply frame after sending a
request PDU (see Part 4).
Type: Unsigned8
Time base: bit time
Trdy_1.5M (G)
This parameter specifies the time interval at the baud rate 1.5 MBaud that a DP-
Master (class 1) needs to be prepared to receive a reply frame after sending a
request PDU (see Part 4).
Type: Unsigned8
Time base: bit time
Tqui_9.6: (G)
This parameter specifies the transmitter fall time (T
QUI
) (see Part 4) at the
baud rate 9.6 kBaud.
Type: Unsigned8
Time base: bit time
Tqui_19.2: (G)
This parameter specifies the transmitter fall time (T
QUI
) (see Part 4) at the
baud rate 19.2 kBaud.
Type: Unsigned8
Time base: bit time
Tqui_93.75: (G)
This parameter specifies the transmitter fall time (T
QUI
) (see Part 4) at the
baud rate 93.75 kBaud.
Type: Unsigned8
Time base: bit time
Page 870
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Tqui_187.5: (G)
This parameter specifies the transmitter fall time (T
QUI
) (see Part 4) at the
baud rate 187.5 kBaud.
Type: Unsigned8
Time base: bit time
Tqui_500: (G)
This parameter specifies the transmitter fall time (T
QUI
) (see Part 4) at the
baud rate 500 kBaud.
Type: Unsigned8
Time base: bit time
Tqui_1.5M: (G)
This parameter specifies the transmitter fall time (T
QUI
) (see Part 4) at the
baud rate 1.5 MBaud.
Type: Unsigned8
Time base: bit time
Tset_9.6: (G)
This parameter specifies the setup time relating to layer 2. This time specifies
the interval between the arrival of an event and the corresponding reaction (see
Part 4) at the baud rate 9.6 kBaud.
Type: Unsigned8
Time base: bit time
Tset_19.2: (G)
This parameter specifies the setup time relating to layer 2. This time specifies
the interval between the arrival of an event and the corresponding reaction (see
Part 4) at the baud rate 19.2 kBaud.
Type: Unsigned8
Time base: bit time
Tset_93.75: (G)
This parameter specifies the setup time relating to layer 2. This time specifies
the interval between the arrival of an event and the corresponding reaction (see
Part 4) at the baud rate 93.75 kBaud.
Type: Unsigned8
Time base: bit time
Tset_187.5: (G)
This parameter specifies the setup time relating to layer 2. This time specifies
the interval between the arrival of an event and the corresponding reaction (see
Part 4) at the baud rate 187.5 kBaud.
Type: Unsigned8
Time base: bit time
Tset_500: (G)
This parameter specifies the setup time relating to layer 2. This time specifies
the interval between the arrival of an event and the corresponding reaction (see
Part 4) at the baud rate 500 kBaud.
Type: Unsigned8
Time base: bit time