[gps-talkusers] Re: Bluetooth connection procedure

  • From: "David" <shotgun@xxxxxxxxxxxx>
  • To: <gps-talkusers@xxxxxxxxxxxxx>
  • Date: Mon, 22 May 2006 06:24:30 -0700

Rob, What I've been doing lately, and it seems to work quite well, is to turn on your PK, or whatever you are using. Wait about ten seconds and turn on your receiver. Wait a few more seconds then load GPS. This seems to work well for me 99 percent of the time.

Once your receiver is pared with your unit, you should not need to search for devices, but from time to time, you might need to remove paring and re-pair the two devices.

Hope this helps,

Dave

taxation WITH representation isn't so hot, either!

----- Original Message ----- From: "Rob Gentell" <rggeneral@xxxxxxxxxxxxx>
To: <gps-talkusers@xxxxxxxxxxxxx>
Sent: Sunday, May 21, 2006 11:53 PM
Subject: [gps-talkusers] Re: Bluetooth connection procedure



Carl,

Sorry for the delayed response.  But it's really quite simple.  About
40% of the time that pairing is required, I get a message similar to
"failed to pair with Holux ...".  It sometimes takes as many as 3 or 4
tries until it actually pairs.  In all cases, I've instructed the pk to
search for devices.  I've seen this occur on another PK running Keysoft
7 and using a Blue Logger, so it doesn't seem like it is receiver
related.  Perhaps you aren't getting complaints about this problem
because the "problem" eventually gets resolved with a little patience
and persistence from the user.

-----Original Message-----
From: gps-talkusers-bounce@xxxxxxxxxxxxx
[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Carl Simmons
Sent: Tuesday, May 09, 2006 10:44 PM
To: gps-talkusers@xxxxxxxxxxxxx
Subject: [gps-talkusers] Re: Bluetooth connection procedure


Rob and List,

I need to better understand these issues as I am not receiving
complaints about this issue. I am using both the PK and mPower with
various receivers including the Holux. I have not experienced this issue
and to the best of my knowledge the BlueTooth connection should follow
the procedures I stated in the previous post.

The Sendero GPS program does not handle any of the Bluetooth
connectivity functions. All we do is examine the status.  Keysoft does
all the Bluetooth pairing and connecting.  There were some improvements
in Keysoft 7.0 over Keysoft 6.1 and 6.2.

I will pass these comments to Humanware and continue to test in this
area. Any comments or difficulty in this area would be appreciated.  I
am sure that Humanware would be very interested in any difficulty you
are having in this area.  The resolution of any problems in the
Bluetooth connectivity area will have to be in the Keysoft area.  So
please advise Humanware of
these issues.

We will continue to work with our users and Humanware to assure that
this issue is being addressed.  I do need your feedback and comments to
be able to address this issue effectively.

Carl Simmons
Sendero Group Training and Technical Support
1-888-757-6810 Ext. 106
carl@xxxxxxxxxxxxxxxx



-----Original Message-----
From: gps-talkusers-bounce@xxxxxxxxxxxxx
[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Rob Gentell
Sent: Tuesday, May 09, 2006 8:20 PM
To: gps-talkusers@xxxxxxxxxxxxx
Subject: [gps-talkusers] Re: Bluetooth connection procedure

Oh yes, I forgot to mention that pairing fails about 40% of the time at
least on the pk with Keysoft and Gps versions 7.0 and 3.5, respectively.
I don't recall the exact error message, but it is similar to "failed to
pair bluetooth device."  Typing 0000 isn't that difficult so I've by now
ruled out user error.  It seemed to have started with Keysoft 7.

-----Original Message-----
From: gps-talkusers-bounce@xxxxxxxxxxxxx
[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of G B
Sent: Tuesday, May 09, 2006 8:05 AM
To: gps-talkusers@xxxxxxxxxxxxx
Subject: [gps-talkusers] Re: Bluetooth connection procedure


Hi, I have the same issue with my pk. Sometimes it takes 2 or 3 times to pare the receiver with the unit and I have to do the same c 3 4 reset to get it to work.

-----Original Message-----
From: gps-talkusers-bounce@xxxxxxxxxxxxx
[mailto:gps-talkusers-bounce@xxxxxxxxxxxxx] On Behalf Of Robert Carter
Sent: Tuesday, May 09, 2006 07:57
To: gps-talkusers@xxxxxxxxxxxxx
Subject: [gps-talkusers] Re: Bluetooth connection procedure

Hi,

My pk sometimes behaves just as you have described.

Robert Carter

At 08:08 AM 5/9/2006, you wrote:
I have an interesting comment about this bluetooth business.
I use the pk for the gps primarily. Yesterday, my pk did a total reset
on me which put everything back to the factory defaults. I went in this

morning andturned the bluetooth on after turning on the
Hollux.
Ok here is where things got interesting. It told me that bluetooth was
not on so I typed y. Now it went on to tell me that the machine was
unable to start
bluetooth.
Ok not wanting to give up, I did a reset with no keys down except
the 2 control keys on the right hand side.
Ok here is what is so intriguing. When I again went into the
connectivity menu, I found to my delight that thebluetooth was on
and I was able to then pair with the hollux and we were off in a
jiffy because the receiver had already come into contact with the
satellites.
Happy traveling, everybody!
Mary Ellen Earls
----- Original Message ----- From: "Scott Marshall"
<Scott.Marshall@xxxxxxx>
To: <gps-talkusers@xxxxxxxxxxxxx>
Sent: Tuesday, May 09, 2006 4:49 AM
Subject: [gps-talkusers] Bluetooth connection procedure


Hello everyone: I have read the message thread on Bluetooth connection problems and have experienced the same myself, running version 3.5 on the MPower. Since I'm a linear thinking kind of guy, here is what I understand the recommended procedure to be:

Once the holux has been paired, activesync is on, and Bluetooth is on:

1. Turn the holux on.
2. Turn the Braille note on and wait for several seconds.
3. Run the GPS program.
4. A hard reset will destroy the pairing.
5. An ordinary reset may cause the Bluetooth function of the bN to be
turned off.

If the above is not correct, please let me know.

Thanks!

Scott








-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.5.5/333 - Release Date: 5/5/2006






-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.392 / Virus Database: 268.5.5/335 - Release Date: 5/9/2006







Other related posts: