+BNC allows to compare files in SP3 format carrying GNSS satellite orbit and clock data. +
+ +3.7.1 Input SP3 Files - optional
+Specify the path for two SP3 files separated by a comma. +
+ +3.7.2 Logfile - mandatory if 'Input SP3 Files' is set
+Specify a logfile to save results of the SP3 file comparison. +
+ +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). @@ -1115,15 +1133,15 @@ -
3.7.1 Directory, ASCII - optional
3.8.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.7.2 Interval - mandatory if 'Directory, ASCII' is set
3.8.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. @@ -1170,5 +1188,5 @@
-3.7.4 Wait for Full Corr Epoch - mandatory if 'Port' is set
3.8.4 Wait for Full Corr Epoch - mandatory if 'Port' is set
When feeding a real-time GNSS network engine (see 'Feed Engine') waiting epoch by epoch for synchronized Broadcast Corrections, or when you 'Combine Corrections' BNC drops (only concerning IP port output) whatever is received later than 'Wait for full corr 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 over aged by 5 sec" shows up in BNC's logfile if 'Wait for full corr epoch' is exceeded. @@ -1178,5 +1196,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 sorted per incoming stream. @@ -1264,10 +1282,10 @@
Figure 12: 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 observation data for any specific epoch which become available within a certain number of latency seconds (see 'Wait for Full Obs Epoch' option). It then - epoch by epoch - outputs whatever has been received. The output comes block wise per stream. 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.8.2 Wait for Full Obs Epoch - mandatory if 'Port' is set
3.9.2 Wait for Full Obs Epoch - mandatory if 'Port' is set
When feeding a real-time GNSS network engine waiting for synchronized observations epoch by epoch, BNC drops whatever is received later than 'Wait for full obs 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 obs epoch' is 5 seconds. @@ -1277,10 +1295,10 @@
-3.8.3 Sampling - mandatory if 'File' or 'Port' is set
3.9.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.
- +Specify 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. @@ -1290,10 +1308,10 @@
-3.8.5 Port (unsynchronized) - optional
3.9.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. Nevertheless, the output comes block wise per stream. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no unsynchronized output is generated.
- +You may use BNC to feed a serial connected device like a GNSS receiver. For that an incoming stream 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 RTK rover. @@ -1302,5 +1320,5 @@
Figure 13: BNC pulling a VRS stream to feed a serial connected RTK rover.
- +Enter a 'Mountpoint' to forward its corresponding stream to a serial connected GNSS receiver. @@ -1310,5 +1328,5 @@
-3.9.2 Port Name - mandatory if 'Mountpoint' is set
3.10.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 @@ -1327,30 +1345,30 @@
-3.9.3 Baud Rate - mandatory if 'Mountpoint' is set
3.10.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.9.4 Flow Control - mandatory if 'Mountpoint' is set
3.10.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.9.5 Parity - mandatory if 'Mountpoint' is set
3.10.5 Parity - mandatory if 'Mountpoint' is set
Select the 'Parity' for the serial output link. Note that parity is often set to 'NONE'.
-3.9.6 Data Bits - mandatory if 'Mountpoint' is set
3.10.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.9.7 Stop Bits - mandatory if 'Mountpoint' is set
3.10.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.9.8 NMEA - mandatory for VRS streams
3.10.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. @@ -1363,8 +1381,8 @@
-3.9.9 File - optional if 'Auto' NMEA is set
3.10.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.9.10 Height - mandatory if 'Manual' NMEA is set
3.10.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. @@ -1374,5 +1392,5 @@
- +@@ -1389,10 +1407,10 @@
-3.10.1 Observation Rate - mandatory if 'Failure threshold', 'Recovery threshold' and 'Script' is set
3.11.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 explicit information from BNC about stream outages and incoming streams that cannot be decoded.
-3.10.2 Failure Threshold - optional
3.11.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 inundate user with too many event reports. @@ -1402,5 +1420,5 @@
-3.10.3 Recovery Threshold - optional
3.11.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 inundate users with too many event reports. @@ -1410,5 +1428,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 OS X systems) together with date and time information. @@ -1442,5 +1460,5 @@
- +This section describes several miscellaneous options which can be applied for a single stream (mountpoint) or for all configured streams. @@ -1454,10 +1472,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 one (first incoming) observation or Broadcast Correction 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 visualized latencies from the 'Latency' tab on the bottom of the main window represent individual latencies and not the mean latencies for the logfile. @@ -1487,5 +1505,5 @@ -
+When configuring a GNSS receiver for RTCM stream generation, the firmware's setup interface may not provide details about RTCM message types observation 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. Contained observation types are also printed because such information is required a-priori to the conversion of RTCM Version 3 MSM streams to RINEX Version 3 files. The idea for this option arose from 'InspectRTCM', a comprehensive stream analyzing tool written by D. Stoecker. @@ -1518,5 +1536,5 @@ -
+BNC can output streams related to the above specified 'Mountpoint' through a TCP/IP port of your local host. Enter a port number to activate this function. The stream contents remains untouched. BNC does not decode or reformat the data. @@ -1530,5 +1548,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 @@ -1671,25 +1689,25 @@
-3.12.1 Mode & Mountpoints - optional
3.13.1 Mode & Mountpoints - optional
Specify the Point Positioning mode you want to apply and the mountpoints for observations and Broadcast Corrections.
- +Choose between plain Single Point Positioning (SPP) and Precise Point Positioning (PPP) in 'Realtime' or 'Post-Processing' mode. Options are 'Realtime-PPP', 'Realtime-SPP', and 'Post-Processing'.
-3.12.1.2 Obs Mountpoint - optional
3.13.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.12.1.3 Corr Mountpoint - optional
3.13.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. Not that the stream's corrections must refer to the satellite Antenna Phase Center (APC).
-3.12.2 Marker Coordinates - optional
3.13.2 Marker Coordinates - optional
Enter the reference coordinate XYZ of the receiver's position in meters if known. This option makes only sense for static observations. Defaults are empty option fields, meaning that the antenna's XYZ position is unknown. @@ -1705,10 +1723,10 @@
-3.12.3 Antenna Eccentricity - optional
3.13.3 Antenna Eccentricity - optional
You may like to specify North, East and Up components of an antenna eccentricity 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.
- +BNC allows to output results from Precise Point Positioning in NMEA format. @@ -1718,5 +1736,5 @@
- +The NMEA sentences generated about once per second are pairs of @@ -1730,5 +1748,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. @@ -1738,5 +1756,5 @@
-3.12.5 Post Processing - optional
3.13.5 Post Processing - optional
When in 'Post-Processing' mode
BNC allows correcting observations for antenna phase center offsets and variations.
-3.12.6.1 ANTEX File - optional
3.13.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. @@ -1763,5 +1781,5 @@
-3.12.6.2 Receiver Antenna Name - optional if 'ANTEX File' is set
3.13.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 than 20 characters. Examples: @@ -1776,14 +1794,14 @@
- +BNC allows using different Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows introducing 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.12.7.1 Use Phase Obs - optional
3.13.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.12.7.2 Estimate Tropo - optional
3.13.7.2 Estimate Tropo - optional
BNC estimates the tropospheric delay according to equation @@ -1797,5 +1815,5 @@
-3.12.7.3 Use GLONASS - optional
3.13.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. @@ -1807,5 +1825,5 @@
- +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 half of the update rate. @@ -1818,5 +1836,5 @@
-3.12.7.6 Averaging - optional if XYZ is set
3.13.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 and their RMS as computed from those individual values obtained most recently throughout this period. RMS values presented for XYZ coordinates and tropospheric zenith path delays are bias reduced while RMS values for North/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: @@ -1831,5 +1849,5 @@
-3.12.7.7 Quick-Start - optional if XYZ is set
3.13.7.7 Quick-Start - optional if XYZ is set
Enter the length of a startup period in seconds for which you want to fix the PPP solution to a known XYZ coordinate. Constraining coordinates is done in BNC through setting the 'XYZ White Noise' temporarily to zero. @@ -1847,5 +1865,5 @@
Figure 18: BNC in 'Quick-Start' mode (PPP, Panel 2)
-3.12.7.8 Maximal Solution Gap - optional if Quick-Start is set
3.13.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 '60' seconds could be an appropriate choice. @@ -1855,5 +1873,5 @@
-3.12.7.9 Audio Response - optional if Quick-Start is set
3.13.7.9 Audio Response - optional if Quick-Start is set
For natural hazard prediction and monitoring it may be appropriate to generate audio alerts. For that you can specify an 'Audio response' threshold in meters. A beep is produced by BNC whenever a horizontal PPP coordinate component differs by more than the threshold value from the specified marker coordinate. @@ -1863,10 +1881,10 @@
- +You may like to introduce specific sigmas for code and phase observations and for the estimation of troposphere parameters.
-3.12.8.1 Code - mandatory if 'Use Phase Obs' is set
3.13.8.1 Code - mandatory if 'Use Phase Obs' is set
When 'Use phase obs' is set in BNC, the PPP solution will be carried out using both, code and phase observations. A sigma of 10.0 m for code observations and a sigma of 0.02 m for phase observations (defaults) are used to combine both types of observations. As the convergence characteristic of a PPP solution can be influenced by the ratio of the sigmas for code and phase, you may like to introduce you own sigmas for code and phase observations which differ from the default values. @@ -1880,30 +1898,30 @@
-3.12.8.2 Phase - mandatory if 'Use Phase Obs' is set
3.13.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. 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.12.8.4 XYZ White Noise - mandatory
3.13.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 when considering possible sudden movements of a rover.
-3.12.8.5 Tropo Init - mandatory if 'Estimate tropo' is set
3.13.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.12.8.6 Tropo White Noise - mandatory if 'Estimate tropo' is set
3.13.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.
- +PPP time series of North (red), East (green) and Up (blue) displacements 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. @@ -1913,5 +1931,5 @@
- +You make like to track your rover position using Google Maps or Open StreetMap as a background map. Track maps can be produced with BNC in 'Realtime-PPP', 'Realtime-SPP' and 'Post-Processing' PPP mode. @@ -1925,30 +1943,30 @@
Figure 19: Track of positions from BNC with Google Maps in the background.
- +The 'Open Map' button opens a windows showing a map according to options specified below.
-3.12.10.2 Google/OSM - mandatory before pushing 'Open Map'
3.13.10.2 Google/OSM - mandatory before pushing 'Open Map'
Specify either 'Google' or 'OSM' as the background for your rover positions.
-3.12.10.3 Dot Size - mandatory before pushing 'Open Map'
3.13.10.3 Dot Size - mandatory before pushing 'Open Map'
Specify the size of dots showing the rover position. A dot size of '3' may be appropriate. The maximum possible dot size is '10'. An empty option field or a size of '0' would mean that you don't want BNC to show the rover's track on the map.
-3.12.10.4 Dot Color - mandatory before pushing 'Open Map'
3.13.10.4 Dot Color - mandatory before pushing 'Open Map'
Specify the color of dots showing the rover track.
-3.12.10.5 Speed - mandatory before pushing 'Open Map'
3.13.10.5 Speed - mandatory before pushing 'Open Map'
With BNC in PPP post-processing mode you can specify the speed of computations as appropriate for visualization. Note that you can adjust 'Speed' on-the-fly while BNC is processing your observatins.
- +BNC allows processing several orbit and clock correction streams in real-time to produce, encode, upload and save a combination of Broadcast Corrections from various providers. All corrections must refer to satellite Antenna Phase Centers (APC). It is so far only the satellite clock corrections which are combined while orbit corrections in the combination product as well as the product update rates are just taken over from one of the incoming Broadcast Correction streams. Combining only clock corrections using a fixed orbit reference has the possibility to introduce some analysis inconsistencies. We may therefore eventually consider improvements on this approach. The clock combination can be based either on a plain 'Single-Epoch' or on a 'Kalman' Filter approach. @@ -2011,5 +2029,5 @@
-3.13.1 Combine Corrections Table - optional
3.14.1 Combine Corrections Table - optional
Hit the 'Add Row' button, double click on the 'Mountpoint' field, enter a Broadcast Corrections mountpoint from the 'Streams' section and hit Enter. Then double click on the 'AC Name' field to enter your choice of an abbreviation for the Analysis Center (AC) providing the Antenna Phase Center (APC) related stream. Finally, double click on the 'Weight' field to enter a weight to be applied to this stream in the combination. The stream processing can already be started with only one corrections stream configured for combination. @@ -2027,5 +2045,5 @@
-3.13.1.1 Add Row, Delete - optional
3.14.1.1 Add Row, Delete - optional
Hit 'Add Row' button to add another row to the 'Combine Corrections' table or hit the 'Delete' button to delete the highlighted row(s). @@ -2051,5 +2069,5 @@
-3.13.1.3 Maximal Residuum - mandatory if 'Combine Corrections' table is populated
3.14.1.3 Maximal Residuum - mandatory if 'Combine Corrections' table is populated
BNC combines all incoming clocks according to specified weights. Individual clock estimates that differ by more than 'Maximal Residuum' meters from the average of all clocks will be ignored.
@@ -2057,9 +2075,9 @@
Default is a 'Maximal Residuum' of 999.0 meters
-3.13.1.4 Sampling - mandatory if 'Combine Corrections' table is populated
3.14.1.4 Sampling - mandatory if 'Combine Corrections' table is populated
Specify a combination sampling interval. Orbit and clock corrections will be produced following that interval. A value of 10 sec may be an appropriate choice.
- +BNC can upload streams carrying orbit and clock corrections to Broadcast Ephemeris in radial, along-track and cross-track components if they are
3.14.1 Add, Delete Row - optional
3.15.1 Add, Delete Row - optional
Hit 'Add Row' button to add another row to the stream 'Upload Table' or hit the 'Delete' button to delete the highlighted row(s).
@@ -2165,5 +2183,5 @@ -3.14.2 Host, Port, Mountpoint, Password - mandatory if 'Upload Table' entries specified
3.15.2 Host, Port, Mountpoint, Password - mandatory if 'Upload Table' entries specified
Specify the domain name or IP number of an NTRIP Broadcaster for uploading the stream. Furthermore, specify the caster's listening IP port, an upload mountpoint and an upload password. Note that NTRIP Broadcasters are often configured to provide access on more than one port, usually port 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s). @@ -2176,5 +2194,5 @@
-3.14.3 System - mandatory if 'Host' is set
3.15.3 System - mandatory if 'Host' is set
BNC allows configuring several Broadcast Correction streams for upload so that they refer to different reference systems and different NTRIP Broadcasters. You may use this functionality for parallel support of a backup NTRIP Broadcaster or for simultaneous support of various regional reference systems. Available options for transforming orbit and clock corrections to specific target reference systems are @@ -2351,10 +2369,10 @@
-3.14.4 Center of Mass - optional
3.15.4 Center of Mass - optional
BNC allows to either referring Broadcast Corrections to the satellite's Center of Mass (CoM) or to the satellite's Antenna Phase Center (APC). By default corrections refer to APC. Tick 'Center of Mass' to refer uploaded corrections to CoM.
- +Specify a path for saving the generated orbit corrections as SP3 orbit files. If the specified directory does not exist, BNC will not create SP3 orbit files. The following is a path example for a Linux system:
/home/user/BNC${GPSWD}.sp3
Note that '${GPSWD}' produces the GPS Week and Day number in the file name.
@@ -2375,5 +2393,5 @@
- +The clock corrections generated by BNC for upload can be logged in Clock RINEX format. The file naming follows the RINEX convention. @@ -2386,13 +2404,13 @@
-3.14.7 Interval - mandatory if 'Upload Table' entries specified
3.15.7 Interval - mandatory if 'Upload Table' entries specified
Select the length of Clock RINEX files and SP3 Orbit files. The default value is 1 day.
-3.14.8 Sampling - mandatory if 'Upload Table' entries specified
3.15.8 Sampling - mandatory if 'Upload Table' entries specified
BNC requires an orbit corrections sampling interval for the stream to be uploaded and sampling intervals for SP3 and Clock RINEX files. The outgoing stream's clock correction sampling interval follows that of incoming corrections and is therefore nothing to be specified here.
-3.14.8.1 Orbits - mandatory if 'Upload Table' entries specified
3.15.8.1 Orbits - mandatory if 'Upload Table' entries specified
Select the stream's orbit correction sampling interval in seconds. A value of 60 sec may be appropriate.
A value of zero '0' tells BNC to upload all orbit correction samples coming in from the real-time GNSS engine along with the clock correction samples to produce combined orbit and clock corrections to Broadcast Ephemeris (1060 for GPS, 1066 for GLONASS).
@@ -2425,11 +2443,11 @@
Note that only when specifying a value of zereo '0' (default) for 'Sampling Orb', BNC produces combined orbit and clock correction messages.
-
3.14.8.2 SP3 - mandatory if 'SP3 File' is specified
3.15.8.2 SP3 - mandatory if 'SP3 File' is specified
Select the SP3 orbit file sampling interval in minutes. A value of 15 min may be appropriate. A value of zero '0' tells BNC to store all available samples into SP3 orbit files.
-3.14.8.3 RINEX - mandatory if 'RNX File' is specified
3.15.8.3 RINEX - mandatory if 'RNX File' is specified
Select the Clock RINEX file sampling interval in seconds. A value of 10 sec may be appropriate. A value of zero '0' tells BNC to store all available samples into Clock RINEX files.
-3.14.9 Custom Trafo - optional if 'Upload Table' entries specified
3.15.9 Custom Trafo - optional if 'Upload Table' entries specified
Hit 'Custom Trafo' to specify your own 14 parameter Helmert Transformation instead of selecting a predefined transformation through 'System' button.
@@ -2440,10 +2458,10 @@Figure 23: Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.
- +BNC can upload a stream carrying Broadcast Ephemeris in RTCM Version 3 format to an NTRIP Broadcaster.
- +Specify the 'Host' IP name or number of an NTRIP Broadcaster to upload the stream. An empty option field means that you don't want to upload Broadcast Ephemeris. @@ -2454,5 +2472,5 @@
-3.15.2 Mountpoint & Password - mandatory if 'Host' is set
3.16.2 Mountpoint & Password - mandatory if 'Host' is set
BNC uploads a stream to the NTRIP Broadcaster by referring to a dedicated mountpoint that has been set by its operator. Specify the mountpoint based on the details you received for your stream from the operator. It is often a four character ID (capital letters) plus an integer number.
@@ -2460,5 +2478,5 @@ -3.15.3 Sampling - mandatory if 'Host' is set
3.16.3 Sampling - mandatory if 'Host' is set
Figure 24: Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an NTRIP Broadcaster.
- +Each stream on an NTRIP Broadcaster (and consequently on BNC) is defined using a unique source ID called mountpoint. An NTRIP Client like BNC accesses the desired stream by referring to its mountpoint. Information about streams and their mountpoints is available through the source-table maintained by the NTRIP Broadcaster. Note that mountpoints could show up in BNC more than once when retrieving streams from several NTRIP Broadcasters. @@ -2488,5 +2506,5 @@
- +To remove a stream from the 'Streams' canvas in the main window, highlight it by clicking on it and hit the 'Delete Stream' button. You can also remove multiple streams simultaneously by highlighting them using +Shift and +Ctrl.
-3.16.3 Reconfigure Stream Selection On-the-fly
3.17.3 Reconfigure Stream Selection On-the-fly
The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process. @@ -2517,14 +2535,14 @@
- +A tabs section on the bottom of the main window provides online control of BNC's activities. Tabs are available to show the records saved in a logfile, for a plot to control the bandwidth consumption, for a plot showing stream latencies, and for time series plots of PPP results.
- +Records of BNC's activities are shown in the 'Log' tab. They can be saved into a file when a valid path is specified in the 'Logfile (full path)' field.
- +The bandwidth consumption per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). The following figure shows an example for the bandwidth consumption of incoming streams. @@ -2534,5 +2552,5 @@
Figure 25: Bandwidth consumption of incoming streams.
- +The latency of observations in each incoming stream is shown in the 'Latency' tab in milliseconds or seconds. Streams not carrying observations (i.e. those providing only Broadcast Ephemeris messages) or having an outage are not considered here and shown in red color. Note that the calculation of correct latencies requires the clock of the host computer to be properly synchronized. The next figure shows an example for the latency of incoming streams. @@ -2542,5 +2560,5 @@
Figure 26: Latency of incoming streams.
- +Precise Point Positioning time series of North (red), East (green) and Up (blue) coordinate components are shown in the 'PPP Plot' tab when a 'Origin' option is defined. Values are either referred to reference coordinates (if specified) or referred to the first estimated set of coordinate components. The time as given in format [hh:mm] refers to GPS Time. The sliding PPP time series window covers a period of 5 minutes. Note that it may take up to 30 seconds or more till the first PPP solutions becomes available. The following figure shows the screenshot of a PPP time series plot of North, East and Up coordinate components. @@ -2550,5 +2568,5 @@
Figure 27: Time series plot of PPP session.
- +The bottom menu bar allows to add or delete streams to BNC's configuration and to start or stop it. It also provides access to BNC's online help function. The 'Add Stream' button opens a window that allows user to select one of several input communication links, see figure below. @@ -2558,10 +2576,10 @@
Figure 28: Steam input communication links.
- +Button 'Add Stream' allows you to pull streams either from an NTRIP Broadcaster or from a TCP/IP port, a UPD port, or a serial port.
-3.18.1.1 Add Stream - Coming from Caster
3.19.1.1 Add Stream - Coming from Caster
@@ -2569,10 +2587,10 @@
-3.18.1.1.1 Caster Host and Port - mandatory
3.19.1.1.1 Caster Host and Port - mandatory
Enter the NTRIP Broadcaster host IP and port number. Note that EUREF and IGS operate NTRIP Broadcasters at http://www.euref-ip.net/home, http://www.igs-ip.net/home, http://www.products.igs-ip.net/home and http://mgex.igs-ip.net/home.
-3.18.1.1.2 Casters Table - optional
3.19.1.1.2 Casters Table - optional
It may be that you are not sure about your NTRIP Broadcasters host and port number or you are interested in other broadcaster installations operated elsewhere. Hit 'Show' for a table of known broadcasters maintained at www.rtcm-ntrip.org/home. A window opens which allows selecting a broadcaster for stream retrieval, see figure below. @@ -2583,10 +2601,10 @@
Figure 29: Casters table.
-3.18.1.1.3 User and Password - mandatory for protected streams
3.19.1.1.3 User and Password - mandatory for protected streams
Some streams on NTRIP Broadcasters may be restricted. Enter a valid 'User' ID and 'Password' for access to protected streams. Accounts are usually provided per NTRIP Broadcaster through a registration procedure. Register through http://igs.bkg.bund.de/ntrip/registeruser for access to protected streams from EUREF and IGS.
- +Use the 'Get Table' button 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 Version 2, RTCM Version 3, or RTNET format. For access to observations, Broadcast Ephemeris and Broadcast Corrections in RTCM format streams must contain a selection of appropriate message types as listed in the Annex, cf. data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3 streams containing message types 1019 (GPS) and 1020 (GLONASS) and 1044 (QZSS) and 1045, 1046 (Galileo) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example source-table. @@ -2601,5 +2619,5 @@
Figure 30: Broadcaster source-table.
-3.18.1.1.5 NTRIP Version - mandatory
3.19.1.1.5 NTRIP Version - mandatory
Some limitations and deficiencies of the NTRIP Version 1 stream transport protocol are solved in NTRIP Version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Version 2 is backwards compatible to Version 1. Options implemented in BNC are: @@ -2623,5 +2641,5 @@
- +Button 'Map' opens a window to show a distribution map of the caster's streams. You may like to zoom in or out using the mouse. Left button: draw a rectangle to zoom, right button: zoom out, middle button: zoom back. @@ -2631,5 +2649,5 @@
Figure 31: Stream distribution map derived from NTRIP Broadcaster source-table.
-3.18.1.2 Add Stream - Coming from TCP/IP Port
3.19.1.2 Add Stream - Coming from TCP/IP Port
Button 'Add Stream' > 'Coming from TCP/IP Port' allows to retrieve streams via TCP directly from an IP address without using the NTRIP transport protocol. For that you: @@ -2650,5 +2668,5 @@
-3.18.1.3 Add Stream - Coming from UDP Port
3.19.1.3 Add Stream - Coming from UDP Port
Button 'Add Stream' > 'Coming from UDP Port' allows to pick up streams arriving directly at one of the local host's UDP ports without using the NTRIP transport protocol. For that you: @@ -2665,5 +2683,5 @@
-
3.18.1.4 Add Stream - Coming from Serial Port
3.19.1.4 Add Stream - Coming from Serial Port
Button 'Add Stream' > 'Coming from Serial Port' allows to retrieve streams from a GNSS receiver via serial port without using the NTRIP transport protocol. For that you: @@ -2705,30 +2723,30 @@
Figure 32: BNC setup for pulling a stream via serial port.
- +Button 'Delete Stream' allows you to delete streams previously selected for retrieval as listed under the 'Streams' canvas on BNC's main window.
- +Button 'Map' opens a window to show a distribution map of the streams selected for retrieval as listed under the 'Streams' canvas. You may like to zoom in or out using the mouse. Left button: draw a rectangle to zoom, right button: zoom out, middle button: zoom back.
- +Hit 'Start' to start retrieving, decoding or converting GNSS data streams in real-time. Note that 'Start' generally forces BNC to begin with fresh RINEX which might overwrite existing files when necessary unless the option 'Append files' is ticked.
- +Hit the 'Stop' button in order to stop BNC.
- +Command line options are available to run BNC in 'no window' mode or let it read data offline from one or several files for debugging or Post Processing purposes. BNC will then use processing options from the involved configuration file. Note that the self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration file name instead of using the default name 'BNC.bnc'.
-3.19.1 No Window Mode - optional
3.20.1 No Window Mode - optional
Apart from its regular windows mode, BNC can be started on all systems as a batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file on disk. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems. @@ -2764,5 +2782,5 @@ -
+Although BNC is primarily a real-time online tool, for debugging purposes it can be run offline to read data from a file previously saved through option 'Raw output file'. Enter the following command line option for that @@ -2781,5 +2799,5 @@
-3.19.3 Configuration File - optional
3.20.3 Configuration File - optional
3.19.4 Configuration Options - optional
3.20.4 Configuration Options - optional
BNC applies options from the configuration file but allows updating every one of them on the command line while the contents of the configuration file remains unchanged. The command line syntax for that looks as follows