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...
Another option would be to install NI LabVIEW in your PC (you can download the community version) and run the source code itself. The code can be downloaded from: https://sourceforge.net/p/dssimpc/code/HEAD/tree/trunk/Source/ You can use any SVN client for that. The instructions for learning how to run the source code locally with a local NI LabVIEW installation are available here: https://sourceforge.net/p/dssimpc/code/HEAD/tree/trunk/Source/README_FIRST.txt Best,
Hi, It’s unfortunate the issue is still happening. At this point, it really might be something local. Have you tried installing it on another computer? If it works fine there, then the problem is definitely on the original machine, and I’m afraid there’s not much I can do on that front. But if the same issue shows up on a different machine, that points to a problem with the installer itself, and I can absolutely dig into that. No one else has reported this so far, which makes me think it’s likely...
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