NokiMo
Turbo V6
Turbo V6

patreon


Boost OS V5 & Updated Patch Tool

New for Version 5:

Patch Tool Updates:

V5 Full Feature List:

Change Log:

5.0 - Initial Release
5.1 - Added the ability to log BCDC via desired EGR Position
5.2 - Bug fix in Spark_Advance_Adders function for MAP based spark

Just like all prior versions this OS Patch is only compatible with 12587603 files. The patch tool can apply the patch to any factory 12587603 bin file as well as upgrade V2-V4 bin files.

To upgrade to V5 follow these steps:

1. Download Latest TunerPro Version, PCM Hammer V20, Attached DLL file, V5 XDF, and Boost OS Patcher.

Note: Ensure DLL file in TunerPro Directory "\Documents\TunerPro Files\Plugins"

2. Open Boost OS Patcher. (With bin file in the same directory)

3. Enter input file name. (e.g. "MyFile.bin")

4. Select an OS version to apply. (Recommended to Apply the Highest Version)

5. Enter the output file name. (e.g. "MyNewFile.bin")

6. Make tune changes, enable features, etc.

7. Flash tune to PCM.

PCM Hammer Version 20 is capable of flashing Boost OS, but Version 21 is not compatible. When flashing changes to the Boost OS Parameters a "Write OS, Calibration, and Boot" must be done since the new parameters are in a. Only the sections where changes were made will flash, hopefully a newer version of PCM Hammer will be able to flash just the calibration sections.

Comments

I have joined Discord.

David Germain

Join the Discord server and we can discuss more. Lots of things are possible, but would likely require additional features.

Branden Butella

Timing retard possible?

David Germain

Boost isn’t required to run the custom OS. I don’t have any specific N2O features, but you can still use it for the other features.

Branden Butella

I'm not planning boost but na/ n2o. Will this work? Particularly timing retard?

David Germain

i figured it out, i commented in several places on your discord server.

scott bradford

Appreciate the feedback, but without a log I can’t really debug or help provide feedback. Join the Discord server and upload a log in the #tuning-help channel.

Branden Butella

im using HPtuners to log it and i realized that in VCMscanner at least the commanded AFR never moves when driving. would be nice to have a confirmation in the logging that its actually following the commanded AFR table. im not sure how to send you a log on here. i can export it to CSV from VCMscanner if thats something your more comfortable with. the other thing i discovered is that when in deceleration the fuel trims go way positive and when the ECU tries to recover from this my truck seems to stall every single time. it didnt really do that when i was running it in open loop fueling. so it got me to thinking about a way to maybe lock the fuel trims in their current state during decel or even have them reset to 0 when in deceleration. The last thing i was thinking about is the update speed of the fuel trims themselves. mine seem rather slow. could be my setup, i dont know. over all it sort of seems to work but not. i found values that are the range that the fuel trims are allowed to move positive or negative, i'll try tweaking those around and see what happens because i do have an overly rich condition in mid RPM that i just cant seem to shake out of it and neither can the fuel trims.

scott bradford

Do you have a data log and tune file of the issue? I can take a look.

Branden Butella

found a potential code flaw when referencing the closed loop target AFR tables. yours isnt using the 3D table look up routine. i patched the code by hand to make it reference this routine and it seems to work a lot better. i have to check the other tables you added to see if they are reading that routine as well. thanks for the tip about STFT being enabled.

scott bradford

STFT needs to be enabled for it to work. My code uses some of the factory closed loop code but makes it work with a wideband.

Branden Butella

tried this version and the wideband closed loop appears to not work at all. when im just cruising along at 2000 RPM in a higher gear target AFR on the table is 14.7 but the actual AFR is 12.70 according to my AEM AFR gauge. i dont have any of the factory STFT or LTFT stuff enabled plus both upstream narrowband sensors have been completely removed. my AEM's sensor lives in the center of my X pipe so to get an accurate reading of both banks. over all it appears like i am just running in open loop the whole time. also my AEM gauges output is wired to the EGR input and is confirmed working via HPtuners VCM scanner. was really excited for this as it would make fuel tuning a breeze if it worked.

scott bradford

@Turbo V6 I have created a Discord account. Not sure how to upload files, it appears this is a chat site? Anyway, LMK how you want to share files. Thanks!

Julia Morgan

If you join the Discord server you can upload the file so I can help.

Branden Butella

Hi, having checksum issues. .bin was OK prior to patch, after the checksum isn't correct. I have some screenshots I can share. Thanks!

Julia Morgan

The way I did wideband control on this was to change the axis for the mv lookup table from airflow mode into EQ ratio. This allowed me to use the normal 0-1.1v input from the o2 sensors and just enable closed loop all the time with a simple jump. Wire both widebands to output the desired 0-1.1v and what is set on the table and it still uses the factory routines without adding additional code. Only problem is i never trusted any wideband controllers ability to generate proper ADC and the LSM-11 sensor was not being made anymore so I abandoned the use of it and kept it as a narrowband system. Great work!

Christian

Your timing is perfect! I'm currently wiring my newest project, an 1989 Corvette with 5.3l swap and twin GT3582 turbos.

John Faubion

Correct. Let me know if there are any issues.

Branden Butella

Awesome. Thanks for all your hard work. No rewiring needed right? Just data log EGR position PID to get BCDC?

Anthony Avila


Related Creators