+A tabs section on the bottom of the main window provides online controle of BNC's activities. Tabs are available to show the records saved in a logfile and for a plot to controle the bandwidth consumtion. +
+ ++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 consumtion per stream is shown in the 'Throughput' tab in bits per second (bps) or kilo bits per second (kbps). +
+ +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.
-3.12.1 Add Stream - Coming from Caster
3.13.1 Add Stream - Coming from Caster
Button 'Add Stream' > 'Coming from Caster' opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints.
-3.12.1.1 Caster Host and Port - mandatory
3.13.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.
-3.12.1.2 Casters Table - optional
3.13.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.
-3.12.1.3 User and Password - mandatory for protected streams
3.13.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/index_ntrip_reg.htm for access to protected streams on www.euref-ip.net and www.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. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. @@ -1006,5 +1022,5 @@
-3.12.1.5 NTRIP Version - mandatory
3.13.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: @@ -1027,5 +1043,5 @@
-3.12.2 Add Stream - Coming from TCP/IP Port
3.13.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: @@ -1046,5 +1062,5 @@
-3.12.3 Add Stream - Coming from UDP Port
3.13.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: @@ -1061,5 +1077,5 @@
-
3.12.4 Add Stream - Coming from Serial Port
3.13.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: @@ -1095,20 +1111,20 @@
-
+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.13.1 No Window Mode - optional
3.14.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. @@ -1119,5 +1135,5 @@
-3.13.2 Offline Mode - optional
3.14.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 file for post processing purposes. Enter the following four command line options for that: @@ -1138,5 +1154,5 @@
- + The default configuration file name is 'BNC.ini'. You may change this name at startup time using the command line option '--conf <confFileName>'. This allows to run several BNC jobs in parallel on the same host using different sets of configuration options. confFileName stands either for the full path to a configuration file or just for a file name. If you introduce only a filename, the corresponding file will be saved in the current working directory from where BNC is started.