Which products are affected?
EVS93xx-EI (Servo PLC V6.x)
EVS93xx-ET (Servo PLC V6.x with technology function)
ESP-DDS2-x (Drive PLC Developer Studio V2.x)
What happens?
If the PLC program processing is stopped by a breakpoint, a task overrun, a manually activated stop (e. g. via code C2108) or a PLC reset the drive responds as set under
Project>Exceptional response.
However, if the exceptional response Warning is set the drive does not activate a warning:
- The system variable DCTRL_bWarn_b remains FALSE.
- The system variable DCTRL_wFaultNumber is 0.
- Code C0168/1 is 0.
The drive is inhibited and the PLC processing is stopped.
When does the problem occur?
When DDS V1.4 has been changed over to DDS V2.x the exceptional response
None has been replaced by
Warning in the
Exceptional behaviour dialog. However, the actual exceptional response of the drive still corresponds to
None.
Possible diagnostics?
Check via code C0183 (= 160: PLC STOP) if the PLC is stopped.
Short-term measures/recommendations?
None.
Evaluation:
According to standard the exceptional response is set to
Trip/CINH, i.e. if the PLC is stopped as described before the PLC activates a trip in the drive and the drive is inhibited. In very few cases the exceptional response is changed over to
Warning. If the PLC is stopped while the exceptional behaviour
Warning is activated, this can only be diagnosed via code C0183.
