-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Model iPSL.Electrical.Loads.PSSE.BaseClasses #25
Comments
@petitrenaudseb The last sentence I do not understand at all. What would the user choose and why would you think our model parameters are hard coded? If you think about the lines where it says a(re=1,im=0) and b(re=0,im=1) those are just starting parameters. |
Let me try to explain my point of view. The easier is the second one. For the first point, i understand what is a and b. My question is that if you set S_p, S_i and S_y it's enough to deduce a and b. |
@petitrenaudseb Ok, now I understand. Regarding the first point, which was originally second, yes, they are hardcoded. PSSE has a certain way of scaling the load depending on the voltage below the threshold value. To my knowledge, my predecessors were not able to find the exact way of describing this function of load vs. voltage. The a0,a1 and a2 came from the curve fitting experiments in Matlab. I should also mention that there are two ways in which this behaviour was modelled and it can be selected via "characteristic" parameter. For the exact functions you can check the code. Regarding the S_p,i and y, I can say that this is done in the same way in PSSE. During the power flow, you can set the constant power, current or shunt and any combination of those three. Then, when you convert the load, constant power can be assigned to constant current or shunt with parameters a and b. So, what you set with S_i and S_y in parameters might not be the same as what you get after conversion with a and b. Check the code and parameters S_P, S_I and S_Y (notice the capital letters). |
About hardcoded parameters, you explanation is ok for me. Regarding the load combination, i try to understand (thanks to your explanation), how to use this model. That's why i ask the previous question: In the example i found in the IPSL, it works because a(re=1,im=0), b(re=0, im=1) and S_i and S_y is equal to zero |
See the screenshot - Pload and Qload are S_p, IPload and IQload are S_i and YPload and YQload are S_y in Modelica. The screenshot is from the Network Data->Load Let's say that you do a load flow which results in Pload = x, Qload = y, IPload = x1, IQload = y1, and YPload = x2 and YQload =y3. The end result after conversion with a and b will be as follows: My point here is, after the power flow you might not have only constant power load! (which is strange to me). Before dynamic simulation you can shift constant power load between the other two as you wish. I hope this explains it. |
it's clear that you might not have only constant power load during dynamic simulation. Thanks for you example, i understand what you mean ! before closing this interesting discussion, when you look at the equations described in the model, parameters S_P, S_Y, and S_I are never used. I think this is a mistake (?) |
You're welcome. Nope. What you're looking at is the base class which is then extended by the models above (Load and Load_variation). So, I'm now closing this issue. :) |
i'm still investigating why, when i use this model, i'm not on steady state, and i think i found something. Let me know if you agree. |
@tinrabuzin @petitrenaudseb which is the status of this issue? |
I still do not agree with the psse base load model, one correction i made in my local library is the following: |
I disagree. You can have a look at the section 7.2.2. of PAGV1 of PSSE. And I consider this issue closed. |
@tinrabuzin |
@tinrabuzin @AIAitesla |
OK. We will do this. Thanks |
I have some questions/ doubt about the input of this model.
If you look at this model, one can fix the following parameters:
constant power load
constant shunt admittance load
constant current load
a and b : load transfert fraction for shunt/current load
If you look at PSSE inputs, a and b are not accessible and are deduced from load description.
Moreover, this model does not take care of the input the user choose : use of hard coded parameters
The text was updated successfully, but these errors were encountered: