Changeset 2705 in ntrip


Ignore:
Timestamp:
Nov 17, 2010, 1:41:26 PM (13 years ago)
Author:
weber
Message:

Section on feeding an engine updated

File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r2700 r2705  
    5555<ul>
    5656<li>RTCM Version 2.x containing message types 18 and 19 or 20 and 21 together with 3 and 22 (GPS and GLONASS), </li>
    57 <li>RTCM Version 3.x containing message types 1002 (GPS, SBAS) or 1004 (GPS), 1010 or 1012 (GLONASS), 1019 or 1020 (broadcast ephemeris), 1057-1068 (premature State Space Representation messages for GPS and GLONASS)</li>
     57<li>RTCM Version 3.x containing message types 1002 (GPS, SBAS) or 1004 (GPS), 1010 or 1012 (GLONASS), 1019 or 1020 (GPS or GLONASS broadcast ephemeris), or the proposed State Space Representation messages for GPS and GLONASS type 1057-1068, or the proposed 'Multiple Signal Messages' (MSM) for GPS, GLONASS or Galileo type 1071-1077, 1081-1087, or 1091-1097.</li>
    5858<li>RTIGS containing GPS record types 200 (observations) and 300 (ephemeris).</li>
    5959</ul>
    … …  
    705705<p><a name="syncout"><h4>3.7. Feed Engine</h4></p>
    706706<p>
    707 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. It comprises the following observations where available:</p>
    708 <p>
    709 StatID, SVPRN, GPSWeek, GPSWeeks, C1, C2, P1, P2, L1, L2, slip_cnt_L1, slip_cnt_L2, lock_timei_L1, lock_timei_L2, S1, S2, SNR1, SNR2
    710 </p>
    711 <p>
    712 Note that slip_cnt stands for the cumulative loss of continuity indicator, lock_timei for the lock time indicator, and SNR for the signal-to-noise ratio 'S' mapped to integer numbers 1 to 9. In case an observation is not available, its value is set to zero '0.000'. Loss of continuity indicator and lock time indicator are set to negative values if undefined.
     707BNC 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 StatID, GPSWeek, GPSWeekSeconds and SVPRN it comprises the following observations where available:
     708<ul>
     709<li>For GPS satellites, 'G':   20 C1C L1C D1C S1C C1W L1W D1W S1W C2P L2P D2P S2P C2X L2X D2X S2X C5  L5  D5  S5</li>
     710<li>For GLONASS satellites, 'R':   16 C1C L1C D1C S1C C1P L1P D1P S1P C2P L2P D2P S2P C2C L2C D2C S2C</li>
     711<li>For Geostationary signal payloads, 'S': C1C L1C D1C S1C C1W L1W D1W S1W</li>
     712<li>For Galileo satellites, 'E': C1  L1  D1  S1  C5  L5  D5  S5</li>
     713</ul>
     714In case an observation is not available, its value is set to zero '0.000'.
    713715</p>
    714716
    … …  
    13571359<p><a name="gettable"><h4>3.14.1.4 Get Table</h4></p>
    13581360<p>
    1359 Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example source-table.
     1361Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004, or GLONASS message types 1010 or 1012, or the proposed State Space Representation messages for GPS and GLONASS type 1057-1068, or the proposed 'Multiple Signal Messages' (MSM) for GPS, GLONASS or Galileo type 1071-1077, 1081-1087, or 1091-1097, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary. The figure below provides an example source-table.
    13601362</p>
    13611363<p>
    … …  
    15361538</li>
    15371539<li>
    1538 Using RTCM Version 3.x, BNC will properly handle message types 1002, 1004, 1010, and 1012. Note that when handling message types 1001, 1003, 1009 and 1011 where the ambiguity field is not set, the output will be no valid RINEX. All values will be stored modulo 299792.458 (speed of light).
     1540Using RTCM Version 3.x, BNC will properly handle message types 1002, 1004, 1010, and 1012, or the proposed State Space Representation messages for GPS and GLONASS type 1057-1068, or the proposed 'Multiple Signal Messages' (MSM) for GPS, GLONASS or Galileo type 1071-1077, 1081-1087, or 1091-1097. Note that when handling message types 1001, 1003, 1009 and 1011 where the ambiguity field is not set, the output will be no valid RINEX. All values will be stored modulo 299792.458 (speed of light).
    15391541</li>
    15401542Concerning 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 solutions.
    … …  
    18191821
    18201822<p>
    1821 The following are proposed 'Multiple System Messages' (MSM) under discussion for standardization:
     1823The following are proposed 'Multiple Signal Messages' (MSM) under discussion for standardization:
    18221824<ul>
    18231825<li>Type 1071, Compact GPS pseudo-ranges</li>
Note: See TracChangeset for help on using the changeset viewer.