LS1 Boost OS - Development

[vwnut8392]

And Bubba, It'd be awesome if I could get a few tips on how the launch control is implemented, I had an issue where I enabled it at >70% tps, and it would spark cut while driving. Especially bad if downshifting, and giving a boot full, where rpm was higher than the launch rpm, the ecu would cut spark, but because rpm was 2000 above the launch limit, it would keep cutting spark even once the rpm was below launch rpm, I had to shut the car off to get it to reset to normal. Hope that makes sense.

I've since set the launch tps to 98%, but I feel it's either something I set incorrectly, or a glitch that may need addressing.

personally i would suggest that the TPS for launch control is removed from the code, its not necessary. if you have clutch switch and wheel speed those variables are good enough for that function.

[vwnut8392]

Here's a 12587603 BIN that has been patched with stock MAP sensor speed density to play with. having speed density with the other MAP modifications included here would be ideal with a boosted application since MAF is as always a flow limiter for a turbo application.

[vwnut8392]

finally got a vehicle built that i can actually mess with this stuff and have worked with the V3.4 of this. seems to work decent but i did find 1 flaw with the wideband closed loop control and that after coming down from deceleration the wideband sits dead lean till i blip the throttle than it comes back into control. im running this with the all the closed loop stuff for the narrowband sensors closed loop control completely shut off since they seemed to interfere with the wideband making contradicting adjustments. im running AEM failsafe with the sensor mounted in my X pipe since that where both banks meet to get the best reading. also i have the texas speed BFD chop monster cam in my 6.0L and when the wideband closed loop control is working it does do a good job with such a radical cam. way better idle fueling control than the stock narrowband sensors could ever do.

another suggestion is to look at sub_3580C, should be familiar with it because i see you made a jump out to custom code at the beginning of this routine. anyhow at the end of that one it appears that that is the decider to set the flag to show the ECU has actually gone into closed loop lambda control or not. i see it reads the coolant temp enable table than it checks the short term fuel trim closed loop enable and if its set it pushes the #2 into RAM byte_FFB2EF. would be great to have in indicator in the log showing that the ECU is in fact in closed loop control when its supposed to be. im using HPtuners to log and i will say that when it appears to be in wideband closed loop control the flag indicating closed loop does not set. should be a way to hijack that and make it set the flag when the wideband is running the show.