The BKG Ntrip Client (BNC) is a program for simultaneously retrieving, decoding and converting real-time GNSS data streams from NTRIP broadcasters like http://www.euref-ip.net/home or http://www.igs-ip.net/home or http://products.igs-ip.net/home.
BNC has been developed for the Federal Agency for Cartography and Geodesy (BKG) within the framework of EUREF's Real-time GNSS Project (EUREF-IP, IP for Internet Protocol) and the Real-Time IGS Pilot Project (RTIGS).
BNC has been written under GNU General Public License (GPL). Binaries for BNC are available for Windows, 32-bit Linux, 64-bit Linux (compiled under -m32 32-bit compatibility mode), Solaris, and Mac systems. We used the MinGW Version 5.1.3 compiler to create the Windows binary. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4.5.2 are installed.
Please ensure that you have installed the latest version of BNC available from http://igs.bkg.bund.de/ntrip/download. We are continuously working on the program and would appreciate if you could send any comments, suggestions, or bug reports to [euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de].
The purpose of BNC is to
BNC mainly supports decoding the following GNSS stream formats and message types:
The first of the following figures shows a flow chart of BNC connected to a GNSS receiver via serial or TCP communication link for the pupose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX batches. The third figure shows a flow chart of BNC feeding a real-time GNSS engine. The engine then estimates satellite orbit and clock correctors. The 'BKG Ntrip Server' (BNS) is used in this scenario to encode correctors to RTCMv3.
Figure: Flowchart, BNC connected to a GNSS receiver for Precise Point Positioning.
Figure: Flowchart, BNC converting RTCM streams to RINEX batches.
Figure: Flowchart, BNC feeding a real-time GNSS engine.
Although BNC is a real-time tool to be operated in online mode, it can be run offline for post-processing of data made availabe from a single file. Furthermore, apart from its regular window mode, BNC can be run as a batch/background job in a 'no window' mode using processing options from a previously saved configuration.
Unless in offline mode, BNC
The main window of BNC shows a top menu bar section, a sections for tabs to set processing options, a 'Streams' section and a section for 'Log' tabs, and a bottom menu bar section, see figure below.
Figure: Sections on BNC's main window.
This chapter describes BNC's settings and how to handle the program. It explains the top menu bar, the processing options, the 'Streams' and 'Log' sections, and the bottom menu bar.
The usual handling of BNC is that you first select a number of streams ('Add Stream'). Any stream configured to BNC shows up on the 'Streams' canvas in the middle of BNC's main window. You then go through BNC's various configuration tabs to select a combination of input, processing and output options before you start the program ('Start'). Records of BNC's activities are shown in the 'Log' tab. The bandwidth consumption per stream, the latency of incoming observations and PPP time series for coordinate components are shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs of the main window.
As a default, configuration files for running BNC on Unix/Linux/Mac systems are saved in directory '${HOME}/.config/BKG'. On Windows systems, they are typically saved in directory 'C:/Documents and Settings/Username/.config/BKG'. The default configuration file name is 'BNC.ini'.
The default file name 'BNC.ini' can be changed and the file contents can easily be edited. On graphical user interfaces it is possible to Drag & Drop a configuration file icon to start BNC (not on Mac systems). Some configuration options can be changed on-the-fly. See annexed 'Configuration Example' for a complete set of configuration options.
3.1. Top Menu Bar
3.1.1 File
3.1.2 Help
3.2. Proxy
3.3. General
3.3.1. Logfile
3.3.2. Append Files
3.3.3. Reread Configuration
3.3.4. Auto Start
3.3.5. Raw Output File
3.4. RINEX Observations
3.4.1. File Names
3.4.2. Directory
3.4.3. File Interval
3.4.4. Sampling
3.4.5. Skeleton Extension
3.4.6. Script
3.4.7. Version
3.5. RINEX Ephemeris
3.5.1. Directory
3.5.2. Interval
3.5.3. Port
3.5.4. Version
3.6. Broadcast Corrections
3.6.1. Directory
3.6.2. Interval
3.6.3. Port
3.6.4. Wait for Full Epoch
3.7. Feed Engine
3.7.1. Port
3.7.2. Wait for Full Epoch
3.7.3. Sampling
3.7.4. File
3.7.5. Port (unsynchronized)
3.8. Serial Output
3.8.1. Mountpoint
3.8.2. Port Name
3.8.3. Baud Rate
3.8.4. Flow Control
3.8.5. Parity
3.8.6. Data Bits
3.8.7. Stop Bits
3.8.8. NMEA
3.8.9. File
3.8.10. Height
3.9. Outages
3.9.1. Observation Rate
3.9.2. Failure Threshold
3.9.3. Recovery Threshold
3.9.4. Script
3.10. Miscellaneous
3.10.1. Mountpoint
3.10.2. Log Latency
3.10.3. Scan RTCM
3.11. PPP Client
3.11.1 Mountpoint
3.11.1.1 XYZ
3.11.2 Options
3.11.2.1 Use Phase Obs
3.11.2.2 Estimate Tropo
3.11.2.3 Use GLONASS
3.11.2.4 PPP Plot
3.11.3 Options cont'd
3.11.3.1 Sigma Code/Phase
3.11.3.2 Quick-Start
3.11.3.3 Averaging
3.11.4 Parameter Sigmas
3.11.4.1 XYZ Init
3.11.4.2 XYZ White Noise
3.11.4.3 Tropo Init
3.11.4.4 Tropo White Noise
3.11.5 NMEA
3.11.5.1 File
3.11.5.2 Port
3.12. Streams
3.12.1 Edit Streams
3.12.2 Delete Stream
3.12.3 Reconfigure Streams On-the-fly
3.13. Logging
3.13.1 Log
3.13.2 Throughput
3.13.3 Latency
3.13.4 PPP Plot
3.14. Bottom Menu Bar
3.14.1. Add Stream - Coming from Caster
3.14.1.1 Caster Host and Port
3.14.1.2 Casters Table
3.14.1.3 User and Password
3.14.1.4 Get Table
3.14.1.5 NTRIP Version
3.14.2 Add Stream - Coming from TCP/IP Port
3.14.3 Add Stream - Coming from UDP Port
3.14.4 Add Stream - Coming from Serial Port
3.14.5 Start
3.14.6 Stop
3.15. Command Line Options
3.15.1. No Window Mode
3.15.2. Offline Mode
3.15.3. Configuration File
The top menu bar allows to select a font for the BNC windows, save configured options or quit the program execution. It also provides access to a program documentation.
The 'File' button lets you
The 'Help' button provides access to
BNC comes with a help system providing online information about its functionality and usage. Short descriptions are available for any widget. Focus to the relevant widget and press Shift+F1 to request help information. A help text appears immediately; it disappears as soon as the user does something else. The dialogs on some operating systems may provide a "?" button that users can click; they then click the relevant widget to pop up the help text.
3.2. Proxy - for usage in a protected LAN
If you are running BNC within a protected Local Area Network (LAN), you might need to use a proxy server to access the Internet. Enter your proxy server IP and port number in case one is operated in front of BNC. If you don't know the IP and port of your proxy server, check the proxy server settings in your Internet browser or ask your network administrator.
Note that IP streaming is often not allowed in a LAN. In this case you need to ask your network administrator for an appropriate modification of the local security policy or for the installation of a TCP relay to the NTRIP broadcasters. If these are not possible, you might need to run BNC outside your LAN on a host that has unobstructed connection to the Internet.
The following defines general settings for BNC's logfile, file handling, reconfiguration on-the-fly, and auto-start.
Records of BNC's activities are shown in the 'Log' tab on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. The logfile name will automatically be extended by a string '_YYMMDD' carrying the current date. This leads to series of daily logfiles when running BNC continuously for extended. Message logs cover the communication status between BNC and the NTRIP broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. All times are given in UTC. The default value for 'Logfile (full path)' is an empty option field, meaning that BNC logs will not saved into a file.
When BNC is started, new files are created by default and any existing files with the same name will be overwritten. However, users might want to append existing files following a restart of BNC, a system crash or when BNC crashed. Tick 'Append files' to continue with existing files and keep what has been recorded so far. Note that option 'Append files' affects all types of files created by BNC.
3.3.3 Reread Configuration - optional
When operating BNC online in 'no window' mode (command line option -nw), some configuration options can nevertheless be changed on-the-fly without interrupting the running process. For that you force the program to reread parts of its configuration in pre-defined intervals from the disk. Select '1 min', '1 hour', or '1 day' to let BNC reread on-the-fly changeable configuration options every full minute, hour, or day. This lets in between edited options become effective without interrupting uninvolved threads. See annexed section 'Configuration Example' for a configuration file example and a list of on-the-fly changeable options.
You may like to auto-start BNC at startup time in window mode with pre-assigned configuration options. This may be required i.e. immediately after booting your system. Tick 'Auto start' to supersede the usage of the 'Start' button. Make sure that you maintain a link to BNC for that in your Autostart directory (Windows systems) or call BNC in a script below directory /etc/init.d (Unix/Linux/Mac systems).
See BNC's command line option -nw for an auto-start of BNC in 'no window' mode.
3.3.5 Raw Output File - optional
BNC can save all data coming in through various streams in the received order and format together in one single daily file. This is of importance i.e. when using the PPP option in offline mode where the contents of different streams carrying observations, orbit/clock correctors, and broadcast ephemeris are to be read from one file. Data will be saved in blocks in the received format seperated by ASCII records like (example):
2010-08-03T18:05:28 RTCM3EPH RTCM_3 67This example block header tells you that 67 bytes are saved in the data block following this record. The information in this block is encoded in RTCM Version 3.x format, comes from Mountpoint RTCM3EPH and was received at 18:05:29 UTC on 2010-08-03. BNC adds its own time stamps because a complete time reference may not be provided for all incoming observations and epochs.
Note that streams in a 'Raw output file' which shall later be used in an offline PPP calculation must all be encoded in the same format.
The default value for 'Raw output file (full path)' is an empty option field, meaning that BNC will not save raw data into a daily file.
Observations will be converted to RINEX if they come in either RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. BNC's RINEX Version 2 observation files generally contain C1, P1, L1, S1, C2, P2, L2 and S2 observations. RINEX Version 3 observation files generally contain the following observation types:
The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming in from various NTRIP broadcasters as well as via a plain UDP and a serial communication link. Decoder 'ZERO' has been selected for one stream to not convert its contents but save it in original format.
Figure: BNC translating incoming streams to 15 min RINEX Version 3 files.
RINEX file names are derived by BNC from the first 4 characters of the corresponding stream's mountpoint (4Char Station ID). For example, data from mountpoints FRANKFURT and WETTZELL will have hourly RINEX Observation files named
FRAN{ddd}{h}.{yy}O
WETT{ddd}{h}.{yy}O
where 'ddd' is the day of year, 'h' is a letter which corresponds to an hour long UTC time block and 'yy' is the year.
If there are more than one stream with identical 4Char Station ID (same first 4 characters for their mountpoints), the mountpoint strings are split into two sub-strings and both become part of the RINEX file name. For example, when simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX Observation files are named as
FRAN{ddd}{h}_KFURT.{yy}O
FRAN{ddd}{h}_CE.{yy}O.
If several streams show exactly the same mountpoint name (example: BRUS0 from www.euref-ip.net and BRUS0 from www.igs-ip.net), BNC adds an integer number to the file name leading i.e. to hourly RINEX Observation files like
BRUS{ddd}{h}_0.{yy}O
BRUS{ddd}{h}_1.{yy}O.
Note that RINEX file names for all intervals less than 1 hour follow the file name convention for 15 minutes RINEX Observation files i.e.
FRAN{ddd}{h}{mm}.{yy}O
where 'mm' is the starting minute within the hour.
Here you can specify the path to where the RINEX Observation files will be stored. If the specified directory does not exist, BNC will not create RINEX Observation files. Default value for 'Directory' is an empty option field, meaning that no RINEX Observation files will be written.
3.4.3 File Interval - mandatory if 'Directory' is set
Select the length of the RINEX Observation file generated. The default value is 15 minutes.
3.4.4 Sampling - mandatory if 'Directory' is set
Select the RINEX Observation sampling interval in seconds. A value of zero '0' tells BNC to store all received epochs into RINEX. This is the default value.
3.4.5 Skeleton Extension - optional
Whenever BNC starts generating RINEX Observation 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. A 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 of a public RINEX header skeleton file for the Brussels EPN station.
However, sometimes public RINEX header skeleton files are not available, its contents is not up to date, or you need to put additional/optional records in the RINEX header. For that BNC allows using personal skeleton files that contain the header records you would like to include. You can derive a personal RINEX header skeleton file from the information given in an up to date sitelog. A file in the RINEX Observations 'Directory' with a 'Skeleton extension' suffix is interpreted by BNC as a personal RINEX header skeleton file for the corresponding stream.
Examples for personal skeleton file name convention: RINEX Observation files for mountpoints WETTZELL, FRANKFURT and FRANCE (same 4Char Station ID), BRUS0 from www.euref-ip.net and BRUS0 from www.igs-ip.net (same 4Char Station ID, identical mountpoint stings) would accept personal skeleton files named
WETT.skl
FRAN_KFURT.skl
FRAN_CE.skl
BRUS_0.skl
BRUS_1.skl
if 'Skeleton extension' is set to 'skl'.
Note the following regulations regarding personal RINEX header skeleton files:
If neither a public nor a personal RINEX header skeleton file is available for BNC, a default header will be used.
Whenever a RINEX Observation file is saved, you might want to compress, copy or upload it immediately via FTP. BNC allows you to execute a script/batch file to carry out these operations. To do that specify the full path of the script/batch file here. BNC will pass the RINEX Observation file path to the script as a command line parameter (%1 on Windows systems, $1 on Unix/Linux/Mac systems).
The triggering event for calling the script or batch file is the end of a RINEX Observation file 'Interval'. If that is overridden by a stream outage, the triggering event is the stream reconnection.
As an alternative to initiating file uploads through BNC, you may like to call an upload script or batch file through your crontable or Task Scheduler (independent from BNC) once every 2 or 3 minutes after the end of each RINEX file 'Interval'.
The default format for RINEX Observation files is RINEX Version 2.11. Select 'Version 3' if you would like to save observations in RINEX Version 3 format.
Broadcast ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3.x as message types 1019 (GPS) or 1020 (GLONASS) or 1045 (Galileo) or via RTIGS records type 300. The file name convention follows the details given in section 'RINEX File Names' except that the first four characters are 'BRDC' and the last character is
Note that streams dedicated to carry Broadacst Ephemeris messages in RTCM v3 format in high repetition rates are listed on http://igs.bkg.bund.de/ntrip/ephemeris.
Specify the path for saving broadcast ephemeris data as RINEX Navigation files. If the specified directory does not exist, BNC will not create RINEX Navigation files. Default value for Ephemeris 'Directory' is an empty option field, meaning that no RINEX Navigation files will be created.
3.5.2 Interval - mandatory if 'Directory' is set
Select the length of the RINEX Navigation file generated. The default value is 1 day.
BNC can output broadcast ephemeris in RINEX Version 3 ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. This function is introduced in order to support i.e. the 'BKG Ntrip Sate Space Server' (BNS) which transforms IGS clocks and orbits into corrections to broadcast ephemeris. Specify an IP port number to activate this function. The default is an empty option field, meaning that no ASCII ephemeris output via IP port is generated.
The source code for BNC comes with an example perl script 'test_bnc_eph.pl' that allows you to read BNC's ASCII ephemeris output from the IP port.
Default format for RINEX Navigation files containing broadcast ephemeris is RINEX Version 2.11. Select 'Version 3' if you want to save the ephemeris in RINEX Version 3 format.
Note that this does not concern the broadcast ephemeris output through IP port which is always in RINEX Version 3 format.
RTCM is in the process of developing new Version 3 messages to transport satellite clock and orbit corrections in real-time. Based on the latest available proposal, the following premature so-called 'State Space Representation' (SSR) messages currently under discussion have been implemented in BNC. The information below should not be misunderstood as a programmers guide. Programming efforts would definitely require access to the RTCM documentation of SSR messages.
RTCM Version 3 streams carrying these messages may be used i.e. to support real-time Precise Point Positioning (PPP) applications.
When using clocks from Broadcast Ephemeris (with or without applied corrections) or clocks from SP3 files, it may be important to understand that they are not corrected for the conventional periodic relativistic effect. Chapter 10 of the IERS Conventions 2003 mentions that the conventional periodic relativistic correction to the satellite clock (to be added to the broadcast clock) is computed as dt = -2 (R * V) / c^2 where R * V is the scalar product of the satellite position and velocity and c is the speed of light. This can also be found in the GPS Interface Specification, IS-GPS-200, Revision D, 7 March 2006.
Orbit corrections are provided in along-track, cross-track and radial components. These components are defined in the Earth-centered, Earth-fixed reference frame of the broadcast ephemerides. For an observer in this frame, the along-track component is aligned in both direction and sign with the velocity vector, the cross-track component is perpendicular to the plane defined by the satellite position and velocity vectors, and the radial direction is perpendicular to the along track and cross-track ones. The three components form a right-handed orthogonal system.
After applying corrections, the satellite position and clock is referred to the 'ionospheric free' phase center of the antenna which is compatible with the broadcast orbit reference.
The orbit and clock corrections do not include local effects (like Ocean Loading or Solid Earth Tides) or atmospheric effects (Ionosphere and/or troposphere). Depending on the accuracy of your application you should correct for such effects by other means. There is currently no RTCM SSR message for ionospheric state parameters. Such messages are needed for accurate single frequency applications. The development of Iono messages will be the next step in the schedule of the RTCM State Space Representation Working Group.
Broadcast Corrections can be saved by BNC in files. The file name convention for Broadcast Correction files follows the convention for RINEX files except for the last character of the file name suffix which is set to "C".
Saved files contain blocks of records in plain ASCII format where - separate for GPS, GLONASS, message types, streams, and epochs - the begin of a block is indicated by a line like (examples):
! Orbits/Clocks: 30 GPS 0 Glonass CLK11
or
! Orbits/Clocks: 0 GPS 19 Glonass CLK11
Such line informs you about the number of records (here 30 and 19) carrying GPS or GLONASS related parameters you should receive next as part of a certain stream.
The first five parameters in each broadcast corrections record are:
In case of RTCM message types 1057 or 1063 these parameters are followed by
Undefined parameters are set to zero "0.000".
Example:
... 1057 0 1538 211151.0 G18 1 0.034 0.011 -0.064 0.000 0.000 0.000 1057 0 1538 211151.0 G16 33 -0.005 0.194 -0.091 0.000 0.000 0.000 1057 0 1538 211151.0 G22 50 0.008 -0.082 -0.001 0.000 0.000 0.000 ... 1063 0 1538 211151.0 R09 111 -0.011 -0.014 0.005 0.000 0.000 0.000 1063 0 1538 211151.0 R10 43 0.000 -0.009 -0.002 0.000 0.000 0.000 1063 0 1538 211151.0 R21 75 -0.029 0.108 0.107 0.000 0.000 0.000 ...
In case of RTCM message types 1058 or 1064 the first five parameters are followed by
... 1058 0 1538 211151.0 G18 0 1.846 0.000 0.000 1058 0 1538 211151.0 G16 0 0.376 0.000 0.000 1058 0 1538 211151.0 G22 0 2.727 0.000 0.000 ... 1064 0 1538 211151.0 R08 0 8.956 0.000 0.000 1064 0 1538 211151.0 R07 0 14.457 0.000 0.000 1064 0 1538 211151.0 R23 0 6.436 0.000 0.000 ...
In case of RTCM message types 1060 or 1066 the first five parameters are followed by
... 1060 0 1538 211610.0 G30 82 2.533 0.635 -0.359 -0.598 0.000 0.000 0.000 0.000 0.000 1060 0 1538 211610.0 G31 5 -4.218 -0.208 0.022 0.002 0.000 0.000 0.000 0.000 0.000 1060 0 1538 211610.0 G32 28 -2.326 0.977 -0.576 0.142 0.000 0.000 0.000 0.000 0.000 ... 1066 0 1538 211610.0 R22 27 1.585 2.024 2.615 -2.080 0.000 0.000 0.000 0.000 0.000 1066 0 1538 211610.0 R23 27 6.277 2.853 4.181 1.304 0.000 0.000 0.000 0.000 0.000 1066 0 1538 211610.0 R24 27 0.846 1.805 13.095 6.102 0.000 0.000 0.000 0.000 0.000 ...
In case of RTCM message types 1059 or 1065 the first five parameters are followed by
... 1059 0 1538 211151.0 G18 2 0 -0.010 11 -0.750 1059 0 1538 211151.0 G16 2 0 -0.040 11 -0.430 1059 0 1538 211151.0 G22 2 0 -0.630 11 -2.400 ...
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' 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.
The output format equals the format used for saving Broadcast Corrections in a file with the exception that the Mountpoint is added at each line's end.
The following is an example output for streams from Mountpoints RTCMSSR, CLK10 and CLK11:
... 1057 0 1538 211151.0 G18 1 0.034 0.011 -0.064 0.000 0.000 0.000 RTCMSSR 1057 0 1538 211151.0 G16 33 -0.005 0.194 -0.091 0.000 0.000 0.000 RTCMSSR 1057 0 1538 211151.0 G22 50 0.008 -0.082 -0.001 0.000 0.000 0.000 RTCMSSR ... 1058 0 1538 211151.0 G18 0 1.846 0.000 RTCMSSR 1058 0 1538 211151.0 G16 0 0.376 0.000 RTCMSSR 1058 0 1538 211151.0 G22 0 2.727 0.000 RTCMSSR ... 1059 0 1538 211151.0 G18 2 0 -0.010 11 -0.750 RTCMSSR 1059 0 1538 211151.0 G16 2 0 -0.040 11 -0.430 RTCMSSR 1059 0 1538 211151.0 G22 2 0 -0.630 11 -2.400 RTCMSSR ... 1063 0 1538 211151.0 R09 111 -0.011 -0.014 0.005 0.0000 0.000 0.000 RTCMSSR 1063 0 1538 211151.0 R10 43 0.000 -0.009 -0.002 0.0000 0.000 0.000 RTCMSSR 1063 0 1538 211151.0 R21 75 -0.029 0.108 0.107 0.0000 0.000 0.000 RTCMSSR ... 1064 0 1538 211151.0 R08 0 8.956 0.000 RTCMSSR 1064 0 1538 211151.0 R07 0 14.457 0.000 RTCMSSR 1064 0 1538 211151.0 R23 0 6.436 0.000 RTCMSSR ... 1066 0 1538 211610.0 R24 27 0.846 1.805 13.095 6.102 0.000 0.000 0.000 0.000 0.000 CLK11 1066 0 1538 211610.0 R23 27 6.277 2.853 4.181 1.304 0.000 0.000 0.000 0.000 0.000 CLK11 1066 0 1538 211610.0 R22 27 1.585 2.024 2.615 -2.080 0.000 0.000 0.000 0.000 0.000 CLK11 ... 1060 0 1538 211610.0 G32 28 -2.326 0.977 -0.576 0.142 0.000 0.000 0.000 0.000 0.000 CLK10 1060 0 1538 211610.0 G31 5 -4.218 -0.208 0.022 0.002 0.000 0.000 0.000 0.000 0.000 CLK10 1060 0 1538 211610.0 G30 82 2.533 0.635 -0.359 -0.598 0.000 0.000 0.000 0.000 0.000 CLK10 ...
The source code for BNC comes with an example perl script 'test_bnc_eph.pl' that allows you to read BNC's Broadcast Corrections from the IP port.
3.6.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.
BNC can generate synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed a real-time GNSS network engine. The output can be produced in a binary format through an IP port and/or a plain ASCII format to save the observations in a local file. Following StationID, GPSWeek, GPSWeekSeconds and SV-PRN it comprises the following observations where available:
The binary output is a continuous stream in the following order:
begEpoch t_obsInternal t_obsInternal ... t_obsInternal endEpoch begEpoch t_obsInternal ...
The corresponding structures are defined as follow:
const char begEpoch[] = "BEGEPOCH"; const char endEpoch[] = "ENDEPOCH"; ... ... class t_obsInternal { public: int flags; char StatID[20+1]; // Station ID char satSys; // Satellite System ('G' for GPS or 'R' for GLONASS or 'S' for Geostationary signal payload) int satNum; // Satellite Number (PRN for GPS NAVSTAR) int slot; // Slot Number (for Glonass) int GPSWeek; // Week of GPS-Time double GPSWeeks; // Second of Week (GPS-Time) double C1; // CA-code pseudorange (meters) double C2; // CA-code pseudorange (meters) double P1; // P1-code pseudorange (meters) double P2; // P2-code pseudorange (meters) double L1; // L1 carrier phase (cycles) double L2; // L2 carrier phase (cycles) int slip_cnt_L1; // L1 cumulative loss of continuity indicator (negative value = undefined) int slip_cnt_L2; // L2 cumulative loss of continuity indicator (negative value = undefined) int lock_timei_L1; // L1 last lock time indicator (negative value = undefined) int lock_timei_L2; // L2 last lock time indicator (negative value = undefined) double S1; // L1 signal-to noise ratio double S2; // L2 signal-to noise ratio int SNR1; // L1 signal-to noise ratio (mapped to integer) int SNR2; // L2 signal-to noise ratio (mapped to integer) };
The source code for BNC comes with an example program called 'test_bnc_qt.cpp' that allows you to read BNC's (synchronized or unsynchronized) binary observation output from the IP port and print the observations in a plain ASCII format on standard output.
Note that any socket connection of an application to BNC's synchronized or unsynchronized observations ports is recorded in the 'Log' tab on the bottom of the main window together with a connection counter, resulting in log records like 'New client connection on sync/usync port: # 1'.
The following figure shows the screenshot of a BNC configuration where a number if streams is pulled from different NTRIP broadcasters to feed a GNSS engine via IP port output.
Figure: Synchronized BNC output via IP port to feed a GNSS real-time engine.
BNC can produce synchronized observations in binary 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
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.
Note that 'Wait for full epoch' does not effect the RINEX Observation file content. Observations received later than 'Wait for full epoch' seconds will still be included in the RINEX Observation files.
3.7.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.
Beware that the size of this file can rapidly increase depending on the number of incoming streams. This option is primarily meant for testing and evaluation.
3.7.5 Port (unsynchronized) - optional
BNC can produce unsynchronized observations from all configured streams in binary 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.
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.
When selecting the serial communication options listed below, make sure that you pick those configured to the serial connected receiver.
3.8.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
Windows: COM1, COM2 Linux: /dev/ttyS0, /dev/ttyS1 FreeBSD: /dev/ttyd0, /dev/ttyd1 Digital Unix: /dev/tty01, /dev/tty02 HP-UX: /dev/tty1p0, /dev/tty2p0 SGI/IRIX: /dev/ttyf1, /dev/ttyf2 SunOS/Solaris: /dev/ttya, /dev/ttyb
Note that you must plug a serial cable in the port defined here before you start BNC.
3.8.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
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
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
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
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
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.
Forwarding valid NMEA-GGA messages to the NTRIP broadcaster is required for receiving 'Virtual Reference Station' (VRS) streams. Thus, in case your serial connected receiver is not capable to provide them, the alternative for VRS streams is a 'Manual' simulation of an initial NMEA-GGA message. Its contents is based on the approximate (editable) latitude/longitude from the broadcaster's source-table and an approximate VRS height to be specified.
In summary: select 'Manual' only when handling a VRS stream and your serial connected GNSS receiver doesn't generate NMEA-GGA messages. Select 'Auto' otherwise.
3.8.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
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.
This option concerns only 'Virtual Reference Stations' (VRS). Its setting is ignored in case of streams coming from physical reference stations.
At various times, the incoming stream might become unavailable or corrupted. In such cases, it is important that the BNC operator and/or the stream providers become aware of the situation so that necessary measures can be taken to restore the stream. Furthermore, continuous attempts to decode corrupted stream(s) can generate unnecessary workload for BNC. Outages and corruptions are handled by BNC as follows:
Stream outages: BNC considers a connection to be broken when there are no incoming data detected for more than 20 seconds. When this occurs, BNC will attempt to reconnect at a decreasing rate. It will first try to reconnect with 1 second delay, and again in 2 seconds if the previous attempt failed. If the attempt is still unsuccessful, it will try to reconnect within 4 seconds after the previous attempt and so on. The wait time doubles each time with a maximum wait time of 256 seconds.
Stream corruption: Not all bits chunk transfers to BNC's internal decoders return valid observations. Sometimes several chunks might be needed before the next observation can be properly decoded. BNC buffers all the outputs (both valid and invalid) from the decoder for a short time span (size derived from the expected 'Observation rate') and then determines whether a stream is valid or corrupted.
Outage and corruption events are reported in the 'Log' tab. They can also be passed on as parameters to a shell script or batch file to generate an advisory note to BNC operator or affected stream providers. This functionality lets users utilize BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations.
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
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.
Note that specifying a value of zero '0' for the 'Failure threshold' will force BNC to report any stream failure immediately. Note also that for using this function you need to specify the 'Observation rate'.
3.9.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.
Note that specifying a value of zero '0' for the 'Recovery threshold' will force BNC to report any stream recovery immediately. Note also that for using this function you need to specify the 'Observation rate'.
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.
Leave the 'Script' field empty if you do not wish to use this option. An invalid path will also disable this option.
Examples for command line parameter strings passed on to the advisory 'Script' are:
FFMJ0 Begin_Outage 08-02-21 09:25:59 FFMJ0 End_Outage 08-02-21 11:36:02 Begin was 08-02-21 09:25:59Sample script for Unix/Linux/Mac systems:
#!/bin/bash sleep $((60*RANDOM/32767)) cat | mail -s "NABU: $1" email@address <<! Advisory Note to BNC User, Please note the following advisory received from BNC. Stream: $* Regards, BNC !
Note the sleep command in this script which causes the system to wait for a random period of up to 60 seconds before sending the email. This should avoids overloading your mail server in case of a simultaneous failure of many streams.
This section describes a number of miscellaneous options which can be applied for a single stream (mountpoint) or for all configured streams.
The following figure shows RTCM message numbers contained in stream 'CONZ0' and the message latencies recorded every 10 seconds.
Figure: RTCM message numbers and latencies.
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.
Latency: Latency is defined in BNC by the following equation:
UTC time provided by BNC's host - GPS time of currently processed epoch + Leap seconds between UTC and GPS time -------------- = Latency
Statistics: BNC counts the number of GPS seconds covered by at least one observation. It also estimates an observation rate (independent from the a priory specified 'Observation rate') from all observations received throughout the first full 'Log latency' interval. Based on this rate, BNC estimates the number of data gaps when appearing in subsequent intervals.
Latencies of observations or corrections to Broadcast Ephemeris and statistical information can be recorded in the 'Log' tab at the end of each 'Log latency' interval. A typical output from a 1 hour 'Log latency' interval would be:
08-03-17 15:59:47 BRUS0: Mean latency 1.47 sec, min 0.66, max 3.02, rms 0.35, 3585 epochs, 15 gaps
Select a 'Log latency' interval to activate this function or select the empty option field if you do not want BNC to log latencies and statistical information.
When configuring a GNSS receiver for RTCM stream generation, the 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.
Tick 'Scan RTCM' to scan RTCM Version 2.x or 3.x streams and log all contained
Note that in RTCM Version 2.x the message types 18 and 19 carry only the observables of one frequency. Hence it needs two type 18 and 19 messages per epoch to transport the observations from dual frequency receivers.
Logged time stamps refer to message reception time and allow to understand repetition rates. Enter 'ALL' if you want to log this information from all configured streams. Beware that the size of the logfile can rapidly increase depending on the number of incoming RTCM streams.
This option is primarily meant for testing and evaluation. Use it to figure out what exactly is produced by a specific GNSS receiver's configuration. An empty option field (default) means that you don't want BNC to print the message type numbers and antenna information carried in RTCM streams.
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 requires pulling in addition
The following figure provides the screenshot of an example PPP session with BNC.
Figure: Precise Point Positioning (PPP) with BNC.
PPP results are shown in the 'Log' tab on the bottom of BNC's main window. Depending on the processing options, the following values are shown about once per second (example):
10-09-08 09:14:06 FFMJ1 PPP 09:14:04.0 12 4053457.429 +- 2.323 617730.551 +- 1.630 4869395.266 +- 2.951
The 'PPP' string in that is followed by the selected mounpoint, a PPP time stamp in GPS Time, the number of processed satellites, and XYZ coordinates with their formal errors as derived from the implemented filter in [m]. The implemented algorithm includes an outlier and cycle slip detection. The maximum for accepted residuals is hard coded to 10 meters for code observations and 10 centimeters for phase observations.
More detailed PPP results are saved in BNC's logfile. Depending on the selected processing options you find
10-08-09 06:04:11 Single Point Positioning of Epoch 06:04:09.0 -------------------------------------------------------------- residuals code 0.386 0.175 -0.378 0.032 -0.103 -2.409 -0.488 -0.576 residuals phase -0.007 -0.001 0.002 0.002 -0.007 -0.005 0.006 0.007 residuals glo 0.015 -0.004 0.006 clk = 68260.392 +- 1.353 trp = 2.331 -0.006 +- 0.100 amb G02 = -0.974 +- 0.809 amb G10 = 3.250 +- 0.720 amb G26 = -5.192 +- 0.911 amb G28 = -0.741 +- 0.909 amb G08 = 1.317 +- 0.719 amb G05 = -1.928 +- 0.742 amb G07 = 4.887 +- 0.853 amb G13 = -1.190 +- 1.221 amb R07 = -145.700 +- 0.717 amb R08 = -140.476 +- 0.939 amb R10 = -128.820 +- 0.710
Note that BNC's 'PPP Client' option can also be used in 'Offline Mode'. Apply the 'Offline Mode' command line options for that to read a file containing synchronized observations, orbit and clock corretors, and broadcast ephemeris. Such a file can be generated using BNC's 'Raw output file' option. The first five characters of the file name read in 'Offline Mode' must then be the same as the specified PPP 'Mounpoint': If you produce a 'Raw output file' named 'FFMJ1' then the PPP 'Mountpoint' needs to be also specified as 'FFMJ1' and the command line to execute BNC on a Windows system in 'Offline Mode' could look like:
bnc.exe --conf c:\temp\BNC.ppp --file c:\temp\FFMJ1 --format RTCM_3
Streams in a 'Raw output file' which shall later be used in an offline PPP calculation must all be encoded in the same format.
When using the PPP option, it is important to understand which effects are corrected by BNC.
Specify a mountpoint if you want BNC to derive coordinates for the affected rover position through a Point Positioning solution.
Furthermore, specify the Point Positioning method you want to apply. Options are
Enter the reference coordinate components X,Y,Z of the receiver's position in meters if known. Default are empty option fields, meaning that the antenna's XYZ position is unknown.
Once XYZ coordinate components are defined, the 'PPP' line in BNC's logfile is extended by Nort, East and Up desplacements to (example):
10-08-09 06:01:56 FFMJ1 PPP 06:02:09.0 11 4053457.628 +- 2.639 617729.438 +- 1.180 4869396.447 +- 1.921 NEU -0.908 -0.571 1.629
The parameters following the 'NEU' string provide Nort, East and Up components of the current coordinate displacement in meters.
BNC allows to use different Point Positioning processing options depending on the capability of the involved receiver and the application in mind.3.11.2.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.2.2 Estimate Tropo - optional
BNC estimates the tropospheric delay according to equation
T(z) = T_apr(z) + dT / cos(z)where T_apr is the a-priori tropospheric delay derived from Saastamoinen model.
By default BNC does not estimate troposphere parameters. Tick 'Estimate tropo' to estimate troposphere parameters together with the coordinates and save T_apr and dT in BNC's log file.
3.11.2.3 Use GLONASS - optional
By default BNC does not process GLONASS observations when in Point Positioning mode. Tick 'Use GLONASS' to use GPS and GLONASS observations for estimating coordinates in Point Positioning mode.
PPP time series of North (red), East(green) and Up (blue) coordinate components will be plotted in the 'PPP Plot' tab when this option 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.
Note that a PPP time series makes only sense for a stationary operated receiver.
You may want to introduce specific sigmas for code and phase observations. You may also like to carry out your PPP solution in Quick-Start mode or output averaged position values.
3.11.3.1 Sigma Code/Phase - 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 5.0 m for code observations and a sigma of 0.02 m for phase observations (defauls) is 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 of 5.0 m and 0.02 m respectively.
3.11.3.2 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.
This so-called Quick-Start option allows the PPP solutions to rapidly converge after startup. It requires that the antenna remains unmoved on the know position throughout the defined period. A value of 120 (default) is likely to be an appropriate choice for 'Quick-Start'
You may need to create your own reference coordinate through running BNC for an hour in normal mode before applying the Quick-Start option.
Figure: BNC in 'Quick-Start - Static' mode
3.11.3.3 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:
10-09-08 09:13:05 FFMJ1 AVE-XYZ 09:13:04.0 4053455.948 +- 0.284 617730.422 +- 0.504 4869397.692 +- 0.089 10-09-08 09:13:05 FFMJ1 AVE-NEU 09:13:04.0 1.043 +- 0.179 0.640 +- 0.456 1.624 +- 0.331 10-09-08 09:13:05 FFMJ1 AVE-TRP 09:13:04.0 2.336 +- 0.002
Entering any positive value up to 1440 (24h mean value) is allowed. An empty option field (default) means that you don't want BNC to output moving average positions into the log file and the 'Log' section. Note that averaging positions makes only sense for a stationary receiver.
You may like to introduce specific estimates for sigmas of parameters to be estimated in the PPP solution.
Enter a sigma in meters for the initial XYZ coordinate componentes. A value of 100.0 may be an appropriate choice. However, this value may be significantly smaller (i.e. 0.01) when starting from a station with a known XYZ position.
3.11.4.2 XYZ White Noise - mandatory
Enter a sigma in meters for the 'White Noise' of estimated XYZ coordinate components. A value of 100.0 may be appropriate considering the potential movement of a rover position.
3.11.4.3 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.4.4 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 1e-6 (default) would mean that the tropospheric effect may vary for 3600 * 1e-6 = 0.0036 meters per hour.
BNC allows to output results from Precise Point Positioning in NMEA format. The NMEA sentences generated about once per second are pairs of
Note that Tomoji Takasu has written a Windows program called RTKPlot for visualizing NMEA strings. It is available from http://gpspp.sakura.ne.jp/rtklib/rtklib.htm and compatible with the NMEA output of BNC's PPP option.
Specify the full path to a file where Point Positioning results are saved as NMEA messages. The generated NMEA file begins with a single GPRMC message which carries only date and time information. The default value for 'File (full path)' is an empty option field, meaning that BNC will not saved NMEA messages into a file.
Specify the IP port number of a local port where Point Positioning results become available as NMEA messages. The default value for '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.
NASA's 'World Wind' software (see http://worldwindcentral.com/wiki/NASA_World_Wind_Download) can be used for real-time visualization of positions provided through BNC's NMEA IP output port. You need the 'GPS Tracker' plug-in available from http://worldwindcentral.com/wiki/GPS_Tracker for that. The 'Word Wind' is not meant for showing centimeter level details.
Each stream on an NTRIP broadcaster (and consequently on BNC) is defined using a unique source ID called mountpoint. An NTRIP client like BNC access the desired data 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.
Streams selected for retrieval are listed under the 'Streams' canvas section on BNC's main window. The list provides the following information either extracted from source-table(s) produced by the NTRIP broadcasters or introduced by BNC's user:
'resource loader' | NTRIP broadcaster URL and port, or TCP/IP host and port, or UDP port, or Serial input port specification. |
'mountpoint' | Mountpoint introduced by NTRIP broadcaster, or Mountpoint introduced by BNC's user. |
'decoder' | Type of decoder used to handle the incoming stream content according to its format; editable. |
'lat' | Approximate latitude of reference station, in degrees, north; editable if 'nmea' = 'yes'. |
'long' | Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'. |
'nmea' | Indicates whether or not streaming needs to be initiated by BNC through sending NMEA-GGA message carrying position coordinates in 'lat' and 'long'. |
'ntrip' | Selected NTRIP transport protocol version (1, 2, R, or U), or 'N' for TCP/IP streams without NTRIP, or 'UN' for UDP streams without NTRIP, or 'S' for serial input streams without NTRIP. |
'bytes' | Number of bytes received. |
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.12.3 Reconfigure Streams On-the-fly
The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process.
Window mode: Hit 'Save & Reread Configuration' while BNC is in window mode and already processing data to let changes of your streams selection immediately become effective.
No window mode: When operating BNC online in 'no window' mode (command line option -nw), you force BNC to reread its 'mountPoints' configuration option from disk at pre-defined intervals. Select '1 min', '1 hour', or '1 day' as 'Reread configuration' option to reread the 'mountPoints' option every full minute, hour, or day. This lets a 'mountPoints' option edited in between in the configuration file become effective without terminating uninvolved threads. See annexed section 'Configuration Example' for a configuration file example and a list of other on-the-fly changeable options.
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 consumtion, 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 the bandwidth comsumption of incoming streams.
Figure: 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 the latency of incoming streams.
Figure: 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 coordiate components.
Figure: 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.
Figure: Steam input communication links.
3.14.1 Add Stream - Coming from Caster
Button 'Add Stream' > 'Coming from Caster' then opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints.
3.14.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 and http://www.igs-ip.net/home and http://www.products.igs-ip.net/home.
3.14.1.2 Casters Table - optional
It may be that your 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 to select a broadcaster for stream retrieval, see figure below.
Figure: Casters table.
3.14.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 on www.euref-ip.net or www.igs-ip.net or products.igs-ip.net.
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.x, RTCM Version 3.x, or RTIGS format. For access to observations, ephemeris or ephemris correctiors, an RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while an RTCM Version 3.x streams must contain
The contents of data field 'nmea' tells you whether a stream retrieval needs to be initiated by BNC through sending an NMEA-GGA message carrying approximate position coordinates (virtual reference station).
Hit 'OK' to return to the main window. If you wish you can click on 'Add Stream' and repeat the process again to retrieve streams from different casters.
Figure: Broadcaster source-table.
3.14.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:
1: NTRIP version 1, TCP/IP.
2: NTRIP version 2 in TCP/IP mode.
R: NTRIP version 2 in RTSP/RTP mode.
U: NTRIP version 2 in UDP mode.
If NTRIP version 2 is supported by the broadcaster:
Select option '1' if you are not sure whether the broadcaster supports NTRIP version 2.
3.14.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:
Streams directly received from a TCP/IP port show up with an 'N' for 'No NTRIP' in the 'Streams' canvas section on BNC's main window . Latitude and longitude are to be entered just for informal reasons.
Note that this option works only if no proxy server is involved in the communication link.
3.14.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:
Streams directly received at a UDP port show up with a 'UN' for 'UDP, No NTRIP' in the 'Streams' canvas section on BNC's main window . Latitude and longitude are to be entered just for informal reasons.
3.14.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:
Windows: COM1, COM2 Linux: /dev/ttyS0, /dev/ttyS1 FreeBSD: /dev/ttyd0, /dev/ttyd1 Digital Unix: /dev/tty01, /dev/tty02 HP-UX: /dev/tty1p0, /dev/tty2p0 SGI/IRIX: /dev/ttyf1, /dev/ttyf2 SunOS/Solaris: /dev/ttya, /dev/ttyb
When selecting the serial communication options listed above, make sure that you pick those configured to the serial connected GNSS receiver.
Streams received from a serial connected GNSS receiver show up with an 'S' (for Serial Port, no NTRIP) in the 'Streams' canvas section on BNC's main window . Latitude and longitude are to be entered just for informal reasons.
The following figure shows a BNC example setup for pulling a stream via serial port on a Linux operating system.
Figure: BNC setup for pulling a stream via serial port.
Hit 'Start' to start retrieving, decoding, and 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 from a file in offline mode. BNC will then use processing options from the 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.ini'.
3.15.1 No Window Mode - optional
Apart from its regular windows mode, BNC can be started on all systems as a background/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.
Example:
bnc.exe -nw
3.15.2 Offline Mode - optional
Although BNC is primarily a real-time online tool, it can be run in offline mode to read data from a previously saved file for post-processing purposes. Enter the following command line options for that:
Example:
./bnc --file FFMJ.dat --format RTCM_3
Note that when running BNC in offline mode, it will use options for file saving, interval, sampling, PPP etc. from its configuration file. Note further that only those data in the file will be processd offline which are encoded as specified with the --format option.
3.15.3 Configuration File - optional
Example:
./bnc --conf MyConfig.ini
This leads to a BNC job using configuration file 'MyConfig.ini'. The configuration file will be saved in the current working directory.
On a Mac-OS X v10.6 (or higher) system the command line would be
open -a /Applications/bnc.app --args -conf /Users/tsyan/MyConfig.ini
if the program is in /Applications and the configuration file 'MyConfig.ini' in /Users/tsyan.
The BKG Ntrip Client (BNC) Qt Graphic User Interface (GUI) has been developed for the Federal Agency for Cartography and Geodesy (BKG) by Leos Mervart, Czech Technical University Prague, Department of Geodesy. BNC includes the following GNU GPL software components:
Georg Weber
Federal Agency for Cartography and Geodesy (BKG)
Frankfurt, Germany
[euref-ip@bkg.bund.de] or [igs-ip@bkg.bund.de]
Acknowledgements
BNC's Help Contents has been proofread by Thomas Yan, University of New South Wales, Australia.
Scott Glazier, OmniSTAR Australia, included the decoding of broadcast ephemeris from RTIGS streams and has been helpful in finding BNC's bugs.
James Perlt, BKG, helped fixing bugs and redesigned BNC's main window.
Andre Hauschild, German Space Operations Center, DLR, revised the RTCMv2 decoder.
Zdenek Lukes, Czech Technical University Prague, Department of Geodesy, extended the RTCMv2 decoder to handle message types 3, 20, 21, and 22 and added loss of lock indicator.
Jan Dousa, Geodetic Observatory Pecny, Czech Republic, provided a tool for drawing stream distribution maps and also helped with fixing bugs.
6.1. Revision History
6.2. RTCM
6.2.1 NTRIP Version 1
6.2.2 NTRIP Version 2
6.2.3 RTCM Version 2.x
6.2.4 RTCM Version 3.x
6.3. RTIGS
6.3.1 SOC
6.4. Configuration Example
6.5. Links
Dec 2006 | Version 1.0b | [Add] First Beta Binaries published based on Qt 4.2.3. |
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' [Add] HTTP Host directive for skeleton file download [Add] Percent encoding for user IDs and passwords [Bug] Exit execution of calling thread for RTCM3 streams [Bug] Signal-slot mechanism for threads |
May 2007 | Version 1.3 | [Add] Source code published. |
Jul 2007 | Version 1.4 | [Bug] Skip messages from proxy server [Bug] Call RINEX script through 'nohup' |
Apr 2008 | Version 1.5 | [Add] Handle ephemeris from RTCM Version 3.x streams [Add] Upgrade to Qt Version 4.3.2 [Add] Optional RINEX v3 output [Add] SBAS support [Bug] RINEX skeleton download following stream outage [Add] Handle ephemeris from RTIGS streams [Add] Monitor stream failure/recovery and latency [Mod] Redesign of main window [Bug] Freezing of About window on Mac systems [Bug] Fixed problem with PRN 32 in RTCMv2 decoder [Bug] Fix for Trimble 4000SSI receivers in RTCMv2 decoder [Mod] Major revision of input buffer in RTCMv2 decoder |
Dec 2008 | Version 1.6 | [Mod] Fill blanc columns in RINEXv3 with 0.000 [Add] RTCMv3 decoder for clock and orbit corrections [Add] Check RTCMv3 streams for incoming message types [Add] Decode RTCMv2 message types 3, 20, 21, and 22 [Add] Loss of lock and lock time indicator [Bug] Rounding error in RTCMv3 decoder concerning GLONASS height [Mod] Accept GLONASS in RTCMv3 when transmitted first [Add] Leap second 1 January 2009 [Add] Offline mode, read data from file [Add] Output antenna descriptor, coordinates and excentricities from RTCMv3 [Add] Reconfiguration on-the-fly [Mod] Binary output of synchronized observations [Add] Binary output of unsynchronized observations [Bug] Fixed problem with joined RTCMv3 blocks |
Dec 2008 | Version 1.6.1 | [Mod] HTTP GET when no proxy in front |
Nov 2009 | Version 1.7 | [Bug] RINEX navigation file format [Add] Upgrade to Qt Version 4.5.2 [Add] Support of NTRIP v2 [Add] Rover support via serial port [Add] Show broadcaster table from www.rtcm-ntrip.org [Add] Enable/disable tab widgets [Add] User defined configuration file name [Mod] Switch to configuration files in ini-Format [Add] Daily logfile rotation [Add] Read from TCP/IP port, by-pass NTRIP transport protocol [Add] Save NMEA messages coming from rover [Add] Auto start [Add] Drag and drop ini files [Add] Read from serial port, by-pass NTRIP transport protocol [Mod] Update of SSR messages following RTCM 091-2009-SC104-542 [Add] Read from UPD port, by-pass NTRIP transport protocol [Mod] Output format of Broadcast Corrections [Add] Throughput plot [Add] Latency plot |
Nov 2009 | Version 1.8 | [Mod] On-the-fly reconfiguration of latency and throughput plots |
Feb 2010 | Version 2.0 | [Mod] Change sign of Broadcast Ephemeris correctors [Add] Real-time PPP option |
Jun 2010 | Version 2.1 | [Bug] SSR GLONASS message generation [Add] PPP in post-processing mode [Mod] Update of SSR messages following draft dated 2010-04-12 [Mod] Generating error message when observation epoch is wrong |
Jul 2010 | Version 2.2 | [Bug] GLONASS ephemeris time |
Aug 2010 | Version 2.3 | [Mod] Internal format for saving raw streams [Bug] Outlier detection in GLONASS ambiguity resolution [Mod] Format of PPP logs in logfile [Bug] Complete acceleration terms for GLONASS ephemeris [Bug] Handling ephemeris IOD's in PPP mode |
Dec 2010 | Version 2.4 | [Add] Output of averaged positions when in PPP mode [Mod] Use always the latest received set of broadcast ephemeris [Add] QuickStart PPP option [Mod] Improvement of data sharing efficiency among different threads [Mod] Design of PPP tab section [Add] Sigmas for observations and parameters [Add] Stream distribution map |
The Radio Technical Commission for Maritime Services (RTCM) is an international non-profit scientific, professional and educational organization. Special Committees provide a forum in which governmental and non-governmental members work together to develop technical standards and consensus recommendations in regard to issues of particular concern. RTCM is engaged in the development of international standards for maritime radionavigation and radiocommunication systems. The output documents and reports prepared by RTCM Committees are published as RTCM Recommended Standards. Topics concerning Differential Global Navigation Satellite Systems (DGNSS) are handled by the Special Committee SC 104.
Personal copies of RTCM Recommended Standards can be ordered through http://www.rtcm.org/orderinfo.php.
'Networked Transport of RTCM via Internet Protocol' Version 1.0 (NTRIP) stands for an application-level protocol streaming Global Navigation Satellite System (GNSS) data over the Internet. NTRIP is a generic, stateless protocol based on the Hypertext Transfer Protocol HTTP/1.1. The HTTP objects are enhanced to GNSS data streams.
NTRIP Version 1.0 is an RTCM standard designed for disseminating differential correction data (e.g. in the RTCM-104 format) or other kinds of GNSS streaming data to stationary or mobile users over the Internet, allowing simultaneous PC, Laptop, PDA, or receiver connections to a broadcasting host. NTRIP supports wireless Internet access through Mobile IP Networks like GSM, GPRS, EDGE, or UMTS.
NTRIP is implemented in three system software components: NTRIP clients, NTRIP servers and NTRIP broadcasters. The NTRIP broadcaster is the actual HTTP server program whereas NTRIP client and NTRIP server are acting as HTTP clients.
NTRIP is an open none-proprietary protocol. Major characteristics of NTRIP's dissemination technique are:
The NTRIP broadcaster maintains a source-table containing information on available NTRIP streams, networks of NTRIP streams and NTRIP broadcasters. The source-table is sent to an NTRIP client on request. Source-table records are dedicated to one of the following: Data Streams (record type STR), Casters (record type CAS), or Networks of streams (record type NET).
Source-table records of type STR contain the following data fields: 'mountpoint', 'identifier', 'format', 'format-details', 'carrier', 'nav-system', 'network', 'country', 'latitude', 'longitude', 'nmea', 'solution', 'generator', 'compr-encryp', 'authentication', 'fee', 'bitrate', 'misc'.
Source-table records of type NET contain the following data fields: 'identifiey', 'operator', 'authentication', 'fee', 'web-net', 'web-str', 'web-reg', 'misc'.
Source-table records of type CAS contain the following data fields: 'host', 'port', 'identifier', 'operator', 'nmea', 'country', 'latitude', 'longitude', 'misc'.
The major changes of NTRIP version 2.0 compared to version 1.0 are:
NTRIP version 2 allows to either communicate in TCP/IP mode or in RTSP/RTP mode or in UDP mode whereas version 1 is limited to TCP/IP only.
Transmitting GNSS carrier phase data can be done through RTCM Version 2.x messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of some interest here are:
RTCM Version 3.x has been developed as a more efficient alternative to RTCM Version 2.x. Service providers and vendors have asked for a standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the Version 2 parity scheme was wasteful of bandwidth. Another complaint was that the parity is not independent from word to word. Still another was that even with so many bits devoted to parity, the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. The Version 3.x standard is intended to correct these weaknesses.
RTCM Version 3.x defines a number of message types. Messages that may be of interest here are:
The following are proposed 'Multiple Signal Messages' (MSM) under discussion for standardization:
The following are proposed 'State Space Representation' (SSR) messages under discussion for standardization:
RTIGS stands for a data format and transport protocol for GPS observations. It was defined by the Real-Time IGS Working Group (RTIGS WG). Its definition is based on the SOC format. Every RTIGS record has one of the following numbers:
Station record number 100
Observation record (O_T) number 200
Ephemeris record (E_T) number 300
Meteorological record (M_T) number 400
Every station has one of the following unique numbers:
1-99 reserved for JPL
100-199 reserved for NRCan
200-299 reserved for NGS
300-399 reserved for ESOC
400-499 reserved for GFZ
500-599 reserved for BKG
600-699 reserved for GEOSCIENCE AUS
700-799 others
etc
The number of bytes in each real time message includes the header as well as the data content, but NOT the pointer.
For example:
All records are related to a station configuration indicated by the Issue of Data Station (IODS). The IODS will enable the user to identify the equipment and software that was used to derive the observation data.
Each record header contains the GPS Time in seconds which flows continuously from 6 Jan-1980 onwards.
The data payload of each record consists of observations. The structures indicate a pointer to data but in fact the broadcast messages do not contain the pointer, only the data. Users will have to manage the data and the pointer is shown in order to illustrate where the data is located in the message and one possible data management option.
All record data are in network byte order (Big Endian), i.e. IA32 users have to swap bytes.
Visit http://igscb.jpl.nasa.gov/mail/igs-rtwg/2004/msg00001.html for further details.
The SOC format has been designed in July 1999 by the Jet Propulsion Laboratory (JPL) and the California Institute of Technology (CalTech) to transport 1Hz GPS data with minimal bandwidth over the open Internet. SOC follows the 'little-endian' byte order meaning that the low-order byte of a number is stored in memory at the lowest address, and the high-order byte at the highest address. Because the transport layer is UDP, the format does not include sync bits, a checksum, or cyclic redundancy checksum (CRC). SOC allows to transport the GPS observable CA, P1, P2, L1, and L2, efficiently compressed down to 14 bytes with 1 mm range resolution and 0.02 mm phase resolution. SOC contains epochs for cycle slips, a stand-alone time-tag per epoch, a minimum representation of the receiver's clock solution, 3 SNR numbers, a unique site id, a modulo 12 hour sequence number and flags for receiver type and GPS health. SOC's simple structure comprises an 8 byte header, a 9 byte overhead for timetag, number of gps, etc., plus 21 data bytes per gps.
Visit http://gipsy.jpl.nasa.gov/igdg/papers/SOC_FORMAT.ppt for further details.
The following table's left column is an example for the contents of a configuration file 'BNC.ini'. It enables the retrieval of stream ACOR0 form www.euref-ip.net for the generation of 15 min RINEX files. RINEX files are uploaded to an archive using script 'up2archive' :
Option | Affiliation |
[General] | Settings: Group |
adviseFail=15 | Outages: Failure threshold |
adviseReco=5 | Outages: Recovery threshold |
adviseScript= | Outages: Script (full path) |
autoStart=0 | General: Auto start |
binSample=0 | Feed Engine: Sampling |
casterUrlList=http://user:pass@euref-ip:2101 | Internal memory: Visited URLs |
corrIntr=1 day | Broadcast Corrections: Interval |
corrPath= | Broadcast Corrections: Directory |
corrPort= | Broadcast Corrections: Port |
corrTime=5 | Broadcast Corrections: Wait for full epoch |
ephIntr=15 min | RINEX Ephemeris: Interval |
ephPath= | RINEX Ephemeris: Directory |
ephV3=0 | RINEX Ephemeris: Version 3 |
font= | Internal memory: Used font |
logFile=/home/weber/bnc.log | General: Logfile (full path) |
rawOutFile= | General: Raw output file (full path) |
miscMount= | Miscellaneous: Mountpoint |
mountPoints=//user:pass@www.euref-ip.net:2101 /ACOR0 RTCM_2.3 43.36 351.60 no 1 | Streams: broadcaster:port/mountpoint |
ntripVersion=1 | Add Stream: NTRIP Version |
obsRate= | Outages: Observation rate |
onTheFlyInterval=1 day | General: Reread configuration |
outEphPort= | RINEX Ephemeris: Port |
outFile= | Feed Engine: File (full path) |
outPort= | Feed Engine: Port |
outUPort= | Feed Engine: Port (unsynchronized) |
perfIntr= | Miscellaneous: Log latency |
proxyHost= | Proxy: Proxy host |
proxyPort= | Proxy: Proxy port |
rnxAppend=2 | General: Append files |
rnxIntr=15 min | RINEX Observations: Interval |
rnxPath=/home/user/rinex | RINEX Observations: Directory |
rnxSample=0 | RINEX Observations: Sampling |
rnxScript=/home/user/rinex/up2archive | RINEX Observations: Script (full path) |
rnxSkel= | RINEX Observations: Skeleton extension |
rnxV3=0 | RINEX Observation: Version 3 |
scanRTCM=0 | Miscellaneous: Scan RTCM |
serialAutoNMEA=Auto | Serial Output: NMEA |
serialBaudRate=9600 | Serial Output: Baud rate |
serialDataBits=8 | Serial Output: Data bits |
serialHeightNMEA= | Serial Output: Height |
serialMountPoint= | Serial Output: Mountpoint |
serialParity=NONE | Serial Output: Parity |
serialPortName= | Serial Output: Port name |
serialStopBits=1 | Serial Output: Stop bits |
startTab=0 | Internal memory: Top tab index |
statusTab=0 | Internal memory: Bottom tab index |
waitTime=5 | Feed Engine: Wait for full epoch |
pppMount= | PPP Client: Mountpoint |
pppSPP=PPP | PPP Client: PPP/SPP |
pppSigmaCode=5.0 | PPP Client: Sigma for Code observations |
pppSigmaPhase=0.02 | PPP Client: Sigma for Phase observations |
pppQuickStart=200 | PPP Client: Quick-Start period |
pppSigmaCrd0=100.0 | PPP Client: Sigma for initial XYZ coordinate |
pppSigmaCrdP=100.0 | PPP Client: White noise for XYZ |
pppSigmaTrp0=0.1 | PPP Client: Sigma for initial tropospheric delay |
pppSigmaTrpP=1e-6 | PPP Client: White noise for tropospheric delay |
pppUsePhase=0 | PPP Client: Use phase data |
pppEstTropo=0 | PPP Client: Estimate troposphere |
pppGLONASS=0 | PPP Client: Use GLONASS |
pppPlotCoordinates=0 | PPP Client: Plot NEU time series |
pppAverage= | PPP Client: Lenght of time window for moving average |
pppRefCrdX= | PPP Client: X coordinate of plot origin |
pppRefCrdY= | PPP Client: Y coordinate of plot origin |
pppRefCrdZ= | PPP Client: Z coordinate of plot origin |
nmeaFile= | PPP Client: NMEA outputfile |
nmeaPort= | PPP Client: NMEA IP output port |
Note that the following configuration options saved on disk can be changed/edited on-the-fly while BNC is already processing data:
NTRIP | http://igs.bkg.bund.de/ntrip/about |
EUREF-IP NTRIP broadcaster | http://www.euref-ip.net/home |
IGS-IP NTRIP broadcaster | http://www.igs-ip.net/home |
IGS products NTRIP broadcaster | http://products.igs-ip.net/home |
Distribution of IGS-IP streams | http://www.igs.oma.be/real_time/ |
Completeness and latency of IGS-IP data | http://www.igs.oma.be/highrate/ |
NTRIP broadcaster overview | http://www.rtcm-ntrip.org/home |
NTRIP Open Source software code | http://software.rtcm-ntrip.org |
EUREF-IP Project | http://www.epncb.oma.be/euref_IP |
Real-time IGS Pilot Project | http://www.rtigs.net/pilot |
Radio Technical Commission for Maritime Services | http://www.rtcm.org |