Find the Connect-button on the toolbar and press the dropdown button see which COM-ports are available. Close the dropdown.
Connect the uBlox receiver, wait a bit for Windows to configure the device, press the Connect-dropdown again, and select the new COM-port.
The COM-port number can also be found using Windows Device Manager. Sometimes with the new uBlox driver, it does not register correctly and it needs to be uninstalled from the device manager. Right click the device, go to Update Driver, "Browse my computer for driver software", "Let me pick from a list", select a uBlox COM port, choose "Next" and install this driver instead.
To read what each message type does, and poll the receiver for the current reading, open the “Messages” view in u-center: [F9]
Now open the "Configure" view in u-center: [Ctrl] + [F9]
In this view, each configuration is pulled automatically from the receiver. To check that you have a valid connection, go to a random menu, change the value (without pressing "Send"), press the "Poll"-button, and verify that the value changes back.
After each change you make, make sure to press the "Send"-button at the bottom left of the window. If not your changes will be discarded.
After all changes have been made, to store the changes to the uBlox's non-volatile memory, go to CFG, make sure "Save current configuration" and "0 - BBR" and "FLASH" are selected, and press "Send". Without this, all the changes are discarded when you power off the uBlox.
If you’re trying to select a menu item that is not available for the connected receiver, the menu item will just jump to another value, so make sure you’re changing the correct value.
The following changes should be made to both the base and the rover receivers for RTK GNSS (with the SenTiBoard). If the base and rovers are the same, you can save the setup on the first receiver and load it on the second (Tools -> GNSS Configuration...). Remember to press “Send” after every change. This is just a suggested setup, and an actual setup should be set to fit your purpose. All binary uBlox messages are supported by the SenTiBoard with the default setup.
NAV5 (Navigation 5)
Dynamic model: 7 – Airborne < 2g (change this as needed)
Fix Mode: 3 – Auto 2D/3D (unsure)
UTC Standard: 3 – USNO (GPS) (unsure)
Min SV Elevation: 12 (unsure)
Target: 1 - UART1
Protocol in: 0 - UBX
Protocol out: 0 - UBX
Target: 3 - USB
Protocol in: 0+1 - UBX+NMEA
Protocol out: 0+1 - UBX+NMEA
Protocol in: none
Protocol out: none
Time source: 1 - GPS time
Measurement Period: 100 ms
Navigation Rate: 10 cyc
Note, on some firmwares you can’t set nav. rate to 10, and then you can’t use GLONASS
Pulse mode: -1 – falling edge
Pulse period: 1000 ms
Pulse frequency: 1 Hz
Pulse length: 100 ms
Time source: 1 – GPS time
GNSS (GNSS Config)
Configure and enable both GPS and maybe GLONASS (needs testing)
Disable the others.
Turn off all messages, except the ones specified below (this is a hassle right now, as you need to go through all messages and turn off each one).
For all the messages below, turn on UART1 and USB (not needed for UAV-receiver). Disable the others.
For accurate time calculation, and single pos. accuracy, choose one of:
Remember to save the configuration to the uBlox FLASH
“Save current configuration”
“0 - BBR” (not sure if this is needed, but I’ve always used it)
“1 – FLASH”
Now, power off the uBlox. Connect to it up again and make sure your configuration is saved.