Internal GNSS driver options for Mesa 3 and Mesa 2 with Windows
8 Nov 2019
The GNSS Driver Options utility for the Mesa 3 and Mesa 2 with Windows can help with making the integrating u-Blox NEO M8 series GNSS receiver work with specific software applications, or resolve other potential issues.
Drivers for the internal GNSS (GPS) receiver in the Mesa 3 and Mesa 2 install automatically through Windows Update. Though not all apps are compatible with the latest drivers for the u-Blox NEO M8 series GNSS receiver. Some previous Mesa 2 units may even encounter an issue where drivers may disappear and be prevented from installing after a major Windows Update. If needing assistance with getting these drivers to work properly with your apps, download and extract the following file, then review the extracted "GNSS Drivers Readme.pdf" document.
Separate links to the previously recommended drivers are as follows.
- uBlox VCP (Virtual COM Port) Device Driver version 2.30
- uBlox Location Sensor Device Driver version 2.30
With our Mesa 2 OS Build Version 17178 and 17255 pre-installed on new units in production between August 2017 and January 2018, we also pre-installed the previous version 2.30 drivers and set a group policy to prevent them from updating. If needed, instructions for removing this group policy are provided in the release notes documents for those OS Builds or in the following article.
If the "Mesa 2 GNSS Driver Options" utility above does not work for you, installing the version 2.30 drivers may require performing a Roll Back from a later version more than once to be more permanent. This is done as follows.
- Tap and hold on the bottom-left Start (Windows logo) button then select Device Manager.
- In Device Manager under Sensors, tap and hold on "u-blox GNSS Location Sensor" then select Properties.
- Under the Driver tab, view the Driver Version to be 2.30 and if not then Roll Back or Uninstall (with "Delete the driver software for this device" if necessary).
- If needed, use the installer above to restore the version 2.30 driver.
- In Device Manager you may need to tap on the Action menu > "Scan for hardware changes" to recover the device.
- If the Driver Version is again not 2.30, perform a Roll Back as explained in step 3.
- Repeat as needed.
- Follow the same steps for the "u-blox Virtual COM Port" in Device Manager under Ports (COM & LPT).
Or you can manually setup a group policy to prevent these drivers from updating. This is done as follows.
WARNING: Setting a group policy to prevent driver updates may stop drivers from working after Windows Update.
Add group policy for u-blox drivers
- Win+R, gpedit.msc
- Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions
- Double click "Prevent installation of devices that match any of these Device IDs".
- Click the "Enabled" radio button
- Click the "Show" Button
- Enter two items (copy and paste from Device Manager): UBLOXVCP\PNP0501 USB\VID_1546&PID_01A8
After getting the drivers to work as needed, we also recommend performing a "Reset Receiver" using Geode Connect".
Version 2.32 and higher of the u-Blox Location Sensor driver enables binary UBX strings which, even if disabled, will automatic re-enable after disconnecting and re-connecting receiver. These UBX strings may cause issues with apps such as Geode Connect 1.2.0 or older and Farmworks Mobile (formerly SiteMate). An alternative technical method to disable these in the later drivers is available in u-Center, but it is recommended to instead update apps to use the newer Location Sensor programming functions.
Version 3.x of the u-Blox VCP driver may not be compatible with apps which were written using a .NET programming language and which call the standard .NET Framework serial communication programming functions, such as Geode Connect 1.2.0 or older. Other previous apps which use the virtual COM port number to access the receiver may also encounter issues. Again it is recommended to update apps to use the newer Location Sensor programming functions instead of legacy serial communications.
Some related articles are as follows.