Related
Hi All,
I have a i-Mate PDA2K-EVDO with the following specs:
ROM:2.03.00 WWE
Radio: HA01_140
Ex ROM: 2.03.11 WWE
Currently with eXpansys FSE9 Car Kit (Includes integrated GPS reciever) URL"http://www.expansys.com.au/product.asp?code=124312", with ALK (Travroute) CoPilot Live 5 for PPC.
The issue that I am having is that when the phone is docked in the car-kit all call functions work fine (except for volume being a little low, but that may be spk position), however I cannot get the GPS software to communicate with the reciever. I am not sure whether the com-port that is used to communicate with the reciever is only being half-opened (or not remaining open).
I have tried modifying the selected COM settings and am currently using (COM 1, 4800) which appears to have some communication with the device. When the unit first is powered-up the GPS recieving light is on (steady) and when GPS location is established the light starts flashing. I have installed GPSInfo (for WM5) and am able to scan ports to establish COM1, 4800 as the connected port. When I then press the "Cold Start" button the GPS reciever resets, and then goes through the re-establishment phase, but no GPS data is being parsed.
To top things off, I did manage to get the CoPilot software to work for all about 5 mins. So I am thinking that this may be a port issue (or something with the reciever).
Can anyone provide some help with the following:
1 - A utility that can check com port activity, and see what is happening at this level.
2 - Some insight as to what other programs may use the same ports as COM1 - As I believe that it is serially emulated as a COM.
3 - Any other insight would be greatly appreciated.
Thanks in advance.
pro-integrator said:
Hi All,
I have a i-Mate PDA2K-EVDO with the following specs:
ROM:2.03.00 WWE
Radio: HA01_140
Ex ROM: 2.03.11 WWE
Currently with eXpansys FSE9 Car Kit (Includes integrated GPS reciever) URL"http://www.expansys.com.au/product.asp?code=124312", with ALK (Travroute) CoPilot Live 5 for PPC.
The issue that I am having is that when the phone is docked in the car-kit all call functions work fine (except for volume being a little low, but that may be spk position), however I cannot get the GPS software to communicate with the reciever. I am not sure whether the com-port that is used to communicate with the reciever is only being half-opened (or not remaining open).
I have tried modifying the selected COM settings and am currently using (COM 1, 4800) which appears to have some communication with the device. When the unit first is powered-up the GPS recieving light is on (steady) and when GPS location is established the light starts flashing. I have installed GPSInfo (for WM5) and am able to scan ports to establish COM1, 4800 as the connected port. When I then press the "Cold Start" button the GPS reciever resets, and then goes through the re-establishment phase, but no GPS data is being parsed.
To top things off, I did manage to get the CoPilot software to work for all about 5 mins. So I am thinking that this may be a port issue (or something with the reciever).
Can anyone provide some help with the following:
1 - A utility that can check com port activity, and see what is happening at this level.
2 - Some insight as to what other programs may use the same ports as COM1 - As I believe that it is serially emulated as a COM.
3 - Any other insight would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
Hi there,
Not too sure if this'll help but with TomTom 5, you need to disable incoming beams on the Start\Settings\Connections\Beam to enable the Hard-Wired GPS to be read..
Try it and let us know the outcome..
Cheers!
Still No Good
Hey Mr Philly,
No luck with the Beam Settings. I even went as fas as Hard Resetting the device :x as Active Sync to Exchange stopped working this morning....
Any other ideas?
Thanks again for your response.
Paul.[/quote]
Paul, you mentioned specificaly that you loaded GPS Info (for WM5) is this the OS you have on the device? if so the GPS applet in the control panel / connections tab might need playing with - BTW I should have mentioned as its a wired GPS unit leave the Receive all beams OFF on this device - Mike
Interesting Point
Hi Mike,
Thanks for joining in on this thread.
I have disabled beams on the device.
THe GPSInfo app loaded was WM5 although I only have WM2003 SE. I have searched through multiple ng's to find a 2K3SE version, but all seem to point to the new version.
This was also the file provided my the distributor of the car-kit & cradle. The GPS unit is integrated into the Car Kit, so that is what i refer to as hard-wired (opposed to GPS).
As for the applet, I do not have a GPS applet in the connections section :?:
Can you provide any more informationon this point.
Thanks again,
Paul.
Disregard it then, I thought you might have loaded up a 2005 OS by chance , this has no bearing on the problem on your device - more thinking time required - Mike
Re: Still No Good
pro-integrator said:
Hey Mr Philly,
No luck with the Beam Settings. I even went as fas as Hard Resetting the device :x as Active Sync to Exchange stopped working this morning....
Any other ideas?
Thanks again for your response.
Paul.
Click to expand...
Click to collapse
Hi Paul..
Apologies.. I also need more thinking time.. :lol:
If I think of anything else, I'll get back to you..
hi there
new to this forum which looks very interesting. Hence asking answer for a problem.
i have bought a Holox BT-321 gps receiver which is blue tooth enabled and i am trying my xda exec to recognise it. aftre turning both devices on xda can see the receiver but puts a yellow question mark before its name.
when turn the gps software on ((Medion Navigator) it does not recognise presence of the gps receiver.
i have great hopes that out there some one does know the answer to this.
to me it appears a software conflict as xda can not install this receiver.
i have tried O2 but they politely refused and asked me to contact gps receiver makers who in turn say the receiver is working fine!!
i was about to pay for a software pathway for sale at ebay but it had been banned by the ebay.
so help please
mohammad asif
Assuming that you did set a port for it (not sure whether it's incoming or outgoing) on the Exec for the GPS unit, you'll probably have to set the port to see the GPS unit on the software also.
That's how I got my GPS unit to work with my software. Please note that the software and the GPS unit that I'm using are not the same as yours. So results might vary.
I too am having exactly the same issues with the Holox 321 and o2 Exec. If anyone has had success pairing a using these two devices and can post a step-by-step walkthrough on how to do it I'd be very grateful.
Thanks.
MDA Pro and BT321
I have got exactly the same problem. It seem that the bluetooth works but the GPS receiver is not recognised. I was thinking of it could be missing drivers or something along those lines
I'm seeing a trend...
hi all,
My m8 has one of them on an XDA2i and the only way we could get it working with TT5 was to set it up as other NMEA GPS on com 6, that did the trick
hope that helps
Thanks BBD, that may help. Trouble is though, I can't even get it to pair correctly. The Exec seems to go through the motions, but the blue light that's meant to flash whenpairing is successful just stays solid.
I also get the question mark appear next to the device in the list of BT devices. What OS is your friend using? WM5 or PPC2003?
hi m8,
he is using WM2003SE, he two has the question mark beside his device I think that just means it does not have a Windows Certificate nothing more, just cheked my TOMTOM device has the question mark too and that works fine
Matt
hi,
just double checked and this is how it worked, pair the GPS receiver up, then go into TomTom and use the NMEA devices with baud rate of 38400 then select bluetooth on com6 and bingo bango your off
cheers
Matt
I think my problem occurs before TT5 is even invloved. From what I've seen WM2005 is very different from PPC2003 as far as BT goes.
I search for a new device and the BT-321 is seen as normal. I select it then enter the sec. key; ok so far. then I'm ask what services I want to use (only "serial port" is available). I select this, then finish. At this point I expect the blue BT light to start flashing telling me I have a successful pairing, but it stays solid. I have tried creating a new outgoing port, but no change.
Until I can get a successful pairing my BT port doesn't appear in the list in TT5, so I can't select it.
I wish I could find someone who has successfully paired these two devices...
Bump.
I can pair my mini s to the bluetooth reciever, but not tt5
i have paired my bluetooth reciever with my xda mini s but when i go to select it in tt5 none of the comports correspond with any i can pair the reciever with. I have installed bttools but this hasnt helped either. someone suggested i needed to build a com port but i dont know where to start, and they also said its because its an xda that theres comport problems, i donubt im the first one with this issue. i pray someone can help me out, would be much appriciated.
email [email protected]
Same problem on my Wizard with the Gpslim 236. However, my fiend brought over his rikaline last night and it worked very quickly. Go figure. I think I'll be exchanging today.
I got the BT321 working with the Universal no problem.
It paired okay, gave me the COM Port option which I took, showed the icon with ? on it.
Going to the COM Ports tab, I created an outgoing port (COM0).
In TT5.21 (I think you need the latest version of TT5) I selected COM0 and after a while it found it no problem..
F.
paring xda exec + gps holux 236
i did pare the 2 after updating tomtom to 5.21 free from tomtom web site then u get com 8 were u can set the outgoing port from the xda ,voila
I have XDA EXEC and have successfully installed the Holux BT-321 Bluetooth GPS. It runs perfectly with a number of GPS applications - so I know the port/Bluetooth configuration is ok. I had to choose an unused com port (0 or 4 work fine). (Ports 1,2,3,6,7,and 9 seem to be already used by the XDA EXEC - so could not be seleted).
BUT (going back to the first post) Medion Navigator (4.2) does NOT recognise the new GPS port. Instead it has options to select ports com1,2,3,6,7,9 but not the "new" port where the GPS is actually configured!
Does anyone have any ideas about this?
After several hours trawling forums and trying lots of things here's what worked for me on an XDA Exec running WM5. In fact I was shocked when it worked! In return for this can someone please think up the next thing after Toothache! The WM5 bluetooth connection thing could also do with a re-write - as could the WM5/XDA Exec instructions/FAQs/help, etc... on BT:
If your aim is to get TomTom working AND you're using a non-TomTom BT GPS, try this (the TomTom GPS seems to install itself without much problem):
1. Pair the GPS with your device BEFORE installing TomTom, because the GPS port needs to be already setup on your device for TomTom to recognise when installed.
2. Then install TomTom
3. Launch the BT connection thing in WM5. Make sure the BT is discoverable (first tab). Select 'Security' tab and ensure 'Authentication (Passkey) required is checked.
4. Go to 'Devices' tab and select 'new partnership...' The pairing thing should find your GPS and will then ask for the passkey - select next WITHOUT entering anything even if there's a passkey. If you enter the passkey now you will not get step 5 which is a crucial milestone.
5. The device should now ask if you want to add the GPS to your list, select yes
6. The name of the GPS is shown. Ensure 'serial' port is checked and hit next
7. You will be asked for the passkey again - enter it this time
8. At this point the GPS may look like it's not paired. The lights may flash as if unpaired. You'll also get a question mark icon next to the GPS in your list. Not to worry.
9. Select 'com ports' tab and select 'new outgoing port'. You should see your GPS listed. Select it and hit next. From the list of ports select COM8. Make sure the 'Secure connection' is UNCHECKED - otherwise you'll be pairing everytime you start TomTom! Select Finish. You should see your GPS (COM8) listed in 'COM ports' tab.
10. Turn off 'device is discoverable' (first tab).
11. Now install TomTom. Having installed the GPS as above, TomTom will now know about COM8 i.e. where your GPS is to be found. If you hadn't done that first there would be no COM8 and no GPS connected to it as far as TomTom is concerned.
12. Turn on the GPS
13. Launch TomTom and go to 'preferences/ GPS Settings'. Select 'configure'. Select 'Other bluetooth GPS'
14. You should get a list of ports and with any luck you should see 'COM8' - select it and hit 'done'.
15. I think at this point the GPS page in TomTom came alive, or maybe I had to restart TomTom - can't remember. And it works thus far!
Toothache - what a palaver!
BT/GPS Problems
Hi,
I have a program that can sort out the com port problems between the bluetooth and gps software.
I have included the program as an attachment, just unzip it into your PC, make sure you reboot your PDA, sync your PDA to the PC and run setup.
Problems solved.
Cheers,
John
bigbird49 said:
Hi,
I have a program that can sort out the com port problems between the bluetooth and gps software.
I have included the program as an attachment, just unzip it into your PC, make sure you reboot your PDA, sync your PDA to the PC and run setup.
Problems solved.
Cheers,
John
Click to expand...
Click to collapse
Hi,
I`m a new member.After installing your litle tool i can`t start this application and also can`t find it under programs or anywhere else?
I`m using a T-Mobile MDA Compact II with WM5 latest ROM, a Holux BT321 and TomTom6. `have expierences with BT and XDA`s using TT5 for a long time.
After upgrading to new devices and new sw i have the following problems:
I can connect the BT321 as a BT Mouse and get a good signal.Using TomTom6 the navigation works with a delay of round about 100 meter. I`m looking for a resolution to connect the BT321 via the NMEA Interface.
regards
AK
____________________________
MDAc II
WM5
BT321
TT6
Britishbulldog said:
hi all,
My m8 has one of them on an XDA2i and the only way we could get it working with TT5 was to set it up as other NMEA GPS on com 6, that did the trick
hope that helps
Click to expand...
Click to collapse
I have tried your advice and it works a treat, thanks to you and everybody else who contribute to this forum
Hi I have a mda compctII, I also have tomtom navigator 5. I am having problems setting up me I-blue gps reciever. I can get everything running and the test program supplied with the gpr reciever connects to the device and shows gps location. But... when I go to run tomtom I cannot get it to recognise the device. It is set up on bluetooth serial port 6 but tomtom does not have this selection availible... and Ideas?
I have no experience pairing a 3rd part BT GPS receiver since I use the original TomTom. I think what you need is to first install BT_COM_PORT.CAB (attached) so that you could select on which COM port to use.
Try upgrading TT to the latest version (5.21) too.
Good luck.
one step closer... in blutooth selection I am given the option for all the com ports... but it will only allow me to select com 6. This option is not shown in tomtom just com:0,2,3 and 9.
Sorry mate, I think I couldn't be of any further help since I have no experience with the I-Blue. If my memory serves me right, I think I saw some posts about the I-Blue in Howard Forum.
i installed TomTom Navigator 6.020 SD BENELUX V660.1219
the program works,
it only cant find my gps device :s
some help would be much appreciated
Have you considered searching for this one - I have answered the same question at least 3 times to date!
Other NMEA Device
Baud Rate 9600
Comm Port 4
Mike
I was having a problem with that also.
It didn't matter if I was in the middle of an empty field running around with the thing in the air like an idiot, the internal antenna was too weak.
Now if I was in the car, the thing would pick up a signal no problem.
After looking into alternatives - like an external antenna - I settled on this:
I just picked up a BT-359W Bluetooth GPS Receiver for 85- Euro new.
The only difference between the BT-359W & BT-359S is the design on the top.
I made sure the battery was 100% charged before I turned it on (old habits die hard) and after spending 5-10 minutes trying to configure the Bluetooth on the HTC P3300 - I am a newbie when it comes to this new technology - it was able to get 3 satellites while I was in the house right away.
The thing is very small also - 82 mm x 41 mm x 13.4 mm (Inches: 3.22" x 1.61" x 0.52").
I would have to say that this is a great alternative to a wired antenna.
Here is a review I read before making my final decision: GlobalSat BT-359 Bluetooth GPS receiver review
Click to expand...
Click to collapse
Originally posted --> HERE
What a waste
Looks like you have a lot of money to burn, or whats the point of having a P3300 (with a bult-in GPS receiver - SIRFIII BTW) and then buying a bluetooth external GPS (basically another SIRFIII) ? cos its external ?
AD10 said:
Looks like you have a lot of money to burn, or whats the point of having a P3300 (with a bult-in GPS receiver - SIRFIII BTW) and then buying a bluetooth external GPS (basically another SIRFIII) ? cos its external ?
Click to expand...
Click to collapse
You missed the point completely.
The internal antenna was too weak.
When I am in a car, I have no problems at all getting a satellite fix.
The reason I bought an external GPS receiver is because I am not in a car all the time when using the GPS.
Longhair said:
When I am in a car, I have no problems at all getting a satellite fix. The reason I bought an external GPS receiver is because I am not in a car all the time when using the GPS.
Click to expand...
Click to collapse
That doesn't make sense at all, it should be the other way around. Inside a car the signal will allways be weaker than outside, because of the surrounding metal.
grun said:
That doesn't make sense at all, it should be the other way around. Inside a car the signal will allways be weaker than outside, because of the surrounding metal.
Click to expand...
Click to collapse
Thanks Grun, I thot I was the only one missing the point...and crikey what a way to shout your ignorance.
grun said:
That doesn't make sense at all, it should be the other way around. Inside a car the signal will allways be weaker than outside, because of the surrounding metal.
Click to expand...
Click to collapse
completely agree, what you're saying doesnt make sense unless you were in some very dense forest with all the trees in leaf, but you say you were in the middle of a field.
im about to install tomtom on my orbit so will see what its like as i used to use a bt gps reciever on my xda IIi
hello
i have installed tomtom ver 5
and i have to say that it works a treat..
it takes about a minute to register on the GPS but it does work well form inside the car aswell as outside the car.
The settings i use are
GPS Program Com 4
GpS Hardware Com 0
and keep the 3rd tab option checked ie pocket pc controlling access
On the GPS setting in tomtom select other NMEA device and choose Com 4
First time use will take about 5 mins so keep the phone still then after should take less than a minute.....
hope it helps
Tomtom not working
I have tried endlessly without success to get the tomtom on my orbit working. It keeps saying 'no gps device found'. When I select 'Other NMEA device' i dont see com port 4 as one of the options, i see com2 and serial (i think).
I thought maybe the software was not properly installed when i read about the com 4 thing and so uninstalled it. However I bought the phone (brand new) with the tomtom from ebay but now i cannot reload the tomtom as it keeps crashing during install.
Any ideas on what next I can do
have you changed the hardware port to com 4 first?
start>settings>connections>gps
then on first page GPS settings it asks what program port form the drop down list select com 4, that should then enable TomTOm GPS settings to display com 4.
remember once you have selected settings connect your phone to PC via actie sync and on
start>programs>quick gps
select menu and select update automatically when connected via active sync
this speeds up the process of finding the satelites and the data is usually valid for abut 3 days, so it does help to locate satelites quicker.
keep the phone still for about 5 mins and it should work..
thanks
l6cum
PS i am using TomTom 5, but the procedure should be the same
hi,
Go to mininova.org and download Tomtom Navigator 6 of it. It might take a couple of days to download sometimes. After you download follow the instructions and it is all user friendly. If you want any help don't hesitate to get back to me. If you want a copy in a CD send me a SAE so that I can write it on a disc and send it to you
Hi Guys
I have been testing out some gps sat navs for work...tested with holux bt gps
So far I have the following which are compatible not compatible.
Destinator... works fine, however will sometimes struggle to pick up signal and requires a reset.. Otherwise all other functionality works great. Sometimes freezes when in 3d mode. (Most of these were true for wm5
Igo Myway plus- Will install on wm6(eventually) however seems to have a memory leak that causes it to slow down to nothing.... Very impressive gps sat nav on wm5. Better than most of the others I tried...
Will add more when test the other models.....
If anyone else can update me with thier info / experiences, please go ahead.
The Garmin Mobile 20 (GPS 20SM) works fine with both Windows Mobile 5 and 6. It is a Bluetooth GPS that supports using Bluetooth for receiving GPS information, and for the speakerphone, but for some reason insists on using the external speaker of the phone for navigation directions. (Or so it seems, I didn't have it long enough to do full testing).
The one problem that it seems to have (at least my unit does - I am awaiting a RMA replacement) is that it will not charge my Cingular 8525, unless I perform a soft-reset after connecting the mini-USB connector. I am hoping that it is a problem with the particular unit that I had, as I really like the Garmin products. (I suspect that it may be an issue with the product itself though, as it will charge a T-Mobile SDA, as well as an old Nokia phone not capable of Bluetooth. The 8525 does charge flawlessly when connected to a PC via mini-USB, or the supplied AC adapter, so I'm sure that it's not a problem with the phone).
-- Joe
Edit: After re-reading this, it appears you're using a generic GPS and evaluating software that works with said unit. The Garmin software pretty much only works with the Garmin units as far as I can tell, so it might not be an appropriate solution for you.
TomTom works flawlessly.
Currently i'm on v6.03 but i used 2 previous versions on WM6 with no problems.
Side note, i don't know if its because of v6.03, or WM6 but this version takes a little longer to acquire a valid GPS signal when initially turned on.
MioMap 3.2, TomTom 6.3 & Destinator 6.2 work flawlessly for me...
Destinator still has the tedious lock up issues... other then that MioMap is the best...
walshieau said:
MioMap 3.2, TomTom 6.3 & Destinator 6.2 work flawlessly for me...
Destinator still has the tedious lock up issues... other then that MioMap is the best...
Click to expand...
Click to collapse
does Miomap have voice commands, or just on screen instructions only? Do they make maps for USA?
marscandybars said:
does Miomap have voice commands, or just on screen instructions only? Do they make maps for USA?
Click to expand...
Click to collapse
Both quests = Positive.