VEGA VEGASON 54P…56P Profibus PA - Manual (Page 50)

50 VEGASON 54P … 56P
PA function diagram and parameters
5.2 Status bytes
Coding of the status byte on the PA output value
Status code Descr. acc. to Profibus standard Probable causes in the VEGA sensor
0x00 bad – non-specific - Flash-Update active
0x04 bad – configuration error - Adjustment error
- Configuration error with PV-Scale
(PV-Span too small)
- Differences in meas. unit
- Error in the linearisation table
0x0c bad – device failure - Hardware error
- Converter error
- Leakage pulse error
- Trigger error
0x10 bad – sensor failure - Meas. value error
- Temperature error
0x1f bad – out of service - constant - "Out of Service" mode switched on
0x44 uncertain – last unusable value - Failsafe useable value (Failsafe-Mode =
"Last valid value" and already valid meas.
value since switching on)
0x48 uncertain – substitute set - Simulation switched on
- Failsafe substitute value (Failsafe-Mode =
"Fsafe value")
0x4c uncertain – initial value - Failsafe substitute value (Failsafe-Mode =
"Last valid value" and no valid meas.
value since switching on)
0x51 uncertain – sensor conversion - Sensor value < lower limit
not accurate – low limited
0x52 uncertain – sensor conversion - Sensor value > upper limit
not accurate – high limited
0x80 good (non-cascade) - ok - ok
0x84 good (non-cascade) – active - Static revision (FB, TB) changed (active
block alarm for 10 sec., after parameter was written
in static category)
0x89 good (non-cascade) – active - Lo-Alarm
advisory alarm – low limited
0x8a good (non-cascade) – active - Hi-Alarm
advisory alarm – high limited
0x8d good (non-cascade) – active - Lo-Lo-Alarm
critical alarm – low limited
0x8c good (non-cascade) – active - Hi-Hi-Alarm
critical alarm – high limited
Note:
All 256 possible status byte values can also be generated by simulation. For this reason, the Failsafe-Mode
should be set to "Wrong calculated value", so that the simulated status will not be modified by the Failsafe cal-
culation.