Testing error responses

To facilitate startup, all error responses can be triggered with test errors. To do so, assign the required code number of an error response (10, 20, 30 or 40) to the corresponding device of the usiTestErrorReactionCode input variable in the user interface of the ErrorManager, and activate the test using the input variable xSetTestError. Remaining runtimes are stored, especially for responses 20 and 30, which should be sufficient to stop the system in an emergency stop. By performing a test, the specified parameters can be tested and adjusted if necessary. By setting the xSetDeviceError input variable, the device (MDP92A / MDE90A) is set to error E26.1 (external error). 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.