Emerson NGA2000 Benutzerhandbuch
System Calibration
90003749(1) [NGA-e (CLD-Software 2.3/MLT-Software 3.1.X)] 04/98
NGA 2000
Supplement - 13
3.4 Controlling System Calibration
After setting-up there is the possibility to start 3 different modes:
system zero-calibration:
In this mode a zero-cal of all modules, which are
enabled for SYSCAL, will be performed. The order of
modules depends on purge time for zero-valves
because the whole calibration is time optimized.
enabled for SYSCAL, will be performed. The order of
modules depends on purge time for zero-valves
because the whole calibration is time optimized.
system zero/span-calibration:
In this mode will be performed a zero-cal and a span-
cal for every enabled AM. The order of calibration is
optimized to have a minimum of calibration time. The
only condition is to have for each AM first the zero-cal
and after this the span-cal. With zero-cal an AM is
zeroed with all ranges together, the span-cal is done
separately for all available ranges. A range is available
if its span-gas value is > 0.0.
cal for every enabled AM. The order of calibration is
optimized to have a minimum of calibration time. The
only condition is to have for each AM first the zero-cal
and after this the span-cal. With zero-cal an AM is
zeroed with all ranges together, the span-cal is done
separately for all available ranges. A range is available
if its span-gas value is > 0.0.
user defined sequence program: In this mode the user is responsible for the
optimization. See setup of this mode.
gas test:
It is also possible to switch for test purposes onto a
specific gas of a specific module. A calibration is not
done.
specific gas of a specific module. A calibration is not
done.
Any mode can be started by the following instances:
•
Manually by operator interaction
•
Triggered by programmable input (DIO)
•
AK-protocol command
•
Programmed time-automatic (no gas test possible!)
•
LON-Variable CMFUNC
It is also possible to cancel a running system calibration. This can be done by the following
instances:
instances:
•
Manually by operator interaction
•
Triggered by programmable input (DIO)
•
AK-protocol command
•
LON-Variable CMFUNC
There is no priority by which way SYSCAL can be started. If SYSCAL was started it can
not be restarted by a further instance. Only after canceling it can be restarted.
not be restarted by a further instance. Only after canceling it can be restarted.