uBlox ZED-F9T-00B-01 RTK problem

GPS/GNSS Development Boards
1

I have a Zed F9T 00B gnss board with a sparkfun TOP106 L1/L2 antenna. Firmware is TM 2.01. I have been trying to get it to fix an RTK solution using Leica Smartnet corrections delivered in RTCM3. I have tried the u-center ntrip client as well as Lefebure ntrip client. I have tried via the USB port and UART 2 (via a serial basic). I am pretty sure the ports are set correctly and working as I see NMEA data streaming through. I have all the ports set to see RTCM3 (eg CFG-UART2INPROT-RTCM3X (0x10750004) = 1) by sending to RAM BBR and Flash then saving. I have had the antenna in open sky and inside with an OK signal. I have set the dynamic mode to various settings. Not once has the Fix Mode left 3D and floated or fixed.

In statistics view in ucenter, the Fix Type (GPS) is 3D, Fix Type (GPS) valid is yes, but the DGPS is No. (I would think it would say yes if corrections were present but not able to yield a float or fix). I have tried to set the UBX-CFG-DGNSS to 3 RTK Fixed ambiguities are fixed whenever possible. SBAS is off.

Does anyone have any insight on this? Do I need new firmware? despite this board and antenna set up being able to see L1/L2, is there a limitation on it being able to operate as an RTK rover?

My end goal is this GNSS board being part of an ASV hydrographic survey platform.

Thanks in advance.

2

Hi,

Looking at the ZED-F9T Product Summary, it doesn’t mention RTK Base or Rover:

https://www.u-blox.com/sites/default/fi … 011626.pdf

Neither does the Line Card:

https://www.u-blox.com/sites/default/fi … 004717.pdf

You would expect that it could, but maybe this is a limitation of the TIM firmware. Unfortunately I don’t have one here I can test. Maybe fixed-position time-mode is more its thing?

You could ask this question on the u-blox support portal: https://portal.u-blox.com/s/

I hope this helps,

Paul

3

With the board being able to resolve L1/L2 and all the mention of RTCM corrections, I kind of assumed that RTK was part of the bag of tricks. I guess it’s another case of firmware shackles on functionality, which is all too common.

Thanks for the reply.

Dallon