how to trouble shoot bluetooth gps receiver

[djaap30]

Hey all,
I just recently installed the official helmi 3.5 kitchen on my xv6700 and everything is working beautifully except for my bluetooth gps receiver. I use the HP ipaq navigation blue tooth receiver. For software i use either windows live search or hp's ipaq nav sw. I had no problems with it prior to installing the kitchen, but now i can't connect to it from either application (live search or HP app). The bluetooth mgr seems to be connecting to it just fine thru com port 4....but no dice from the apps. I also found out that the receiver has a default passkey of "2003" so i made sure that was correct in my bluetooth settings....still no dice. Can anyone give any pointers on how to troubleshoot this?....
thanks in advance....
Dan

[fparkin]

the gps icon in setting did you tell Program to use comport 1 and gps uses 4 comport

[wb8yst]

I run three apps (PocketFMS, iGuidence 4, Topo USA) with the gps (iBlue 737 Pro 5 Hz)
and have found that most of the apps like comm 6 and above.
I allowed it to search for the gps, put the pass codes in and made sure the outgoing is port is com6.
I think I also ckecked serial on as well.

[wb8yst]

Also, I had to reinstall an app before it would see com 6, streets 2007 (which I quit using) / Topo USA did not like having the com port changed after the first install, I would delete the com port listed prior and it just never find the new com port. iGuidence and PocketFMS could care less about the changes in the com ports as long as the setup is reused in iGuidence, PocketFMS com's can be changed on the main screen page.

[djaap30]

no, it's set to com4 in the app and the bt settings....as a matter of fact that was the only one available. prior to installing the ktchen, I was using com8.

[kevinakasmiley]

Did you check the box that says "make this device visible to other devices" in bt settings?

[djaap30]

yes, that doesn't fix it either.
I also have the "secure connection" check box checked in the incoming port settings.

[djaap30]

hey all...
I fixed it. I had an incoming com connection and apparently, it requires an outgoing com port, not an incoming port....thanx for helping....