2 bar tune for Turbo LT1 F-body possible with '93 ECM? DA3

[steveo]

i can dig into other stuff that uses map to see if adjustment is necessary

i'd like to say we can set baro to a static value for a boosted engine, assuming it isnt going cross country (or maybe even if it is)

[hotrodf1]

i can dig into other stuff that uses map to see if adjustment is necessary

i'd like to say we can set baro to a static value for a boosted engine, assuming it isnt going cross country (or maybe even if it is)

Thank you, thank you , thank you SteveO and Xnke for thinking about / looking into this for me. Looks like there's a few items in there to get me in trouble!

So you could potentially set baro = 100 manually, but I'd still use the 2 bar MAP and set all the tables as such, where 55kpa = 100 in reality?


I don't have much to offer in the way of solutions, as I just don't understand the code and how it works. (but I can test it! ) Is there somewhere you would suggest that I could learn up on this?

[steveo]

Thank you, thank you , thank you SteveO and Xnke for thinking about / looking into this for me. Looks like there's a few items in there to get me in trouble!

So you could potentially set baro = 100 manually, but I'd still use the 2 bar MAP and set all the tables as such, where 55kpa = 100 in reality?


I don't have much to offer in the way of solutions, as I just don't understand the code and how it works. (but I can test it! ) Is there somewhere you would suggest that I could learn up on this?

if running fixed baro i think you'd set it to something like 50kpa (7F)

these are all motorola 68k instructions, look up a tutorial on 68k (aka 68000) assembly code online somewhere, there are lots of them

[hotrodf1]

if running fixed baro i think you'd set it to something like 50kpa (7F)

these are all motorola 68k instructions, look up a tutorial on 68k (aka 68000) assembly code online somewhere, there are lots of them

Ok I’ll check it out.

And the ecu currently reads 55.4 kpa as the baro reading. So if we set it to that my current tune and all would remain valid I think.

[hotrodf1]

i can dig into other stuff that uses map to see if adjustment is necessary

i'd like to say we can set baro to a static value for a boosted engine, assuming it isnt going cross country (or maybe even if it is)

Hello Steveo,

I've been looking at the disassembly some with the code you referenced in previous posts. I can at least find it in there, big step for me LOL. Currently reading up on the Motorola 68k stuff. Learning curve for me, I'm certainly not a programmer.

Where do we go from here?

[hotrodf1]

More parts have showed up. Hotside stuff will all be here in a couple days.

Any time to look into the baro update deal Steveo?

[steveo]

i took that DA3 xdf and added a patch for what we discussed earlier, so apply that patch, then modify the scalar named ** BAROMETRIC INITIALIZER

i -think- that will force whatever initial baro value you set. please test it, even key on engine off just to see if the initializer holds.

i also noticed that the xdf is a bit error prone, for example the map threshold for PE entry had no conversion on its value (i added a conversion), just be wary of any MAP related parameters that dont max out at ~105kpa, they might not have their math done properly.

[steveo]

just to detail what we're doing with this hacky fixed baro patch (want to modify as little as possible)

- @0xC366 instead of setting baro=map during its update routine if conditions are met, it simply sets baro=baro and moves on.

- @0xA3CF during the keep-alive (or other update) routine (which ensures map never exceeds baro), it compares map to baro, but doesn't actually store the value (i just changed STAA to LDAA, so it's loading the value again and continuing on)

- @0xE5E4 we override the initial value for BARO (0xFF / 104.5KPA) to a new fixed value (about half of that for your two bar thing)

keep in mind the bin offset is 0x8000 and disassembly addresses are relative to 0x0000.. so if you're looking at the bin, subtract 0x8000 from the addresses above

[hotrodf1]

You da man Steveo!

Thank you for the help. I have found a couple resources for operations / coding / instruction for the 68HC11, but still so much to learn. The computer science stuff I took in college was FORTRAN, and I remember about none of it LOL. So cool you are able (and willing!!) to help me out and make this work. I still can't believe TunerPro is out there, and these files are available, basically for free.

