Index: trunk/BNC/src/bnchelp.html =================================================================== --- trunk/BNC/src/bnchelp.html (revision 4726) +++ trunk/BNC/src/bnchelp.html (revision 4728) @@ -48,12 +48,14 @@ -

+
  • RTCM 3 decoder for conventional ans MSM observation messages and a RTCM 3 encoder & decoder for SSR messages, both written for BKG by Dirk Stoecker, Alberding GmbH, Schoenefeld, Germany
    • + +

    +

    +Note that some figures presented in this documentation show screenshots from earlier version of BNC. If so then there was no relevant change in the contents or no change at all.

    Acknowledgements
    -Earlier versions of BNC's Help Contents have been proofread by Thomas Yan, University of New South Wales, Australia. He also provided pre-compiled builds of BNC for Mac systems.
    +Earlier versions of BNC's Help Contents have been proofread by Thomas Yan, University of New South Wales, Australia. He also provides builds of BNC for Mac systems.
    Scott Glazier, OmniSTAR Australia has been helpful in finding BNC's bugs.
    James Perlt, BKG, helped fixing bugs and redesigned BNC's main window.
    @@ -99,6 +101,6 @@

    @@ -117,5 +119,5 @@

    -Note further that BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files. +Note also that BNC allows to by-pass its decoding and conversion algorithms, leave whatever is received untouched and save it in files.

    @@ -669,6 +671,4 @@ and hence follows UNAVCO's famous 'TEQC' program. The remarkable thing about BNC in this context is that it supports RINEX Version 3 under GNU General Public License.

    -

    -

    Figure 7:Example for satellite availability, elevation and PDOP plots.

    3.6.1 Action - optional

    @@ -698,5 +698,5 @@

    -

    Figure 8: Example for 'RINEX Editing Options' window.

    +

    Figure 7: Example for 'RINEX Editing Options' window.

    3.6.3 Input Files - mandatory if 'Action' is set

    @@ -712,16 +712,38 @@

    -

    Figure 9: Example for RINEX file editing with BNC in Post Processing mode.

    - -

    -If 'Analyze' is selected, specifying a 'Log' file to output analysis results is mandatory.
    -

    +

    Figure 8: Example for RINEX file editing with BNC in Post Processing mode.

    + +

    +If 'Analyze' is selected, specifying a 'Log' file to output analysis results is mandatory. The following is a RINEX quality check analysis logfile example: +

    +Analyze File
