Received my Cobb/FSWERKS Accessport v3!

Discussion in 'Fiesta ST EcoBoost™ Tuning' started by McRib 1s Back, Dec 20, 2013.

  1. spangenb

    spangenb Active Member

    Ok Rib here are some fresh pics. I like the option to take the AP down when going to Wal-Mart, etc. There are details on the ProClip parts and the OBD adapter cable in another thread about ProClip stuff.
    uploadfromtaptalk1391290567027.jpg uploadfromtaptalk1391290584567.jpg uploadfromtaptalk1391290602126.jpg uploadfromtaptalk1391290623161.jpg uploadfromtaptalk1391290642246.jpg uploadfromtaptalk1391290653965.jpg
    bryramos, McRib 1s Back and Firesail like this.
  2. Register or Sign in

    Advertisement Sponsor

  3. Firesail

    Firesail Active Member

  4. McRib 1s Back

    McRib 1s Back Well-Known Member

  5. Robert

    Robert New Member

    __V__ likes this.
  6. McRib 1s Back

    McRib 1s Back Well-Known Member

    The car had been running great until Big Willow. As background, I used the 93 map w/100 octane fuel without issue at SoW. The car was fast, really felt great, and had no incidents of any kind (no pinging or reduction in OAR-L either, happily at "-1" the entire day). The little street driving I did with the same setup was great too.

    Update from 2/15 @ Big Willow:

    Fast forward to last Sunday and the car developed an issue pretty early on. The first session was fine, but on my second session, I went into limp-home mode on the ECU. Going into this mode on the track really sucks! For fun, I kept my driving line. It turns out the car is only about 20 seconds a lap slower over the 2.5 miles. :)

    Here's how it happened, twice! Coming around on turn nine, fast into turn one, I brake hard and late, taking the turn at about 75-80 MPH. The ECU alerts at the tail-end of braking in exactly the same place. Code is "P061A No description available". Is that an O2 sensor?

    I was able to reset the ECU and clear the code after the first time, but it happened again in exactly the same spot on the next session.

    This time around, I simply went back to the 91 map. It hasn't happened again, and I ran the rest of the day that way. My car went home with the same map, and there hasn't been a recurrence.

    There's a weird electro-mechanical feel to this problem. Did the hard braking shift something on the car, temporarily, and cause the sensor to have a problem? Did the 91 map really have anything to do with this? Maybe I was just slower with that map and not applying quite the same braking force?

    Thoughts? Thanks in advance!
  7. jariten

    jariten Member

    My friend used to get P061A on a Ram a couple years ago. It had to do with the generated torque not matching the ECU torque or something like that. Limp mode every time. If I remember correctly it was fixed with a PCM update at the dealer.
  8. McRib 1s Back

    McRib 1s Back Well-Known Member

    Thanks, that sounds plausible -- but recall that we're talking about a Cobb/FSWERKs AP and a Cobb map (not a stock OEM map). I fully expect that a new Cobb map will address this. If we only hit this under race/track conditions, it's not an emergency.

    If nothing else, it's another data point about the 93 octane map not being 100% sorted out (and totally understandable). My 93 map is only a "race map" and I run 100 octane with it. I can see getting another true 100 octane map later, but either way I expect that we'll see more development soon -- for all of the maps. We have a small laundry list of niggling bugs...
  9. wash

    wash Active Member

    There are only a hand full of ODMs designing EFI computers or PCMs (power train control module).

    With the amount of re-use business want to do, I'm not surprised that error messages are the same between different manufacturers.

    As far as what's in a Cobb tune, its probably almost entirely different table values and enabling additional functionality built in to the PCM. Neither of those would change error codes.

    It certainly can lead to errors being generated but that's a different story.
  10. McRib 1s Back

    McRib 1s Back Well-Known Member

    Yep, that really is interesting -- it struck me the same way, and I wasn't surprised about the possibility of shared codes between dissimilar makes.

    We're also looking at a corner case here. Normal street driving and spirited canyon runs didn't reveal the problem. I'd like Cobb to comment on this. :)
  11. spangenb

    spangenb Active Member

    This is all the OBD standard. Wouldn't the codes be standardized? I don't know the answer. Just throwing it out there.
  12. McRib 1s Back

    McRib 1s Back Well-Known Member

    There certainly are standard OBD II codes, and I was just stating that the AP read that value without description -- no surprise. I don't have any insight into this code so maybe it really is just a standard code. I'm just hoping it gives Cobb insight into the nature of the issue. Until this is fixed, I won't be using the 93 octane map on a track.
  13. stuntdoogie

    stuntdoogie Active Member

    You shouldve logged it and sent it to Cobb for evaluation.

    Sent from my SPH-D710 using Tapatalk
  14. D1JL

    D1JL Well-Known Member

    From the FiST Service Manual

    P061A - Internal Control Module Torque Performance

    This DTC sets when an error occurs in the PCM.

    Possible Causes:
    Software incompatibility issue
    Damaged PCM

  15. McRib 1s Back

    McRib 1s Back Well-Known Member

    Thanks, Dave. This confirms our suspicion. I don't think I have damage, however. I'm betting that's valid on a stock car.

    My car still feels good on the 91 map. It goes pretty fast, anyhow. :)
  16. D1JL

    D1JL Well-Known Member

    I am sure everything is OK.
    I'll just bet the Cobb 93 needs a little tweak.
    After all you were pushing it harder than I think Cobb tested it.
    Remember they only used a dyno not the repetitive laps that you did.

  17. Irsinn

    Irsinn New Member

  18. spangenb

    spangenb Active Member

    Hi Irsinn. Search the forum for ProClip and you will find my posts with links, part numbers, etc. Let me know if you can't find it.
  19. Irsinn

    Irsinn New Member

    Found it ... Much Grass!

    Nice to see this forum is a bit more civil than some forums for other performance cars I have owned... Thanks to all!
    spangenb likes this.
  20. COBB

    COBB Active Member

    That's a very odd issue! I sent your post to Braden, our calibrator, and I'll see what he can find out.

  21. McRib 1s Back

    McRib 1s Back Well-Known Member

    Thanks -- Braden and I are in touch now. We're working through this and I'll share a meaningful update with the forum later.
    Firesail and __V__ like this.

Share This Page