Accessport performance measurement failure

[jodyr]

I can't get the performance measurement feature on my new Accessport to work with my '16 FiST. Both the 0-60 and 1/4 mile measurement cause the unit to report a crash. I have to unplug and replug the AP to get it to work. I've been working with Cobb support on this, but it's been a week since they escalated my case with no new information. I'm hoping one of y'all may have had the same problem and fixed it.

 

[FiestaSTdude]

I've had that issue too. No idea how to fix it though

 

[jodyr]

I have to report that I'm a bit disappointed at how Cobb Support is handling this. The person I was speaking with said I was being escalated to the Ford team and then crickets. Apparently it's a software bug in the AP OS, but there's no word on a remedy, meaning, I'm presently not getting the full measure of what I paid a good deal of money for.

 

[jodyr]

I was just issued a 10% discount at Cobb with a basic "we're working on it but don't have any kind of timetable as to when it will be remedied." I'd say the 10% discount was better than nothing, but feel a 20% discount is more warranted in this situation when 20% of the functionality of the AP is presently unavailable.

 

[FiestaSTdude]

I was just issued a 10% discount at Cobb with a basic "we're working on it but don't have any kind of timetable as to when it will be remedied." I'd say the 10% discount was better than nothing, but feel a 20% discount is more warranted in this situation when 20% of the functionality of the AP is presently unavailable.

Hopefully they can find a fix. I just want a fully functional Accessport

 

[Clint Beastwood]

I have to report that I'm a bit disappointed at how Cobb Support is handling this. The person I was speaking with said I was being escalated to the Ford team and then crickets. Apparently it's a software bug in the AP OS, but there's no word on a remedy, meaning, I'm presently not getting the full measure of what I paid a good deal of money for.

On the software development and engineering side, you can't just "fix" something like that - they have to do intensive analysis to avoid unintended consequences, with lots of testing in between. Some companies throw out fast update cycles, other companies have slow ones - the fast update cycles tend to then require other fast updates, which require other fast updates, etc. because they introduce new variables without adequate testing. Cobb isn't a shoot from the hip company, they're going to be slow and methodical and release a fairly buttoned down update when they're ready.

Aside from that, the performance metric functionality of the Cobb isn't the main point of the product, it's an accessory provided as a byproduct of the core functionality of the device - as the performance metrics aren't part of the core functionality, it's bound to be low priority overall. It's a far cry from 20% of the functionality of the AP, it's more like having one of your car's floormats being ripped.

 

[jodyr]

Thanks for that information, Clint. I was maybe overstating the importance of the measurement feature to a degree, but to me it's more than a tear-in-the-floormat-level annoyance. It's presented as a core feature in the UI, after all. That's where I got my 20% figure from.

 

[Clint Beastwood]

Thanks for that information, Clint. I was maybe overstating the importance of the measurement feature to a degree, but to me it's more than a tear-in-the-floormat-level annoyance. It's presented as a core feature in the UI, after all. That's where I got my 20% figure from.

I get you - it's just... I don't think anyone ever has purchased an access port for the performance metrics functionality. We all know why we bought them

Not saying I don't want all of my accoutrements to work correctly, but as long as it flashes the flashies and zooms the zoomies, the reason we bought the things is intact.

The software development cycle is a beast, and if they are trying to maintain 50 state compliance, I'm not sure, but they probably have to recertify after each major revision or something.

 

[dhminer]

Not an exact solution but if you do a data log and floor it, you can see the acceleration times if you graph time on one axis and speed on the other

 

[jodyr]

I was contacted by Cobb support today and asked to update my AP to a beta version of the firmware, v1.7.4.2-20221. I'm happy to report that this fixed the problem and I'm able to perform the 0-60 and 1/4 mile measurements now.

 

[1.6]

The fix is now out of beta and a part of the main update fork. Its cool that they listened and fixed the issue!

Firmware Update 1.7.4.2-20372:

Date: 02/03/2022

New Features:

New In-Use Performance Tracking feature now located under the Troubleshooting menu. This feature displays emissions related monitor counters.
Bug Fixes:

Fixed an issue that would sometimes cause the 0-60 and 1/4 mile Performance menu to not work correctly.

 

[FiestaSTdude]

The fix is now out of beta and a part of the main update fork. Its cool that they listened and fixed the issue!

Firmware Update 1.7.4.2-20372:

Date: 02/03/2022

New Features:

New In-Use Performance Tracking feature now located under the Troubleshooting menu. This feature displays emissions related monitor counters.
Bug Fixes:

Fixed an issue that would sometimes cause the 0-60 and 1/4 mile Performance menu to not work correctly.

I updated my Accessport and the 0-60 and 1/4 mile feature now works!

Now can somebody explain why my 0-60 times are so bad? I guess all seasons and torque in first gear don't play well together lol

 

[1.6]

I updated my Accessport and the 0-60 and 1/4 mile feature now works!

Now can somebody explain why my 0-60 times are so bad? I guess all seasons and torque in first gear don't play well together lol

Yup... all that torque puts you in spin city.

Im not sure how accurate the 0-60 is on the AP but some things you can try are:

Temporarily increase the red line so you can hit 60 in 2nd gear, temporarily decrease air pressure in the front tires until they hook more consistently, remove the spare tire and jack and try doing runs with and without launch control to find what works for you.

You can also try flat foot shifting but that might blow something up so try at your own risk lol.

 

[FiestaSTdude]

Yup... all that torque puts you in spin city.

Im not sure how accurate the 0-60 is on the AP but some things you can try are:

Temporarily increase the red line so you can hit 60 in 2nd gear, temporarily decrease air pressure in the front tires until they hook more consistently, remove the spare tire and jack and try doing runs with and without launch control to find what works for you.

You can also try flat foot shifting but that might blow something up so try at your own risk lol.

Thanks for the tips. It's not like this is a drag car, I just think it's fun to see how fast I can get.
Does anyone know how accurate the Accessport 0-60 measurements are? I was wondering about that as well.

 

[LiLfieSTa]

just use your head =] who needs the AP?

i avg 5.8 secs to 60 almost all the time in my head.
trust me i know, ive been counting since preschool.

 

[M-Sport fan]

I am curious to know an accurate 0-60 for a tuned, 300+ to the wheels S280 or bigger, with limited slip and sticky tires (200 or 100 tread wear, but NOT drag slicks/radials).

Just how far below 5 seconds could that be, even with launch control, and flat fott shifting?