Why do I need to add "*" to my Alarm filter after upgrading from PLSCADA 7.20?
Issue
After upgrading from PLSCADA 7.20 or before, user now needs to add the wild character "*" to search for generic alarms.
Example:
In PLSCADA 7.20, user could search for all sags by typing in "sag" (without quotes) in the filter.
In Power SCADA Expert (PSE) 7.30 and above, user will need to type in "*sag" (without quotes) to get the same result.
Product
Power SCADA Expert 7.30 and above
PLSCADA 7.20 and below
Environment
OS supported by PLSCADA or PSE software
Cause
Changes to the alarming engine now require the "*" to be prepended to the string the user is filtering on.
Resolution
User must now prepend "*" to any filter if the word being filtered is not the first word in the alarm.
After upgrading from PLSCADA 7.20 or before, user now needs to add the wild character "*" to search for generic alarms.
Example:
In PLSCADA 7.20, user could search for all sags by typing in "sag" (without quotes) in the filter.
In Power SCADA Expert (PSE) 7.30 and above, user will need to type in "*sag" (without quotes) to get the same result.
Product
Power SCADA Expert 7.30 and above
PLSCADA 7.20 and below
Environment
OS supported by PLSCADA or PSE software
Cause
Changes to the alarming engine now require the "*" to be prepended to the string the user is filtering on.
Resolution
User must now prepend "*" to any filter if the word being filtered is not the first word in the alarm.
게시 대상: 슈나이더 일렉트릭 Korea
도움이 필요하신가요?
제품 선택기
애플리케이션에 적합한 제품과 액세서리를 빠르고 쉽게 찾을 수 있습니다.
견적 받기
영업 관련하여 온라인으로 문의하시면 전문가가 연락드립니다.
구매처
해당 지역의 가장 가까운 슈나이더 일렉트릭 대리점을 쉽게 찾을 수 있습니다.
지원 센터
한 곳에서 모든 요구 사항에 대한 지원 리소스를 찾아보십시오.