Database Info

Rikaline 6010 for xdaII

I am not able to use the receiver with Autoroute 2004(pocket streets). The manual suggests that I ensure a virtual COM port is established before connecting the receiver, which I am not able to get around. I am lost and stuck with an expensive receiver. Can some help, please? ASAP

Daz, when you try to run the program does it give the option to choose your gps/com port?

no, nothing came up on the screen. Fortunately I have been able to resolve the problem. Need to disable to incoming beam option in connection setting

I currently have the same problem with rakaline 6031-x7 and tomtom navigator. I use to connect the gps reciever via blutooth manager as slave and then set it up in tomtom on my ipaq. now I can't find any options in bluetooth settings on my xda2. Any chance of a little help?
:?

gavcha, the xda2 is braindead where bluetooth is concerned, are you running the latest gps 2.09 from tomtom? If you are using that and it still isnt working, download towas patch, remove the gps from the bonding on your bluetooth, install towas patch, run tomtom wizard, gps manager in discoverable mode, add device in bt manager by choosing "new", choose the gps, ok everything, towas patch should then come up and give you the serial option, choose that. When finished go to tomtom gps, choose tomtom bluetooth and in the second drop down your gps should be available, choose that and it should work.

Cheers mate. me being the impatient ba£$%rd that I am found this site
http://bluetooth.i-networx.de/index_e.html
Very usefull, up and running in no time. Seems to be in the same vein as your suggestion. Thanks for all your help I am slowly getting use to this xda milarky! Finaly I can sell the Ipaq!!!!
Cheers again.

Good to know it works, when O2 release the update it should get better, by the way that link you posted has been a pain in the ass for me, I have clicked that link in numerous posts and NEVER been able to connect, I have the patch now but does anybody else have problems linking to the above link.?

yeah i had problems going back to it when i was checking it to put it in my last post. try googling xda2 bluetooth manager. thats what took me to another forum with the link to this. worth a try. :idea:

GPS can't bound

