[Ænema]

Originally Posted by ihc95

Yes I did. I actually drove a lot before installing the AP to make sure the battery was charged. Oil temps were around 230-240. Why do you think there was smoke?

White smoke is coolant, Bluish smoke is oil and Black smoke is fuel. If it was, in fact, WHITE SMOKE then you have coolant that is being burned.

[VNeBLOB42]

Originally Posted by benzy89

Did you let the engine warm up (oil temps in 200* area) before you started ripping on it?


I really hope so

LOL,

To piggyback off your post, with stock oil cooler, is it normal to see 240 average temp with aggressive tune? While driving normal with 90 deg. Temps. It seems to be normal to me?

[skinrock]

Originally Posted by VNeBLOB42

LOL,

To piggyback off your post, with stock oil cooler, is it normal to see 250 average temp with aggressive tune? While driving normal with 90 deg. Temps. It seems to be normal to me?

Mine hovers around 230-250 depending on ambient temps and driving style.

[VNeBLOB42]

Originally Posted by skinrock

Mine hovers around 230-250 depending on ambient temps and driving style.

+1. 250 when I am on an aggressive cruse. 230 with cooler air. Thanks for the confirmation.

[Ænema]

Originally Posted by VNeBLOB42

Lol, there has been people getting banned, so by the post doesn't necessarily mean noob.

Could be a returning enthusiast.

No sir, new to e90. I have, however, been a long time N54tech member. That place tends to be JB heavy, so I'm just widening my horizons a bit. I am very experienced Cobb user, though.

[benzy89]

Originally Posted by ihc95

Yes I did. I actually drove a lot before installing the AP to make sure the battery was charged. Oil temps were around 230-240. Why do you think there was smoke?

You said that a friend had mentioned a poof of white smoke coming from your exhaust during a pull.

Originally Posted by VNeBLOB42

LOL,

To piggyback off your post, with stock oil cooler, is it normal to see 240 average temp with aggressive tune? While driving normal with 90 deg. Temps. It seems to be normal to me?

240-250 is completely natural & healthy for a street car. For a track car, you might want it closer to 220 to avoid over heating & Limp Mode

Originally Posted by Ænema

No sir, new to e90. I have, however, been a long time N54tech member. That place tends to be JB heavy, so I'm just widening my horizons a bit. I am very experienced Cobb user, though.

Not surprised, N54 Tech was started by Terry & it's where he posts all his tune updates.

[ihc95]

Originally Posted by benzy89

You said that a friend had mentioned a poof of white smoke coming from your exhaust during a pull.

No you misunderstood. I was asking why do you think I have smoke? Not whether or not I had smoke.

[Mangler]

two logs (every parameter imaginable), major WG dump 5700rpm. Discuss

T

[dinkoh]

Anyone running Stage2+ w/o upgraded intake? I'm just wondering if its really necessary... reading posts that an upgraded intake does very little.

[VNeBLOB42]

Originally Posted by dinkoh

Anyone running Stage2+ w/o upgraded intake? I'm just wondering if its really necessary... reading posts that an upgraded intake does very little.

One may argue that DCI sucks too much heat. Never really tested it myself, seen some post and it really didn't make a difference from drop in to DCI. I would do a drop in at the very least. Car needs to breath efficiently.

[cstavaru]

Hi,

I tried to install Cobb AccessPort Manager in Windows 8 and the driver did not install successfully. Any solutions ?

Also, is there a way to find out the ECU type without first installing (marrying) the AccessPort ?

Below is the driver installation log that I found in the driver folder:

15:39:32 -- LOG START --

15:39:32 INF File: C:\Program Files (x86)\AccessPORT\AccessPORT Driver\Cobb_OBDFTDI.INF

15:39:32 Setting SuppressNewHWUI registry value to try and suppress messages during XP install...

15:39:32 Processing driver CLEANUP for Hardware ID: USB\VID_1a84&PID_0212

15:39:32 Deleting OEM*.INF files that contain the above hardware ID...

15:39:32 Processing driver INSTALL for Hardware ID: USB\VID_1a84&PID_0212

15:39:32 Pre-installing driver from: C:\Program Files (x86)\AccessPORT\AccessPORT Driver\Cobb_OBDFTDI.INF

