I'm working with an h22 turbo setup, bouncing the boost cut because of the stock map sensor. I have a 3 bar map sensor installed and wired in, however the program doesen't want to run it very well.

I clicked the 3 bar setting, set the fuel cut value to 9, and redid the vacuum map scalars to match the 1.75bar settings. Unfortunately though the car does not like to idle unless you have your foot on the throttle, and when you try to rev the car up it just wants to die. Its really acting like there is no map sensor.

The map sensor we have is known to be good as we pulled it off a working car.

Any help appreciated....thanx.

 

I would mess with the scalars too drastically. Also put it at around 8, I think that might work better. I am running a 2.5 bar no problems.

 

1.) Ask Uber questions on Uber site

2.) I wrote a very detailed write on that site

3.) It's still ON THE FIRST PAGE AND THE TITLE IS OBVIOUS "Official how to use and scale 3 bar map sensor" Topic: http://uberdata.pgmfi.org/foru...=3494
and yes it works!!

is adseguy gonna have to choke a bitch!

 

lol

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by adseguy &raquo;</TD></TR><TR><TD CLASS="quote">
is adseguy gonna have to choke a bitch! </TD></TR></TABLE>

maybe...

 

Thanks guys I'll try that....

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by quickchris &raquo;</TD></TR><TR><TD CLASS="quote">Thanks guys I'll try that.... </TD></TR></TABLE>

I'm having the exact same problems as you. How did you finally figure it out?

 

Recheck your wiring. it is 80% a wiring job cuz 3 bar works great in uberdata

 

Wiring doesn't cause that type of problem. I found another thread that basically says that 3 bars suck with UD.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by adseguy &raquo;</TD></TR><TR><TD CLASS="quote">1.) Ask Uber questions on Uber site

2.) I wrote a very detailed write on that site

3.) It's still ON THE FIRST PAGE AND THE TITLE IS OBVIOUS "Official how to use and scale 3 bar map sensor" Topic: http://uberdata.pgmfi.org/foru...=3494
and yes it works!!

is adseguy gonna have to choke a bitch! </TD></TR></TABLE>

i followed this write up when i did mine. it worked well, though i found that i had to mess with my air/fuel ratios a lot, they were like 50% off or something. anyway, it took me about a half hour of playing with in my driveway and around my neighborhood, but i got it running and idling fine

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Enzo Speed &raquo;</TD></TR><TR><TD CLASS="quote">Wiring doesn't cause that type of problem. I found another thread that basically says that 3 bars suck with UD.</TD></TR></TABLE>

WHAT? sure it does. You can turn on a car with no signal since it just shows WOT. I've done it before.

I have personally used and tuned a few cars using 3bar and Uberdata....zero problems using my method

 

Well at any rate, it's 3 measly wires. I didn't screw it up.

I finally got it to idle by subtracting 25% fuel in the idle vac columns.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Enzo Speed &raquo;</TD></TR><TR><TD CLASS="quote">Well at any rate, it's 3 measly wires. I didn't screw it up.

I finally got it to idle by subtracting 25% fuel in the idle vac columns.</TD></TR></TABLE>

Ah yes...the wonders of tuning

 

Oh boy, figured out the biggest problem. I got scammed and somebody sold me a 1 Bar map. Sweet

I ordered a new 3 bar. Hopefully that will help a bit

 

and once again 3-bar works FLAWLESSLY with uberdata

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by boosted k20 &raquo;</TD></TR><TR><TD CLASS="quote">and once again 3-bar works FLAWLESSLY with uberdata</TD></TR></TABLE>

Then why are there a million and one complaints about it? People having to rescale their injectors and redo all the vacuum portions of their maps.

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Enzo Speed &raquo;</TD></TR><TR><TD CLASS="quote">

Then why are there a million and one complaints about it? People having to rescale their injectors and redo all the vacuum portions of their maps.</TD></TR></TABLE>

and.......it works. sucks you got scamed though...Good luck with that

 

I followed adseguy's write-up. everything went peachy. Idle on the GM 3bar is a tad more sensitive than stock map sensor imo but once you get the AFRs and scalars dialed in it's good. so uberdata+gm 3bar = works flawlessly

 

I'm still confused about the scalars. Do you:

A) Set them to what you want? Like can set it to 27 - 21 - 18 - 13 - 8 etc and then the ECU will read from my created scalars?

B) Datalog and see where the engine is idling, then change the scalar to what my vac gauge is reading?

What I want to know is, if I delete all the scalars and put nothing in, would the car still idle in the same vac columns? Do the scalars actually change anything, or are they just titles that should be matched to my boost/vac gauge?

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Enzo Speed &raquo;</TD></TR><TR><TD CLASS="quote">

Then why are there a million and one complaints about it? People having to rescale their injectors and redo all the vacuum portions of their maps.</TD></TR></TABLE>

dont change the 1st and the last map scaler heading.s leave them stock.


and the so called "million and one" complaints u r get n are from lazy people who expect to have a perfect basemap right off the bat. u need to spend a couple of hours tuning the car

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by boosted k20 &raquo;</TD></TR><TR><TD CLASS="quote">

dont change the 1st and the last map scaler heading.s leave them stock.
</TD></TR></TABLE>


But I can make the others whatever I want? How come when I click "write" they change slightly? (i.e. "13" becomes "12.54")

 

You can set them to what you want, just don't touch the first and last one because (I think) that is what is used as the "range" for the ECU and sensor.

On my car I just went about a little under half the columns for vaccum and scaled them evenly then I went about 3-4 PSI spaces for the boost all the way to 18.....then it goes straight to 28 because I knew I wouldn't be using anything above 18PSI

I don't understand why you want to erase all the columns and see where it idles....just create the vac/boost column to how yuo will be boosting and whereever it idles tune those columns......why are you making it hard? Just curious

 

Ah, I'm not making it hard, it's already hard

I didn't know if I could make the columns whatever I wanted. Because with the 3bar option selected, it makes most of the columns vacuum, then leaves you with like 6 columns for boost. I'm going up to 27psi and it jumped 6psi per column which I didn't like.

I guess I'll just jack some of the vac columns and turn them into boost columns. I'd rather have the better tune in boost than in vac.

 

If you are going to 27PSI then I suggest running Crome because of the 24x20 tables...makes tuning MUCH safer IMO because there are no large jumps then, but yeah you can change them to anything you want if you use uberdata like mentioned in the thread...GL

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by Enzo Speed &raquo;</TD></TR><TR><TD CLASS="quote">


But I can make the others whatever I want? How come when I click "write" they change slightly? (i.e. "13" becomes "12.54")
</TD></TR></TABLE>

That because of the calculations getting rounded off. 12.54 isn't far off from 13