Diagnostic Management; Diagnostic Buffer - Varian Turbo-V 81-AG Rack Controller Notice De Mode D'emploi

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 Write success
1 Controller response was "NACK"
2 Controller response was "Unknown window"
3 Controller response was "Bad Data Type"
4 Controller response was "Over range"
5 Controller response was "Bad operation"
6 Controller response was an unknown response
F Parameter not supported by the controller
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
range).
(i.e. over range or under

Diagnostic buffer

Off
Set
0 B station non exist (set by master)
0
B station not ready (slave not ready for
1
data exchange)
cfg fault (configuration data doesn't
B
2
match)
ext diag (slave has external
B
3
diagnostic data)
B not supported (slave doesn't support
4
requested function)
B invalid slave response ( slave sets
5
permanent '0')
B prm fault (wrong parameter
6
assignment)
B master_lock (slave is parameterised
7
by another master)
1 B prm req (slave has to be re-
0
parameterised)
stat diag (static diagnosis)
B
1
B fixed '1'
2
B wd_on (response monitoring active)
3
Freeze mode (received freeze
B
4
command)
Synch mode (received synch
B
5
command)
B reserved
6
diag deactivated (slave is
B
7
parameterised by another master)
2 Reserved
3 Master Add (master address after
parameterisation. FF= without parameter)
4 Ident number high
5 Ident number low
6 External diagnosis "Header" length
indication including header
7 Interface Status
B Controller not responds
0
B Controller not identified
1
B Input data not fully coherent yet
2
B Not used
3
B Not used
4-7
8 B – Start/Stop diag status
7-4
B – Low Speed diag status
3-0
9 B – Soft Start diag status
7-4
B – Vent Valve
3-0
1 B – Purge Valve
7-4
0 B – Mode
3-0
1 B – High speed
7-4
1 B – Low Speed
3-0
105
TECHNICAL INFORMATION
Meaning
87-900-986-01 (C)