Changeset 6952 in ntrip
- Timestamp:
- Jun 23, 2015, 5:02:37 PM (9 years ago)
- File:
-
- 1 edited
-
trunk/BNC/src/bnchelp.html (modified) (16 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r6949 r6952 2076 2076 <li>L3 biases, also known as 'floated ambiguities', given per satellite. 2077 2077 </ul> 2078 These parameters are saved together with their standard deviation. The following is an example extract from a log 2078 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: 2079 2079 </p> 2080 2080 <p> … … 2303 2303 </p> 2304 2304 <p> 2305 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 2305 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. 2306 2306 </p> 2307 2307 … … 2329 2329 <p><a name="pppaverage"><h4>3.13.7.6 Averaging - optional if XYZ is set</h4></p> 2330 2330 <p> 2331 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 2331 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: 2332 2332 </p> 2333 2333 <pre> … … 2337 2337 </pre> 2338 2338 <p> 2339 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 2339 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. 2340 2340 </p> 2341 2341 … … 2961 2961 </p> 2962 2962 <p><img src="IMG/screenshot26.png"/></p> 2963 <p><u>Figure 2 8:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.</p>2963 <p><u>Figure 29:</u> Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an NTRIP Broadcaster.</p> 2964 2964 2965 2965 <p><a name="upeph"><h4>3.16. Upload Ephemeris</h4></p> … … 2970 2970 <p><a name="brdcserver"><h4>3.16.1 Host & Port - optional</h4></p> 2971 2971 <p> 2972 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. 2973 </p> 2974 <p> 2975 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 2976 port 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s). 2972 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. 2973 </p> 2974 <p> 2975 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). 2977 2976 </p> 2978 2977 … … 2988 2987 2989 2988 <p><img src="IMG/screenshot28.png"/></p> 2990 <p><u>Figure 29:</u> 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.</p>2989 <p><u>Figure 30:</u> 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.</p> 2991 2990 2992 2991 <p><a name="streams"><h4>3.17. Streams</h4></p> 2993 2992 <p> 2994 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.2993 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. 2995 2994 </p> 2996 2995 … … 3017 3016 </li> 3018 3017 <li> 3019 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 3018 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. 3020 3019 </li> 3021 3020 <li> 3022 3021 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. 3023 3022 <br>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. 3024 <br>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. .3023 <br>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. 3025 3024 </li> 3026 3025 </ul> … … 3055 3054 3056 3055 <p><img src="IMG/screenshot08.png"/></p> 3057 <p><u>Figure 3 0:</u> Bandwidth consumption of incoming streams.</p>3056 <p><u>Figure 31:</u> Bandwidth consumption of incoming streams.</p> 3058 3057 3059 3058 <p><a name="latency"><h4>3.18.3 Latency</h4></p> … … 3063 3062 3064 3063 <p><img src="IMG/screenshot07.png"/></p> 3065 <p><u>Figure 3 1:</u> Latency of incoming streams.</p>3064 <p><u>Figure 32:</u> Latency of incoming streams.</p> 3066 3065 3067 3066 <p><a name="ppptab"><h4>3.18.4 PPP Plot</h4></p> … … 3071 3070 3072 3071 <p><img src="IMG/screenshot13.png"/></p> 3073 <p><u>Figure 3 2:</u> Time series plot of PPP session.</p>3072 <p><u>Figure 33:</u> Time series plot of PPP session.</p> 3074 3073 3075 3074 <p><a name="bottom"><h4>3.19. Bottom Menu Bar</h4></p> … … 3079 3078 3080 3079 <p><img src="IMG/screenshot06.png"/></p> 3081 <p><u>Figure 3 3:</u> Steam input communication links.</p>3080 <p><u>Figure 34:</u> Steam input communication links.</p> 3082 3081 3083 3082 <p><a name="streamadd"><h4>3.19.1 Add Stream</h4></p> 3084 3083 <p> 3085 Button 'Add Stream' allows you to pull streams either from a n NTRIP Broadcaster or from a TCP/IP port, a UPD port, or aserial port.3084 Button 'Add Stream' allows you to pull streams either from a NTRIP Broadcaster or from a TCP/IP port, UPD port, or serial port. 3086 3085 </p> 3087 3086 … … 3104 3103 <p><img src="IMG/screenshot04.png"/></p> 3105 3104 3106 <p><u>Figure 3 4:</u> Casters table.</p>3105 <p><u>Figure 35:</u> Casters table.</p> 3107 3106 3108 3107 <p><a name="streamuser"><h4>3.19.1.1.3 User and Password - mandatory for protected streams</h4></p> 3109 3108 <p> 3110 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 <u>http:// igs.bkg.bund.de/ntrip/registeruser</u> for access to protected streams from EUREF and IGS.3109 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 <u>http://register.rtcm-ntrip.org</u> for access to protected streams from EUREF and IGS. 3111 3110 </p> 3112 3111 … … 3122 3121 </p> 3123 3122 <p><img src="IMG/screenshot05.png"/></p> 3124 <p><u>Figure 3 5:</u> Broadcaster source-table.</p>3123 <p><u>Figure 36:</u> Broadcaster source-table.</p> 3125 3124 3126 3125 <p><a name="ntripv"><h4>3.19.1.1.5 NTRIP Version - mandatory</h4></p> … … 3152 3151 3153 3152 <p><img src="IMG/screenshot24.png"/></p> 3154 <p><u>Figure 3 6:</u> Stream distribution map derived from NTRIP Broadcaster source-table.</p>3153 <p><u>Figure 37:</u> Stream distribution map derived from NTRIP Broadcaster source-table.</p> 3155 3154 3156 3155 <p><a name="streamip"><h4>3.19.1.2 Add Stream - Coming from TCP/IP Port</h4></p> … … 3226 3225 </p> 3227 3226 <p><img src="IMG/screenshot15.png"/></p> 3228 <p><u>Figure 3 7:</u> BNC setup for pulling a stream via serial port.</p>3227 <p><u>Figure 38:</u> BNC setup for pulling a stream via serial port.</p> 3229 3228 3230 3229 <p><a name="streamsdelete"><h4>3.19.2 Delete Stream</h4></p>
Note:
See TracChangeset
for help on using the changeset viewer.
