Changeset 4039 in ntrip


Ignore:
Timestamp:
Apr 23, 2012, 9:44:50 PM (13 years ago)
Author:
weber
Message:

Documentation completed

File:
1 edited

Legend:

Unmodified
Added
Removed

  • TabularUnified trunk/BNC/bnchelp.html

    r4037 r4039  
    127127
    128128<p>
    129 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 a PPP time series for coordinates are shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs of the main window.
     129The 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'). Most configuration tabs are dedicated to a certain functionality of BNC. If the first option field on such a configuration tab is empty, the affected functionality is - appart from a few exceptions -  deactivated.</p>
     130
     131Records of BNC's activities are shown in the 'Log' tab. The bandwidth consumption per stream, the latency of incoming observations and a PPP time series for coordinates are shown in the 'Throughput', 'Latency' and 'PPP Plot' tabs of the main window.
    130132</p>
    131133<p>
    … …  
    214216&nbsp; &nbsp; &nbsp; 3.12.6.2 <a href=#ppprecantenna>Antenna Name</a><br>
    215217&nbsp; &nbsp; &nbsp; 3.12.6.3 <a href=#pppsatant>Apply Satellite Antenna Offsets</a><br>
    216 &nbsp; &nbsp; &nbsp; 3.12.7 <a href=#pppopt>PPP Options</a><br>
     218&nbsp; &nbsp; &nbsp; 3.12.7 <a href=#pppopt>Basic Options</a><br>
    217219&nbsp; &nbsp; &nbsp; 3.12.7.1 <a href=#pppphase>Use Phase Obs</a><br>
    218220&nbsp; &nbsp; &nbsp; 3.12.7.2 <a href=#ppptropo>Estimate Tropo</a><br>
    … …  
    339341<p><a name="ssl"><h4>3.2.2 SSL - Transport Layer Security</h4></p>
    340342<p>Communication with an NTRIP broadcaster over SSL requires the exchange of client and/or server certificates. Specify the path to a directory where you save certificates on your system. You may like to check out <u>http://software.rtcm-ntrip.org/wiki/Certificates</u> for a list of known NTRIP server certificates. Don't try communication via SSL if you are not sure wheter this is supported by the involved NTRIP broadcaster. </p>
    341 <p>SSL communication may involve queries coming from the NTRIP broadcaster. Tick 'Ignore SSL authorization erros' if you don't want to be bothered with this.</p>
    342 <p>Note that SSL communication is usually done over port 443.</p>
     343<p>SSL communication may involve queries coming from the NTRIP broadcaster. Tick 'Ignore SSL authorization erros' if you don't want to be bothered with this. Note that SSL communication is usually done over port 443.</p>
    343344
    344345<p><a name="general"><h4>3.3. General</h4></p>
    … …  
    372373<p><a name="rawout"><h4>3.3.5 Raw Output File - optional</h4></p>
    373374<p>
    374 BNC can save all data coming in through various streams in one daily file. The information is recorded in the specified 'Raw output file' in the received order and format. This feature allows a BNC user to run the PPP option in offline mode with observations, orbit/clock correctors, and broadcast ephemeris being read from a previously saved file. It supports the offline replay/repetition of a real-time situation for debugging purposes. It is not meant for post-processing purposes.
     375BNC can save all data coming in through various streams in one daily file. The information is recorded in the specified 'Raw output file' in the received order and format. This feature allows a BNC user to run the PPP option in offline mode with observations, orbit/clock correctors, and broadcast ephemeris being read from a previously saved file. It supports the offline repetition of a real-time situation for debugging purposes. It is not meant for post-processing.
    375376</p>
    376377<p>
    … …  
    3793802010-08-03T18:05:28 RTCM3EPH RTCM_3 67
    380381</pre>
    381 This example block header tells you that 67 bytes weree 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 in order to allow the complete reconstruction of a recorded situation.
    382 </p>
    383 <p>
    384 The default value for 'Raw output file (full path)' is an empty option field, meaning that BNC will not save all raw data into one single daily file.
     382This example block header tells you that 67 bytes were saved in the data block following this time stamp. 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 in order to allow the reconstruction of a recorded real-time situation.
     383</p>
     384<p>
     385The default value for 'Raw output file' is an empty option field, meaning that BNC will not save all raw data into one single daily file.
    385386</p>
    386387
    387388<p><a name="rinex"><h4>3.4. RINEX Observations</h4></p>
    388389<p>
    389 Observations will be converted to RINEX if they come in either RTCM Version 2.x or RTCM Version 3.x format. Depending on the RINEX version and incoming RTCM message types, the files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS, and COMPASS. In case an observation type is listed in the RINEX header but the corresponding observation is unavailable, its value is set to zero '0.000'. Note that the 'RINEX TYPE' field in the RINEX Version 3 Observation file header is always set to 'M(MIXED)' even if the file only contains data from one system.
    390 </p>
    391 
    392 <p>
    393 The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming 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.
     390Observations will be converted to RINEX if they come in either RTCM Version 2.x or RTCM Version 3.x format. Depending on the RINEX version and incoming RTCM message types, the files generated by BNC may contain data from GPS, GLONASS, Galileo, SBAS, QZSS, and COMPASS. In case an observation type is listed in the RINEX header but the corresponding observation is unavailable, its value is set to zero '0.000'. Note that the 'RINEX TYPE' field in the RINEX Version 3 Observation file header is always set to 'M(MIXED)' or 'Mixed' even if the file only contains data from one system.
     391</p>
     392
     393<p>
     394The screenshot below shows an example setup of BNC when converting streams to RINEX. Streams are coming from various NTRIP broadcasters as well as from a serial communication link. Specifying a decoder string 'ZERO' would have meant to not convert the affected stream contents but save its contents as received.
    394395</p>
    395396<p><img src="IMG/screenshot16.png"/></p>
    … …  
    501502</p>
    502503<p>
    503 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'.
     504As 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 one or two minutes after the end of each RINEX file 'Interval'.
    504505</p>
    505506
    … …  
    592593<p>
    593594Mandatory if 'Edit/Concatenate' selected:<br>
    594 Specify full path to output RINEX observation file(s), and<br>
     595Specify full path to output RINEX observation file(s) and
    595596specify full path to output RINEX navigation file(s).
    596597</p>
    … …  
    649650! Orbits/Clocks: 0 GPS 19 Glonass CLK11
    650651<p>
    651 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.
     652Such line informs you about the number of records (here 30 and 19) carrying GPS or GLONASS related parameters you should receive next.
    652653</p>
    653654<p>
    … …  
    13851386</p>
    13861387
    1387 <p><a name="pppopt"><h4>3.12.7 PPP Options</h4></p>
     1388<p><a name="pppopt"><h4>3.12.7 Basic Options</h4></p>
    13881389<p>BNC allows to use different Point Positioning processing options depending on the capability of the involved receiver and the application in mind. It also allows to introduce specific sigmas for code and phase observations as well as for reference coordinates and troposphere estimates. You may also like to carry out your PPP solution in Quick-Start mode or enforce BNC to restart a solution if the length of an outage exceeds a certain threshold.
    13891390</p>
Note: See TracChangeset for help on using the changeset viewer.