-
Notifications
You must be signed in to change notification settings - Fork 1
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
Temperature Derating #26
Comments
We currently have three different types of table for temperature derating: "Derate":{"Enable":true,"Mode":0,"TempC":[30,35,40],"AirDensity":[1.225,1.1,1],"DeratedMaxPowerKW":[[3000,3000,2000],[3000,2700,1200],[3000,2400,600]]} "Derate":{"Enable":true,"Mode":1,"TempC":[30,35,40],"Elevation":[1000,1800,2500],"DeratedMaxPowerKW":[[3000,3000,2000],[3000,2700,1200],[3000,2400,600]]} "Derate":{"Enable":true,"Mode":2,"DeratedMaxPowerKW":[3000,2700,2400,2000,600],"Elevation":[1000,1800,2400],"TempC":[[30,37,40,42,45],[30,35,37,40,42],[30,32,35,37,40]]} These tables are not formatted in the standard Octue way. I will try to reformat them like the rest of the schema. Note: All this data is made up and so not subject to NDA. |
OK, took some hand editing but here they are in the same order in Octueish "Derate": {
"Enable": true,
"Mode": 0,
"parameters": [
{
"label": "temperature C",
"dimension": 0,
"points": [30, 35, 40]
},
{
"label": "AirDensity",
"dimension": 1,
"points": [1.225, 1.1, 1]
},
"DeratedMaxPowerKW": [
[
3000000, 3000000, 2000000
],
[
3000000, 2700000, 1200000
],
[
3000000, 2400000, 600000
]
]
}
"Derate": {
"Enable": true,
"Mode": 1,
"parameters": [
{
"label": "temperature C",
"dimension": 0,
"points": [30, 35, 40]
},
{
"label": "Elevation m",
"dimension": 1,
"points": [1000, 1800, 2500]
},
"DeratedMaxPowerKW": [
[
3000000, 3000000, 2000000
],
[
3000000, 2700000, 1200000
],
[
3000000, 2400000, 600000
]
]
}
"Derate": {
"Enable": true,
"Mode": 2,
"parameters": [
{
"label": "DeratedMaxPower"
"dimension": 0,
"points": [3000000, 2700000, 2400000, 2000000, 600000]
},
{
"label": "Elevation"
"dimension": 1,
"points": [1000, 1800, 2400]
},
"temperature C": [
[
30, 37, 40, 42, 45
],
[
30, 35, 37, 40, 42
],
[
30, 32, 35, 37, 40
]
]
} |
To consider:
|
Please do not forget to define transition between temp set points (linear/other) and re-start lags etc. See attachment to first comment in this string of comments. |
@thclark I believe we decided during the last call that we do not need to consider wind speed as part of thermal derating "not-required" (at least for the first edition of the standard) I think it is "essential" to have what Nick laid out but also important "essential" to capture the additional details I added in my draft. |
Update: Kell came back and said don't worry about wind-speed-dependent derating after searching for an example (apparently it was a one-off) |
Captured TODOS from schema drafting session:
|
Please see attached a crude draft of what should be added to the Schema. Redlined edits/suggestions welcome
Draft.Wind.Turbine.Derating_08142023_Rev0.docx
The text was updated successfully, but these errors were encountered: