Fixed false RS2

Reach RS2 / RS2+ RTK / PPK configuration
1

In survey in RTK mode in bad situations, with obstruction by Vegetation, trees … I realized that the RS2 is easily. However, staying in the spot for a while, the position varies considerably. I monitor the point, and it seems that the variation always follows the same direction. I observed several fixed points, at the same point, with coordinates varying considerably. Always with a good number of satellites, good pdop, and good RMS. What can I do to ensure that the Fixed is really Fixed and ensures adequate positional accuracy?

Att
Mauricio from Brazil

1 Like
3

Hi Mauricio,

Could you clarify which firmware version is installed on your device?

Also, please, share the following data so that we can analyze them and figure out what might go wrong:

  • raw data log
  • position log
  • base correction log
1 Like
4

Hi Tatiana,

How are you?

The firmware version of my RS2 is: v2.22.3;

I only have the raw data log, I have no position record or base correction, I was not instructed to record this;

Is this file enough?
Or I can register all possible files in the next surveys;

5

Hi Mauricio,

I’m fine, hope you’re well too :slightly_smiling_face:

It’d be better if you have a chance to record all the data during an additional test. Raw data is fine for understanding the conditions of the survey and satellite signal quality, but I’d like to check the RTK solution, too.

6

hello tatiana

I am also well!!!

OK,
We will record the data during a survey to be able to send you later for analysis.

Thank you for now!

1 Like
7

Hello

follows survey done over the weekend

https://we.tl/t-zuLqHo4bah

8

Hi @mauricioranzan,

I downloaded the data, will check.

Thanks for the test!

9

15 posts were split to a new topic: Testing Reach RS2 on v2.22.4 firmware version

10

Hi @mauricioranzan,

I’ve looked into the data, and it seems you haven’t attached the base correction log. May I ask you to send it to me, too?

Also, the RTK position file is the 5-hours log of a single solution. Could you clarify whether Reach was getting corrections during the test?

1 Like
11

Tatiana,

But the only files recorded on my base are these.

UBX, LLH, RINEX,

has no option to record something else

12

Hi @mauricioranzan,

Can you share the files recorded on the rover, too?

13

good morning tatiana

All right?

Follows Rover LLH

solution_202004231411_LLH.zip (85.4 KB)

14

Hi @mauricioranzan,

Thanks! The UBX raw data file would be of much help, too. Could you share it as well?

15

raw_202003101242_UBX.zip (1.2 MB)

16

Hi @mauricioranzan,

Thank you! I checked the data and noticed that they all had been recorded during different surveys. The base raw data log (UBX) was collected on May 2, the rover’s raw data (UBX) is dated March 10 while the position rover’s data (LLH) was recorded on April 23.

Unfortunately, it’s quite hard to say anything certain regarding the issue you experienced without the full data set logged during one survey. Is there any chance you can check all the files you have once again and provide me with the following files recorded simultaneously?

  • UBX file from the base
  • UBX file from the rover
  • LLH file from the rover
  • RTCM3 file from the rover

I need rover’s LLH file to evaluate the RTK solution quality and scattering; base and rover UBX files to check how many good satellites with high SNR were tracked at the same time by both these devices; RTCM3 file to compare that the rover got all the data sent by the base unit.

Without this info, I’m afraid, it’s quite hard to conclude anything.

1 Like
17

Good night Tatiana!

I thought I could send any file for analysis, since the problem is not one-off, but recurring!

18

Hi @mauricioranzan,

I need a full dataset to say anything certain. Otherwise, if I have files from different surveys, I neither can see the whole picture of what’s going wrong nor provide the analysis of the issue.

That’s why it’d be nice if you can share all the data I asked above recorded during one survey.

Thank you!

1 Like
19

Hello Tatiana

All right?

Following are files from a survey of the same day for your analysis!

I know there are many factors that influence accuracy, ambiguity resolution, multi-routing …
But there must be some configuration or procedure for me to eliminate or reduce the incidence of false fixes.

I wish that when it is fixed, it is really fixed.

Especially because I am not getting favorable and reliable results with Post Processing of RS2 data, so I want to be able to trust the RTK solution.

https://we.tl/t-WVlbTMuNJK

20

Hi @mauricioranzan,

Sorry it took so long to get back to you!

We accomplished a set of tests trying to reproduce the issue you’d encountered, and, in the result, released a new dev firmware update v2.23.8. Would it be possible for you to test it? We have improved the RTK solution calculation, especially in somewhat challenging conditions. We believe this should help you achieve better results in RTK.

Please note that dev releases provide early access to the new features and are not intended for the real-filed use.

1 Like
22

@tatiana.andreeva
Would this also be reflected in RTKlib ?