15:39:33 Driver pre-install result: FAILED, e000022f

15:39:33 Driver update result: FAILED, e000020b

15:39:33 Device not found when attemping to updating driver.

15:39:33 Restoring SuppressNewHWUI registry value...

15:39:33 -- LOG END --

15:39:33 -- LOG START --

15:39:33 INF File: C:\Program Files (x86)\AccessPORT\AccessPORT Driver\AP_20.inf

15:39:33 Setting SuppressNewHWUI registry value to try and suppress messages during XP install...

15:39:33 Processing driver CLEANUP for Hardware ID: USB\VID_1a84&PID_0121

15:39:33 Deleting OEM*.INF files that contain the above hardware ID...

15:39:33 Processing driver CLEANUP for Hardware ID: USB\VID_1a84&PID_0120

15:39:33 Deleting OEM*.INF files that contain the above hardware ID...

15:39:33 Processing driver CLEANUP for Hardware ID: USB\VID_1a84&PID_0210

15:39:33 Deleting OEM*.INF files that contain the above hardware ID...

15:39:33 Processing driver CLEANUP for Hardware ID: USB\VID_1a84&PID_0211

15:39:33 Deleting OEM*.INF files that contain the above hardware ID...

15:39:33 Processing driver CLEANUP for Hardware ID: USB\VID_1a84&PID_0213

15:39:33 Deleting OEM*.INF files that contain the above hardware ID...

15:39:34 Processing driver INSTALL for Hardware ID: USB\VID_1a84&PID_0121

15:39:34 Pre-installing driver from: C:\Program Files (x86)\AccessPORT\AccessPORT Driver\AP_20.inf

15:39:34 Driver pre-install result: FAILED, 2

15:39:34 Driver update result: FAILED, 2

15:39:34 Processing driver INSTALL for Hardware ID: USB\VID_1a84&PID_0120

15:39:34 Pre-installing driver from: C:\Program Files (x86)\AccessPORT\AccessPORT Driver\AP_20.inf

15:39:34 Driver pre-install result: FAILED, 2

15:39:34 Driver update result: FAILED, e000020b

15:39:34 Device not found when attemping to updating driver.

15:39:34 Processing driver INSTALL for Hardware ID: USB\VID_1a84&PID_0210

15:39:34 Pre-installing driver from: C:\Program Files (x86)\AccessPORT\AccessPORT Driver\AP_20.inf

15:39:35 Driver pre-install result: FAILED, 2

15:39:35 Driver update result: FAILED, e000020b

15:39:35 Device not found when attemping to updating driver.

15:39:35 Processing driver INSTALL for Hardware ID: USB\VID_1a84&PID_0211

15:39:35 Pre-installing driver from: C:\Program Files (x86)\AccessPORT\AccessPORT Driver\AP_20.inf

15:39:35 Driver pre-install result: FAILED, 2

15:39:35 Driver update result: FAILED, e000020b

15:39:35 Device not found when attemping to updating driver.

15:39:35 Processing driver INSTALL for Hardware ID: USB\VID_1a84&PID_0213

15:39:35 Pre-installing driver from: C:\Program Files (x86)\AccessPORT\AccessPORT Driver\AP_20.inf

15:39:35 Driver pre-install result: FAILED, 2

15:39:35 Driver update result: FAILED, e000020b

15:39:35 Device not found when attemping to updating driver.

15:39:35 Restoring SuppressNewHWUI registry value...

15:39:35 -- LOG END --

Thanks !

[jetbill]

Originally Posted by VNeBLOB42

One may argue that DCI sucks too much heat. Never really tested it myself, seen some post and it really didn't make a difference from drop in to DCI. I would do a drop in at the very least. Car needs to breath efficiently.

Running an AFE DCI (with cobb st1 agg) with my IAT above 140 and ambient is around 93 (florida).

It's a black car, I do suspect the factory airbox with drop in would be my best bet to help lower IAT and reduce timing pulls.

[VNeBLOB42]

Originally Posted by cstavaru

Hi,

I tried to install Cobb AccessPort Manager in Windows 8 and the driver did not install successfully. Any solutions ?

Also, is there a way to find out the ECU type without first installing (marrying) the AccessPort ?



