Progress Thread finally tuning (and more)

I have your .bin file. Now, I need the definition file.



  1. With his tune open in Binary Editor, look at the bottom-left status bar for the loaded strategy/definition filename. Double-clicking that name may show its revision and other details. Getting Started.doc
  2. Open Windows File Explorer, select This PC, and search for GUFB. Let the search finish.
  3. Look for a file ending in .xls, .xlsx, or .cry that matches the name shown in Binary Editor. A common location is C:\Binary Editor\DEF\GUFB, though the installation folder can differ. Moates
  4. Copy that file to the Desktop, then attach the copy just as he attached the BIN. No need to open or modify it.
If several GUFB files turn up, send a screenshot of the results and the definition name shown in Binary Editor so we can identify the right one.
ive got nothing with .xls, .xlsx or .cry. Everything under GUFB is a .bin
 
IMG_8176.webp
 
Below is the modified .bin file and a .zip file containing old values, new values etc.

The revision extends spark coverage to 160% raw load, reduces timing through the higher-load regions, and resamples the tables sharing that load axis. Measured NA scaling points remain unchanged; It corrected the anomalous upper endpoint to hold the 6,000-rpm value.

Retained the existing fuel targets, MAF transfer, and injector settings, and removed the two-second high-load open-loop delay.

Offline byte, interpolation, and checksum checks passed. This has not been validated in Binary Editor or on the engine. Open it with your GUFB definition and compare the tables against the included report before writing it. Initial testing should establish timing agreement, wideband accuracy, fuel-pressure tracking, and charge temperature before progressing into boost.

The very last file (.pdf) is a guide that will walk you through manually inputting each of the suggested changes.

It should be pretty conservative. Your data-logs after you've had a chance to test it, will tell us more.


I probably don't have to say this but I will: Make sure all of current files are saved someplace where you [know] you can get to them.

Let us know how it does!
 

Attachments

Man this is awesome, thanks! What a treasure it is to have access to people so willing to share their knowledge and spend their time helping. I hope I can help others in meaningful ways. I'll get busy with this tomorrow and follow up! Thank you thank you and thank you again....
 
  • Like
Reactions: Noobz347
Where is your ACT sensor mounted? That could change my timing recommendation. Also, is yours intercooled?

Noobz, what total timing did you give him ay 140-160 load?

The bottom row, R7 / 160.00061%, shows the 160% values. There’s no separate 140% row—the ECU interpolates between R6 / 100% and R7 / 160% to get those numbers.

1792297426789.webp



So, in the main operating range, about 16–17° at 140% load, tapering to 14–15° at 160%
 
I want the data logs to tell us how it 'feels'.

JD has already done the hard part getting it all up and running.
I promise I will run and share logs. I will do some NA logs, then finish the boosted tune and put the blower stuff back on the car and do some more. Tell me what parameters I should run. I want to exclude anything not needed to keep it as tidy as possible.

I will get the logs posted but it might take a few days. The Mrs. is pretty pissed at me now for having my head buried in this project for the last week so I need to turn my attention away from the car for a bit. Dont worry because it wont be long before she gets tired of me fawning over her. Please bear with me.

I really like the looks of the timing table you made Noobz.

To everyone who is helping drag me across the finish line, thank you very much!

:hail:
 
  • Like
Reactions: WhiteCobra95