Davis Montenegro

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...

Hello, I think I need to understand your setup a bit better, because the issue you’re running into sounds more conceptual than technical. When you’re working within an OpenDSS session, whether it’s running locally or in the cloud, you don’t need to recompile the model every time you run a power flow. Once the session is up, the model stays in memory as long as that OpenDSS host process is alive. That’s why it sounds to me like you might be spinning up a Lambda function for each run, or maybe using...

Hello, I think I need to understand your setup a bit better, because the issue you’re running into sounds more conceptual than technical. When you’re working within an OpenDSS session, whether it’s running locally or in the cloud, you don’t need to recompile the model every time you run a power flow. Once the session is up, the model stays in memory as long as that OpenDSS host process is alive. That’s why it sounds to me like you might be spinning up a Lambda function for each run, or maybe using...

Oh yes, that is common. Instead of clicking on the file, click in the button at the top that says "Download Snapshot", this will download the file for you within a zip file. Please let me know how it goes. Best,

Hello, The documentation is distributed normally as a CHM file, you can download it here: https://sourceforge.net/p/electricdss/code/HEAD/tree/trunk/Version8/Distrib/Doc/OpenDSS%20Documentation.chm However, this is a Windows native format, but there are options if you want to read it in other OS like Linux: https://www.baeldung.com/linux/compiled-html-help-files . Please give it a try in the meantime. Best,