Trajectory Points extracted from LS doesn't synchronize to integer second

[RTKSurveyor]

Hi Everyone,

I got a JAVAD triumph LS from my boss. I tried the trajectory survery with Network RTK function. LS fixed good in most case. When I tried to export points to csv/txt file. I am confused why time tag shown in txt file was not syncronize to integer second, it makes me hard to compare with the other RTK device. Like the others, they all output trajectory at integer UTC second.

And it's quite confusing that millisecond will change from 0.5 -> 0.2, as can be seen below. I converted .jps raw GNSS measurement to rinex, every epoch time is integer second, but how can your RTK solution changed to a float value?

 

[Joe Paulin]

My guess is that it has to do with BEAST mode settings as those are all at 0.2 or 0.5 of a second, which would be 5HZ and 2HZ respectively. If you were to set it to 1 HZ or disable the BEAST mode, see if that fixes your issue.

 

[Michael Stazhkov]

When I tried to export points to csv/txt file. I am confused why time tag shown in txt file was not syncronize to integer second, it makes me hard to compare with the other RTK device. Like the others, they all output trajectory at integer UTC second.
And it's quite confusing that millisecond will change from 0.5 -> 0.2, as can be seen below. I converted .jps raw GNSS measurement to rinex, every epoch time is integer second, but how can your RTK solution changed to a float value?

Hi, could you attach the JPS file to the forum?

 

[Michael Stazhkov]

I am confused why time tag shown in txt file was not syncronize to integer second

Actually it seems you have selected RTK rate 0.2 sec, so RTK produces a solution each 200 ms.

And it's quite confusing that millisecond will change from 0.5 -> 0.2, as can be seen below.

By default standalone positions have 0.1 sec rate, so its time has 100 ms step.

 

[RTKSurveyor]

Hi, could you attach the JPS file to the forum?

Hi Michael,

Since the file is 20 MB, it's not allowed to attach it directly. I put it into my DropBox, here is the share link, Please take a look
https://www.dropbox.com/s/vx4wu2gkwykvepe/Point24_093429.jps?dl=0

 

[RTKSurveyor]

Hi, could you attach the JPS file to the forum?

I also extract the project folder in the LS. It has a sqlite database, I know you can get what you want from this file, also shared here.
https://www.dropbox.com/s/k5k8gp2jxlwaxg1/2017 DSRC2-171015.zip?dl=0

 

[Michael Stazhkov]

Your file is OK. Something wrong with time tags recorded in database. We will investigate the issue. Thank you.

 

[Michael Stazhkov]

I see that you work in RTK extrapolation mode. In this case RTK can produce solutions with 10 Hz (aligned to 100 ms). For recording to database we order solutions with 10 Hz. The raw GNSS file was recorded with 1 Hz that it why all solutions in the file are aligned to 1 sec.
So everything is OK in your data.

 

[Michael Stazhkov]

For future in case when in trajectory settings only "Elapsed Time" filter is selected we can improve filter of incoming epochs for trajectory recording and use only epochs with solution time aligned to the selected period.

 

[Matt Johnson]

Michael if he turns off extrapolation mode and sets the RTK Rate to 1 sec as shown data should be logged at the integer second as desired correct?

 

[Michael Stazhkov]

Michael if he turns off extrapolation mode and sets the RTK Rate to 1 sec as shown data should be logged at the integer second as desired correct?

View attachment 6826

It is enough to set RTK rate to 1 sec.

 

[RTKSurveyor]

It is enough to set RTK rate to 1 sec.

I think the problem still exist. Even if I reset the configuration to factory default. I get the screen shot of those configuration.

 

[Michael Stazhkov]

Thank you. The bug with time tags in trajectory will be fixed in the next major release 2.1.0.x