How can I bound the GPS on my IMate with WM5?
It seems that the GPS program in the setting is not letting it connect.
I tryed to downgrade back to wm3 and everithing work fine.
Can I remove the GPS program? I can't find it in the remove program (because it come with the rom).
Please help me :-(

you don't need the gps settings in the connection tab. set programport to <none> and hardwareport to <none> and on the third tab don't set the option on.
then you should be able to use your gps as usual. Is it BT or wired?

Navigon 6 and Qtek 2020 GPS Problem

hi, i use a xdaii with an german mobile 5 3.00a and radio 1.08. I want to youse navigon 6 on my pda but it cant find the gps mouse navigon 5 works nice without any problems. is there any fixes for it? i try 4 days to find something but there is nothing. please help

have you paired correctly with your gps?you need to assign an incoming serial port.Mine is serial port 5 and baud rate 38400. (not on navigon but it is common in every software)

yes i try all ports but there is no connection. navigon 5 works without any problem but navigon 6 cant find gps with the same configuration.
thank you for your reply

Hi There
Try to follow the following steps these might help
mine is working
Installing TomTom Navigator
15. Using File Explorer, navigate to the .CAB file you copied to your SD card and install R-Edit
on your Pocket PC. R-Edit can be acquired from http://www.pocketfleet.homeunix.com/REGEDIT.htm
but you can also Google for any other Windows Mobile 5 Registry Editor.
16. Run R-Edit from the Programs Menu.
17. Within R-Edit, navigate to the registry key "HKEY_LOCAL_MACHINE\ControlPanel\GPS Settings"
18. Within the registry key, delete the DWORD entry marked "Hide"
19. Add a DWORD entry called "Group" and give it a Value of "2"
20. Soft reset your Pocket PC.
21. On your Pocket PC, go to Settings > Connections to ensure that the GPS icon is there.
If it is not then I can only apologise but it may not be possible to get TomTom working with
your GPS device. It is necessary for TomTom to see a specific GPS serial port that can
(as far as I can tell) only be set by this GPS connection program. After you have paired
with your Bluetooth GPS device you could try setting an Outgoing port to COM7: as that is
a default COM port that TomTom Navigator can connect to. Do step 22 then skip to step 26.
22. Turn on your Bluetooth GPS and stick it in a location that it's likely to get a signal.
On your Pocket PC, enable Bluetooth and search for new devices. Establish a bond (pair) with
your GPS device and ensure you check the "Serial Port" option.
23. Go to Settings > Connections > Bluetooth. Create a new Incoming COM Port. I chose COM8 for this.
24. Other guides on the Internet tell you to also create an Outgoing port and setting it
as COM7 but doing this would not work on the PPC that I was using so I had to create the
Outgoing COM port on COM0. Either way you need an Outgoing COM port to be set.
If you can set it as COM7: then you should do so, if not, use COM0:
25. Go to Settings > Connections > GPS. Set the GPS communication port to the same
Outgoing COM port that you set above. For the PPC I was using,
I had to set it as COM0: above so will set it here as COM0: also.
The "Manage GPS Automatically" checkbox should already be checked but if it isn't, check it and OK out.
26. Start up TomTom Navigator using the Programs menu and run through the setup procedure as
normal but select "Other Bluetooth GPS" when asked to select a GPS device.
27. TomTom will ask you to now pair your GPS device with your Pocket PC.
We've already done that so click Continue.
28. You will be given a list of ports that your GPS device is likely to be on.
Remember that this is the Outgoing port that we created earlier in steps 24 and 25.
Basically the COM port you set here must be the same as the one you set in step 24 and 25.
29. Select the relevant COM port and then click Next. You will likely be taken straight
in to the map view and with any luck your Pocket PC and GPS device will start communicating and your Pocket PC will show your position on the map.
30. If you made a mistake in setting the COM port that your GPS device lives on,
simply tap anywhere on the screen. Tap Preferences, tap Next three times until you
see an icon that looks like a satellite labelled GPS status. Tap that icon and then tap configure to change the COM port.

thank you for the instruction. but i cant change something from the settings because they are the same on my device.

Problems connecting to Holux 236Slim with Treo 750 WM 6

I had no problem pairing with my Holux 236slim external GPS but cannot locate the GPS when scanning for it using the Holux GPS View software, nor does MS Livesearch locate the GPS. Livesearch asks for a com port and I've tried them all with no success. Does anyone know which comport the Treo 750 should use? And what about the remote GPS settings which ask for both "program" and "hardware" com ports (which cannot be the same)?

The way that I understand it (from messing around, mostly) is that the "external GPS" program allows "sharing" of the BT signal by multiple programs. Here's what I did.
1) Pair the GPS via Bluetooth.
2) Set the GPS up as a comm port - BT, Settings, COM Ports, New Outgoing Port. I set my GPS up as COM 8, secure.
3) Next, go into the External GPS application. Set up the "Program" port as the port you'd like to scan from the mapping application - I used COM 0. Set up the "Hardware" port to match what you did in step 2 - in my case, COM 8, 4800 baud. Check the box on the "Access" page so you can share the BT GPS signal.
From whatever application you're using (Google Maps, WLS, or other), set up the application to look for the GPS on the "Program" comm port, in my case, COM 0. I've had WLS, GMM, and a program called "Beeline GPS" running all at the same time, sharing the same GPS.
Hope this helps,
-Craig

Thanks very much for your help!
Your solution worked like a charm -- thanks very much for your help. I used the same settings in External GPS. I'm using with Livesearch maps and that worked fine.

Try "Com 0", thats what I use with Tom Tom!

Any method to 'fool' programs into using a Bluetooth GPS

We all know the Tilt's GPS is slow, uses a lot of battery, and often continues to use battery after exiting all programs using it unless you soft reset. So I use my bluetooth GPS.
Works great, for programs which have a com port setting. There are some which do not, some are on the todo list, but some other programs are no longer under development.
What I'd like to be able to do is to 'fool' any program into using the Bluetooth's com port. I have GPSGate listening to the bluetooth GPS and outputting to com1 so that I can run whatever number of programs using the GPS data on com1, but I can't get several Wifi scanners to use com1, can't get the camera's GPS feature to use com1, etc.
I've tried a few things like messing with the built-in GPS settings and changing them to com1 hoping programs might then access com1, tried setting GPSGate to com4 to see if programs would access it instead of the built-in, but I think when programs access the built-in device they don't access it on com4, they access it on GPD4 or such.. Anyway.
So again, how to make programs which you cannot specify a com port use GPSGate's com port? Or another program if necessary..
Thanks!

