error

onlineamiga · 01-31-2006, 01:25 PM

Hi, Im using GPSSecure with xport, I get:

Invalid Parameter set in Open(): The request is not supported.

When i try to connect to the virtual com port. If i close xport and connect direct onto my GPS Receiver then it seems to be connect OK, but doesnt seem to be doing a great job in obtaining a fix.

Any ideas ? Cheers

xBrady · 01-31-2006, 05:25 PM

First thing that I would try is connecting to the virtual port with another GPS application. Do you have anything else you could test it out with?

onlineamiga · 02-01-2006, 08:55 AM

At the moment only a GPS test utility i got with my receiver. just outputs gps data and fix info... and that works fine.

xBrady · 02-01-2006, 11:36 AM

Quote: Originally Posted by onlineamiga

If i close xport and connect direct onto my GPS Receiver then it seems to be connect OK, but doesnt seem to be doing a great job in obtaining a fix.

GPSSecure doesn't effect how well your receiver gets a fix. It only reads what is givin to it. So if you plug in your GPS info utility it is going to have the same problem getting fixes.

What GPS receiver are you using?

onlineamiga · 02-07-2006, 10:18 AM

Well my GPS info utility reports a fix whereas gps secure doesnt. Erm im using some USB non branded piece of crap i think! But its supposed to be fully NMEA compliant. Just comes up as a GPS Locator USB to serial thing.

xBrady · 02-07-2006, 12:09 PM

Quote: Originally Posted by onlineamiga

Well my GPS info utility reports a fix whereas gps secure doesnt. Erm im using some USB non branded piece of crap i think! But its supposed to be fully NMEA compliant. Just comes up as a GPS Locator USB to serial thing.

One thing that may be happening is a difference in what is considered a fix. GPSSecure looks at the HDOP value given by your receiver (just a number saying how accurate the information it is spitting out is), based on that it determines if you have a fix. Your GPS info program may be a little bit more lax on what it considers to be a fix. Are you using this in your house or have you tried it outside too?
Another thing to check is the settings in GPSSecure, make sure they are the com port and baud rate is the same as what you have in your GPS info program.

max-o · 02-08-2006, 02:34 PM

I too am having the same problem. It's as if the program cannot accept input from com ports higher than a certain number as my first virtual com port avaiable is 8. Google Maps, iGuidance, S&T, etc all read the virtual ports fine. When GPSSecure connects directly to the GPS (com 3) it has no problem

wake · 03-16-2006, 06:08 PM

I am having this exact problem.

I am using a USB GPS Receiver.

If I load ONLY GPSSecure and set it to my com port, it works great and gets a fix. However, Live Tracking fails for some reason and I have to force uploads.

If I launch ONLY iGuidance 2.1, it works great and follows me around as I drive.

If I launch GPSSecure with iGuidance 2.1, and choose iGuidance 2.1 as my connectivity option, it states it is connected to iGuidance however I do not get a fix.

I then tried using XPort3 and split my com6 into com7 and com8. iGuidance itself runs great off com7 and com8. If I run GPSSecure and put it on com7 or com8, I get the Open() error. If I set GPSSecure to com6 (the original split com), it crashes completely.

Any advice? I am going from Indiana to Texas here in a week, so I thought I would give this a shot. It will still "work", however I can only have one application running at a time, so I wouldn't be able to log the entire trip as I won't be able to look at the GPS Software itself.

xBrady · 03-19-2006, 12:04 PM

Alright, can you guys do me a favor? Set up xPort however you were setting it up before (when it wasn't working). Then go into your device manager, open up the COM ports tree and print screen it. Then either PM me the image or post it in here.
Thanks

max-o · 03-24-2006, 08:54 PM

Com 8 is being used by S&T. I also noticed that it well sucessfully not connect to a com port when Xport is off. IE if i tell it to connect to com 9 and nothing is there it well say nothing is there instead of giving an error.

nkotch · 04-05-2006, 09:57 AM

Will try and do the above when I'm back in the car, but having the same trouble as these guys. Using Xport to out to ports 12, 13, 14, 15. iGuidance is running fine on COM13 and has a fix. Set GPSsecure to use GPS receiver feed on COM 12 (all the same baud rate) and then I save. When I hit connect on the main program screen I get the error that was described above.

EDIT: Just looked at it in the car and it's similar to above, the ports that i have set in Xport don't show up in the device manager, but iGuidance connected to one of those xport ports still works.

p.nightmare · 04-25-2006, 08:24 AM

same thing.
oziexplorer and mapmokey work well with ports 10 and 11.

xBrady · 04-26-2006, 02:42 PM

It looks as if the DLL I was using won't work with how xport emulates the port. On the rewrite of everything I'm using a different API (the one included in the new .NET framework) instead of the old library which was half some one elses and half mine. I'll have you guys try the new version in a little bit (my senior project will be done tomorrow). If the xPort emulations don't work with the new version then I'll get with Curiosity and see if we can get them compatible with each other. I know gpssecure was working with 2 of the port splitters I used, but the emulated ports also showed up in device manager.

Sonicxtacy02 · 07-11-2006, 05:23 PM

any news with this.. i have this exact problem.

xBrady · 07-19-2006, 09:12 AM

Once again, I'm sorry but I don't check this sub-forum very often anymore. I'll PM curiosity right now and see if we can figure it out.