Difference between NMEA and POS files

Reach Module / M+ / M2 RTK / PPK configuration
1

I’ve been using RTKNavi to process two CORS stations (26Km apart) and noticed a difference between the logged RTK NMEA output from RTKNavi and the POS file from RTKpost using the converted RCTM files from logged output of RTKnavi

I load the NMEA into RTKPlot and the centre of the cluster is one location and load the POS file and get a different centre location. If I load both at the same time (Solution 1 and 2) they overlap.
What I’m doing wrong or incorrectly interpreting ?

2020-07-16 14_32_06-Greenshot
2020-07-16 14_32_06-Greenshot1366×768 94.2 KB
2020-07-16 14_28_07-Greenshot
2020-07-16 14_28_07-Greenshot1366×768 92.4 KB

What it appears to be, is a discrepancy between the cursor? position (bottom right) and the log position (lower left) for the same place on the screen with the POS file - they read the same with the NMEA file

(This version 2.4.3 b31 of RTKplot)

2020-07-16 15_16_36-Greenshot
2020-07-16 15_16_36-Greenshot1366×768 110 KB

2

I think it’s a bug in that version, watch out with versions of RTKlib giving different results !

1 Like
3

What filter did you use? Forward/Backward/Combined?

Maybe try version b33 from their support site?

You could try going backwards to b28 as well…

4

I used the combined filter, but version 2.4.3 demo5 b26 seems to give the results I would expect.

It seems with some many different versions of RTKlib most with minor bugs and varying results.

I will try your suggested links as well - thank you.

1 Like
6

One odd thing I have noticed is when I load a POS file into version b33 waypoints show in the wrong place on RTKplot

In version 2.4.3 demo5 b26 the waypoint is in the correct expected place with the exactly the same files loaded. It seems every version of the RTKlib suite has it’s own errors.

2020-07-17 16_37_28-
2020-07-17 16_37_28-1366×729 116 KB

7

Hi @myozone,

Thanks for noticing this!

May I ask you to share your logs? You can send it on support@emlid.com, if it contains some sensitive information.

We should try to reproduce this behavior and fix it. I’ll keep you posted on the results.

9

Hi David,

Just want to let you know that we’ve reproduced these issues. We’re going to fix it in the next RTKLib versions.

10

This topic was automatically closed 100 days after the last reply. New replies are no longer allowed.