Hello, do you have the update code for IEEE 33-bus
They seem to follow the expected location from the relative path in the DSS scripts, i.e., https://data.openei.org/s3_viewer?bucket=oedi-data-lake&prefix=SMART-DS%2Fv0.9%2F2016%2FFull_Texas%2Fprofiles%2F from your sample. You probably can get more info from the repo at https://github.com/openEDI/documentation/blob/main/SMART-DS/Readme.md (it's unlikely the authors subscribe to this forum).
I am trying to use a network for Texas that is defined in OpenDSS. The network is available at https://data.openei.org/s3_viewer?bucket=oedi-data-lake&prefix=SMART-DS%2Fv0.9%2F. Inside the loadshape.dss, it needs some files that are defined by file=../../../../../profiles/res_kw_4691_pu.csv. Could you please where at this aws address, I can find this csv files? All the files for load data at https://data.openei.org/s3_viewer?bucket=oedi-data-lake&prefix=SMART-DS%2Fv0.9%2F2016%2FFull_Texas%2Fload_data%2F&limit=50...
Adding unified interface for DLL generation in C++. This version is also compatible with MacOS, extending the compilation capabilities. Currently the DLL has been tested for compilation in Windows, Linux and MacOS.
Adding unified interface to the DLL as alternative for exposing the code as infrastructure.
Thank you all for the valuable feedbacks and instructions On Fri, Sep 4, 2026 at 8:31 AM Meisam Ansari ansri273@users.sourceforge.net wrote: There are many utilities and consulting companies that have started leveraging OpenDSS in some of their batch analysis where conventional enterprise tools like CYME, Synergi, Windmill, etc do not easily support them. The gap is that the models must first be converted from the current tools to OpenDSS and thoroughly validated. An advanced power system engineer...
There are many utilities and consulting companies that have started leveraging OpenDSS in some of their batch analysis where conventional enterprise tools like CYME, Synergi, Windmill, etc do not easily support them. The gap is that the models must first be converted from the current tools to OpenDSS and thoroughly validated. An advanced power system engineer who has worked with OpenDSS and has coding skills can most likely write a small pipeline and try to do it. However, many engineers do not have...
There are many utilities and consulting companies that have started leveraging OpenDSS in some of their batch analysis where conventional enterprise tools like CYME, Synergi, Windmill, etc do not easily support them. The gap is that the models must first be converted from the current tools to OpenDSS and thoroughly validated. An advanced power system engineer who has worked with OpenDSS and has coding skills can most likely write a small pipeline and try to do it. However, many engineers do not have...
Thank you so much for the help, it really cleared up my doubt. Sorry for the delayed reply here on the forum. I really appreciate the suggested material as well, and I'll be sure to come back to the forum if anything else comes up. Thanks again!
Hello, Thanks for sharing this. My initial thought is that this could be a useful opportunity in the right context. Traversing the circuit model and retrieving element properties can already be done quite efficiently today, either through the circuit tree or by using the incidence and Laplacian matrices that DSS already generates. With those structures in place, the kinds of actions you described above should be fairly straightforward. They also help avoid creating unnecessary duplicates. I would...
Hi Davis, It would be great to have a feedback regarding this. Thank you, Ayodhya On Thu, Aug 20, 2026 at 10:34 PM Ayodhya Dameesha ayodhyadameesha@users.sourceforge.net wrote: The current model is developing a knowledge graph representation of an OpenDSS distribution network model. The long term aim is to develop a semantic knowledge graph for OpenDSS distribution systems that integrates electrical topology, equipment properties, simulation results, and analytical relationships. On Thu, Aug 20,...
The current model is developing a knowledge graph representation of an OpenDSS distribution network model. The long term aim is to develop a semantic knowledge graph for OpenDSS distribution systems that integrates electrical topology, equipment properties, simulation results, and analytical relationships. On Thu, Aug 20, 2026 at 5:59 PM Davis Montenegro davismont@users.sourceforge.net wrote: Hello, Thanks for sharing this, it helps me understand the direction you’re taking. From what you described,...
Hi, There are plenty of resources available, including this forum, and folks here are always happy to help. Typically, we use this space to work through specific questions about the software, like “How do I do this?” or “Why isn’t this working the way I expect?” Do you have a particular application or use case in mind? Best,
Hello, Thanks for sharing this, it helps me understand the direction you’re taking. From what you described, it sounds like you’re trying to combine an ontology layer with a DSS‑based knowledge graph, is that right? If so, I’m curious how this approach differs from simply exporting the circuit’s CIM dataset from DSS and then loading it into a knowledge graph using Python tools like rdflib. Is that essentially what you’re doing now, or is your workflow meaningfully different? Best,
Thank you what do you feel about the chatbot and traversing based solution? On Wed, Aug 19, 2026 at 10:55 PM Meisam Ansari ansri273@users.sourceforge.net wrote: I suggest trying https://opengridharbor.com/ . This is a free powerful tool with nearly interprise capabilities that you can visualize your opendss model and interact with that. OpenDSS Visualizer https://sourceforge.net/p/electricdss/discussion/861976/thread/09c60028f4/?limit=25#2428 Sent from sourceforge.net because you indicated interest...
Hello Everyone! I am new with this tool and would love to learn it. I looked at the user manual and also some youtube videos but I would love to learn from someone to actually use it. Context: I to understand real world simulation of adding generating facility and energy storage to the grid. From a capacity headroom to what will happen to the gird if we do this and that. I will appreciate it greatly!
I suggest trying https://opengridharbor.com/ . This is a free powerful tool with nearly interprise capabilities that you can visualize your opendss model and interact with that.
Hi Davis, Thank you for your reply. Yes my purpose of this is to make a better visualize representation. Also as this is a graph based approach we can traverse through the graphs and find solutions. Also we can create chatbots and ml developments based on this presentation. The dataset was IEE dataset and they are txt files. I want to know is it be worthful if I continue the development and build a python library for this. Also Im open for other feedbacks as well. Thank you, Ayodhya
Hi, Thanks for sharing. This is an interesting representation, but I was wondering what is the purpose of it. Is it to display dependiencies? Connectivity? Relationship? Was this derived from an XML/RDF dataset? Best,
Hi Sergio, Sorry for the delay in getting back to you, things have been quite busy on my end. I took a closer look at your setup, and there are a few key features worth keeping in mind: When an IBR is running in grid‑following mode, it should avoid providing any grounding source to the grid. For that reason, GFL‑mode devices are typically connected in delta. In practical deployments, vendors often include a switchable grounding reactor so they can disconnect the ground path whenever the IBR is operating...
Hi Sergio, Sorry for the delay in getting back to you, things have been quite busy on my end. I took a closer look at your setup, and there are a few key features worth keeping in mind: When an IBR is running in grid‑following mode, it should avoid providing any grounding source to the grid. For that reason, GFL‑mode devices are typically connected in delta. In practical deployments, vendors often include a switchable grounding reactor so they can disconnect the ground path whenever the IBR is operating...
Hi Sergio, Sorry for the delay in getting back to you, things have been quite busy on my end. I took a closer look at your setup, and there are a few key features worth keeping in mind: When an IBR is running in grid‑following mode, it should avoid providing any grounding source to the grid. For that reason, GFL‑mode devices are typically connected in delta. In practical deployments, vendors often include a switchable grounding reactor so they can disconnect the ground path whenever the IBR is operating...
Im planning to create a graph based visualizer for open dss based on python. Im sharing a sample of it. It would be great to have feedbacks for this concept. Thank you
Adding unified grid simulation example for NCIM
Hi all, I'm an undergraduate student on a scientific-initiation scholarship, adapting the IEEE 13-bus test feeder as my study case: a BESS in Grid-Forming (GFM) mode islanding bus 675 through a switch between buses 692 and 675, in dynamics mode (OpenDSS Desktop 11.0.0.1). The Storage successfully switches into GFM (edit Storage.BESS1 State=Discharging ControlMode=GFM SafeVoltage=0) and, in some configurations, delivers real power for exactly one timestep right after activation — but the very next...
Hi all, I'm an undergraduate student on a scientific-initiation scholarship, adapting the IEEE 13-bus test feeder as my study case: a BESS in Grid-Forming (GFM) mode islanding bus 675 through a switch between buses 692 and 675, in dynamics mode (OpenDSS Desktop 11.0.0.1). The Storage successfully switches into GFM (edit Storage.BESS1 State=Discharging ControlMode=GFM SafeVoltage=0) and, in some configurations, delivers real power for exactly one timestep right after activation — but the very next...
Adding solar PVs to a bus can significantly reduce the short-circuit (SC) current at the bus where the PV is connected, depending on how the fault and PV inverter are modeled. The key reason is that PV systems are usually inverter-based sources, and their fault-current contribution is much more limited than that of a conventional synchronous generator or the utility grid. For a short circuit at the connected bus: The grid normally supplies a large fault current. The PV inverter detects the abnormal...
Hey Joe, This usually happens when the irradiance loadshape isn’t properly linked to the PVSystem or the duty/daily mode isn’t set correctly. Snapshot works because it uses the current value, but daily sims need the loadshape to be assigned with the right interval and mode. If you’re testing a few different profile setups and need a quick way to pick the next one, a simple ruleta aleatoria can help keep it moving.
Hey Joe, This usually happens when the irradiance loadshape isn’t properly linked to the PVSystem or the duty/daily mode isn’t set correctly. Snapshot works because it uses the current value, but daily sims need the loadshape to be assigned with the right interval and mode
InvControl: fix crashes and init bugs with disabled/Storage DERs
Hi Joe, It sounds like you’re trying to use FaultStudy mode for this, but unfortunately that won’t give you the results you’re looking for. As explained here (https://opendss.epri.com/FaultStudyMode1.html), the fault analysis only accounts for injections from sources and generators. A PCE like a PVSystem is brought into the model as a negative Y‑primitive, which is why you’re seeing the values being reported. A better approach is to explicitly add a fault and run the simulation in snapshot mode....
Hi Joe, It sounds like you’re trying to use FaultStudy mode for this, but unfortunately that won’t give you the results you’re looking for. As explained here (https://opendss.epri.com/FaultStudyMode1.html), the fault analysis only accounts for injections from sources and generators. A PCE like a PVSystem is brought into the model as a negative Y‑primitive, which is why you’re seeing the values being reported. A better approach is to explicitly add a fault and run the simulation in snapshot mode....
Hello, This was quite a query, but I think I have the answers you need: Considering the differences in fault currents for almost every buses in "ALL-Node Fault Currents" in text1, the 3-Phase fault is modeled as an unsymmetrical fault. Is my understanding correct? I would check the fault study mode notes in which Roger back in the day explained the differences between a regular snapshot simulation and fault study. https://opendss.epri.com/FaultStudyMode1.html . Given the workflow explained at this...
Refining Storage voltage ride-through momentary cessation mode to reflect idling losses (C++).
Refining Storage voltage ride-through momentary cessation mode to reflect idling losses.
cleaning up
Adding example for illustrating the operation of the voltage ride-through capabilities and compliance with IEEE 1547.
Migrating interpolation, voltage ride-through capabilities for IBR (PV and BESS) and cleaning up the code.
Adding voltage ride-through for IBR including Storage. Documentation updated and operational states refined.
I need some guidance on Short Ciruit study in OpenDSS. I am a bit new to short circuit study so I would appreciate your patience in reading my long post. First, I went through the online manual and a few posts in the forum and tried it myself. I took the IEEE 13 bus circuit and just added a few lines at the end to get some exports. // ... // Existing IEEE 13 bus code // Solve // Added these below the Solve command Solve mode=FaultStudy Show Fault export FaultStudy fault.csv export SeqZ seqz.csv I...
I need some guidance on Short Ciruit study in OpenDSS. I am a bit new to short circuit study so I would appreciate your patience in reading my long post. First, I went through the online manual and a few posts in the forum and tried it myself. I took the IEEE 13 bus circuit and just added a few lines at the end to get some exports. // ... // Existing IEEE 13 bus code // Solve // Added these below the Solve command Solve mode=FaultStudy Show Fault export FaultStudy fault.csv export SeqZ seqz.csv I...
Seems like the rated current (set at irrad=1) approx is subtracting from the fault current as when I set the PV 10 times bigger around 10 times more SC reduction.
Hi, hoping someone can help on this. Adding solar PV to a network is causing the SC at some buses (mode=fault study) to drop by 40% (multi MW solar PV connected there). I had expected it to be around the same or increased slightly. This isn't a protection reach issue as I'm talking about the fault at the bus itself where the PV is connected. Is the fault current from solar PV (1.1-1.5pu) not adding to the network fault current there?
It's a large circuit with ~250km of MV circuits and ~300 trafos with loads and PV (~5-25kWp) on them all as well as ~25MV connected PV (100's kWp to multiple MWp). There are 3 feeders in the circuit. Not sure what you want to see as it is across 7 or 8 files. As I say a small circuit works fine for me. It behaves like this in DSS & DSSG
It's a large circuit with ~250km of MV circuits and ~300 trafos with loads and PV (~5-25kWp) on them all as well as ~24 MV connected PV (100's kWp to multiple MWp). There are 3 feeders in the circuit. Not sure what you want to see as it is across 7 or 8 files. As I say a small circuit works fine for me. It behaves like this in DSS & DSSG
It's a large circuit with ~250km of MV circuits and ~300 trafos with loads and PV (~5-25kWp) on them all as well as ~24 MV connected PV (100'skWp to multiple MWp). There are 3 feeders in the circuit. Not sure what you want to see as it is across 7 or 8 files. As I say a small circuit works fine for me. It behaves like this in DSS & DSSG
In my circuit I have some PV installations. They output correctly in snapshot mode. When I do daily sims the voltage & current at feeder header are constant. If I change the irradiance loadshape to constant (all 1s) the simulation works fine and I can see voltages and currents varying for the daily varying load. Why is a non-constant irradiance profile for PV causing this behaviour? I'm using the irradiance profile as a pu output (i.e. between 0 and about 0.85 at highest) and irrad=1 for this.
In the master file after creating new circuit, then OH/UG circuits, trafos, loads and PVs, I calcvoltbases, import bus co-ords and then solve, place energy meters & monitors solve again then run daily simulation with solve mode=daily. (Note, my version is 11.0.0.1)
Sorry that should have been irrad=1 in my first post and not Pmpp! (now corrected above)
In my circuit 33kV I have some PV installations. They output correctly in snapshot mode. When I do daily sims the voltage & current at feeder header are constant. If I change the irradiance loadshape to constant (all 1s) the simulation works fine and I can see voltages and currents varying for the daily varying load. Why is a non-constant irradiance profile for PV causing this behaviour? I'm using the irradiance profile as a pu output (i.e. between 0 and about 0.85 at highest) and irrad=1 for th...
****************** SOLVED! ******************** Thanks @wsunderm1 for looking into this for me. These type of problems have a habit of sticking with you even when you've gone to bed! I had an idea last night that an EARLY declaration of these load and PV profiles might solve the problem. I was leaving them until I redirected to the loads and PV files which had them at the top of them and these were last to be declared in the circuit definition. Instead I moved those loadshape declarations (moving...
****************** SOLVED! ******************** Thanks @wsunderm1 for looking into this for me. These type of problems have a habit of sticking with you even when you've gone to bed! I had an idea last night that an EARLY declaration of these load and PV profiles might solve the problem. I was leaving them until I redirected to the loads and PV files which had them at the top of them and these were last to be declared in the circuit definition. Instead I moved those loadshape declarations (moving...
****************** SOLVED! ******************** Thanks @wsunderm1 for looking into this for me. These type of problems have a habit of sticking with you even when you've gone to bed! I had an idea last night that an EARLY declaration of these load and PV profiles might solve the problem. I was leaving them until I redirected to the loads and PV files which had them at the top of them and these were last to be declared in the circuit definition. Instead I moved those loadshape declarations (moving...
******** [Solved] ********* Thanks @wsunderm1 for looking into this for me. These type of problems have a habit of sticking with you even when you've gone to bed! I had an idea last night that an EARLY declaration of these load and PV profiles might solve the problem. I was leaving them until I redirected to the loads and PV files which had them at the top of them and these were last to be declared in the circuit definition. Instead I moved those loadshape declarations (moving the PV one to first...
I don't see anything that jumps out. I think I would have defined the energymeters and the monitors before opening that line, but the way you have it I think should still work. I tried a simple example circuit and calling solve mode=daily directly results in it running 24 hours, so no issue there. Are the UAT energymeter and monitor upstream or downstream of the line that you open? You might also check the isolated elements (Show->Isolated) and make sure that all of the downstream devices are still...
This was what I originally was using in master file after creating circuit, 3* vsources for 3 feeders, and then circuits, trafos, loads and PVs. Setting number hour etc was only me tryingto debug the problem. (Note, my version is 11.0.0.1) After loading circuit there's this below: set voltagebases=[33,0.4] calcvoltagebases // Last input file to read into the network model Buscoords Buscoords_TBS.dss open line.cp7_1::cp17 ! Need to ensure the line to UAT feeder is open solve // *** Energy meters required...
Before sending it privately (I'm just another OpenDSS user), can you share just the solve "loop"... Like how you do the set mode, setting the number and the stepsize and then the solve calls. Maybe something will jump out. If there are any other script statements that you have in the solve loop (like changing the status of anything else like a line), please include those. Hopefully just this portion of the script will be enough to maybe see what the issue is. I'll try to recreate it on my end in...
I can share the full model but would need to send it privately.
Sorry that should have been irrad=1 in my first post and not Pmpp!
It's a large circuit with ~250km of 33kV (mainly OH) and ~300 trafos with loads and PV (~5-25kWp) on them all as well as ~24 MV connected PV (150-3500kWp). There are 3 feeders in it. Not sure what you want to see as it is across 7 or 8 files. As I say a small circuit works fine for me. It behaves like this in DSS & DSSG
I should add when I use set hour=xx and set number=1 and manually change the hour and cycle through it that way I get the voltage varying. However, if I leave it at number=1 and stepsize=1hr and keep repeating the solve command (set mode=daily established) it remains at the 0 hr voltage. It has to be cleared and run from that hour first. This only happens when the irrad profile is anything other than all 1's. I've tried it on another smaller circuit and it works fine. My circuit has >800 buses.
Can you share a sample script here on the forum, that shows this? I just ran a daily simulation, PV only, with varying pu irradiance (0 to 1) and see large changes in the output. The Pmpp for this is 1000 (kW) and the kVA is 1200. The %Pmpp is 100 and irradiance=1. This was for a 13.8kV system. I was using the latest OpenDSS.exe (64-bit, distrib folder) from sourceforge in the source code repository under the Version8 folder structure. The version for the OpenDSS executable is: 11.0.1.1 One thing...
In my circuit 33kV I have some PV installations. They output correctly in snapshot mode. When I do daily sims the voltage & current at feeder header are constant. If I change the irradiance loadshape to constant (all 1s) the simulation works fine and I can see voltages and currents varying for the daily varying load. Why is a non-constant irradiance profile for PV causing this behaviour? I'm using the irradiance profile as a pu output (i.e. between 0 and about 0.85 at highest) and Pmpp=1 for thi...
bringing back default CMake presets (release).
Adding recent export result fix to C++
Hi Sam, It looks like the export feature relies on a @result variable that isn’t actually being populated anywhere in the software. From what I can tell, the original idea was to use that variable to store the text results too, but that part never got implemented. I’ve gone ahead and added it to the code so everything behaves consistently. You can download the updated executable here: https://sourceforge.net/p/electricdss/code/HEAD/tree/trunk/Version8/Distrib/x64/OpenDSS.exe Replace it in your local...
Updating user manual for including IBR voltage ride-through compatibility.
Adding executable for testing. 6/26/2026
MergingIBR and PVSystem compatibility with voltage ride-through curves for compliance with IEEE 1547. Fixing issue with result variable not assigned. This variable was declared somewhere in the past but never used, adding an inconsistency with export commands.
Thank you so much Davis for your reply again. This command generates all elements powers. I tried" Export Result", it exports Null. I would like to export that one element shown in Results in a csv or text file, is there any way to do this?
Hi Sam, Yes, check on the Export options: https://opendss.epri.com/Export.html Try for instance: Export ElemPowers This will export a CSV file containing the powers for all the elements in the circuit model. There are different export options, pick the one that fits your needs. Best,
Hi Davis, Thank you for your response. Is it possible to get these outputs in a text or excel file?
Hi Fayezeh, Sorry about my earlier reply, I think I brushed past the problem too quickly. What you’re doing is actually pretty interesting, because the whole idea is to capture time‑domain behavior using frequency‑domain sweeps. And I do think there’s a path to make that work, as usual. In the example I attached, the approach is to shift the system’s base frequency and then stitch the per‑frequency results together at the end, which is essentially how harmonic analysis operates. If that tweak isn’t...
Many thanks. Yes, I am already using OpenDSS harmonic mode. My question is more specific: I am modeling a four-wire LV line with a 4×4 Rmatrix and Xmatrix, but I do not have conductor geometry data, so I cannot use LineGeometry. I want to approximate frequency dependence as follows: resistance increases with harmonic order to represent skin effect inductance is assumed approximately constant My question is: can RCurve be applied directly to a Rmatrix or Xmatrix model? From the documentation, it looks...
Hello. I am doing harmonic studies that i need to apply skin effects in my lines, i am using Four-Wire LV Network Modeling (by using 4*4 Rmatrix and Xmatrix). I dont have access to line data (conductor size , GMR, conductor spacing / geometry), so i cant use LineGeometry. So i think the only option is using Reactor. But i dont know how correctly apply it. Based on some simplification, i only want to introduce "conductor resistance that corrected for skin effect and reactance was scaled linearly with...
Many thanks for the quick feedback Davis.
Hi Sam, I put together a simple example for you to try out (attached). If you run it using the standalone executable, just make sure to check the Results tab as shown in the screenshot. You’ll see the outputs listed as P and Q for each phase (P1, Q1, P2, Q2, P3, Q3). Best,
Fix in ShowResults.cpp to match how pascal real-to-string conversion deals with printing of -0.0 as "0.0".
Bugfix in Recloser.cpp. Added missing ".c_str()" to prevent printing of garbage in evetnt log.
Porting changes from Relay.pas and DRelay.pas to Relay.cpp and OpenDSSCDLL.cpp, from commit 4116. Repeating commit message (partially) here for reference:
Cleanup porting of Recloser.pas to Recloser.cpp after features added in version Delphi 11.0.0.1 (Commits 4114 and 4112).
Recloser.pas and Relay.pas: fixed bug where ShowEventLog set to false was silently turning 1-phase lockouts into a 3-phase lockouts. Ported fix to Recloser.cpp - pending porting for Relay.cpp. Also, in Relay.pas, moved debug trace logging to be conditional on DebugTrace to match Recloser.pas.
Bugfix in InitPropertyValues for SwtControl.cpp. Indexing issue and missed Reset property.
Bugfixes in SwtControl.pas, Recloser.pas, Relay.pas and their C++ equivalents:
Bug on setter for generator speed variable. Missed div by 2*pi.
Hi OpenDSS Team, As suggested in the forum for one element output. I used commands below in interface: select pvsystem.XYZ; powers; However, I do not know how to see results of this. You have mentioned to do conversion in interface. I am not sure what kind of command I can use for this. Would you please guide in this matter. I also want to see the results of these two commands in standalone, is this possible? I also have looked into these two links: https://sourceforge.net/p/electricdss/discussion/beginners/thread/c1ae7d30ea/?limit=25#e2fd/59dc...