Problem with BNC RTNET Upload

[brack@…]

Dear BKG colleagues,

we are facing a problem with the RTNET upload with BNC versions 2.13.x. From the raw-output-file it seems that both RTNET and broadcast streams are correctly read, but no corrections are uploaded. From the bnc-log-file we get one of two errors for each RTNET block:

1) "no Epoch line found"
2) "no EOE found"

It seems that BNC splits the RTNET stream into blocks (between 1 and several tens of lines) and tries to decode each one of them separately instead of buffering from the Epoch line to the EOE entry, so either the Epoch line is contained, but no "EOE" (case 2) or the "EOE", but not the preceding Epoch line (case 1).

The same RTNET stream with BNC versions 2.12.x works fine.

I will also upload the raw and log output files.

Are you aware of such problems or do you have an idea what might be the issue here?

Thank you and best regards,
Andreas Brack

[brack@…]

BNC log file

[brack@…]

BNC raw output

[stuerze]

Dear Andreas Brack,

Thank you for this hint, your error analysis and the raw data example!

The RTNET decoding in BNC versions 2.12.x unfortunatelly had data gaps in a lot of other cases. But I will investigate your example in more detail and let you know as soon the problem is hopefully solved.

Best regards, Andrea

[stuerze]

Dear Andreas,

after a simplification of the RTNET stream decoding procedure it seems that I can read your data:

Epochs from raw file:

11:35:55.000
11:36:00.000
11:36:05.000
11:36:10.000
11:36:15.000
11:36:20.000
11:36:25.000
11:36:30.000
11:36:35.000

Logfile:

25-02-04 11:35:57 Broadcaster: Connect timeout for CLOCK@products.igs-ip.net:2101) Connection refused
25-02-04 11:35:57 RTCM3EPH-MGEX: Get data in RTCM 3.x format
25-02-04 11:35:57 RTCM3EPH-MGEX: UNHEALTHY EPH J04 LNAV: 2025 02 04 12 00 00
25-02-04 11:35:57 CLKBM: Get data in RTNet format
25-02-04 11:35:57 Broadcaster: Connect timeout for CLOCK@products.igs-ip.net:2101) Connection refused
25-02-04 11:35:58 RTCM3EPH-MGEX: OUTDATED EPH S48 SBAS: 2025 02 04 21 00 32
25-02-04 11:35:59 RTCM3EPH-MGEX: UNHEALTHY EPH J02 LNAV: 2025 02 04 12 00 00
25-02-04 11:36:00 RTCM3EPH-MGEX: UNHEALTHY EPH J03 LNAV: 2025 02 04 12 00 00
25-02-04 11:36:02 bncRtnetUploadCaster: decode 2025-02-04 11:35:55.000 CLOCK products.igs-ip.net:      2101 IGS20 ./BKG0MGXRTS${V3PROD}.SP3 ./BKG0MGXRTS${V3PROD}.CLK ./BKG0MGXRTS${V3PROD}.BIA
25-02-04 11:36:07 RTCM3EPH-MGEX: OUTDATED EPH E12 FNAV: 2025 01 22 08 40 00
25-02-04 11:36:07 RTCM3EPH-MGEX: OUTDATED EPH E12 INAV: 2025 01 22 08 40 00
25-02-04 11:36:07 bncRtnetUploadCaster: decode 2025-02-04 11:36:00.000 CLOCK products.igs-ip.net:      2101 IGS20 ./BKG0MGXRTS${V3PROD}.SP3 ./BKG0MGXRTS${V3PROD}.CLK ./BKG0MGXRTS${V3PROD}.BIA
25-02-04 11:36:08 RTCM3EPH-MGEX: OUTDATED EPH S34 SBAS: 2025 02 04 00 00 00
25-02-04 11:36:09 RTCM3EPH-MGEX: UNHEALTHY EPH R19 FDMA: 2025 02 04 11 45 18
25-02-04 11:36:12 bncRtnetUploadCaster: decode 2025-02-04 11:36:05.000 CLOCK products.igs-ip.net:      2101 IGS20 ./BKG0MGXRTS${V3PROD}.SP3 ./BKG0MGXRTS${V3PROD}.CLK ./BKG0MGXRTS${V3PROD}.BIA
25-02-04 11:36:13 RTCM3EPH-MGEX: UNHEALTHY EPH E14 FNAV: 2025 02 04 11 00 00
25-02-04 11:36:13 RTCM3EPH-MGEX: UNHEALTHY EPH E14 INAV: 2025 02 04 11 00 00
25-02-04 11:36:14 RTCM3EPH-MGEX: UNHEALTHY EPH C48 D1  : 2025 02 04 11 00 14
25-02-04 11:36:14 RTCM3EPH-MGEX: UNHEALTHY EPH E18 FNAV: 2025 02 04 11 20 00
25-02-04 11:36:15 RTCM3EPH-MGEX: UNHEALTHY EPH E18 INAV: 2025 02 04 11 20 00
25-02-04 11:36:16 RTCM3EPH-MGEX: OUTDATED EPH S48 SBAS: 2025 02 04 21 00 32
25-02-04 11:36:17 RTCM3EPH-MGEX: UNHEALTHY EPH R26 FDMA: 2025 02 04 11 45 18
25-02-04 11:36:17 RTCM3EPH-MGEX: OUTDATED EPH C56 D1  : 2025 02 05 07 00 14
25-02-04 11:36:17 bncRtnetUploadCaster: decode 2025-02-04 11:36:10.000 CLOCK products.igs-ip.net:      2101 IGS20 ./BKG0MGXRTS${V3PROD}.SP3 ./BKG0MGXRTS${V3PROD}.CLK ./BKG0MGXRTS${V3PROD}.BIA
25-02-04 11:36:18 RTCM3EPH-MGEX: OUTDATED EPH C57 D1  : 2024 06 25 20 00 14
25-02-04 11:36:19 RTCM3EPH-MGEX: OUTDATED EPH C58 D1  : 2025 02 05 05 00 14
25-02-04 11:36:22 bncRtnetUploadCaster: decode 2025-02-04 11:36:15.000 CLOCK products.igs-ip.net:      2101 IGS20 ./BKG0MGXRTS${V3PROD}.SP3 ./BKG0MGXRTS${V3PROD}.CLK ./BKG0MGXRTS${V3PROD}.BIA
25-02-04 11:36:27 bncRtnetUploadCaster: decode 2025-02-04 11:36:20.000 CLOCK products.igs-ip.net:      2101 IGS20 ./BKG0MGXRTS${V3PROD}.SP3 ./BKG0MGXRTS${V3PROD}.CLK ./BKG0MGXRTS${V3PROD}.BIA
25-02-04 11:36:29 RTCM3EPH-MGEX: OUTDATED EPH S34 SBAS: 2025 02 04 00 00 00
25-02-04 11:36:29 RTCM3EPH-MGEX: OUTDATED EPH E01 FNAV: 2023 04 30 00 40 00
25-02-04 11:36:29 RTCM3EPH-MGEX: OUTDATED EPH E01 INAV: 2023 04 30 00 40 00
25-02-04 11:36:32 bncRtnetUploadCaster: decode 2025-02-04 11:36:25.000 CLOCK products.igs-ip.net:      2101 IGS20 ./BKG0MGXRTS${V3PROD}.SP3 ./BKG0MGXRTS${V3PROD}.CLK ./BKG0MGXRTS${V3PROD}.BIA
25-02-04 11:36:33 RTCM3EPH-MGEX: OUTDATED EPH S48 SBAS: 2025 02 04 21 00 32
25-02-04 11:36:37 bncRtnetUploadCaster: decode 2025-02-04 11:36:30.000 CLOCK products.igs-ip.net:      2101 IGS20 ./BKG0MGXRTS${V3PROD}.SP3 ./BKG0MGXRTS${V3PROD}.CLK ./BKG0MGXRTS${V3PROD}.BIA
25-02-04 11:36:38 RTCM3EPH-MGEX: OUTDATED EPH C18 D1  : 2019 04 20 14 00 14
25-02-04 11:36:39 RTCM3EPH-MGEX: OUTDATED EPH E12 FNAV: 2025 01 22 08 40 00
25-02-04 11:36:39 RTCM3EPH-MGEX: OUTDATED EPH E12 INAV: 2025 01 22 08 40 00
25-02-04 11:36:42 RTCM3EPH-MGEX: OUTDATED EPH S34 SBAS: 2025 02 04 00 00 00
25-02-04 11:36:42 bncRtnetUploadCaster: decode 2025-02-04 11:36:35.000 CLOCK products.igs-ip.net:      2101 IGS20 ./BKG0MGXRTS${V3PROD}.SP3 ./BKG0MGXRTS${V3PROD}.CLK ./BKG0MGXRTS${V3PROD}.BIA

I will test it now with other data as well.

Best regards, Andrea

[brack@…]

Dear Andrea,

thank you very much for your quick help! Looking forward to a future BNC release that can read our data...

Best regards, Andreas