Pages: 1 ... 15 16 [17]
Author Topic: Actual pre-control in LDRPID  (Read 37976 times)
SB_GLI
Hero Member
*****

Karma: +84/-7
Offline Offline

Posts: 1011


« Reply #240 on: February 12, 2019, 07:35:22 AM »

What will happen if I log fixed 90 or 95% duty only until lets say 3500rpm. Will the tool use this logfile because there is WOT from start to 3500?
Or in general: should i log this 90% with a K03/K04 because it will overspool and get damaged maybe.

In PRJs first post there is 90% in the last column of KFLDIMX and 95% in the last column of KFLDRL.
I understand that you will have to set 95% in KFLDRL because of spoolup and for the absolut maximum duty.

Why is there 90% duty in the last column of DIMX? Is it because of the logic: the last column (pressure value) is higher than what you are planning to run so it doesnt matter if its 90 or 95?



Using this method, DIMX is merely a conversion of the DC axis in KFLDRL to pressure.  For example, if you have a 80% column in DIMX, and the value is 1,700, that means that the 80% column KFLDRL can be translated 1,700.  If you are requesting 1,700 mbar, the values in the 80 column will be used as the final DC.
Logged
aef
Hero Member
*****

Karma: +42/-15
Offline Offline

Posts: 1078


« Reply #241 on: February 12, 2019, 07:51:12 AM »

not sure if i understand you with my limited english
lets say i would like to see 1600@3500 tapering to 1100@7000

i will have to set last column of dimx to 1800 with 95% because you have to cover the whole boost range in the dimx according to this some posts before
2) KFLDIMX pssol high axis point should be above maximum achievable boost (not max desired boost).  This is done to ensure full range is covered (last row of KFLDRL table values is all 95).  LDRXN/KFLDHBN may limit boost below this level, but can be ignored here.

so why is prj only using 90@1000 in the first post of this thread?

Logged
SB_GLI
Hero Member
*****

Karma: +84/-7
Offline Offline

Posts: 1011


« Reply #242 on: February 12, 2019, 11:27:13 AM »

Quote from: aef
not sure if i understand you with my limited english
lets say i would like to see 1600@3500 tapering to 1100@7000

i will have to set last column of dimx to 1800 with 95% because you have to cover the whole boost
range in the dimx according to this some posts before

You need to make sure that your highest DIMX column has values > 1600.  If you use 1,800 in a 90 column, for instance, that means that the values somewhere in between the 80 and 95 column of DRL will be used to specify the final duty cycle when requested pressure is 1,800.

Quote from: aef
so why is prj only using 90@1000 in the first post of this thread?

Because it was not real data, only an example?


Logged
aef
Hero Member
*****

Karma: +42/-15
Offline Offline

Posts: 1078


« Reply #243 on: February 12, 2019, 04:12:25 PM »

What is the range filter for? I dont understand it with just the words given.

I did logs with 5120hack but forgot to change some pvd* values in the ecu (multiply by two) so i renamed the columns to force the tool to use pvdkds_w.
My pu_w and pvdkds_w are multiplied by two during logging.

But I wonder why the tool does read these numbers. I mean if I compare the last row from tool (90) with the logged pvdkds minus pu. Isn't this the cell value in the tool 1:1?

If you have a look into the log you will find 2095-995=1100mbar boost @ 3000 but in the tool its red (interpolated and 600mbar higher)

I changed the min filter to 1900 and the red values in the export is a bit smaller.

Does throttle cut affect the log? I got this in the 90% log Sad
Think i will have to log the 90% again with higher ldrxn wo have actual boost near reqboost, correct?

« Last Edit: February 12, 2019, 04:27:11 PM by aef » Logged
aef
Hero Member
*****

Karma: +42/-15
Offline Offline

Posts: 1078


« Reply #244 on: February 13, 2019, 04:23:13 PM »

I finally got it

what do you think?

last question: what is the range filter for?
Logged
aef
Hero Member
*****

Karma: +42/-15
Offline Offline

Posts: 1078


« Reply #245 on: Yesterday at 12:49:55 AM »

The program filters based on throttle plate angle (wdkba) or accel pedal angle (wped|wped_w).  It uses throttle plate angle, if it exists, otherwise accel pedal, which has to be > 90% for a sample to be included.  a sample must be above min rpm param (default 2500) to be included.

From there it uses the spool filter to remove samples to the left of an "x" second window where the boost increase is > "y" amount.

I have an update to post, but forum file storage is stuffed.  It extrapolates upward which makes it easier to use when approaching MAP limit.

hmm not sure if i understand this.
why do i have 7 interpolated values in my 2000rpm row?
Logged
SB_GLI
Hero Member
*****

Karma: +84/-7
Offline Offline

Posts: 1011


« Reply #246 on: Yesterday at 11:50:58 AM »

My only suggestion is to generate KFLDRL that has all 95's in the last column.   Max WGDC will otherwise be limited and you'll spool slower.
Logged
Pages: 1 ... 15 16 [17]
  Print  
 
Jump to:  

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