SIRIUS F9P : Never RTK FIX

ZED-F9P RTK
1

Hello,

I am a new user and have had a problem for a while …

My hardware configuration is:

ROVER SIRIUS RTK GNSS F9P / TELEMETRY 433 Mhz / Software U-CENTER
and
BASE SIRIUS RTK GNSS F9P / TELEMETRY 433 Mhz

On my base:

RTCM3.3 1005 > UART2 / USB
RTCM3.3 1074 > UART2 / USB
RTCM3.3 1084 > UART2 / USB
RTCM3.3 1094 > UART2 / USB
RTCM3.3 1097 > UART2 / USB
RTCM3.3 1124 > UART2 / USB
RTCM3.3 1127 > UART2 / USB
RTCM3.3 1230 > UART2 / USB
RTCM3.3 4072.0 > UART2 / USB
RTCM3.3 4072.1 > UART2 / USB

NMEA GxGGA > USB
NMEA GxGLL > USB
NMEA GxGSA > USB
NMEA GxGSV > USB
NMEA GxRMC > USB
NMEA GxVTG > USB
NMEA GxGRS > USB
NMEA GxGST > USB
NMEA GxZDA > USB
NMEA GxGBS > USB
NMEA GxDTM > USB
NMEA GxGNS > USB
NMEA GxVLW > USB

NAV-STATUS > USB

RATE : 1000ms

SURVEY-IN : 60s / 1.5m

UART2 :

  • RTCM3 : IN / OUT
  • 57600 baud

On my rover:

NAV-POSLLH > UART2 / USB
NAV-STATUS > UART2 / USB
NAV-VELNED > UART2 / USB

NMEA GxGGA > USB
NMEA GxGLL > USB
NMEA GxGSA > USB
NMEA GxGSV > USB
NMEA GxRMC > USB
NMEA GxVTG > USB
NMEA GxGRS > USB
NMEA GxGST > USB
NMEA GxZDA > USB
NMEA GxGBS > USB
NMEA GxDTM > USB
NMEA GxGNS > USB
NMEA GxVLW > USB

NAV-STATUS > USB

RATE : 200ms

UART2 :

  • RTCM3 : IN
  • 57600 baud

Of course the 433 Mhz radios are at the same speed : 57600 baud (I tried different configurations: mavlink, rawdata …).

I am permanently in 3D !
Looks like I’m not getting RTCM frames, yet on the U-CENTER screenshot on the rover you can see I’m getting them …

exemple_center
exemple_center1366×728 306 KB

Could you give me the possible reasons?
My configuration is not correct?

Could you help me ? I don’t know what to do.

Thank you so much.
Olivier

2

Get back to the basic RTK test by connecting the Base UART-RTCM port directly to the Rover. (stop using Radio).
Then report the results again.

3

Thank you for your reply.
I have already tried this solution, I have connected the UART of the base to the rover. But I’m still in 3D.
I looked in “RTCM input status” I do receive frames on the rover (screenshot below).
Thank you so much.
Olivier

exemple_center2
exemple_center21366×728 305 KB

4

Hi again.

5

Receiver needs to be in TIME mode, check reporting from UBX-NAV-PVT
After taking a close look at the photos you provide.
I have a couple of solutions that you can try: (do this for F9P Base)

  • Turn off export RTCM-4072 message and turn on export RTCM-1005 message back .
  • Use static position: Set Base a static coordinate value and static survey mode (Do not use Survey-In mode).
6

Hello and thank you very much for your response.
I finally switched to RTK FIX !!!

FIXED
FIXED1366×728 307 KB

On the F9P BASE I disabled the RTCM-4072, the RTCM-1005 was already active, and I disabled SURVEY-IN mode, and it works!

On the other hand, deactivating the SURVEY-IN mode is very annoying. The base will be moved regularly and it will be very difficult to hard grip the position each time.

How can I do ?
Why is SURVEY-IN mode not working?

Thank you very much for your valuable advice.

Olivier

7

I’m answering my own question …

SURVEY-IN mode is not suitable for RTK FIX because it does not define the base position precisely enough. That’s it ?

8

Congratulations . I responded with my experience.
I don’t have their code. Only Ublox’s developers know exactly what’s going on.
Survey-IN was created to work exactly as described (automatically converging position for a preset time), but unfortunately it doesn’t work, at least until now.

Only one way to deal with it is to try to mark the place you will go back again , and hope until someone finds a bug and fix it in the next update version .

9

Hello and thank you, your help has been very invaluable to me.
It is nice to talk to nice and knowledgeable people.
Thanks again and have a nice day!

10

Thanks. You too.