- Install usb virtual port inf how to#
- Install usb virtual port inf install#
- Install usb virtual port inf serial#
- Install usb virtual port inf drivers#
Note: When the Olimexino has just started up and is still in bootload mode it will show up in the device manager as WinUSB Bulk Device. Please remember the COM port which has been assigned to it. After the installation Windows should now recognize the Olimexino as STMicroelectronics Virtual COM Port, see below:
Install usb virtual port inf install#
Install the correct driver by running VCP_V1.3.1_Setup.exe or VCP_V1.3.1_Setup_圆4.exe located in the directory: /Installs/Drivers/VirtualCOMport/įollow the instructions given by the installer. This is not the right driver, unfortunately another driver has to be installed, hang on this is the last step. When the Olimexino is connected the device manager will show it as STM32 Virtual COM port. To use HANtune over USB a virtual COM port is used to connect to the STM32 Olimexino. By reading these signals, you can see if the software is working correctly and the parameters can be changed to tune the algorithm. HANtune is a PC program that reads signals (variables) and writes parameters (constants) from/to the board. To revert to the older u-blox driver with Windows 10, you will want to first download that driver from the u-blox Product Resource page, then follow the instructions inside the blue circle.To read the variables and change the parameters that are in the model, you can use HANtune. To revert to the generic Windows driver with Windows 10, follow the instructions in the blue circle above. Here is a copy of the document but it may be too small to read here and may be out of date by the time you read this so I suggest you click on this link to take you to the original document.
Install usb virtual port inf how to#
U-blox has published a flowchart on their website to help users decide which driver to use and how to rollback to older drivers. The older driver is listed as “u-blox GNSS Standard Driver for Windows”.
Install usb virtual port inf drivers#
I recommend this one.Īll three u-blox drivers are available for download from their Product Resources page. So far I have found it works fine, and it does not automatically get replaced by Windows like the generic driver does. U-blox recommends this for older versions of Windows but I have started using this recently with Windows 10. U-blox GNSS Reciever (COMx): This is the older u-blox driver before they switched to the sensor interface. It has some limitations though, the primary one being that you can only run one of these devices on a computer at a time, so I don’t recommend this one either. U-blox Virtual COM Port (COMx): This is the driver recommended by u-blox if you want to support both the sensor interface and the COM port interface. It will work fine with RTKLIB, but Windows has an annoying habit of automatically replacing it with the sensor driver, so I have recently stopped using this one.
Install usb virtual port inf serial#
USB Serial Device (COMx): This is the generic COM port Windows driver and is what u-blox recommends for Windows 10 when using the COM port interface. If it shows up under “Ports” it may be listed in one of three different ways depending on which driver is installed. Here is an example of what it looks like when it shows up under “Ports”: If it shows up under “Sensors” then RTKLIB will not be able to see it. The receiver will either show up under “Ports” or under “Sensors”.
You can determine which driver you are using by opening the Windows Device Manager while the u-blox reciever is plugged into the computer. To make things more confusing, there are actually three different drivers that will support the COM port interface. RTKLIB does not support sensor device drivers, so it is necessary to force the driver installation process to revert to a driver that supports the COM port interface. Installing the u-blox USB drivers for Windows for use with RTKLIB can be a little tricky now that u-blox has switched their default Windows configuration from using COM port drivers to using sensor device drivers.