Diagnostic Management - Agilent Technologies TwisTorr 305 FS User Manual

Technical Information

Diagnostic Management

In addition to the ProfiBus six byte standard diagnostic, the interface provides both
user diagnostic and static diagnostics functions.
The standard diagnostic management is fully compliant with the ProfiBus
specification.
During the start-up phase after power on, the first byte in the user diagnostic area,
can assume values different from zero.
This byte has the following meaning:
Bit 0 = 1: controller not responds (RS485 link broken)

Bit 1 = 1: controller not identified (not compatible with the ProfiBus gateway)

Bit 2 = 1: first loop of requests not ended (values in the input data are not fully

coherent yet)
So, if the first byte is equal to 0, the interface is working properly, otherwise there is
a problem.
Each nibble in the bytes following the interface status byte represents the status of
the last attempt to write a parameter with following coding (diag status byte):
0
1
2
3
4
5
6
F
The ProfiBus external diagnosis services are used to report following unexpected
situations:
Controller fail: if the controller goes in fail mode, an external diagnostic service

is required and one byte in the diagnostic buffer signals the type of failure.
User parameter mismatch: if the user sets one or more parameters out of their

allowed range, a ProfiBus external diagnostic service is required and some bits
in the diagnosis frame signals which parameter is wrong (i.e. over range or
under range).
Agilent TwisTorr 305 FS Remote Controller User Manual
Write success
Controller response was "NACK"
Controller response was "Unknown window"
Controller response was "Bad Data Type"
Controller response was "Over range"
Controller response was "Bad operation"
Controller response was an unknown response
Parameter not supported by the controller
255