Error Handling; General - Heinzmann Programmer 2 Manual

7 Error Handling

7.1 General

The HEINZMANN Digital Controls include an integrated error monitoring system by
which errors caused by sensors, speed pickups, etc., may be detected and reported. By
means of two different permanently assigned digital outputs the error types can be output
via some visual or audible signal at nearly all HEINZMANN speed governors.
There is also the possibility of having a basic diagnosis performed by means of error
indications by LEDs and, when working with the PRIAMOS series, an additional
diagnosis by means of seven segment display.
The different errors can be viewed by the parameters 3000..3099. A currently set error
parameter will read the value "1", otherwise the value "0".
Generally, the following errors types can be distinguished:
Errors in configuring the control and adjusting the parameters
These errors are caused by erroneous input on the part of the user and cannot be
intercepted by either the PC or the Hand Held Programmer. They do not occur with
controls from series production.
Errors occuring during operation
These errors are the most significant ones when using governors produced in series.
Errors such as failure of the speed pickups, setpoint adjusters, pressure and
temperature sensor or logical errors such as excessive temperatures or low boost
pressure are typical of this category.
Internal computational errors of the control
These errors may be due to defective components or other inadmissible operating
conditions. Under normal circumstances, they are not likely to occur.
To cancel an error one should first establish and eliminate its cause before clearing any of
the current errors. Some errors are cleared automatically as soon as the failure cause has
been eliminated. Errors can be cleared by means of the PC, by the Hand Held Programmer
or, if accordingly configured, by the digital input 2828 SwitchErrorReset. If the system
does not stop reporting an error, the search for its cause must go on.
Principally, the control starts operating on the assumption that there is no error and will
only then begin to check for possible occurrences of errors. This implies that the control
can be put into an error free state by a reset of the control unit, but will immediately begin
to report any errors that are currently active.
There are two categories of errors. One category comprises errors that permit of
maintaining engine operation though functionality will in some cases be restricted (e.g.,
Programmer PG 02
7 Error Handling
33