Pages: [1] 2
Author Topic: Issue with boost request  (Read 14066 times)
em.Euro.R18
Full Member
***

Karma: +4/-5
Offline Offline

Posts: 219


« on: February 01, 2014, 11:51:12 AM »




Seem to be having trouble with request boost. At peak I'm requesting 15.1psi which is 2060mb actual is around 13psi. Timing curve I'll have to work on smoothing there is no timing pull. Engine load looks about right for this boost pressure and I'm not exceedingor even close to  LDRXN, also since I am not experiencing knock LDRXNZK shouldn't be a factor if I'm not mistaken. I figured 185% in IRL would net at least 17psi. IRL isn't maxed out and I don't notice any intervention taking place. Kind of stumped
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #1 on: February 01, 2014, 01:06:47 PM »

KFTARX
Logged

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 experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
em.Euro.R18
Full Member
***

Karma: +4/-5
Offline Offline

Posts: 219


« Reply #2 on: February 01, 2014, 10:42:59 PM »

I figured with the iats werent hitting 50*+c in the winter months so I left everything stock from 60ish and up. Feels like your right I set all multipliers to 1 and I believe that did the trick but still need to make logs.
Logged
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709


« Reply #3 on: February 02, 2014, 11:36:16 AM »

Forget target boost, figure out why actual isn't meeting target.
Logged
em.Euro.R18
Full Member
***

Karma: +4/-5
Offline Offline

Posts: 219


« Reply #4 on: February 03, 2014, 08:27:21 AM »

I'm right with ya Phila_dot. No reason why actual shouldn't be hitting target. Figuring either a decent leak in the charge side or possible tear in the DV . I already informed project owner to look into pressure testing. I figured someone here would pick up on that.  Tongue
Logged
em.Euro.R18
Full Member
***

Karma: +4/-5
Offline Offline

Posts: 219


« Reply #5 on: February 03, 2014, 09:13:09 PM »





From what I've read so far setting KFTARX to 1 (and when you do this I assume this is simply a multiplier for boost request) which should have corrected the issue... Could this have something to do with specified load passing spec. corrected?
Logged
em.Euro.R18
Full Member
***

Karma: +4/-5
Offline Offline

Posts: 219


« Reply #6 on: February 06, 2014, 10:56:59 AM »

I spotted KFTARX wasn't setup with the correct resolution so I corrected that hopefully that will fix the issue. I've come across threads on here where some users have flattened LDIATA but I'm not sure if I have to do that in this case. LDIATA is a correction factor for load regulation but I'm not sure what the values are. Possibly % correction in the n75 duty? So I assume set it to 0 or at least lower the values.

But my first step will be KFTARX again
Logged
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709


« Reply #7 on: February 06, 2014, 11:29:36 AM »

rlmax_w is not the issue as it isn't limiting rlmx_w.

Did you log rlsol_w?

Did you touch any of the boost pid?
Logged
em.Euro.R18
Full Member
***

Karma: +4/-5
Offline Offline

Posts: 219


« Reply #8 on: February 06, 2014, 11:57:19 AM »

I havn't been able to figure out the me7logger yet so I'm not 100% sure I'm logging the correct engine load block in vagcom. I assumed engine load (specified) would be rlsol_w.

I didn't touch any other map in boost PID besides increasing the limiter in IMX. I also maxed HBN at 3.98
« Last Edit: February 06, 2014, 01:34:46 PM by em.Euro.R18 » Logged
em.Euro.R18
Full Member
***

Karma: +4/-5
Offline Offline

Posts: 219


« Reply #9 on: February 11, 2014, 01:54:36 PM »

I've finally got the hang of the data logger so I'll check rlsol_w next still hitting some sort of limit with plsol. Last logs show from 2040mb to 1980mb peak request.
« Last Edit: February 11, 2014, 06:51:01 PM by em.Euro.R18 » Logged
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709


« Reply #10 on: February 11, 2014, 07:54:18 PM »

I havn't been able to figure out the me7logger yet so I'm not 100% sure I'm logging the correct engine load block in vagcom. I assumed engine load (specified) would be rlsol_w.

I didn't touch any other map in boost PID besides increasing the limiter in IMX. I also maxed HBN at 3.98

rlsol_w is desired load, specified load is rlmx_w.

You increased what IMX limiter and why?

You have zero PID response despite underboosting and holding at least one full psi below setpoint.
Logged
em.Euro.R18
Full Member
***

Karma: +4/-5
Offline Offline

Posts: 219


« Reply #11 on: February 12, 2014, 08:50:06 AM »

KFLDIMX I raised because its defined as integral control limits for charge pressure regulation. My interpretation of that is that it limits the duty cycle of the n75. I'll try reverting back to stock if thats not recommended.
Logged
nyet
Administrator
Hero Member
*****

Karma: +608/-168
Offline Offline

Posts: 12271


WWW
« Reply #12 on: February 12, 2014, 11:36:56 AM »

You'll generally never need to raise it, only lower it.. and when you have to adjust it, it will be obvious
Logged

ME7.1 tuning guide
ECUx Plot
ME7Sum checksum
Trim heatmap tool

Please 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
em.Euro.R18
Full Member
***

Karma: +4/-5
Offline Offline

Posts: 219


« Reply #13 on: February 13, 2014, 12:36:15 PM »

Heres the last log I took with rlsol, 168-172 request's I've seen. Request still hovers around 2030 - 1980mb with IMX back to stock.
Logged
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709


« Reply #14 on: February 13, 2014, 01:40:10 PM »

You will get more comments if you post graphs
Logged
Pages: [1] 2
  Print  
 
Jump to:  

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