A version of RTKLIB optimized for low cost GNSS receivers, especially u-blox receivers. It is based on RTKLIB 2.4.3 and is kept reasonably closely synced to that branch. This software is provided “AS IS” without any warranties of any kind so please be careful, especially if using it in any kind of real-time application.
I try to get Observation from Ublox F9P with the best time tolerance possible for precise positioning.
To get that, i set up the Receiver with 20hz UBX-RAWX output, decimate to 1sec and truncate the timestamp with -TADJ=1.0 option.
With convbin, it's working well (ie: convbin -ti 1.0 -tt 0.025 -ro -TADJ=1.0 file20hz.ubx).
With str2str, it's not working (ie: str2str -in file://file20hz.ubx#ubx -out file://file1hz.rtcm3#rtcm3 -msg "1077(1),1087(1),1097(1),1107(1),1127(1)" -opt -TADJ=1.0).
In the output file, there is plenty of empty observation messages and one OK every seconds.
I suspect the -TADJ=1.0 option is done before the RTCM3 decimation...
Can you help me for my project?
Tested on Raspberry pi3 with raspbian10 and RTKLIB b34c.
I try to get Observation from Ublox F9P with the best time tolerance possible for precise positioning.
To get that, i set up the Receiver with 20hz UBX-RAWX output, decimate to 1sec and truncate the timestamp with -TADJ=1.0 option.
With convbin, it's working well (ie: convbin -ti 1.0 -tt 0.025 -ro -TADJ=1.0 file20hz.ubx).
With str2str, it's not working (ie: str2str -in file://file20hz.ubx#ubx -out file://file1hz.rtcm3#rtcm3 -msg "1077(1),1087(1),1097(1),1107(1),1127(1)" -opt -TADJ=1.0).
In the output file, there is plenty of empty observation messages and one OK every seconds.
I suspect the -TADJ=1.0 option is done before the RTCM3 decimation...
Can you help me for my project?
Tested on Raspberry pi3 with raspbian10 and RTKLIB b34c.