COBB AccessPoint v3 and 997.1TT - install times, problems, notes, etc
COBB AccessPoint v3 and 997.1TT - install times, problems, notes, etc
I just got an AccessPoint V3 from Cobb, after doings research but one of the things I could not find was "how long" each stage of the install would take (on a 997.1TT), there are reports of 30 minutes to 5 minutes, so I figured I would time it for my car. Your times might vary but at least you have a rough guideline.
From the install actually starting to backup the stock ECU :
The backup of the factory ECU was : 6:04 -- immediately gets a CEL error of PSM failure (but its ok)
The flashing of the stage0 map was : 7:16 -- this includes key OFF and counting to 30 seconds before key ON
The reset of the ECU after flashing : 1:16 - CEL errors for several devices failing, PTM, PSM, ABS, etc (also ok ... if not a little unnerving)
The 2nd reset of the ECU finalizing : 2:08
Total 16:47
Problem/Note: When I first got the AP I hooked it up to the computer and it had the OTS maps on it already. But there was a firmware update. (from 1.7.3.0-18814 to 1.7.3.1-16388)
After I did this update which reported "successful" I could no longer see any maps on the AP. Also, when I tried to load in downloaded maps from Cobb it would say "transfer 0 files" and nothing would transfer.
I contacted Cobb and they said this was normal and that when you go to install the AP in the car it will then see the OTS maps; which it did! After the AP installed, I was then able to see all the maps again in the AP Manager. That was a bit weird!
Problem: After the install of the Stage0 map, the fuel gauge would read 0 (like absolute 0, right off the scale) even though I had 1/4 tank. Searching, I found a 6speed article about others having the same problem.
If you have less than 1/2 tank (under the float amount) and the ECU resets, its drops to 0 and needs to re-learn. Easiest way around it is to fill up, which fixed my fuel gauge right away. Probably being full before the install would have avoided it completely?
Problem: This one is a bit annoying, since I was talking to Cobb about my 997.1 and asking about the "Auto On/Off" feature, and they said it works fine. But when I install the AP I could not see the feature at all, so I contacted Cobb again and they said "oh yeah, its not supported on Porsche" This was one of my concerns because I did not want to plug/unplug or power on/off the unit every time I got in/out of the car, and I considered the auto off a MUST have. Cobb has said that they would update their site to explicitly say that the Porsche Auto On/Off was not supported, but a little LATE for me, be fore-warned. I know many people after they flash stage1 or 2, don't even leave the unit connected, but for me right now, because its new and I want to see the gauges, I want to leave it connected.
I will probably add/expand on this article as I run into things of note, or problems, feel free to add your tid-bits, it could very well help the next Cobb user.
From the install actually starting to backup the stock ECU :
The backup of the factory ECU was : 6:04 -- immediately gets a CEL error of PSM failure (but its ok)
The flashing of the stage0 map was : 7:16 -- this includes key OFF and counting to 30 seconds before key ON
The reset of the ECU after flashing : 1:16 - CEL errors for several devices failing, PTM, PSM, ABS, etc (also ok ... if not a little unnerving)
The 2nd reset of the ECU finalizing : 2:08
Total 16:47
Problem/Note: When I first got the AP I hooked it up to the computer and it had the OTS maps on it already. But there was a firmware update. (from 1.7.3.0-18814 to 1.7.3.1-16388)
After I did this update which reported "successful" I could no longer see any maps on the AP. Also, when I tried to load in downloaded maps from Cobb it would say "transfer 0 files" and nothing would transfer.
I contacted Cobb and they said this was normal and that when you go to install the AP in the car it will then see the OTS maps; which it did! After the AP installed, I was then able to see all the maps again in the AP Manager. That was a bit weird!
Problem: After the install of the Stage0 map, the fuel gauge would read 0 (like absolute 0, right off the scale) even though I had 1/4 tank. Searching, I found a 6speed article about others having the same problem.
If you have less than 1/2 tank (under the float amount) and the ECU resets, its drops to 0 and needs to re-learn. Easiest way around it is to fill up, which fixed my fuel gauge right away. Probably being full before the install would have avoided it completely?
Problem: This one is a bit annoying, since I was talking to Cobb about my 997.1 and asking about the "Auto On/Off" feature, and they said it works fine. But when I install the AP I could not see the feature at all, so I contacted Cobb again and they said "oh yeah, its not supported on Porsche" This was one of my concerns because I did not want to plug/unplug or power on/off the unit every time I got in/out of the car, and I considered the auto off a MUST have. Cobb has said that they would update their site to explicitly say that the Porsche Auto On/Off was not supported, but a little LATE for me, be fore-warned. I know many people after they flash stage1 or 2, don't even leave the unit connected, but for me right now, because its new and I want to see the gauges, I want to leave it connected.
I will probably add/expand on this article as I run into things of note, or problems, feel free to add your tid-bits, it could very well help the next Cobb user.
I also have a Durametric Pro and was worried that making coding changes while the AccessPort was installed to the car would create some type of conflict, but it seems you can use the Durametric Pro to code a change (which persists after a car restart) after you have installed and bounded the AccessPort to your car.
More Detail: Once I installed the Stage0 map, I removed the AP from the ODB2 port and installed the Durametric Pro. First I had it look at the ECU engine and read it, and it read it fine, no complaints. I then went to the "alarm" gateway/component and in "coding" section, it read and listed all of the codes. I then changed one "require brake pedal to start engine" and set that to inactive. I then cycled the car and started it (without the brake pedal) and plugged in the AccessPort and it came up normal and did some datalogging and looked at gauges, and it was all good. Now I know this is NOT an extensive test given the number of parameters you can change on the Durametric but at least its some guidance that it will probably work for all.
More Detail: Once I installed the Stage0 map, I removed the AP from the ODB2 port and installed the Durametric Pro. First I had it look at the ECU engine and read it, and it read it fine, no complaints. I then went to the "alarm" gateway/component and in "coding" section, it read and listed all of the codes. I then changed one "require brake pedal to start engine" and set that to inactive. I then cycled the car and started it (without the brake pedal) and plugged in the AccessPort and it came up normal and did some datalogging and looked at gauges, and it was all good. Now I know this is NOT an extensive test given the number of parameters you can change on the Durametric but at least its some guidance that it will probably work for all.
Last edited by IvanRaide; Sep 3, 2020 at 06:00 PM.
I decided to update this with the times to UNINSTALL the Cobb:
Start: uninstall : 8:19.92
Off/On - Reset ECU : 1:08.71 -- note! you will get PSM, PTM, ABS errors again -- but its all fine
(total time with 30 seconds Off/On) - 10:41
Start: uninstall : 8:19.92
Off/On - Reset ECU : 1:08.71 -- note! you will get PSM, PTM, ABS errors again -- but its all fine
(total time with 30 seconds Off/On) - 10:41
Thread
Thread Starter
Forum
Replies
Last Post




