Changeset 9092 in ntrip


Ignore:
Timestamp:
Sep 3, 2020, 12:16:48 PM (2 weeks ago)
Author:
stuerze
Message:

feed engine output changed: bnchelp is adapted accordingly

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/src/bnchelp.html

    r9006 r9092  
    26842684
    26852685<p>
    2686 Each epoch in the synchronized output begins with a line containing the GPS Week Number and the seconds within the GPS Week. Following lines begin with the mountpoint string of the stream which provides the observations followed by a satellite number. Specifications for satellite number, code, phase, Doppler and signal strength data follow definitions presented in the RINEX Version 3 documentation. In case of phase observations, a 'Lock Time Indicator' is added. The end of an epoch is indicated by an empty line.
    2687 </p>
    2688 
    2689 <p>
    2690 A valid 'Lock Time Indicator' is only presented for observations from RTCM Version 3 streams. The parameter provides a measure of the amount of time that has elapsed during which the receiver has maintained continuous lock on that satellite signal. If a cycle slip occurs during the previous measurement cycle, the lock indicator will be reset to Zero. In case of observations from RTCM Version 2 streams, the 'Lock Time Indicator' is always set to '-1'.
    2691 </p>
    2692 
    2693 <p>
    2694 An optional valid 'Lock Time' is only presented for observations from RTCM Version 3 streams. The parameter provides a measure of the amount of time that has elapsed during which the receiver has maintained continuous lock on that satellite signal. If a cycle slip occurs during the previous measurement cycle, the lock time will be reset to Zero. The 'Lock Time' could be of interest becuase the Lock Time Inficator is different for different RTCM3 measurement types. Hence, the 'Lock Time' in seconds is computed with the respective calculation rule.
     2686Each epoch in the synchronized output begins with a line containing the GPS Week Number and the seconds within the GPS Week. Following lines begin with the mountpoint string of the stream which provides the observations followed by a satellite number. Specifications for satellite number, code, phase, doppler and signal strength data follow definitions presented in the RINEX Version 3 documentation. In case of phase observations, a 'Slip Counter' is added. The end of an epoch is indicated by an empty line.
     2687</p>
     2688
     2689<p>
     2690A valid 'Slip Counter' is only presented for observations from RTCM Version 2 streams (Cummulative Loss of Lock Indicator). In RTCM Version 3 streams a 'Lock Time Indicator' is available instead. This parameter indicates a measure of the amount of time that has elapsed during which the receiver has maintained continuous lock on that satellite signal. If a cycle slip occurs during the previous measurement cycle, the 'Lock Time Indicator' will be reset to zero. But, this 'Lock Time Indicator' ist defined with different resolution for different RTCM version 3 observation types (MSMi, legacy messages).
     2691</p>
     2692
     2693<p>
     2694From the RTCM version 3 'Lock Time Indicator' a valid 'Lock Time' can be computed with the respective calculation rule. This parameter provides a measure of the amount of time that has elapsed during which the receiver has maintained continuous lock on that satellite signal in seconds. If a cycle slip occurs during the previous measurement cycle, the 'Lock Time' will decrease. This information will be used, to provide a 'Slip Counter' for RTCM Version 3 observations as well.  With it, we have an output format that is independent from the RTCM version of the observations. The 'Lock Time' output can be activated optional.
    26952695</p>
    26962696
     
    27252725<tr><td>Observation Code</td><td><b>L</b>1C</td><td>1X,A3</td></tr>
    27262726<tr><td>Carrier Phase Observation</td><td>133446552.870</td><td>1X,F14.3</td></tr>
    2727 <tr><td>Lock Time Indicator</td><td>11</td><td>1X,I4</td></tr>
     2727<tr><td>Slip Counter</td><td>11</td><td>1X,I4</td></tr>
    27282728
    27292729<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
     
    27392739<tr><td>Observed Signal Strength &nbsp; &nbsp;</td><td>34.750</td><td>1X,F8.3</td></tr>
    27402740
    2741 <tr><td><u>Lock Time (optional)</u></td><td></td><td></td></tr>
     2741<tr><td>&nbsp;</td><td>&nbsp;</td><td>&nbsp;</td></tr>
     2742
     2743<tr><td><b>Lock Time (optional)</b></td><td></td><td></td></tr>
    27422744<tr><td>Observation Code</td><td><b>T</b>2W</td><td>1X,A3</td></tr>
    27432745<tr><td>Computed Lock Time &nbsp; &nbsp;</td><td>937.000</td><td>1X,F8.3</td></tr>
Note: See TracChangeset for help on using the changeset viewer.