I have a box which converts gps/nmea to irda format, I choose irda in the tomtom port settings and nmea 4800, it works fine with ipaq 1910, ipaq 3850 etc, however when I try it on xda the system slows to a crawl once I choose "infrared", no signal is found and the system eventually locks, any idea what the difference is betwenn the ipaq irda and the xda. Am I missing something obvious?
I have installed device manager on the xda, it shows the irda port as com 3, however tomtom just offers infrared port, doesnt show com 3, but as I said before, if I choose infrared port it produces a lock up of the system after an almost total slowdown of the system. It just seems weird to me that it will work on the other pocket pc'c.
Related
Can anybody tell me how to use the infrared port for TOMTOM navigator, I am able to use it on all the ipaqs that I have including 3630, 1910, 3850, 3870, 3970 etc, in the drop down list for gps settings on the ipaq it shows one as "generic irda", and works fine, however in the xda settings for gps under tomtom it shows "infrared port", if I choose it I get a slow down of system and eventual lockup, is there something different about the ports or protocol? maybe the speed, any help greatly appreciated as I am trying to run wireless without bluetooth and irda seemed the way to do it. . The ir port works perfectly for file transfer etc. Thanks in advance.
Dear Friends,
I bought an MDA 2 (QTEK2020) and a wired XAIOX X3 GPS receiver and installed TOMTOM Navigator 3.01
The Xaiox is a rather new type I think (can receive up to 16 satellites)
I saw in the list of GPS Receivers that this brand XAIOX was not in, but on the website of Xaiox is mentionned that the gps protocol is NMEA 0183v3 compatible and you should pick 9600 baud rate.
In the TomTom list I saw NMEA 0183v2 9600 (version 2 only). I checked this one and waited 45 minutes,but didn't get any connection.
The field 'receive incomming beams' (like infrared,...) is set out,as i read this could block an incomming port like the receiver.
My Xaiox receiver has no lights,so I can't see any status. It had a serial cable out,and i bought a small piece to convert to USB, and this USB connects to a smaller type of usb on the bottom of the MDA2.
I'm not sure if I should choose 'Serial on Com1' or Serial on USB. But I tried both of them and still no connection. I also tried all of the other brands in the list like Destinator 3,SIRF 9600,TOMTOM,... but no connection.
This GPS receiver is brand new, and I tried it at home with power cable in, cause i the gps receiver had to load also. Also on the road no connection.
I updated to TomTom 3.03 but no change.
1>Is the GPS receiver NMEA protocol V3 too high for the one in the TomTom Navigator list (NMEA v2 only)?
2>Do I choose the wrong port or gps receiver model ?
3>Do I have to close phone connections in order to use GPS ?
I tried 'Turn Flight Mode Off' but it didn't work either...strange stuff...
Thanks and a happy 2005 everyone!!!![/b]
Usb will not work, it will need to be wired for serial connection, what is this mini usb converter you are using? The phone is not capable of communicating with a usb gps receiver because both the gps and the phone are usb slave devices and have no capability to talk to one another.
Hello,
I bought an MDA 2 (QTEK2020) and a wired XAIOX X3 GPS receiver and installed TOMTOM Navigator 3.01
I have 1.72.00WWE latest rom version.
The Xaiox is a rather new type I think (can receive up to 16 satellites)
I saw in the list of GPS Receivers that this brand XAIOX was not in, but on the website of Xaiox is mentionned that the gps protocol is NMEA 0183v3 compatible and you should pick 9600 baud rate.
In the TomTom list I saw NMEA 0183v2 9600 (version 2 only). I checked this one and waited 45 minutes,but didn't get any connection.
I always see GPS SIGNAL UNRELIABLE
The field 'receive incomming beams' (like infrared,...) is set out,as i read this could block an incomming port like the receiver.
My Xaiox receiver has no lights,so I can't see any status. It had a serial cable out,and i bought a small piece to convert to USB, and this USB connects to a smaller type of usb on the bottom of the MDA2.
I'm not sure if I should choose 'Serial on Com1' or Serial on USB. But I tried both of them and still no connection. I also tried all of the other brands in the list like Destinator 3,SIRF 9600,TOMTOM,... but no connection.
This GPS receiver is brand new, and I tried it at home with power cable in, cause the gps receiver had to load also. Also on the road no connection.
I updated to TomTom 3.03 but no change.
1>Is the GPS receiver NMEA protocol V3 too high for the one in the TomTom Navigator list (NMEA v2 only)?
2>Do I choose the wrong port or gps receiver model ?
3>Do I have to close phone connections in order to use GPS ?
I tried 'Turn Flight Mode Off' but it didn't work either...strange stuff...
Thanks and a happy 2005 everyone!!!!
ir beamsa receive off
Hello,
Try to switch of the infrared you can find his under connections
you will have a com1 now and i think it will work
greatings and happy newyear!
I have updated my XDAii with WM2005 (1.60c), everything I tested works fine, but I only have a problem with MN4.2 and an original Navigon BT Mouse.
I have changed the two .ini-files (prefs.ini + spgps.ini) to COM4 (the outgoing port).
Switching on the BT-Mouse the blue BT-LED of the mouse is flashing but after starting of MN the BT-LED of the mouse stays off and there's no connection.
I've never seen the mouse with no BT-LED before, because when the mouse is on BT is also on.
It seems that MN says the mouse to switch off BT ???
With Navio (for example) the connection is working on COM4.
It also worked with WM2003.
Has anybody any ideas?
Greetings
ossi
I use the GNS 5840 BT/TMC receiver.
It seems that the WM 5.0 BT stack does not allow for serial connection at 38400 baud which is needed by GNS/Navigon receivers.
I cannot connect at all to my receiver.
Error message from CruxView: "Could not set baudrate"
Sascha
My mouse is running with 4800 Baud and with Navio it works, only with MN4.2 i have this problem.
Ossi
The original Navigon GPS receiver (Navigon modular) which was shipped with MN|4.x is manufactured by GNS and runs on 38400 baud.
Sascha
It's an updated MN4.2 (i think 1.5 was the version with my receiver) and it worked with WM2003.
ossi
Did you guys realize all WM6 versions posted here have Bluetooth Problems ?
Does any1 of you try using a bluetooth GPS with tomtom and wm6 on prophet ?
Here is the problem. On preferences of bluetooth you can add connections then link them. after that you do virtual ports on wich the connection is selected.
Now here comes the buggy part. on wm5 it worked you could choose Incoming and Outgoing ports wich is needed to control and link to a external GPS device. Since crystal, shadow ... and all these roms its not possible to define a Incoming Port thats why TOMTOM in my case does not work anymore. if i downgrade to wm5 and set a incoming port everything runs fine.
Do you know something about this Problem ?
i am currently using tomtom6 with a holux gps bluetooth receiver and i have no problems. you just have to pair your devices and then setup an outgoing com port. even if bluetooth is off, tomtom manages to activate it and connect to my gps device - tested on crystalV5
same here with holux. just pair devices, make outgoing port, setup gps in tomtom, and no problemo. no need for an incoming port.
What problems?
I have been flashing the different WM6 roms and I have no problems whatsoever in using them with my BT GPS. Do the actions by the two previous posts before me and you should not have a problem. Cheers!
It looks like it is not a bug but a feature you describe! Keep in mind that newer software is developped to make things easier...
I use Totom with the original Tomtom BT receiver and I don't have to make any setting or pairing at all. All is taken care of by Tomtom and WM without any interaction by me. Convinient!
alphazero said:
Did you guys realize all WM6 versions posted here have Bluetooth Problems ?
Does any1 of you try using a bluetooth GPS with tomtom and wm6 on prophet ?
Here is the problem. On preferences of bluetooth you can add connections then link them. after that you do virtual ports on wich the connection is selected.
Now here comes the buggy part. on wm5 it worked you could choose Incoming and Outgoing ports wich is needed to control and link to a external GPS device. Since crystal, shadow ... and all these roms its not possible to define a Incoming Port thats why TOMTOM in my case does not work anymore. if i downgrade to wm5 and set a incoming port everything runs fine.
Do you know something about this Problem ?
Click to expand...
Click to collapse
I am having exactly the same problem as you. I have used different WM6.1 rom and the "New Incoming Port" option doesn't show up after i connect my Holux GPS receiver..
yes ihave the same problem with the shadows roms ( TE & CE & ... )
use the korand 3.1 rom thats good ( not have BT problem )
sorry of my english
I have SLIM BT GPS some problem with Google Maps - but I have overcome them by manually setting the GPS in Google Maps options. Woks cool..
From the other hand I have strange problems with sending files from other devices to my JAMin.
I am not sure but the solution is to remove JAMin from the list of paired devices on PC/NOKIA and then You can send files to JAMin. If JAMin is on the list of paired devices - sending do not work.
Best
Use or NDrive I have no problem at WM6
cannot create BT handsfree profile
I'm using Korand's WWE 3.1, WM6.1 ROM - it is excellent, thanks Korand for your work
The only issue I have is with the BT: I have linked up TomTom, and CompeLand via GPSGate fine, and everything works perfectly. However, I have not been able to completely pair my car handsfree.
It took a while to add the device, but I eventually managed it. In settings/Devices, if I press & hold on this device, I get just edit or delete, but set as Hands-free, set as Wireless Stereo are greyed out.
And in the Com ports tab, there should be an option for New Outgoing Port, but it's blank, so I can't tell WM how to connect this device.
Would any kind soul know how to resolve this (any cabs?)
tia
Paul
possible solution to BT ports issue
Posted this on Korand 3.1 WWE (WM6.1), posting it here so that the information is not missed:
in the Output tab of GPS gate, you can add all sorts of ports, including COM ports.
Once you decide to choose the Add COM port option, you can then choose which COM port you want to add. I added COM3 and COM6. I had all sort of problems after that, the device was maxing out on processor and memory. So I removed COM3, and the device runs OK again.
I suspect - and hope - that COM6 is the one for my car handsfree, since I had it running whilst both these ports were enabled. I need to research this a bit more, but it's promising so far
(there is also a virtual activesync port which runs very well for syncing).
These COM ports do not show up in the BT COM ports tab, nor is the "new outgoing port" option available, but this seems to be the way to go
People that have BT problems and they are using any WM6.1 in my opinion they must go back to WM6 and your problem is solved.
I've tried A LOT of WM6.1 and i had problems with BT. But any WM6 rom works fine to me.
I think we should wait for a WM7 (when it comes some day ) to see if the problem is solved. At the mid -time stick with WM6 imo.