Focus ST - Desired Torque Drops

[murfie]

Could it be the blow through slope logic? Popcorn refers to late combustion that dumps fuel into the exhaust. It would be one of the few ways the ECU would know about this happening. EVC/IVO values on MP 10 would promote most blow through during boost.
Looks like the limit is happening spread across MPs 9, 10, and 13. 10 and 13 have lower values until 3000RPM. After that all MP are the same.
Also you are right at the maximum load table values if you correct for BP.

Might be as simple as enabling OP VCT have the exhaust cam rotate back toward 0 sooner to prevent the extra BT from higher boost levels. Or modify the drivability distance table to go to MPs closer to 0 sooner.

[Blown383]

I know if I rotate the cam back sooner, I will lose torque. On the F150s, there are a couple of tables that exist that can be changed to raise the popcorn limit. Unfortunately, when I emailed support, they said those tables do not exist in this calibration.

[murfie]

Those tables you refer to are to prevent misfires. Have you tried lowering the ECT temperature for misfire detection under engine diag. to some thing like 150*. It may ignore those tables at operating temps then.

[xpl1337]

Hi, anyone found a solution to this problem all this time? I have excatly the same problem on my 2017 focus st, and i cant find a solution. My desired torque drops just above 3350-3400 rpm.

[soad85]

Bumping this back up, same exact issue on a '17 FOST here. Desired torque drops off at ~3500rpm, and sets a flat limit of 285 or 286 torque. Ive been through 50+ tune revisions, talked with a professional ST/ecoboost tuner, and contacted HPT support. So far nobody can figure out why it's happening.

[mass-hole]

Bumping this back up, same exact issue on a '17 FOST here. Desired torque drops off at ~3500rpm, and sets a flat limit of 285 or 286 torque. Ive been through 50+ tune revisions, talked with a professional ST/ecoboost tuner, and contacted HPT support. So far nobody can figure out why it's happening.

What do all of your sources say?

I just had a problem with my F150 where all of my sources looked fine, and my desired brake torque was good, but my actual torque was dumping and throttle closing. Ended up being the turbo pressure ratio table. There was no indication that was the issue.

[Bill88stang]

ANYONE EVERY FIGURE THIS OUT? LOL i have same issue

[CherryTuning]

Hello,

Just bumping this thread up from the dead because I have only recently started tuning the Ford platform, and after fighting the same torque request drop, I believe I have found the issue... The torque limitation maps that end at 3360rpm are actually slightly larger in the binary data, and as such VCM Editor isn't getting the final row and it's reducing torque request at 3390rpm

I opened the stock file in VCM Editor, changed the maps, loaded it into the car, then pulled the binary with a different tool which then allowed me to open it in my binary editor software (WinOLS) to inspect the maps. Interestingly, as a side note, my logging is reporting a 388Nm torque request when over 3400 (regardless of my driver demand) - not 390Nm - I just changed my scaling to show a 500Nm number where HP Tuners is showing 500Nm, however given this discrepancy, I'm thinking that the actual scaling on the map is different too (out by <1%, meaning a 500Nm torque request is actually only 497Nm... not that it really matters in the scheme of things)

Anyway, here is the map shown in Nm, as imported from the ECU that had been modified by VCM Editor:
Ford_Torque_Error.png

Here is is in ft.lbs (I just changed my map scaling to convert the binary to show ft.lbs equivalent):
Ford_Torque_Error_ftlbs.png

After spending hundreds upon hundreds of hours working specifically on the torque modelling for the Hyundai i30N (I have one of our shop cars up to 535BHP with a completely standard engine), I know how insanely beneficial it is to have correctly modelled torque - and the fact that these maps are wrong means that anyone who is tuning these cars with VCM Editor is either turning off the torque monitoring, or is incorrectly scaling torque/load maps to give higher load requests at lower torque numbers, neither of which are the ideal way to tune any torque based ECU.

I plan on devoting a lot more time into the Ford Focus/Fiesta platforms in the coming months, so anything that I find I'll be happy to share.

Stay tuned!

[CFGBR95]

Yep, you're right, I've just checked my winOLS file for the focus and VCM Editor isn't fully exposing that table. Someone needs to raise a ticket for it.

If you ever moved onto the MK7 or MK8 Fiesta STs, give me a shout, been doing dev work on my own for a while now and I know the MK8 seems fairly popular is Aus!

[bloubul7]

On the MK7 Fiesta ST there are also a lot of tables not exposed in HP tuners which are required

[CFGBR95]

On the MK7 Fiesta ST there are also a lot of tables not exposed in HP tuners which are required

There's enough to see over 330hp and 420nm on the hybrids and S280 with ease whilst keeping closed loop torque control from what I've seen.