Anyhow, tonight I got it loaded onto the EEPROM per your instructions, and tried key on engine off first. Baro was showing 54.63, which is what I had set it to in the scalar var. you put in the XDF ( ** BARO INITIALIZER ). So far so good . . .

Then decided to start it, and see what happens. No drama! She starts and drives just like before. I didn't have the wideband on it, so not sure if the A/F ratio is right where it was, but it seems close enough for now. After driving for a bit, some cruising, some WOT stuff, etc., the BARO was still the same. So it appears that is working.

So, is there anything to worry about here, with setting the baro manually like we have? If the weather changes etc., altitude changes, will I have issues with the A/F ratio getting thrown out of whack? I'm sure the Baro reading has a strong influence on the fuel delivery calculation. I have no idea how "sensitive" to a small change in actual Baro it would be. Remember I'm in open loop, so there's no BLMs at work here.

Also, should I expect to get the "high MAP sensor" code 33 when I go into boost? Obviously can't try that just yet.

Some of the stainless hotside mandrel bends showed up today. Gettin ready to get serious, not lacking much now.

[steveo]

So, is there anything to worry about here, with setting the baro manually like we have? If the weather changes etc., altitude changes, will I have issues with the A/F ratio getting thrown out of whack? I'm sure the Baro reading has a strong influence on the fuel delivery calculation.

hell no, a 2 bar map with an 8 bit scale isn't nearly accurate enough for weather barometrics! the stock sensor is about 0.5kpa resolution. with your division you're more like 1kpa per step now.

think about it, what is your summer to winter kpa variation anyway? now divide it by two since you halved your kpa, i bet it's 0.02 or less.

tune for high air density, and when air density drops a bit from the weather, the extra juice wont hurt anything.

large altitude changes are an issue, but keep in mind even if you DID have baro update on startup, you'd have to pull over and restart the car every time you changed altitude, agin, that's why lots of factory turbo cars have a second sensor for baro pressure

boosted engines don't mind being a bit rich in the short term, all that extra combustion pressure and heat will burn off the excess no problem.

Also, should I expect to get the "high MAP sensor" code 33 when I go into boost? Obviously can't try that just yet.

i doubt it ...? but we could just disable that code. i don't think most speed density ECMS throw a default on map errors (if it did, it would probably be pretty nasty in this case)

if i have more time i'll trace all your map sensor code too and see if i can find anything like that, or other variables that need to be /2

[hotrodf1]

just to detail what we're doing with this hacky fixed baro patch (want to modify as little as possible)

- @0xC366 instead of setting baro=map during its update routine if conditions are met, it simply sets baro=baro and moves on.

- @0xA3CF during the keep-alive (or other update) routine (which ensures map never exceeds baro), it compares map to baro, but doesn't actually store the value (i just changed STAA to LDAA, so it's loading the value again and continuing on)

- @0xE5E4 we override the initial value for BARO (0xFF / 104.5KPA) to a new fixed value (about half of that for your two bar thing)

keep in mind the bin offset is 0x8000 and disassembly addresses are relative to 0x0000.. so if you're looking at the bin, subtract 0x8000 from the addresses above

When I subtract 8000 from E5E4, I get 65E4. I notice the address for the barometric scalar in TunerPro definition file is 65E5. Could this be why manual baro setting doesn't work?

[hotrodf1]

When I subtract 8000 from E5E4, I get 65E4. I notice the address for the barometric scalar in TunerPro definition file is 65E5. Could this be why manual baro setting doesn't work?

Tried changing that address, no success. Baro stayed right where it was at (like 67 or something). Thought I was one to something. Maybe it has something to do with the "non volatile memory" - from the disassembly notes ? It's like the ECM is reading the value stored instead of writing what we want it to.

Also tried to just disable part of the patch. If I disabled either half of the patch, it did not update the Baro setting at key on, that surprised me. Disabled the whole patch, then it would update Baro to MAP of 55kPa. BUt upon driving, it would update Baro to something under boost eventually. Something in the high 60's running the tune rich.