Tuning diary

[grayjay]

Also- entries for TVUB (injector latency voltage dependence) in your latest .bin are different form the Bosch specs for "386cc" injectors. Was this an intentional injector adaptation tuning strategy or perhaps an error?

[willemml]

Also- entries for TVUB (injector latency voltage dependence) in your latest .bin are different form the Bosch specs for "386cc" injectors. Was this an intentional injector adaptation tuning strategy or perhaps an error?

I took these values from a TT225 bin. Where did you find the Bosch specs? I spent a long time looking for a datasheet but didn't find anything, I must have been looking in the wrong place/with the wrong search terms...

What values do you have?

[willemml]

Thanks- totally understand that Hextune is WIP, I just wanted to follow and see it developing. I did get the compiled .exe installed and it starts fine, great start and I am looking forward to more progress on it.

Yeah, happy to make it easy for people to try out, feedback is appreciated. I have been working on improved 3D graphing functionality with live reloading of the graph when you edit values. I will upload another exe when the bugs are ironed out (opening a graph while the window is too small causes a crash).

Comparing my logging files yours, I still have a lot of work needed on my tune. I only have 90 octane available and I am getting knocking & ignition retard events under boost so I need to work further on fueling and base ignition timing to keep knock under better control. I also figured out that much of my current boost tune is riding (stock) KFLDHBN instead of altered LDRXN. Tunerpro's compare tool is great for identifying all the differences between two .bins.

I've been meaning to try using 91 or 89 octane (which is much easier to get, I have to drive 30 minutes out of my way to get 93) I'll stick to 93 for the time being until I have the time to empty the tank twice with testing.
Stock KFLDHBN is very low. And yeah, I love TunerPro's compare tool, it's one of the top items on my list for HEXTuner.

To tune the ignition angle I would just pull each value after the first rpm range you get knock in back by 3 until you have 0 knock, and then maybe increase a little after boost starts tapering down.

What is the post cat lambda disable map xdf location that you changed? There are several Kat maps, I did not spot which one you reassigned. I did see and made the recent location change for CWSLS (SAI diagnosis) that was called out in community thread, I just dont see anything similar for Kat maps. The 1.8 stage 1 Community thread post #776 also has another xdf with even more tables defined, seems to be an expanded fork from the TylerW xdf. It would be nice if Tunerpro (or hextune) could find and help manage merging of differences in xdf files, sort of like it can do for .bin files.

Sorry, I meant SAI CDSLS as mentioned in the community thread.
My goals for HEXTuner do involve more definition manipulation, I am probably going to switch to a new file format of my own because XDF is clunky and not well documented.
If/when I do that I will create tools to easily convert from XDFs, as well as tooling to compare differences between the definitions so you can pull in from a bunch of XDFs.

Other changes I want to work on, alter KFNWSE - Map for intake camshaft advance. On our B6, VVT is implemented more just as an EGR emissions control feature but the stock 225 TT ECU tuning uses VVT for performance, retarding intake cam early under load to achieve faster boost spool up then advancing later when no longer needed. I would like to either try matching KFNWSE to the TT settings or else setup and log runs with the VVT advanced and then retarded, compare and try to determine optimal switchover points.

Oh that's really interesting. I have been considering trying out TT225 stock maps for everything because it runs K04 and the same injectors.

