|
nyet
|
 |
« Reply #120 on: July 03, 2014, 03:35:31 PM »
|
|
|
However, I'm not sure what you mean that I should not be moving. There is boost error present so I needs to be moving to correct it.
Just saying that if DRL is calibrated correctly, a constant boost req should not require the PID to do anything (or much)... pre->post lin correction should be sufficient to (mostly) maintain boost, and lde should remain near zero. |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
|
phila_dot
|
|
« Reply #121 on: July 03, 2014, 05:04:18 PM »
|
|
|
Just saying that if DRL is calibrated correctly, a constant boost req should not require the PID to do anything (or much)... pre->post lin correction should be sufficient to (mostly) maintain boost, and lde should remain near zero.
Conpletely accurate, but that's also assuming P, I, and D are doing their job. I should still track back to the setpoint in steady state if it needs to. I get what you're saying though that I shouldn't have to do much after it accumulates. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #122 on: July 03, 2014, 05:21:17 PM »
|
|
|
Conpletely accurate, but that's also assuming P, I, and D are doing their job. I should still track back to the setpoint in steady state if it needs to.
Yep. But remember, P is out of the gain schedule if lde is anywhere remotely near zero. And D should be basically zero, since nothing should be moving if req boost is steady and DRL is calibrated correctly. |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
|
phila_dot
|
|
« Reply #123 on: July 03, 2014, 05:54:40 PM »
|
|
|
Yep. But remember, P is out of the gain schedule if lde is anywhere remotely near zero. And D should be basically zero, since nothing should be moving if req boost is steady and DRL is calibrated correctly.
Did you mean D is zero in steady state and P is near zero based on current error? |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #124 on: July 03, 2014, 10:13:47 PM »
|
|
|
Did you mean D is zero in steady state and P is near zero based on current error?
Yes and yes. And when P is near zero, it is out of the gain sched.. |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
Basano
Full Member
Karma: +90/-3
 Offline
