I just pushed an update that fixes it, try it. 

Windows 11 version - found that a previous version download works and then the current version will install over the top.

What windows version?

TYVM!

I have it working.

-Aubrey

This is the link

https://www.turbo-play.com/update2/tu.php?p=99fc8ed0-fafa-4bd9-9f10-0c923392dd59&f=99fc8ed0-fafa-4bd9-9f10-0c923392dd51

While the dialog box only has up to 38400 listed, I have been successful with a 115200 baud device, by just hand entering the baud rate when setting up the gpsdirect service.

I haven't figured out how to set the baud rate for the transfer service, yet, but for the gpsdirect service, 57600 should work if you just hand type it in instead of pick an option from the dropdown.

Sorry that took me so long, was busy with stuff. I'd want to see that live, can we get connected in some facebook/skype?

There's a way to set a fixed XYZ, it's in the "Installation options" for the GPSDirect in GPSComplete.    

There's an old app I 'd created to do that, I 've to dig it someway. Perhaps you can find some "GPS IP Sharing" app in the android store meanwhile?    

I guess you have used GPSReverse to create a port. Try opening it with PuTTy.

Try the transfer tool (GPSDirect as 'Inject'. then the Transfer tool FROM the bluetooth com port TO the driver).

Enable the 'tell windows I always have data' option in installing GPSDirect.    

Not with the simulator (which picks random XY on first call) but you can use some Android server which posts XY NMEA to GPSComplete.

Hello,

Thank you for your prompt response.
I see that it does not return about the altitude. Understood.

Regards.

As I see from the docs (https://learn.microsoft.com/en-us/uwp/api/windows.devices.geolocation.geoposition?view=winrt-22621) it only returns lon and lat. I will take another look.    

Yes, I'm currently working on it.    

Thanks for the reply.  I thought that I had read where you had already added UDP as an option.  I have checked and the Sierra Wireless MP70 will only send the NMEA reports over UDP.

Do you expect to have the UDP option in the near future?

Thanks

Zach

If your data is UDP then I'm currently working on the Transfer Tool to work with UDP servers (currently only TCP).    

I can not seem to upload the screen shots.  The site disconnects.

For the Sensor Driver Installation I have NMEA Source as Injection, everything else is default.

For the Transfer Tool I have Source as IP:Port (TCP Client) and 192.168.13.31:17335.  Destination is Inject with nothing else.

When I look at the Sensor Explorer I can see the GPSDirect Sensor but there is no data except the Time stamp.

If I try the Telnet Tool, UDP Accept - Port 17335 I do not get anything.  When I try the UDP Accept - Port 22335 I do not get anything.

When I run Wire Shark I am able to see captures with Source: 192.168.13.31 Destination: 192.168.13.100 Protocol UDP Info: 17335 -> 22335 Len=238.  These show the NMEA strings in the payload.

Thanks

Zach

When I can get the Port scan to show anything it does send the NMEA sentences.

I will give it another try to see if I can grab some screen shots of what I am seeing.

Is there any User Guide available?

Thanks

Zach

No, the destination is the injection to the driver. Does the manual port scanning of 192.168.13.31:17335 (use the testing TCP out tool) return NMEA strings?

Probably some corrupt Windows installation.

Does bing maps work?

Can you please explain how to use the UDP injection feature?  I have my modem reporting the NMEA data to UDP 22339.  It is reporting it to the IP address that the computer takes on when it connects. 

In GPSComplete (Transfer Tool) I have the following:
Source - TCP/UDP Server
xx.xxx.x.xxx:22339
Destination:Inject

Is this all I have to do and it should work?  Or do I need to make some alterations to the GPSDirect portion?  

Thanks,

I have somehow managed to resolve this - i had to remove and reinstall the TT service. 

I initially was concerned that this would have to be done on ever power up, but so far so good this has remained ok (for example when booted this morning the service was working ok and producing nmea strings with my location on the com port).

However on think this has become an issue for my ongoing use of this is that the $GPGGA NMEA string being produced shows the number of satellites as 0 (even though it is correctly returning a location).  This is causing me an issue as the software im trying to use this NMEA string will ignore any strings with 0 satellites as they could be erroneous.  Does the TT set this to 0 as default, and is there anyway to change this 0?

I have just realised that while there is a NMEA string being produced to my COM port the ILocation data isn't being set across

The the NMEA $GPRMC string is zeros with no location details - although when I use the "ILocation Query" in GPS Complete accurate XYZ are being found.

e.g.

$GPRMS,092826,A,0000.000,N,00000.000

Any ideas on how to resolve?

Thanks for responding,

I tried all of them an none showed a XYZ. 

I have subsequently used the Transfer Tool and GPS reverse in Client mode to spit out the NMEA from ILocation.

Open the Sensor Explorer and try them one by one to see which returns a XYZ.

Not all hardware exposes a Sensor (instead, their services are available only through "ILocation" which is practically all what a maps-like app needs).

That said, are you sure that none of these 7 sensors is the appropriate sensor? Sometimes their names are misleading.

What sort of crash?

It terminates itself? It gets stuck?

hi,

so with putty  gps-complete dump some lines,after few lines GPS-complete crash, i have to restart my computer (MS surface Go3, Win11)

any idea ?

Does PuttY work with the COM port?

check the correct BAUD speed.

Btw contact https://www.turboirc.com/support/bc2.php to request your key (it's usually sent immediately but some times it goes to spam or our servers are busy).

Best

hi Team,

thats works so far , BUT i cennot get out any data from the virtual COM port. tried with a terminal program linked to the port.

the GPS-Complete COM-port tool shows the correct data stream.

any help ?

btw: i paid for the license, but i did NOT get any reply with key or registration data :-(

Best,

Oliver

I 'd say to try the transfer tool approach.

Setup the GPSreverse as "client", then the Transfer Tool from the ILocation to the GPSReverse.

Best,

https://www.gpssensordrivers.com/ -> download

Hello, I ' ll remove that on next updates. GPSComplete always updates on start and it always remains in the latest version.

Best

I just tested these and the driver works, are you sure it's due to the strings?

perhaps a baud problem?

Hi,

These are the strings I am getting from the GNSS receiver.  The driver is not resolving the location data from it.

21:04:34  $GNRMC,210434.00,A,3757.17195,S,14510.93076,E,0.947,,270322,11.83,E,A*18
21:04:34  $GNVTG,,T,,M,0.947,N,1.753,K,A*37
21:04:34  $GNGGA,210434.00,3757.17195,S,14510.93076,E,1,07,1.94,36.9,M,-1.9,M,,*7A
21:04:34  $GNGSA,A,3,05,18,29,26,,,,,,,,,2.95,1.94,2.23*1E
21:04:34  $GNGSA,A,3,74,83,68,,,,,,,,,,2.95,1.94,2.23*1B
21:04:34  $GPGSV,3,1,12,05,37,132,25,10,07,328,,13,17,093,,15,28,060,*77
21:04:34  $GPGSV,3,2,12,16,13,219,19,18,62,235,27,20,10,135,18,23,39,334,*72
21:04:34  $GPGSV,3,3,12,25,25,353,,26,34,246,25,29,69,089,23,41,13,288,*7A
21:04:34  $GLGSV,3,1,10,67,04,159,25,68,41,123,30,69,45,046,,70,03,358,*67
21:04:34  $GLGSV,3,2,10,73,09,329,,74,28,285,18,75,21,226,,83,30,109,28*62
21:04:34  $GLGSV,3,3,10,84,52,193,,85,10,246,20*6A
21:04:34  $GNGLL,3757.17195,S,14510.93076,E,210434.00,A,A*6D

I have found that sometimes it will recognise the strings and work, but if I remove and re-install the driver it will not until the pc is restarted.

Thanks

Glenn

Some $GN* messages are already recognized by the driver (GGA and RMC).

Hello,

i also try to get the positionen Information of a Teltonika RUT 955 to a Windows PC.

Is there any new information how to get it done?

Hi Chris,

have you somehow managed to get your Teltonika GPS location into Windows?
I own a RUT 955 would like to achieve the same thing (note to the admins: That was the ONLY REASON I purchased GPS Complete!).

Any help or idea would be appreciated :)

Tom

I will take a look at the next update, thanks.    

The data I get from the router into the UDP accept tool is:

$GPGSA,A,2,10,12,17,19,24,32,,,,,,,1.2,0.9,0.8*3A

$GPGGA,102524.00,5213.801023,N,00054.047962,W,1,06,0.9,69.3,M,47.0,M,,*4C

$GPRMC,102524.00,A,5213.801023,N,00054.047962,W,0.0,172.4,140322,3.8,W,A*3A

$GPGSA,A,2,10,12,17,19,24,32,,,,,,,1.1,0.8,0.8*38

$GPGGA,102529.00,5213.801023,N,00054.047963,W,1,06,0.8,69.3,M,47.0,M,,*41

$GPRMC,102529.00,A,5213.801023,N,00054.047963,W,0.0,172.4,140322,3.8,W,A*36

$GPGSA,A,2,10,12,17,19,24,32,,,,,,,1.1,0.8,0.8*38

$GPGGA,102534.00,5213.801023,N,00054.047962,W,1,06,0.8,69.3,M,47.0,M,,*4C

$GPRMC,102534.00,A,5213.801023,N,00054.047962,W,0.0,172.4,140322,3.8,W,A*3B

However, when monitoring COM4 the data is incorrect and does not contain any lat/long coordinates:

$GPGGA,105603,0000.000,N,00000.000,E,0,0,0.0,0.0,M,0.0,M,,*42

$GPRMC,105603,V,0000.000,N,00000.000,E,000.0,000.0,140322,000.0,E*66

$GPGGA,105603,0000.000,N,00000.000,E,0,0,0.0,0.0,M,0.0,M,,*42

$GPRMC,105603,V,0000.000,N,00000.000,E,000.0,000.0,140322,000.0,E*66

$GPGGA,105603,0000.000,N,00000.000,E,0,0,0.0,0.0,M,0.0,M,,*42

$GPRMC,105603,V,0000.000,N,00000.000,E,000.0,000.0,140322,000.0,E*66

$GPGGA,105604,0000.000,N,00000.000,E,0,0,0.0,0.0,M,0.0,M,,*45

$GPRMC,105604,V,0000.000,N,00000.000,E,000.0,000.0,140322,000.0,E*61

$GPGGA,105604,0000.000,N,00000.000,E,0,0,0.0,0.0,M,0.0,M,,*45

$GPRMC,105604,V,0000.000,N,00000.000,E,000.0,000.0,140322,000.0,E*61

$GPGGA,105604,0000.000,N,00000.000,E,0,0,0.0,0.0,M,0.0,M,,*45

$GPRMC,105604,V,0000.000,N,00000.000,E,000.0,000.0,140322,000.0,E*61

It seems that the transfer tool is not dealing with the data correctly.

If we paste the good data into port 8500 using Putty, the location on the PC is shown correctly

I have twice tried to add a comment on this and both times it has failed.

the Teltonika RUTX12 router can only send data to an IP and Port. We have configured it to send to his PC IP and port 8500

We used the Accept tool provided by GPS Complete to listen to port 8500 on his PC and we could see GPS data arriving, we copied it to a file.

The setup the Transfer tool to accept on 8500 and inject to the GPS Direct driver

We setup GPS Direct in injection mode

This did not see to work as the position never updated.

We then used putty to connect to port 8500 on his PC and pasted the data we captured with the listen tool. The position immediately updated based on that data.

We further tested this by using a website to generate fake GPS data and pated it into putty. Doing this updated the position each time ad we did a virtual tour of Berlin.

So it seems that the transfer tool is not accepting data externally but the accept tool does (note we did not have both running at the same time) 

I' d try the transfer tool.

Install the GPS Driver as 'injection' and the Transfer tool FROM the IP:Port TO the GPS Driver.

Instead of a direct driver connection, try the Transfer Tool based (install driver in injection mode, then TT from IP to driver).

Hi Support Team,

I've been working with it on software "i-boating" but nothing else.

in the system is declared as a device named "Qualcomm (R) Location"

with and .inf file but I'm not able to work with another program because there is no COM port to communicate with the positioning:

Hello. The driver would be useless in arm since no sensor API is exposed there (as far as we know).

Best,

Hello. The transfer tool expects NMEA format.

As for the C# program, what exactly do you want? The easier way is the command line API. (https://www.gpssensordrivers.com/ -> Manual and API -> Command Line).

Please contact the author through https://www.turboirc.com/business to ensure that your license key is correctly generated.

Best

Is there a license.txt file inside this directory?

Hello.

Please tell me the directory in which you have gpscomplete64.exe.

So I have to install the GPSDirect driver with configuration "Inject".
After that I Install the Transfer Tool with this configuration:
Source -> TCP/UDP Server, localhost:61821
Destination -> Inject.

If done, the sensor explorer should show the correct GPS coordinates for the selected source right?

I did it this way but missed some step I think ...

When I do the TPC Connect test, I could see the NMEA messages, but without that my software just waits and seems not to be connected via the transfer tool

Any advice? UDP or TCP / who should be Client and who should be Server?

This TCP/Connect is a testing tool. You must setup the Transfer Tool to read the data from your server and inject it into the GPS Direct (Install GPSDirect into injection mode and Transfer Tool).

I will take a look, perhaps it was due to latest tax changes.    

Perhaps we can setup a remote debugging session so I can see it.     

Does the "Continuous Location"  testing show the alt?

Generally, there are two methods to implement location grabbing and that's ILocation and Continuous Location, try both and tell me the results.

You said that the Sensor Explorer does show alt and heading, so where's the issue?    

Hello.

The driver does not function with any sort of hardware - what we can do is to setup a remote debugging session so we can test it on your own machine to verify it.

Best,

Bueller...

Bueller...

Bueller...

Bueller...

Bueller...

Thank you for your response. I followed your instructions, and its still not working.


I followed these instructions to the letter on an almost identical machine, and it didn't work.  What is wrong with these steps?  Why won't this work?

https://www.bobjohnson.com/blog/how-to-use-the-gps-in-your-toughbook-for-turnbyturn-navigation/



I followed your instructions, and got even less of a result.


These are the steps I am following, if I am reading your instructions correctly:

1) GPS direct driver ---> Install driver ---> Injection ---> 4800 ---> OK

