NefMoto

On my M Box logs my ActualBoost is almost identical to my desired boost.
But PS_w seems to follow the break boost.
Any idea what would cause this?
Logs being taken with me7logger

ps_w is not boost, ps_w is modeled intake pressure...
If you want it to match your boost pressure you need to recalibrate your intake model. It is derived from the HFM5 signal, not from the MAP sensor.
However, I would not bother. Just make sure it does not hit 2550mbar. If you look at the FR, then rlroh_w gets converted to ps_w and then back to rl_w. If you peg ps_w you also peg rl_w, which is a bad thing, since you will run lean.

Hmmmm but isn't ActualBoost supposed to show you what the MAP sensor is seeing?

pvdkds_w != ps_w

Exactly.

Actual boost is pvdkds_w and it is from the MAP sensor.
ps_w is an internally calculated pressure value from the MAF sensor for the intake model...

For the boost tuning look at pvdkds_w vs. plsol_w

This should help explain my question.
This shows pvdkds_w vs. plsol_w.
They are both near identical.
This is a rough tune on my single turbo s4

(http://i1357.photobucket.com/albums/q755/britishturbo/20015AudiS48D0907551M0261207143_template_20121229_000752_zps25a430ec.png)

Is it the reason for ps_w being much lower than boost that you are confused about?

No no. The true boost is only 10psi.
N75 isn't hooked up yet.
Its showing ActualBoost much higher.

But... I just got a CEL. For MAP sensor.
So in guessing with no map it uses Expected Boost ?

Need to look at FR exactly how the signal is substituted if your MAP sensor is disconnected. I am sure you can manage ;)
You should have started with saying that your car is in limp mode and MAP sensor is off.

Was not really clear what you wanted to say. Sorry.

The MAP sensor is hooked up and in place lol :-p
I guess it just has a problem.

(http://i1357.photobucket.com/albums/q755/britishturbo/Screenshot_2012-12-29-16-28-06_zps32732f08.png)

You shouldn't be attempting to tune anything with all of those faults. Once repaired everything will change, negating all the progress you make now.

Agreed. ONLY tune a *100%* known good setup. Make that 110%

Otherwise you are just wasting your time.

The faults literally just came up.
The only one that really means anything is the MAP sensor.
The vss isn't plugged in that's why there's a code for that.
The first code is just because evap is unplugged.
The o2 codes aren't real. They are reading just fine from the wideband.

:-)

The computer thinks they're real (the o2 sensor codes), real enough to put your car into limp. Same with the VSS.

I'm hooking the vss up tomorrow - I just got the car on the road last weekend and didn't realize it wasn't plugged back in.
The CEL wasn't on during the tuning runs I did the last couple of days, just came on today. So I'll look into the O2 sensor codes.

Car for sure wasn't in limp during tuning runs to dial in the MAF

I know you're saying it wasn't in limp, but there is a difference between Soft limp vs hard limp-unless you're accustomed to driving the car, you might not be aware it's even happening. All I'm saying is in order to properly dial something in you should be certain everything is working together. You wouldn't try to tune a guitar that's missing a string would you?

I love your project,and the direction it's heading. Keep up the good work.

Ha! I love the guitar analogy. I play guitar lol.

Point taken. I'm really more doing shake down runs than fine tuning right now anyway. Tomorrow I'll be working in n my exhaust and tracking down the bugs :-)

So I still can't get my MAP sensor to work.
I've tried 2 different S4 sensors and even a generic Motorola 4250 sensor hooked up and I get the same issue.
After a few starts I get a check engine light for the MAP sensor, and the logs show the desired boost to be the same as actual.
I have checked the harness, I have continuity to the ECU on the output (pin 4) and I have 5V between pin 1 and 3.
Bad ECU maybe? About the only thing I have left to try!

The only other thing I see is that using VAGCOM looking at measuring block 115 I see what looks like values for ActualBoost. Is this just a simulated number or is this supposed to show the sensor reading?
If it's showing sensor reading why would the logs from me7logger and the CEL both say there is a problem?

Hmmmm. Help or ideas appreciated!
Thanks.

Stupid question: you do know there is a MAP limit, right?

lol yes!
Using someones awesome me7logger app I get identical values for both actual and requested everywhere . Which is what. I understand the ecu will do with no map signal.

Disconnected MAP == FFFF

I read an audi document that says it will use an assumed value in that case though. Hmmmm.
I just want my map to work haha

Maybe you are just that good  ;D

Your codes aren't open circuit anyway. I have never seen or heard of requested and actual being the exact same. I can check the code for those DTC's and see the cause and reaction at some point.

Can you log and or graph just requested vs actual please.  I am kinda color blind.

Haha I would appreciate it!

I will do that later for you.

this is a very strange issue FWIW, i have never seen it, especially after replacing the map sensor.

in block 115 of vag-com you should be able to see requested vs actual.  maybe try that to ensure something isnt up with your logging apps as vag-com is kinda like old faithful.

I did that today but just sitting still. Not under load. I'll try that tomorrow. 
But I have map sensor CELs...

Here ya go:

(http://i1357.photobucket.com/albums/q755/britishturbo/boost_zpsf1eeb0ff.png)

And the data:

(http://i1357.photobucket.com/albums/q755/britishturbo/boost-log_zps0c4e2b1c.png)

Wow that is strange.

Can you post your ME7L def/ecu/cfg files?

See, I'm not totally crazy haha :-P

Here ya go!

start selling tunes, you got that shit nailed down perfect... :P

One of the strangest things i have seen so far with these ecus, i am stumped.

Hahahaha :-P

youll have to find somebody to give you the location to udsl_w (map voltage) i guess

also log pvdksf_w and pvdkmx_w?

I'm betting you are looking at PVDKMX...

Hmmmm well everything says it's pvdksf_w that I'm looking at doesn't it?
I also logged pvdksf and it shows the same thing as well.

Any idea where udsl_w is?

Checked CELs - same codes.
Cleared codes.
Flashed new tune
Fired up vagcom:

(http://i1357.photobucket.com/albums/q755/britishturbo/IMG_20130106_131410_141_zps93caff53.jpg)


Started car:

(http://i1357.photobucket.com/albums/q755/britishturbo/IMG_20130106_131640_641_zps7fa89e40.jpg)

Hmmmmm lol

Where is your map line hooked to?

Post throttle body. Where the F-hose would be. You don't think its all because of that do you?

LOL

Hint: Look where the MAP is from factory...

I knew it as soon as I saw the idle reading vs the KOEO reading.

Ha I know. I didn't expect it not to work at all haha v

Hopefully all is well when that's fixed.

You know I never expected the ecu to freak out over vacuum lmao.
Makes total sense now. I'll have to move it when I get back from Canada.

So I located the MAP sensor to the intercooler piping Pre Throttle Body:

(http://i1357.photobucket.com/albums/q755/britishturbo/IMG_20130111_141555_763_zps48378412.jpg)

And here is the result!

(http://i1357.photobucket.com/albums/q755/britishturbo/boost_zps11aa82ae.png)

Yay! It works correctly now!
Car runs a lot better too, the on throttle hesitation is gone :-)
Thanks for all the feedback guys!

N75 hooked up.

(http://i1357.photobucket.com/albums/q755/britishturbo/boost-spike_zps8418e48f.png)