Thread: Iguidance and com port issues.

make sure you have the latest driver from globalstats website. are you using xport? if not, you pretty much need to. just the fact that streets and trips might have still been in control of the gps while you tried iguidance might be part of it

Alright, I tried Xport. It seems to just indicate which com port each device uses, unless I missed something.

choose the port at the top that the GPS reciever is (dont worry about the list at the bottom) then click enable, then in the open boxes below select the ports you want it to output

(sorry its not real descriptive... i dont have it in front of me, just going off memory)

i also have a slight issue with iGuidance 4 with the com port.... i have xPort sending it out to ports 10 and 11 (10 for RR, 11 for iG) and sometimes when i run iG it works, and sometimes it goes back to port 1 and i have to input port 11.... works but is annoying at times... not sure why but ive been too busy / lazy to trouble shoot it yet.

Originally Posted by stonestatue

Alright, I tried Xport. It seems to just indicate which com port each device uses, unless I missed something.

Xport works great. Its purpose is to split the port up so multiple applications (ie. rr and iguidance) can use the port.

You put the input as the actual port that the gps uses in device manager, if your using windows. Then you can specify the output ports that your applications can use.

For example, i connect my gps and in my device manager its assigned as com3. Then in xport, as my input port i would put com3 (i think it will automatically detect the port too), then in my output ports i can use any that aren't in use so they are not being stolen from another application. So, in my output ports i can assign com4,com5. So, in this case if i was using riderunner and iguidance i would assign those output ports to those applications, so that riderunner and iguidance can both use the ports. Make sense?

I uninstalled Microsoft Street and Trips as well as the USB to Serial driver that came with the GPS on the installation disk. I downloaded and installed the driver from GlobalSat's website just in case it's a later version than the disk. Then I restarted.

Now when I use Xport, it won't even detect the GPS. I also tried to manually select the com port assigned to it in the Device Manager, but it isn't listed in the available com ports in the drop down input com ports list. Device Manager assigned com 4, but 4 isn't listed.

iGuidance will only remember 1 digit port numbers. Use something lower than 10.

@stonestatue Uninstall the driver that doesn't work. Install the one that does.

Ya, I think there's some sort of issue with using COM ports above 7, try and use something lower. And don't use xPort3 when troubleshooting, it just adds an extra layer of something that could be broken. Turn it off and just try and pick up the right port in the GPS application. Once you have that working, then get xPort3 working after.

And always have the latest driver, iGuidance wouldn't pick up my receiver neither until I installed the right driver.

In iGuidance, beside the com port setting, make also sure to set the correct baud rate. Alternatively, use the "auto detect" feature of iGuidance to find your GPS receiver.