If interested, this may be helpful: https://poweragent.seas.harvard.edu/ Best,
Hello, Thanks for sharing the model, I couldn't help noticing several features in the model you shared: The loads are commented out, for which there is no demand The base frequency is set to 50 Hz at the beginning of the script Master.dss (see "set defaultbasefrequency=50"). I simulated under these conditions and the voltages all across the model are equal to 1pu (see attachment). It will not change event if you go on a daily simulation. Besides, the loads have assigned a "yearly" loadshape in the...
Hello, I’m afraid it’s tough to pin down the cause without taking a closer look at the model itself. There are several reasons why voltages might show up above the upper ANSI limits, and the specifics really depend on how the system is set up. If you’re able to share the model or walk me through your configuration, that would make it much easier to understand what’s going on. In the meantime, here are a couple of quick checks that often help uncover the issue: Verify the system frequency is set correctly...
Hello, The error you’re seeing suggests there’s an issue with the protocol being used, so I’m curious which one your setup is relying on. Just as a reminder, the OpenDSS‑G TCP/IP interface uses a proprietary ASCII protocol, and the client side has to implement that protocol exactly as described in the user manual (see the TCP/IP protocol section). Have you already implemented that on your PLC client, or is it connecting in a different way? OpenDSS‑G version 7 is available at the link below if you’d...
Hello, Your issue is coming from the WindGen generator. I noticed you tried setting QMode=2, but that parameter only works when you’re using the model’s built‑in volt‑var control. Since that mode isn’t active in your case, forcing it ends up breaking the simulation. The good news is you don’t need to replace any of your DSS files. The latest DSS release (version 11) already includes the fix for the issue that was identified last year. So as long as you’re running the current version, you’re covered....
BTW, I fogot to mention that your loads have no kV property declared, which breaks the simulation. Pleas especify the kV value for the loads accordingly. Best,
Hello, Regarding your questions: Why does the EventLog show no dispatch actions even when the monitored power at Line.L1 is clearly above 3100 kW? -- The EventLog requires a global flag to be enabled to allow controllers to store their logs, for this, need to add the following command after the first "Clear" command: set EventLogDefault = Yes Is the ElementList syntax (Bat1, Bat2, Bat3, Bat4) correct for multi-unit control, or should I define individual controllers? -- The Syntax is correct. No need...
Thanks Alex, It’s pretty incredible how much can change in just a couple of years. Large language models are everywhere now, and I’m seeing more and more OpenDSS users experimenting with AI assistants built specifically to work with the tool. Some of these efforts are even coming from industry groups that want to push power‑system simulation tools like DSS forward. What’s interesting is that the industry seems to be taking the lead naturally—using DSS as the simulation backbone while layering modern...