1 / 15

Angel Aquino, Ph.D. WECC MVWG June 19-20, 2013

SVCs Modeling in PowerWorld Simulator. Angel Aquino, Ph.D. WECC MVWG June 19-20, 2013. angel@powerworld.com 217-398-2340 ext. 21. SVSMOx Models. Types of SVC models from WECC standard svsmo1 – SVC is assumed to consist of at least one TCR coordinated with MSSs .

tryna
Download Presentation

Angel Aquino, Ph.D. WECC MVWG June 19-20, 2013

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SVCs Modeling in PowerWorld Simulator Angel Aquino, Ph.D.WECC MVWGJune 19-20, 2013 angel@powerworld.com 217-398-2340 ext. 21

  2. SVSMOx Models • Types of SVC models from WECC standard • svsmo1 – SVC is assumed to consist of at least one TCR coordinated with MSSs. • svsmo2 – SVC is assumed to consist only of TSR and/or TSC branches resulting in a fast discrete device coordinated with MSSs. • svsmo3– generic SVS model incorporating a STATCOM and coordinated with MSSs. • PowerWorld created specific models in Simulator with the same name. • svsmo1 , svsmo2 and svsmo3

  3. Implementation in Simulator • Models can be read directly from a DYD • May also create them through the Simulator interface or by reading Simulator AUX files • Steady State model is read from an EPC file • Inputs in the EPC are included with some modifications in Simultor: • SVC EPC Type 5 will be set to svsmo1 • SVC EPC Type 6 will be set to svsmo3 • SVC EPC Type 7 will be set to svsmo2

  4. SVSMO1 DYD Specification #SVSMO1 model svsmo1 40598 " KEELER E " 230 "v1" 40598 " KEELER E " 230 : #9 "UVSBmax" 0.50 "UV1" 0.6 "UV2" 1.1 "UVT" 0.0 "OV1" 1.3 "OV2" 1.5 "UVtm1" 30.0 "Uvtm2" 40.0 "OVtm1" 30.0 "Ovtm2" 40.0 "flag1" 1. "flag2" 0. "Xc1" 0.02 "Xc2" 0.0 "Xc3" 0.0 "Vup" 1.1 "Vlow" 0.0 "Tc1" 0.0 "Tb1" 0.01 "Tc2" 0.0 "Tb2" 0.0 "Kpv" 50.0 "Kiv" 250.0 "vemax" 99.9 "vemin" -99.9 "T2" 0.01 "Bshrt" 3.50 "Bmax" 3.5 "Bmin" -3.0 "Tshrt" 999.0 "Kps" 0.0 "Kis" 0.00001 "vrmax" 1.15 "Vrmin" 0.0 "Vdbd1" 0.0 "Vdbd2" 0.0 "Tdbd" 0.0 "PLLdelay" 0.03 "eps" 0.5 "Blcs" 170.0 "Bscs" 45.0 "Blis" -180.0 "Bsis" -50.0 "Tmssbrk" 25.00 "Tdelay1" 25.00 "Tdelay2" 25.00 "Tout" 300.0 Simulator Specification

  5. SVSMO2 DYD Specification #SVSMO2 model svsmo2 40893 "ROGUE " 230 "V1" 40893 "ROGUE " 230 : #9 "UVSBmax" 0.20 "UV1" 0.5 "UV2" 0.3 "UVT" 0.5 "OV1" 1.3 "OV2" 1.5 "UVtm1" 1.0 "Uvtm2" 7.0 "OVtm1" 1.0 "Ovtm2" 0.25 "flag1" 1 "flag2" 0. "Xc1" 0.0 "Xc2" 0.0 "Xc3" 0.0 "Vup" 1.1 "Vlow" 0.0 "Tc1" 0.0 "Tb1" 0.01 "Tc2" 0.0 "Tb2" 0.0 "Kpv" 1.0 "Kiv" 25.0 "Vemax" 99.9 "Vemin" -99.9 "T2" 0.01 "Bshrt" 0.50 "Tshrt" 999.0 "Kps" 0.0 "Kis" 0.00001 "vrmax" 1.15 "Vrmin" 0.0 "Vdbd1" 0.0 "Vdbd2" 0.0 "Tdbd" 0.0 "PLLdelay" 0.03 "eps" 0.5 "Blcs" 8.0 "Bscs" 8.0 "Blis" -10.0 "Bsis" -10.0 "Tmssbrk" 25.00 "Tdelay1" 25.00 "Tdelay2" 25.00 "Tout" 300.0 "dbe" 0.002 "dbb" 0.01 "PrintB" 0 Simulator Specification

  6. SVSMO3 DYD Specification #SVSMO3 model svsmo3 47801 "HOPKR 1 " 34.50 "v1 " 47801 "HOPKR 1 " 34.50: "modbase" 100.1 "Xc0" 0.011 "Tc1" 0.01 "Tb1" 0.11 "Kp" 0.01 "Ki" 25.1 "vemax" 0.51 "vemin" -0.510 "To" 0.0051 "Imax1" 1.1 "dbd" 0.1 "Kdbd" 10.1 "Tdbd" 0.11 "Kpr" 0.01 "Kir" 0.0011 "Idbd" 0.21 "Vrmax" 0.11 "Vrmin" -0.101 "Ishrt" 1.41 "UV1" 0.51 "UV2" 0.21 "OV1" 1.11 "OV2" 1.21 "Vtrip" 1.31 "Tdelay1" 1.1 "Tdelay2" 0.081 "ecap" 0.01 "Iupr" 0.51 "Ilwr" -0.51 "TdelLC" 60.1 "Tout" 300.1 "sdelay" 0.021 "I2t" 0.01 "Reset" 0.1 "hyst" 0.1 "flag1" 1.01 "flag2" 0.011 "Xc1" 0.1 "Xc2" 0.1 "Xc3" 0.011 "V1" 1.0215 "V2" 0.9751 "Tc2" 0.01 "Tb2" 0.01 "Tmssbrk" 0.01 Simulator Specification

  7. Example with SVSMO1 Switched Shunt to which the model belongs • The regulated bus. • None means the terminal bus. • Floating point inputs

  8. SVSMO1 Dynamic Model Diagram + +

  9. SVSMOs Matching power Flow Data • Power Flow Data Loaded from epc or AUX file • MSSs loaded from epc or AUX file • You can add or modify the parameters in the dialog. Can add or delete MSSs shunts. The control mode needs to be SVC

  10. SVSMOs Data Verification • The Power Flow Model needs to match the dynamic model to eliminate initialization issues in the transient stability. • There are a couple pieces of input data that are duplicated in the power flow and dynamic data sets • Linear droop parameter Xc • Control mode in the Power Flow model implies which dynamic model • What should software do when these don’t match?

  11. Data Verification:Droop Control • Droop Data must match • Power Flow Data: Xc value • Stability Data: Xc1 value • What should we do when they don’t match • We’re already seeing this in WECC cases • Presently, initialization won’t be at steady state  no disturbance run will not be flat • We’re considering 3 options • Add a validation warning, but leave it the way it is • Add a validation warning message and change Xc1 internally so it matches Xc • Add a validation error message and prevent simulation

  12. Data Verification:EPC Device Type  SVSMOx

  13. PowerWorld Simulator Switched Shunt Control Advanced Options SVC Control Options

  14. What if Dynamic SVSMOx specified but doesn’t match? • Already seeing WECC cases • Fixed switched shunt with an svsmo1 model • Continuouswith an svsmo3 model • We could try to make some guesses at how to initialize these. • Should we do this? • Or should we just disable the dynamic model and add validation warnings

  15. Status • Available in Simulator 17 since January of 2013 • We’re still tweaking how to handle model validation warnings/errors

More Related