Interesting, so when you uninstall AP and then reinstall, it puts all the maps back on? Neat. Oh well, I"ll just wait until Tuesday.

 

@Alex@Stratified Can I update my AP using this firmware and still use your calibration?

 

I have been able to use mine with the new firmware.

 

@COBB What time is this update going live? I want to know when I should be looking to update my AP to the final release version.

 

Lol. I've been connected since 330am.

 

In for an update on what the new features are

 

the v204 maps and note
COBB Tuning - Accessport Off The Shelf Maps
https://cobb.app.box.com/focus-st-map-notes
V204 – Major Update Added custom WGDC compensations. Adjusted rev limiter strategy. Adjusted BPV settings.

This sounds promising

V204 – Performance and Pseudo Economy Mode
o Map slot 1 = Performance – This is the standard OTS map with full performance.o Map slot 2 = Pseudo-Economy – This mode disables the wastegate and adjusts WOT fueling for efficiency. This
can be used to quickly lower power for times when performance is not needed but is not as thorough as the true Economy Mode calibration. For full economy enhancements please use the Economy Mode calibration.

 

V1.7.1.1-8831 is out. no list of changes that I see.

 

Dear @COBB,

I love you guys. The new compensations are excellent. I'm already in love and I haven't even utilized all of them yet.
I appreciate that you allow us to also use the OEM tables + compensation or the COBB + compensation.

Thanks,
Bugasu

Edit:
I noticed you guys say Load Error = Load Desired Tq Ctl - Load Actual.

What then is the true difference between Load Desired Tq Ctl and Load Desired HDFX?
I've been using HDFX, assuming it derives from a blend of the current torque request applied to all Load to Torque tables,
and then has further limits applied to it. (LSPI and so-forth).

Load Desired Tq Control seemed to ignore the limits. Wouldn't it make sense to follow HDFX instead of Tq Cntrl?

 

Dear @COBB,

I love you guys. The new compensations are excellent. I'm already in love and I haven't even utilized all of them yet.
I appreciate that you allow us to also use the OEM tables + compensation or the COBB + compensation.

Thanks,
Bugasu

Edit:
I noticed you guys say Load Error = Load Desired Tq Ctl - Load Actual.

What then is the true difference between Load Desired Tq Ctl and Load Desired HDFX?
I've been using HDFX, assuming it derives from a blend of the current torque request applied to all Load to Torque tables,
and then has further limits applied to it. (LSPI and so-forth).

Load Desired Tq Control seemed to ignore the limits. Wouldn't it make sense to follow HDFX instead of Tq Cntrl?

The HDFX version is based on the lookup from the array of tables and does not include limitations based on torque control events. If the load target was limited the load desired to control would be more representative of the true target. When not limited these two targets should be nearly identical.

They posted a tweet about it today but nothing here it seems. In the release notes it mentions "Focus ST ROM Support Added" does any one know what this is?

We added support for the new TSB rom files as well as some older 2013 files that were rare to see.

Cheers,
Braden @ COBB

 

Strange, no official release info from Cobb

 

They posted a tweet about it today but nothing here it seems. In the release notes it mentions "Focus ST ROM Support Added" does any one know what this is?

 

Something must not be right. I'm looking at a v204 tune and don't see the new wastegate tables nor do I see anything different in the 5-way maps outside of desired fuel targets. Both slot 1 and 2 have a WGDC of 0

 

Have you updated your ATR software?

Braden @ COBB

 

It really blows my mind how much Cobb takes care of the community. I'm so used to HP Tuners where the devs pretty much **** on the customers and wouldn't really share much info.

 

Is anyone elses OAR not adjusting? I noticed my AP picked up a new update as well, so maybe that has something to do with it.

I absolutely love the compensations!

Just my OAR seems to stay at 0, and the rest of my tune (timing, LSPI) behaves that way as well.

Thanks for the clarification on TQ Cntrl vs HDFX. I figured it had to be something like that. I did know the HDFX came from the tables, but I've noticed it limits from LSPI tables at the very least.
So I assume the Tq Cntrl one will go further and include things like traction control, ramp-limits and stuff then?

 

I was just about to start a thread on this. Updated to the latest firmware last night. Got a new map from @matt@pandamotorworks and tried the entire drive into work to get the OAR adjusted. I used the same technique I've always used and it didn't budge. I was going to try again after work and if it didn't work reflash the map. But I think I'll wait and see if others have this issue.

 

Just got off the phone with Braden and wanted to clarify a few things to save him the time:

- The FW update is not needed for the new tables to work but it is a good time to make sure the FW is up to date on your AP
- All the previous maps will work as they should. The compensations are not going to change any of their behaviour.
- When enabling the WGDC compensations in the 5-WAY maps (Configure 5-Way WGDC Compensation Mode), make sure that you specify which compensation mode you want in each 5 way map (WGDC Compensation Mode). The 5 way compensation WGDC Compensation Mode under the Wastegate tables is ignored at that point.

Thanks again Braden and COBB for the great development and support!

 

I agree. We have a cold front moving through and this is awesome testing weather. So far I set up 2 slots with the AAT comp and two using the stock PID tables and things are looking pretty darn sweet.

