Index: trunk/BNC/bnchelp.html =================================================================== --- trunk/BNC/bnchelp.html (revision 4160) +++ trunk/BNC/bnchelp.html (revision 4161) @@ -60,5 +60,5 @@
  • retrieve real-time GNSS data streams via TCP directly from an IP address without using the NTRIP transport protocol,
  • retrieve real-time GNSS data streams from a local UDP or serial port without using the NTRIP transport protocol,
    • -
  • generate high-rate RINEX Observation and Navigation files to support near real-time GNSS post-processing applications,
    • +
  • generate high-rate RINEX Observation and Navigation files to support near real-time GNSS Post Processing applications,
  • generate ephemeris and synchronized or unsynchronized observations epoch by epoch through an IP port to support real-time GNSS network engines,
  • generate clock and orbit corrections to Broadcast Ephemeris through an IP port to support real-time Precise Point Positioning on GNSS rovers,
    • @@ -123,5 +123,5 @@ Furthermore, apart from its regular window mode, BNC can be run as a batch/background job in a 'no window' mode using processing options from a previously saved configuration or from command line. @@ -398,5 +398,5 @@

    4.3.5 Raw Output File - optional

    -BNC can save all data coming in through various streams in one daily file. The information is recorded in the specified 'Raw output file' in the received order and format. This feature allows a BNC user to run the PPP option offline with observations, Broadcast Corrections, and Broadcast Ephemeris being read from a previously saved file. It supports the offline repetition of a real-time situation for debugging purposes. It is not meant for post-processing. +BNC can save all data coming in through various streams in one daily file. The information is recorded in the specified 'Raw output file' in the received order and format. This feature allows a BNC user to run the PPP option offline with observations, Broadcast Corrections, and Broadcast Ephemeris being read from a previously saved file. It supports the offline repetition of a real-time situation for debugging purposes. It is not meant for Post Processing.

    @@ -628,5 +628,5 @@

    -

    Figure 7: Example for RINEX file editing with BNC in post-processing mode.

    +

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

    4.6.5 Command Line, No Window - optional

    @@ -2275,5 +2275,5 @@

    4.19. Command Line Options

    -Command line options are available to run BNC in 'no window' mode or let it read data offline from one file or several files for debugging or post processing purposes. BNC will then use processing options from the configuration file. Note that the self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration file name instead of using the default name 'BNC.ini'. +Command line options are available to run BNC in 'no window' mode or let it read data offline from one file or several files for debugging or Post Processing purposes. BNC will then use processing options from the configuration file. Note that the self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration file name instead of using the default name 'BNC.ini'.

    @@ -2441,5 +2441,5 @@ Jun 2010  Version 2.1   -[Bug] SSR GLONASS message generation
    [Add] PPP in post-processing mode
    [Mod] Update of SSR messages following draft dated 2010-04-12
    [Mod] Generating error message when observation epoch is wrong +[Bug] SSR GLONASS message generation
    [Add] PPP in Post Processing mode
    [Mod] Update of SSR messages following draft dated 2010-04-12
    [Mod] Generating error message when observation epoch is wrong @@ -2680,9 +2680,9 @@
    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 differen Ntrip versions and generate 1sec/15min 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 differen Ntrip versions and generate 1sec/15min RINEX Version 3 observation files. See http://igs.bkg.bund.de/ntrip/observations for observation stream resources.

    2. File 'RinexEpn.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. +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. @@ -2692,5 +2692,5 @@
    3. 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 rate 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. +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 rate 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.

      4. @@ -2712,5 +2712,5 @@
    4. 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 otions are set in support of the QuickStart mode. The output is saved in a specific post processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm. +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 otions are set in support of the QuickStart mode. The output is saved in a specific Post Processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm.