Custom Query (104 matches)

We're using bnc 2.12.2 to retrieve data from different casters (about ~250 different mountpoints) at a sample rate of 10 seconds. Every day at midnight we loss all the mountpoints data. It looks like there is some kind of problem with the time reference used by bnc in this case and therefore it discards all date with "Old epoch" messages (find attached full log).

In case it is useful for your, there seem to be two things also happening at the day change: configuration read (which is always done, even if the onTheFlyInterval is not set) and rinex files creation. Perhaps some of this tasks is blocking the others, which adds a delay bigger than the sample rate?

Thanks in advance, David Roma

I'm sorry, this is the first time for me reporting a BNC bug and I didn't found any procedure of how and where to do it. Please let me know if I'm reporting it at the wrong place or if you need any more information.

Recently our BNC (Bnc2.11.1-CentOS6-64bit-static) crashed with the following output message:

RTCM2_23::extract: P.nDataWords()>=1
RTCM2_23::extract: P.nDataWords()>=1
RTCM2_23::extract: P.nDataWords()>=1
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.

terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc

The bnc_update.log doesn't show any information related to the error.

Dear BKG staff, we are running BKG Ntripcaster v 2.0.21, and monitoring RTCM3 streaming latencies with BNC Client 2.10 (log latency set to every 5 minutes).

We probably found a bug (or something we could not explain) in one of the modules of the BKG Ntripcaster software.

The module src/source.c has a variable named READ_RETRY_DELAY

The value for this is set to 400. Leaving this value, we observe an unexpected high latencies on all of our data streams. If we change the variable to a lower value (we are currently using READ_RETRY_DELAY value of 50), latencies measured by BNC Client decrease systematically by about 0.5 seconds.

The figure attached shows an example for AUCK_RTCM streaming. Red values are the one with READ_RETRY_DELAY set as default (400), whereas green values has this value set to 50. Any comments/suggestions from you would be really appreciated!

Thanks,

Elisabetta D'Anastasio GNS Science - Te Pu Ao