Nice job B!

 

For those with no oar movement are you using slot 2 economy or slot 1?

 

Mine doesn't adjust in either mode.

 

I had issues getting mine to adjust before. I had to brake boost a little to get it to move.

 

Yeah I tried that on my way to work today and nothing changed. Im thinking something isn't right in the file? Hell I dunno

 

I get that... I'm saying I drove 10 or so miles yesterday on it and then 30-something miles to work today and it didn't budge. In the past, I've been able to force it to learn by doing sustained medium load pulls in high gear from a low starting rpm, and in the process, getting it to learn from 0.0 to -1.0 gradually in 2-3 pulls. That isn't working in this instance at all.

 

Did you see you ignition correction adding and holding timing when you where trying to force it?

 

Mine did finally start to adjust. I was unaware of the "Green" reset. I'll keep that in mind for the future!

 

That's good to hear. I will be monitoring the situation! Haha

EDIT: Mine started to move as well. It took about 50 miles of driving for me to see any change. Once I did, I did some medium load 6th gear pulls and it went down to -1.0, but it took several more pulls than it did on the old files.

 

Honestly, I wasn't looking while I was doing it... but I did get it to go to -1.0 today on my way home from work. COBB had mentioned that it was going to take longer because it was a 'green' reset or something like that? It did take longer, but it adjusted. Maybe 75 miles total since I flashed.

 

For mine it seemed like there was probably some sort of mileage / time delay because now I can adjust it as if it were normal.

For me it was a pain in the butt, because my load targets change with my OAR

 

For mine it seemed like there was probably some sort of mileage / time delay because now I can adjust it as if it were normal. For me it was a pain in the butt, because my load targets change with my OAR

Ahhhh that sounds tricky. I suppose one of these days I'll get around to learning how to tune for load. That's the way I'd like to do it, but I don't have a clue where to start and I don't have a ton of time unfortunately

 

Its not too hard. I just like the consistency it gives me, especially in ND. I can tune in 100*F and be sure that when it hits -20*F this winter that I won't overboost and shoot a rod (assuming the roads will be clear enough to boost in the winter ). I believe my pro-tune from @Alex@Stratified also performs similarly, in that unlike OTS maps, it has a nice load cap on it.

The Load cap by OAR is pretty easy to do with the LSPI tables. You set the High Mid Low up the way you want, and then use the LSPI OAR value to basically blend between the tables based on your OAR. I do this in my own table because I want the extra insurance if I get a bad batch of gas, even if it means I have to drop 20-30hp to do it. At the end of the day, this is my DD, and I can't have it blow up on me

So my own tune varies both Timing and Load with OAR. Its more things for me to have to tune, but I've kind of been doing it one revision a day, and making tweaks as I go.

 

Its not too hard. I just like the consistency it gives me, especially in ND. I can tune in 100*F and be sure that when it hits -20*F this winter that I won't overboost and shoot a rod (assuming the roads will be clear enough to boost in the winter ). I believe my pro-tune from @Alex@Stratified also performs similarly, in that unlike OTS maps, it has a nice load cap on it. The Load cap by OAR is pretty easy to do with the LSPI tables. You set the High Mid Low up the way you want, and then use the LSPI OAR value to basically blend between the tables based on your OAR. I do this in my own table because I want the extra insurance if I get a bad batch of gas, even if it means I have to drop 20-30hp to do it. At the end of the day, this is my DD, and I can't have it blow up on me So my own tune varies both Timing and Load with OAR. Its more things for me to have to tune, but I've kind of been doing it one revision a day, and making tweaks as I go.

I'll have to enlist your assistance when I get around to fooling with it. My original plan was to have a separate tune for the "winter blend" fuel we get here in Chicago during the cold months. Lower boost, mild ignition, etc... Being my DD as well, but also living in Chicago for 30 years, I know I'm not going to be boosting its brains out in the winter anyway. But if I can incorporate everything I want into one map, I may shoot for that.

 

This is reference to the OTS 91 tune v204, did anyone else notice less boost? I only drive it for a few miles, but it seems it's barely reaching 21psi. Before v203 I could get 24psi no problem. Any thought?........

https://www.facebook.com/estercost

 

Having hte same issue. Used to hit 22.5 easy but now can only do 21.5 max. Not a big deal, but would like to understand what is causing this. Hvaen't really spent any time to figure it out yet.

 

Braden is there any chance we can get some logging monitor "packages"? For example 5 user-defined monitor sets that can be quickly selected . Maybe even a similar function for the AP dashboard. It would be really nice to be on the road and log my fuel monitors on a wot run and then conveniently log VE on the highway during the same drive without excessive and technically illegal playing with my AP to set it up.

 

It's a highly requested feature and is on our development list. There is no ETA at this time however.

Cheers,
Braden @ COBB

 

Me thinks something it's wrong with the alpha I loaded today.

 

Please revert to release FW as the alpha site is generally reserved for feature testing. In this case the new FW is for a very specific use case and should not be used on properly working V3's right now.

Typically we would post more mass use updates to BETA but had others posted during the testing session we offered. I'll have the post updated shortly to reflect the status of the Faw.

Cheers,
Braden @ COBB

 

Firmware 8844?