Custom Query (131 matches)

Using BKG Ntrip Client Version 2.12.6 we get no Glonass with RTCM_3.2 streamed basestation data. If we include a RTCM_3 stream we get Glonass with both. If we just have a RTCM_3 stream we get Glonass. With version 2.8 it worked but had caps and dropouts.

Any ideas?

Hello,

We are running the BNC Client to collect latency metrics and create 1s Rinex2 files from our streaming stations across New Zealand. We manage about 50 streaming sites with one instance of the BNC client.

We have upgraded to the latest BNC version (2.12.6) last week on 2018/05/16.

BNC Client stopped logging metrics at the beginning of the midnight of UTC day 2018- 05-20. The latency records restarted normally after a restart of the BNC Client.

I have enclosed the configuration file we use with the BNC Client (only username and password are changed in there) and the BNC log file for the day that had the latency metrics dropping off.

We run BNC Client on: Linux 3.10.0-862.2.3.el7.x86_64 x86_64 x86_64 x86_64 GNU/Linux

with the following command:

/usr/local/bin/bnc -nw --conf /work/bnc/conf/BNC.ini

I know that our colleagues at Geoscience Australia are having the same problem, and they experienced the same behavior at the beginning of each UTC week.

We were previously using v 2.12.3 of the software with no issues.

Thanks a lot for your attention,

Kind regards,

Elisabetta

--- Elisabetta D’Anastasio Geodetic Processing Specialist Geohazards Monitoring Department, GNS Science - Te Pῡ Ao

If scanRTCM enabled:

• check sourcetable format
• check RTCM version based on message types
• check receiver (1033)
• write message types summary in sourcetable format
• check nav-systems based on message types
• check stream bitrate
• warning if ADV NULLANTENNA