Tabla de contenido
Publicidad
Diagnostic management
In addition to the ProfiBus six byte standard diag-
nostic, the interface provides both user diagnostic
and static diagnostics functions
The standard diagnostic management is fully com-
pliant with the ProfiBus specification.
During the start-up phase after power on, the first
byte in the user diagnostic area, can assume val-
ues 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 compati-
ble with the ProfiBus gateway)
•
Bit 2 = 1: first loop of requests not ended (val-
ues 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 at-
tempt 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 re-
quired 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).
Diagnostic buffer
OFF
SET
0
B
station non exist (set by master)
0
B
station not ready (slave not ready for
1
data exchange)
B
cfg fault (configuration data doesn't
2
match)
B
ext diag (slave has external diagnostic
3
data)
B
not supported (slave doesn't support re-
4
quested function)
B
invalid slave response ( slave sets per-
5
manent '0')
B
prm fault (wrong parameter assignment)
6
B
master_lock (slave is parameterised by
7
another master)
1
B
prm req (slave has to be re-
0
parameterised)
B
stat diag (static diagnosis)
1
B
fixed '1'
2
B
wd_on (response monitoring active)
3
B
Freeze mode (received freeze com-
4
mand)
B
Synch mode (received synch com-
5
mand)
B
reserved
6
B
diag deactivated (slave is parameter-
7
ised by another master)
2
Reserved
3
Master Add (master address after parameterisa-
tion. 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
Active Stop diag status
3 - 0
10
B
Vent Valve diag status
7 - 4
B
Purge diag status
3 - 0
11
B
Heater Jacket diag status
7 - 4
B
Stop Speed Reading diag status
3 - 0
12
B
High speed setting diag status
7 - 4
B
Low speed setting diag status
3 - 0
13
B
Water Cooling Max Temp diag status
7 - 4
B
Water Cooling Hyst diag status
3 - 0
14
B
Set Point Hyst diag status
7 - 4
B
Heater Jacket Setting diag status
3 - 0
15
B
Flow Meter Threshold diag status
7 - 4
B
Reserved diag status
3 - 0
16
B
Set Point Value diag status
7 - 4
B
Set Point Delay diag status
3 - 0
17
B
Vent Valve Open Delay diag status
7 - 4
B
Vent Open Time diag status
3 - 0
92
TECHNICAL INFORMATION
MEANING
87-900-968-01(C)
Publicidad
Tabla de contenido
