rtkbase IGN PPP compute failure

Describe the bug A rinex file sent to the IGN PPP online service fails because there is more than 24H observables. A workaround is to delete 2 or 3 of the last observables to stay below 24H duration.

Apr 08 '23 07:04 Stefal

To use -te parameter with convbin, full date is needed : -te 2023/04/10 07:00:00 I tried -span 1 to limit time span but it doesn't work.

edit: -span works only with -ts

Apr 10 '23 13:04 Stefal

Dear Stefal,

I've elminated observables to stay below 24H, but still get :

2023-05-06-LL60-LL61_Ynys-Mon_ign.23o non calculé.

What am I doing wrong?

Thanks,

Dafydd

My setup is as follows:

Gnss receiver: Ublox_NEO-M8T - Board: Raspberry Pi Zero W Rev 1.1 Os: Raspbian 10 (Buster) CPU Temp: 44.4 C° - (highest record: 46.0C°) Uptime: 7d 21h 49mn 23s Storage: 11.07GB available of 15.38GB - (24.8 % used)

May 09 '23 14:05 nubotix

I forgot to mention I'm using RTKBase v2.4.1

CSRS-PPP SPARK just succesfully processed the truncated file. (It rejected my previous untruncated attempts)

Thanks for your really useful software!

Dafydd

May 09 '23 14:05 nubotix

I just wanted to warn you that a lot of PPP tool works only with L1+L2 data. The M8T is L1 only.

May 10 '23 10:05 Stefal

One way to check if the rinex timespan is too long is to check these two lines : TIME OF FIRST OBS and TIME OF LAST OBS

then use a bash command like cut/awk/split/csplit

Nov 12 '23 19:11 Stefal

I've set file overlap default value to 0s https://github.com/Stefal/rtkbase/commit/0dfed9b8624e8007e0fba0b52a01396b84db0245

Dec 29 '23 13:12 Stefal

I still see the issue from time to time. One example today :

  2025    10    15    23    59   30.0000000     GPS         TIME OF FIRST OBS   
  2025    10    17    00    00   00.0000000     GPS         TIME OF LAST OBS

(RTKBase 2.6.3)

Oct 18 '25 11:10 Stefal