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

[Xnke]

The baro update can happen any time the PCM would normally do a baro update, regardless of 100kpA, but it will happen automatically at 100kpA. You need to disable that.

How are you retarding your spark?

[hotrodf1]

The baro update can happen any time the PCM would normally do a baro update, regardless of 100kpA, but it will happen automatically at 100kpA. You need to disable that.

Is there any way to know when it would be updating the Baro? After tonight I'm not convinced the ECM is going to care, even if it does update. It's still going to just see 54.36. Now when boost is in the equation, what will happen? I have no idea.

But I don't have a way to disable the auto update - at least not that I know of. Unless Tunercats can do it, which I don't have. I've looked a few times, and TunerPro doesn't seem to have a way to change the baro update programming. I'm kinda stumped on this one so far. Thoughts?

How are you retarding your spark?

Just using the standard tables. I charted the 1 bar vs. 2 bar readings out in excel and modified the table that way. Starting with 60kPa, just start pulling timing out. pull more at 70, more still at 80, and so on. All values over 55 in the table will be "boost" (since 55 on the 2 bar MAP is 100 on the 1 bar map), but the ECM doesn't really know, it's just using the tables as designed based on MAP reading.

I had the car running and driving pretty nice tonight on the 2 bar tune. CHanges for tonight were just to max out the cylinder volume, and reduce injector constant to 28 (have 32lb injectors) to richen enough. I'm not exactly sure what other gremlins are waiting for me on this. At least in NA trim, it seems to be just fine. I think by modifying the PW calculation this way, it's compensated for the low baro reading. Can anyone confirm that makes sense?

[Xnke]

Baro updates, at least in the P66 codes, happen at a maximum RPM that can be set, and 100% throttle. So for example, the factory settings for the 3.4L camaro is 4000RPM, so with the stock throttle body, at anything under 4000RPM if you went 100% throttle, it would take a barometric reading. If you're under boost when that happens, all your un-boosted fueling will be significantly affected. There are (in the 3.4L camaro code) 25 parameters that are affected by the barometric readings, including: altitude correction to MAP, MAP sensor offset, IAC steps multiplier vs baro, A/C added IAC steps multiplier vs baro, barometric correction to accelleration enrichment, barometric multiplier for power enrichment threshold, fuel pulse width multiplier vs baro.

In tunerpro, you can do a ctl-F to search for any parameter with BARO in the name to pull all the ones you need to consider.

I don't have DA3 or EE up in front of me right now, but I do have the v6 version from the same years code pulled up-that's what I'm working on.

Also, when you did your scaling did you take into account the different MAP sensor offsets?

1 bar sensor has a 10.3kpA offset, 2 bar is 8.8kpA. So, your ADC counts (what the PCM is using the actually do the fueling) would be (offset - minimum readable pressure) / ((max readable pressure - minimum readable pressure)/255) If you didn't take that into account, it could be a problem later. The computer doesn't read kpA, or even volts, it reads ADC counts...so a 0-5V sensor has 255 discrete steps, minus 0 and 255, that are usable.

[hotrodf1]

Baro updates, at least in the P66 codes, happen at a maximum RPM that can be set, and 100% throttle. So for example, the factory settings for the 3.4L camaro is 4000RPM, so with the stock throttle body, at anything under 4000RPM if you went 100% throttle, it would take a barometric reading. If you're under boost when that happens, all your un-boosted fueling will be significantly affected. There are (in the 3.4L camaro code) 25 parameters that are affected by the barometric readings, including: altitude correction to MAP, MAP sensor offset, IAC steps multiplier vs baro, A/C added IAC steps multiplier vs baro, barometric correction to accelleration enrichment, barometric multiplier for power enrichment threshold, fuel pulse width multiplier vs baro.

First: what represents 100% throttle? on TPS% or MAP reading? GUessing TPS %.

So it sounds like my safest bet is to somehow take that RPM for the update and just run it up to 7000 or something that I won't be hitting. How in the world do I do that, if it's not an option in the $DA3 mask I have on TUnerPro? I do have a couple other ones from other sources, but pretty sure they have even less, I'll check anyway. I'm somewhat new to tuning, this LT1 was the first I've tuned that didn't have a carb, LOL. So to do a binary editor or something, I just would have no idea where to start to be honest.

I think I dealt with several tables that have a baro reading, or MAP reading, but if it updates to something other than 54 ish kPa, I can see that it will likely get really rich. Which would mean I'd have to shut the car off, then restart to reset the baro reading, and get it back home. I haven't bought all my turbo stuff, so was trying to get the 2 bar tune worked out somewhat before I spent the money.

In tunerpro, you can do a ctl-F to search for any parameter with BARO in the name to pull all the ones you need to consider.

Ok I'll try that

I don't have DA3 or EE up in front of me right now, but I do have the v6 version from the same years code pulled up-that's what I'm working on.

Also, when you did your scaling did you take into account the different MAP sensor offsets?

1 bar sensor has a 10.3kpA offset, 2 bar is 8.8kpA. So, your ADC counts (what the PCM is using the actually do the fueling) would be (offset - minimum readable pressure) / ((max readable pressure - minimum readable pressure)/255) If you didn't take that into account, it could be a problem later. The computer doesn't read kpA, or even volts, it reads ADC counts...so a 0-5V sensor has 255 discrete steps, minus 0 and 255, that are usable.

I think so. Here's a snip of what i did, maybe you can give it a look and see if it makes sense. I found equations for voltage vs. MAP reading for both MAP sensors. So I took the 1 bar reading, then converted to volts. Then took each voltage and converted to the 2 bar equivalent reading. (see first pic) It seems to be working well, my old VE tables were modified according to this, and when I ran closed loop to get a read on BLMs, I'm seeing a pretty nice even display, so it would seem whatever offset has in reality been taken care of. Not sure, just trying to logic my way through

[hotrodf1]

Well I'm happy to report that the 2 bar MAP tune is working well with the motor running NA.

THe most immediate concern I have now is just the inability to turn off the barometric updates in the ECM. Could someone at PCM for less solve this for me perhaps?

I tried looking through the $DA3 disassembly, but that's way over my head to even attempt to figure out where I'd need to go to add that variable in TunerPro. Any ideas out there?

[Xnke]

It's been talked about in the $EE code for a long time, but something was in the way-I am not sure what it was. I know the RPM limit is hardcoded and would require a major code redesign if you wanted to go higher than the factory PCM's max RPM (not the stock engine redline, but the "PCM" redline...) and I think the 2-bar MAP swap was something similar. Hopefully this thread will result in a proper 2-bar support for the LT1 PCM...there are a few old Nissan V8's that could REALLY benefit from this (they used a distributor with a timing output identical to the optispark!)

[hotrodf1]

It's been talked about in the $EE code for a long time, but something was in the way-I am not sure what it was. I know the RPM limit is hardcoded and would require a major code redesign if you wanted to go higher than the factory PCM's max RPM (not the stock engine redline, but the "PCM" redline...) and I think the 2-bar MAP swap was something similar. Hopefully this thread will result in a proper 2-bar support for the LT1 PCM...there are a few old Nissan V8's that could REALLY benefit from this (they used a distributor with a timing output identical to the optispark!)

I'm pretty sure the $EE code has the baro update feature worked out already. I think skinny pedal said he was able to turn it off.

That being said, if someone was sharp, it seems as if they could use the code in $EE to find where it's buried at in $DA3, maybe it looks similar. Might be way off base on that. Again, over my head at this point.

I think I'm at the point where I'm just gonna have to try it and see what happens. Then, if it doesn't work. . . . I"m not sure what I'll do. LOL