Brett Roberts
EF5
I recently went through this fiasco on my new tablet, too. GPSDirect is a finicky program that doesn't seem to operate in the way that something like GPSGate does, where you open it, leave it running, and viola -- everything works. Instead, it installs the driver for a fake "device" which creates the link between your COM port and the Windows Location Services position. It looks to me like all it does is perform this installation, and that starting the program on subsequent boots doesn't do anything in particular to re-activate the COM-WLS link.I recently began setting up a Toshiba Encore tablet (Win 8.1) for the express purpose of replacing my notebook computer and mount yet, keeping the overall functionality. I've loaded the typical apps (GRL3, GPSGate, Spotter Network, etc.) Which all seem to operate well in desktop mode. The problem I'm now running into is Incorporating "Metro" applications into the mix. Primarily mapping programs which require "Windows Location Services"
I've followed the advice and instruction of Nick Nolte's installation of "GPS Direct" and have not had any success in getting that particular app to function as it should. I can direct known good COM ports with good GPS data to this application and it basically does nothing. I can't find any recent updates to this app since others have pointed out that this app seemed to break when a recent update was applied. My question is if anyone has had recent success installing this in an 8.1 tablet or if they are seeing the same issue as I? I don't want to spend any further time on this if it is irreparably broken or if support has gone away. But it seems to be the only option when incorporating an external GPS into 8.1 Metro applications.
After installing the driver in GPSDirect, if you go to Device Manager, you should see a device called "gpsdirect" under the Sensors category. The key for me was that every time I reconnect my bluetooth GPS puck, this virtual device needs to be disabled and then re-enabled. Re-enabling it seems to force Windows to "look" for the data on the COM port again. You can do this manually each time, but it's kind of a pain. What I've done to help out is to use Task Scheduler in Windows, along with a free program called devmanview, to force the disable/enable action to happen 30 s after startup -- this way, as long as I turn my bluetooth puck on before or during startup, GPSGate is already sending information to the virtual COM port by the time gpsdirect starts looking for it. One could also create a batch script that calls devmanview and does the disabling/enabling, then place that script on your desktop for an easy one-click action after you've connected your GPS puck. The *program* GPSDirect is never needed beyond the initial driver installation (at least, WLS is now getting my GPS position after doing the disable/enable without the program ever running).
Of course, this all assumes that the driver installation is working and that you're getting data into WLS during the initial install. From your post, I can't tell if you're having trouble with that as well. For me, if I remember correctly, I had to play with the baud rate a couple times before it worked. If you choose the correct COM/baud and then click "Install," you should see accurate GPS data begin showing up at the bottom of the window (under "Testing") shortly afterwards. If you don't, try clicking "Get ILocation" just to make sure.
If you have any more trouble, let me know, and I can double-check my setup. One thing is for sure: this process alone will make me think twice about ever reformatting/reinstalling Windows on my tablet!