Index: trunk/BNC/src/bnchelp.html =================================================================== --- trunk/BNC/src/bnchelp.html (revision 6951) +++ trunk/BNC/src/bnchelp.html (revision 6952) @@ -2076,5 +2076,5 @@
  • L3 biases, also known as 'floated ambiguities', given per satellite. -These parameters are saved together with their standard deviation. The following is an example extract from a log file when BNC was in 'Single Point Positioning' (SPP) mode: +These parameters are saved together with their standard deviation. The following is an example extract from a logfile when BNC was in 'Single Point Positioning' (SPP) mode:

    @@ -2303,5 +2303,5 @@

    -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/cos(z) in BNC's log file. +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/cos(z) in BNC's logfile.

    @@ -2329,5 +2329,5 @@

    3.13.7.6 Averaging - optional if XYZ is set

    -Enter the length of a sliding time window in minutes. BNC will continuously output moving average values and their RMS as computed from those individual values obtained most recently throughout this period. RMS values presented for XYZ coordinates and tropospheric zenith path delays are bias reduced while RMS values for North/East/Up (NEU) displacements are not. Averaged values for XYZ coordinates and their RMS are marked with string "AVE-XYZ" in BNC's log file and 'Log' section while averaged values for NEU displacements and their RMS are marked with string "AVE-NEU" and averaged values for the tropospheric delays and their RMS are marked with string "AVE-TRP". Example: +Enter the length of a sliding time window in minutes. BNC will continuously output moving average values and their RMS as computed from those individual values obtained most recently throughout this period. RMS values presented for XYZ coordinates and tropospheric zenith path delays are bias reduced while RMS values for North/East/Up (NEU) displacements are not. Averaged values for XYZ coordinates and their RMS are marked with string "AVE-XYZ" in BNC's logfile 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: 

    @@ -2337,5 +2337,5 @@

    -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. +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 logfile and the 'Log' section. Note that averaging positions makes only sense for a stationary receiver.

    @@ -2961,5 +2961,5 @@

    -

    Figure 28: Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.

    +

    Figure 29: Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.

    3.16. Upload Ephemeris

    @@ -2970,9 +2970,8 @@

    3.16.1 Host & Port - optional

    -Specify the 'Host' IP name or number of an NTRIP Broadcaster to upload the stream. An empty option field means that you don't want to upload Broadcast Ephemeris. -

    -

    -Enter the NTRIP Broadcaster's IP 'Port' number for stream upload. Note that NTRIP Broadcasters are often configured to provide access on more than one port, usually -port 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s). +Specify the 'Host' IP number or URL of an NTRIP Broadcaster to upload the stream. An empty option field means that you don't want to upload Broadcast Ephemeris. +

    +

    +Enter the NTRIP Broadcaster's IP 'Port' number for stream upload. Note that NTRIP Broadcasters are often configured to provide access through more than one port, usually ports 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s).

    @@ -2988,9 +2987,9 @@

    -

    Figure 29: Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an NTRIP Broadcaster.

    +

    Figure 30: Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an NTRIP Broadcaster.

    3.17. Streams

    -Each stream on an NTRIP Broadcaster (and consequently on BNC) is defined using a unique source ID called mountpoint. An NTRIP Client like BNC accesses the desired stream by referring to its mountpoint. Information about streams and their mountpoints is available through the source-table maintained by the NTRIP Broadcaster. Note that mountpoints could show up in BNC more than once when retrieving streams from several NTRIP Broadcasters. +Each stream on an NTRIP Broadcaster (and consequently on BNC) is defined using a unique source ID called mountpoint. An NTRIP Client like BNC accesses the desired stream by referring to its mountpoint. Information about streams and their mountpoints is available through the source-table maintained by the NTRIP Broadcaster.

    @@ -3017,10 +3016,10 @@
  • -In case you need to log the raw data as is, BNC allows users to by-pass its decoders and directly save the input in daily log files. To do this, specify the decoder string as 'ZERO'. The generated file names are created from the characters of the streams mountpoints plus two-digit numbers each for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and running BNC on March 29, 2007 would save the raw data in a file named WTZZ0_070329. +In case you need to log the raw data as is, BNC allows users to by-pass its decoders and directly save the input in daily logfiles. To do this, specify the decoder string as 'ZERO'. The generated file names are created from the characters of the streams mountpoints plus two-digit numbers each for year, month, and day. Example: Setting the 'decoder' string for mountpoint WTZZ0 to 'ZERO' and running BNC on March 29, 2007 would save the raw data in a file named WTZZ0_070329.
  • BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA format to the NTRIP Broadcaster. In return, a user-specific data stream is generated, typically by Network-RTK software. VRS streams are indicated by a 'yes' in the source-table as well as in the 'nmea' column on the 'Streams' canvas in BNC's main window. They are customized exactly to the latitude and longitude transmitted to the NTRIP Broadcaster via NMEA-GGA messages.
    If NMEA-GGA messages are not coming from a serial connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'long' columns on the 'Streams' canvas. However, in most cases you would probably want to change these defaults according to your requirement. Double-click on 'lat' and 'long' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only streams with a 'yes' in their 'nmea' column can be edited. The position must preferably be a point within the VRS service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'long' used. -
    Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner when not using the NTRIP Version 2 transport protocol.. +
    Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner when not using the NTRIP Version 2 transport protocol.
    • @@ -3055,5 +3054,5 @@

    -

    Figure 30: Bandwidth consumption of incoming streams.

    +

    Figure 31: Bandwidth consumption of incoming streams.

    3.18.3 Latency

    @@ -3063,5 +3062,5 @@

    -

    Figure 31: Latency of incoming streams.

    +

    Figure 32: Latency of incoming streams.

    3.18.4 PPP Plot

    @@ -3071,5 +3070,5 @@

    -

    Figure 32: Time series plot of PPP session.

    +

    Figure 33: Time series plot of PPP session.

    3.19. Bottom Menu Bar

    @@ -3079,9 +3078,9 @@

    -

    Figure 33: Steam input communication links.

    +

    Figure 34: Steam input communication links.

    3.19.1 Add Stream

    -Button 'Add Stream' allows you to pull streams either from an NTRIP Broadcaster or from a TCP/IP port, a UPD port, or a serial port. +Button 'Add Stream' allows you to pull streams either from a NTRIP Broadcaster or from a TCP/IP port, UPD port, or serial port.

    @@ -3104,9 +3103,9 @@

    -

    Figure 34: Casters table.

    +

    Figure 35: Casters table.

    3.19.1.1.3 User and Password - mandatory for protected streams

    -Some streams on NTRIP Broadcasters may be restricted. Enter a valid 'User' ID and 'Password' for access to protected streams. Accounts are usually provided per NTRIP Broadcaster through a registration procedure. Register through http://igs.bkg.bund.de/ntrip/registeruser for access to protected streams from EUREF and IGS. +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://register.rtcm-ntrip.org for access to protected streams from EUREF and IGS.

    @@ -3122,5 +3121,5 @@

    -

    Figure 35: Broadcaster source-table.

    +

    Figure 36: Broadcaster source-table.

    3.19.1.1.5 NTRIP Version - mandatory

    @@ -3152,5 +3151,5 @@

    -

    Figure 36: Stream distribution map derived from NTRIP Broadcaster source-table.

    +

    Figure 37: Stream distribution map derived from NTRIP Broadcaster source-table.

    3.19.1.2 Add Stream - Coming from TCP/IP Port

    @@ -3226,5 +3225,5 @@

    -

    Figure 37: BNC setup for pulling a stream via serial port.

    +

    Figure 38: BNC setup for pulling a stream via serial port.

    3.19.2 Delete Stream