Where's the "connect" option for bluetooth devices in WM5?

danl · 01-31-06, 09:46 AM

Title says it all. I've been having trouble consistently pairing my BT gps with the axim. In WM2003SE, there is a "connect" option for every bt device that is discovered in the bluetooth manager. But in WM2005, there is no such thing.

I've properly set up my gps, ie discover, found device, check serial service, new outgoing port, etc. And it works fine. But when I turn off the pda and the gps and turn them back on, they do not automatically communicate, which I thought they should once they have been previously paired. I have to re-discover the gps, pair it again, new outgoing port, etc.

Am I missing something? I'm somewhat of a novice when it comes to BT, but I assumed that once paired, both devices should be able to automatically find each other and communicate as soon as I turn on bluetooth.

Khris · 01-31-06, 09:48 AM

Because WM5 uses the Microsoft BT stack (which WM2003SE doesn't), you're not going to have/see the same options as before.

SolSie · 01-31-06, 09:53 AM

The Navigation program should initiate and connect automatically for you!

danl · 01-31-06, 04:53 PM

Originally Posted by SolSie

The Navigation program should initiate and connect automatically for you!

That was my assumption as well, but that doesn't happen. For instance, I have everything configured properly and iGuidance running. I close the app and turn off the PDA, then the gps. A short while later I turn both on. I run iGuidance, but there is no gps signal. I can tell from the gps that it hasn't connected to any device via bluetooth. Nothing happens until I go to the bluetooth mgr, rescan for devices, discover the gps unit, click on it, then check serial, then add a "New Outgoing Port" again overwriting the previous.

Is there something I'm not doing? Ie I have to turn on the pda before the gps? Or I have to wait 5-10 mins? The bluetooth pairing/partnership is there, but it won't "connect" and there's no "connect" option as in 2003.

danl · 02-02-06, 09:37 AM

Any help? Actually its seems to be getting worse. Lately I would turn both the pda and the gps, but I get no data from the gpsinfo utility or iGuidance. So I remove the gps partnership, rediscover and re-pair them. Still nothing. It usually takes me 10-20 mins of fiddle around, soft resets, turn off and on, etc to get the gps working. Anyone have the Globalsat BT338 and can suggest any tips/hints?

danl · 02-03-06, 09:43 AM

Think I answered my own question. I removed and re-added the partnership. Then I created a new outgoing port on com8, and an incoming port on com7. I then went into the GPS applet and set both hardware and program port to "none", and uncheck the "let windows manage gps device automatically". Now I seem to be able to connect to the gps consistently, though knock on wood I only tried it 3 times. Like someone mentioned the software application, 3dtracking or iGuidance or gpsinfo, will auto connect to the gps for me (ie fast blinking led on the BT338 to indicate connection).

Only think I worry about is that the windows gps applet supposedly allows multiple programs to access the gps data stream. I typically want to run iGuidance in the foreground, and 3dtracking in the background to log my movement. That may be broken now.

danl · 02-03-06, 09:57 AM

I think I have my problem solved. I removed and re-added the partnership. Then I created a new outgoing port on com8, and an incoming port on com7. I then went into the GPS applet and set both hardware and program port to "none", and uncheck the "let windows manage gps device automatically". Now I seem to be able to connect to the gps consistently, though knock on wood I only tried it 3 times.

You can find the official instructions for pairing with WM5 PPC are here: http://www.usglobalsat.com/forum/topic.asp?TOPIC_ID=28

But I didn't follow that exactly, since I changed to com port 8 and disabled windows gps management.