Supported Features
Supported PSS®E Components
Each PSS®E component is mapped into one or multiple HYPERSIM components, depending on the type and parameters of the PSS®E component.
For instance, the synchronous machine component of the PSS®E is converted to HYPERSIM's synchronous machine and controllers if the dynamic data is available.
The list of all supported PSS®E components can be found under C:/OPAL-RT/UnifiedDatabase/Documentation/docs/phasor/HYPERSIM.html#phasor-domain-to-hypersim
Replace Machines Option
The Replace machines with voltage sources option allows users to replace a machine with an ideal voltage source if the machine is linked to an unsupported control component (Exciter, Stabilizer or Turbine/Governor).
- If the option is not activated, the machine is imported without its controls.
- If the exciter is not supported, the associated stabilizer is not imported either, as the stabilizer must be connected to the exciter of the machine.
Sequence data
The sequence data of the system can be provided by the *.seq file of the PSS®E. This data is used to calculate the unbalanced fault current in the PSS®E for the steady-state condition.
Once a *.seq file is present, the tool completes the line and transformer parameters using the sequence data.
The sequence data of the machine may have some conflicts with the dynamic data, moreover, the machine parameters are available in the *.dyr file. Therefore, non of the machine data is mapped from the *.seq file.
Coordination
The coordination of the components can be defined by *.gps or *.substations file.
An example of a *.gps file is as follows:
Substation,Latitude,Longitude,BUS#,BUS NAME,BUS VOLTAGE (kV),PSSE Bus Name,
STATION1,45.5019,73.5674,1,BUS1,345,,
STATION2,45.5666,73.5444,1,BUS2,345,,
An example of a *.substations file is as follows:
Substation,BUS#,BUS NAME,x,y
STATION1,1,b1,-100,0
STATION2,1,b2,-120,10
Auto-Layout
In the case of the absence of neither *.gps nor *.substations, an auto-layout algorithm is used to generate coordinates in the HYPERSIM.
Conversion Reports
For each import, the reports will be stored in the folder of ConversionReports_YYYY-MM-DD_HH-mm next to the PSS®E file. The report files are as follows:
computer.log : The report of calculating variables to generate components in the database
export.log : The report of generating netlists used to create python code and the edd file
full.log : The full report containing the export.log, computer.log, mapper.log, parser.log, hypersim_import.log
hs_error.log : The list of errors happened during importing the model in the HYPERSIM
hs_import.log : The report of the imported model in the HYPERSIM. This report contains the details of adding, connecting, rotating, and setting the parameters of the components in the HYPERSIM
hypersim_import.log : The outline report of the imported model for the HYPERSIM
mapper.log : The mapper report, including skipped unsupported components
names.json : The list of components in the PSS®E files
parser.log : The parser report, including errors during parsing
{model_name}.edd : The generated edd file used to import the model into the HYPERSIM
{model_name}.py : The generated python code used to import the model into the HYPERSIM
nonImportedComponents.csv : The list of unsupported components found in the PSS®E file, and a list of the machines replaced with voltage sources (only when this option is activated)
Limitations
Supported PSS®E Files
Only data from *.raw, *.dyr, *.seq, and *.gpg or *.substations files are used to import to HYPERSIM. Even if other files with the same names are provided (for instance *.sld files), they are ignored by the import tool.
In the *.raw files, bus base voltages are considered to be rms line-to-line voltages and are given in kV.
Only files of the PSS®E version 32 are officially supported. However, it is still possible to export files of the newer versions of PSS®E.