FLISR is Re-triggering on Single-Phase Trips When Another Phase has Already Locked Out
(Doc ID 2853100.1)
Last updated on MARCH 02, 2022
Applies to:
Oracle Utilities Network Management System - Version 2.4.0.1.0 to 2.5.0.1.0 [Release 2.4 to 2.5]Oracle Network Management for Utilities - DMS - Version 2.4.0.1.0 to 2.5.0.1.0 [Release 2.4 to 2.5]
Information in this document applies to any platform.
Symptoms
On : 2.4.0.1.0 version, Web Workspace
FLISR is re-triggering on non three-phase trips when another phase has already locked out.
It is expected that if B and C phase lock out and FLISR fails to solve and then A phase locks out, FLISR should not attempt to solve.
How to Repeat
- Set FLISR_SINGLE_PHASE_MODE "Rule Value 2" to "1"
- Set FLISR_VOLT_LOSS_THRESHOLDS "Rule Value 1" to "disabled"
- Restart services
- Set SCADA measurements to OPEN and Indicate a fault (FI) on a single-phase of a breaker.
- Wait 5 seconds and set the Phase Lockout (PL) on the same phase of step 1. for that device.
- Wait 75 seconds so FLISR can run and finish the work.
- Set SCADA measurements to OPEN and Indicate a fault (FI) on a a different single-phase of the same breaker.
- Wait 5 seconds and set the Phase Lockout (PL) on the same phase of step 4. for that device.
- Observe NO duplicate messages on FLISR event shown on Work Agenda.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
Fix Description |
Migration |
References |