MK7 Golf R please help with torque limit?

[rot62]

I have a 2015 Mk7 Golf R with a DSG. Im having problems with the car closing the throttle on gear shifts and taking to long to open fully again.
I had it on the dyno and the tune was making around 500Nm, reaching boost target and the throttle staying fully open during a pull.
Now its on the road and you do a pull from 1st up to 4th its only getting to about 440Nm, not reaching boost target and after gearbox shifts the throttle quickly opens to about 70% and then slowly opens but never reaches being fully open before the DSG needs to shift again.
If I do a manual pull say in 3rd gear from 2500 rpm to 6500 ( like when it was on the dyno) the throttle goes fully open and boost target can be reached.
Im lost to where I should be looking and what to log to see what is limiting the car when going up though the gears

[aaronc7]

Any logs capturing the issue? I'll try to take a look later tonight.

[jasontrumpio]

I ran into this before and am racking my brain trying to remember what I did to fix this. I think Aaron actually helped me with it.

[rot62]

Any logs capturing the issue? I'll try to take a look later tonight.

I have only just back to this car but here a log of the problem going up though the gears with the throttle closing and a long of just a third gear pull

[rot62]

I think i may be moving forward had a play with indicated torque limit tables MAX PC1 -MAX PC4 and now a can see over 500nm and the throttle is not closing. But the new problem is if I try and put these tables up over 560mn the car goes into fault and shuts the throttle off completing until you cycle the power" stop and restart car"

[alwaysbrokemk5]

Have you tried setting ECM 29541 to a value out of the way? (Engine -> Torque Model -> Monitoring)

Also what are you using for boost control?
Throttle inlet pressure set point is set to 37.5psi boost pressure flat
Max pressure ratio is set to 28ish psi boost pressure flat
and then driver requested torque is just flat at 600nm

An is38 isn't gonna hold that high of a pressure up top

[rot62]

Have you tried setting ECM 29541 to a value out of the way? (Engine -> Torque Model -> Monitoring)

Also what are you using for boost control?
Throttle inlet pressure set point is set to 37.5psi boost pressure flat
Max pressure ratio is set to 28ish psi boost pressure flat
and then driver requested torque is just flat at 600nm

An is38 isn't gonna hold that high of a pressure up top

its got ball bearing hybrid on it

[rot62]

Have you tried setting ECM 29541 to a value out of the way? (Engine -> Torque Model -> Monitoring)

thanks i will give that a try

[alwaysbrokemk5]

If you are tuning it with an aftermarket turbo in it, you'll need to make some adjustments to the wastegate tables. Even better if you reach out to the support and get the wastegate patch added for your box code.

[rot62]

If you are tuning it with an aftermarket turbo in it, you'll need to make some adjustments to the wastegate tables. Even better if you reach out to the support and get the wastegate patch added for your box code.

I didn't think that the wastegate was doing to bad at the moment.
I did see all the comments about the wastegate patch, but i didn't want to change to much until I got my head around this platform as this is my first time trying to tune 1.
I could find any documents for tuning this platform with Hp tuners so I have been using the simos tools docs.

[aaronc7]

The problem is you really have no idea how the WG is doing with regular mode 22 logging (what HPT has).

Your box code is 5G0906259E_0007, which is SC8H65 software/OS version. I just made a high speed ram logger and simple wastegate logic patch for H65 last night, but you'd need to move to VW_Flash or Simos Tools of course.

[rot62]

The problem is you really have no idea how the WG is doing with regular mode 22 logging (what HPT has).

Your box code is 5G0906259E_0007, which is SC8H65 software/OS version. I just made a high speed ram logger and simple wastegate logic patch for H65 last night, but you'd need to move to VW_Flash or Simos Tools of course.

I did try with Simos tools first but couldn't get pass the stock torque limit, it looked like the xdf was missing tables for the dsg. can I send the the xdf and bin that I had?

[aaronc7]

You're on 0D9300012L_4932, which is F49M software, and there's an xdf that has every single possible table defined, so there's no reason you can't get past whatever limiter you're hitting.

If you're on facebook, joining the simos tools users group on there is a good place to get started and place to ask questions and whatnot. I can take a look too

[rot62]

You're on 0D9300012L_4932, which is F49M software, and there's an xdf that has every single possible table defined, so there's no reason you can't get past whatever limiter you're hitting.

If you're on facebook, joining the simos tools users group on there is a good place to get started and place to ask questions and whatnot. I can take a look too

I did join the Simos tools group and thats when it is was pointed out the missing tables.
Is the Hp logged "Wastegate Duty Cycle" and "Wastegate Duty Cycle Desired" not what the wastegate is doing?

[aaronc7]

Two different things.

WG and WG desired in the case of hptuners or mode 22 logging is commanded WG position vs actual WG position. It has its own PID control system to ensure commanded position = actual.

What RAM logging opens up is the ability to log what the "base" commanded WG position is.... aka what's being commanded (before PID control) in the WG tables. This allows you to know if and where you need alter the WG feedforward tables so you get smoother boost curve with minimal closed loop intervention.

IDK who commented that the XDF is missing something that's required, but that's definitely not the case. Either F49M_DSG_v1.013.xdf or F49M.ALL.xdf will have it.

[rot62]

just to share this is where I ended up with. I have new problem but only when using launch control. But I will start other thread for that.