Technical data

MESOMATIC Automation und Messtechnik GmbH D-71394 Kernen
4.4.4. Slave diagnosis
The standard diagnosis reads "DK900_V1.0".
If the DK900 Profibus controller is unable to get into contact with the DK900, or if the
communication with the DK900 has been interrupted, a diagnosis with the EXT_DIAG Bit being
set will be put out.
Diagnosis via the Profibus:
Byte Description
0 Number of the bytes of the diagnosis (0x0F hex)
1..10 Text "DK900
_
V1.0"
11 Fatal ERROR, the EXT_DIAG Bit will be set
Bit 7 Successive serial data errors
Bit 6 Successive serial timeout errors
Bit 5 ROM error (gateway)
Bit 4 RAM error (gateway)
Bit 0 Reserved, this bit does not cause any diagnosis.
12 Last error code
Bit 5 No valid Profibus address received from EEPROM.
Bit 4 No valid Profibus address received via the serial
interface.
Bit 3 Serial data error
Bit 2 Serial timeout
Bit 1 Hardware error
13 Counter (constant) of the errors occurred
14 Bit 0 Reserved (1)
Table 7 Diagnosis
4.4.5. The extended identifier (0xC0, 0xFF, 0xFF)
The extended identifier serves only to configure the DK900 at the manufacturer’s plant. It
does not allow to be configured together with other identifiers, but only alone.
The channel of the extended identifier allows to transmit to the DK900 serial commands with
a length of up to 125 Bytes, via the Profibus.
Attention! Not all Profibus Masters support extended identifiers.
Attention! The configuration parameters of the DK900 comprise appr. 1 kilobyte of data
(appr. 10 data blocks of about 100 Bytes each), which must then be stored and
managed by the Master.
DK900 18