If you are still not getting updates, and there are no errors in the Application log, we need to make sure that the GPS/GNSS is running and has a fix.
This procedure can vary significantly between different brands of tablets and GPS/GNSS devices. It is best if you try to get a fix Outside
, away from all obstructions. Some tablets may Never
get a fix indoors (my Asus will not)
Tools you'll need
- GPS Satellite (get this from the Windows 8 Store) - Not the best, but it will show you when your on-board GPS/GNSS is producing data, rather than just the location platform
- GPSView version 1.2.2 allows you to view NMEA data coming through the port from your GPS and in some cases, allows you to set the baud rate and other parameters of you device
- GPSView 2.0.16 is just a newer version of the above. Always nice to get a different view of the same data.
- Sensor Diagnostic Tool this is the important one, right here. Allows you to see all the sensors on your device, what kind of properties and what kind of data they produce. And you can watch it in real time so you know it is working. You can also capture the data to a log file.
Always start with a clear view of the sky. The cheapest standalone GPS device made probably has a bigger and better GPS antenna than your tablet. Trying to get a fix when you're inside the house is just adding an additional problem to the situation. Go outside, startup GPS Satellite, and wait until you have valid GPS/GNSS data shown. Your horizontal error should be less significantly less than 100 meters. If it's not, then you are not getting your location data from the GPS/GNSS it's as simple as that.
Don't go any further. If you cannot complete Step 1, and get a valid signal and data from GPS Satellite, there isn't much point in going any further. Something is wrong with your GPS/GNSS chip. Either the driver is corrupt or missing, or there is some other issue. Open the sensor diagnostics tool and see if it can even identify a GPS/GNSS sensor. If it can, then the problem is very likely the driver itself. If this is the case, check with your manufacturer about getting a new driver for your chip. Lenovo's driver for the Broadcom GNSS chipset will work on many different tablets.
If you've got a signal, great! Now open the sensor diagnostics tool, highlight the GPS/GNSS sensor and take a look at the output. In the top window on the right, you'll see the general properties of your device. In the middle window, you should see an ever-changing stream of position and satellite data, including NMEA data (more on that in a moment). The bottom windows should be a steady stream of Sensor Data events, with an occasional Sensor Status Change event (but possibly not).
If all that looks good, here's how you take a look at your NMEA data. In the menu at the top, click events. Now uncheck "Show Events". That will stop the flow of event data, and you can now scroll the middle window (data) down to show the NMEA string, typically the last item in the list.
At this point, you have validated that you have a GPS/GNSS chip, that it is able to acquire and lock to the satellite signal, and that it is delivering valid information into the system. Now we're ready for Localizer.
Localizer installs virtual comport driver software during setup. Please consult the installation how-to for further instructions on installing Localizer. Assuming that Localizer had been successfully installed, here's what you should see:
- Start Localizer and display the interface. If you have not selected a port to use, do so now. The info panel should be showing all "000" and the GPS status should say "Detecting GPS/GNSS Sensor" or similar wording.
- Once the Sensor is detected, the status text turns green and reports "Ready". You should see positional data displayed in the info window very shortly thereafter.
- Once you see values start changing, you should also see NMEA data displayed in the window at the bottom of the UI. At this point Localizer is working, and you can minimize it or leave it visible on the desktop.
- To validate the NMEA data, open GPSView 1.2.2, and connect to your assigned port with a baud rate of 9600. You should see position data, and if you open the NMEA tab, you'll see NMEA strings displayed. If you cannot open the serial port for any reason, check Device manager to make sure it shows up properly. If it doesn't, see the install guide on how to fix problems with the virtual serial port software.
If you are seeing NMEA strings, then you're done. That's ALL Localizer is advertised to do...provide NMEA data out a virtual comport for use by an application.
Where do I find the error log? Localizer writes its errors to the Windows Application Log. They are all prefaced with the name Localizer, and actual errors will have a yellow "Warning" icon.