ok, so i have the and does pocketlogger, and it connects and datalogs and works fine, except for when a cel is tripped for whatever reason. if the cel is on, the pocketlogger will not stay connected. it will connect for a split second, i'll be able to see the cel code, and it will immediatly lose the connection. it does this for as long as the cel is on, which is really annoying, b/c that's one of the main reason for having the logger. as soon as i reset the ecu, or the cel goes off, it connects again like normal w/ no problem. while trying to get it connect when the cel is on, i've tried all different packet/byte timing combinations. i've reset them, put them both at both extremes, everything. nothing works, and i'm really getting frustrated. i've even talked to the guys at pocketlogger, who are pretty cool, and they have never heard anything like this, and couldn't give me any help w/o seeing the car. has anyone else had this type of problem? any ideas? i'm gettin' really pissed at this thing. i've got no idea.

Try it with the car "ON" but not started. Ie, the key position you're in immediately after turning the starter. My datalogger will only reset CEL's when the motor is not running.

You may need a new cable too, try using someone else's cable with your palm and see if that works better.

hmmm, i thought i tried that, but i'm not sure. i'll have to try it again. does yours also not connect when the engine is on and the cel is on?

i can't imagine it being the cable, b/c it works fine when no cel is on

The reason I mention the cable is that it has electronics in it. Sounds like one of the resistors might be out of tolerance and at 11v it operates fine, but at 13v or something with the car on, it breaks.

If you have a PC datalogger, it's the grey 9pin side that has electronics, not the big red side. Not sure about configuration of Pocketlogger, but I know most intermittant electrical problems are cabling related.

oh ok, guess i'll have to talk to the pocketlogger guys again. thanks

We had a 97 NT Talon come down to see if we could do anything about this. We could not duplicate your problem. I would try the logger on a different car or swap ECUs. You can almost immediately cause a CE light (for testing) if you disconnect the MAP sensor.

What we found is with the car running, (it came with a CE light on already), the logger connected fine and displayed the errors. It stayed connected. When we tried to clear the error codes, the ECU "hung up" the connection. A connection could not be established again until we cycled the ignition. At that point, the errors were gone.

We caused a CE light by pulling the MAP sensor and with only the ignition on (car not running), we were able to retrieve the code and the logger stayed connected. We then tried to clear the errors and it clear the error and stayed connected. All seemed normal.

This was all done on an m100 with the default delay values.

If you can try the logger on another car, you can eliminate either a problem with the ECU or a problem with the logger.


Regards,
Mike Montalvo
digital tuning, inc.
www.pocketlogger.com

BTW, that was MY 97 which, conveniently, came with a blatant misfire, a small EVAP leak and a massive EVAP leak.
PocketLOGGER said misfire in cyl 2, I switched the plug wires, drove to school, got another CEL while the car was running, came out to be misfire cyl 3 (I just swapped those two in the middle), and basically narrowed down my problem to crappy plug wires.
I am a believer in this thing and can't wait to get one myself.
Thanks Mike (and John for introducing me to it) :thumbsup

hey mike, thanks for posting some info. ok i'm going to try and use the logger on another car and see if i can replicate the problem. i just have to find a compatible car and trip the cel.

is it possible that anything else(maybe other programs on the palm, or other apps, settings, etc.) could be messing up the interfacing at all? i have palm Vx .

I think that has happened to my car on the logger too. Cycling the igntion seemed to work. I also use the M100..otherwise, the logger works fine, and I know the ECU is fine..i can get up to 17 samples a second on my car without any errors..

i had to have cycled the ign a good 10 times :P w/ no luck. i might have to just wait till the east coast shootout to test the logger on another 2gnt.

You dont have to test it on another 2gnt to rule out the logger.

Here is a list of some compatible cars.

http://pocketlogger.com/prod/obd2speed.php