Thanks !

Windows 8 huh, Did COBB release AP Manager for Win 8 yet? I thought Win 8 was still under beta?

I think you can get a pretty good idea based upon build date, but that's the best way, just plug in and allow the COBB to connect to your ECU and tell you the ECU Type.

[enrita]

Originally Posted by VNeBLOB42

Windows 8 huh, Did COBB release AP Manager for Win 8 yet? I thought Win 8 was still under beta?

I think you can get a pretty good idea based upon build date, but that's the best way, just plug in and allow the COBB to connect to your ECU and tell you the ECU Type.

+ 1
System Requirements:
Windows: XP 32 (not 64bit), Vista (32 or 64bit) or Windows 7 (32 or 64bit)
OSX: 10.5 or 10.6 (on Intel machines only)

[Ænema]

Originally Posted by cstavaru

Hi,

I tried to install Cobb AccessPort Manager in Windows 8 and the driver did not install successfully. Any solutions ?

Also, is there a way to find out the ECU type without first installing (marrying) the AccessPort ?

Below is the driver installation log that I found in the driver folder:
Thanks !

I've had that issue before. Just try going to Cobb's website and downloading the AP manager from there. It's what I did, however I'm on windows 7 so I can't guarantee that will work for you.

[cstavaru]

Originally Posted by VNeBLOB42

Windows 8 huh, Did COBB release AP Manager for Win 8 yet? I thought Win 8 was still under beta?

I think you can get a pretty good idea based upon build date, but that's the best way, just plug in and allow the COBB to connect to your ECU and tell you the ECU Type.

Windows 8 is final since August 16. You can download a 90-day trial from Microsoft if you want.

I plugged the Cobb into the OBD port and did not find a way to find out the ECU type. There is a section about AccessPort with an information mark where I can see the AP firmware version and it also has a "Vehicle" setting under which a "?" sign appears.

[dinkoh]

Originally Posted by VNeBLOB42

One may argue that DCI sucks too much heat. Never really tested it myself, seen some post and it really didn't make a difference from drop in to DCI. I would do a drop in at the very least. Car needs to breath efficiently.

I'm not sure if drop-in filters makes a difference compared to OEM filter?

[enrita]

Originally Posted by cstavaru

Windows 8 is final since August 16. You can download a 90-day trial from Microsoft if you want.

I plugged the Cobb into the OBD port and did not find a way to find out the ECU type. There is a section about AccessPort with an information mark where I can see the AP firmware version and it also has a "Vehicle" setting under which a "?" sign appears.

You still have giac flashed? That might be the issue.
I would flash it stock first. Some people had issues installing cobb on a non oem flash
Mail cobb

[marv85]

Originally Posted by enrita

You still have giac flashed? That might be the issue.
I would flash it stock first. Some people had issues installing cobb on a non oem flash
Mail cobb

+1

[cstavaru]

Originally Posted by enrita

You still have giac flashed? That might be the issue.
I would flash it stock first. Some people had issues installing cobb on a non oem flash
Mail cobb

I do not intend to install Cobb over GIAC, I have an appointment for stock reflash in 2 days. But I wanted to download the maps and look at the table values in ATR, etc. Right now I'm stuck because I can't install the driver. I emailed Cobb, hopefully they will respond soon.

[ihc95]

Originally Posted by dinkoh

I'm not sure if drop-in filters makes a difference compared to OEM filter?

I had this question a few months ago as well. On a stock car a drop in filter will do next to nothing, if not loose power. However on a tuned car, I say its worth getting. I am not a fan of DCI's at all. Im not saying they dont work, I am personally not comfortable allowing the engine to suck in very hot air. Also, they look so damn ugly and cheap in the engine bay. I am getting a BMS drop in until I buy a full STETT CAI.

[Ænema]

Originally Posted by cstavaru

I do not intend to install Cobb over GIAC, I have an appointment for stock reflash in 2 days. But I wanted to download the maps and look at the table values in ATR, etc. Right now I'm stuck because I can't install the driver. I emailed Cobb, hopefully they will respond soon.

In order to get ATR working you will need to have the AP installed. You will have to connect the AP to the computer when downloading ATR and I'm pretty sure it requires the AP to be married during this process.