I just moved from sea level to 1200ft of elevation and it looks like EGO is pulling fuel pretty consistently now. I found the barometric correction setting under "General Settings" and dropped my lower limit to cover any elevation in the area but didn't see a tunable correction map or anything. Is there a correction map I can adjust to pull fuel at elevation? Any idea what it's called or where to find it? Sorry for the dumb question, I've never had to mess with it before and not sure exactly what I'm looking for, I just know whatever it's called doesn't seem to be tuned properly right now.

2000 Miata
MS3X
Reading 96.6 kpa ambient


***Edit*** Found the barometric correction table. I was using MSDroid and I don't think it's on their app. It looks like my barometric correction table is all zeroed out. If anyone wants to share a map I could start from rather than going into it blind I'd appreciate it. If not, I'll take a stab at it and see how things go.

 

You sure you didn't see a fuel blend change? On a FI speed density setup, the baro correction is more of a VE modifier for the exhaust back pressure than it is for the ambient inlet pressure. Obviously it can be used for that if desirable.

 

Mine is zeroed out but still does things. I think the table is to modify the standard baro correction formula.
I posted some info on my findings here:
https://www.miataturbo.net/megasquir...5/#post1410463
Note this is with two map sensors installed.
I often cover 2 to 4kft of elevation change and haven't needed to tinker with the baro table.

 

Yeah, we had the car transported here with a full tank of gas so fuel hasn't changed. I know I'm not at crazy elevation or anything, but I'm pretty sure that's what the difference is.

 

FW version?

 

Looks like: MS3 1.4.0

 

I looked at a log from last week at sea level and "barocor" was 99%, today's log at 1200ft elevation was at 101%, so it was actually adding fuel at ambient 96kpa vs 101kpa. I adjusted the barometric correction table to pull some fuel and it was at 97% barometric correction and seemed a lot better. I'm going to keep playing with it and maybe look into adding a 2nd map sensor. Thanks the help.