Yeah and it's normal for some BOV like synapse to be opened at idle (that's why they need to be recirculated for proper air measurement in MAF tune)

 

So maf tune at idle does not need to be sealed critically, domyz, as log as its recirculating?

 

At rest there is constant release of excess pressure. At slow increase same, quick stab slight decrease but not enough to collapse the bag which is a reflection of time to shut the bov after manifold gets some pressure.

 

It release pressure at idle? Am I missing something ... because you're supposed to be at vacuum/negative pressure at idle.

 

I've studied this in and out for my anti lag thread. Uicp is positively charged at idle.

 

On decel

 

Yeah I mixed up things , UICP is + at idle and throttle plate is close (vacuum in intake manifold). So BOV pressure signal is negative and BOV air pipe is +.
So there is some air getting out of BOV, I'd advice people to recirculate in MAF with a BOV opened at idle, or get another BOV.

 

What I'm wondering is if it leaks at idle during maf , is that going to be a problem? When trying to calculate ve?

 

Not really because you'll still end up tweaking SD maps at the end. It give a rough start idea, but need ajustement when switching back to SD.

 

Alrighty.. I'm gonna try maf later today and see how I do.

 

Wow, glad you showed me this. I was always under the impression that the upper intercooler pipe was still under a slight vacuum at idle. I remember a couple honda's I messed with back in the day were sucking air at idle so I just assumed the same here. Good to know tho.

 

Glad we had a discussion -and not an argument . I was going to use a condom instead of that mini zip loc though haha

I think the dtt method is worth mentioning in the op though..

 

To make the popup disappear you need to change the root cause: The value someone linked in the equation for VE is lowercase "l" but the Load1byte in EvoScan is "L". I changed my EvoScan equation settings for VE to follow suit(check your Load1byte log reference if you aren't sure).

 

Hey guys, I need a little help. I think I've got something set up incorrectly. I'm converting my MAF tune to SD using 88592715 rom. I've logged VE and built my VE map on the SD rom. Cruising seems ok. But under boost I'm reading Load values way over what I did on the MAF tune. My VE map is very close to what I was reading on the MAF tune so not sure why the load can be that far off. I have map2kpa and kpa2load both at 1:1. I'm using the omni4bar, is there something I need to set up on the SD side for the omni?

 

There is map sensor scaling if you right click edit table is that set for the right sensor?