Pages: [1] 2
Author Topic: E85 throttle cut :(  (Read 13750 times)
technic
Full Member
***

Karma: +18/-5
Offline Offline

Posts: 227


« on: August 06, 2014, 12:59:58 PM »

Hi guys,

I'm working on E85 conversion of a Skoda 1.8T, but I have run into trouble Undecided
Car now has 4bars FPR, no extra tuning (besides KRKTE, ignition and coldstart maps)

I have 0 misfires, 0 CF (Its E85) and actual boost follows requested quite ok.

The problem is that I have throttle cut. Not much, but I can feel it, and I think it is due to unstable lambda values (too big diff sporadically)

I would be very happy for a few professional opinions Smiley Log attached and some graphs for your viewing pleasure.

Cheers
/Lars

Edit: Spelling
« Last Edit: August 06, 2014, 01:22:45 PM by technic » Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Online Online

Posts: 12270


WWW
« Reply #1 on: August 06, 2014, 01:35:25 PM »

There is NO way you are feeling 100->98.85% throttle cut.

Your problem is your boost request. It's a mess.
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
technic
Full Member
***

Karma: +18/-5
Offline Offline

Posts: 227


« Reply #2 on: August 06, 2014, 03:26:19 PM »

I was a bit sloppy when reading logs - only noticed that trottle was != 100%. Sorry  Embarrassed

Indeed desired boost, actual boost and actual load is a mess.

Could be a bad N75 or WG maybe, but then why does requested load look so weird after 4750?

Based on KFMIRL and LDRXN I would expect 135 load% at 5520 but loadrequest is 118. KFTARX cannot influence as IATs never goes above 45 degrees. And as I said, no misfires or knock.

Any suggestions what to log to narrow this down?
Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Online Online

Posts: 12270


WWW
« Reply #3 on: August 06, 2014, 03:30:10 PM »

Indeed desired boost, actual boost and actual load is a mess.

Uh.. don't bother looking at actual if desired is wrong.

Quote
Could be a bad N75 or WG maybe, but then why does requested load look so weird after 4750?

Exactly.

Recheck all of these:

KFMIRL
LDRXN
KFLDHBN
KFTARX
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
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Online Online

Posts: 12270


WWW
« Reply #4 on: August 06, 2014, 03:33:28 PM »

btw you did not log timing. Perhaps it is knock control intervening?
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
technic
Full Member
***

Karma: +18/-5
Offline Offline

Posts: 227


« Reply #5 on: August 06, 2014, 03:52:27 PM »

Yes, well, I logged fzabg_w_[1-4] and dwkrz_[1-4] earlier (I had problems logging so many variables at the same time in me7_logger).
Zero on all. No misfires or ign. retard.

KFMIRL
KFLDHBN
KFTARX

are all stock.

LDRXN is 135 from 2520 to 5520, 128@6000 (Not enough boost to be limited by KFLDHBN)






Logged
technic
Full Member
***

Karma: +18/-5
Offline Offline

Posts: 227


« Reply #6 on: August 06, 2014, 10:01:13 PM »

I don't get this. Requested load is fine up to 4850, but requested boost fluctuates.

How come the ecu think it needs to request such varying boost to achieve the load (which is quite flat up to that point) Huh
Logged
daniel2345
Full Member
***

Karma: +11/-7
Offline Offline

Posts: 197


« Reply #7 on: August 06, 2014, 10:53:46 PM »

Take yourself a software documentation for an ME7. Floating around everywhere.

Follow the path from rlmax to plsol or pssol and see, what can influence it.

There are agr calculations in between, lambda efficency, base pressure dependancys and other stuff...
Logged
technic
Full Member
***

Karma: +18/-5
Offline Offline

Posts: 227


« Reply #8 on: August 07, 2014, 12:13:32 AM »

I'm well aware of that document Wink I have read LDXXX parts many, many times but not from that aspect I guess. I have actually never seen this behavior before...
But you are of course totally correct, Daniel. I need to follow the path to pssol more rigorously.

Thanks for all hints, both of you.
« Last Edit: August 07, 2014, 01:24:26 AM by technic » Logged
nyet
Administrator
Hero Member
*****

Karma: +607/-168
Online Online

Posts: 12270


WWW
« Reply #9 on: August 07, 2014, 11:15:53 AM »

Good luck :/

I wish I could help more.

Please let us know if you track down the issue.
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
technic
Full Member
***

Karma: +18/-5
Offline Offline

Posts: 227


« Reply #10 on: August 08, 2014, 07:03:38 AM »

Yes, I'll let you know if I solve it, but right now I'm very puzzled.

Don't believe this is a software issue. I'm now running on stock file with KRKTE as _only_ change. LTFT is +/- 2%.  

It is rlsol_w is still a mess after 5000 rpm Sad  Could a vaccuum leak result in rlsol_w going nuts?

pvdkds_w (act boost) follows plsol (req boost) fine, so I ruled out the N75. Unplugged it and boost held steady around 1340mbar (tapered off very slowly after 4200 RPM and ended at 1280mBar@7000). So I don't think it is a boost leak

One clue (maybe) is that I have now started to get the DTC : 17608 Boost Pressure Control Valve (N249): Mechanical Malfunction

Next thing is to log milsol_w, etazwbm and etalab...

The saga continues... All ideas - good or bad - are still welcome Smiley
« Last Edit: August 08, 2014, 07:11:17 AM by technic » Logged
technic
Full Member
***

Karma: +18/-5
Offline Offline

Posts: 227


« Reply #11 on: August 10, 2014, 09:22:57 AM »

I have logged some more. misopl1_w is pulsating after 5000 rpm. misopl1_w is affected by milsol_w, etazwbm and
etalab (none shows up in me7info though  Undecided ) and these three combined is input to KFMIRL.

So, something bad is happening before misopl1_w...
Logged
phila_dot
Hero Member
*****

Karma: +173/-11
Offline Offline

Posts: 1709


« Reply #12 on: August 10, 2014, 09:42:46 AM »

Sounds like slow path torque intervention.

Look into MDKOL
Logged
technic
Full Member
***

Karma: +18/-5
Offline Offline

Posts: 227


« Reply #13 on: August 10, 2014, 10:43:43 AM »

Thanks philia_dot. I logged B_mibeg = 0 and miszul_w = 99.2188 so MDLBEG (in MDKOL) shouldn't be limiting, so something earlier then.
With slow path, do you mean torque control NOT coming from lambda and ign efficiency?

I would like to log everything before MDLBEG but they don't seem to be available (from ME7info)




Logged
technic
Full Member
***

Karma: +18/-5
Offline Offline

Posts: 227


« Reply #14 on: August 11, 2014, 01:32:29 AM »

MAF output doesn't affect misopl1_w, does it?
Logged
Pages: [1] 2
  Print  
 
Jump to:  

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