This document shows the steps of importing a PSCAD model into HYPERSIM.
| Table of Contents |
|---|
Step 1- Create a new HYPERSIM model
Select New from File tab, then create a HYPERSIM file.
...
Select the desired folder and choose the file name, then Save it.
...
Step 2- Import the PSCAD model
The PSCAD import feature can be found in the Network Import tools from the HYPERSIM
...
...
Select the *.pscx model from PSCAD option and Import it.
...
The input file should be a .pscx file. It does not need to be located next to the .ecf file.
Only .pscx files generated by PSCAD v4 and v5 can be used to import a model from PSCAD to HYPERSIM. Other PSCAD files such as *.babx or *.psmx are not used.
In case a component from a custom library is used in the model, the library file should be located in the identical folder as the *.pscx file.
Options
The following options are available
Only DLL configurations |
This options restricts the import to the PSCAD dll configuration files. |
Remove not connected buses |
This options removes automatically not connected buses if any. |
Additional information
Once the importing procedure is started, the Python API analyzes the PSCAD input circuit and prepares a Python script. This script relies on data stored in a folder named ConversionReports_YYYY-MM_DD-DD_HH-mm, located next to the PSCAD input file. Subsequently, the Python script is executed, importing the model into HYPERSIM. Each component is assigned a unique identifier that corresponds precisely to its PSCAD original identification number, facilitating easy reference to the original design. The duration of the conversion process varies depending on the size of the model and the number of components involved, often taking several minutes.
After the import process is finished, reports are created within the aforementioned conversion report folder. These reports provide information about the overall success and performance of the conversion, along with a list of any components that may not have been successfully converted.
The figure below shows an example of the generated reports.
. These reports can be shared to OPAL-RT to help debug any issues because they contain detailed information about warnings and errors that occurred during the import of the model.
The reports are as follows:
hs_error.log:details on the state of connection to HyWorks
hs_import.log: warnings and errors related to the addition, connection, rotation of components and setting of parameters while creating the model
netlist.xlsx: An excel file containing all the components imported in the model with their parameters
{model_name}_full.log: groups information found in mapper and parser logs
{model_name}_mapper.log: skipped or unsupported components while mapping to Unified Database components are found in this report
{model_name}_parser.log: information on the parsing of the input file
{model_name}_modelexporter.log: details on the generation of the python code used to import the model, can be used for debugging purposes
{model_name}.edd: generated edd file used to import the model to HYPERSIM
{model_name}.py: generated python code used to import the model to HYPERSIM