Introduction To ProfiBus DP
__________________________________________________________________
_______________________________________________________________________________________
Acromag, Inc. Tel:248-624-1541 Fax:248-624-9234 Email:sales@acromag.com http://www.acromag.com
32
The parameter Status can be tested to indicate the success or failure of
the Diag_Data function with possible values of: OK, DS, NA, RS, UE, NR,
and RE.
The following bits are taken from the diagnostic information bytes above
and treated as follows:
PRM_REQ (From DU Byte 2)
If this flag is set, the slave has to be parameterized. The application
has detected a state requiring a new startup with appropriate
reparameterization and reconfiguration. Following this diagnostic, the
master performs a startup with specified reparameterization and
configuration.
An example where this type of diagnostic might occur is if a modular
ProfiBus system has been expanded (i.e. a module was added).
There are three diagnostic bits that can be driven by the application:
STAT_DIAG, EXT_DIAG, and EXT_DIAG_OVERFLOW.
STAT_DIAG (From DU Byte 2)
Because of a state in the application, the slave cannot provide valid
data. After receiving this diagnostic, the master continues to request only
diagnostic information from this slave until the slave resets this bit. If the
normal ProfiBus DP state is data exchange, data communication can be
resumed immediately after the static diagnosis bit is cleared. An example of
where this diagnostic may be encountered is for a slave whose output driver
voltage supply has failed.
EXT_DIAG (From DU Byte 1)
The slave uses the EXT_DIAG=1 bit to signal that user-specific
diagnostic data is present in the user diagnostics area. EXT_DIAG=1
causes a diagnostic telegram to be sent to the ProfiBus master. After the
cause of the diagnostic message has been corrected (the applicable bit
combination in the user-related diagnostic data is 0), the EXT_DIAG bit must
also be reset (set to 0) and this is necessary for certification.
If this bit is set, a diagnostic entry must be present in the user-related
diagnostic area. If this bit is clear, then the standard status information of
the diagnostic area is involved and this is handled with a lower priority.
When the EXT_DIAG bit is cleared (0), the data must be considered as
status information from the viewpoint of the system and this data is not
treated as diagnostic data by the master.
EXT_DIAG_OVERFLOW (From DU Byte 3)
The slave sets this bit when more diagnostic data is available than will
fit into the area provided for diagnostic data. For example, more channel
diagnostic data may be present than the sending buffer or the receiving
buffer of the master can hold.
Comentarios a estos manuales