PSCAD Addition · Issue #98 · modelscript/modelscript · GitHub
Skip to content

PSCAD Addition #98

Open
Open

Description

@gkhalley

PSCAD is arguably the most used software for EMT studies for electric utilities in the United States. EMT studies are required by NERC for generation from inverter based resources (IBR) such as a utility scale solar farm, wind generators, or batteries. It will also be required to place high impact large loads (HILL) such as datacenters on the grid.

Incorporate PSCAD into the tool.

ERCOT, real-time operator (RTO) in Texas, is on the cutting edge of constructing new IBR for HILL. They have established PMView (https://sites.google.com/view/pmview/home) as a model quality tests for new IBR. While they have tried to automate the process, it still requires significant setup and understanding.

The real challenge is helping utilities, stakeholders in each RTO, understand and reliable test each black-box PSCAD dll provided by vendors. They must also verify plant models that they have built with field data. In spite of AI taking over, utilities are resistant to closed processes that come from AI. Being able to use "best of class" tools to show how things work is the best approach.

Activity

  1. gkhalley commented on Oct 14, 2026

    @gkhalley
    Author

    Another tool that competes with PSCAD, not currying the favor of the United States, is EMTP software. It is the commercial version of https://www.atp-emtp.org/ . The separation of the code was long ago. This might also be helpful: https://github.com/NatLabRockies/ParaEMT_public . I'm not a user of either.

  2. gkhalley commented on Oct 16, 2026

    @gkhalley
    Author

    What workflow is being replaced with Modelscript? Modeling falls into two classes: certified and best-in-class. A certified model is what you submit to the authority having jurisdiction. As you know PSCAD fits that. Best-in-class broadens the understanding and makes the engineer more confident.

    This is the role of Modelscript for EMT and it should quickly ascertain the data is complete and reasonable. This is typically done by running the analysis and checking the results. Modelscript seems ideal for checking the results. If they are incomplete or not reasonable, then engineers (not PhDs or mathematicians) like to have tools that look at them from a real-world physical way like comparing MOD-026 (https://www.nerc.com/globalassets/standards/reliability-standards/mod/mod-026-1.pdf) testing where you set PID parameters and look at step-change results.

    Separate note: I have determined a way to create an FMI from the DLL I have.

  3. nachawati commented on Oct 21, 2026

    @nachawati
    Member

    I’ve implemented an initial prototype of a web-native .pscx schematic editor paired with a basic electromagnetic transient (EMT) simulation engine that exports results to both COMTRADE and PSCAD .out formats. While it still requires significant UI polish and rigorous numerical validation, the core goal is ambitious: bridging circuit-level EMT simulation with SysML v2 regulatory requirement modeling and formal verification via ModelScript.

    Two architectural questions I’m currently navigating:

    1. PSCAD Master Library dependencies: What is the best strategy for handling unresolved references when users load circuits dependent on the proprietary master library?

    2. Open benchmark suite: Is there precedent or best practice for publishing an open benchmark and validation suite of representative .pscx test circuits alongside reference output curves?

    Image
  4. gkhalley commented on Oct 22, 2026

    @gkhalley
    Author

    Fantastic progress! Seeing the web-native schematic editor generating .out and COMTRADE runs directly is huge.

    A few thoughts on your two questions:

    Master Library Dependencies: An open Modelica-based equivalent library is the cleanest path forward. Implementing core passive EMT primitives (transformers, lines, loads) where parameter names and topologies map directly to PSCAD's standard definitions lets users run standard cases without touching proprietary .flx files. For unmapped blocks, falling back to a stub/black-box component with exposed ports is usually necessary until mapped. I’m discussing the parameter matching and component definitions with colleagues to see what we can standardize here.

    Benchmark Precedent: For open suites, the most established precedents are the CIGRE benchmark systems (e.g., CIGRE B4 or the European MV distribution benchmark) and IEEE distribution/transmission test feeders adapted for EMT (like the 9-bus or 14-bus systems), along with open NREL/EPRI IBR models. Publishing these with canonical COMTRADE reference waveforms generated from verified PSCAD runs provides a solid baseline for automated regression.

    The SysML v2 integration will help pin down requirements systematically. I'll test workflows internally against existing benchmarks to uncover edge cases and work on outlining a practical roadmap over the next couple of weeks. Excellent work!

    Open-access generic IBR EMT models from EPRI and NREL are hosted primarily across their public research repositories and GitHub organizations:

    EPRI Generic EMT Models (GitHub): Available under the EPRI development organization on GitHub at epri-dev. Key repositories include open-source generic EMT models for grid-following resources, such as the Generic-Type-IV-Wind-EMT-Model-for-Grid-Following and OpenDER for DER/IBR interconnection requirements. EPRI also provides research reports and generic model documentation via the main EPRI Website.

    NREL Grid-Forming & Inverter Models (GitHub & Research): NREL distributes open-source IBR simulation toolsets and PSCAD automation scripts through their primary GitHub organization at NREL (including utilities like PyPSCAD) and through the multi-lab UNIFI Consortium (Universal Interoperability for Grid-Forming Inverters) specifications and benchmark cases hosted via the UNIFI Consortium Website.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions