Pocketlogger Problems

[sp00ln]

I've been using my pocketlogger for years, and it's been great. However, recently I've been having troubles with it connecting to my ECU via OBD-II. It started slowley, every-so-often (where I couldn't connect to the ECU for the life of me), but now I cant even connect at all. It just sits there in "waiting for connection" mode. I tried searching, but I couldn't find anything usefull.

Are there any pocketlogger problems that anyone is aware of? Updates for the software? I dont think it's a cable/palm connection problem because if I press the hotsink button, it immidiatly goes into hotsink.

Anyone know what's going on, or any possible remedies???

 

[olmytsi]

You have to adjust the byte timing so that you get the best speed possible. You can find the info here under "Byte Timing" http://pocketlogger.com/instructions/quickstartobd2.html

 

[sp00ln]

I'll try the again, and I'll get back to you. I havent changed anything, it's just been getting worse... and finally stopped working. Weird :\

 

[olmytsi]

Mine did the same thing several times across the years and that's what fixed it every time.

 

[sp00ln]

I tried last night... it just starts feezing. :\

 

[olmytsi]

What do you mean it starts freezing?

 

[spyderturbo007]

You may want to do a hard reset on the Palm, unless you have a bunch of other data on there. Then reload the program and DTC database. Make sure that you don't use your last hotsync, because that might be the files that are corrupted.

If not, I have been experiencing a similar problem with my palm and I believe that it is tied to the cable I have in the car. Have you tried moving the cable when the palm is trying to connect. I'm talking about the part that connects to the palm and not the OBD-II port side.

Good luck

 

[sp00ln]

Yeah, I've moved the parts that connect to both the OBD-II and palm itself, and it *seems* I get the best results when I mess with the OBD-II side - the palm side seems secure, and a good attachment. Could something be wrong with my cable/obdII connection?

How would I do a "hard reset" on the palm? The button on the back that you push down with a pin? I've tried that, but it didn't erase any data.

What I ment by freezing is that when I did the byte adjustment, you know, where it goes by itself and lowers the rate until an error occurs, but it just freezes. The time on the test will stay at 5 seconds, then jump to 30, then not go beyond that.

The only thing I used my palm for is to datalog. I'll try to delete everything on the palm and re-load pocketlogger.

 

[MaNGiNa24]

I was having that same issue on my M100, then when I upgraded to my T1 it wouldn't work at all.