Which products are affected?
TensionControl template as of V2.0, DancerControl template as of V2.0
What happens?
Although g_DCTRL_bTripReset=TRUE is written from the user program a pending error is sometimes not reset although the error cause has been eliminated.
When does the problem occur?
Dependent on the status of the button in the visualisation for resetting an error the g_DCTRL_bTripReset input of the target interface is cyclically written from the template. In order to acknowledge an error from the user's side it is only possible to use the same interface. Due to this parallel operation it may happen that the command is not accepted.
Possible diagnostics?
The DCTRL_bTripReset input is to be set to TRUE in the control configuration or once from the user program. Afterwards it can be observed that this status is not maintained as expected but reset to FALSE after a very short period of time.
Short-term measures/recommendations?
In order to acknowledge the error the reset input g_DCTRL_bTripReset=TRUE must be written several times from the user program, i. e. cyclically or in an interval task.
Evaluation:
An error can be acknowledged by repeated writing. The operation via the visualisation mainly serves for demonstration purposes and is not used in the every day production routine. In the template documentation it is explicitly pointed out that the g_DCTRL_bTripReset variable must not be accessed and written from the user program.