Bumping in case anyone missed it.
Thanks!

SOLVED! But not for the faint of heart.
The developer of BasicGPS pointed me to this URL when I was asking him if he could implement selecting the com port for the GPS, since I use GPSGate with a Bluetooth GPS, not the built-in one:
http://msdn.microsoft.com/en-us/library/bb202089.aspx
From this, following these steps, I was able to make the Intermediate Driver use COM1, therefore using GPSGate/Bluetooth! So far this works in BasicGPS and I'm pretty sure it works in the camera too, so probably works in every program! Good news for people who hate the built-in GPS as much as I do!
Here are the basic steps, but you'll want to read the URL above. It's really written for developers, which I am not, but it made enough sense for me.
I used Resco Explorer to browse into this registry key. I made a copy of the whole key, then browsed in.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers
There is a key named CurrentDriver, which was set to GPSOneDevice, which is apparently my built-in GPS. So I made a copy of the whole GPSOneDevice registry key, named it GPSGate. Then went into that key, changed the InterfaceType from POLL to COMM and added a string called CommPort and set it to COM1: where GPSGate outputs its info. I also modified the FriendlyName to "GPSGate Bluetooth". Finally, I changed the CurrentDriver to reference my new GPSGate registry key, and voila!
I'm not 100% sure it's working, as the built-in GPS is warmed up and would respond fairly quickly, but in a few days I'm going to try the camera in GPS mode and see if it immediately gets a fix from my Bluetooth unit vs 5+ minutes with the built-in GPS.
That said, I've tried GPSTest, BasicGPS, camera, etc, all get a fix immediately and update with the Bluetooth GPS on. If I turn the Bluetooth GPS off, they all stop getting updates. Previously when I was trying to figure out how to do this, I would discover the built-in GPS was still being used because I'd turn off the Bluetooth GPS and programs would continue to get new GPS data. So this tells me it's working! I'll follow up again in a few days to say for absolute sure.
Yay!

Just a followup here.. I think it's working, but if I monitor the data on COM9 (bluetooth) or COM1 (GPSGate re-distributing COM9 data), the data streams in at a reasonable pace.. Perhaps 6k of data in 10 or so seconds.. I didn't measure it closely.
But when I monitor data on COM4 the data is very fast, after about 10s it was up to 60k and when I left a few different programs open for a while they either crashed, never got a real lock, or locked up.
So not sure why, but the string of bluetooth->gpsgate->intermediate driver is causing a LOT more data to be produced.
I wasn't planning on using the intermediate driver for applications, I am still going to use the COM1 port for that when possible, but I wonder about the stability of using the camera and/or other programs which can't change the com port with this configuration.
Oh well! So far the camera seems to pick up a coordinate very quickly and probably disconnects from the GPS, so it's probably fine.
I suppose if I were truly curious I could capture the NMEA data and compare between the two. If anyone can do that who is also curious, I can do it and attach the data. I wouldn't know what to look for.

Hi,
ok, perhaps I know the Problem why my intermediate driver doesn't do his job. I can find this key in my reg:
Code:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers
But that is all. This key hasn't any values or subkeys. But why?
I'll try to find out the default Settings...
So. I've created following settings:
Code:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver
CurrentLogFile="\Temp\gps.log"
IsEnabled=dword:00000001
HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers
CurrentDriver="TestFile"
HKEY_LOCAL_MACHINE\System\CurrentControlSet\GPS Intermediate Driver\Drivers\TestFile
File1="\Temp\test.nmea"
FriendlyName="File Test #1"
InterfaceType="File"
After creating settings I "rebooted" my device. Then I start my GoogleMaps-App and configured it to use "managed GPS".
Result: GoogleMaps didn't get data from test-file and I cannot find the log-file in Temp-Folder. What the hell is going wrong here?
YFI: If I configure GoogleMaps to use GPS an COM4 (115200 Baud) then all works fine.