Dynamics voltage violation checks

asked 2020-07-19 13:57:54 -0600

boat14 gravatar image

updated 2020-07-24 08:02:04 -0600

Can someone help explain the usage for the dynamics voltage violation checks in PSS/e 34?

This is under the "Voltage Violation" tab in the "Dynamics" > "Dynamic Simulation Options" dialog box.

To see if I could get it to work, I did the following:

  • Set up my contingency script to include the following before initializing:

iErr = psspy.set_volt_viol_subsys_flag(all = 1) # Monitor all buses for voltage violations

iErr = psspy.set_voltage_rec_check(vprchk = 1, vprthr = 0.98, vprtim = 0.1) # Primary voltage check for violations below 0.98 for 0.1s

  • Simulated a large bus fault for several cycles.
  • Cleared the fault and triggered the voltage violation check:

iErr = psspy.trig_volt_violation_check(1) # Trigger voltage violation checks

After that, I checked the progress output log but I didn't find anything that stood out. I'm fairly certain there were voltage violations as I did a quick spot check in PSSPLT and found several buses that had bus voltages below 0.98 for longer than 0.1s after the fault.

Resolved edit: It turns out there's a bug in the PSS/e python API. Running the commands in batch form is the working alternative and violations show up in the progress output like this:

VOLTAGE PRIMARY RECOVERY CHECK AT BUS 151 TESTBUS
AT TIME  1.183 VOLTAGE AT BUS WAS BELOW THE THRESHOLD VALUE OF 0.980 pu FOR MORE THAN  0.100 (s)
edit retag flag offensive close merge delete