I also still need to work on boost PID control. Either implement the full pre-control strategy described at Nefmoto by setting up KFLDRL and KFLDIMX or else just try adjusting the three PID term tables KFLDRQ0, KFLDRQ2, & KFLDRQ2 (these are the three separate Proportional, Integral, and Derivative term response maps). I understand that these all have row axis of 100, 200, 400, & 700 that are the mBar deviation of boost setpoint error, but any idea what the entries within the table represent? Description I have seen is that these are corrections that are made by each PID term for each 100mBar of boost setpoint error. Are these table entries in units of PID duty cycle? (table values are around 20-30. Or, are thes mBar adjustments that somehow feed together into another PID table(s)? The stock KFLDRQx table entries all look like they were crudely setup by audi without much PID tuning and could likely benefit from some tweaking to produce different response at each of the 100, 200, 400, & 700 setpoint deviation levels. It would just help if I better understood how these table entries influence the final PID control.

This is also where I still need to do more work. I am thinking I will try to implement the full pre-control strategy. I have no idea what those units are. I suspect that I am going to need to learn how a PID actually works.

[willemml]

Ok so I took a crack at the feed forward PID implementation. I used SB_GLI's tool to calculate the new KFLDRL.

So to do this you need to first take some logs at fixed waste gate duty cycles. I did logs at 0, 10, 20, 30, 40, 50, 60, 70, and 80 percent.
To do this, edit your bin so that CWMDAPP = 8 and then every time you flash in between logs you will edit KFLDRAPP to be your desired WGDC. If you use the intervals I did you'll wind up with 9 bins.

Ok so now take each file, flash it, and log a 3rd gear pull. You need to log the following:
- wdkba (throttle plate angle)
- ldtvm (waste gate duty cycle)
- nmot (rpm)
- pvdks_w (absolute manifold pressure)
- pus_w (atmospheric pressure)

In the end you should have 9 logs, and if you open each one up you should see that during the pull your WGDC was locked at the desired value.

Thats the how to get started, I think I did the actual bin editing wrong for the second bit, so I will post it later. The axis for KFLDIMX is defined twice and one of them halves the boost axis values. I think I put them too low which locked WGDC at 95% most of the time, fun, but a very quick way to overspool and kill the turbo.

Edit:

I forgot to adjust KFLDHBN so I was still running a 2.6 pressure ratio... Anyways I dropped that down and now my PID changes look better.

So continuing, once you've done the logs go back to your original bin (without the WGDC changes). Edit KFLDIMX so that each column contains only one value. Supposedly you are supposed to make this perfectly linear. So I used the interpolate function in TunerPro to make the axis values go from 0 to 2300 and the each row to go from 0 to 95. I also set the column axis to the values suggested in the LDRPIDTool.

Once you have your values set for KFLDIMX, you need to input them into LDRPIDTool. Once you've done that, open the folder that contains only your 9 fixed WGDC logs with the tool. Then click generate. It should give you a table. You can copy and paste this into the KFLDRL table in TunerPro. You will have to massage the values around the edges because the tool doesn't calculate everything. I just set the far edge values to something that I liked and then used the interpolate tool again to make it smooth.

I can't tell if this has made anything better, and I am pretty sure that I did it wrong. I am still not sure what the ideal KFLDIMX values are, but I'm not seeing anything super negative in logs.

As always, feel free to ask for clarification and do point out any mistakes I made. I don't really know what I'm doing, but I am figuring things out.

I will post all the logs and bins at some point tomorrow. Oh also, tried doing a few 0-100, the best logged one was only 13.6s I think... A little more fun than 3rd gear pulls on the same stretch of road over and over again.
I also will probably do another fixed WGDC log again at 90%, and I will likely set the result of that to my maximum requested load and or pressure ratio. I won't do 95% because then there is no limit on boost/spool which is bad.
I'll then re-run the LDRPID tool and put the values into my bin for KFLDLR.
Also really starting to look forward to the FMIC arriving, I've been hitting very high IATs (50-76) especially with ambient temperature having come up to 7C.

[willemml]

Went and did more PID tuning today. I did another locked WGDC run at 90%, and then re-ran the LDRPID tool. After putting those values in and massaging everything so the transitions were smooth I flashed it and did a 3rd gear pull.
in the 3-4k range the WGDC would suddenly drop so I upped the last column of KFLDRL and logged a few times until I had massaged the values to the point where actual and requested boost were following each other very closely.

I also upped KRKTE (after a week or two of driving my LTFTs had hit +7%... I also realized that I had set ZKLAMFAW wrong, I had it high instead of low (so LAMFAW was heavily delayed, no wonder I was getting knock...) so I dropped that down to 10 and it seems much better now.

As promised here are the uploaded logs for my PID tuning process with each locked WGDC as well as each bin and a config for ME7VisualLogger: https://files.willemml.net/files/tuning/pid/
And here are the logs for yesterday and today for my final fine tuning of KFLDRL. https://files.willemml.net/files/tun...gs/audizine45/

I also change LDRXN a bit to do some smoothing and slightly more load at the high end.

I also uploaded my final bins, as of this post I am running v14 https://files.willemml.net/files/tuning/wml_tune/

[willemml]

Oh also here is the latest version of HEXTuner, 3D graphing works, however it will crash in some cases if the window is too small. https://files.willemml.net/files/sof...ew-edc5f80.exe

[Gin+]

Oh also here is the latest version of HEXTuner, 3D graphing works, however it will crash in some cases if the window is too small. https://files.willemml.net/files/sof...ew-edc5f80.exe

I can't wait to check that out