-BNC has been written under GNU General Public License (GPL). Binaries for BNC are available for Windows, Linux, and Solaris systems. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.0.1 are installed. +BNC has been written under GNU General Public License (GPL). Binaries for BNC are available for Windows, Linux, and Solaris systems. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.2.3 are installed.
| History | ||
| Dec 1, 2006 | Version 1.0b | Binaries of first beta version published. |
| Jan 20, 2007 | Version 1.1b | [Add] Observables C2, S1, and S2 [Add] Virtual reference station access [Bug] RTCM2 decoder time tag fixed [Mod] Small letters for public RINEX skeleton files [Add] Online help through Shift+F1 |
| Feb 1, 2007 | Version 1.2b | [Bug] Output only through IP port [Bug] Method 'reconnecting' now thread-save + |
| Dec 2006 | Version 1.0b | Binaries of first beta version published. |
| Jan 2007 | Version 1.1b | [Add] Observables C2, S1, and S2 [Add] Virtual reference station access [Bug] RTCM2 decoder time tag fixed [Mod] Small letters for public RINEX skeleton files [Add] Online help through Shift+F1 |
| Apr 2007 | Version 1.2b | [Bug] Output only through IP port [Bug] Method 'reconnecting' now thread-save [Add] ZERO decoder added [Mod] Download public RINEX skeletons once per day [Mod] Upgrade to Qt Version 4.2.3 [Mod] Replace 'system' call for RINEX script by 'QProcess' |
BNC decodes and converts GNSS data streams carrying code and phase data coming in
+
Warning
@@ -61,10 +63,11 @@
B - 4.3. Port for Binary Output
B - 5. RINEX
- B - 5.1. RINEX Directory
- B - 5.2. RINEX Script
- B - 5.3. RINEX File Interval
- B - 5.4. RINEX Sampling
- B - 5.5. RINEX Skeleton Extension
- B - 5.6. Append Files
+ B - 5.1. RINEX File Names
+ B - 5.2. RINEX Directory
+ B - 5.3. RINEX Script
+ B - 5.4. RINEX File Interval
+ B - 5.5. RINEX Sampling
+ B - 5.6. RINEX Skeleton Extension
+ B - 5.7. Append Files
B - 6. Mountpoints
B - 6.1. Add Mountpoints
@@ -195,5 +198,9 @@
-Observations are converted to RINEX Version 2.11. RINEX file names are derived by BNC from the first 4 characters of the corresponding mountpoint (4Char Station ID) while omitting the residual part of the mountpoint string. Thus, retrieving data from mountpoints FRANKFURT and WETTZELL leads to hourly RINEX observation files named
+Observations will be converted to RINEX Version 2.11 if they come in either RTCM Version 2.x, RTCM Version 3, or RTIGS format. BNC's RINEX observation files generally contain C1, C2, P1, P2, L1, L2, S1, and S2 observations. In case an observation is unavailable, its value is set to zero '0.000'. Note that even if a RINEX file does not contain GLONASS data, the 'RINEX TYPE' field in the RINEX file header may be set to 'M (MIXED)'. + + ++RINEX file names are derived by BNC from the first 4 characters of the corresponding mountpoint (4Char Station ID) while omitting the residual part of the mountpoint string. Thus, retrieving data from mountpoints FRANKFURT and WETTZELL leads to hourly RINEX observation files named
FRAN{ddd}{h}.{yy}O
@@ -223,14 +230,11 @@
where 'mm' is the starting minute within the hour.
-BNC's RINEX observation files generally contain C1, C2, P1, P2, L1, L2, S1, and S2 observations. In case an observation is unavailable, its value is set to zero '0.000'. Note that even if a RINEX file does not contain GLONASS data, the 'RINEX TYPE' field in the RINEX file header may be set to 'M (MIXED)'. -
- -B - 5.1 RINEX Directory - optional
B - 5.2 RINEX Directory - optional
Enter a path for saving the RINEX files in a directory. If this directory does not exist, BNC will not create RINEX files. Default value for 'RINEX directory' is an empty option field, meaning that streams are not converted to RINEX.
-B - 5.2 RINEX Script - optional
B - 5.3 RINEX Script - optional
Whenever a RINEX file is saved, you may like to compress, copy or upload it immediately via FTP. For that you enter the full path of a script or batch file which is then called to carry out these operations. The RINEX file path will be passed to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux systems). @@ -240,17 +244,17 @@
-B - 5.3 RINEX File Interval - mandatory if 'RINEX directory' set
B - 5.4 RINEX File Interval - mandatory if 'RINEX directory' set
Select the interval for the RINEX file generation. Default for 'RINEX file interval' is 15 minutes.
-B - 5.4 RINEX Sampling - mandatory if 'RINEX directory' set
B - 5.5 RINEX Sampling - mandatory if 'RINEX directory' set
Select the RINEX sample interval in seconds. Zero '0' stands for converting all incoming epochs to RINEX. Default for RINEX 'Sampling' is '0'.
-B - 5.5 RINEX Skeleton Extension - optional
-Whenever BNC generates a new RINEX file, it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. An HTTP link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See http://www.epncb.oma.be:80/stations/log/skl/brus.skl for an example for a public RINEX header skeleton file concerning the EPN station Brussels. +
B - 5.6 RINEX Skeleton Extension - optional
+Whenever BNC starts generating RINEX files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. An HTTP link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See http://www.epncb.oma.be:80/stations/log/skl/brus.skl for an example for a public RINEX header skeleton file concerning the EPN station Brussels.
@@ -301,5 +305,5 @@
-
+When starting BNC, new RINEX files are created by default. Probably existing files will be overwritten. However, it may be desirable to append observations to already existing RINEX files following a restart of BNC after an intentional 'Stop', a system crash or a crash of BNC. Hit 'Append files' to continue with already existing files and thus save what has been recorded so far. Note that option 'Append files' also concerns the 'ASCII output file' and the 'Log' file. @@ -339,5 +343,5 @@
-Hit button 'Get Table' to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM 2.x, RTCM 3, or RTIGS formats. RTCM 2.x streams must contain message types 18 and 19 while RTCM 3 streams must contain GPS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Select your streams line by line, use +Shift and +Ctrl when necessary. +Hit button 'Get Table' to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM 2.x, RTCM 3, or RTIGS format. RTCM 2.x streams must contain message types 18 and 19 while RTCM 3 streams must contain GPS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Select your streams line by line, use +Shift and +Ctrl when necessary.
@@ -355,5 +359,8 @@