lookinfor400hp
15+ Year Contributor
- 102
- 0
- Sep 28, 2005
-
Jacksonville,
Florida
#1- I searched and found nothing on this. Everything seems to be 2G related.
#2-Ok , so I have tried all three of my Palms (old Palm IV, and two M130's)
Still unable to log with my new pocketlogger setup, it displays connection error. I have used two different serial cables for the M130's with the same error (one eBay cable and one I bought through Pocketlogger). They hotsync just fine, but still unable to log. Could this be a data port problem?
Keep in mind my IV with mmcd worked fine before I switched to Pocketlogger. Short of attempting to reload mmcd and trying it that way I don't know what else to do.
How can I check my diagnostic port to see if its the culprit? Is this something that anyone else has gone though?
Dan
FYI
I just swapped in my working non-EPROM ECU with the same results. So I believe I can rule out the ECU as a cause.
Any ideas where to look. I have been digging though my factory manual with no luck as of yet where the diag port might be faulty.
#2-Ok , so I have tried all three of my Palms (old Palm IV, and two M130's)
Still unable to log with my new pocketlogger setup, it displays connection error. I have used two different serial cables for the M130's with the same error (one eBay cable and one I bought through Pocketlogger). They hotsync just fine, but still unable to log. Could this be a data port problem?
Keep in mind my IV with mmcd worked fine before I switched to Pocketlogger. Short of attempting to reload mmcd and trying it that way I don't know what else to do.
How can I check my diagnostic port to see if its the culprit? Is this something that anyone else has gone though?
Dan
FYI
I just swapped in my working non-EPROM ECU with the same results. So I believe I can rule out the ECU as a cause.
Any ideas where to look. I have been digging though my factory manual with no luck as of yet where the diag port might be faulty.
Last edited by a moderator: