I found a display bug in the para regarding alert handling configs with old/migrated alerts (The alerts itself are working as expected).
1. We have migrated a project from PVSS 3.9 to WinCC OA 3.14
2. We have alerts with the following settings: Boolean, discrete, good range: 1
3. After migrating the project the para from 3.14 displays these alerts with a good range of 0 instead of 1.
It seems that the internal format of the alert_hdl has changed.
Creating an ASCII export with a 3.9 and a 3.14 project shows that these are created different between the versions.
The rows for DetailNr are switched and column _alert_hdl.._match uses other values.
While the alerts still work the para cannot handle this and shows wrong information.
Example from an ASCII export:
Code: Select all
PVSS 3.9
ElementName TypeName DetailNr _alert_hdl.._type _alert_hdl.._class _alert_hdl.._match
AlarmTest01.Value AlarmTest 13
AlarmTest01.Value AlarmTest 1 5 S7_Warning. 0
AlarmTest01.Value AlarmTest 2 5 1
WinCC OA 3.14
ElementName TypeName DetailNr _alert_hdl.._type _alert_hdl.._class _alert_hdl.._match
AlarmTest01.Value AlarmTest 13
AlarmTest01.Value AlarmTest 1 5 *
AlarmTest01.Value AlarmTest 2 5 S7_Warning. 0