PDA

View Full Version : EE Hack logging at high elevation question



Hotrodhawk
07-07-2023, 11:58 PM
The text field for "MAP" turns red in color when I'm driving high elevation roads. What's this telling me?

Lt1 ee running closed loop

NomakeWan
07-08-2023, 04:19 AM
Probably that the current MAP value is above the current BARO value.

On $EE, if you're changing elevation significantly (up or down), slap the gas pedal. The computer will update your BARO value using the MAP sensor when the throttle is above 85%. This is because the LT1 only has a MAP sensor and not a separate BARO sensor.

Hotrodhawk
07-08-2023, 03:27 PM
Probably that the current MAP value is above the current BARO value.

On $EE, if you're changing elevation significantly (up or down), slap the gas pedal. The computer will update your BARO value using the MAP sensor when the throttle is above 85%. This is because the LT1 only has a MAP sensor and not a separate BARO sensor.

Thanks, I will take a look at the log file when I get home.
Now that you mention the baro update, I belive I've seen a flag setting for that when looking through all of those.
I'm surprised key off then key on doesn't force a map/baro update.

It's normal for me to go from 4400' elv too above 8000- 9000 feet elevation over a 40 mile canyon run.

steveo
07-08-2023, 06:21 PM
I'm surprised key off then key on doesn't force a map/baro update.

of course it does

eehacks warning thresholds and data ranges are in a csv config file

i put some arbitrary values there that i felt were good enough for average folks.

you can copy it and change the thresholds with your favourite spreadsheet program if you want

Hotrodhawk
07-09-2023, 06:04 PM
of course it does

eehacks warning thresholds and data ranges are in a csv config file

i put some arbitrary values there that i felt were good enough for average folks.

you can copy it and change the thresholds with your favourite spreadsheet program if you want

SteveO
Could you point me towards the name of this warning threshold and I'll take it from there.
Thanks again.
Ps this little 355 LT1 just did a sweet roll race from 40 mph againt a Opitma Ultimate Challange 70 Chevelle with a 540 BBC. Motor to motor on the hit the Firehawk put a car and half on him. He gathered up the half car with his front end stuck to my rear bumper. Talk about converting a BBC owner to exclam; "That SBC is stout"... made my summer so far.

steveo
07-09-2023, 06:53 PM
its wherever you installed eehack, there's a file called 'ee_definition.csv'

it's a csv file, has the following fields. you could just edit it in notepad if you wanted

OFFSET,SHORT_NAME,LONG_NAME,UOM,VIEWLEVEL,SIZE,PRE CISION,MULT,ADD,MINPATCH,MAXPATCH,SPECIAL,WARN_LOW ,WARN_HIGH,RANGE_LOW,RANGE_HIGH

WARN_LOW and WARN_HIGH are probably what you want

copy the file before you edit it, it's not checked very carefully so if you mess the format up eehack will probably just crash

Hotrodhawk
07-21-2023, 07:25 PM
Steveo I got the car out for a drive yesterday and the log showed that when I stomp on it the Baro dose not up date. I had to pull over shut the car off and restart it. Then the Baro updated to the correct elevation I was at.
I'm trying to find what's causing this to no update. I'm using a stock f-body bin and comparing againt my bin and nothing is popping out when I search for any "baro" settings that are diffent than mine.

2844 Barometric Pressure Update RPM states it's a routine that can update the base baro pressure while the engine is running. My bin is set at 3600 the same as a stock ta bin.


Any pointers you can offer?

Hotrodhawk
07-21-2023, 08:13 PM
Is 2844 baro press update rpm mean it updates below the setting or above that rpm?

2841 min tps for baro up-date is set at 38%

2842 min tps difference for baro up date is set "0"

Hotrodhawk
07-21-2023, 08:27 PM
I have more findings steveo or anyone with answers... thx

Hotrodhawk
07-21-2023, 10:10 PM
That is what's happening but stabbing the peddle dose not update the baro in my case. The only way I can get it to update is key off then key on.

Can't belive that gm would require a family loaded up in the old Roadmaster to go wot in mountian terrain....lol

Something is off in my case

NomakeWan
07-21-2023, 10:32 PM
Is 2844 baro press update rpm mean it updates below the setting or above that rpm?

2841 min tps for baro up-date is set at 38%

2842 min tps difference for baro up date is set "0"

2844 update RPM is the maximum RPM for the baro to update. So if it's set to 3600, then the engine needs to be below 3600 RPM in order to update.
2841 min TPS is the minimum TPS level for the baro to update. So if it's set to 38%, then the throttle needs to be at least 38% before it will update.
2842 min delta TPS is the minimum change in TPS before the baro updates. If it's set to 0, then there does not need to be a change in TPS and baro update will just use the values from 2844 and 2841.

There is also a table at 2846 and a check value at 2845 relating to baro updates, but it's not known what those do or how they are defined. In my experience driving a '94 Corvette from 300 feet to 4800 feet, all I had to do was mat the gas and as long as the RPM value was below the limit, the baro updated.

FirstGenThree
08-18-2023, 06:46 AM
I'm curious to see where this goes. I've been wondering how and why this matters. If you go up in elevation, I believe you wont be able to reach the higher kpa values in your VE tables-but the air won't be there to need fuel so..? Does it shift the scale of your VE table? and if so why? Apparently i'm missing something here, as far as I see it, the engine is concerned with actual manifold density, not relative pressure to start up.

NomakeWan
08-18-2023, 09:24 PM
Going up doesn't usually matter until and unless you force the baro update then go back down. It will also matter if you live at a high elevation and regularly commute to a much lower elevation without ever getting on the throttle. In those situations, the BARO will be set to the high elevation reading, and you'll end up leaning out at the lower elevations since the computer will be doing BARO corrections based on incorrect ambient pressure. Going rich isn't a huge deal, and you tend to get on the throttle more when climbing, so it's not usually an issue for going up.

Going down, however, you do have to be aware of the BARO update routine.