2) Transfer tool: SOURCE ---> (COM port or IP port (TCP client)" ---> COM3 ---> DESTINATION ---> Inject.  The Fourth drop down menu is blank.  


Sensor explorer says 0000000000.  NMEA is $GPRMC,050151,V0000.000.N0000.000E00000.....  with zero satellites.



I went to the "smart devices" tab, and tried to add my android phone.  That takes me to a link for a "GPS sharing for windows sensor" - THAT LINK IS DEAD.



I am at a total loss here.  I have tried this every which way, and no matter what I do, it simply refuses to work. I went out and bought the damned antenna and installed it, and it seems like I should have just gone to bestbuy and bought a GPS to stick on my dashboard, and and myself weeks of frustration. I don't understand why this is so difficult.

Hello.

The init message means that the GPS device has not a lock. 

Try a transfer tool based aproach:

• Install GPSDirect in Injection mode
• Install Transfer Tool FROM the COM port (and set the com port) TO the Injection

Tell me if this time the sensor explorer works.    

You can type the port speed manually.

We are not willing to modify the driver to do that, but perhaps I can make the executable open the com port and switch the device in a future version.

Sirf is rarely used though.

We are not willing to modify the driver to do that, but perhaps I can make the executable open the com port and switch the device in a future version.

Sirf is rarely used though.

There is a command in SiRF that allows a SiRF interface to switch back to NMEA, did you try that?    

My point is, that the driver should do that automatically. Obviously.

There is a command in SiRF that allows a SiRF interface to switch back to NMEA, did you try that?    

Try injection installation and transfer tool    

Just took a look at the code, I already have wildcard for $GNGGA, $GNRMC, $GNGSA, $GNGSV, (Driver UMDF 2.x).

I got the current API header file, but whats about ignoring the second char in the NMEA sequence ? Any progress ?

Thanks for your help.

We have updated the plugin API structure, contact the author through business-contact in the site to request a C header.

This would be nice, meanwhile I struggeling with your plugin-api, I successfull created and load a plugin DLL which  set s x,y,z correctly ( from a thread that reads it from the serial interface) but all the other values that I set, like satcount,heading, speed, fixquality appearing in tottally different field they should  in your Test-Sensor-Explorer.

I will take a look, the standard is GP but perhaps I can make it ignore the second character.

First, check if there's actually a connection to the com port. Connect with the testing tools to the COM port and check if there's valid NMEA strings there.

Turbo transfer web page is broken. No way to access the download page.

Im working at it, did you try it over the Transfer Tool?    

Hi the same thing happens with my set up. I would like to purchase as it works great right after installation but the second it hybernates or I restart it needs to removed and re installed. I’m running Windows 10 on a tough book cf30. 

Hopefully there’s a solution.

thank you! 

Jordan 

I will take a look

+1

(Check the Transfer tool meanwhile).

Means that the port lags. Is the port configuration correct? Baud speed? 

Also try a transfer tool installation (install driver in injection mode). 

Instead of installing at a bluetooth device from the installation options, install to a COM port. Sometimes Windows assigns the same COM ports to the same-class bluetooth devices.

However, there is a chance that you get a new port, in which you must uninstall + reinstall the driver. However this shouldn't be a hassle from GPSComplete, no reboot needed. Just one uninstall and one install click.

Thanks for the quick reply, but perhaps I wasn't quite clear what I wanted to do. I want to have a separate GPS unit in each of my cars so that I don't have to move the GPS units each time I switch cars. However, at any given time, only one GPS would be active. 

Looking at the install with GPSComplete, it tells me that a drivers is installed, and it lists my GPS unit (which is connected via Bluetooth), but also the GPS unit's unique serial number attached to it. Specifically, it says:

Installed (XGPS150-4C08889[BT[107395942585 UMDF 2.x ... ...

Here XGPS150 is the model name, and the next six characters are the serial number. This seems to indicate that somehow your driver is tied not only to my model of BT GPS, but also to the specific one I happen to have.

So the question is what would happen if I now try to use either a totally different GPS unit when I am in a different car, where the second one is say connected by USB, or even a different copy of my original Bluetooth GPS? Would either of these scenarios work?

Thanks,

Martin

GPSDirect can connect to one COM port only.  There is a pending modification to allow it to connect to different COM ports via the TransferTool, I will notify you when it's ready.

Any update?

Thanks,

Tim Martin

If you think you can look at it relatively soon, no need to refund.  Enjoy your vacation!

Thanks,

Tim Martin

Not yet, we are in vacation, if you 'd like I would refund you.

Best

Hi, any progress on the iOS tool?

 - Tim Martin

I will take a look, thanks for noticing, it's been a while since we updated the iOS tool.    

The problem with the shared mode is that all applications that open it must specify it. So even if GPSComplete opens the port in shared mode, other applications will fail to open it unless they also specify that mode. 

Try to configure appropriately the application that wants the access to the com port. 

If you want professional programming assistance, please use the "Business Contact" link on the GPSComplete download site. Generally, you don't need developer's experience to use GPSComplete.    

I have to test it on Windows 8, which is a bit difficult at this time, but I will try.

Does it work in simulation mode?        

I have to test it on Windows 8, which is a bit difficult at this time, but I will try.

Does it work in simulation mode?        

I have to test it on Windows 8, which is a bit difficult at this time, but I will try.

Does it work in simulation mode?        

Do you have a utility with your GPS that can test the accuracy and the lock?

Check if the connection problem persists.    

$GPGGA,145135.00,4337.25311,N,11612.51432,W,1,04,16.52,823.6,M,-19.4,M,,*50

$GPVTG,350.49,T,,M,8.557,N,15.848,K,A*09

$GPGGA,145136.00,4337.25333,N,11612.51408,W,1,04,16.51,823.6,M,-19.4,M,,*59

$GPVTG,351.24,T,,M,8.267,N,15.310,K,A*01

$GPGGA,145137.00,4337.25382,N,11612.51371,W,1,04,16.49,823.6,M,-19.4,M,,*52

$GPVTG,351.60,T,,M,8.108,N,15.017,K,A*0F

Then there is a problem with the connection.

It returned ->

"Maximum connections reached - refused" and "Connection to host lost"

Yes, telnet to that IP and port. Check the messages, especially the the RMC and the GGA.

See for example a valid RMC message: https://www.trimble.com/OEM_ReceiverHelp/V4.44/en/NMEA-0183messages_RMC.html

Are the NMEA sentences sent to the driver valid?

GPSDirect can work with any application that shares NMEA data over TCP.

Hi again,

IThe port-settings are right.

Qirx checks all possible COM-ports and detects port speed and settigns, if the configured port/speed-settings are active with GNSS-data, it obviously (from logfile) stops scanning for other active COM-ports.

I have tried using a Garmin GPS60CSx in NMEA 4800 via a Pl-2302 serial - USB virtual COM cable, and the QIRX detects it and uses it.

It seems to be some difference between the COM-port made by Pl2302 and GPSReverse?

//Espen

Does the GPSComplete port testing tool find the COM4 port and does it get data? Usually, it's a matter of setting a correct baud rate and other port settings (default 9600).

Most probably because google maps only uses IP (it wouldn't have access to a sensor).

I mean to get the data from your phone to the driver.

Which app do you use for the connection to the driver?

Does your phone actually have a gps lock? try it outdoors.

Here are the command line arguments:https://www.gpssensordrivers.com/cmdline.html

/j is not in the list because it's a hidden one, I only reveal it to users that are asking for it.

So to install gpsdirect, gpscomplete64 /c install /d gpsdirect2 /s COM4 /b 9600 /j 1

Thank you for the prompt response.

Can you please explain what you mean by "Install with the command line parameter /j 0."  I apologize in advance if this is an obvious instruction.

This delay is set on purpose to cope with some devices that need some seconds to initialize.

Install with the command line parameter /j 0.

Start -> run -> devmgmt.msc -> Sensors -> delete GPSDirect.

This is interesting. 

Can you check if the "Continuous Location" GPSComplete test has the same issue? Does it hang after a while?

So I just wanted to give an update on this as I have went through some more testing.

I have tried 3 different sensor drivers on my tablet and all three seem to be running into the same issue. Everything will work just fine for a while and then all the sudden the Maps app will just loose the location and either not start the turn by turn, or in a couple cases it lost it during a re-route and just hung on the screen showing re-routing.

I ran this with the GPS Complete sensor driver, a sensor driver created by Panasonic for their Toughpads, and an external GPS puck that had the U-Blox sensor driver built into it. I also tested on a Dell tablet that had a built in sensor (not a virtual one linked up to an external GPS device). I am starting to think that rather than it being an issue with the sensor driver that it might be something with the Maps app itself. I was able to check the Event Viewer on my tablet after one of the instances and it was listing an App Hang on Maps.exe.

I am still researching when I have time but I wanted to at least pass this along that I am having the same problems when running other sensor drivers as well. Not sure if you have seen or heard of this from anyone else or have an inside knowledge of if it might be a bug in Maps.exe?

Ok, so I was finally able to get out and do a little testing. I was able to successfully navigate to about 3 different locations and then all of the sudden the maps app was no longer seeing my position or was able to process the turn by turn.

During the time when the maps app was not receiving my location, I went into the DriverLog and I could see where locations where being seen and scrolling through. I tried restarting the computer but was still not being seen by the maps app. I also tried restarting the transfer tool service but this still did not get a location in map. Finally I went to Device Manager and disabled the GPSDirect v2 driver, left it disabled for a minute and then re-enabled it. Once it was re-enabled the maps app was again seeing my location and I could navigate properly. 

Initial testing seems like something is getting hung up in the sensor driver and disabling and re-enabling it is freeing it up to allow the maps app to receive information from it again.

Does the driver log  show that there is actually data to be passed?

Try setting up the transfer tool instead of a direct connection.

Normally Win 10 supports UMDF 2 drivers but this might be a somewhat limited edition.

Even simulation fails?

x64

v1 drive also does not install

x64 or x86? The v1 driver installs?

GPSDirect can only connect to TCP at this moment, can you use TCP?

The GPSDirect installation dialog has a precision setting option.

Is there a screenshot of what its meant to look like?  as I will have to go back and redo it I suppose.

The GPSDirect installation dialog has a precision setting option.

Is there a screenshot of what its meant to look like?  as I will have to go back and redo it I suppose.

The GPSDirect installation dialog has a precision setting option.

What is the precision mode set in the GPSDirect installation?

**edit** I downloaded your latest driver and un-installed the old and re-installed the new. I am getting gpsdata location data fine inside of your wee app and during the install its set to continuous however if anything the accuracy is how 3~4km out and does not update inside of googlemaps at all so if anything its worse with this update.

I got my cig lighter socket adapter for my surface pro3 today so I have tried to get locations and while on the move, it simply fails to see my location and as I drive about no updates to location occurs.  However when I open the gpsdirect driver and drive along, in continious mode I see the location is changing but google maps etc do not see any changes.

Ok, well if its "weird" then in that case I think I'll try varying the hardware. So I will re-try on my Dell M4800 laptop to make sure its not the surface pro3 with windows 10 and I think I read I can use my Android phone's GPS, it maybe simply that this GPS hardware or software has an issue.

Of course it could just be me, a re-try or 2 might make that obvious also.

I will take a look, seems weird.

They are both identical.   Last night the location was really accurate within 3m, this morning I moved 7km and it still showed me at the old location in googlemaps.   I opened the gpsdirect software and this showed my new location but googlemaps showed me in the middle of the harbour again.  This suggests that the location isnt being updated?  The software that comes with the GPS is working fine, it gives me the right location (as far as I can tell) .  Am I missing something like I need to set something up so windows10's location gets updated continiously?  something needs to be running on startup?

What do you mean by different?

My earlier posts dont seem to have appeared here.   So to repeat, I get a location from the GPS from the GPS software.  "the continuous location testing op option in GPSComplete"  not sure what this is, my best guess looking in your software is its seeing the Lat and Long OK.   However googlemaps has a 5~7km error showing me the middle of the harbour so I'd guess its not getting to the "location" services. 

Will have to check when I get home but google maps is showing me swimming in the middle of the harbour so something is not working OK.

--edit-- timestamp is incrimenting.

I was sure that I already tried it this way. But now it works!

GREAT! Nice Tool. Thank you so very much!!

Btw. Have a look at the Teltonika Router. It is a very nice device with lots of features. (No Ad!)

I 'd say you try a TransferTool based installation.

• Install the sensor driver in Injection mode
• Install the Transfer Tool with source: COM Port driver or IP Port, enter below 172.16.10.1:8500, destination  Inject 

I checked the output using GPSRedirect to COM3. I used VisualGPS and can see the incoming data with no positions in.

I also checked your diagnostic tool. State is still initializing. I made a screenshot, but cannot upload in here.

My sending GPS device is 172.16.10.1 on TCP 8500. Theese are the values I enter when installing the driver. Is this correct? Do I have to make some other settings?

When I injected these two RMC/GGA sentences to the driver I did get a ready status. 

How do you know there is no fix? Can you use the Sensor Diagnostic Tool? (http://www.gpssensordrivers.com/sensordiagnostictool.exe)

Thank you for your very quick response.

The device is an LTE/WLAN router with integrated GPS (Teltonika RUT955). There I can see position data and the fix. 

The received sentences look like this in the telnet tool (positon data edited):

$GPRMC,072502.00,A,5206.845585,N,01324.496539,E,0.0,191.6,230719,0.7,E,A*33

$GPGGA,072506.00,5206.845568,N,01324.496553,E,1,06,0.8,171.3,M,44.0,M,,*6D

$GPVTG,191.6,T,190.9,M,0.0,N,0.0,K,A*2D

How do you see that the device itself has a fix?

Paste some example sentences you have received.

I suggest you try to connect to the bluetooth device via it's COM port setting, not directly.

Added photo #7 to the link in the first message.

The sensor shows up at #36 as GPSDirect UMDF 2.x, but the values are all zero except for Time Stamp, which appears to be correct.

Thank you for support!

Hello.

What does the sensor explorer shows when the driver is installed?

Pass X,Y,Z in the baud/port field, e.g. 24.2,37.6,122.5

Delete the sensor driver along with "Delete the driver software for this device" , then clear HKLM\Software\GPSSensor7 key

I have the same issue, but don't know which part should be removed from devmgmt.msc. The devmgmt.msc files under c:\windows\system32 and c:\windows\sysWOW64 are not modified this year though I installed GPSDirect this week. Could you please give me some detains? Thanks!

Remove it from devmgmt.msc and try again.

Still seeing same problem.

See screenshot at: https://ibb.co/TPKNcdz

For the precision, GPSDirect ignores it when the setting is 'use maximum precision' in installation dialog. Remove that.

I've the same issue here. I've just downloaded and installed the driver.

Sensor explorer report 560 mt for Z but the win 10 gnss service provide 0.

The precision is not correct too: gnss shows always 1 but the USB gps says 2 or more. 

Thanks for support. 

Make sure you have removed the driver (try from devmgmt.msc to remove it to be sure).

Continuous Location (WIndows 10) is still showing `z:0` 

I updated, removed driver, added driver.  Should I have done something differently? 

Thanks for the quick turn around!
Jared

I 've made changes to the driver, take a look.

> So the sensor explorer reports it but not the location?

Yes, that's correct. 

Thank you!  Awesome piece of software!

Jared

Images can be found here: 

https://photos.app.goo.gl/VncfUz4BGRCp921QA

So the sensor explorer reports it but not the location? I 'll take a look.

Yes, same result.  

z: 0 

There are some issues with image pasting. Thanks for the notification.

The LocationReport generally is an old API that doesn't report altitude. Did you try to use the Windows 10 Continuous Location?

When the mode has "Update data", the data is updated from the GPS even if the data is null/invalid. 

When the mode has "Report to Windows", then the data (kept from a valid state or updated to the latest depending on the update mode before) is sent to the sensor.

"Don't update data" does nothing.

"Always tell Windows I have data" means that Windows thinks the data is always valid, it's always resent constantly even if no actual data is there.

I tried using the Transfer Tool method and so far it's looking like it's working, Windows hasn't stopped the device yet.  It's been about 30-45 minutes so I'm hopeful, I can update later once I know more for sure.

As a side note, and for future internet travelers:  I had a small curve ball setting up the Transfer Tool from GPS Complete.  Source was a COM port so I selected that, but nothing populated in the second drop down afterwards.  I knew the port number I wanted (port 9) so I typed "9" into that box, but that didn't work.  I tried typing "COM9" on a whim and that did work.  I'm not sure if that drop down was supposed to populate or not, but it would have been nice to know that's the syntax the Transfer Tool was looking for.  No matter though, as long as it keeps working I'm happy.

Try a Transfer Tool based approach first and tell us if it worked.

https://www.gpssensordrivers.com/ -> Manual and API -> Transfer Tool examples.

• To use a COM port, enter it (e.g. COM3), then the baud speed. If the driver does not work with the baud speed you select, lower the speed.
• To use a bluetooth device directly (if your bluetooth GPS does not have a COM port or if the COM setting does not work) then select a bluetooth device from the list (The Bluetooth device must be recognized and paired with your system). The baud speed is ignored.

What does this one mean?

"Either with the GPSDirect driver listening to a COM port or directly to the Bluetooth device."

I'm sorry, I don't understand.  From the GPSCOMPLETE web page, I see ..

   GPSDirect is a user-level driver (UMDF) that can read a COM port, a Bluetooth device or a TCP/IP Source that contains GPS NMEA data and map it to a Windows GPS Sensor for your Windows applications to be GPS sensor-aware.

That is exactly what I am trying to do, have a Bluetooth device transmitting NMEA data appear as a "local" Windows GPS sensor.

Your web page says "it can read a COM port", your reply says "It does not listen to a COM port".  This makes no sense to me ...

The connections GPSDirect makes are outgoing. It does not listen to a COM port, it has to use an outgoing COM port which the bluetooth device is listening itself.

We never disclose software protection mechanisms to the public.

The idea is, of course, not to compel an individual user to pay $15, but to make sure our large customers get the best of our support.

Glad you figured it out.

It starts malfunctioning in various ways.

Uninstall/reinstall the port driver?

Try an external tool (PuTTY) to verify the error?

Check devmgmt.msc for errors?

$GPNULL means that there is a connection failure. Did you try reading the COM port with the port testing tools?    

Thanks.  I guess the problem is that I do not know what is meant here by port and sensor.

I thought I did, but apparently not. Is that explained clearly somewhere?

I used to be able to just plug in the BU-353 (not S4) and it worked, but Windows now has changed. 

I also have radio programming cables that used to work and I'm guessing that now on Windows 10, they won't?

There is a quick manual in https://www.gpssensordrivers.com/ -> Manual and API -> Transfer Tool examples.

> Try, instead using the driver directly with the sensor, to use Transfer Tool.

> Install GPSReverse in Client mode, then the TT from the Sensor to the GPSReverse.

Thanks. I'm afraid, though ,that I have no clue what " TT from the Sensor to the GPSReverse" means.

I've tried various combinations.  Is there documentation somewhere?

Try, instead using the driver directly with the sensor, to use Transfer Tool.

Install GPSReverse in Client mode, then the TT from the Sensor to the GPSReverse.

But I don't see location data in the streams I get with virtual port on or in OpenCPN

$GPGGA,203139,0000.000,N,00000.000,E,1,0,0.0,0.0,M,0.0,M,,*48

$GPRMC,203139,A,0000.000,N,00000.000,E,000.0,000.0,280319,000.0,E*7D

$GPGSA,M,1,,,,,,,,,,,,,0.0,0.0,0.0*3C

GPSDirect is for COM port -> Sensor.

GPSReverse is for Sensor -> Com port, so I guess you need this one.

What's the sensor values using the sensor testing tool? Does it show longitutde/latitude there?

We 'll take a look, but I doubt that anything can be done at the moment apart from waiting to see if there is some new driver API that would allow the driver to be visible to WSL.

According to https://blogs.msdn.microsoft.com/powershell/2006/08/31/writing-and-reading-info-from-serial-ports/ the following code should work in Powershell but, as you can see, the port is not being detected as a serial port.  This would explain why it is not being properly mapped to WSL.  I believe if this can be resolved, we probably will see work with WSL.  I was using the v2 driver for this test.

PS H:\> $port= new-Object System.IO.Ports.SerialPort COM8,9600,None,8,one
PS H:\> $port.Open()
Exception calling "Open" with "0" argument(s): "The given port name is invalid.  It may be a valid port, but not a
serial port.

We 'll take a look, but I doubt that anything can be done at the moment apart from waiting to see if there is some new driver API that would allow the driver to be visible to WSL.

I have GPSReverse working on Windows 10, 1809.  putty to COM8 works great.  Run putty under WLinux (Debian distro written for WSL) to /dev/ttyS8 and no data.  Possible issue with virtual com port and WSL?

I have created GPSReverse with both 1 & 2 (both worked) and with MTH enabled/disabled (both worked) so all 4 combos worked in Windows but not when attaching within the Linux running under WSL.  Microsoft has supported com ports in WSL since 1709.

Thanks!  I am ready upgrade from evaluation if we can get this to work!

Pete

Note: One difference between real port and the virtual port that I see in the Device Manager is the Port Settings tab is missing from the virtual port properties.  I don't know if this would affect it.

I see. I'm not sure if anything fixable is missing at the moment, did you try  installing the V2 driver ? There is an option in GPSReverse to install the experimental UMDF 2.x driver which might work better.

No, you are not understanding.  The port works correctly with Windows programs running natively in Windows, including putty.

Microsoft introduced something called Windows Subsystem for Linux (WSL) in Windows 10 which allows Linux applications to run under a Linux distro without knowledge of Windows.  In Windows 10 1709, Microsoft added serial port support where /dev/ttySn map directly to COMn ports in the Windows OS.  What I am saying in this thread is that functionality does work for physical serial ports and for -some- virtual serial ports but not yours.  The question is "What is missing in your driver that Microsoft is looking for to successfully map your COMn driver to /dev/ttySn?"

The Linux putty and the Windows putty are working perfectly.  putty is a simple terminal tester when connected to a serial port and works basically the same in Windows and in Linux making it an excellent test tool for your adapter.

Have you looked at the WSL serial port support implemented by Microsoft and verified that your drivers will be properly mapped?

Then a PuTTy issue, try opening the port as long port (if COM8, open it as \\.\COM8).

Is the testing tool that come with GPSComplete (Any COM Port Open) able to open the port?

We do not assist in programming questions here; Please feel free to contact us via the Business Contact (https://www.turboirc.com/business) for expert advice on your issue.

Best,

Hi,

I'm Sorry, It's not truth. A C++ (http://www.naughter.com/enumser.html ) doesn't work.

BR

I have no knowledge of .NET, I suggest you try stackoverflow to check what could be wrong.

In C++ it works fine.

I don`t understand , my  simple c# program (error: he given port name does not start with COM/com or does not resolve to a valid serial port ):

            // Create a new SerialPort object with default settings.

            _serialPort = new SerialPort();

            // Allow the user to set the appropriate properties.

            _serialPort.PortName = "COM4";

            _serialPort.BaudRate = 38400;

            _serialPort.Parity = Parity.None;

            _serialPort.DataBits = 8;

            _serialPort.StopBits = StopBits.One;

            _serialPort.Handshake = Handshake.RequestToSend;

            // Set the read/write timeouts

            _serialPort.ReadTimeout = 500;

            _serialPort.WriteTimeout = 500;

             _serialPort.Open();

Yes it works, you need a program that is able to open the port. Try \\.\COM4 as well. 

How can I help?

https://www.virustotal.com/#/file/ed3385fff054aef9abc35005b0b72ffd14bb5e34ddaedc199572d01876adb4ee/detection

https://www.virustotal.com/#/file/aa2a12727e18ac74098c68e5afa0a9ac75280bebc8d2912f75468b0748a6e40a/detection

Something is wrong with your system.

You need GPSDirect. Did you install and test it via the sensor explorer?

Install it to the com port provided by the BT.

The best debugging option is to download https://play.google.com/store/apps/details?id=com.michaelchourdakis.windows7gpssharing and test. If gpsdirect can connect to this, then you have a problem with your nmea server.

All versions have UMDF support, current 1809 works fine.

The proper test for the driver is a) to use sensor explorer to test for the signal flow and b) to use ms maps to check if it gets a location. The ILocation is deprecated and it is not going to work reliably.

I'm not having any luck with the inject method.  When I do iLocationQuery it comes back with nothing.

My previous version of GPSDirect used sensor driver version 9.21.11.290 (7/16/2018).  This new driver version is 17.56.49.734 (1/16/2019) and will not work properly with our Windows build.  Is there a way to roll back the driver version to see if it will work with our new Windows build?

Since you installed GPSComplete in inject mode, "Inject" is the target you must use in TT. 

The TT Source must be the IP/Port of the network source.

The destination should be the sensor driver, not the default location (which is an obsolete API).

I install the GPSDirect driver in Injection mode.

I install Transfer Tool with Source=COM Port , put in port 6257, and then Destination = Set Default Location.

When I do an ILocationQuery it will work a couple times, but then the location coordinates go away and I can't it to work again.

We did fine on testing the previous build of GPSComplete but this latest update doesn't seem compatible with the drivers on our latest build of Windows 10.  What build versions  are GPSComplete fully compatible with?

You have to use this port number in Transfer Tool configuration. Port number set in injection mode in GPSDirect is ignored.

There might be an incompatibility. Install the driver in injection mode and install the Transfer Tool to get data from the COM port and to inject it to the driver.

But do use the testing tool that comes with GPSComplete, because the same tool is used by the driver to read the com port.

I'm using the program supplied by the manufacture. This shows an constant data steam from the GPS coming into the computer. No delays or stops in the stream of data.

Here is an link to the program:

http://www.qstarz.com/download/QstarzGpsView%20v1.2.24.zip

Thanks for the quick feedback.

I have tested today, GPS direct in Inject mode. The transfer tool setup to read from COM6 and in inject mode. 

I get one time the data when I open the sensor explorer. The data looks to be valid but the time stamp is not updating. When I close sensor explorer and open again the time stamp stays the same when I first open it.

When using the GPSdirect as I mention in my first post directly reading from com6 the data was updating for 5 to 10 min and then stopped as the driver stopped with an error 43. Any more suggestions are welcome.

The driver is not always fully compatible with the hardware. That's why we have created the transfer tool, so try that. Install the driver in injection mode, then the transfer tool from the com Port to the driver.

Best

Load com port driver Test -- and got good data --- try normal and injection with no data being transfer to computer

also I just received an update on 12/23/2018 -- just wondering

I check baud rates and are the same at 9600 -- also for some background i program computes for 32 years a retired for 19 years

i have setup the RS232 port for printers and other devices I am not new to the old serial ports.  I just donot understand what is going on.

more background i have a surface go running windows 10 home -- I also have a surface pro running windows 10 pro and have same problem on both systems.

In that case you usually need to change the baud rate.

Note that unless the COM port tool reads the data correctly, the other tools won't work since they share the same code.

Using the com tool -- all i get on the port is garbage -- i do have a program that reads that port just fine.

thanks

the manual selection of com ports load fine -- need to test --- try Maps and does not seem to work need more testinging

do i need to load the reverse drivers with same port?

also there is another com driver that gets load when i put in the GPS receiver in ubs port

will that cause problems

where do i get the testing software you gave name for

I found test software -- under tools

I turn on port and get info.  --- I get location and loc info is not where i am looks like it is not reading GPS -- I use google earth to get my location and it dose not match the location from sensor.

So how do i get the sensor to talk to the GPS receiver ?

Are you sure it correctly detects the COM port?

Try a manual selection.

Use the testing com port tools to verify that the port actually works.

Driver loads in Simulation mode.

Driver only fails in Auto

Does it also fail to load in simulation mode?

Check if you actually have a signal in Sensor Explorer tests.

The any com port is just a testing feature to check if there is data in the port.

It seems that there are incompatibilities  between driver and port, you should try the transfer tool mode.

Install the driver in injection mode, then configure the TT.

The issue seems to be completely different than I thought.

As long as in the "Any COM Port on" mode, the client stays connected to GPSGate and it seems the data is routed through to the application (not guaranteed as I didn't drive so far).

As soon as in "COM Port off" mode the connection to GPS gate is lost within about 10 seconds (some sort of a timeout). This behaviour is also true while driving in which case no data is passed to the application.

In "Sensor Explorer on" mode (that's what I used so far while testing) the connection is also lost.

Is it because in the "Any COM Port On" mode GPSDirect is constantly requesting new data? Could be that it is actually a problem of the Maps-Application who should request data, but Microsoft doesn't want the application to be used for on-road navigation.

Kind rergards

Ruedi

I'm in Central Australia on very, very poor internet. So I prepared the whole post before having internet.

Being in Coober Pedy I installed the latest Windows 10 updates and at the same time noticed that you sent an automatic update.

Reading your answer I prepared the reply and noticed that the application now works up to 10 minutes before freezing. After restarting the Maps application the whole thing worked again for some minutes. Something must have changed. Huge improvement. I will continue testing tomorrow and give you a result (hopefully).

By the way: All tests have been done while stationary i.e. not driving. Vibration should not be an issue.

Cheers and thanks for the fast reply.

Ruedi

Would you paste me the nmea strings returned from gps gate?

Take them using the com port tests in GPSComplete.

Ciao Michael, any news?

ciao Piero

Find me on skype (windowsnt_997) to try a remote debugging session.

The helper is working, but the output of transfer tool is still all zeroes

To clarify for you, I get nmea sentences not GPNULL, but the values are zeroes

ciao Piero

You are correct, i fixed it with a helper, try the update in a few minutes.

Yes that's correct, thats the correct values. The TT configuration has changed.

If that's the correct values how can I identify the GNSS entry?

ciao Piero

Yes that's correct, thats the correct values. The TT configuration has changed.

Good day again, installed the update but:

- in "configure transfer tool", in the dropbox where I should see the names of sensor driver I see a list of exadecimal values instead

- I uninstalled and reinstalled driver, but still exadecimal values

thanks and best regards Piero

I found the bug and I'm fixing it, expect an update later.

Hi Team ,

Thanks for the clarification .

Looking forward for future Update releases.

Regards

Gaurav

0,0 is treated by windows internally as a "no-position" (because it's unlikely you are actually in the Guinea gulf center).

Therefore, zero in lat/long is not treated as a real value, but as a testing one. However I will see if there is an option to override this.

Geolocation service.

Other than that, there might be a custom control panel service for the particular tablet that switches the sensor on/off.

Thanks for the reply!

Upgrade from a Win 7 Home version?
Fresh install of Windows 10 Enterprise Edition

Some service disabled? (check services.msc)
Which services in particular are you interested in?

Some group policy applied?
Yes but we have other Toughpads with the same group policy that had successful installs.

Upgrade from a Win 7 Home version?

Some service disabled? (check services.msc)

Some group policy applied?

I guess that the previous Windows version was a version without the sensor interface then.

Sorry, I should have specified : Windows 10, but an upgraded-from-Windows-7.

On a true Windows 10 it works fine.

Thanks for the prompt response!

Not all Windows versions support GPSComplete, are you running some "reduced" or home version?

Thank you!

The  baud rate has only a meaning for physical COM ports. There is no meaning in setting it in a virtual port, so you can use 4800 in your app.

That said, I will take a look to check if there is a way to force a virtual number.

The com port is permanently opened by GPSDirect, however a soon to be released update will enable opening the com port in shared mode.

The location finder depends also on other factors. Your first testing step should be the sensor explorer to check if the data flow is correct.

I see, in that case GPSReverse is of no use to you (it does not work with every hardware, that is why we provide an evaluation).

Refund initiated.

Some devices are intended to return location information (that is why maps work) using the location API, but they are not using the common sensor protocol.

In such cases you cannot use GPSReverse to directly create a com port.

What you can do is:

• Install GPSReverse in client mode (there is such an option in the installation dialog)
• Configure the transfer tool to transfer data from ILocation to the COM port driver.
• Start the transfer tool

I am using the built in GPRS / 4G LTE module internal to the Surface Pro 2017 LTE.

How can I test if its compatible? its a Microsoft Product and operating system.

It works fine with internal Maps application etc

Do you actually have a sensor compatible with the Windows Sensor Mechanism?

At this moment GPSComplete does not support multiple connections, but we may add it in the future.

GPSDirect works with a local bluetooth GPS device, that is, a bluetooth attached to the computer.  To connect an android phone, the connection works over TCP.

The sensor driver menu has an uninstall function.

I did a lot of googling and from what everyone was saying, GPSDirect could be used to add external GPS capability to my Windows 10 PC and then I would be able to access and use offline navigation maps etc. 

So GPSDirect only works with internet connection?

If that is true I don't think this will work for me. How do uninstall the GPSComplete Drivers. There is no uninstall. 

The sharing works over TCP, not over COM port.

You have to enable the sensor somehow, most probably via a sensor item in control panel.

There is the location API and there is the sensor API. The latter one works with any kind of sensor (not just location) and returns the full set of information that a sensor can provide.

By contrast, the location API is based on Windows estimation of the location; this may come from the sensor, may come from the WiFi, may come from anything Windows seems appropriate.

I do see values for speed and heading in the Sensor Explorer:

#12 {055C74D8-CA6F-47D6-95C6-1ED3637A0FF4}/6   55.600000
#13 {055C74D8-CA6F-47D6-95C6-1ED3637A0FF4}/7  124.600000

Does the Sensor Explorer use something internal, or is the same COM Location API that I'm using? I'm starting to wonder if there's some configuration / permission / conversion detail that I'm missing...

This PC is not physically moving, but I'm feeding it NMEA data that was recording while moving — for testing/dev purposes.

I just tried reading the same data via the newer Windows.Devices.Geolocation APIs, and I do get good speed/heading data. So the problem seems limited to the old Win32 Location API.

The fact that it shows zeroes means that you don't have (yet) a GPS Fix.

Can you try it outdoors?

Also, the fact that ILocation works means that it gets data from your WiFi, not GPS.

Sorry, I tried to attach screenshots. This did not work.

The GPS Port Testing shows zeros N and Zeros E

The ILocastion is shown correctly

Yes, install GPSDirect on the COM port of the bluetooth directly with the "maximum precision" option enabled.

After that however, you won't be able to see the COM port from apps that need the COM port.

Thank you for your reply. GPS direct sensor drive was recommended in this WikiCamps forum to obtain a GPS fix http://www.wikicamps.com.au/forum.php?id=58362&start=0 . What I want to do is see my location in WikiCamps as we travel. I have Windows 10 tablet/laptop and my location does not update or display accurately. Can your software help with this?

Hello there.

It's possible that your software wants to access the COM port directly. If it can, why you would need to use GPSDirect anyway?

Does the Sensor Explorer in Tests menu show the GPSDirect data?

That option is there to force data when there is no data. You can use the "Always tell Windows there is data" to force the Location API to see that there is data (it keeps the previous valid value).

In theory of course, in practice we don't know where exactly the Location API gets the data from.

I went out today to test and didn't see any of those jumps, so I'm not sure what the deal was last weekend.

Is there documentation somewhere or can you give a better description of what the different options under "On lost signal" do, and how it affects the location in the Windows Location API?

Various Windows builds seems to do different things, and we cannot force them to use the sensor unless WiFi is off.

However I am looking for some new sensor properties that may prevail to Maps.

Yeah, I check everything except the shared COM mode.

I just noticed while driving today in an area with a lot of commercial buildings (stores like Menards, Walmart, etc.) the gps location was bouncing around as if windows location services was falling back to wifi/access points for location. It wasn't attenuation from the buildings, it was just random jumps for one update where it looked like it was snapping to an access point. When I was away from the stores, even in dense residential areas it was fine without any random jumps.

I've been testing different setups because I have a mix of apps that use Windows Location API then some legacy software that requires COM. Then I have the requirement for NMEA logging as well as transmitting to a web server, so I use GPSGate for that. So today I was testing GPSDirect as the software that reads the bluetooth GPS. I had a couple dropouts in the Windows Maps and Maps Pro apps, plus the random spiking I described earlier. I was also running GPSGate reading the Windows Location API for its input and logging the NMEA stream to a file which also has the spikes.

Use the maximum precision option when installing the driver.

Mostly just curious what kind of info is in there, but also to see if there could be clues as to why I would get random signal jumps or dropped signals when the GPS device was still reporting good reception

I found it, April 9, I will send you an e-mail asap.

I don't see a record, do you remind me the purchase date so I check it through PayPal?

What is the e-mail used to purchase?

I downloaded the gpscomplete file and installed the sensor driver! Installation was successfull but during sensor sensor testing the software got stuck. But obviously the AIP was working as i could localize my position in the windows map apps! BUT with qv7 i can no longer use the internal gps (can not find gps-device on com-port)!

Had to uninstall the sensor driver to get it working again, but with no more position for win-apps! :-(( what can i do to have positioning for both  systems? Qv7 can use com/nmea/sensors, etc but does not work with the sensor driver!! :-((

Martin

okay, thx!

so i just need "gpsdirect"?

Try it; evaluation is available.

The TT helps when the data is not there in COM port testing (In GPSReverse only).

I guess you have installed GPSDirect. Did you specify maximum precision option?

Usually there is a Control Panel entry to start the sensors, or you can start them on reboot if disabled.

Sorry. To clarify I am able to install the drivers without receiving an error message

Sigh your web site stuff the contents of my message into the url and when I try to send portion of log file my network blocks the url. How can I send this as attach .txt file? I tried to message you directly but got same result.

I see, I guess that something blocks the installation of the driver.

Can you take a look at setup log?

 c:\windows\inf\setupapi.dev.log

What do you mean by first? Here's my step by step. 
1. Launch GPSComplete

2. Click Sensor Driver in upper left

3. Select Install

4. Select NMEA Source(Have tried all options here and all fail)

5. Receive Prompt "Installation Failed. 3758096967"

The next step is to verify outside GPSReverse (i.e. the Sensor Tester) whether the actual XYZ values are consistent.

Hooray!!!  It seems to be working now.  But it stop after a moment, even outdoors.  I am taking this to the boat to see if it works in a wide open area.

I checked the output of the sensor with Sensor Explorer when the position is given or not and the sensor data seems frozen in both situations.  Nothing changes not even the Time Stamp even when the location is updating on the openCPN application.

As for COM6 when the position is shown or not I see groups of 5 lines updating every second.

Another thing I noticed is the position updates are very responsive at times but at others they are sluggish.

OpenCPN shows a line in front of the actual position.  This line length is a function of the speed.  Sometimes the line length makes sense but at time the line is showing even when I am not moving.

Could there be an issue with openCPN acting up on the received data from GPSReverse?

Thanks for your help.

Ok from the beginning.

Install GPS reverse through the com port driver menu. In the dialog select the client mode, leave the others default.

In the transfer tool menu, select configure. As the source, select the sensor to use (make sure that the tool can see the sensor changing by testing the sensor from the tests menu). As the destination target, select the com port driver and below, the com port used by GPS reverse.

Then, start the transfer tool from the same menu.

Then, test the com port from the any port com tester from the tests menu.

Best,

Man, this is like playing Dungeons and Dragons!

How do I install GPSReverse in client mode? There is no installation I can do for GPSReverse, it gets installed with gpscomplete64.exe.  Correct?

TT is in-between the sensor and GPSReverse, correct?  What would the destination COM port for TT be, the final application (openCPN) COM port?

Can you clearly explain what to do or is it too much to ask?

Thanks

Install the gps reverse in client mode, then TT to the destination com port, then start TT and test again.

M.

Device manager shows that GPS Reverse is on COM6 and the device is working properly, and GNSS 47531 is also working properly

I think the COM Port test was failing because I was only writing 6 in the box instead of COM6.  Now for COM6 my screen is filling with lines of data updating about every second.  These lines all start with $GP and seem that they carry Longitude and Latitude values, they are for example:

$GPGGA, 171341,0000.000,N,00000.000,E,1,0,0.0,0.0,M,,4B

When testing the Virtual COM Port it shows only 3 lines with one of them having the same type of data as shown above.

When opening Sensor Explorer, and looking at Broadcom GNSS 47531, several columns show information.  In the Value column the first number is a Time Stamp, the second shows a latitude number consistent with my location, and the third a longitude also consistent with my location.  Then there are many more values below these first three.

When testing ILocation the report gives X=35.717609, Y=33.580235, Z=88.29.  I have no clue what these numbers are.

I have tried to install and start the Transfer Tool and setting the Source to Sensor driver and choosing Broadcom GNSS 4731, but for the Destination I don't know what to choose, COM Port or Set Default Location, and what the values would be.

Still no data is going to openCPN when setup to receive data from COM6 at 9600 baud.

Are you sure it's the correct COM port number?

What does devmgmt.msc say about the port?

When testing a COM Port I always get a failed message.

I am not sure how to set the Source and Destination on the Transfer Tool.

I guess the source is the Broadcom 47531 with a location 22 as shown on Device manager.  As for the Destination I have no clue what is need to be to connect to GPSReverse.

The first thing to do is, after installation of GPS reverse, to check if there is data from it using the menu tests, any com port tester.

Do you get anything there?

The newest GPSReverse allows you to setup a fixed COM port in order to get the desired COM1 name.

Did you try that?

I will take a look.

Does the same thing happen with LocationFixer ?

Some devices only need /f, not /u 4.

I 'll take a look to check if any other options are available for getting rid of the IP location.

Just to verify, does the same error exist if you install GPSDirect from the GUI?

Here's what it looks like in our mapping software:

https://www.dropbox.com/s/rf00u0tx93lqb69/GPS%20issue%201.png?dl=0

Zoomed in you can see it jumping back and forth:

https://www.dropbox.com/s/uk6tqvzbtv9moi4/GPS%20issue%20zoomed.png?dl=0

Just to verify, does the same error exist if you install GPSDirect from the GUI?

If your GPS already exposes a sensor interface then GPSComplete is not needed.

If not, then usually with some configuration mechanism, a USB device can emulate a serial port.

If your hardware cannot expose a com port, then it cannot be used with GPSComplete.

I was able to get a sensor driver loaded by using GPSDirect that I got from Google.

https://drive.google.com/drive/folders/0B4u-2njuXGa1UUNGT0M3aEtNc1U

Was able to fix my privacy settings which then allowed me to use a usb gps device.

Thanks for your help.

The existence of a GPS device does not necessarily mean that it be possible to map it as a sensor.

The error you are seeing means that the required libraries are missing from Windows. For example, all server versions do not have the sensor interface.

For client versions, check any possible option in control panel to enable the sensor interfaces, or perhaps a hardware button.

M.

Hello there. The driver outputs both \r\n. 

You can test the sentences in http://freenmea.net/decoder

M.

Are you sure that the original gps data is consistent? That is, your device does not lose the signal?

NMEA 2.0? Take a look to check if nmea 0183 can be set.

did you ever figure out how to install it in client mode?

Thanks for the instructions. Unfortunatley, it seems that now the GPS sentences sent to the virtual port, are incomplete or broken.

I will try to fix it and, eventually, come back in the forum

ciao and thanks Piero

The client mode is available in GPSReverse installation (menu COM Port Driver -> Install).

Ciao support team, the problem is exactly how to install GPS reverse in client mode:

- I have downloaded the last version at 64 bit from your site (I am a licensed user). It is one executable "GPSComplete64"

- There is no installation procedure. When I launch it I see the window of the program, but there are no options for "client mode" anywere.

- I tried the procedure several times but no success in configuring and running the transfer tool.

What am I doing wrong?

ciao and thanks Piero

Hello there.

1. Install GPSReverse in Client mode

2. Install TT to forward sensor to GPSReverse

3. You are ready to use GPSReverse.

M.

Got it to work, what an amazing product. 

FYI, I am using a Sierra Wireless Airlink GSX450   for a GPS device with a static IP that is connected to a computer with a USB cable to push data to my navigation applications. Often the USB would come loose and the application would  fail. The proposed solution was to try and get the GPS UDP packets from the GPS device over the ethernet or wirelessly (for portability in our machine's cab). We set up the device to broadcast the packets and created a listening server to capture each of the packets and then send them back out using TCP protocol and override the location sensor on our Surface Pros with your program.

Your program bridged the location services gap and saved me hundreds of lines of code that would have been required to override the coordinates in each application. What is even better,  some of my out of the box applications can run in tandem with my custom ones because of our static IP requirement for enterprise purposes.

Thank you.

The nmea is valid (http://freenmea.net/decoder).

Did you also enable high precision in the driver setup?

Thanks for such a quick response.

I typically don't program with sockets but I set up a python TCP server and client and was able to pass my NMEA string to the client. However, I am not able to override the sensor on the device or get a good coordinate test. On a good note, when I installed the sensor driver my server did recognize the connection. I think I am getting close but must be missing something small.

- for a test I did set up an HTTP server to feed the strings as raw text but no luck :)

The tcp data is in two formats, neither of which created a location. Simulation and fixed modes worked perfectly on my surface pro, which was awesome.

Formats

• As message parts with new line characters at the end of each line
  

$GPGGA,140034.0,3616.251543,N,08642.748318,W,1,08,1.0,163.3,M,-26.0,M,,*64
$GPRMC,140034.0,A,3616.251543,N,08642.748318,W,0.0,16.1,101017,0.0,E,A*2A
$GPVTG,16.1,T,16.1,M,0.0,N,0.0,K,A*23

• As a single message

$GPGGA,140034.0,3616.251543,N,08642.748318,W,1,08,1.0,163.3,M,-26.0,M,,*64$GPRMC,140034.0,A,3616.251543,N,08642.748318,W,0.0,16.1,101017,0.0,E,A*2A$GPVTG,16.1,T,16.1,M,0.0,N,0.0,K,A*23

Thanks,

Tom

Try with 16299.

I will take a look, did you try using the share mode? Some drivers require that.

M.

Are the two devices in the same network?

It works over IP, not over bluetooth.

The Transfer Tool is useful when the reverse driver cannot access an existing sensor because the sensor is only visible to non-drivers. That is where it is used, no where else.

Why you connect to the emulator android and not to a real-life android device?

Also, in the android emulator you can use GPS apps.

Generally, the driver works with most hardware immediately, but some setups require a bit of research.

I am glad you made it. You can use your friend's paypal to get a license.

Best.

I'm not aware of this problem, what GPS chipset is your hardware?

M.

Hello.

1.Do the gps lines (gga,rmc) in anyport tester show correct location?

2.Does the sensor explorer show correct location when GPSDirect is selected?

Play with the shared option to open t the com port.

first i forgot to run GPScomplet in admin mode, it probably explains that the process was not fully done

it is not fully clean, when i install the sensor driver, GPSinfo app still doesn't work, but reinstalling the original driver fix it and the sensor driver remains installed, so all my apps can work together: either GPSinfo, MapFactor or GPS map+

for me it is ok, many thanks for this update

jean-michel

Play with the shared option to open t the com port.

don't know what you mean ? i tried both using the shared option and without checking it, it makes no difference 

just forgot a point, when I INSTALL the sensor driver, it nevers ends correctly with a message saying "installed" the application stays locked "not responding" and   I must force it to stop and then I reopen to verify that the sensor has been installed.

Maybee the process is not fully done ?

I have updated the driver, take a look.

here are links to my USB GPS
http://usglobalsat.com/p-688-bu-353-s4.aspx#images/product/large/688.jpg

http://usglobalsat.com/s-172-bu-353-s4-support.aspx

Play with the shared option to open t the com port.

I have updated the driver, take a look.

- in all cases, previous version or new one (with or w/o checking the com shared option) the application GPSinfo provided with the USB GPS and the "GPS to serial driver" doesn't work anymore after using GPSComplete

- to fix it i have to reinstall the provided "GPS to serial driver" 

- using MapFactor GPS navigation (from windows store) it works only with GPSComplete (nothing new with the new version)

- i did'nt try again CartePro (or MapPro) which is supposed to support both modes (sensor or USB) my evaluation version has expired

anyway GPSinfo works only with the USB driver and Mapfactor works only with the sensor driver, so it is good enough for testing.

i am waiting for a new update from you and/or your advices

Jean-Michel

Hello there.

It depends on the com port. Sometimes it can be shared, sometimes it cannot. GPSDirect usually locks the com port, but a further update will allow it to keep it unlocked. It should be available in a few days.

As for the license, buying a personal license will help us enhance the development of GPSDirect.

Best,