P2610 PCM internal engine off timer performance
 

Just got this code after driving around to let my ECU settle after an AP reflash.

Put on the Cobb TIH last night, this morning flashed the Stage 1 SF + TIH 93 BTv102 map after updating my firmware for the Beta.

I did a search and its PCM internal engine of timer performance, searched the trouble code on here and didnt find anything.

Anyone heard of this?

I would contact the COBB support team.

Check this out----------

The timer may latch if the batteries have been disconnected and then reconnected. The timer may also latch during reprogramming. The check engine light won't turn on until the test for the performance of the timer has failed 2 times in a row...so immediately after you reprogram or reconnect the batteries everything will seem OK. 2 keys cycles later you will know if the timer needs to be unlatched.



It is a timer in the ECM that keeps track of the number of seconds that the ignition switch has been off. Your timer is latched and not functioning so the code has been set. With the ignition off, remove both of the ECM connectors and leave them off for at least 1 minute. Then replace them making sure to seat them carefully and completely. If you have a scanner, you can now clear the code and the light will stay off. If you don't have a scanner to clear the codes, the code will clear itself after 3 ignition cycles.

Thanks man!

I figured it may have had to do with the harness. I had to remove the battery tray and ECU to do the TIH install.

I cleared to code and Ill do some key cycles to see if it comes back.

Well Shit.

Now im getting P0096, P0111, P2183 in addition to the P2610 now.

I disconnected and reconnected the ECU harness and cleared the codes

Go to the Cobb Forums and post. They're usually pretty quick with support.

Mazdaspeed3

lmao. i just had the same exact issue after i just updated the firmware and added on the FFS and LC. so far i just cleared the codes with the AP, and they haven't gone on again. if they come back on imma reset battery n go back to the update before the beta until this is figured out

Popped up again

Mine did too yesterday when I was leaving the fire station.

I just reflashed back to a v101 map.

I cant get my AP back to the last non-beta release though

I saw ur post on Cobb tuning. Hopefully they get back to us quick. I called Friday and let them know. They took ny name and number and said if they have info they will reach me

Are you staying on the V102 Beta maps or going back to the V101 like I did?

I could give a flying fuck about launch control

Yea iono what I'm going to do. What map are u using? Since the car runs fine I'm tempted to just leave it and keep clearing the code. I just like the ffs

I just got this code this morning also, any updates on fixes?

Dunno mine went away with the roll back to the V1.01

Weird stuffs. @Admin, can we move this thread to the Genpoo troubleshooting section?

Just to be curios, how long did you got the CEL after you reflashed?.....

had P2006 after reflashing to Stage2 on V101. Code went away but I'm still listening the a kwick kwick noise when engine starts cold. Same noise I got the first day CEL came up. Looking forward to get that light up again so I can take it to the dealership Because Mazda has a TSB on P2006.

FYI: After I went back to the stage1 map that was runing fine before, CEL came up. I have a thread in the troubleshooting section on this...

After going back to stock, light was off and I reflashed the stage2 V102 and it seems to be doing it for me.

I would get the CEL after 3 or 4 key cycles after the flash, which I have read is a common time for them to pop up.

I did install the Cobb TIH at the same time so I did remove the battery and ECU. My ECU connections are locked and tight and have no noticable boost leaks.

I may try to go back to the Beta maps this weekend and see if it resurfaces.

Same here. I'm getting 2183 and 2610 with the v102 maps. I clear the codes with AP and the codes keep coming back after I start the car three or four times. I'm back to v101 maps with no codes. The only way I can have LC & FFS without codes is to leave AP manager on the latest non beta update. Update ATR to the newest beta update. Then load a v101 map on ATR, enter my MAF correction and LC & FFS settings, save that map, drag that map to AP manager and then reflash my car. I don't notice any difference between v101 and v102 maps. Is there a difference besides faster datalog rates?

Bertrand is the first 2010 Ive seen with these issues. Everyone else that has posted with problems has had a 2011.

im goin back to the 1.01 maps because i think its the same exact thing. you can open up 1.01 map and save it with LC/FFS as stated before.

Ok, so I just tried to run v102 again one last time . Now there's four codes 0111,2245,2183 and 2610. Not trying this anymore till Cobb says there's some kind of fix.

Didnt get the 2245 code but I had the other 3.

I had this exact issue with the beta AP upgrade with FFS and LC. I rolled the upgrade back and reflashed back to the non-beta map. It have had no issues sice. It looks as if Cobb needs to find a gremlin.

Cleared code 2610, and its back.

In having this issue on 1.01 and 1.02 maps. As long as this cel isn't dangerous idc ill keep clearing it until they fix this

Yeah, i started getting this p2610 when I started using the new 1.02 maps/atr update, so I'm sure it has something to do with that. I love the FFS, so I'll just keep clearing the code till they come up with a fix.

i have the same problem with same codes but car feels fine :/

I drove 50 miles with the 102 map and my LTFT's never settled down. With the old 101 maps they always settled by 20 miles. Fuck the 102 maps till they get it fixed. I'm not going wot with the ecu freaked out and throwing four codes. FFS works fine with 101 maps as long as you save them with the beta ATR firmware.

So it seems the problem is the beta upgrade to the AP firmware and not the Beta upgrade to computer race program or the LC/FFS feature. Maybe the higher sampling rate is the culprit? Either way I will wait for the fix.

damn i just updated my shit to 102 yesterday and got 2 codes today i was on stage 2 101 and went to the stage 2 102 and car felt better overall imo soon as these codes popped up i didnt know wtf they were so i flashed to stage 1 101 now it feels sluggish again but no codes, glad i ran into this thread

^punctuation= good

i don't believe its the maps causing this, i believe its the firmware. i'm using 101 map on updated firmware with lc and ffs, and i still get the fucking CEL daily. annoying as fuck, i called cobb about it and they said they haven't heard anything about it (they took my name and number), i suggest you guys give them a call and just let them know that its more than one person with this issue, so they can get this shit resolved.

You have same symptoms as me. I posted in the trouble shooting section about P2600.

After going back to 101 it's seems to have settle. But I have a kwick kwick no ice at cold starts

Phone + swype = fail



guess I'll email them tomorrow, we need to get more people to contact them though

The only codes I threw were p2610 & p2183 but I reflashed right away

I posted a link to this thread over at the Cobb forum. Pretty sure they'll see it.

http://www.cobbforums.com/forums/sho...irmware-update

yeah i just ran into cobb in another thread as well and posted a link to this one so he should stop by

same thing, got those 4 codes last night, i was running on v102 with lc/ffs enabled. (FFS is awesome!) I reflashed the v101 back this morning that I had prior to all the beta updates. will keep that on till this is figured out, i think i can live without lc/ffs for a little while lol.

more people are coming out now like rape victims, so its a matter of time now before something gives

If you guys can catch one them when they are in the active user section, pm them and link to this thread.

There are so many q's and tuning threads, they may miss it.

im tellin u, just give them a call directly. lot easier and then im sure they will be aware.

Wierd, Ive had no issues at all, but I have not enabled FFS.