Pages: 1 ... 11 12 [13] 14 15 ... 22
Author Topic: Actual pre-control in LDRPID  (Read 250411 times)
6L20vt
Full Member
***

Karma: +2/-0
Offline Offline

Posts: 152


« Reply #180 on: February 26, 2018, 12:33:34 PM »

Do you think that would be correct?
Logged
6L20vt
Full Member
***

Karma: +2/-0
Offline Offline

Posts: 152


« Reply #181 on: February 26, 2018, 12:45:06 PM »

sorry this is the image
Logged
SB_GLI
Hero Member
*****

Karma: +116/-10
Offline Offline

Posts: 1022


« Reply #182 on: February 26, 2018, 04:46:26 PM »

Any change to flatten the request out more where actual begins to meet requested is what you need.   That means, either increase request around 2,500 or decrease request around 3k, whatever works best for you.  You have this gigantic cliff of a request and that isn't helping.  If you didn't have that, even if imx wasn't 100% on the money, it's close, and the difference would trim out after a pull or two.

Another thing to consider is that you might not have great data at 2,000 - 2,500 rpm which could be a contributing factor.

All in all, your calibration is really close, so I'd feel good about what you have so far if I were you.  Smiley
Logged
contrast
Full Member
***

Karma: +20/-3
Offline Offline

Posts: 215


« Reply #183 on: February 27, 2018, 11:36:15 PM »

I would like to comment quickly by saying that setting up KFLDIMX and its axes along with proper set of logs has worked perfect for any turbo setup. Be it big and laggy or super quick spool. I haven’t had the need to touch any of the PID maps so far.

I do have a recommendation that yielded even greater results on fast spooling turbos. I did a set of 0-90 duty cycle logs in third gear from 1500 rpm to redline. This produced a map that I saved in WinOLS. Then I did the same logs in fifth/sixth gear from 1000 to about 3500 rpm. I then merged the two resulting maps together. This gave me data for zones that I access only during overtaking on highway for example etc. No overshoot/undershoot, actual boost follows target on point.
Logged
6L20vt
Full Member
***

Karma: +2/-0
Offline Offline

Posts: 152


« Reply #184 on: February 27, 2018, 11:44:15 PM »

I would like to comment quickly by saying that setting up KFLDIMX and its axes along with proper set of logs has worked perfect for any turbo setup. Be it big and laggy or super quick spool. I haven’t had the need to touch any of the PID maps so far.

I do have a recommendation that yielded even greater results on fast spooling turbos. I did a set of 0-90 duty cycle logs in third gear from 1500 rpm to redline. This produced a map that I saved in WinOLS. Then I did the same logs in fifth/sixth gear from 1000 to about 3500 rpm. I then merged the two resulting maps together. This gave me data for zones that I access only during overtaking on highway for example etc. No overshoot/undershoot, actual boost follows target on point.

Thank you very much for your contribution, I will make more logs as soon as I can.
Logged
6L20vt
Full Member
***

Karma: +2/-0
Offline Offline

Posts: 152


« Reply #185 on: March 01, 2018, 02:41:54 PM »

well after some tests and changes, I used the filter of the tool to try to make the spool softer, and I have achieved this

I have managed to reverse the situation, now it does not reach the demand, I think it is a matter of trying until it gets closer, and then making minor adjustments in other points.
Logged
SB_GLI
Hero Member
*****

Karma: +116/-10
Offline Offline

Posts: 1022


« Reply #186 on: March 17, 2018, 12:36:46 PM »

What did you have in KFLDRL?  Do you intend on only running 1.1 bar max?  KFLDIMX should be configured so the lowest value is less than base boost, and highest value is greater than max boost you intend to run.  Make the values linear in between.
« Last Edit: March 17, 2018, 12:58:05 PM by SB_GLI » Logged
SB_GLI
Hero Member
*****

Karma: +116/-10
Offline Offline

Posts: 1022


« Reply #187 on: March 21, 2018, 08:15:12 AM »

Should I use the KFLDIMX axis values your tool suggests me (and log again of course... Undecided)?
0 - 400 - 800 - 1200 - 1400 - 1600 - 1800 - 2000

No, you should do what I said a couple of posts up.  Make an KFLDIMX that covers your desired boost range, and make it linear.   This should be an easy concept to understand.
Logged
SB_GLI
Hero Member
*****

Karma: +116/-10
Offline Offline

Posts: 1022


« Reply #188 on: March 21, 2018, 04:03:27 PM »

Thanks, did it, logged again, applied calculated kfldrl and boost runs pretty good, I can definately feel a difference.

SB_GLI, I love you <3  Grin Grin #nohomo

Attaboy
Logged
sonflasch
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 68


« Reply #189 on: April 27, 2018, 02:09:50 AM »

on 1.8t it works great ...

could one include the consideration for plgrus_w for 2.7t?

or can someone tell me how I can use the tool for it.

unfortunately I can not do an asm hack.

Many Thanks



Gesendet von meinem SM-G930F mit Tapatalk

Logged
sonflasch
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 68


« Reply #190 on: April 27, 2018, 05:51:54 AM »

you could use CWLDIMX to input without the plgrus_w on IMX.
then use the measurements drive with fixed ldtvm ... tool.
but without plgrus_w or drive with CWLDIMX brings problems in the amount.
I do not know if that works for RS4 at all, I'm on the job
Logged
sonflasch
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 68


« Reply #191 on: May 09, 2018, 09:25:02 AM »

Hello @all

the input plgrus_w in pu_w I have changed with success-> check on the tabel witch ols300 ( plsol over Applikation).
I would rather leave plgrus_w original. I want to make it switchable,better for emulator ride.

my idea
when switching by CWLDIMX to 1, pu_w should be switched -> on picture marked.
how can I turn 0.0 to pu_w?
not a fixed value but RAM_pu_w
I'm not that good at the ASM hack yet, but I'm trying to learn

would then share my successes
Many thanks

https://ibb.co/iTLPJn
https://ibb.co/gn4UjS


Logged
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6034


« Reply #192 on: May 11, 2018, 02:31:10 AM »

You don't need plgrus_w original, because it's a nightmare to calibrate.
If you are not using original logic in it for boost control, then just make plgrus_w = pu_w, and change the actuator spring maps to reflect it.
Much easier to tune aftermarket, and not worse in any way - in fact done many times like this from factory.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
sonflasch
Full Member
***

Karma: +12/-2
Offline Offline

Posts: 68


« Reply #193 on: June 01, 2018, 10:45:12 PM »

You don't need plgrus_w original, because it's a nightmare to calibrate.
If you are not using original logic in it for boost control, then just make plgrus_w = pu_w, and change the actuator spring maps to reflect it.
Much easier to tune aftermarket, and not worse in any way - in fact done many times like this from factory.

on RS4
input without the plgrus_w on IMX (plgrus_w = pu_w)
look from address 07A6A0
« Last Edit: June 25, 2019, 03:04:49 PM by sonflasch » Logged
prj
Hero Member
*****

Karma: +1072/-480
Offline Offline

Posts: 6034


« Reply #194 on: June 02, 2018, 05:02:01 AM »

Not the correct way to do it.
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
Pages: 1 ... 11 12 [13] 14 15 ... 22
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.034 seconds with 17 queries. (Pretty URLs adds 0s, 0q)