• Home
  • Popular
  • Login
  • Signup
  • Cookie
  • Terms of Service
  • Privacy Policy
avatar

Posted by User Bot


01 Dec, 2024

Updated at 14 Dec, 2024

Why am I not getting NMEA output in RTKLib despite providing all required RTCM data?

I am working on an RTK-based positioning system, and I’ve encountered an issue while using RTK Navi software with RTCM data. Here’s a brief overview of what I’m doing and the issue I'm facing:

Workflow:

1.Raw Signal File: I have a raw GNSS signal file from this source

2.Conversion to RTCM: I’ve used GNSS-SDR to process and convert this raw GNSS signal to RTCM data.

3.RTK Navi Configuration: I’m sending this RTCM data to RTK Navi (in rover mode) via a TCP server stream in single positioning mode.

RTCM Data Breakdown:

The RTCM message contains:

1019 Message: GPS ephemeris data

1077 Message: MSM (Multiple Signal Messages) which contains satellite observations

Logs from RTK Navi: Despite having both ephemeris data (from the 1019 message) and observation data (from the 1077 message),

I’m seeing the following logs in RTK Navi:

3 outsolheads:
3     0.102: rtksvrthread:
3 decode_rtcm3: len= 64 type=1019
3 outsolexs:
3 outnmea_gsa:
3 outnmea_gsv:
3 outsolexs:
3 decode_rtcm3: len= 64 type=1019
3 decode_rtcm3: len= 64 type=1019
3 outsolexs:
3 outnmea_gsa:
3 outnmea_gsv:
3 outsolexs:
3 decode_rtcm3: len= 98 type=1077
3 rtcm3 1077: signals=L1C
3 sortobs: nobs=5
3 rtkpos  : time=2024/11/28 06:24:06.180 n=5
3 pntpos  : tobs=2024/11/28 06:24:06.180 n=5
3 satposs : teph=2024/11/28 06:24:06.180 n=5 ephopt=0
2 no broadcast ephemeris: 2024/11/28 06:24:06 sat= 1 iode= -1
3 no broadcast clock 2024/11/28 06:24:06.102 sat= 1
2 no broadcast ephemeris: 2024/11/28 06:24:06 sat=11 iode= -1
3 no broadcast clock 2024/11/28 06:24:06.098 sat=11
2 no broadcast ephemeris: 2024/11/28 06:24:06 sat=17 iode= -1
3 no broadcast clock 2024/11/28 06:24:06.097 sat=17
2 no broadcast ephemeris: 2024/11/28 06:24:06 sat=20 iode= -1
3 no broadcast clock 2024/11/28 06:24:06.104 sat=20
2 no broadcast ephemeris: 2024/11/28 06:24:06 sat=32 iode= -1
3 no broadcast clock 2024/11/28 06:24:06.100 sat=32
3 estpos  : n=5
3 rescode: rr=0.000 0.000 0.000
2 06:24:06.18: point pos error (lack of valid sats ns=6)

The log suggests that no broadcast ephemeris data is being received for certain satellites (e.g., sat=1, sat=11, sat=17, etc.), which might be causing issues with the position calculation. The point position error indicates a lack of valid satellites, despite having satellite observations.

I have parsed the RTCM message and confirmed that the data contains the GPS ephemeris (1019) and satellite observations (1077),following is the output:

RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 
RTCM Message: 

My Question:

1.Why is RTK Navi not able to process the RTCM data correctly and output the NMEA messages as expected?

2.Are there any issues with the RTCM data (1019 and 1077 messages) or configuration that might prevent RTKLib from processing and outputting NMEA data?

3.How can I ensure that RTK Navi or RTKLib is properly processing the ephemeris and observation data from the RTCM messages and outputting NMEA correctly?

Additional Information:

1.I’m using RTKLib by cloning this https://github.com/rtklibexplorer/RTKLIB repository and build code for linux.

2.The RTCM data is being sent over TCP in real-time to the software.

3.The rover is in single positioning mode.