Related
Hello, all,
we try to connect to the serial port of the XDA, but I cannot open the port COM1:
We have the proper connector, but I have no chance to open the port by software. What can be the reason, do I have to make something on the connectors (bridges ?).
Thanks a lot ...
i initially had this problem using windows xp. i fixed it by changing the settings of the resources (I/O Range and IRQ) COM1 uses in the device manager.
hope this helps.
Thanks, but I do NOT mean the serial port of any connected PC, I mean the serial port at the bottom of XDA.
I programmed it by embedded VC, on other devices this works, but the phone edition seems to disable the port. I can see COM1: in the registry, but it's not getting active.
I read, that I need a null-modem cable, but this also wasn't sucessfull. What should be inside the cable to communicate with any serial device outside the XDA?
Thanks
Make sure the IR port isn't grabbing COM1:
Start/Settings/Connections Tab/Beam
"Receive all incoming beams and select discoverable mode" should be left unchecked. In addition, close (via Settings/System Tab/Memory/Running Programs Tab/Stop) any driver software for accessories like keyboards that connect to the sync/charge port. Then you should be able to connect to COM1.
With respect to a Null Modem: You need to also hardwire some handshaking lines together, so don't abandon the null modem.
Hi,
thanks for the first replies. I already switched off the IrDA, and I can open the COM1: of XDA. Everything seems okay, but no data on TX...
I saw the connector layout on this site, but can (want) somebody to tell me the layout, if I want to do serial data-connection to an external device(not activesync)? I think, I need more hardwires than known by me....
I connected:
RTS (pin 9) with CTS (pin 7)
DCD (pin 6) with DTR (pin 11)
RX (pin 10)
TX (pin 8)
GND (pin 16)
What else can I do ????
sjaeger said:
I connected:
RTS (pin 9) with CTS (pin 7)
DCD (pin 6) with DTR (pin 11)
RX (pin 10)
TX (pin 8)
GND (pin 16)
Click to expand...
Click to collapse
I would attempt to connect DCD to the DTR of the computer at the other end, but am unsure whether this woud make a difference.
We experienced problems with the sreial port in older versions of the ROM. if I remember correctly, things didn't work in 3.00.xx. But I doubt you're using something that old.
Good luck...
Thanks,
but are there any other bridges/hardwires inside to do inside the connector to acivate the serial activity of the port ?
Thanks,
but are there any other bridges/hardwires inside to do inside the connector to acivate the serial activity of the port ?
I also don't have a PC on the other side, it's a device, which has no handshaking ability...
sjaeger said:
Thanks, but I do NOT mean the serial port of any connected PC, I mean the serial port at the bottom of XDA.
I programmed it by embedded VC, on other devices this works, but the phone edition seems to disable the port. I can see COM1: in the registry, but it's not getting active.
I read, that I need a null-modem cable, but this also wasn't sucessfull. What should be inside the cable to communicate with any serial device outside the XDA?
Thanks
Click to expand...
Click to collapse
You do need a null modem adapter. If you are using one, it may not be a proper one.
Or you can use a "serial/modem interface cable" you can get from www.pc-mobile.net in the XDA page.
Does anybody know how to access the hardware serial port (on Blue Angel)? I can use IR (COM1) and Bluetooth (COM4) to send/recieve data, but the bottom pins don't give any voltage. I've tried other ports (to COM9) but the device hangs unless it's COM2.
Here's the test app, select port on the left and then click 'Open Port'. When the port is open, the device is showing what is read at the port. You can click 'Salji' to start/stop sending dummy data via port or "Lista Portova" to list the available ports.
http://www.megaupload.com/?d=T36RIZKE
marko_serb said:
Does anybody know how to access the hardware serial port (on Blue Angel)? I can use IR (COM1) and Bluetooth (COM4) to send/recieve data, but the bottom pins don't give any voltage. I've tried other ports (to COM9) but the device hangs unless it's COM2.
Here's the test app, select port on the left and then click 'Open Port'. When the port is open, the device is showing what is read at the port. You can click 'Salji' to start/stop sending dummy data via port or "Lista Portova" to list the available ports.
http://www.megaupload.com/?d=T36RIZKE
Click to expand...
Click to collapse
You have to deactivate IR to get Serial Port working, as thay use the same port!
(Settings/Connections/Beam/deactivate Receive all incoming beams )
I've tried that, when "Receive all incoming beams" is enabled - COM1 is invisible to the program and reports error, when disabled - the IR becomes COM1
marko_serb said:
I've tried that, when "Receive all incoming beams" is enabled - COM1 is invisible to the program and reports error, when disabled - the IR becomes COM1
Click to expand...
Click to collapse
Try the attached file by haicom.
Serial and USB crandle have different pin-out!
http://forum.xda-developers.com/wiki/index.php?title=Connectors
Serial should be Com2 and is usable when Com1/IR is disabled.
Thanks! I'll give it a try as soon as I find a way to disable IR (and find some time to play with it)
I have a Magellan 315 handheld reciever. There is a dataport on it, and you can hook it up to a laptop to upload more maps to it. My question is how do you kow if a GPS unit is suitable for use as just a reciever for a PDA? If I butcher a cable to hook it to my XDA, which pins do I use in the connector? I have read the pinouts discussions and am still confused. Thanks.
You could hook it up if you have the gps to serial port cable for the gps, a serial to pc cable for the xda and a null modem adaptor in between them. Then set your port on xda to com 1, nmea 4800.
I was just going to "engineer" a cable for it, since the data cable costs about $50 US. I just didnt' know if handheld recievers were designed to output the coordinates like I need.
The gps will output nmea sentences, your mapping software will then use these to overlay your position on the map.
Thanks alot Cruisin
For the benefit of others considering using a handheld receiver in this way, you will need to confirm that your GPS has 'NMEA' out which is the data feed you require to drive an external application. The fact that it can connect to a PC via a serial cable to upload/download waypoint does not mean this is necessarily so. Whilst most modern handhelds do have NMEA out the older models didn't always have the facility.
For the Magellan 315, to turn NMEA output on, Press the MENU key then select 'Setup'. Press ENTER. Select 'NMEA' and press ENTER. Select 'V2.1 GSA' and then press ENTER. Next set the baud rate. Press MENU then select 'Setup' and press ENTER. Next Select 'BAUD RATE' and press enter. Select 4800 for the baud rate. Press ENTER and you are done
That is exactly what I needed to know! You da man Griffog! 8)
But one more q: can I use any map software I want (most, not any)?
You can use the 315 to drive any GPS enabled app be it on a PC or a PDA that accepts NMEA input (it's the defacto standard so most do) this includes Streets & Trips, MapPoint etc on the Pc and TomTom Navigator, CoPilot, and many more on the PDA
For one final bit of clarity.
Which wires from a GPS (315 in my case) go to which pins on the XDA (reference the wiki connectors page if needed)? I know this quesiton has been asked, but I can't seem to find a clear cut answer.
Thank you sooooo much!
I have recently "upgraded" from xdaII to xdaIIs and I'm having a few problems. I have upgraded the BT stack to 3500 but I still can seem to connect to my tomtom gps. Device sees it but tomtom 3 cant. I'm completely confused by the connection wizard- none of the profiles seems to fit gps. I also dont seem to be able to send or receive files from my old xdaII. What am I doing wrong?
I'm also a little confused about roms. Do I need to upgrade my rom? Is there a simple way avoiding anything too technical (I've read about "country codes" and other wierd stuff). My current config is:
ROM: 1.12.62
Radio: 1.02.00
Protocol: 1337.32
ExtROM: 1.12.178
Could someone please help! I only have a few days to decide if I want to keep it or stick with my xdaII...
Gps's use the serial profile to transmit the data over - its like a virtual serial connection - so you need to tell tomtom to look on a com port AFAIK,.
For eample in my Tomtom list of connections there is one called 'BT on Com6, ' which is the bluetooth comport on my unit.
But there are also listed more com ports...
Com5
Com4
Bluetooth Serial port Com7
The XDA only actually has 1 com port (com1) so any other are virtual ports created by various software, you just need to find out which one is the one for the GPS...
So in "tomtom gps v3.07" I go to the gps tab and by default its set to infrared port. I change to "BT on com6" and click OK. When I restart the program it always resets to "infrared port" even if I try a different port. Really am stuck- never had any problems with my xdaII- just put in BT port and it picked it up automatically...
The problem is it's not always the same com port for different devices - firstly does your unit have the widcoom stack version of are you on the microsoft stack..
Whichever you have you need to find where the BT com port is configured..
On my widcomm i go to 'bluetooth setting' ; 'services' ; "serial port'; 'advanced'
in there it says...
inbound com port : 6
outbound com port : 7
so the incoming com port on my bluetooth is 6 hence the 'BT com port on 6' listed in my tomtom gps.
so you need to find your BLuetooth com port and find out which com port number it is set to. Not sure as to why tomtom gps does not save your settings, the only thing I can think of is becuase it never gets a valid signal from the comport select, and does not save the change unless it does.
Also: I assume the gps unti has a pairing with your XDA unit?
So does the widcom stack work on the xdaIIs? If so where can get it?
Sorry: I cannot be certiain the widcomm works with the IIs, but is can be downloaded from this site if you are willling to try, just do a search oin widcoom, and you will find a lot of entries...
For the MS BT stack; look under start, settings,System tab. There is a icon labeleld Bluetooth settings in there you can see/set the com ports for the bluetooth link. they also need to be enabled witch a check box before they will work...
So on "bluetooth seetings" serial port/advanced I have inbound COM port 5 and Outbound COM port 6. Below it says "Default device for outgoing serial connections: TomTom Wireless GPS. Display the device selection screen the next time an outgoing serial connection is attempted" next to a ticked box. I have tried bt com 5 and 6 in the gps settings and it wont save or recognise either. I can, however, pair and connect to the device in my BT manager but Tomtom doesnt recognise it...
Hmmm - all sound ok to me but I currently use a wired GPS, so I have not actually done it. I'm afraid I'm as stuk as you are now...
Sorry bro- I have sorted this now. Thanks...
For me, I just selected Comm 5 from the GPS status drop down and it works like magic!
is there anyone using WM5 ROM's on a BA that succesfully uses the integrated GPS virtualizer as can be found as "GPS" button in the settings->connections
In more detail this is what i find:
Ozi seems to be the only gps using application that can setup an active bluetooth connection to an GPS device using the build-in GPS virtualizer of WM5 wich is called Intermediate GPS driver and wich can be found via the "GPS" button at the connections settings page of your device.
The use of this virtualizer is that you can simultanious have multiple applications active that use GPS data.
Next info is what i tested so far, maybe others recognize and/or understand much better then i do how this should work. Any help is appreciated.
I think it has something to do with discovering, or being allowed to discover by WM5, COM ports.
Just to make sure we're talking the same issue a little chain:
- there's a BT-GPS device
- discovered via BT-applet on WM5
- on my bt-gps: if the blue light goes on&off it's not connected, if its steady on it's connected to a PDA
NEW in WM5 is that one has to seperatly define:
- the service the bt-gps needs to use: just one choice "serial services"
- next on a seperate tab one needs to define an new outgoing and/or incoming port
- one can choose only the discovered bt-gps
- one can only choose a COM port numbered 6, 7 or 8 and one defines the baudrate here.
- i choose COM6 and 57600baud
From this point there is a COM6 available for applications, any application i start is able to set-up the bt-gps connection and read gps-data.
- ozi explorer, tomtom, igo, reperion
- all setup with listening to COM6
- all make the blue-light on the gps-device go steady on
- all disconnect from the gps-device when exiting the application, blue-light on gps-device starts flashing
Next step is using the intermediate gps driver incorporated in WM5 to virtualize&share the gps-device.
- on the GPS-applet define COM6 as the h/w port with 57600 baudrate
- on the GPS-applet define COM7 as the s/w port, choices are COM0/9 and GPD1/9
- i defined COM7 as the s/w port.
So now with COM7 we are on the virtual side of the GPS-applet
When i start ozi-explorer i can choose several ports for the GPS
- COM1/4 for specific goals
- COM6 (recognized by ozi as Bluetooth Serial Port)
- COM7 (recognized by ozi as ActiveDevice)
Activating the GPS function in Ozi with GPS-port set to COM7 will make ozi to talk to the virtualside of the intermediate gps driver and then via this driver will initiate the bt-gps connection (blue light on the gps-device will go steady on) and start reading gps-data. Stopping&starting the gps function in ozi will nicely turn the bt-gps connection off&on.
So far so good.
Important note: In the registry one can find \HKLM\System\CurrentControlSet\GPS Intermediate Driver\ActiveDevice
According to the writer of gpsid.dll http://msdn.microsoft.com/library/d...rmediatedriverinputsourceregistrysettings.asp this is the place to look for the gps-device definitions.
As you might have read above the name "ActiveDevice" is exactly what ozi found as tag for COM7
All the other gps using product like Igo see COM7 as "unnamed" port.
So it looks as if the other app's, including Fransons serial tools, don't look at the right place in the registry for the info on COM7. And since Ozi does work well i think it's a problem to be resolved by the navigation application developers and not on WM5 level.
And once ozi setup the connection all the other apps suddenly do find COM7 and read GPS data. From that point on i can stop ozi, the connection to the bt-gps will stay. When i then stop igo or reperion or whatever, then the bt-gps will be disconnected.
Then a bit about gpsgate, maybe to get some more idea on how the behaviour is in wm5.
- i totaly inactivate the Intermediate GPS driver from WM5 (b.t.w. i softreset after every change to make sure it's a clean test)
- all the nav. Apps can directly connect to COM6 (see above)
- gpsgate will only give me COM1/4 and COM9 as an option
- COM6/7/8, the only options i have as h/w port on the bt-gps are NOT seen by gpsgate
- then i re-active the Intermediate GPS driver and now gpsgate gives me the option of COM7 as input and i setup a virtual port in gpsgate COM8.
- quite useless, a gps-virtualizer which can only listen to some other driver's virtual port.
- but then it act as all the other app's. Only when a bt-gps connection is setup via ozi, gpsgate will read data on the virtual com7 port.
- this gives the weard situation:
- bt-gps comes in on h/w COM6
- Intermediate GPS driver from WM5 listens to port6 and virtualizes that to COM7
- Ozi explorer initiate the connection and listens to COM7
- gpsgate will also listen to virtual COM7, where gpsgate thinks this is the h/w input side
- gpsgate will passthrue to its own virtual port COM8
- reperion i configured to listen to COM8, and reperion will succesfully read data from COM8, via COM7, via COM6.
Still with me? Maybe you need to draw this out on a little piece of paper ;-)
Anyway, it looks as if most gps-using s/w don't setup the gps-communication up in a proper way to be handled by the Intermediate GPS driver. Ozi Explorer is the positive exception here.
Found an app on SourceForge called GPSproxy... first off it enables me to use Garmin Que, and all the MapSource maps with my non Garmin BT-GPS... but it also enables the use of Virtual COM Ports in WM5... so far I have had Garmin Que, with at least two of the following: TomTom, Vito Navigator II and Virtual Earth Mobile running at the same time on my BA... still playing, I'll update after my trip to Scotland...
thx for the info. took me a while to get it all my pda via gprs on holiday and no desktop around.
just can't get the virtual ports passing data. it works when mapping one port to another via ' settings' in gpsproxy. but when I add a port in 'virtual port' settings it is recognized in navprogs, but gps data comes through.
I turned off the internal gps-applet
any tips on how you set it up.
thx.
Have you guys tried these?
http://www.pocketgear.com/software_detail.asp?id=22697
http://franson.com/gpsgate/
We're judging them in the PocketPC Magazine Awards.
V
yep, tried it. doesn't pickup the right definitions from wm5 registry, doesn't setup the comms to the gps. and when asking for support just blaming microsoft, so i'm not thrilled.
so far the only good one is ozi-explorer. picks up all the right registry values, realtime, no softresets or whatever needed. just plug&play on bt-gps & wired gps.
I was using Mapking 7 and Agis 1.66 beta when a friend introduced me to Garmin que. I managed to use GPSProxy 2.2 to run Garmin Que 2.9 with Agis concurrently but was not able to run Garmin que and Mapking concurrently. If I don't use Garmin Que and use WM 5 GPS control, I can run Agis and Mapking together but not Garmin Que.
Garmin Que needs at least 1 available port as virtual port to support Garmin Que protocol and another available port as virtual port to run another GPS programme. I'm using a O2 XDA IIs and I can only manage to squeeze out com port 7 for Garmin Que protocol and com port 0 which is not supported in Mapking. Agis is able to use com port 0.
After searching for about a week, I realised that if I don't need to use Infra Red, I can make use of that com port. I used Task Manager v2.1 by FdcSoft to unload the infra red dll (IRCOMM.DLL) and got hold of com port 3, which I was able to create as a virtual port.
Now I can run Garmin Que and Agis or Garmin and Mapking using GPSProxy.
GPS port is com port 6.
Garmin Que Protocol is com port 7
Garmin Que output port is com port 3
The only issue I have now is to find out a way to disable com port 3 by default so that I don't need to do it after each soft reset. Any help here would be most appreciated.
xdaradar said:
is there anyone using WM5 ROM's on a BA that succesfully uses the integrated GPS virtualizer as can be found as "GPS" button in the settings->connections
In more detail this is what i find:
Ozi seems to be the only gps using application that can setup an active bluetooth connection to an GPS device using the build-in GPS virtualizer of WM5 wich is called Intermediate GPS driver and wich can be found via the "GPS" button at the connections settings page of your device.
The use of this virtualizer is that you can simultanious have multiple applications active that use GPS data.
Next info is what i tested so far, maybe others recognize and/or understand much better then i do how this should work. Any help is appreciated.
I think it has something to do with discovering, or being allowed to discover by WM5, COM ports.
Just to make sure we're talking the same issue a little chain:
- there's a BT-GPS device
- discovered via BT-applet on WM5
- on my bt-gps: if the blue light goes on&off it's not connected, if its steady on it's connected to a PDA
NEW in WM5 is that one has to seperatly define:
- the service the bt-gps needs to use: just one choice "serial services"
- next on a seperate tab one needs to define an new outgoing and/or incoming port
- one can choose only the discovered bt-gps
- one can only choose a COM port numbered 6, 7 or 8 and one defines the baudrate here.
- i choose COM6 and 57600baud
From this point there is a COM6 available for applications, any application i start is able to set-up the bt-gps connection and read gps-data.
- ozi explorer, tomtom, igo, reperion
- all setup with listening to COM6
- all make the blue-light on the gps-device go steady on
- all disconnect from the gps-device when exiting the application, blue-light on gps-device starts flashing
Next step is using the intermediate gps driver incorporated in WM5 to virtualize&share the gps-device.
- on the GPS-applet define COM6 as the h/w port with 57600 baudrate
- on the GPS-applet define COM7 as the s/w port, choices are COM0/9 and GPD1/9
- i defined COM7 as the s/w port.
So now with COM7 we are on the virtual side of the GPS-applet
When i start ozi-explorer i can choose several ports for the GPS
- COM1/4 for specific goals
- COM6 (recognized by ozi as Bluetooth Serial Port)
- COM7 (recognized by ozi as ActiveDevice)
Activating the GPS function in Ozi with GPS-port set to COM7 will make ozi to talk to the virtualside of the intermediate gps driver and then via this driver will initiate the bt-gps connection (blue light on the gps-device will go steady on) and start reading gps-data. Stopping&starting the gps function in ozi will nicely turn the bt-gps connection off&on.
So far so good.
Important note: In the registry one can find \HKLM\System\CurrentControlSet\GPS Intermediate Driver\ActiveDevice
According to the writer of gpsid.dll http://msdn.microsoft.com/library/d...rmediatedriverinputsourceregistrysettings.asp this is the place to look for the gps-device definitions.
As you might have read above the name "ActiveDevice" is exactly what ozi found as tag for COM7
All the other gps using product like Igo see COM7 as "unnamed" port.
So it looks as if the other app's, including Fransons serial tools, don't look at the right place in the registry for the info on COM7. And since Ozi does work well i think it's a problem to be resolved by the navigation application developers and not on WM5 level.
And once ozi setup the connection all the other apps suddenly do find COM7 and read GPS data. From that point on i can stop ozi, the connection to the bt-gps will stay. When i then stop igo or reperion or whatever, then the bt-gps will be disconnected.
Then a bit about gpsgate, maybe to get some more idea on how the behaviour is in wm5.
- i totaly inactivate the Intermediate GPS driver from WM5 (b.t.w. i softreset after every change to make sure it's a clean test)
- all the nav. Apps can directly connect to COM6 (see above)
- gpsgate will only give me COM1/4 and COM9 as an option
- COM6/7/8, the only options i have as h/w port on the bt-gps are NOT seen by gpsgate
- then i re-active the Intermediate GPS driver and now gpsgate gives me the option of COM7 as input and i setup a virtual port in gpsgate COM8.
- quite useless, a gps-virtualizer which can only listen to some other driver's virtual port.
- but then it act as all the other app's. Only when a bt-gps connection is setup via ozi, gpsgate will read data on the virtual com7 port.
- this gives the weard situation:
- bt-gps comes in on h/w COM6
- Intermediate GPS driver from WM5 listens to port6 and virtualizes that to COM7
- Ozi explorer initiate the connection and listens to COM7
- gpsgate will also listen to virtual COM7, where gpsgate thinks this is the h/w input side
- gpsgate will passthrue to its own virtual port COM8
- reperion i configured to listen to COM8, and reperion will succesfully read data from COM8, via COM7, via COM6.
Still with me? Maybe you need to draw this out on a little piece of paper ;-)
Anyway, it looks as if most gps-using s/w don't setup the gps-communication up in a proper way to be handled by the Intermediate GPS driver. Ozi Explorer is the positive exception here.
Click to expand...
Click to collapse
wow wow wow....
I read it twice... I will read it again... because it's a little hard to understand ! (I took my piece of paper )
But I think I've got solution to my GPS prb here !
For me this is the solution - Tmob MDA Vario II - Cingular rom
IT WORKS !!!! BUT YOU HAVE TO CREATE TWO VIRTUAL PORTS - USE PORTSPLITTER !!!
All I had to do is download http://www.gpsmeter.com/ portsplitter as discussed in the other threads, HOWEVER......
Instead of what manuals seem to say, even from other softwarez like GPSGate, create TWO or more VIRTUAL ports in PORTSPLITTER!! Connect each GPS app to a DIFFERENT VIRTUAL PORT.
Also, when pairing and configuring your GPS, try taking a high Comport like 9. Go down one if no success.
Then when configuring PORTSPLITTER, don't be alarmed that your COMPORT isn't in the drop down list, MANUALLY enter "COMx" without the usual ":" where x stands for a number..the high real COM portnumber you configured when pairing/setting up.
You must use your keyboard or the stylus to manually enter the Comport if it is not in your dropdown list in PORTSPLITTER..
for speedreaders :
install PORTSPLITTER http://www.gpsmeter.com
use highest physical COMport available to pair your GPS
Define TWO virtual ports (instead of what seems to be written everywhere or am I really lame?)
Connect each Application to different virtual ports
My setup on a T-Mobile MDA Vario II (with Cingular ROM)
Physical Port 9
Virtual Ports in PORTSPLITTER 4,8
Hardware COMport in PORTSPLITTER (COM9 had to manually enter it, it was unavailable from drop down.... .... ...)
TomTom Navigator mapped to virtual COM8 (Didn't show up in TOMTOM until PORTSPLITTER running and connected to GPS.. ..)
Reperion *sweet favorite GPS app" mapped to Virtual COMPort 4 (Reperion eats all ports, no problems there....)
Please o please report...
jppech said:
wow wow wow....
I read it twice... I will read it again... because it's a little hard to understand ! (I took my piece of paper )
But I think I've got solution to my GPS prb here !
Click to expand...
Click to collapse
Yes, I also have some problems in going through this text
I have a problem with Ozi and external GPS receiver as well, I do not know how to use the information i this post, perhaps if I tell you what the problem is you could help me
I have the FS Loox n560 with a built in GPS receiver but due to its rather poor reception I decided to buy an external device.
So far so good
Ozi has no problem in using the internal GPS, I simply choose the right COM port and the receiver switches on automatically.
But the problem is to use the external GSP receiver.
OZI can use only a limited number of COM ports (1,2,3,5,6,8)
COM 6 is the predefined software GPS port and COM 8 is the hardware port.
I cannot associate my BT GPS receiver with any of these ports.
Port splitter also does not help since it also can split only ports that I cannot associate with my BT GPS receiver.
I have been wondering how I could make use of my external GPS receiver with OZI???
Do you have any idea how to handle this probem?
my i-mate kjam have only 6 and 7, how can i have more???
my i-mate kjam have only 6 and 7, how can i have more???
many GPS softwares are looking for different ones.
please help me
Hi All
Thanks for creating such a great site - its become a total lifeline for me with my XDA.
I need some help on setting up my sat nav. I have Tom Tom 5 put on a 1gig SD card, and I'm using a fortuna GPS U2 receiver which has a USB connector one end, a connector to the PDA in the middle and a PS2 connector to the GPS antenna on the other end.
Been trying to configure it in Tom Tom, I know I need to set the baud rate to 4800 as per fortuna's website, but does anyone know what I should tell the system the GPS is connected to? I have a number of options:
Com9
Serial Cable on Com 1
Serial on USB
Infared Port
Serial cable on Com 2.
I've sat out in the car an played around but can't get it to pick up a signal and I'm ondering whether its me setting it up wrong that isn't helping.
Please...can anyone help me?
Simon
try this
on your phone go into settings then connections then beam and untick beam then in tomtom go into change preferences then show gps status then into configure select other gps receiver then select com1 try this if you search wallaby forum there is lots of post on this
jay
try this
on your phone go into settings then connections then beam and untick beam then in tomtom go into change preferences then show gps status then into configure select other gps receiver then select com1 try this if you search wallaby forum there is lots of post on this some of these cables don't work i got one off ebay said it would work but never had to change the wiring look at thishttp://wiki.xda-developers.com/index.php?pagename=Connectors
jay
Thanks Jay - after lots of swearing and soldering I have now reassigned the pins and so far all seems well. The only thing I'm not getting at the moment is audio out of the speaker - however I do get audio when the headset is connected. Does anyone have any ideas?
audio
turn the audio on in tomtom its in the settings