wsunderm1

By setting it to model=3, that is telling OpenDSS that you have a user-written model (DLL) that computes the load injection. Is that intentional in your study? If so, I would look at the DLL code as a possible source of the issue.

By setting it to model=3, that is telling OpenDSS that you have a user-written model (DLL) that computes the load injection from User-written Model. Is that intentional in your study? If so, I would look at the DLL code as a possible source of the issue.

I had to fix several spacing issues and other errors in your files to get them to run in OpenDSS. Have you modified the IEEE123Master.dss that you are compiling with the first statement? My guess is that there is a missing Clear statement somewhere and when you run the script a second time you are seeing this error of a duplicate PV1 definition. I would place a Clear statement right before the compile statement in your script and see if you still encounter the error. It should look like this in your...

In OpenDSS the script "New circuit.mycircuit" causes a voltage source to be created. The name of the voltage source, by default is "source" with that command. Note that unless otherwise specified, the voltage source created has a number of default values. The help on VSource goes into a lot more detail. Here's an example of a voltage source getting created through the New circuit, where the Thevenin impedances are given in ohms. New Circuit.mycircuit ~ BasekV=34.5 pu=1.0 angle=0.0 ~ Z1=[1.4610, 11.360]...

To add to what Paulo mentioned about decreasing the Thevenin impedance, there is a fairly recent addition to the VSource properties that might help achieve what you are looking for, if you are wanting an ideal voltage source. If you already have a voltage source defined, you can edit it similar to the following in OpenDSS: Edit "Vsource.source" model=ideal

I think we need to see more about the OpenDSS script/circuit (or at least components) that is (are) being defined in the python code. After your python script has defined these items, but before a solve, you might try a dss.Text.Command('Save circuit') and look at the resulting dss files. If you don't see an error there, please post the resulting dss files here for us to view.

If the code snippets are shown in the order that they are executed in python, the shapev and generic XYcurve should be defined before you use them in the Storage and InvControl.

It's hard to say without knowing more about the circuit that the PVSystem with InvControl is 'installed' in and the parameters that you have set. I might suggest, at the end of your simulation code (you appear to be using the COM interface), add the following to cause the OpenDSS COM engine to show the eventlog in a text editor: DSSText.Command='show eventlog'; In the eventlog there should be entries regarding what voltage the InvControl is 'seeing' and the reactive power absorbed or injected based...