Custom Query (104 matches)

Hello,

I am trying to install v2.12 of BNC and am getting the following error after performing qmake bnc.pro then make:

bncsslconfig.h:8:29: error: invalid use of incomplete type ‘class QSslConfiguration’
 class bncSslConfig : public QSslConfiguration {
                             ^
In file included from /usr/local/Trolltech/Qt-4.8.5/include/QtNetwork/qabstractnetworkcache.h:48:0,
                 from /usr/local/Trolltech/Qt-4.8.5/include/QtNetwork/QtNetwork:7,
                 from bncgetthread.h:29,
                 from bncwindow.h:32,
                 from bncwindow.cpp:64:
/usr/local/Trolltech/Qt-4.8.5/include/QtNetwork/qnetworkrequest.h:56:7: note: forward declaration of ‘class QSslConfiguration’
 class QSslConfiguration;
       ^
Makefile:940: recipe for target '.obj/release/bncwindow.o' failed
make[1]: *** [.obj/release/bncwindow.o] Error 1
make[1]: Leaving directory '/home/pg_user/Desktop/bnc-2.12.2-ubuntu14-64bit-shared/BNC/BNC/src'
Makefile:150: recipe for target 'sub-src-make_default-ordered' failed
make: *** [sub-src-make_default-ordered] Error 2

I am following the directions given in the BNC Help PDF on page 21 (Linux Systems), using Qt v4.8.5 on Ubuntu 16.04 LTS. Please let me know what I need to do to install and/or use this application on my platform.

Hello! I am trying to get RTCM (3v) format from septentrio receiver. I get the error message (block 1092 contain partial data! Ignored!). The block that show the error are 1091,1092,1071,1072,1081 and 1082. Could you help about how to resolve this error. Thanks you in advance. Note: I hope use correctly this tool.

Hello, We have systematic delays when 2 different messages are transmitted by the NTRIP Caster at the same time. For example, for a data stream containing the following messages : 1004 (1Hz), 1012 (1Hz), 1006 (0.1 Hz), 1008 (0.1 Hz) and 1033 (0.1 Hz), every 10 seconds, the delay increases from 1 to 2 seconds and stay at 2 seconds 1 second more. When the caster send all these 5 messages at the same time, the delay increases. Is there any fine tuning to do to solve this non expected behavior ? Thanks a lot. Benoît Gobin Manager of SATINFO - French GNSS Network