Changeset 178 in ntrip for trunk/BNC


Ignore:
Timestamp:
Sep 24, 2006, 2:18:49 PM (18 years ago)
Author:
mervart
Message:

* empty log message *

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/bnchelp.html

    r176 r178  
    11
    2 <a name="back_contents">
    32<p><h3>BKG Ntrip Client (BNC)</h3></p>
    43
     
    4544<p>
    4645BNC has been developed under GNU General Public License (GPL). Binaries for BNC are available for Windows, Linux, and Solaris systems. It is likely that BNC can be compiled on other systems where a GNU compiler and Qt Version 4 are available.
    47 &nbsp; [<a href=#back_contents>Back</a>]<br>
    48 </p>
    49 
    50 <br>
    51 <a name="back_options">
     46</p>
     47
     48<br>
    5249<a name="options">
    5350<p><h3>B - Options</h3></p>
     
    7673B - 9. <a href=#stop>Stop</a><br>
    7774B - 10. <a href=#nw>No Window</a>
    78 &nbsp; [<a href=#back_contents>Back</a>]<br>
    7975</p>
    8076
     
    9490<li>
    9591Quit the execution of BNC.
    96 &nbsp; [<a href=#back_options>Back</a>]<br>
    9792</li>
    9893</ul>
     
    112107Help contents.<br>
    113108You may keep the 'Help Contents' window open while setting BNC options.
    114 &nbsp; [<a href=#back_options>Back</a>]<br>
    115109</li>
    116110</ul>
     
    124118<p>
    125119Note that IP streaming may be generally denied in a LAN. In such a case you need to request an appropriate modification of the security policy from your network administrator or ask for the installation of a TCP relay to involved NTRIP broadcasters. If that doesn't work out, run BNC on a host that is connected to the Internet through an Internet Service Provider (ISP).
    126 &nbsp; [<a href=#back_options>Back</a>]<br>
    127120</p>
    128121
     
    131124BNC lets you output synchronized observations epoch by epoch. This output is made available in ASCII format and in binary format. The output comprises the following observations if available:</p>
    132125StatID, SVPRN, GPSWeek, GPSWeeks, sec, C1, P2, L1, L2, SNR1, SNR2, pCodeIndicator, cumuLossOfCont.
    133 &nbsp; [<a href=#back_options>Back</a>]<br>
    134126</p>
    135127
     
    141133<p>
    142134Note that 'Wait for full epoch' does not influence the RINEX file contents. Observations received later than 'Wait for full epoch' seconds will still be included in the RINEX files.
    143 &nbsp; [<a href=#back_options>Back</a>]<br>
    144135</p>
    145136
     
    148139<p>
    149140Enter the full path for a file to save synchronized observations in plain ASCII format. Default value is an empty option field, meaning that no ASCII output file is generated.
    150 &nbsp; [<a href=#back_options>Back</a>]<br>
    151141</p>
    152142
     
    154144<p><h4>B - 4.3 Port for Binary Output - optional</h4></p>
    155145<p>
    156 BNC makes synchronized observations available in a binary format through an IP port. Enter the port number to activate this function. Default is an empty option field, meaning that no binary output is generated.
    157 </p>
    158 <p>The binary output is provided in the following format:<br>
    159 Input from Leos?
    160 &nbsp; [<a href=#back_options>Back</a>]<br>
     146BNC makes synchronized observations available in a binary format through an IP
     147port. Enter the port number to activate this function. Default is an empty
     148option field, meaning that no binary output is generated.
     149</p>
     150<p>The binary output is provided as a continuous stream
     151<pre>
     152begEpoch
     153begObs 
     154Observation
     155begObs 
     156Observation
     157begObs 
     158Observation
     159...
     160endEpoch
     161begEpoch
     162...
     163</pre>
     164where the corresponding structures are defined as
     165<pre>
     166const char begEpoch = 'A';
     167const char begObs   = 'B';
     168const char endEpoch = 'C';
     169struct Observation {
     170  char     StatID[5+1];    // Station ID
     171  char     SVPRN;          // Satellite PRN
     172  short    GPSWeek;        // Week of GPS-Time
     173  int      GPSWeeks;       // Second of Week (GPS-Time)
     174  double   sec;            // second
     175  double   C1;             // CA or P1-code pseudorange (meters)
     176  double   P2;             // P2-code pseudorange (meters)
     177  double   L1;             // L1-carrier phase (meters)
     178  double   L2;             // L2-carrier phase (meters)
     179  short    SNR1;           // Signal-to noise ratio (0.1 dB)
     180  short    SNR2;           // Signal-to noise ratio (0.1 dB)
     181  int      pCodeIndicator; // 0 ... CA Code, 1 ... P Code
     182  unsigned cumuLossOfCont; // Loss of lock indicator (0 to 31)
     183} ;
     184</pre>
    161185</p>
    162186
     
    167191<p>
    168192In case you retrieve streams that show mountpoints with an identical 4Char Station ID (same first 4 characters), the mountpoint string is split in two sub-strings and both become part of the RINEX file name. Example: When simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, there RINEX file names are defined as FRAN*_KFURT.* and FRAN*_CE.*.
    169 &nbsp; [<a href=#back_options>Back</a>]<br>
    170193</p>
    171194
     
    174197<p>
    175198Enter a path for saving the RINEX files in a directory. If this directory does not exist, BNC will not generate RINEX files. Default value for 'RINEX directory path' is an empty option field, meaning that streams are not converted to RINEX.
    176 &nbsp; [<a href=#back_options>Back</a>]<br>
    177199</p>
    178200
     
    181203<p>
    182204Whenever a RINEX file is generated, you may like to compress, copy, or upload it immediately. For that you enter the full path of a script or batch file carrying out these operations. The RINEX file name will be passed to the script as a command line parameter.
    183 &nbsp; [<a href=#back_options>Back</a>]<br>
    184205</p>
    185206
     
    188209<p>
    189210Select the interval for RINEX file generation. Default for 'RINEX file interval' is 15 minutes.
    190 &nbsp; [<a href=#back_options>Back</a>]<br>
    191211</p>
    192212
     
    195215<p>
    196216Select the RINEX sample interval in seconds. Zero '0' stands for converting all incoming epochs to RINEX. Default for 'RINEX sampling' is '0'.
    197 &nbsp; [<a href=#back_options>Back</a>]<br>
    198217</p>
    199218
     
    205224<p>
    206225Example: Mountpoint FRAN0 leads to the generation of RINEX files FRAN*.*. The header part of this files would be overwritten by the content of an existing skeleton file FRAN.skl in case 'RINEX skeleton extension' is set to 'skl' .
    207 &nbsp; [<a href=#back_options>Back</a>]<br>
    208226</p>
    209227
     
    212230<p>
    213231Each stream on an NTRIP broadcaster is defined through a unique source ID called mountpoint. An NTRIP client like BNC can access the data of a desired stream by its mountpoint. Information about mountpoints is available through the sourcetable maintained by the NTRIP broadcaster.
    214 &nbsp; [<a href=#back_options>Back</a>]<br>
    215232</p>
    216233
     
    219236<p>
    220237Button 'Add Mountpoints' opens a window that lets you select data streams by their mountpoints.
    221 &nbsp; [<a href=#back_options>Back</a>]<br>
    222238</p>
    223239
     
    226242<p>
    227243Enter the NTRIP broadcaster host IP and port number. <u>http://www.rtcm-ntrip.org/home</u> provides information about known NTRIP broadcaster installations. Note that EUREF and IGS operate NTRIP broadcasters at <u>http://www.euref-ip.net/home</u> and <u>http://www.igs-ip.net/home</u>.
    228 &nbsp; [<a href=#back_options>Back</a>]<br>
    229244</p>
    230245
     
    233248<p>
    234249Streams on NTRIP broadcasters may be password protected. Enter a valid User ID and Password for access to protected NTRIP broadcaster streams. Accounts are usually provided per NTRIP broadcaster through a registration procedure. Register through <u>http://igs.bkg.bund.de/index_ntrip_reg.htm</u> for access to protected streams on <u>www.euref-ip.net</u> and <u>www.igs-ip.net</u>.
    235 &nbsp; [<a href=#back_options>Back</a>]<br>
    236250</p>
    237251
     
    240254<p>
    241255Hit button 'Get Table' to download a sourcetable from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Remember that BNC can only decode and convert streams that come in RTCM 2.x, RTCM 3, or RTIGS format. RTCM 2.x streams must contain message types 18 and 19 while RTCM 3 streams must contain message types 1001 or 1003, better 1003 or 1004, see data field 'format-details' for available message types and their repetition rates in brackets. Select your streams line by line, use +Shift and +Ctrl when necessary. Hit 'OK' to return to the main window.
    242 &nbsp; [<a href=#back_options>Back</a>]<br>
    243256</p>
    244257
     
    249262<p>
    250263BNC automatically selects one out of several internal decoders for a stream based on its 'format' and 'format-details' as given in the sourcetable. It may happen that you need to overrule the automated decoder selection because of sourcetable setup deficiencies. Therefore BNC allows to edit the decoder part for each stream shown under 'Mountpoints'. Accepted decoder strings allowed to be introduced are 'RTCM_2.x', 'RTCM_3', and 'RTIGS'.
    251 &nbsp; [<a href=#back_options>Back</a>]<br>
    252264</p>
    253265
     
    259271<p>
    260272Note that a connection to the NTRIP broadcaster may break or a stream requested may be temporarily unavailable. When this happens, a reconnect is tried with decreasing frequency. BNC first tries to reconnect with 1 second delay, if unsuccessful, tries again in 2 seconds from the last attempt, if still unsuccessful tries with 4 seconds from the last attempt etc. Each attempt doubles the delay from the previous attempt. The maximum delay between attempts is limited to 60 seconds. The reconnection process is documented in 'Log file'.
    261 &nbsp; [<a href=#back_options>Back</a>]<br>
    262273</p>
    263274
     
    266277<p>
    267278Hit 'Start' to start retrieving, decoding, and converting GNSS data streams in real-time.
    268 &nbsp; [<a href=#back_options>Back</a>]<br>
    269279</p>
    270280
     
    273283<p>
    274284Hit the 'Stop' button to stop BNC.
    275 &nbsp; [<a href=#back_options>Back</a>]<br>
    276285</p>
    277286
     
    283292<p>
    284293Note that the self-explaining contents of the configuration file can easily be edited and option -nw is not available under Windows.
    285 &nbsp; [<a href=#back_options>Back</a>]<br>
    286294</p>
    287295<br>
     
    314322<li>
    315323EUREF as well as IGS follow an open data policy. Streams are made available through NTRIP broadcasters at <u>www.euref-ip.net</u> and <u>www.igs-ip.net</u> free of charge to anybody for any purpose. It is not clear today how many users will have to be supported simultaneously. The situation may develop in a way that it becomes difficult to serve all registered users at any time.  In case limited dissemination resources on the NTRIP broadcaster side (software restrictions, bandwidth limitation etc.) make it necessary, first priority in stream provision will be given to stream providers, real-time analysis centres, and re-broadcasting activities while access for others may be temporarily denied.
    316 &nbsp; [<a href=#back_contents>Back</a>]<br>
    317324</li>
    318325</ul>
     
    336343Frankfurt, Germany<br>
    337344euref-ip@bkg.bund.de
    338 &nbsp; [<a href=#back_contents>Back</a>]<br>
    339345</p>
    340346<br>
     
    349355<tr><td>EUREF-IP Pilot Project &nbsp;</td><td><u>http://www.epncb.oma.be/euref_IP</u></td></tr>
    350356<tr><td>Real-Time IGS Working Group &nbsp;</td><td><u>http://igscb.jpl.nasa.gov/projects/rtwg/index.html</u>
    351 &nbsp; [<a href=#back_contents>Back</a>]<br>
    352357</table>
    353358<br><br>
    354359
    355 <a name="back_annex">
    356360<a name="annex">
    357361<p><h3>F - Annex</h3></p>
     
    364368F - 3. <a href=#rtigs>RTIGS</a><br>
    365369&nbsp; &nbsp; &nbsp; F - 3.1 <a href=#soc>SOC</a>
    366 &nbsp; [<a href=#back_contents>Back</a>]<br>
    367370</p>
    368371<br>
     
    391394<li>Considering security needs; stream providers and users don't necessarily get into contact, streams often not blocked by firewalls or proxy servers protecting Local Area Networks.</li>
    392395<li>Enables streaming over mobile IP networks because of using TCP/IP.</li>
    393 &nbsp; [<a href=#back_annex>Back</a>]<br>
    394396</ul>
    395397</p><br>
     
    407409<p>
    408410Sourcetable records of type NET contain the following data fields: 'identifiey', 'operator', 'authentication', 'fee', 'web-net', 'web-str', 'web-reg', 'misc'.
    409 &nbsp; [<a href=#back_annex>Back</a>]<br>
    410411</p>
    411412
     
    417418<p>
    418419Copies of RTCM Recommended Standards can be ordered through <u>http://www.rtcm.org/orderinfo.php</u>.
    419 &nbsp; [<a href=#back_annex>Back</a>]<br>
    420420</p>
    421421<br>
     
    451451<li>
    452452Type 19 and 21 messages are the uncorrected pseudo-range measurements and pseudo-range corrections used in RTK.
    453 &nbsp; [<a href=#back_annex>Back</a>]<br>
    454453</li>
    455454</ul>
     
    481480<li>Type 1020, GLONASS Ephemeris (under development).</li>
    482481<li>Type 4088 and 4095, Proprietary messages (under development).
    483 &nbsp; [<a href=#back_annex>Back</a>]<br>
    484482</li>
    485483</ul>
     
    489487<p>
    490488Input from Ken?
    491 &nbsp; [<a href=#back_annex>Back</a>]<br>
    492489</p>
    493490
     
    496493<p>
    497494Input from Ken?
    498 &nbsp; [<a href=#back_annex>Back</a>]<br>
    499 </p>
    500 <p>
    501 &nbsp; [<a href=#back_contents>Back</a>]<br>
    502 </p>
    503 
    504 
    505 
    506 
     495</p>
     496<p>
     497</p>
     498
     499
     500
     501
Note: See TracChangeset for help on using the changeset viewer.