Changeset 2840 in ntrip


Ignore:
Timestamp:
Dec 27, 2010, 9:49:54 PM (13 years ago)
Author:
weber
Message:

'Feed Engine' section modified

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r2835 r2840  
    212212&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.14.1.4 <a href=#gettable>Get Table</a><br>
    213213&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.14.1.5 <a href=#ntripv>NTRIP Version</a><br>
     214&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 3.14.1.6 <a href=#map>Map</a><br>
    214215&nbsp; &nbsp; &nbsp; 3.14.2 <a href=#streamip>Add Stream - Coming from TCP/IP Port</a><br>
    215216&nbsp; &nbsp; &nbsp; 3.14.3 <a href=#streamudp>Add Stream - Coming from UDP Port</a><br>
    … …  
    447448<p><a name="ephemeris"><h4>3.5. RINEX Ephemeris</h4></p>
    448449<p>
    449 Broadcast ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3.x as message types 1019 (GPS) or 1020 (GLONASS) or 1045 (drafted, Galileo) or via RTIGS records type 300. The file name convention follows the details given in section 'RINEX File Names' except that the first four characters are 'BRDC' and the last character is
     450Broadcast ephemeris can be saved as RINEX Navigation files when received via RTCM Version 3.x as message types 1019 (GPS) or 1020 (GLONASS) or 1045 (proposed, Galileo) or via RTIGS records type 300. The file name convention follows the details given in section 'RINEX File Names' except that the first four characters are 'BRDC' and the last character is
    450451</p>
    451452<ul>
    452453<li>'N' or 'G' for GPS or GLONASS ephemeris in two separate RINEX Version 2.11 Navigation files, or</li>
    453 <li>'P' for GPS plus GLONASS ephemeris saved together in one RINEX Version 3 Navigation file.
     454<li>'P' for GPS plus GLONASS plus Galileo ephemeris saved together in one RINEX Version 3 Navigation file.
    454455</ul>
    455456
    … …  
    727728<p><a name="syncout"><h4>3.7. Feed Engine</h4></p>
    728729<p>
    729 BNC can generate synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed a real-time GNSS network engine. The output can be produced in a binary format through an IP port and/or a plain ASCII format to save the observations in a local file. Following StationID, GPSWeek, GPSWeekSeconds and SV-PRN it comprises the following observations where available:
    730 <ul>
    731 <li>For GPS satellites, 'G': C1C L1C D1C S1C C1W L1W D1W S1W C2P L2P D2P S2P C2X L2X D2X S2X C5  L5 D5  S5</li>
    732 <li>For GLONASS satellites, 'R': C1C L1C D1C S1C C1P L1P D1P S1P C2P L2P D2P S2P C2C L2C D2C S2C</li>
    733 <li>For Geostationary signal payloads, 'S': C1C L1C D1C S1C C1W L1W D1W S1W</li>
    734 <li>For Galileo satellites, 'E': C1  L1  D1  S1  C5  L5 D5  S5</li>
     730BNC can generate synchronized or unsynchronized observations epoch by epoch from all stations and satellites to feed a real-time GNSS network engine. Observations can be streamed out through an IP port and/or saved in a local file. The output is always in plain ASCII format and comprises the following parameters:
     731<ul>
     732<li>For GPS satellites:<br>StationID GPSWeek GPSWeekSec 'G'PRN C1C L1C SlipCountL1 D1C S1C C1W L1W SlipCountL1 D1W S1W C2P L2P SlipCountL2 D2P S2P C2X L2X SlipCountL2 D2X S2X C5  L5 SlipCountL5 D5  S5</li>
     733<li>For GLONASS satellites:<br>StationID GPSWeek GPSWeekSec 'R'PRN SlotNumber C1C L1C SlipCountL1 D1C S1C C1P L1P SlipCountL1 D1P S1P C2P L2P SlipCountL2 D2P S2P C2C L2C SlipCountL2 D2C S2C</li>
     734<li>For Geostationary signal payloads:<br>StationID GPSWeek GPSWeekSec 'S'PRN C1C L1C SlipCountL1 D1C S1C C1W L1W SlipCountL1 D1W S1W</li>
     735<li>For Galileo satellites:<br>StationID GPSWeek GPSWeekSec 'E'PRN C1  L1  SlipCountL1 D1  S1  C5  L5 SlipCountL5 D5  S5</li>
    735736</ul>
    736737In case an observation is not available, its value is set to zero '0.000'.
    737738</p>
    738739
    739 <p>The binary output is a continuous stream in the following order:</p>
     740<p>
     741The following is an output examples for GPS, GLONASS and Galileo satellites and a geostationary payload signal:
    740742<pre>
    741 begEpoch
    742 t_obsInternal
    743 t_obsInternal
    744 ...
    745 t_obsInternal
    746 endEpoch
    747 begEpoch
    748 t_obsInternal
     743...
     744WTZX3 1616 149732.0000000 E52  27089285.092   142354765.663 -1       2212.322          45.500    27089287.942   106304461.365 -1       2212.404          42.300
     745...
     746WTZX3 1616 149732.0000000 G10  22608910.719   118810687.059 -1       2965.339          49.300    22608909.593   118810311.312 -1       2965.339          36.000    22608915.003    92579465.057 -1       2966.012          36.000           0.000           0.000 -1          0.000           0.000           0.000           0.000 -1          0.000           0.000
     747...
     748WTZX3 1616 149732.0000000 G07  23633028.684   124192961.644 -1       3686.418          48.800    23633026.847   124192961.885 -1       3686.418          35.000    23633032.480    96773737.419 -1       3685.139          35.000    23633033.547    96773738.190 -1       3685.172          43.500           0.000           0.000 -1          0.000           0.000
     749...
     750WTZX3 1616 149732.0000000 R20 2   24149338.926   129137949.211 48       2950.111          42.800    24149340.305   129137949.481 48       2950.111          41.800    24149356.146   100440627.082 48       2949.895          39.500    24149356.702   100440626.859 48       2949.896          40.000
    749751...
    750752</pre>
    751 
    752 <p>The corresponding structures are defined as follow:</p>
    753 <pre>
    754   const char begEpoch[] = &quot;BEGEPOCH&quot;;
    755   const char endEpoch[] = &quot;ENDEPOCH&quot;;
    756 ...
    757 ...
    758 class t_obsInternal {
    759  public:
    760   int    flags;
    761   char   StatID[20+1];  // Station ID
    762   char   satSys;        // Satellite System ('G' for GPS or 'R' for GLONASS or 'S' for Geostationary signal payload)
    763   int    satNum;        // Satellite Number (PRN for GPS NAVSTAR)
    764   int    slot;          // Slot Number (for Glonass)
    765   int    GPSWeek;       // Week of GPS-Time
    766   double GPSWeeks;      // Second of Week (GPS-Time)
    767   double C1;            // CA-code pseudorange (meters)
    768   double C2;            // CA-code pseudorange (meters)
    769   double P1;            // P1-code pseudorange (meters)
    770   double P2;            // P2-code pseudorange (meters)
    771   double L1;            // L1 carrier phase (cycles)
    772   double L2;            // L2 carrier phase (cycles)
    773   int    slip_cnt_L1;   // L1 cumulative loss of continuity indicator (negative value = undefined)
    774   int    slip_cnt_L2;   // L2 cumulative loss of continuity indicator (negative value = undefined)
    775   int    lock_timei_L1; // L1 last lock time indicator                (negative value = undefined)
    776   int    lock_timei_L2; // L2 last lock time indicator                (negative value = undefined)
    777   double S1;            // L1 signal-to noise ratio
    778   double S2;            // L2 signal-to noise ratio
    779   int    SNR1;          // L1 signal-to noise ratio (mapped to integer)
    780   int    SNR2;          // L2 signal-to noise ratio (mapped to integer)
    781 };
    782 </pre>
    783 
    784 <p>
    785 The source code for BNC comes with an example program called 'test_bnc_qt.cpp' that allows you to read BNC's (synchronized or unsynchronized) binary observation output from the IP port and print the observations in a plain ASCII format on standard output.
     753<p>
     754The source code for BNC comes with a perl script called 'test_tcpip_client.pl' that allows you to read BNC's (synchronized or unsynchronized) ASCII observation output from the IP port and print it on standard output.
    786755</p>
    787756<p>
    … …  
    790759
    791760<p>
    792 The following figure shows the screenshot of a BNC configuration where a number if streams is pulled from different NTRIP broadcasters to feed a GNSS engine via IP port output.
     761The following figure shows the screenshot of a BNC configuration where a number of streams is pulled from different NTRIP broadcasters to feed a GNSS engine via IP port output.
    793762</p>
    794763<p><img src=":bnchelp/screenshot12.png"/></p>
    … …  
    797766<p><a name="syncport"><h4>3.7.1 Port - optional</h4></p>
    798767<p>
    799 BNC can produce synchronized observations in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Synchronized means that BNC collects all data for any specific epoch which become available within a certain number of latency seconds (see 'Wait for Full Epoch' option). It then - epoch by epoch - outputs whatever has been received. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary synchronized output is generated.</p>
     768BNC can produce synchronized observations in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Synchronized means that BNC collects all data for any specific epoch which become available within a certain number of latency seconds (see 'Wait for Full Epoch' option). It then - epoch by epoch - outputs whatever has been received. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary synchronized output is generated.</p>
    800769</p>
    801770
    … …  
    823792<p><a name="syncuport"><h4>3.7.5 Port (unsynchronized) - optional</h4></p>
    824793<p>
    825 BNC can produce unsynchronized observations from all configured streams in binary format on your local host (IP 127.0.0.1) through an IP 'Port'. Unsynchronized means that BNC immediately forwards any received observation to the port. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary unsynchronized output is generated.</p>
     794BNC can produce unsynchronized observations from all configured streams in ASCII format on your local host (IP 127.0.0.1) through an IP 'Port'. Unsynchronized means that BNC immediately forwards any received observation to the port. Specify an IP port number here to activate this function. The default is an empty option field, meaning that no binary unsynchronized output is generated.</p>
    826795<p>
    827796
    … …  
    10471016<ul>
    10481017<li>a stream carrying satellite orbit and clock corrections to Broadcast Ephemeris in the form of 'State Space Representation' (SSR) messages as proposed by RTCM (i.e. premature message type 1060). Note that for BNC these correctors need to be referred to the satellite's Antenna Phase Center (APC). Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/orbits</u>. Stream products.igs-ip.net:2101/CLK11 is an example.</li>
    1049 <li>a stream carrying Broadcast Ephemeris available as RTCM Version 3 message types 1019, 1020, and (drafted) 1045. This is a must only when the stream coming from the receiver does not contain Broadcast Ephemeris or provides them only at very low repetition rate. Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>. Stream RTCM3EPH on caster products.igs-ip.net:2101 is an example.</li>
     1018<li>a stream carrying Broadcast Ephemeris available as RTCM Version 3 message types 1019, 1020, and (proposed) 1045. This is a must only when the stream coming from the receiver does not contain Broadcast Ephemeris or provides them only at very low repetition rate. Streams providing such messages are listed on <u>http://igs.bkg.bund.de/ntrip/ephemeris</u>. Stream RTCM3EPH on caster products.igs-ip.net:2101 is an example.</li>
    10501019</ul>
    10511020</p>
    … …  
    14301399
    14311400<p>
    1432 Button 'Add Stream' &gt; 'Coming from Caster' then opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints.
     1401Button 'Add Stream' &gt; 'Coming from Caster' then opens a window that allows user to select data streams from an NTRIP broadcaster according to their mountpoints and show a distribution map of offered streams.
    14331402</p>
    14341403
    … …  
    14931462<p>
    14941463Select option '1' if you are not sure whether the broadcaster supports NTRIP version 2.</li>
     1464</p>
     1465
     1466<p><a name="map"><h4>3.14.1.6 Map - optional</h4></p>
     1467<p>
     1468Button 'Map' opens a window to show a distribution map of the casters's streams. You may like to zoom in or out using option 'Zoom +' or 'Zoom -'. You may also like to 'Clean' or 'Reset' a map or let it 'Fit' exactly to the current size of the window. Option 'Close' shuts the window.
    14951469</p>
    14961470
    … …  
    16471621</li>
    16481622<li>Concerning the RTCM Version 3.x premature message types 1057-1068 (see RTCM document 091-2009-SC104-542 'Version 3 Proposed Messages - Set 10'), a final decision is not yet made. Note the what's implemented in BNC is just a temporary solution.</li>
    1649 <li>Concerning the RTCM Version 3.x premature message types 1071-1077, 1081-1087, 1091-1097 (see RTCM document 086-2010-SC104-587 'New RTCM-3 Multiple Signal Message Proposal for GPS, GLONASS and GALILEO'), a final decision is not yet made. Note the what's implemented in BNC is just a temporary solution.</li>
     1623<li>Concerning the RTCM Version 3.x premature message types 1071-1077, 1081-1087, 1091-1097 (see RTCM document 086-2010-SC104-587 'New RTCM-3 Multiple Signal Message Proposal for GPS, GLONASS and Galileo'), a final decision is not yet made. Note that what is implemented in BNC is just a temporary solution.</li>
    16501624<li>
    16511625Using RTCM Version 2.x, BNC will only handle message types 18 and 19 or 20 and 21 together with position and the antenna offset information carried in types 3 and 22. Note that processing carrier phase corrections and pseudo-range corrections contained in message types 20 and 21 needs access to broadcast ephemeris. Hence, whenever dealing with message types 20 and 21, make sure that broadcast ephemeris become available for BNC through also retrieving at least one RTCM Version 3.x stream carrying message types 1019 (GPS ephemeris) and 1020 (GLONASS ephemeris).
    … …  
    16991673Zdenek Lukes, Czech Technical University Prague, Department of Geodesy, extended the RTCMv2 decoder to handle message types 3, 20, 21, and 22 and added loss of lock indicator.<br>
    17001674Jan Dousa, Geodetic Observatory Pecny, Czech Republic, provided a tool for drawing stream distribution maps and also helped with fixing bugs.<br>
     1675Denis Laurichesse, Centre National d'Etudes Spatiales (CNES), suggested to synchronize observations and clock corrections to reduce high frequency noise in PPP solutions.
    17011676</p>
    17021677
    … …  
    19461921<li>Type 1086, Full GLONASS pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
    19471922<li>Type 1087, Full GLONASS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br></li>
    1948 <li>Type 1091, Compact GALILEO pseudo-ranges</li>
    1949 <li>Type 1092, Compact GALILEO carrier phases</li>
    1950 <li>Type 1093, Compact GALILEO pseudo-ranges and carrier phases</li>
    1951 <li>Type 1094, Full GALILEO pseudo-ranges and carrier phases plus signal strength</li>
    1952 <li>Type 1095, Full GALILEO pseudo-ranges, carrier phases, Doppler and signal strength</li>
    1953 <li>Type 1096, Full GALILEO pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
    1954 <li>Type 1097, Full GALILEO pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br></li>
     1923<li>Type 1091, Compact Galileo pseudo-ranges</li>
     1924<li>Type 1092, Compact Galileo carrier phases</li>
     1925<li>Type 1093, Compact Galileo pseudo-ranges and carrier phases</li>
     1926<li>Type 1094, Full Galileo pseudo-ranges and carrier phases plus signal strength</li>
     1927<li>Type 1095, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength</li>
     1928<li>Type 1096, Full Galileo pseudo-ranges and carrier phases plus signal strength (high resolution)</li>
     1929<li>Type 1097, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)<br></li>
    19551930</ul>
    19561931</p>
Note: See TracChangeset for help on using the changeset viewer.