Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 721
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
The parameter may be structured. The subparameters and their belonging to a
parameter is represented by indenting their names by 2 characters.
The information whether an optional parameter is used or which parameter of a
selection has to be selected in a specific case is not mentioned in these
tables.
However, the information shall be present at the DDLM/FDL- and DDLM/FMA1/2-
Interfaces.
Representation of functions and their parameters.
Table 6. Representation of the Parameters of Function Calls
+------------------------------+-----+-----+-----+-----+
! Parameter Name !.req !.ind !_Upd !.con !
! ! ! !.req ! !
! ! ! !
*
) ! !
+------------------------------+-----+-----+-----+-----+
! Requestparameter1 ! M ! ! M ! !
! Parameter_A ! S ! ! S ! !
! Parameter_B ! S ! ! S ! !
! Requestparameter2 ! U ! ! U ! !
! ! ! ! ! !
! Status ! ! ! ! M !
! Responseparameter1 ! ! M ! ! M !
! Responseparameter2 ! ! C ! ! C !
! ! ! ! ! !
+------------------------------+-----+-----+-----+-----+
! !
!
*
) In the place of the _Upd.req primitive !
! the .res primitive is possible. !
+------------------------------------------------------+
meaning:
.req Request function primitive
.ind Indication function primitive
_Upd.req Update Request function primitive
.con Confirmation function primitive
.res Response function primitive
M Parameter is mandatory
U Parameter is an user option;
can be used or omitted
S Parameter is selected, there are several alternatives
C the existence of the parameter depends of the value
of a second parameter
The function acknowledgements (.res and .con) contain a status parameter, the
possible values are defined below:
Page 722
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Table 7. Status Values of the Functions
+-----+--------------------------------------------+------------+
!Value!Meaning !Source !
+-----+--------------------------------------------+------------+
!OK !Acknowledgement positive ! !
!IV !Invalid parameters in request !Local !
!NO !Service in this state not possible !Local !
!DS !Local-FDL/PHY Entity is not in logical !Local FDL !
! !token-ring or disconnected from line ! !
!NA !Negative ack,no reaction from remote station!Local FDL !
!RS !Service or remote-address at remote-LSAP !Remote FDL !
! !or remote-LSAP not activated; ! !
! ! - remote-station is no DP-Station ! !
! ! - remote-station is not yet ready for ! !
! ! these functions ! !
! ! - remote-station is associated with an ! !
! ! other Requester ! !
! ! - optional service not available ! !
!RR !Resources of the remote-FDL Entity !Remote FDL !
! !not sufficient or not available ! !
!UE !Remote-DDLM/FDL interface error !Remote FDL !
!NR !No Response data !Remote FDL !
!TO !Function-Timeout expired !Local DDLM !
!FE !Format-Error in a Request-frame !Remote DDLM !
!RE !Format-Error in a Response-frame !Local DDLM !
!LE !Data-block-length too large(Up-/Download) !Remote User !
!NI !Function not implemented !Remote User !
!EA !Area too large (Up-/Download) !Remote User !
!AD !Access denied !Remote User !
!IP !Invalid Parameter !Remote User !
!SC !Sequence Conflict !Remote User !
!SE !Sequence Error !Remote DDLM !
!NE !Area non-existent !Remote User !
!DI !Data Incomplete !Remote User !
!NC !Master parameter set not compatible !Remote User !
! ! ! !
+-----+--------------------------------------------+------------+
Page 723
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
9.3 DP-Master - DP-Slave Functions
9.3.1 Read DP-Slave Diagnostic Information
The Data_Unit contains the diagnostic information. If a bit has been set this
means that the event which is linked with this bit has occurred. The diagnostic
information consists of a standard diagnostic information (octet 1 to octet 6)
and an extended diagnostic information (Ext_Diag_Data).
Table 8. DDLM_Slave_Diag
+------------------------------+-----+-----+-----+-----+
! Parameter Name !.req !.ind !_Upd !.con !
! ! ! !.req ! !
+------------------------------+-----+-----+-----+-----+
! Rem_Add ! M ! ! ! M !
! Req_Add ! ! M ! ! !
! ! ! ! ! !
! Status ! ! ! ! M !
! Diag_Data ! ! ! M ! C !
! ! ! ! ! !
+------------------------------+-----+-----+-----+-----+
Rem_Add:
The parameter Rem_Add (Remote_Address) specifies the FDL-Address of the DP-Slave
from which the diagnostic information are requested.
Type: Unsigned8
Range: 0 to 126
Req_Add:
This parameter contains the station address of the requester. With the help of
this address it is determined if the watchdog control shall be triggered.
Type: Unsigned8
Range: 0 to 125
Status:
The parameter Status indicates success or failure of this function.
Possible Values: OK,DS,NA,RS,UE,NR,RE
Diag_Data:
Type: Octet String
Length: 6 to 32 (extendible to 244, see section "Restrictions")
Page 724
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Octet 1: Station_status_1
MSB LSB
+--+--+--+--+--+--+--+--+
Bit-No !7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
The individual bits have the following meaning:
Bit 7: Diag.Master_Lock
The DP-Slave has been parameterized from another master. This bit is
set by the DP-Master (class 1), if the address in octet 4 is different
from 255 and different from the own address. The DP-Slave sets this
bit to zero.
Bit 6: Diag.Prm_Fault
This bit is set by the DP-Slave if the last parameter frame was
faulty, e. g. wrong length, wrong Ident_Number, invalid parameters.
Bit 5: Diag.Invalid_Slave_Response
This bit is set by the DP-Master as soon as receiving a not plausible
response from an addressed DP-Slave. The DP-Slave sets this bit to
zero.
Bit 4: Diag.Not_Supported
This bit is set by the DP-Slave as soon as a function was requested
which is not supported from this DP-Slave.
Bit 3: Diag.Ext_Diag
This bit is set by the DP-Slave. It indicates that a diagnostic entry
exists in the slave specific diagnostic area (Ext_Diag_Data) if the
bit is set to one. If the bit is set to zero a status message can
exist in the slave specific diagnostic area (Ext_Diag_Data). The
meaning of this status message depends on the application and will not
be fixed in this specification.
Bit 2: Diag.Cfg_Fault
This bit is set by the DP-Slave as soon as the last received
configuration data from the DP-master are different from these which
the DP-Slave has determined.
Bit 1: Diag.Station_Not_Ready
This bit is set by the DP-Slave if the DP-Slave is not yet ready for
data transfer.
Bit 0: Diag.Station_Non_Existent
This bit is set by the DP-Master if the respective DP-Slave can not be
reached over the line. If this bit is set the diagnostic bits contains
the state of the last diagnostic message or the initial value. The DP-
Slave sets this bit to zero.
Page 725
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Octet 2: Station_status_2
MSB LSB
+--+--+--+--+--+--+--+--+
Bit-No !7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
The individual bits have the following meaning:
Bit 7: Diag.Deactivated
This bit is set by the DP-Master as soon as the DP-Slave has been
marked inactive within the DP-Slave parameter set and has been removed
from cyclic processing. The DP-Slave sets this bit always to zero.
Bit 6: reserved
Bit 5: Diag.Sync_Mode
This bit is set by the DP-Slave as soon as the respective DP-Slave has
received the Sync control command.
Bit 4: Diag.Freeze_Mode
This bit is set by the DP-Slave as soon as the respective DP-Slave has
received the Freeze control command.
Bit 3: Diag.WD_On (Watchdog on)
This bit is set by the DP-Slave as soon as his watchdog control has
been activated.
Bit 2: This bit is set to 1 by the DP-Slave.
Bit 1: Diag.Stat_Diag (static diagnostics)
If the DP-Slave sets this bit the DP-Master shall fetch diagnostic
informations as long as this bit is reset again. For Example, the DP-
Slave sets this bit if it is not able to provide valid user data.
Bit 0: Diag.Prm_Req
If the DP-Slave sets this bit the respective DP-Slave shall be
reparameterized and reconfigured. The bit remains set until
parameterization is finished. This bit is set by the DP-Slave.
If bit 1 and bit 0 are set, bit 0 has the higher priority.
Octet 3: Station_status_3
MSB LSB
+--+--+--+--+--+--+--+--+
Bit-No !7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
The individual bits have the following meaning:
Page 726
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Bit 7: Diag.Ext_Diag_Overflow
If this bit is set there exists more diagnostic information than
specified in Ext_Diag_Data. For Example, the DP-Slave sets this bit if
there are more channel diagnostics than the DP-Slave can enter in its
send buffer; or the DP-Master sets this bit if the DP-Slave sends more
diagnostic information than the DP-Master can enter in its diagnostic
buffer.
Bit 0 to 6: reserved
Octet 4: Diag.Master_Add
In this octet the address of the DP-Master is entered which has
parameterized this DP-Slave. If none of the DP-Masters has
parameterized the DP-Slave then the DP-Slave inserts the address 255
in this octet.
Octet 5 to 6 (unsigned16): Ident_Number
The manufacturer identifier is given for a DP-Device. This identifier
can be used on the one hand for verification purpose and on the other
hand for exact identification.
Octet 7 to 32: Ext_Diag_Data (extendible to 244, see section "Restrictions")
In this area the DP-Slave can enter its specific diagnostic. It is
defined a block structure with one header byte each for the device
related diagnostic and the identifier related diagnostic:
Device related diagnostic:
Header byte:
MSB LSB
+--+--+--+--+--+--+--+--+
Bit-No !7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
! ! ! ! ! ! ! ! meaning:
! ! ! ! ! ! ! !
! ! +--+--+--+--+--+---- block length in bytes
! ! including header byte 2 to
! ! header byte 63
! !
+--+---------------------- Bit 7, Bit 6 fixed to 00
In this block general diagnostic information is entered as for Example
overtemperature, undervoltage or overvoltage. The coding is defined device
specific.
For further interpretation the Ident_Number shall be used.
Page 727
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Identifier related (module) diagnostic:
For each used identifier byte at the configuration one bit is reserved. It is
padded to byte limits. The bits which are not configured shall be set to zero. A
set bit means that in this I/O area diagnostic is pending.
Header byte:
MSB LSB
+--+--+--+--+--+--+--+--+
Bit-No !7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
! ! ! ! ! ! ! ! meaning:
! ! ! ! ! ! ! !
! ! +--+--+--+--+--+---- block length in bytes
! ! including header byte 2 to
! ! header byte 63
! !
+--+---------------------- Bit 7, Bit 6 fixed to 01
Bit structure for identifier related diagnostic:
MSB LSB
+--+--+--+--+--+--+--+--+
Bit-No !7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
! ! ! ! ! ! ! !
! ! ! ! ! ! ! +--- identifier byte 0 has diagnostic
! ! ! ! ! ! +------ identifier byte 1 has diagnostic
! etc.
+------------------------ identifier byte 7 has diagnostic
etc.
Channel related diagnostic:
In this block the diagnosed channels and the diagnostic reason are entered in
turn. The length per entry is 3 octets.
Octet 1: Identifier number
MSB LSB
+--+--+--+--+--+--+--+--+
Bit-No !7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
! ! ! ! ! ! ! ! meaning:
! ! ! ! ! ! ! !
! ! +--+--+--+--+--+---- identifier number 0 to 63
! !
! !
+--+---------------------- Bit 7, Bit 6 fixed to 10
Page 728
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Octet 2: Channel number
MSB LSB
+--+--+--+--+--+--+--+--+
Bit-No !7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
! ! ! ! ! ! ! ! meaning:
! ! ! ! ! ! ! !
! ! +--+--+--+--+--+---- channel number 0 to 63
! !
+--+---------------------- input/output
00 reserved
01 input
10 output
11 input/output
For identifier bytes which contain both input and output, the direction of the
diagnosed channel is indicated in bit 7 and bit 6 of the channel number.
Octet 3: Type of diagnostic
MSB LSB
+--+--+--+--+--+--+--+--+
Bit-No !7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
! ! ! ! ! ! ! ! meaning:
! ! ! ! ! ! ! !
! ! ! +--+--+--+--+---- error type
! ! !
+--+--+------------------- channel type
000 reserved
001 bit
010 2 bit
011 4 bit
100 byte
101 word
110 2 words
111 reserved
Error type:
0 reserved
1 short circuit
2 undervoltage
3 overvoltage
4 overload
5 overtemperature
6 line break
7 upper limit value exceeded
8 lower limit value exceeded
9 error
10 reserved
.
15 reserved
16 manufacturer specific
.
31 manufacturer specific
Page 729
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
Example: Structure of a diagnostic according to the pattern above
MSB LSB
+--+--+--+--+--+--+--+--+
!7 !6 !5 !4 !3 !2 !1 !0 !
+--+--+--+--+--+--+--+--+
+--+--+--+--+--+--+--+--+
!0 !0 !0 !0 !0 !1 !0 !0 ! device related diagnostic:
+--+--+--+--+--+--+--+--+
! device specific ! meaning of the bits is defined
+--+--+--+--+--+--+--+--+ manufacturer specific
! diagnostic field !
+--+--+--+--+--+--+--+--+
! of length 3 !
+--+--+--+--+--+--+--+--+
!0 !1 !0 !0 !0 !1 !0 !1 ! identifier related diagnostic:
+--+--+--+--+--+--+--+--+
! 1 ! identifier number 0 has diagnostic
+--+--+--+--+--+--+--+--+
! 1 ! identifier number 12 has diagnostic
+--+--+--+--+--+--+--+--+
! 1 ! identifier number 18 has diagnostic
+--+--+--+--+--+--+--+--+
! !
+--+--+--+--+--+--+--+--+ channel related diagnostic:
!1 !0 !0 !0 !0 !0 !0 !0 ! identifier number 0
+--+--+--+--+--+--+--+--+
!0 !0 !0 !0 !0 !0 !1 !0 ! channel 2
+--+--+--+--+--+--+--+--+
!0 !0 !1 !0 !0 !1 !0 !0 ! overload, channel bit organized
+--+--+--+--+--+--+--+--+
!1 !0 !0 !0 !1 !1 !0 !0 ! identifier number 12
+--+--+--+--+--+--+--+--+
!0 !0 !0 !0 !0 !1 !1 !0 ! channel 6
+--+--+--+--+--+--+--+--+
!1 !0 !1 !0 !0 !1 !1 !1 ! upper limit value exceeded, channel
+--+--+--+--+--+--+--+--+ word organized
If the DP-Slave transmits more diagnostic information than the DP_Master is able
to process in its diagnostic buffer, the DP-Master sets the bit
Diag.Ext_Diag_Overflow. If there are more diagnostic information pending at the
DP-Slave than can be transmitted, the following is to note:
- it is allowed to truncate only on the block limits of the device
related, identifier related or channel related diagnostic.
- if in the length field of the device related diagnostic or the identifier
related diagnostic a length unequal to zero is entered, this marks a
complete (not truncated) diagnostic block.
For efficiency reasons it is allowed to transmit a Diag_Data field with a fixed
length. In this case the unused bytes following Ext_Diag_Data shall be filled
with zero at the DP-Slave and/or the DP-Master (class 1).
9.3.2 Transfer Input and Output Data
This function permits the local user of the DP-Master to transmit output data to
a DP-Slave and at the same time to request input data from this remote station.
The number of input and output data which are reserved by the DP-Slave are
checked against the configuration data during the start-up phase of the DP-
System. If diagnostic messages or errors occur in the DP-Slave, the existence of
Page 730
PROFIBUS-Specification-Normative-Parts-8:1997
Copyright by PNO 1997 - all rights reserved
these messages is indicated to the DP-Master by means of a high prior response
frame (interpretation of Diag_Flag).
Table 9. DDLM_Data_Exchange
+------------------------------+-----+-----+-----+-----+
! Parameter Name !.req !.ind !_Upd !.con !
! ! ! !.req ! !
+------------------------------+-----+-----+-----+-----+
! Rem_Add ! M ! ! ! M !
! Outp_Data ! U ! U ! ! !
! ! ! ! ! !
! Status ! ! ! ! M !
! Diag_Flag ! ! ! M ! M !
! Inp_Data ! ! ! U ! U !
+------------------------------+-----+-----+-----+-----+
Rem_Add:
The parameter Rem_Add (Remote_Address) specifies the FDL address of the remote
station.
Type: Unsigned8
Range: 0 to 126
Outp_Data:
This parameter contains the output data. Normally the data conveyed in this
parameter are directly output to the periphery at the DP-Slave. If the Sync-Mode
is activated these data are buffered in the DP-Slave and are not output to the
periphery prior to renewed synchonization.
Type: Octet String
Length: Preferably 0 to 32 (extendible to 244, see section "Restrictions")
Status:
The parameter Status indicates success or failure of the function.
Possible values: OK,DS,NA,RS,RR,UE,RE
Diag_Flag:
This parameter indicates if a diagnostic exists at the DP-Slave. These
diagnostic information are fetched by the DP-Master (class 1) with the function
DDLM_Slave_Diag.
Type: Boolean
True: diagnostic existent
False: No diagnostic information
Inp_Data:
This parameter contains the input data of the DP-Slave.
Normally the delivered data in this parameter reflect the direct picture of the
DP-Slave periphery. If the Freeze mode is activated these input data are read
from an intermediate buffer. The data represent the state of DP-Slave periphery
in the moment of the last Freeze control command.
Type: Octet String
Length: Preferably 0 to 32 (extendible to 244, see section "Restrictions")