+------------
+File:            cut02530.12o
+Marker name:     CUT0
+Receiver:        TRIMBLE NETR9
+Antenna:         TRM59800.00     SCIS
+Start time:      2012-09-09 00:00:00.000
+End time:        2012-09-09 23:59:30.000
+Interval:        30
+# Sat.:          56
+# Obs.:          54159
+# Slips (file):  295
+# Slips (found): 52
+Mean MP1:        0.25382
+Mean MP2:        0.163092
+Mean SNR1:       4.83739
+Mean SNR2:       5.09455
+
    +

    + +

    3.6.5 Directory for Plots - optional if 'Action' is set

    +

    +If 'Analyze' is selected, specifying the path to a directory where plot files will be saved is optional. File names will be composed from the RINEX input file name(s) plus suffix 'PNG' to indicate the plot file format in use.

    -

    Figure 10: Example for RINEX quality check output with BNC in Post Processing mode. A multipath and a signal-to-noise ratio analysis are presented in terms of a sky plot.

    - -

    3.6.5 Directory for Plots - optional if 'Action' is set

    -

    -If 'Analyze' is selected, specifying the path to a directory where plot files will be saved is optional. File names will be composed from the RINEX input file name(s) plus suffix 'PNG' to indicate the plot file format in use.

    +

    Figure 9: Example for RINEX quality check graphics output with BNC. A multipath and a signal-to-noise ratio analysis are presented in terms of a sky plot.

    + +

    +

    Figure 10: Example for satellite availability, elevation and PDOP plots as a result of a RINEX quality check with BNC.

    3.6.6 Command Line, No Window - optional

    @@ -773,4 +795,5 @@ reqcOutNavFileRINEX Navigation output file reqcOutLogFileLogfile +reqcPlotDirPlot file directory reqcRnxVersionRINEX version of emerging new file reqcSamplingSampling interval of emerging new RINEX file @@ -2823,18 +2846,25 @@
  • Type 1096, Full Galileo pseudo-ranges and carrier phases plus signal strength (high resolution)
  • Type 1097, Full Galileo pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)

    • -
  • Type 4021, Compact SBAS pseudo-ranges
    • -
  • Type 4022, Compact SBAS carrier phases
    • -
  • Type 4023, Compact SBAS pseudo-ranges and carrier phases
    • -
  • Type 4024, Full SBAS pseudo-ranges and carrier phases plus signal strength
    • -
  • Type 4025, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength
    • -
  • Type 4026, Full SBAS pseudo-ranges and carrier phases plus signal strength (high resolution)
    • -
  • Type 4027, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)

    • -
  • Type 4031, Compact QZSS pseudo-ranges
    • -
  • Type 4032, Compact QZSS carrier phases
    • -
  • Type 4033, Compact QZSS pseudo-ranges and carrier phases
    • -
  • Type 4034, Full QZSS pseudo-ranges and carrier phases plus signal strength
    • -
  • Type 4035, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength
    • -
  • Type 4036, Full QZSS pseudo-ranges and carrier phases plus signal strength (high resolution)
    • -
  • Type 4037, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)
    • +
  • Type 1101, Compact SBAS pseudo-ranges
    • +
  • Type 1102, Compact SBAS carrier phases
    • +
  • Type 1103, Compact SBAS pseudo-ranges and carrier phases
    • +
  • Type 1104, Full SBAS pseudo-ranges and carrier phases plus signal strength
    • +
  • Type 1105, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength
    • +
  • Type 1106, Full SBAS pseudo-ranges and carrier phases plus signal strength (high resolution)
    • +
  • Type 1107, Full SBAS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)

    • +
  • Type 1111, Compact QZSS pseudo-ranges
    • +
  • Type 1112, Compact QZSS carrier phases
    • +
  • Type 1113, Compact QZSS pseudo-ranges and carrier phases
    • +
  • Type 1114, Full QZSS pseudo-ranges and carrier phases plus signal strength
    • +
  • Type 1115, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength
    • +
  • Type 1116, Full QZSS pseudo-ranges and carrier phases plus signal strength (high resolution)
    • +
  • Type 1117, Full QZSS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)

    • +
  • Type 1121, Compact COMPASS pseudo-ranges
    • +
  • Type 1122, Compact COMPASS carrier phases
    • +
  • Type 1123, Compact COMPASS pseudo-ranges and carrier phases
    • +
  • Type 1124, Full COMPASS pseudo-ranges and carrier phases plus signal strength
    • +
  • Type 1125, Full COMPASS pseudo-ranges, carrier phases, Doppler and signal strength
    • +
  • Type 1126, Full COMPASS pseudo-ranges and carrier phases plus signal strength (high resolution)
    • +
  • Type 1127, Full COMPASS pseudo-ranges, carrier phases, Doppler and signal strength (high resolution)

    • @@ -2865,71 +2895,78 @@
      +
    1. File 'RinexObs.bnc'
      -The purpose of this configuration is to convert RTCM streams to RINEX Observation files. The configuration pulls streams from several NTRIP Broadcasters using different Ntrip versions and generate 15min 1Hz RINEX Version 3 Observation files. See http://igs.bkg.bund.de/ntrip/observations for observation stream resources. +The purpose of this configuration is to convert RTCM streams to RINEX Observation files. The configuration pulls streams from several Ntrip Broadcasters using different Ntrip versions and generate 15min 1Hz RINEX Version 3 Observation files. See http://igs.bkg.bund.de/ntrip/observations for observation stream resources. +

      2. + +
    2. File 'RinexEph.bnc'
      +The purpose of this configuration is to convert RTCM streams to RINEX Navigation files. The configuration pulls an RTCM Version 3 stream carrying Broadcast Ephemeris coming from the real-time EUREF and IGS network. It saves hourly RINEX Version 3 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast Ephemeris resources. +

      3. + +
    3. File 'SSR.bnc'
      +The purpose of this configuration is to save Broadcast Corrections from RTCM SSR messages in a plain ASCII format as hourly files. See http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF orbit/clock products. + +

      4. +
    4. File 'RinexConcat.bnc'
      +The purpose of this configuration is to concatenate RINEX Version 3 files to produce a concatenated file and edit the marker name in the file header. The sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the documentation for examples on how to call BNC from command line in 'no window' mode for RINEX file editing, concatenation and quality checks. +

      5. + +
    5. File 'RinexQC.bnc'
      +The purpose of this configuration is to check the quality of a RINEX Version 3 file through a multipath analysis. The results is saved in disk in terms of a plot in PNG format. See section 'RINEX Editing & QC' in the documentation for examples on how to call BNC from command line in 'no window' mode for RINEX file editing, concatenation and quality checks. +

      6. + +
    6. File 'RTK.bnc'
      +The purpose of this configuration is to feed a serial connected receiver with observations from a reference station for conventional RTK. The stream is scanned for RTCM messages. Message type numbers and latencies of incoming observation are reported in BNC's logfile. +

      7. + +
    7. File 'FeedEngine.bnc'
      +The purpose of this configuration is to feed a real-time GNSS engine with observations from a number of remote reference stations. The configuration pulls streams provided in various formats from different Ntrip Broadcasters. Incoming observations are decoded, synchronized and output through a local IP port and saved into a file. Failure and recovery thresholds are specified to inform about outages. +

      8. + +
    8. File 'PPP.bnc'
      +The purpose of this configuration is Precise Point Positioning from observations of a rover receiver. The configuration reads RTCM Version 3 observations, a stream of Broadcast Corrections and a Broadcast Ephemeris stream. Positions are saved in the logfile. +

      9. + +
    9. File 'PPPQuickStart.bnc'
      +The purpose of this configuration is Precise Point Positioning in Quick-Start mode from observations of a static receiver with precisely known position. The configuration reads RTCM Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream. Positions are saved in NMEA format on disc. Positions are also output through IP port for real-time visualization with tools like RTKPLOT. +

      10. + +
    10. File 'PPPPostProc.bnc'
      +The purpose of this configuration is Precise Point Positioning in Post +

      11. +Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation files and a Broadcast Corrections files. PPP processing otions are set to support the Quick-Start mode. The output is saved in a specific Post Processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm. + +
    11. File 'SPPQuickStartGal.bnc'
      +The purpose of this configuration is Single Point Positioning in Quick-Start mode from observations of a static receiver with precisely known position. The configuration uses GPS, GLONASS and Galileo observertions and a Broadcast Ephemeris stream. +

      12. + +
    12. File 'Sp3.bnc'
      +The purpose of this configuraiton is to produce SP3 files from a Broadcast Ephemeris stream and a Broadcast Corrections stream. Note that this requires an ANTEX file because SP3 file contents should be referred to CoM. +

      13. + +
    13. File 'Sp3ETRF2000PPP.bnc'
      +The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. This leads to an SP3 file containing orbits referred also to ETRF2000. Pulling in addition observations from a reference station at precisely known ETRF2000 position allows to compare an 'INTERNAL' PPP solution with ETRF2000 reference coordinates. +

      14. + +
    14. File 'Upload.bnc'
      +The purpose of this configuration is to upload orbits and clocks from a real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads precise orbits and clocks in RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast Corrections and encodes them in RTCM Version 3 SSR messages to uploads them to an Ntrip Broadcaster. The Broadcast Corrections stream is referred to satellite Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format and clocks in Clock RINEX format. +

      15. + +
    15. File 'UploadPPP.bnc'
      +This configuration equals the 'Upload.bnc' configuration. However, the Broadcast Corrections are in addition used for an 'INTERNAL' PPP soltution based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the Broadcast Corrections through observing coordinate displacements. +

      16. + +
    16. File 'Combi.bnc'
      +The purpose of this configuration is to pull several streams carrying Broadcast Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the combination product in RTCM Version 3 SSR messages and uploads that to an Ntrip Broadcaster. The Broadcast Corrections stream is not referred to satellite Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format and clocks in Clock RINEX format. +

      17. + +
    17. File 'CombiPPP.bnc'
      +This configuration equals the 'Combi.bnc' configuration. However, the combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the combination product through observing coordinate displacements. +

      18. + +
    18. File 'UploadEph.bnc'
      +The purpose of this configuration is to pull a number of streams from reference stations to get hold of contained Broadcast Ephemeris messages. These are encoded then in a RTCM Version 3 stream which only provides Broadcast Ephemeris with an update rate of 5 seconds.
      19. -
      -
    19. File 'RinexEph.bnc'
      -The purpose of this configuration is to convert RTCM streams to RINEX Navigation files. The configuration pulls an RTCM Version 3 stream carrying Broadcast Ephemeris coming from the real-time EUREF and IGS network. It saves hourly RINEX Version 3 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast Ephemeris resources. -
      20. -
      -
    20. File 'SSR.bnc'
      -The purpose of this configuration is to save Broadcast Corrections from RTCM SSR messages in a plain ASCII format as hourly files. See http://igs.bkg.bund.de/ntrip/orbits for further real-time IGS or EUREF orbit/clock products. -
      21. -
      -
    21. File 'RinexConcat.bnc'
      -The purpose of this configuration is to concatenate RINEX Version 3 files to produce a concatenated file and edit the marker name in the file header. The sampling interval is set to 30 seconds. See section 'RINEX Editing & QC' in the documentation for examples on how to call BNC from command line in 'no window' mode for RINEX file editing, concatenation and quality checks. -
      22. -
      -
    22. File 'RTK.bnc'
      -The purpose of this configuration is to feed a serial connected receiver with observations from a reference station for conventional RTK. The stream is scanned for RTCM messages. Message type numbers and latencies of incoming observation are reported in BNC's logfile. -
      23. -
      -
    23. File 'FeedEngine.bnc'
      -The purpose of this configuration is to feed a real-time GNSS engine with observations from a number of remote reference stations. The configuration pulls streams provided in various formats from different NTRIP Broadcasters. Incoming observations are decoded, synchronized and output through a local IP port and saved into a file. Failure and recovery thresholds are specified to inform about outages. -
      24. -
      -
    24. File 'PPP.bnc'
      -The purpose of this configuration is Precise Point Positioning from observations of a rover receiver. The configuration reads RTCM Version 3 observations, a stream of Broadcast Corrections and a Broadcast Ephemeris stream. Positions are saved in the logfile. -
      25. -
      -
    25. File 'QuickStartPPP.bnc'
      -The purpose of this configuration is Precise Point Positioning in Quick-Start mode from observations of a static receiver with precisely known position. The configuration reads RTCM Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream. Positions are saved in NMEA format on disc. Positions are also output through IP port for real-time visualization with tools like RTKPLOT. -
      26. -
      -
    26. File 'PPPPostProc.bnc'
      -The purpose of this configuration is Precise Point Positioning in Post Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation files and a Broadcast Corrections files. PPP processing options are set to support the Quick-Start mode. The output is saved in a specific Post Processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm. -
      27. -
      -
    27. File 'SPPQuickStartGal.bnc'
      -The purpose of this configuration is Single Point Positioning in Quick-Start mode from observations of a static receiver with precisely known position. The configuration uses GPS, GLONASS and Galileo observations and a Broadcast Ephemeris stream. -
      28. -
      -
    28. File 'Sp3.bnc'
      -The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a Broadcast Corrections stream. Note that this requires an ANTEX file because SP3 file contents should be referred to CoM. -
      29. -
      -
    29. File 'Sp3ETRF2000PPP.bnc'
      -The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. This leads to an SP3 file containing orbits referred also to ETRF2000. Pulling in addition observations from a reference station at precisely known ETRF2000 position allows to compare an 'INTERNAL' PPP solution with ETRF2000 reference coordinates. -
      30. -
      -
    30. File 'Upload.bnc'
      -The purpose of this configuration is to upload orbits and clocks from a real-time GNSS engine to an NTRIP Broadcaster. For that the configuration reads precise orbits and clocks in RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast Corrections and encodes them in RTCM Version 3 SSR messages to uploads them to an NTRIP Broadcaster. The Broadcast Corrections stream is referred to satellite Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format and clocks in Clock RINEX format. -
      31. -
      -
    31. File 'UploadPPP.bnc'
      -This configuration equals the 'Upload.bnc' configuration. However, the Broadcast Corrections are in addition used for an 'INTERNAL' PPP solution based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the Broadcast Corrections through observing coordinate displacements. -
      32. -
      -
    32. File 'Combi.bnc'
      -The purpose of this configuration is to pull several streams carrying Broadcast Corrections and a Broadcast Ephemeris stream from an NTRIP Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the combination product in RTCM Version 3 SSR messages and uploads that to an NTRIP Broadcaster. The Broadcast Corrections stream is not referred to satellite Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format and clocks in Clock RINEX format. -
      33. -
      -
    33. File 'CombiPPP.bnc'
      -This configuration equals the 'Combi.bnc' configuration. However, the combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP solutions based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the combination product through observing coordinate displacements. -
      34. -
      -
    34. File 'UploadEph.bnc'
      -The purpose of this configuration is to pull a number of streams from reference stations to get hold of contained Broadcast Ephemeris messages. These are encoded then in a RTCM Version 3 stream which only provides Broadcast Ephemeris with an update rate of 5 seconds. -
      35. +

    @@ -3043,4 +3080,5 @@ reqcPlotDirReqc: QC plots directory reqcOutLogFile=Reqc: Output logfile +reqcPlotDir=Reqc: Plot file directory reqcRnxVersion=Reqc: RINEX version reqcSampling=Reqc: RINEX sampling