Hi, if anyone has had success using Destinator PN on the HTC Tytn, I would appreciate any help. I have a GlobalSat BT338 which I had previously used successfully on an O2 ATOM, but recently upgraded to a HTC Tytn. I cannot seem to get a Com Port to work - on Bluetooth pairing - setting an outgoing COM port - can only get Com 0, and Com 2 and Com 4 as available ports. Yet, on the Destinator PN Find GPS mode - only available Com options are Coms 1,5,6,7 and 8.
I use the same receiver, but I have only used TTN6 and iguidance 3. Both allow the selection of the avialable com port (I chose Port 2). If there is no way to do it you kay want to switch the AS port to 2, 4, or 0, and then use the default AS port (port 5) to fix the problem.
First you've got to pair your GPS.
Then go to the "COM" tab in the bluetooth manager
Add a new outgoing port with the GPS as device (do not tick the serial port box)
* Copy the "DestinatorApps/Destinator/Destinator.ini" from the pocket pc to your desktop
* Open this in a hex editor and change where it says C.O.M.6 to the com port of your gps. Mine was Com5 so I just changed the 6 to a 5.
* Copy the "Destinator.ini" file back onto the PPC
I have already had this problem and fixed it myself... do a quick search... there is a file you can download and it shows all com ports... much easier than doing a hex edit, etc...
yes same here - I have got this to work a few months ago with the tytn and destinator pn - cant remember how - but it does work ...
alternatively, get the new destinator PN (6) - it lets you choose all the ports and works super fast!!
Related
This message contains all postings in this thread
dated before January 19th 2003
Subject: NT serial connection solved !
From: Ric. Wilson
Date: 10 Jan, 2003 10:14:34
HI
I posted a couple of days ago with a serial connection problem
on my work laptop AS 3.5/6 to NT 4.00 1381 sp6
I discovered the modem was on com1
I created com2 pushed the modem onto com2 rebooted and it worked
fine.
It seems that com1 must be dedicated to AS or it will not play.
Give it a go
Let me know how you get on
Cheers
Ric.
Subject: NT and Serial
From: Stewart
Date: 12 Jan, 2003 17:17:41
Hi Ric,
Interesting what you say about the modem being on COM1. I am not
at all technical, but have been confused as to why NT control
panel, ports, showed COM1 and COM2 when there is only one serial
port at the back of my laptop. It could well be that I have the
same problem.
Any chance you can expand on your "I created COM2, pushed the
modem to COM2 and rebooted"?? I understand the rebooting bit,
but not the rest of it!
Cheers,
Stewart
Subject: NT
From: Ric
Date: 15 Jan, 2003 17:51:59
Hi Stewart
Go to Control Panel / Modems and see which port your modem uses.
Go to Control Panel / Ports and see how many ports you have
installed.
To get it all to work you MUST have activesync ONLY on COM 1. If
this means uninstalling your modem drivers and pushing them onto
COM2 then so be it. ( If you only have COM 1 installed install
COM 2 using default settings first, then uninstall modem then
reboot, then install modem drivers and push them on to COM 2 not
COM 1when prompted
The term COM ? refers to the drivers for a com port rather than
the actual number of physical ports you have on the machine. 1
com port can use up to 8 COM ? settings.
A bit confusing I know.
If you are still struggling let me know
Subject: serial cable and DCD signal
From: Eddy
Date: 16 Jan, 2003 19:15:25
I made a serial cable myself according to the pin layout as
described under Connectors on this website.
I use Active Sync 3.6 under NT4 and XP as well.
Unfortunately no connection was establised. From an XDA point of
view everything was OK and the XDA sends the word "CLIENT" to
the desktop PC. However the desktop PC did recognize this. And
so no answer was sent to the XDA.
I analysed the connection of a collegue of mine using an IPAQ
and official COMPQ serial cable. It turned out that in that
situation the DCD (Data Carrier Detect) signal was high. On a 9
pin COMport connector this pin 1.
According to the specification of xda-developers.com it should
not be used.
As a solution I connected on the 9 pin COMport connector pin 1
to pin 6. And now everything works fine!
I am happy, but how come nobody else discovered this???
:wink:
Dear friend I'm using BT GPS. In some s/w (like Destinaor 6) there is no problem to select the assign BT port (COM 5 in my JasJam) , but some old s/w (like NaviGuide 3 and more) it refuses to let me choose the BT COM Port, it allow me to choose other port like COM 6 , COM 3 and others which I can not assign the BT COM Port to them. Did someone come across this problem ? Is there any Reg tweak that will allow such s/w to know the existance of the assigned BT Com Ports ?
Please advice.
I came across this problem when using wm5 and old versions of Destinator. I couldnt find a way to get wm5 to "open" up the other com ports so I added to hack the actual program. In Destinator it was in .ini file in hex. not sure about the other programs. Problem was everytime you changed something in the settings of the program it would over write my hacked .ini.
Problem solved !!!
Attached is an application whice enable for me all the COM ports !! just copy to your mobile and run the CAB file attached
i had this exact problem and the only solution i found was a program called Franson GPSGate http://franson.com/gpsgate/ this program allows you to remap the port to enable its useage by destinator, and as a side effect, it also allows you to have multiple programs accessing your gps downstream at once
Hi guys,
I want to connect to activesync on my pc.
The problem is i only have COM6 & COM7 available on my S200,
so I assign the COM6 in Activesync but can't select COM6 in my Bluetooth
utility.
When trying to synch the S200 is giving me cannot find an existing bluetooth partnership with a pc that supports activesync.
Am i'm doing something wrong here?
any help is appreciated
cheers
koenie said:
Hi guys,
I want to connect to activesync on my pc.
The problem is i only have COM6 & COM7 available on my S200,
so I assign the COM6 in Activesync but can't select COM6 in my Bluetooth
utility.
When trying to synch the S200 is giving me cannot find an existing bluetooth partnership with a pc that supports activesync.
Am i'm doing something wrong here?
any help is appreciated
cheers
Click to expand...
Click to collapse
My problem is same to you ,
Any one can help?
leeleeguo said:
My problem is same to you ,
Any one can help?
Click to expand...
Click to collapse
which bluetooth stack are you using?
toshiba?
gokhanmoral said:
which bluetooth stack are you using?
toshiba?
Click to expand...
Click to collapse
Thanks!
My PC is Dell M1210,and the bluetooth module is Dell wireless 355 Module
with Bluetooth 2.0+EDR Technology
leeleeguo said:
Thanks!
My PC is Dell M1210,and the bluetooth module is Dell wireless 355 Module
with Bluetooth 2.0+EDR Technology
Click to expand...
Click to collapse
generally, the incoming serial port for the pc over bluetooth is COM7.
however, sometimes it is not available to select in activesync or wmdc(for vista).
you can try to set it manually. try the followings:
- if your PC and phone is already bound over bluetooth, delete the relationship.
- start -> run -> regedit (enter)
- go to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows CE Services
- you will see a REG_SZ (string) value named as "SerialPort". change it to COM7
- reboot the PC. try to bind over bluetooth again. this time you should see "ActiveSync Service" not "Serial Port" during the binding process. start the binding process from your phone, not from the PC.
if the incoming serial port is different than COM7, then use it. I am sure there is something in the control panel to let you add/delete/modify that setting. check it before starting.
good luck.
gokhanmoral said:
generally, the incoming serial port for the pc over bluetooth is COM7.
however, sometimes it is not available to select in activesync or wmdc(for vista).
you can try to set it manually. try the followings:
- if your PC and phone is already bound over bluetooth, delete the relationship.
- start -> run -> regedit (enter)
- go to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows CE Services
- you will see a REG_SZ (string) value named as "SerialPort". change it to COM7
- reboot the PC. try to bind over bluetooth again. this time you should see "ActiveSync Service" not "Serial Port" during the binding process. start the binding process from your phone, not from the PC.
if the incoming serial port is different than COM7, then use it. I am sure there is something in the control panel to let you add/delete/modify that setting. check it before starting.
good luck.
Click to expand...
Click to collapse
It's ok,also need to del the unused serial port
Thank you
Hello
I've managed to select the incoming port in Activesync to COM6
and set the outgoing port on my S200 to COM6
but the pda is reporting that he doesn't find a computer that supports Activesync, although they are paired
I'm using the Widcomm stack
the widcomm program is reporting these 3 services are available on the pda:
- Connect NPA & Dialup & voice Gateway, serial port is not one of them
hello there i have just got an bluenext gps reciver i connect it to my xda II via bluetooth and then istart tomtom and it says no gps device what shell i do please i need elp
The complete steps for this is in the Wiki under Himalaya/Himalaya Faq:
Pair your bluetooth GPS device with your Himalaya first.
After this, make sure to choose the advanced option which will give you the choice of choosing the serial connection and then which port you want to use.
I always choose Com 5 as this seems to work fastest, most stable etc.
After this, you then leave bluetooth on and in discoverable mode.
After this, load up your software.
The correct com port should then appear in the list of possible com ports for you to choose from (Com 5).
After that, all should be well with the world.
Hello people,
As everyone knows, there are people who cant connect the new Roms with ActiveSync, for those who cant, we will post here the rigth ones.
Let´s go guys, let's do some work for us... and encourage the people to cook for us too!
The Roms tested:
BD's v5 (Blackdragon) - Thanks mkoch5 for test it.
Best Regards
have u tried this?
1. Keep the WM device connected.
2. Go to Start > Start Search.
3. Enter Device Manager or devmgmt.msc to launch the Device Manager window.
4. Look under the Network adapters node for Microsoft Windows Mobile Remote Adapter. If this is not present, skip to step 5. Otherwise, right-click Microsoft Windows Mobile Remote Adapter and choose to Uninstall.
5. Look under the Mobile Devices node for Microsoft USB Sync. If this is not present, skip to step 6. Otherwise, right-click Microsoft USB Sync and choose to Uninstall.
6. Disconnect and reconnect the WM device. The device driver for the PPC Phone will re-install and Windows Mobile Device Center will launch.
exakt said:
have u tried this?
1. Keep the WM device connected.
2. Go to Start > Start Search.
3. Enter Device Manager or devmgmt.msc to launch the Device Manager window.
4. Look under the Network adapters node for Microsoft Windows Mobile Remote Adapter. If this is not present, skip to step 5. Otherwise, right-click Microsoft Windows Mobile Remote Adapter and choose to Uninstall.
5. Look under the Mobile Devices node for Microsoft USB Sync. If this is not present, skip to step 6. Otherwise, right-click Microsoft USB Sync and choose to Uninstall.
6. Disconnect and reconnect the WM device. The device driver for the PPC Phone will re-install and Windows Mobile Device Center will launch.
Click to expand...
Click to collapse
I´m using the activesync 4.5 in windows XP. I can connect the Niki while i´m using older ROMs, but newest, i cant.
regards
can´t help but same with my Niki100
Michael
Please Guys, can anyone cook some ROMS with the old active sync function for those who can´t connect with computer?
Best Reagards
I tried the same ROM on a NIKI200 (the other one is a NIKI100) and Active Sync works perfectly
Someone knows where the difference is between 100 and 200 ?
I have same problem on my XDA Star too. On newer rom (Phoenix and latest Lilly) can not connect with activesync
hmmmmmm flashed the NIKI100 again ...and now it works with Activesync
and also in FAST Mode
Don´t know why ... but it works
Michael
Awsome!
What ROM do you used?
regards
I used BD´s V5 .... and it works ...nearly perfect
Michael
Anyone tested the New LILLY ROM v1.4.5 (Build 20757.1.4.0)?
Has anyone sollution about this problem????