CEL came on, not sure if it's the same as the big thread

[kajun]

Yesterday I picked up an OBDII bluetooth connector that had been recommended by another 86 owner - I'd been curious about the connector and the data I could get out of it, so I plugged it in & connected to Torque. Played around with it, checked for error codes (none found), and then went out for a short drive to see how the data logging worked (it didn't work).

When I got back to my house, I noticed the CEL & slip lights were both on (!). Not sure what was happening, I turned off the car & pulled out the OBD transmitter.

This morning, I started the car again for my drive to work, and the CEL is still on. The SL is no longer on, and there's no rough idle, so it doesn't look like the issue people are having in the sticky, but given the timing I'm a little suspicious. The one thing I have noticed is that as the (automatic) transmission drops back into 1st around the 10 mph (15-17km/h) mark, there's a little "stutter" from the transmission. No problems when shifting up, or in any of the other gears, just when slowing to 1st I can feel the gear change.

I'll plug the connector in tonight and see what error code is being reported, but just thought I'd float this while I'm at work to see if anyone has experienced something similar.

Any advice from those around here? I haven't accidentally triggered an error code while using the OBD connector, have I?

[strat61caster]

You could pull the terminals off the battery to "reset" the car if the code isn't something alarming, if there's really an issue it should show up again shortly.

[kajun]

Tried plugging in the OBD connector last night after seeing the code again - couldn't connect for some reason; turned on the ignition, and the light went away. I'll chalk it up as a mystery.

[FRSBRZGT86FAN]

Originally Posted by kajun

Tried plugging in the OBD connector last night after seeing the code again - couldn't connect for some reason; turned on the ignition, and the light went away. I'll chalk it up as a mystery.

Maybe its the issue other members have been having? Most of the connectors have horrible connections due to them needing to be re pinned?

[SkullWorks]

Originally Posted by FRSBRZGT86FAN

Maybe its the issue other members have been having? Most of the connectors have horrible connections due to them needing to be re pinned?

Huh?

Haven't heard of such an issue, is the supposed problem with a certain brands obd2 connector or are you saying some cars are wired incorrectly?

I have been playing with a Tactrix openport 2.0 cable and various software bits mostly logging CAN data. I have on 2 occasions upset the car where it reported it "lost connection to dash module" never had any issues with the cluster though...cleared it and it would never be an issue again...unless i tried accesing the ecu with outdated SSM2 protocol

[FRSBRZGT86FAN]

Originally Posted by SkullWorks

Huh?

Haven't heard of such an issue, is the supposed problem with a certain brands obd2 connector or are you saying some cars are wired incorrectly?

I have been playing with a Tactrix openport 2.0 cable and various software bits mostly logging CAN data. I have on 2 occasions upset the car where it reported it "lost connection to dash module" never had any issues with the cluster though...cleared it and it would never be an issue again...unless i tried accesing the ecu with outdated SSM2 protocol

Well, multiple people complained of the OBDII connector on the cars were wired incorrectly, causing them to lose or get a bad signal when connecting to the car with an OBDII tool or connector. Like on the user Dezoris's car he had a similiar issue:http://www.ft86club.com/forums/showt...ight=connector

[kajun]

Hmm, hadn't seen that thread/issue before. I'll try out the connector on another car and see if it's the connector or the car that's at issue.