Forerunner 201 COM1 problem.

[Bokkie]

I downloaded new software for my 201. I have the serial cable connected and the device is switched on and is in its cradle. If I run the updater it complains that access to all the COM ports is denied. If I run the 201 logbook program and try to connect it tells me it cannot connect to the device. I had this working several months ago though I did reformat my hdd and reloaded the OS etc. If I look at the COM port in the device manager it tells me the drivers are loaded and that it is enabled.

Anyone any ideas why the COM port refuses to work anymore? I used to have this working once upon a time. I think the OS reload might have clobbered something but I can't see what.

[kokopeli123]

Have the same problem with a Garmin Geko 201 after I loaded the latest update for MapSource that enabled it to work with the iQue.

Anybody figured out how to fix this?

kokopeli123

[duhgus]

All the sudden they change the name of the forum and BLAMO! We're getting GEKO and FORERUNNER questions!!! What has this world come to?!?!?


KIDDING! KIDDING! KIDDING!

I have the 201 as well, but gave it to my woman for walks around the neighborhood. I've never tried to use the serial cable. I downloaded the new software as well, but haven't had cause to use it. I'll try to recreate the problem. (The 201 has given me nothing but problems...RMA'ed it twice)

What software versions are being used?

[JMckie]

Whatever the solution is, please remember post it here. It might help with my own Mapsource COM1 problem.

[Bokkie]

Originally posted by duhgus
All the sudden they change the name of the forum and BLAMO! We're getting GEKO and FORERUNNER questions!!! What has this world come to?!?!?


KIDDING! KIDDING! KIDDING!

I have the 201 as well, but gave it to my woman for walks around the neighborhood. I've never tried to use the serial cable. I downloaded the new software as well, but haven't had cause to use it. I'll try to recreate the problem. (The 201 has given me nothing but problems...RMA'ed it twice)

What software versions are being used?

As it is, my 201 has the latest 2.4 software that Garmin have available for download. My main problem now is that the LogBook software cannot download my laps.

One serial port to bring them all, and in the nighttime screw them. One solution to bring them all and in the daytime download them. Something like that.

[sherio]

It's probably not this but just in case... did you make sure the pin of the serial connector is securely stuck in the cradle? If there's any metal showing, then it needs to be pushed in more. All my friends and I had this problem.

Sheri

[Bokkie]

Originally posted by sherio
It's probably not this but just in case... did you make sure the pin of the serial connector is securely stuck in the cradle? If there's any metal showing, then it needs to be pushed in more. All my friends and I had this problem.

Sheri

Mine is locked down real tight on the serial port on the PC and the connecting pin to the cradle is pushed in all the way, no metal showing. As I say, this used to work a while ago and all I did was reformat and reinstall the OS and apps.

[duhgus]

Well, I have to say that this Logbook software is pretty d@mn cool! Props to Garmin!

The software version of the 201 pops up as 3.40. The Athlete Logbook software version is listed as 2.5. I was able to auto-detect the 201 and download all of the tracks...er, laps.

I found that the first time it wouldn't connect, so I checked to make sure the serial cable was plugged into the correct spot on the cradle. It was but wasn't plugged in the whole way. Seems like it had one more "click" to go. That seemed to do the trick.

The "updater" software confirmed that the 201 software version was 3.40.

[Querod]

I had a similar problem when I got my forerunnner. If you have the palm hot synch manager on it conflicts witht he forerunner's connection. I have to disble hotsynch in my computer before I use forerunner. I hope this works.

SF, Felix

[Bokkie]

I found the problem. The COM port had been hijacked, not by HotSync, but by ActiveSync. I disable the COM port and rebooted and it was after that I got the error from ActiveSync barfing about the port not being available. I reenabled the port, and voila, my Forerunner is now working ok.

[jonasolof]

Now it's getting interesting.

Since Forerunner now works OK with the Comm port, does Active Synch work OK with the same comm port also? Or do you only activate Active sync manually, as can be done with Palm hotsync, another well known comm port hijacker.

In general, a serial to usb converter can be a good way to circumvent these conflicts. Only, it often happens that the USB installation of a virtual comm port gives a port number which is too high, like number 11. I was until recently unaware that win2k and XP allows you to change the comm port number under comm port properties in the device manager. One can often find a free low comm port number by looking in the list displaying thee choices of comm port numbers. Why the USB installation wouldn't go for that number in the first hand I don't know.

BTW, Nokia has an app for changing comm port numbers which I think works on win98 also.

A couple of years ago, most navigation related software only accepted comm port numbers up to 4. More recently, I've seen up to 9. All this is pretty impotant when testing i.a. NMEAout or QuePId, especially witrh usb-serialk converters.

Finally, is there a guide to how a software's comm port affiliation is listed in the registry? Sometimes, you can't disable a hijacked comm port and it would be good to do it on a lower level.

[Bokkie]

Jonas,

I have to start smashing tiles off the bathroom walls. Not in response to the COM port angst, but in response to my wife's "honey-do" list! To neglect the latter could have serious consequences, of which all men are aware, and will no doubt offer their moral support.:D

I'm at a loss why ActiveSync should take it for its own when I've been using USB exclusively for syncing. Unfortunately, my HX4700 is on RMA duty and only due back in camp next week, so I won't know how ActiveSync will respond when I reconnect, but I'll deal with each problem at a time when it happens.

Point I'm getting at from my first paragraph is that I'll look through the registry later and see if I can unearth anything. I have 8 COM ports supposedly available when I load Forerunner's LogBook software, but whether that is picked up dynamically at runtime or just a catch-all thumb-suck I don't know for sure.

I'll hopefully report back later - honey-do list permitting!

;)

[jonasolof]

I won't comment on the honey-do list problem. Too sensitive a topic.