TESEO-VIC3D PSTMPPSDATA ref_sec issue
- July 13, 2026
- 0 replies
- 24 views
Hi,
I’m using TESEO-VIC3D for PPS generation for time synchronization and OCXO frequency correction. I wanted to use PSTMPPSDATA NMEA messages in order to read quantization_error parameter and apply it in my program to eliminate the quantization error of PPS signal. Mostly it works well, but I ran into couple of issues:
- There is a ref_sec parameter in the PSTMPPSDATA message that should refer to a specific second for which the message corresponds. For some seconds, this message is missing, e.g.:
2026-07-11 17:43:09.564 $PSTMPPSDATA,1,1,1,0,0,0,0.500000,0,633,420,420,633,0,0,0,0,0,11,3,5,18,4,0,0,6.622e-09,65473709.68,48000018.67,4*24
2026-07-11 17:43:09.567 $PSTMTRAIMSTATUS,1,0,15,7,5,2,11*54
2026-07-11 17:43:09.573 $PSTMTRAIMUSED,1,5,7,21,11,16,9*7C
2026-07-11 17:43:09.576 $PSTMTRAIMRES,1,5,-3,-9,6,-3,10*16
2026-07-11 17:43:09.580 $PSTMTRAIMREMOVED,1,2,30,4*2F
2026-07-11 17:43:10.616 $PSTMTRAIMSTATUS,1,0,15,8,5,2,12*58
2026-07-11 17:43:10.620 $PSTMTRAIMUSED,1,5,7,21,11,16,9*7C
2026-07-11 17:43:10.623 $PSTMTRAIMRES,1,5,-4,-2,5,-5,6*28
2026-07-11 17:43:10.626 $PSTMTRAIMREMOVED,1,2,30,4*2F
2026-07-11 17:43:11.575 $PSTMPPSDATA,1,1,1,0,0,0,0.500000,0,633,420,420,633,0,0,0,0,0,13,3,5,18,4,0,0,1.378e-08,65473709.69,48000018.68,4*24
2026-07-11 17:43:11.578 $PSTMTRAIMSTATUS,1,0,15,10,5,2,13*60
2026-07-11 17:43:11.581 $PSTMTRAIMUSED,1,5,7,21,11,16,9*7C
2026-07-11 17:43:11.584 $PSTMTRAIMRES,1,5,-7,0,4,-3,5*00
2026-07-11 17:43:11.587 $PSTMTRAIMREMOVED,1,2,30,4*2F
As you can see, this message is omitted for ref_sec=12 (while PSTMTRAIMSTATUS is sent for the same ref_sec)
- ref_sec should only be values 0-59, but I observed a jump from ref_sec=41 to ref_sec=239, which shouldn’t be a correct value. It seems like an error of processing signed/unsigned 8bit values in FW. Moreover, when ref_sec finally reaches 255, the next two PSTMPPSDATA messages have both ref_sec=0 (even though they are not sent at the same time), see the attached log (ref_sec_jump.txt):
- What is a realiable way to connect ref_sec to a specific PPS pulse? Documentation is not very specific about that.
- pps_valid and synch_valid parameters in PSTMPPSDATA - What exactly do they mean? Documentation does not specify that.
Version of FW in my TESEO module (response to PSTMGETSWVER,255):
$PSTMVER,GNSSLIB_8.4.19.27.11_ARM*66
$GPTXT,DEFAULT VIC CONFIGURATION*24
$PSTMVER,OS20LIB_4.4.0_ARM*40
$PSTMVER,GPSAPP_2.14.0.11_VIC3DA_ARM*30
$PSTMVER,BINIMG_4.6.18.11_VIC3DA_ARM*3F
$PSTMVER,SWCFG_8406532d*34
$PSTMVER,STAGPSLIB_6.0.1_ARM*5B
$PSTMVER,DRLIB_2.14.1_ARM*7E
$PSTMVER,STA8090_922bc043*60
$GPTXT,(C)2000-2018 ST Microelectronics*29
$GPTXT,DEFAULT VIC CONFIGURATION*24
I tried to search for this in the forum, but I haven’t found anything about this. I would appreciate your help with this issue.
Best regards,
Filip