Posts: 192
|
|
« Reply #125 on: July 04, 2014, 12:47:27 AM »
|
|
|
Hi! Interesting comments, borne out by what I saw in the logs. D is zero in the steady state. I increased KFLDRL and logged again this morning. A bit surprised by the result... As far as I can make out, the post-linearization duty cycle remains the same, but less pre-linearization duty cycle is needed to achieve this. And the boost curve stays the same. It's like the actual boost is has reached some other set point and the PID is maintaining it. Love to hear what you make of this   There are two plot's overlaid in the chart, before and after the KFLDRL changes. Purple line is pre-lin duty cycle (ldtvr_w) Green line is post-lin duty cycle (ldtvm or ldtv_w, they are the same in value) Red line is specified boost Blue line is actual boost |
|
|
|
« Last Edit: July 04, 2014, 12:50:22 AM by Basano »
|
Logged
|
|
|
|
Nottingham
Full Member
Karma: +13/-1
Offline
Posts: 204
|
|
« Reply #126 on: July 04, 2014, 04:43:59 AM »
|
|
|
Could someone help me on the rev & speed limiters on the attached (stock) file?
For some reason changing the NMAX (1C9982h), NMAXGA (1DB368h) and NMAXOGGA (1DB380h) have no effect what so ever.
The engine still cuts at the stock limit (6800rpm). The GA and OGGA tables shouldn't be even altered but I tried that too just to be sure.
Also all of the VMAX related limiters seem to be set either to 255km/h or 511km/h but yet the actual VMAX seems to be limited to around 230km/h.
At that speed the engine starts cutting power.
|
|
|
|
|
Logged
|
|
|
|
|
IamwhoIam
|
|
« Reply #127 on: July 04, 2014, 06:14:12 AM »
|
|
|
You need to open your eyes a bit more for Nmax  it's VERY easy. |
|
|
|
|
Logged
|
I have no logs because I have a boost gauge (makes things easier)
|
|
|
|
nyet
|
|
« Reply #128 on: July 04, 2014, 09:47:04 AM »
|
|
|
As far as I can make out, the post-linearization duty cycle remains the same, but less pre-linearization duty cycle is needed to achieve this. And the boost curve stays the same.
Keep going! Add more DRL until the pre-lin is flat where req boost is flat. Near steady state, the shape of pre-lin should roughly match req boost. I'm guessing you're near the turbo's limit, which means no matter how much DRL you add, you may never see req boost. At that operating point, boost is likely almost unresponsive to DC. |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
Nottingham
Full Member
Karma: +13/-1
Offline
Posts: 204
|
|
« Reply #129 on: July 04, 2014, 12:43:23 PM »
|
|
|
You need to open your eyes a bit more for Nmax it's VERY easy. Forgot to say that I already adjusted NMAXDV and NMAXDZ too, zero effect. Unless the rpm limit set by NMAXTO is active even below the lowest oil temperature I am pretty much out of ideas  There's NMAXDVG too I see. |
|
|
|
|
Logged
|
|
|
|
Basano
Full Member
Karma: +90/-3
Offline
Posts: 192
|
|
« Reply #130 on: July 04, 2014, 01:52:23 PM »
|
|
|
Behold, the masterpiece... Well not quite, but I have an answer! I'm guessing you're near the turbo's limit, which means no matter how much DRL you add, you may never see req boost. At that operating point, boost is likely almost unresponsive to DC.
Spot on. I've just logged one more iteration of KFLDRL where I jump straight to 95%. No half-measures, just 95% output for any input greater than 20% from 5500 rpm upwards. And yes, actual boost still tails off. Why am I so pleased? - because now I understand I've run into a physical limitation of my KO4! I'll work on tidying up KFLDRL  |
|
|
|
« Last Edit: July 04, 2014, 01:55:33 PM by Basano »
|
Logged
|
|
|
|
|
majorahole
|
|
« Reply #131 on: July 04, 2014, 02:10:43 PM »
|
|
|
Forgot to say that I already adjusted NMAXDV and NMAXDZ too, zero effect. Unless the rpm limit set by NMAXTO is active even below the lowest oil temperature I am pretty much out of ideas There's NMAXDVG too I see. could something else be causing the issue? aren't those limiters "without errors"?? I'm just guessing as I haven't even bothered raising those as my engine didn't seem to make anymore power past 6200rpm as it is |
|
|
|
|
Logged
|
|
|
|
Nottingham
Full Member
Karma: +13/-1
Offline
Posts: 204
|
|
« Reply #132 on: July 04, 2014, 02:24:59 PM »
|
|
|
Regarding the VMAX I'm no longer sure what to believe.
ECUSafe shows that one of the several VMAX limiters is set to 225km/h, which is within the range of the actual top speed achieavable.
This 225km/h limiter (7080h) however is defined as NMAXF, which equals 7200rpm with the 0.25 factor. With the factor used for VMAX (1/128, 0.007813) the value
is 225km/h. I assume the same value cannot have two different meanings?
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #133 on: July 04, 2014, 05:42:53 PM »
|
|
|
And yes, actual boost still tails off. Why am I so pleased? - because now I understand I've run into a physical limitation of my KO4!
which probably means you are probably way off the reservation efficiency wise, and likely near the overspin boundary. Consider consulting the K04 compressor map... |
|
|
|
|
Logged
|
ME7.1 tuning guideECUx PlotME7Sum checksumTrim heatmap toolPlease do not ask me for tunes. I'm here to help people make their own. Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your ex
|
|
|
Nottingham
Full Member
Karma: +13/-1
Offline
Posts: 204
|
|
« Reply #134 on: July 05, 2014, 03:29:35 PM »
|
|
|
Regarding the fuelling, please correct me if I am wrong:
The stock injectors on 200hp (e.g. AXX & BWA) engines seem to flow 1027cm³/min @ 110bar based on the KRKATE (34.25 / 0.03333).
When I swapped the S3 injectors I used the flow difference of 13% stated by APR as a ballpark value.
Based on the logs I made the actual difference in the flow is pretty exactly 15%. With KRKATE scaled down by 13% the LTFT has settled to -2%.
However if I raise the fuel pressure for example from 110bar to 120bar the KRKATE needs to be scaled again?
(1027 * 1.15) * ((120/110) SQRT) = ~ 1233cm³/min <> (34.25 / 1233) = 0.02777ms (KRKATE)
|
|
|
|
|
Logged
|
|
|
|
|
