View previous topic :: View next topic |
Author |
Message |
RogerStenning Occasional Visitor
Joined: May 23, 2004 Posts: 31
|
Posted: Sun Jun 20, 2004 6:46 pm Post subject: |
|
|
icsys wrote: | Nice one Tim
The common denominators here are:
4100 BT receiver and SmartSTv2SP2
The fault is apparent using a 1940 and 2210.
Could it be a software driver for the bluetooth manager?? The receiver does appear to be communicating to the iPAQ's as the Navman icon is there! |
Not quite. I'm using an iPaq h1940, yes, but the BT GPSr is the 4410.
As I mentioned above, my thinking is that there's some form of problem with the Bluetooth manager within the iPaq firmware, given that people that use the sleeve versions of Navman do not seem to have the problem that Bluetooth users are suffering.
Conclusion: HP may have to look into this, and come up with a patch of some form.
Thoughts? |
|
Back to top |
|
|
icsys Frequent Visitor
Joined: Feb 20, 2004 Posts: 1154 Location: South Lancashire, UK
|
Posted: Mon Jun 21, 2004 1:20 pm Post subject: |
|
|
Roger,
I have the 4410 package.
The 4410 consists of the 4100 bluetooth receiver and SmartSTv2 software.
In fact the 4400, 4410, 4460 all use the same 4100 receiver
RogerStenning wrote: | As I mentioned above, my thinking is that there's some form of problem with the Bluetooth manager within the iPaq firmware, given that people that use the sleeve versions of Navman do not seem to have the problem that Bluetooth users are suffering.
|
I was thinking the same.
Looking at the Tomtom thread about BT registry hacks I am wondering if something along these lines will help at all? _________________ Ian.
iPAQ 2210 | Navman 4100 BT Receiver
Navman iCN 635
TomTom GO
Anquet OS mapping
|
|
Back to top |
|
|
RogerStenning Occasional Visitor
Joined: May 23, 2004 Posts: 31
|
Posted: Mon Jun 21, 2004 7:41 pm Post subject: |
|
|
Sorry, brainfart. You're spot on.
I dunno about registry hacks, being rather new to PPCs, but it may be the way to go. That said, it may be that both MS and HP arte aware of the problem, and are/will be working on a patch or solution for it.
We shall see.
Not really in the mood for deeper thought on this tonight: I just got in from a ten hour shift on the buses, and I'm fubared. |
|
Back to top |
|
|
icsys Frequent Visitor
Joined: Feb 20, 2004 Posts: 1154 Location: South Lancashire, UK
|
Posted: Tue Jun 22, 2004 4:49 pm Post subject: |
|
|
Well I was hoping that some of our technical minded users out there may be able to suggest a good starting point to resolve this problem before I resort to updating the ROM to the latest 1.10 (bearing in mind I already have the old 1.10)
With reference to the "GPS Protocol Error - Get Protocol Timeout" message reported by sfi i'm thinking the ROM update may fix the problem.
Any suggestions? _________________ Ian.
iPAQ 2210 | Navman 4100 BT Receiver
Navman iCN 635
TomTom GO
Anquet OS mapping
|
|
Back to top |
|
|
sfi Occasional Visitor
Joined: Mar 18, 2004 Posts: 17
|
Posted: Tue Jun 22, 2004 11:10 pm Post subject: |
|
|
I think you already have the latest rom firmware |
|
Back to top |
|
|
icsys Frequent Visitor
Joined: Feb 20, 2004 Posts: 1154 Location: South Lancashire, UK
|
Posted: Wed Jun 23, 2004 3:43 pm Post subject: |
|
|
Yep...
You're right! I downloaded the 'latest' ROM this morning and found out that it is the same as the March update
So it's back to the drawing board with this problem. _________________ Ian.
iPAQ 2210 | Navman 4100 BT Receiver
Navman iCN 635
TomTom GO
Anquet OS mapping
|
|
Back to top |
|
|
icsys Frequent Visitor
Joined: Feb 20, 2004 Posts: 1154 Location: South Lancashire, UK
|
Posted: Thu Jun 24, 2004 11:55 am Post subject: |
|
|
I dont think we're going to get much help with this
Posted on the HP forums but no reply.
Sent mail to Navman support but no reply. But wait, what's this in my Inbox?
Hot off the press from Navman
Quote: | This is a problem with the BT manager. HP have said that there are a number of fixes on their website that should remedy this. |
I am now thinking of applying this recently released Bluetooth Driver Security Update to see if that helps. _________________ Ian.
iPAQ 2210 | Navman 4100 BT Receiver
Navman iCN 635
TomTom GO
Anquet OS mapping
|
|
Back to top |
|
|
sfi Occasional Visitor
Joined: Mar 18, 2004 Posts: 17
|
Posted: Thu Jun 24, 2004 3:14 pm Post subject: |
|
|
The update didn't fix it for me.
The Bluetooth manager is puzzling
I’ve tried switching to the BT manager with an active GPS connection. The Bluetooth screens seem to be contradictory.
The my shortcuts screen shows no active connection, the active connections screen shows an active outgoing connection while the status screen shows ”not connected”
The GPS application meanwhile is receiving OK. |
|
Back to top |
|
|
icsys Frequent Visitor
Joined: Feb 20, 2004 Posts: 1154 Location: South Lancashire, UK
|
Posted: Thu Jun 24, 2004 11:09 pm Post subject: |
|
|
HP support suggested :
We suggest that you download the perform the Bluetooth drive update on the iPAQ from the link given below:
http://h18000.www1.hp.com/support/files/handheldiPAQ/us/download/19650.html
However, this didn't work either. _________________ Ian.
iPAQ 2210 | Navman 4100 BT Receiver
Navman iCN 635
TomTom GO
Anquet OS mapping
|
|
Back to top |
|
|
RogerStenning Occasional Visitor
Joined: May 23, 2004 Posts: 31
|
Posted: Fri Jun 25, 2004 9:03 am Post subject: |
|
|
I've had a one-off success in not having to perform a soft reset. If any of you can replicate it, we might be able to get HP/MS to make a working patch for the BT manager: Here are the details.
At the end of the route, go into SmartST, menu -> GPS Status,and UNCHECK the box, top left of screen, marked 'GPS'. Exit SmartST.
Click the BT symbol, bottom right of the main PPC screen. Disconnect from the 4410 BT GPS. Then turn BT off.
Now, as I've said, it only worked once, but if we can replicate it with someone else's PPC, we might be on-track to figure out where the problem lies.
Hope this helps, anyhow. |
|
Back to top |
|
|
kartracer Frequent Visitor
Joined: 26/03/2003 20:15:33 Posts: 502 Location: United Kingdom
|
Posted: Fri Jun 25, 2004 11:33 am Post subject: |
|
|
RogerStenning,
I thought that this discussion was about not having to reset a route calculation if taking a break en route.
If you merely want to avoid having to soft reset the Ipaq between different journeys, then I find that just exiting SmartST before switching of the Ipaq always does the trick. This is with a 5550 and 4410. _________________ Kam |
|
Back to top |
|
|
icsys Frequent Visitor
Joined: Feb 20, 2004 Posts: 1154 Location: South Lancashire, UK
|
Posted: Fri Jun 25, 2004 3:07 pm Post subject: |
|
|
This thread IS about having to soft reset mid-route when taking a break.
However, I have managed to replicate Roger's findings:
With everything switched on...
Calculate a route, after first instruction, go to the 'GPS status', un check the GPS box in top left corner, switch off iPAQ (without shutting down ST) receiver will go to sleep.
Switch on receiver, switch on iPAQ, (it still has the 'GPS status' page open)
check the GPS box, BT manager pops up and finds Navman, click it and wahay.... a sat fix!
This was a static test. I need to try it on a journey.
Not quite the same method but it worked several times. _________________ Ian.
iPAQ 2210 | Navman 4100 BT Receiver
Navman iCN 635
TomTom GO
Anquet OS mapping
|
|
Back to top |
|
|
kartracer Frequent Visitor
Joined: 26/03/2003 20:15:33 Posts: 502 Location: United Kingdom
|
Posted: Fri Jun 25, 2004 3:20 pm Post subject: |
|
|
Right. I'll have to try that.
The thing that confused me was that Roger said to "Exit SmartST" after unchecking the GPS box. _________________ Kam |
|
Back to top |
|
|
RogerStenning Occasional Visitor
Joined: May 23, 2004 Posts: 31
|
Posted: Fri Jun 25, 2004 9:32 pm Post subject: |
|
|
kartracer wrote: | Right. I'll have to try that.
The thing that confused me was that Roger said to "Exit SmartST" after unchecking the GPS box. |
Sorry about that. The exit method worked when I tried it, and I've tried a couple of other methods that failed, before I read the method described by icsys. I've tried this method today, on the way home from work, and it worked for me as well. Nice one, mate!
Looks like we've a working get-around for this problem, folks! |
|
Back to top |
|
|
kartracer Frequent Visitor
Joined: 26/03/2003 20:15:33 Posts: 502 Location: United Kingdom
|
Posted: Sat Jun 26, 2004 4:48 pm Post subject: |
|
|
Yes. It works fine for me too! A good workaround. :D _________________ Kam |
|
Back to top |
|
|
|
Posted: Today Post subject: Pocket GPS Advertising |
|
|
We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?. Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
|
|
Back to top |
|
|
|