If you are trying to log your wideband through your AC pressure signal, you'll not be able to simply create a function string and expect it to work. Now you have to create a user math parameter. It can be done here:



Like this(pay no attention to the 7.14, it's my offset for my ethanol mix):

 

Nice info, thanks for that.

How's the new 3.0 VCM suite? I haven't updated yet but i was reading the release notes the other day and it seems decent.

 

It's nice. Having the ability to edit my VVE on my E37 is awesome. They are bragging about how much faster and more high res the scanner is. I'd say it is much more powerful. I just went on a 3 minute run, floored it once, and my laptop battery died.

 

Thanks for the info jesse. have you tried playing with the map/rpm boundaries?

 

Yes. I already have a feel for them. I've noticed that the coefficients seem to edit each zone independently of each other, so they will never be smooth or perfect. But I have a theory about changing the zones. If you have a really stubborn rpm/map area that doesn't change because it is on a boundary line or stubborn or some crap(which I have definitely had), you can change the zone boundaries and it will no longer have that problem.

Another theory: It also allows you to modify VE for higher MAP values, especially under boost. For example, stock the VE considers everything over 86kPa as zones 5, 11, 17, 23, and 29. This means anything over 86kPa are in the same group, which if you're pushing 250 or 300kPa is a huge zone. If you wanted to, you could change the MAP zones to, say, 120kPa and above. You know, make the zones less huge. You could do the same for RPM zones if you're pushing way higher RPM than the stock tune.

 

so would you say that making the upper zones smaller would give more accurate fueling? because when you make the table 2 bar, the last zones are huge and im thinking that would make it somewhat inaccurate. still kindof unsure about the point of them tho. care to share a pic of your ve table?

 

I'd say it's more making things easier to deal with on your end. You should be able to edit most of it without it being inaccurate. In my experience it's just the values near boundary lines that just don't want to change.

 

i also dont really get how the vvt is integrated into the VE. I understand why they would do it that way, but does that mean i have to tune per cam angle? seems like a huge pita, i know you dont have vvt but i do.

 

From what I experimented with, you should only have to change the base table and the car will compensate the cam angle stuff on its own. As a test I changed the base table to 600 across the board then watched the 3d model as I changed the cam angles. They didn't jump to the stock numbers so that's what I'm basing my assumption on.

 

Thats good to hear. Thanks for the info.

 

Thanks for the info.