Fixed as of:
L_IE1P_ApplicationError (as of V3.26.0)
Behavior of the new version:
If no “ModuleHandler” is connected, the error is logged via the “Application” module.
Description of the behavior:
Although the 'xSetError[y]" on the function block L_IE1P_SetError or L_IE1P_SetErrorSingle, no entry is made in the log. Furthermore, the defined error response is not executed.
Under what conditions does this behavior occur?
The behavior described above occurs when the 'ModuleHandler' input of the function blocks L_IE1P_SetError or L_IE1P_SetErrorSingle (from the L_IE1P_ApplicationErrors library) is not connected to the ModuleHandler of the Lenze i950 controller or servo drive.
Affected products:
L_IE1P_ApplicationError starting with V3.24
Short-term measures:
Connect the 'ModuleHandler' input of the function blocks L_IE1P_SetError and L_IE1P_SetErrorSingle to, for example, an instance of the function block L_IM1P_ModuleHandler.
Assessment/Recommendations:
The ModuleHandler function was introduced in the Lenze controller with Release V3.24. Every component in the controller system is connected to the ModuleHandler. This makes it possible to determine in the log which component triggered an error message. When an application-specific error message is triggered, the module or component that triggered the error message must be specified. This is done via the “ModuleHandler” input mentioned above.
[Automatic Translation]
