The GPS sensor driver suite for Windows.
Windows 10/11 x64 (New Interface)
Download Windows 10/11 x64Windows 7-11 x64
Download Windows 7-11 x64Windows 7-11 x86
Download Windows 7-11 x86
The drivers come with an evaluation license (if you only use the Simulation or Fixed modes, you will be granted a license for free as long as you mention the driver in your site/blog). If you want a standard license, please select one of the two options below. Before purchasing, try the evaluation versions to verify that they work with your hardware. If they do not work with your hardware, do not purchase, but contact us instead.
PayPal Personal payments are usually instantly processed, so if you do not receive a mail from us in the next 24 hours, check your spam folder or contact me via the Business Contact.
|
GPSDirect + GPSReverse (Bundle) EUR 14,99 | |
|
GPSDirect EUR 9,99 | |
|
GPSReverse EUR 9,99 |
Have I tested the COM port for actual GPS Data in NMEA format? You should see NMEA messages that start with $GPGGA, $GPRMC, $GPGSV etc.
Have I checked c:\windows\inf\setupapi.dev.log for installation errors?
Do I need the transfer tool in case where direct connection fails? (Install with Injection mode).
Is GPSReverse correctly installed? Test with a COM port tool, you should see NMEA messages.
Have I checked c:\windows\inf\setupapi.dev.log for installation errors?
Do I need the transfer tool in case where direct connection fails? (Install with Client mode).
Am I trying to use the COM port from multiple applications. Install with the multithreading mode on.
Request a business license that allows you to use GPSDirect or GPSReverse in your apps or redistribute it as a company or for mass redistribution or for C++ source code licensing in the Business Support here.
The configuration of your data forwarding mode heavily impacts how the system recovers from or succumbs to process hangs. Operational Vector Centralized Forwarding (Tunneling) Local Forwarding (Autonomous) Capsulates and tunnels frames to a central controller. Processes and routes data frames directly at the AP level. Wired Bandwidth Drain
“EWP hang” is not simply a direct substitution of solid lumber practices. Engineers and framers must consult EWP manufacturer literature and hangar evaluation reports (e.g., ICC-ES ESR-1782 for I-joists). Failure to account for EWP-specific connection behavior leads to crushing, splitting, or premature collapse.
Follow this sequence to clear the process backlog and protect your network hardware from repetitive lockups:
The core of the EWP Hang is geometry. It is the study of how weight distributes across the body. When you dial in a perfect hang, you stop feeling the weight of your gear; you only feel its presence. ewp hang
The EWP Hang is more than a way to carry a wallet. It is a statement of intent. It says that you value order over chaos, function over form, and readiness over reliance.
There is a deeper psychological comfort to the EWP Hang: the concept of the tether. In a world where we are constantly losing things—phones, keys, patience—the EWP Hang represents an unbreakable link.
Equipment tagged out of service and quarantined for inspection. The configuration of your data forwarding mode heavily
Properly detailed EWP hangars, using web stiffeners and approved connectors, can equal or exceed solid-sawn lumber performance.
I can provide the specific CLI commands needed to adjust your system timers.
Advanced endpoint scanners dynamically query device compliance. Out-of-sync security policy servers fail to release isolation tags, causing internal application loops. Wired Bandwidth Drain “EWP hang” is not simply
A bad hang is a distraction—it pulls on your belt loop, it creates a bulge in your pocket, it turns a tool into a burden. A perfect EWP Hang, however, creates a state of zero friction. It is the art of aligning the center of gravity so that the wallet, the chain, and the tools move with you, not against you. It is the difference between carrying a load and wearing an extension of yourself.
The system periodically issues verification pulses. A high density of 802.1X enterprise clients failing to answer within the maximum attempt threshold can flood the buffer.