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

**kur4o** · 10-09-2018

$c366 01 01 01 01 [4 bytes, 01 value]
$e576 01 01 01 01 01 01 01 01 01 01 01 01 [12 bytes, 01 value]

In addition to Steveo patch change the bytes at this addresses to values specified and baro shouldn`t update anymore.

The tables are not added to the xdf since the disassembly is partial and not all parameters are identified.

**hotrodf1** · 10-09-2018

Originally Posted by kur4o

$c366 01 01 01 01 [4 bytes, 01 value]
$e576 01 01 01 01 01 01 01 01 01 01 01 01 [12 bytes, 01 value]

In addition to Steveo patch change the bytes at this addresses to values specified and baro shouldn`t update anymore.

The tables are not added to the xdf since the disassembly is partial and not all parameters are identified.

So what's this going to do? I gotta figure out how to actually do this too. LOL. Can I google it?

Do I need to add a table into TUnerPro to do this? Or try to use the hex editor? Like below for $C366?
hex edit - $C366.JPG

And then for $E576 like this? hex edit $E576.JPG

**steveo** · 10-09-2018

added kur4o's patches to my patches for you. just patch the patch and let us know how she goes

**hotrodf1** · 10-09-2018

Originally Posted by steveo

added kur4o's patches to my patches for you. just patch the patch and let us know how she goes

Hells yeah. Will give it a go hopefully tomorrow.

Many thanks again to you both !

**hotrodf1** · 10-10-2018

Well fellas, we have some success so far! I am indebted to you both, there was no way in the world I was going to figure that out.

I still don't understand what you did there, but it seems to work great. I didn't drive real far, but did the loop that would always reset it a couple times before, and this time she's solid.

Strangely enough, the Baro does update at key on, obviously not a bad thing at all, but then no amount of romping seemed to phase that baro setting.

Yahoo, let the real tuning begin, I hope.

**hotrodf1** · 10-11-2018

Well tonight was a little different story. I adjusted the spark tables, and a bit on the lower VE table, and was going for a test drive.

Then I notice cruising AFR seems to be quite lean and she's surging some. WTH? Check the scanner and she's updated to 10.35kPa again (happened a week and half ago or so)! Cycling key on / off did nothing to change it. So just went back home. Thought maybe it was the tune somehow, so tried yesterday's .bin file, and the 10.35 remained.

The only way I could get well from it was to try an unpatched tune. Load it, key on, then baro matched the current MAP reading, which is no surprise.

So then I loaded the latest tune back in, and it stayed put at 54.36 but I didn't drive it to try it out and see if it held or not. Guess I'll try that again tomorrow.

What's odd is that when I loaded the new patch last night, the BARO reading updated from in the 60's, down to 54.xx. It seemed to update at key on. BUt then tonight once it pulled 10.35 it wouldn't update again at key on.

Is it possible the ECM just saw a glitch in that sensor or something at the wrong time? Also, a common theme is it seems to happen after an adjustment in the .bin and a chip swap. Maybe it just wasn't seated in the ZIF or something?

**kur4o** · 10-11-2018

There is an error. Now baro never updates from memory. The value had cleared when you removed power from pcm.

Tell me what fixed value you want for baro. Do you want it to update at ign on engine off. There is also 6 tables that are baro related modifiers. If you set the baro at 55 kp these tables will always read the lowest position.

Patching anything will not be that hard. Just need to know how do you like the PCM to behave. Do you know some other PCM from that era that use 2 bar map sensor and turbo setup. I can copy the conversion from raw map to baro, so you don`t have to lose these built in baro corrections.

There is another conversion from raw baro 3f to some scaled map baro value stored at byte_0158. byte_0158 is used for baro table lookups.