Hello, have there a car, 180hp (Seat Leon DE file), with k03s with K04-23 internals, exhaust, intake, 440cc injectors+walbro pump. Stock MAF. Targeting 1.3bar constant then tapering naturaly. KTRKE+tvub+fkkvs modified for new injectors , trims ok, AFR at WOT also(peak 15ms). Around 5500rpm  boost instantly drop from  almost 1.2 to 0.9bar (cca from 180 to 150 load).No knock. No change in specified boost or specified load at situation. VCDS doesnt showing change of WGDC  maxed at these rpm) which is weird. No DTC errors of course.

Tried off torque monitoring and armd (hope correctly).
MLMAX rised (never did before)
Two times rised KFMIRL( over 210 on 100% row)+ acordingly made KFMIOP + even KFMI_UM
Obviosus limiters MAF,pressureratio ect are rised several times also.
Tried different N75, the same, Tried high rpm pull with actuator hose off and no drop.
On stock file runs 0.6-0.5bar constantly to limiter, specified load+boost matched actual.
Tried lower boost to around 1bar(cca 165load), it drops also but little later around 6000rpm.


Sorry, tried to connect ME7logger, but recieved 0x1 init error,  and VCDS logs nobody download(i can send of course).

Is there something different in 150/180 files against 210/225 ?
I never read about this problem, but it must be common on K04ed 150/180hp cars, isnt?

Stop messing with the ECU.

Intake hose is collapsing because filter is shit or the hose is shit.

Another filter did not change issue.  But i play with a car on dyno for several hours. Found with actuator hose off it holds almost the same boost at high rpm as my lowered "no drop" settings, so probably the issue will be in the actuator movement. But with vacuum pump(or pressure) it moves free.

Measured vacuum on factory K03 aluminium intake J pipe, outlet for evap valve, just before compressor wheel(K04 42mm inducer). At 0.8bar in 6000rpm there was -0.25bar ,  when i simulate stronger actuator(added two external springs) turbo holds 1.0bar in 6000rpm then there was -0.35bar. No difference with airfilter on or complete off. And power difference at these rpm was only 5bhp cca, almost negligible still around 200-210bhp mark.  Dissapointing.

If you can point me where i can get enought info, i will be glad. I had usuals 0x4(if i remmeber correctly) and now 0x1 errors. No clean way how to solve it found on this forum. Only random users success, which didnt work for me. I worked ok on my very first ME7.1car, then i did just ME7.5 and no connection at all.
I dont cry, just dont want to be seen as ignorant.

He said it worked ok with his other ME7.1 car, so it is likely a k-line or baud rate issue.

to get visual me7 logger to work you must first download me7logger. Install me7logger and be sure you extract all the me7logger files to a brand new folder. Place the folder in my documents and just to be sure, name it "me7logger" here is the link:

http://nefariousmotorsports.com/forum/index.php/topic,837.0title,.html

Now download the me7logger GUI

http://nefariousmotorsports.com/forum/index.php?topic=1079.0

This is the instructions from the thread:

It is a single executable just unzip and drop it in the root of your ME7Logger directory(the one with the bin, defs, ecus, etc. directories).  Create a shortcut to the exe on your desktop to make it easy to run.

***FIRST TIME USERS OF ME7Logger*** I believe this will make it simpler to use(read the quickstart guide two posts down), but you still need to read the README for ME7Logger to understand how it works and how to edit your config files.  Also this download is just the GUI, you will need ME7Logger as well.

Lastly, Install visualme7logger:

Here is download link. This will instantly start the download.

https://visualme7logger.codeplex.com/downloads/get/1455766

Install instructions:

To run VisualME7Logger:
Copy the VisualME7Logger.exe into the ME7Logger directory before running.
VisualME7Logger requires at minimum .Net 4 framework (4.5 and 4.5.1 also work)
Windows 8: If you receive a "Smart screen" warning upon executing the program, right click on the exe and select Properties.  On the Properties page, click the "Unlock" button to stop these warnings.

Follow all instructions carefully and you should be fine. I received your PM. My cable also has blue obd2 connector with blue light on it as well as silver cord and usb connector. It is likely the same cable. to be sure open nefmoto with your cable plugged into the computer and click refresh at the top. if the device bar says "FTDI FT232RL" then we have same cable and I confirm working. When using vag-com how do you connect in settings? com port? FTDI? if com, what com port? once you have followed all of these instructions you'll need to setup me7logger to use COM and specify your com port. Also, in device manager is serial enumerator checked?

Have you created a .ecu file with your .bin for use in me7logger? The GUI will help with that.

GL ? and lemme know, or any one of the guys if your still in a pickle and could use more help.