+BNC allows to concatenate RINEX files and edit their contents. Observation and navigation files can be handled. BNC can also carry out a quality check of the contents of RINEX files. This functionality in BNC stands for +
Select an action. Options are 'Edit/Concatenate' and 'Analyze'. +
3.6.2 Set Edit Options - mandatory if 'Edit/Concatenate' is set
Once action 'Edit/Concationate' is selected, you have to specify editing options. BNC lets you specify the RINEX version, sampling rate, begin and end of file and marker, antenna or receiver details. +
+ +3.6.3 Input Files - mandatory if 'Action' is set
+Specify full path to input RINEX observation file(s), and
+specify full path to input RINEX navigation file(s).
+
3.6.4 Output Files - mandatory if 'Action' is set
+Mandatory if 'Edit/Concatenate' selected:
+Specify full path to output RINEX observation file(s), and
+specify full path to output RINEX navigation file(s).
+
+Mandatory if 'Analyze' selected:
+Specify logfile(s) to output analysis results.
+
Differential GNSS and RTK operation using RTCM streams is currently based on corrections and/or raw measurements from single or multiple reference stations. This approach to differential positioning is using 'observation space' information. The representation with the RTCM standard can be called 'ObservationSpace Representation' (OSR). @@ -726,15 +766,15 @@ -
3.6.1 Directory, ASCII - optional
3.7.1 Directory, ASCII - optional
Specify a directory for saving Broadcast Corrections in files. If the specified directory does not exist, BNC will not create Broadcast Correction files. Default value for Broadcast Corrections 'Directory' is an empty option field, meaning that no Broadcast Correction files will be created.
-3.6.2 Interval - mandatory if 'Directory, ASCII' is set
3.7.2 Interval - mandatory if 'Directory, ASCII' is set
Select the length of the Broadcast Correction files. The default value is 1 day.
- +BNC can output epoch by epoch synchronized Broadcast Corrections in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Specify an IP port number to activate this function. The default is an empty option field, meaning that no Broadcast Correction output via IP port is generated. @@ -781,5 +821,5 @@
-3.6.4 Wait for Full Epoch - mandatory if 'Port' is set
3.7.4 Wait for Full Epoch - mandatory if 'Port' is set
When feeding a real-time GNSS network engine waiting epoch by epoch for synchronized Broadcast Corrections, BNC drops (only concerning IP port output) whatever is received later than 'Wait for full epoch' seconds. A value of 2 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming Broadcast Corrections stream and the delay acceptable by your application. A message such as "COCK1: Correction overaged by 5 sec" shows up in BNC's logfile if 'Wait for full epoch' is exceeded. @@ -789,5 +829,5 @@
- +BNC can generate synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed a real-time GNSS network engine. Observations can be streamed out through an IP port and/or saved in a local file. The output is always in plain ASCII format and comprises the following parameters: @@ -847,10 +887,10 @@
Figure: Synchronized BNC output via IP port to feed a GNSS real-time engine.
- +BNC can produce synchronized observations in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Synchronized means that BNC collects all data for any specific epoch which become available within a certain number of latency seconds (see 'Wait for Full Epoch' option). It then - epoch by epoch - outputs whatever has been received. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary synchronized output is generated.
-3.7.2 Wait for Full Epoch - mandatory if 'Port' is set
3.8.2 Wait for Full Epoch - mandatory if 'Port' is set
When feeding a real-time GNSS network engine waiting for synchronized input epoch by epoch, BNC drops whatever is received later than 'Wait for full epoch' seconds. A value of 3 to 5 seconds could be an appropriate choice for that, depending on the latency of the incoming streams and the delay acceptable for your real-time GNSS product. Default value for 'Wait for full epoch' is 5 seconds. @@ -860,10 +900,10 @@
-3.7.3 Sampling - mandatory if 'File' or 'Port' is set
3.8.3 Sampling - mandatory if 'File' or 'Port' is set
Select the synchronized observation output sampling interval in seconds. A value of zero '0' tells BNC to send/store all received epochs. This is the default value.
- +Specifies the full path to a 'File' where synchronized observations are saved in plain ASCII format. The default value is an empty option field, meaning that no ASCII output file is created. @@ -873,10 +913,10 @@
-3.7.5 Port (unsynchronized) - optional
3.8.5 Port (unsynchronized) - optional
BNC can produce unsynchronized observations from all configured streams in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Unsynchronized means that BNC immediately forwards any received observation to the port. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary unsynchronized output is generated.
-
+You may use BNC to feed a serial connected device like an GNSS receiver. For that one of the incoming streams can be forwarded to a serial port. The following figure shows the screenshot of an example situation where BNC pulls a VRS stream from an NTRIP broadcaster to feed a serial connected rover. @@ -885,5 +925,5 @@
Figure: BNC pulling a VRS stream to feed a serial connected rover.
- +Enter a 'Mountpoint' to forward its corresponding stream to a serial connected GNSS receiver. @@ -893,5 +933,5 @@
-3.8.2 Port Name - mandatory if 'Mountpoint' is set
3.9.2 Port Name - mandatory if 'Mountpoint' is set
Enter the serial 'Port name' selected on your host for communication with the serial connected receiver. Valid port names are @@ -910,30 +950,30 @@
-3.8.3 Baud Rate - mandatory if 'Mountpoint' is set
3.9.3 Baud Rate - mandatory if 'Mountpoint' is set
Select a 'Baud rate' for the serial output link. Note that using a high baud rate is recommended.
-3.8.4 Flow Control - mandatory if 'Mountpoint' is set
3.9.4 Flow Control - mandatory if 'Mountpoint' is set
Select a 'Flow control' for the serial output link. Note that your selection must equal the flow control configured to the serial connected device. Select 'OFF' if you don't know better.
-3.8.5 Parity - mandatory if 'Mountpoint' is set
3.9.5 Parity - mandatory if 'Mountpoint' is set
Select the 'Parity' for the serial output link. Note that parity is often set to 'NONE'.
-3.8.6 Data Bits - mandatory if 'Mountpoint' is set
3.9.6 Data Bits - mandatory if 'Mountpoint' is set
Select the number of 'Data bits' for the serial output link. Note that often '8' data bits are used.
-3.8.7 Stop Bits - mandatory if 'Mountpoint' is set
3.9.7 Stop Bits - mandatory if 'Mountpoint' is set
Select the number of 'Stop bits' for the serial output link. Note that often '1' stop bit is used.
-3.8.8 NMEA - mandatory for VRS streams
3.9.8 NMEA - mandatory for VRS streams
Select 'Auto' to automatically forward all NMEA-GGA messages coming from your serial connected GNSS receiver to the NTRIP broadcaster and/or save them in a file. @@ -946,8 +986,8 @@
-3.8.9 File - optional if 'Auto' NMEA is set
3.9.9 File - optional if 'Auto' NMEA is set
Specify the full path to a file where NMEA messages coming from your serial connected receiver are saved.
-3.8.10 Height - mandatory if 'Manual' NMEA is set
3.9.10 Height - mandatory if 'Manual' NMEA is set
Specify an approximate 'Height' above mean sea level in meter for your VRS to simulate an initial NMEA-GGA message. Latitude and longitude for that (editable) are taken from the broadcaster's source-table. @@ -957,5 +997,5 @@
- +@@ -972,10 +1012,10 @@
-3.9.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold', and 'Script' is set
BNC can collect all returns (success or failure) coming from a decoder within a certain short time span to then decide whether a stream has an outage or its content is corrupted. This procedure needs a rough a priory estimate of the expected observation rate of the incoming streams.
An empty option field (default) means that you don't want an explicit information from BNC about stream outages and incoming streams that cannot be decoded.
-3.9.2 Failure Threshold - optional
3.10.2 Failure Threshold - optional
Event 'Begin_Failure' will be reported if no data is received continuously for longer than the 'Failure threshold' time. Similarly, event 'Begin_Corrupted' will be reported when corrupted data is detected by the decoder continuously for longer than this 'Failure threshold' time. The default value is set to 15 minutes and is recommended so not to innundate user with too many event reports. @@ -985,5 +1025,5 @@
-3.9.3 Recovery Threshold - optional
3.10.3 Recovery Threshold - optional
Once a 'Begin_Failure' or 'Begin_Corrupted' event has been reported, BNC will check for when the stream again becomes available or uncorrupted. Event 'End_Failure' or 'End_Corrupted' will be reported as soon as valid observations are again detected continuously throughout the 'Recovery threshold' time span. The default value is set to 5 minutes and is recommended so not to innundate users with too many event reports. @@ -993,5 +1033,5 @@
- +As mentioned previously, BNC can trigger a shell script or a batch file to be executed when one of the events described are reported. This script can be used to email an advisory note to network operator or stream providers. To enable this feature, specify the full path to the script or batch file in the 'Script' field. The affected stream's mountpoint and type of event reported ('Begin_Outage', 'End_Outage', 'Begin_Corrupted' or 'End_Corrupted') will then be passed on to the script as command line parameters (%1 and %2 on Windows systems or $1 and $2 on Unix/Linux/Mac systems) together with date and time information. @@ -1022,5 +1062,5 @@
- +This section describes several miscellaneous options which can be applied for a single stream (mountpoint) or for all configured streams. @@ -1034,10 +1074,10 @@ -
+Specify a mountpoint to apply one or several of the 'Miscellaneous' options to the corresponding stream. Enter 'ALL' if you want to apply these options to all configured streams. An empty option field (default) means that you don't want BNC to apply any of these options.
- +BNC can average latencies per stream over a certain period of GPS time, the 'Log latency' interval. Mean latencies are calculated from the individual latencies of at most one (first incoming) observation or correction to Broadcast Ephemeris per second. The mean latencies are then saved in BNC's logfile. Note that computing correct latencies requires the clock of the host computer to be properly synchronized. Note further that the latencies available from the 'Latency' tab on the bottom of the main window represent individual latencies and not the mean latencies for the logfile. @@ -1067,5 +1107,5 @@ -
+When configuring a GNSS receiver for RTCM stream generation, the firmware's setup interface may not provide details about RTCM message types. As reliable information concerning stream contents should be available i.e. for NTRIP broadcaster operators to maintain the broadcaster's source-table, BNC allows to scan RTCM streams for incoming message types and printout some of the contained meta-data. The idea for this option arose from 'InspectRTCM', a comprehensive stream analyzing tool written by D. Stoecker. @@ -1093,5 +1133,5 @@
- +BNC can derive coordinates for a rover position following the Precise Point Positioning (PPP) approach. It uses either code or code plus phase data in ionosphere free linear combinations P3 or L3. Besides pulling a stream of observations from a dual frequency receiver, this also @@ -1214,23 +1254,23 @@
-3.11.1 Mode & Mountpoints - optional
3.12.1 Mode & Mountpoints - optional
Specify the Point Positioning mode you want to apply and the mountpoints for observations and Broadcast Ephemeris corrections.
- +Choose between plain Single Point Positioning (SPP) and Precise Point Positioning (PPP) in 'Realtime' or 'Post-Processing' mode.
-3.11.1.2 Obs Mountpoint - optional
3.12.1.2 Obs Mountpoint - optional
Specify an 'Observations Mountpoint' from the list of selected 'Streams' you are pulling if you want BNC to derive coordinates for the affected rover position through a Point Positioning solution.
-3.11.1.3 Corr Mountpoint - optional
3.12.1.3 Corr Mountpoint - optional
Specify a Broadcast Ephemeris 'Corrections Mountpoint' from the list of selected 'Streams' you are pulling if you want BNC to correct your positioning solution accordingly.
-3.11.2 Marker Coordinates - optional
3.12.2 Marker Coordinates - optional
Enter the reference coordinate components X,Y,Z of the receiver's position in meters if known. This option makes only sense for static observations. Default are empty option fields, meaning that the antenna's XYZ position is unknown. @@ -1246,15 +1286,15 @@
-3.11.3 Antenna Excentricity - optional
3.12.3 Antenna Excentricity - optional
You may like to specify North, East and Up compoments of an antenna excentricity which is the difference between a nearby marker position and the antenna phase center. If you do so BNC will produce coordinates referring to the marker position and not referring to the antenna phase center..
-3.11.4 NMEA & Plot Output - optional
3.12.4 NMEA & Plot Output - optional
BNC allows to output results from Precise Point Positioning in NMEA format. It can also plot a time series of North, East and UP displacements of coordinate components.
- +The NMEA sentences generated about once per second are pairs of @@ -1271,5 +1311,5 @@
- +Specify the IP port number of a local port where Point Positioning results become available as NMEA messages. The default value for 'NMEA Port' is an empty option field, meaning that BNC does not provide NMEA messages vi IP port. Note that the NMEA file output and the NMEA IP port output are the same. @@ -1279,5 +1319,5 @@
- +PPP time series of North (red), East(green) and Up (blue) coordinate components will be plotted in the 'PPP Plot' tab when this option is ticked. Values will be either referred to an XYZ reference coordinate (if specified) or referred to the first estimated XYZ coordinate. The sliding PPP time series window will cover the period of the latest 5 minutes. @@ -1287,5 +1327,5 @@
-3.11.5 Post Processing - optional
3.12.5 Post Processing - optional
When in 'Post-Processing mode
BNC accepts RINEX v2 as well as RINEX v3 observation or navigation file formats. Files carrying Broadcast Ephemeris corrections must have the format produced by BNC in the 'Broadcast Corrections' option. @@ -1294,10 +1334,10 @@
- +BNC allows to correct observations for antenna phase center offsets and variations.
-3.11.6.1 ANTEX File - optional
3.12.6.1 ANTEX File - optional
IGS provides a file containing absolute phase center corrections for GNSS satellite and receiver antennas in ANTEX format. Entering the full path to such an ANTEX file is required for correcting observations for antenna phase center offsets and variations. It allows you to specify the name of your receiver's antenna (as contained in the ANTEX file) to apply such corrections. @@ -1307,5 +1347,5 @@
-3.11.6.2 Receiver Antenna Name - optional if 'ANTEX File' is set
3.12.6.2 Receiver Antenna Name - optional if 'ANTEX File' is set
Specify the receiver's antenna name as defined in your ANTEX file. Observations will be corrected for the antenna phase center's offset which may result in a reduction of a few centimeters at max. Corrections for phase center variations are not yet applied by BNC. The specified name must consist of 20 characters. Add trailing blanks if the antenna name has less then 20 characters. Examples: @@ -1320,5 +1360,5 @@
-3.11.6.3 Apply Satellite Antenna Offsets - optional if 'ANTEX File' is set
3.12.6.3 Apply Satellite Antenna Offsets - optional if 'ANTEX File' is set
BNC allows to correct observations for satellite antenna phase center offsets. (This option is not yet implemented.) @@ -1330,14 +1370,14 @@
- +BNC allows to use different Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows to introduce specific sigmas for code and phase observations as well as for reference coordinates and troposphere estimates. You may also like to carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold.
-3.11.7.1 Use Phase Obs - optional
3.12.7.1 Use Phase Obs - optional
By default BNC applies a Point Positioning solution using an ionosphere free P3 linear combination of code observations. Tick 'Use phase obs' for an ionosphere free L3 linear combination of phase observations.
-3.11.7.2 Estimate Tropo - optional
3.12.7.2 Estimate Tropo - optional
BNC estimates the tropospheric delay according to equation @@ -1351,15 +1391,15 @@
-3.11.7.3 Use GLONASS - optional
3.12.7.3 Use GLONASS - optional
By default BNC does not process GLONASS but only GPS observations when in Point Positioning mode. Tick 'Use GLONASS' to use GLONASS observations in addition to GPS (and Galileo if specified) for estimating coordinates in Point Positioning mode.
-3.11.7.4 Use Galileo - optional
3.12.7.4 Use Galileo - optional
By default BNC does not process Galileo but only GPS observations when in Point Positioning mode. Tick 'Use Galileo' to use Galileo observations in addition to GPS (and GLONASS if specified) for estimating coordinates in Point Positioning mode.
- +Zero value (or empty field) means that BNC processes each epoch of data immediately after its arrival using satellite clock corrections available at that time. Non-zero value 'Sync Corr' means that the epochs of data are buffered and the processing of each epoch is postponed till the satellite clock corrections not older than 'Sync Corr' are available. Specifying a value of half the update rate of the clock corrections as 'Sync Corr' (i.e. 5 sec) may be appropriate. Note that this causes an additional delay of the PPP solutions in the amount of the update rate. @@ -1372,5 +1412,5 @@
-3.11.7.6 Averaging - optional if XYZ is set
3.12.7.6 Averaging - optional if XYZ is set
Enter the length of a sliding time window in minutes. BNC will continuously output moving average values ns and their RMS as computed from those individual values obtained most recently throughout this period. RMS values presented for XYZ coordinates and tropospheric zenit path delays are bias reduced while RMS values for Nort/East/Up (NEU) displacements are not. Averaged values for XYZ coordinates and their RMS are marked with string "AVE-XYZ" in BNC's log file and 'Log' section while averaged values for NEU displacements and their RMS are marked with string "AVE-NEU" and averaged values for the tropospheric delays and their RMS are marked with string "AVE-TRP". Example: @@ -1385,5 +1425,5 @@
-3.11.7.7 Quick-Start - optional if XYZ is set
3.12.7.7 Quick-Start - optional if XYZ is set
Enter the lenght of a startup period in seconds for which you want to fix the PPP solution to a known XYZ coordinate. Constraining coordinate components is done in BNC through setting the 'XYZ White Noise' temporarily to zero. @@ -1398,5 +1438,5 @@
Figure: BNC in 'Quick-Start' mode
-3.11.7.8 Maximal Solution Gap - optional if Quick-Start is set
3.12.7.8 Maximal Solution Gap - optional if Quick-Start is set
Specify a 'Maximum Solution Gap' in seconds. Should the time span between two consecutive solutions exceed this limit, the algorithm returns into the Quick-Start mode and fixes the introduced reference coordinate for the specified Quick-Start period. A value of '120' seconds could be an appropriate choice. @@ -1406,5 +1446,5 @@
- +You may like to introduce specific sigmas for code and phase observations and for the estimation of troposphere parameters. @@ -1423,68 +1463,28 @@
-3.11.8.2 Phase - mandatory if 'Use Phase Obs' is set
3.12.8.2 Phase - mandatory if 'Use Phase Obs' is set
Specify a sigma for phase observations. Default is 0.02 m.
- +Enter a sigma in meters for the initial XYZ coordinate componentes. A value of 100.0 (default) may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting for example from a station with known XZY position in Quick-Start mode.
-3.11.8.4 XYZ White Noise - mandatory
3.12.8.4 XYZ White Noise - mandatory
Enter a sigma in meters for the 'White Noise' of estimated XYZ coordinate components. A value of 100.0 (default) may be appropriate considering the potential movement of a rover.
-3.11.8.5 Tropo Init - mandatory if 'Estimate tropo' is set
3.12.8.5 Tropo Init - mandatory if 'Estimate tropo' is set
Enter a sigma in meters for the a-priory model based tropospheric delay estimation. A value of 0.1 (default) may be an appropriate choice.
-3.11.8.6 Tropo White Noise - mandatory if 'Estimate tropo' is set
3.12.8.6 Tropo White Noise - mandatory if 'Estimate tropo' is set
Enter a sigma in meters per second to describe the expected variation of the tropospheric effect. Supposing 1Hz observation data, a value of 3e-6 (default) would mean that the tropospheric effect may vary for 3600 * 3e-6 = 0.01 meters per hour.
- - --BNC allows to concatenate RINEX files and edit their contents. Observation and navigation files can be handled. BNC can also carry out a quality check of the contents of RINEX files. This functionality in BNC stands for -
Select an action. Options are 'Edit/Concatenate' and 'Analyze'. -
3.12.2 Set Edit Options - mandatory if 'Edit/Concatenate' is set
Once action 'Edit/Concationate' is selected, you have to specify editing options. BNC lets you specify the RINEX version, sampling rate, begin and end of file and marker, antenna or receiver details. -
- -3.12.3 Input Files - mandatory if 'Action' is set
-Specify full path to input RINEX observation file(s), and
-specify full path to input RINEX navigation file(s).
-
3.12.4 Output Files - mandatory if 'Action' is set
-Mandatory if 'Edit/Concatenate' selected:
-Specify full path to output RINEX observation file(s), and
-specify full path to output RINEX navigation file(s).
-
-Mandatory if 'Analyze' selected:
-Specify logfile(s) to output analysis results.
-