RS2 RTK issues

I’m having the same issue, haven’t been getting fix on Ntrip after updating.

1 Like

Hi Abiodun,

To help us to determine the issue, please, share the following:

  • screenshot of the Correction Input tab while receiving corrections on your Reach RS2 with raw data debug option on
  • the raw data log, position log, and base correction log from the rover

raw_202011170733_UBX.zip (2.0 MB) base_202011170747_RTCM3.zip (19.9 KB) Final1.zip (22 Bytes)

raw_202011170800_UBX.zip (31.4 KB) base_202011170800_RINEX-3_03.zip (1.2 KB) base_202011170800_rtcm3.zip (314.1 KB) raw_202011170801_UBX.zip (2.9 MB)

Hi Abiodun,

Thanks for the logs! I’ll check them and get back with the news.

I think the problem is the mountpoint which is only a DGPS (dm-accuracy)

Hi Abiodun,

Thanks for your patience!

I’ve checked your data. It looks like the corrections from the base are not in RTCM3 format. That’s why the receiver can’t use them for calculation.

Please check the connection with another Mount Point that can share the RTCM3 corrections. It’d be also helpful if you could share the screenshot of the Correction Input tab while the grey tick next to the connection message is pressed: this will help us to see the correction messages that the NTRIP sends.

2 Likes