Parametrisation Diagnostic; Output Buffer Diagnostics - Agilent Technologies TMP Profibus 969-9261 Bedienungshandbuch

Bit 1
Bit 2
So, if the first byte is equal to 0, the interface is working properly,
otherwise there is a problem.
Following the first user diagnostic byte there are the diagnostic
buffers correlated to each device connected to the low-speed network
(RS-485).
Each buffer is divided in two sections:

Parametrisation Diagnostic

Two bytes reporting the result of each single parameterisation
operation (MSB of byte 0 is correlated to the first parameters, LSB of
byte 1 is correlated to the 16th parameter).
Refer to the relative "Parameter Buffer Structure" "Diagnosis byte-bit"
column.

Output Buffer Diagnostics

Each nibble in the bytes following the parametrisation diagnostic
buffer, represents the status of the last attempt to write a parameter
with following coding (diag status byte):
0
1
2
3
TMP Profibus Gateway User Manual / 87-900-976-01 (F)
1: controller not identified (not compatible with the ProfiBus
gateway)
1: first loop of requests not ended (values in the input data
are not fully coherent yet)
Write success
Controller response was "NACK"
Controller response was "Unknown window" (parameter not
supported by the controller model)
Controller response was "Bad Data Type"
Technical Information
Diagnosis Management
18
167/178