-The usual handling of BNC is that you first select a number of streams from NTRIP broadcasters ('Add Streams'). 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 tabs to select a combination of processing options before you start the program ('Start'). Records of BNC's activities are shown in the 'Log' canvas on the bottom of the main window. +The usual handling of BNC is that you first select a number of streams from NTRIP broadcasters ('Add Streams'). 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 tabs to select a combination of processing options before you start the program ('Start'). Records of BNC's activities are shown in the 'Logs' canvas on the bottom of the main window.
@@ -128,6 +128,6 @@
3.12. Streams
3.12.1. Add Streams
- 3.12.2. Broadcaster Host and Port
- 3.12.3. Broadcaster User and Password
+ 3.12.2. Caster Host and Port
+ 3.12.3. Caster User and Password
3.12.4. Get Table
3.12.5. Delete Streams
@@ -195,5 +195,5 @@
-Records of BNC's activities are shown in the 'Log' canvas on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Log (full path)' field. The message log covers 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 'Log (full path)' is an empty option field, meaning that BNC logs will not saved into a file. +Records of BNC's activities are shown in the 'Logs' canvas 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 message log covers 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.
@@ -505,5 +505,5 @@-Note that any socket connection of an application to BNC's synchronized observations 'Port' is recorded in the 'Log' canvas on the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'. +Note that any socket connection of an application to BNC's synchronized observations 'Port' is recorded in the 'Logs' canvas on the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'.
@@ -523,5 +523,5 @@-Note that any socket connection of an application to BNC's unsynchronized observations 'Port' is recorded in the 'Log' canvas on the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'. +Note that any socket connection of an application to BNC's unsynchronized observations 'Port' is recorded in the 'Logs' canvas on the bottom of the main window together with a connection counter, leading to log records like 'New Connection # 1'.
@@ -606,5 +606,5 @@-Outage and corruption events are reported in the 'Log' file/canvas. 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 utilise BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations. +Outage and corruption events are reported in the 'Logs' canvas. 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 utilise BNC as a real-time performance monitor and alarm system for a network of GNSS reference stations.
@@ -695,5 +695,5 @@-Latencies of observations or corrections to Broadcast Ephemeris and statistical information can be recorded in the 'Log' file/canvas at the end of each 'Performance log' interval. A typical output from a 1 hour 'Performance log' interval would be: +Latencies of observations or corrections to Broadcast Ephemeris and statistical information can be recorded in the 'Logs' canvas at the end of each 'Performance log' interval. A typical output from a 1 hour 'Performance log' interval would be:
@@ -754,10 +754,10 @@ -+
3.12.2 Broadcaster Host and Port - mandatory
3.12.2 Caster Host and Port - mandatory
Enter the NTRIP broadcaster host IP and port number. http://www.rtcm-ntrip.org/home provides information about known NTRIP broadcaster installations. Note that EUREF and IGS operate NTRIP broadcasters at http://www.euref-ip.net/home and http://www.igs-ip.net/home.
-+
3.12.3 Broadcaster User and Password - mandatory for protected streams
3.12.3 Caster 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.