Much lower boost target in 2nd than 3rd. TC off. Load x Gear x RPM has same values in all gears.

[bradsm87]

I'm a bit stumped on this one. I thought I just had really bad lag in low gears due to the bigger turbos and WGDC tuning still in progress so I did a 2nd gear log and it's the boost TARGET that's low.

See log below. It runs over 14psi in 3rd gear.

http://datazap.me/u/bradsm87/rr600-r...8-22&zoom=7-35


@martial@mhd , Is there any scenario where MHD skips overwriting the load per gear table?

[bradsm87]

Here's a 2-3 run to better show what I'm talking about.

http://datazap.me/u/bradsm87/rr600-r...=0&data=4-8-22

Here's a 3rd gear run from low RPM. Very different to the boost target in 2nd gear.

http://datazap.me/u/bradsm87/rr600-r...2&zoom=101-188

[TwistedTuning]

torque limit active is not logged in any of those logs. So hard to say if its a torque limiter in place or not. Are you using BBG or LBG? (boost by gear, load by gear).

There was one log where you went WOT under 2000rpms. i think it was like 1500rpms. i'd refrain from that, but its just my opinion. the 2nd-3rd gear log seems to bring boost target and mean in 2nd gear up to the 13-14psi you mention you hit in 3rd just in the upper RPMs. Makes me wonder if its just something in the tune. Maybe you inadvertently selected one of the gear limiters or something and didnt know it.

Can you log with the added parameter "Torque Limit Active". The wastegate duty cycle seems on par with the boost the car is creating.

[bradsm87]

Good idea. I'll log torque limiter active. Load per gear is filled with the same values in all gears. BLM per gear is blank and has never been set up yet.

I usually don't log from very low rpm like the 3rd gear log there but I'm trying to determine the max possible boost the turbos can produce at low rpm so I can set up the edge of the very high value (unachievable boost) part of my WGDC base table.

[bradsm87]

My new tune is started from the PPK for my car, rather than the stock BIN file. I forgot I did actually notice this difference months ago in this table. I suspect that's it. Will test today.

Stock:



PPK:

[martial@mhd]

@martial@mhd , Is there any scenario where MHD skips overwriting the load per gear table?

Here's how the bin is modified before flashing
- if the first RPM breakpoint cell is empty (0), rpm breakpoints are copied from the load target table.
- it the first cell of the table is empty (0), then each row is filled with the load target values.
- if the "load per gear" flash option is checked, the first 3 rows are capped with the flash options values.

[jyamona]

My new tune is started from the PPK for my car, rather than the stock BIN file. I forgot I did actually notice this difference months ago in this table. I suspect that's it. Will test today.

Stock:



PPK:

Very interested to hear if this fixes it!

[bradsm87]

Very interested to hear if this fixes it!

It did fix it. It seems that table works exactly as it says. I'd say it's safe to move that table to the "Torque Limiting Maps" section of the XDF.

[trebila]

so the "max torque at clutch" are "max boost by gear" tables, already defined in the DME.
Interesting.

[jyamona]

so the "max torque at clutch" are "max boost by gear" tables, already defined in the DME.
Interesting.

Not really. Load per gear tables that were added are just that, load per gear. Torque and clutch is an abstraction on top of that. It will look up torque via Load to Torque tables, then apply cap. I suggest maxing the torque at clutch table and using load per gear table, as it provides a limit per gear and per rpm.

[trebila]

understood.

but using always the same load to torque tables, playing with this max torque at clutch tables would induce different max boost per gear.

maybe harder to correctly set, compared to your load by gear tables