cancel
Showing results for 
Search instead for 
Did you mean: 

Which PPS $PSTMPPSDATA and $PSTMUTC messages related with? With previous or with next?

RSeny
Associate II

2019-05-24 10:01:31.578471543 | processPps()

2019-05-24 10:01:31.711095091 | $PSTMPPSDATA,1,1,1,0,0,0,0.500000,0,713,248,0,0,0,0,0,36,3,11,18,4,0,1.301e-08,65473955.16,25999998.74*16

2019-05-24 10:01:31.739373411 | $PSTMUTC,100135.000,24052019,1242727295,18,2*57

2019-05-24 10:01:31.739501850 | unixtime 1558692095 dUnixtime 0.000000013010 leapSec 18 leapSecValid 2

2019-05-24 10:01:32.578423766 | processPps()

Here previous PPS came at 10:01:31.578471543 local time

next at 2019-05-24 10:01:32.578423766

My understanding that quantization error from $PSTMPPSDATA 1.301e-08 should be added to next PPS signal to have precise time of the PPS. Am I right?

Following this logic $PSTMUTC should be the same next PPS second. Is this true?

Thank you in advance!

Ruslan

4 REPLIES 4
Francesco Virlinzi
ST Employee

Hi

It seems you are using the Teseo-SDK.

The GNSS Community is targetting GNSS Binary Image solution.

Could you open a discussion with your relevant FAE?

Thanks

Regards

Francesco

Hi, Francesco!

I'm not using Teseo-SDK. I'm using UART to communicate with the module and digital signal 1PPS.

So I have incoming PPS number N

then group of NMEA messages by UART

then next PPS number N+1

as you can see in log in my first message with times attached.

Seconds switched on PPS coming. My question is

$PSTMUTC give number of a second starting from next PPS? Or this is the number of the current second started from previous to the $PSTMUTC message PPS signal?

This is a question about how binary image generates messages and PPS signals.

Best regards

Ruslan

Ciao

The UTC time information reported in the  $PSTMUTC NMEA message are used to evaluates the Next PPS signal.

The $PSTMPPSDATA reports against which UTC time the PPS has been evaluated/generated.

Hope this helps

Regards

Francesco

Thank you, Francesco! This is useful information for me.

Can you also take a look at previous branch with attenuator tuning question (How to increase attenuation value in Teseo III RF front-end?)?

Values you suggested:

CDB-140 @ 0x0A

CDB-141 @ 40

if it helps, you can also tests different vales for CDB-141 (140 is mandatory @ 0x0A)

Does not work. What we can do to troubleshoot?

Best regards,

Ruslan