Testing error responses

To facilitate startup, all error responses can be triggered with test errors. To do so, assign the required code number to an error response (10, 20, 30 or 40) to the input variable usiTestErrorReactionCode in the user interface of the ErrorManager for the corresponding device, and activate the test with the input variable xSetTestError. Responses 20 and 30 in particular contain remaining runtimes that should be sufficient to stop the system in the event of an emergency stop. By performing a test, the specified parameters can be tested and readjusted, if necessary. The device (MDP92A / MDE90A) is set to error E26.1 (external error) by setting the input variable xSetDeviceError. This error has response code 10 because it is a device fault. The error response is performed accordingly. A device fault can only be set if the device is not in FCB 51.