Documentation Home Page ◇ HYPERSIM Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.
Examples | PowerFactory Import 39-Bus New England System
The IEEE39 bus example model is a modified version of the default PowerFactory example
Details are provided below, see https://opal-rt.atlassian.net/wiki/spaces/PDOCHS/pages/940114297/Examples+PowerFactory+Import+39-Bus+New+England+System#Description
Location
This example model can be found in the HYPERSIM under the category "How To" with the file name "PowerFactory_Import_39_Bus.ecf".
The folder structure of this demo is as follows:
├───PowerFactory_Import_39_Bus
│ │ PowerFactory_Import_39_Bus.csv
│ │ PowerFactory_Import_39_Bus.svt
│ …
│ │
│ └───PowerFactory_ref_model
│ PowerFactory_Import_39_Bus.xml
│ PowerFactory_Import_39_Bus_Results.csv
The folder PowerFactory_ref_model contains the XML export of the PowerFactory model, and the simulation results from PowerFactory which can be used for comparison purposes.
Description
This model is a modified version of the 39 Bus System example provided by PowerFactory 2023:
A new Study Case was created in the original project, which is partially based on the EMT Simulation Fault Bus 03 one. This new Study Case was in turn associated to 4 modified network variations.
All together, this set of network variations results in a network model with the following modifications:
PH-E connected constant impedance, 100% static loads.
ESST1A excitation system models associated to all synchronous machines.
The model avr_ESST1A is located in the Data Manager at DIgSILENT Library\Dynamic Models\_ Archive\PF 2022 Models\PSS/E compatible\avr_ESST1A.BlkDef
Name | Value | Unit | Description |
|---|---|---|---|
Tr | 0 | [s] | Measurement Delay |
Tb | 10 | [s] | Filter 1st Delay Time Constant |
Tc | 1 | [s] | Filter 1st Derivative Time Constant |
Tb1 | 0 | [s] | Filter 2nd Delay Time Constant |
Tc1 | 0 | [s] | Filter 2nd Derivative Time Constant |
Ka | 200 | [pu] | Controller Gain |
Ta | 0.015 | [s] | Controller Time Constant |
Kc | 0 | [pu] | Current Limiter Factor |
Kf | 0 | [pu] | Stabilization Path Gain |
Tf | 1 | [s] | Stabilization Path Time Constant |
Klr | 0 | [pu] | Current Input Factor |
Ilr | 0 | [pu] | Current Input Reference |
Vos | 1 | [1,2] | PSS Input Selector |
Vel | 2 | [1,2,3] | Uel Input Selector |
Vimin | -0.1 | [pu] | Controller Input Minimum |
Vamin | -5 | [pu] | Controller Minimum Output |
Vrmin | -100 | [pu] | Exciter Minimum Output |
Vimax | 0.1 | [pu] | Controller Input Maximum |
Vamax | 5 | [pu] | Controller Maximum Output |
Vrmax | 100 | [pu] | Exciter Maximum Output |
Explicit reference angle definition = -30 deg, as a setpoint of the machine connected to the swing bus.
The events in the modified Power Factory Study Case are as follows:
A 2-Phase Short-Circuit event in Bus 03 at t = 0.3 s (phases A-B):
An immediate clearing of the short circuit in Bus 03 at t = 0.5 s:
Note that these two events are imported to HYPERSIM using a custom fault block () with the following parameters:
The following parameters are part of the default model and should remain unchanged
YN connected synchronous machines.
2-winding transformers without saturation, nor sequence data.
Import the PowerFactory model
The PowerFactory import tool aims to enhance efficiency by automatically converting models from PowerFactory to HYPERSIM. This feature not only saves time but also reduces the risk of errors associated with manual imports.
The PowerFactory import tool comprises a parser, mapper, and exporter:
The parser analyzes and interprets PowerFactory model components and parameters. It converts the PowerFactory xml file into a list of objects.
The mapper performs a mapping between PowerFactory and Unified Database (UDB) components and parameters.
The exporter creates the HYPERSIM model after a successful database import.
To import the example model, start by creating a new HYPERSIM model and continue by following the steps described in https://opal-rt.atlassian.net/wiki/spaces/PDOCHS/pages/940573160 .
As explained in https://opal-rt.atlassian.net/wiki/spaces/PDOCHS/pages/940114297/Examples+PowerFactory+Import+39-Bus+New+England+System#Location , the xml input file for the example can be found under the PowerFactory_ref_model folder.
Wait until the end of the import process. A message “Import successful” in the Import Panel interface indicates that the import is completed.
Simulation and Results
Load Flow Test
It is highly recommended to start a validation process by conducting a comparison of load flow results.
In the Load Flow Calculation window from PowerFactory, select “AC Load Flow, balanced, positive sequence” as the calculation method. Also, make sure the Consider Voltage Dependency of Loads option is selected. Then Execute the command.
The Network Model Manager will now display the updated load flow results. For instance, voltage magnitude and angle at each bus can be obtained from the Flexible Data table of the Busbar element, as shown below:
Load flow calculation must also be carried out in HYPERSIM (see the steps in https://opal-rt.atlassian.net/wiki/spaces/PDOCHS/pages/149750821). The table below shows the absolute errors in voltage magnitude and angle for all buses in the network model. Please notice that even though in general all error values are negligible, there is a relatively large mismatch in the voltage angle at bus 34 (i.e.,
Bus Name | Voltage Magnitude (p.u.) PowerFactory | Voltage Angle (deg) PowerFactory | Voltage Magnitude (p.u.) HYPERSIM | Voltage Angle (deg) HYPERSIM | Abs Error Magnitude (p.u.) | Abs Error Angle (deg) |
|---|---|---|---|---|---|---|
Bus 01 | 1.046214 | -12.0555 | 1.0462122 | -12.0329202 | 1.7732E-06 | 0.022611 |
Bus 02 | 1.045679 | -9.39227 | 1.0456804 | -9.36704637 | 1.3875E-06 | 0.025221 |
Bus 03 | 1.025286 | -12.0539 | 1.0252941 | -12.0285709 | 8.0735E-06 | 0.025317 |
Bus 04 | 0.998359 | -12.3966 | 0.9983732 | -12.3757845 | 1.4242E-05 | 0.020828 |
Bus 05 | 0.999966 | -10.9221 | 0.999983 | -10.9052561 | 1.6984E-05 | 0.016865 |
Bus 06 | 1.002336 | -10.1444 | 1.0023532 | -10.1283234 | 1.7244E-05 | 0.016065 |
Bus 07 | 0.992023 | -12.4492 | 0.9920393 | -12.4325911 | 1.6346E-05 | 0.016568 |
Bus 08 | 0.991209 | -13.0053 | 0.9912241 | -12.9884342 | 1.5077E-05 | 0.016849 |
Bus 09 | 1.026118 | -13.4384 | 1.0261248 | -13.4190768 | 6.7874E-06 | 0.019356 |
Bus 10 | 1.012398 | -7.9011 | 1.0124106 | -7.88227368 | 1.2572E-05 | 0.01883 |
Bus 11 | 1.00781 | -8.66865 | 1.007824 | -8.65071392 | 1.3972E-05 | 0.017932 |
Bus 12 | 0.980848 | -38.7538 | 0.9808615 | -38.7349346 | 1.352E-05 | 0.018841 |
Bus 13 | 1.009218 | -8.66974 | 1.0092313 | -8.64997982 | 1.3342E-05 | 0.019755 |
Bus 14 | 1.005863 | -10.4825 | 1.0058777 | -10.4603722 | 1.4702E-05 | 0.022126 |
Bus 15 | 1.007598 | -11.1703 | 1.0076148 | -11.1408674 | 1.6841E-05 | 0.029388 |
Bus 16 | 1.023418 | -9.84383 | 1.0234371 | -9.81134222 | 1.9118E-05 | 0.032491 |
Bus 17 | 1.026392 | -10.9972 | 1.0264056 | -10.9672343 | 1.3557E-05 | 0.029959 |
Bus 18 | 1.02455 | -11.8445 | 1.0245605 | -11.8162632 | 1.0473E-05 | 0.028188 |
Bus 19 | 1.033471 | -4.61092 | 1.0335418 | -4.56663021 | 7.0838E-05 | 0.044293 |
Bus 20 | 1.015495 | -5.5864 | 1.0121634 | -5.73269454 | 0.00333163 | 0.146291 |
Bus 21 | 1.024844 | -7.49965 | 1.0248568 | -7.46727255 | 1.2845E-05 | 0.032381 |
Bus 22 | 1.045289 | -3.05329 | 1.0452954 | -3.02098845 | 6.4183E-06 | 0.032305 |
Bus 23 | 1.040321 | -3.27612 | 1.0403282 | -3.24381711 |
OPAL-RT TECHNOLOGIES, Inc. | 1751, rue Richardson, bureau 1060 | Montréal, Québec Canada H3K 1G6 | opal-rt.com | +1 514-935-2323
Follow OPAL-RT: LinkedIn | Facebook | YouTube | X/Twitter