Index: trunk/BNC/src/bnchelp.html =================================================================== --- trunk/BNC/src/bnchelp.html (revision 7683) +++ trunk/BNC/src/bnchelp.html (revision 7685) @@ -1,17 +1,13 @@ -

BKG Ntrip Client (BNC) User Manual
+

BKG Ntrip Client (BNC)
Version 2.12.0

-Software by
-Leos Mervart(1), Andrea Stürze(2), Georg Weber(2), Axel Rülke(2), Dirk Stöcker(3) -

-(1) Czech Technical University (CTU), Department of Geomatics, Prague, Czech Republic
-(2) Federal Agency for Cartography and Geodesy (BKG), Frankfurt, Germany
+Georg Weber(1), Leos Mervart(2), Andrea Stürze(1), Axel Rülke(1), Dirk Stöcker(3) +

+(1) Federal Agency for Cartography and Geodesy (BKG), Frankfurt, Germany
+(2) Czech Technical University (CTU), Department of Geomatics, Prague, Czech Republic
(3) Alberding GmbH, Wildau, Germany -

-Documentation by
-Georg Weber(2)

Copyright
@@ -21,5 +17,5 @@ To help justify funding the development of BNC, we kindly ask users to include a citation when applying the software results in a publication. We suggest:

-Mervart, Leos, Andrea Stürze, Georg Weber, Axel Rülke and Dirk Stöcker:
+Weber, G., L. Mervart, A. Stürze, A. Rülke and D. Stöcker:
            BKG Ntrip Client, Version 2.12. Mitteilungen des Bundesamtes
            für Kartographie und Geodäsie, Vol. 49, Frankfurt am Main, 2016. @@ -234,6 +230,6 @@ 7BNC's 'Network' panel configured to ignore eventually occurring SSL error messages2.2.2 8BNC translating incoming streams to 15 min RINEX Version 3 files2.4 -9Converting Broadcast Ephemeris stream to RINEX Version 3 Navigation file2.5.5 -10Example for 'RINEX Editing Options' window2.6.7 +9BNC converting Broadcast Ephemeris stream to RINEX Version 3 Navigation files2.5.5 +10Example for BNC's 'RINEX Editing Options' window2.6.7 11Example for RINEX file concatenation with BNC2.6.7 12Example for creating RINEX quality check analysis graphics output with BNC2.6.7 @@ -241,30 +237,30 @@ 14Sky plot examples for multipath, part of RINEX quality check analysis with BNC2.6.7 15Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC2.6.7 -16BNC configuration example for comparing two SP3 files with satellite orbit and clock data2.7.3 -17BNC configuration example for pulling, saving and output of Broadcast Corrections2.8.3 +16Example for comparing two SP3 files with satellite orbit and clock data using BNC2.7.3 +17Example for pulling, saving and output of Broadcast Corrections using BNC2.8.3 18Synchronized BNC output via IP port to feed a GNSS real-time engine2.9 19Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams2.10 20BNC pulling a VRS stream to feed a serial connected RTK rover2.10 -21RTCM message numbers, latencies and observation types2.12 +21RTCM message numbers, latencies and observation types logged by BNC2.12 22Real-time Precise Point Positioning with BNC, PPP Panel 12.13.1 23Precise Point Positioning with BNC, PPP Panel 2, using RTKPLOT for visualization2.13.2 24Precise Point Positioning with BNC, PPP Panel 32.13.3 -25BNC in 'Quick-Start' mode (PPP, Panel 2)2.13.3.8 -26Track of positions from BNC with Google Maps in the background2.13.4.3 -27Example for a background map from Google Maps and OpenStreetMap (OSM) resources2.13.4.3.1 +25Precise Point Positioning with BNC in 'Quick-Start' mode, PPP Panel 42.13.3.8 +26Track of positions from BNC with Google Maps in background2.13.4.3 +27Example for background map from Google Maps and OpenStreetMap (OSM) resources2.13.4.3.1 28BNC combining Broadcast Correction streams2.14.1.1 29BNC uploading the combined Broadcast Correction stream2.14.1.1 30'INTERNAL' PPP with BNC using combined Broadcast Correction stream2.14.1.1 -31Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94'2.15.3 -32Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster2.15.9 -33Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an Ntrip Broadcaster2.16.3 -34Bandwidth consumption of incoming streams2.18.2 -35Latency of incoming streams2.18.3 -36Time series plot of PPP session showing displacements2.18.4 -37Steam input communication links2.19 -38Casters table2.19.1.1.2 -39Broadcaster source-table2.19.1.1.4 -40Stream distribution map derived from Ntrip Broadcaster source-table2.19.1.1.6 -41BNC setup for pulling a stream via serial port2.19.1.4 +31Setting BNC's Custom Transformation Parameters window, example for 'ITRF2008->GDA94'2.15.3 +32BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster2.15.9 +33BNC producing Broadcast Ephemeris stream from globally distributed RTCM streams; upload in RTCM format to an Ntrip Broadcaster2.16.3 +34Bandwidth consumption of RTCM streams received by BNC2.18.2 +35Latency of RTCM streams received by BNC2.18.3 +36Example for time series plot of displacements produced by BNC2.18.4 +37Steam input communication links accepted by BNC2.19 +38BNC's 'Select Broadcaster' table2.19.1.1.2 +39Broadcaster source-table shown by BNC2.19.1.1.4 +40Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table2.19.1.1.6 +41BNC configuration for pulling a stream via serial port2.19.1.4

@@ -544,20 +540,20 @@

-

Figure 1: Flowchart, BNC connected to a GNSS rover for Precise Point Positioning.

+

Figure 1: Flowchart, BNC connected to a GNSS rover for Precise Point Positioning

-

Figure 2: Flowchart, BNC converting RTCM streams to RINEX batches.

+

Figure 2: Flowchart, BNC converting RTCM streams to RINEX batches

-

Figure 3: Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections.

+

Figure 3: Flowchart, BNC feeding a real-time GNSS engine and uploading encoded Broadcast Corrections

-

Figure 4: Flowchart, BNC combining Broadcast Correction streams.

+

Figure 4: Flowchart, BNC combining Broadcast Correction streams

1.4 Handling

@@ -584,5 +580,5 @@

-

Figure 5: Sections on BNC's main window.

+

Figure 5: Sections on BNC's main window

@@ -627,7 +623,7 @@

Figure 6: Management of configuration options in BNC:
- - - + + +
                Left:BNC in graphics mode; active configuration options are introduced through GUI input fields and finally saved on disk.
                Middle:BNC in 'no window' mode; active configuration options are read from disk.
                Right:BNC in 'no window' mode without configuration file; default configuration options can be replaced via command line options.
                Left:BNC in graphics mode; active configuration options are introduced through GUI input fields and finally saved on disk
                Middle:BNC in 'no window' mode; active configuration options are read from disk
                Right:BNC in 'no window' mode without configuration file; default configuration options can be replaced via command line options
@@ -716,5 +712,5 @@

  • File 'RinexEph.bnc'
    Purpose: Convert a RTCM stream -carrying navigation messages to RINEX Navigation files. The configuration +with navigation messages to RINEX Navigation files. The configuration pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the real-time EUREF and IGS networks and saves hourly RINEX Version 3 Navigation @@ -725,15 +721,15 @@
  • File 'BrdcCorr.bnc'
    Purpose: 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. +SSR messages in hourly plain ASCII files. See +http://igs.bkg.bund.de/ntrip/orbits for various real-time IGS or EUREF +orbit/clock correction products.

  • File 'RinexConcat.bnc'
    Purpose: Concatenate several RINEX Version 3 files to -produce one concatenated file and edit the marker name in the file header. The +produce one compiled 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. +mode for RINEX file editing, concatenation and quality check.

    • @@ -743,12 +739,12 @@ 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. +file editing, concatenation and quality check.
  • File 'RTK.bnc'
    Purpose: Feed a serial connected receiver with -observations from a reference station for conventional RTK. The stream is +observations from a nearby 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. +observations are reported in BNC's logfile.

    • @@ -756,7 +752,7 @@ Purpose: Feed a real-time GNSS engine with observations from remote reference stations. The configuration pulls a single -stream from an Ntrip Broadcaster. It would of course be possible to pull +stream from an Ntrip Broadcaster. You could also pull several streams from different casters. Incoming observations are decoded, -synchronized and output through a local IP port and saved into a file. Failure +synchronized, output through a local IP port and also saved into a file. Failure and recovery thresholds are specified to inform about outages.
    @@ -771,5 +767,5 @@
  • File 'PPPNet.bnc'
    Purpose: Precise -Point Positioning for several rovers or receivers from a network of +Point Positioning for several rovers or receivers from an entire network of reference stations in one BNC job. The possible maximum number of PPP solutions per job depends on the processing power of the hosting computer. This example @@ -785,5 +781,5 @@ Broadcast Ephemeris stream. Positions are saved in NMEA format on disc. They are also output through IP port for real-time visualization with tools -like RTKPLOT. Positions are also saved in the logfile. +like RTKPLOT. Positions are saved in the logfile.

    • @@ -799,5 +795,5 @@
  • File 'PPPGoogleMaps.bnc'
    Purpose: Track BNC's point positioning -solution using Google Maps or OpenStreetMap as background. BNC reads a +solutions using Google Maps or OpenStreetMap as background. BNC reads a RINEX Observation file and a RINEX Navigation file to carry out a 'Standard Point Positioning' solution in post processing mode. Although @@ -810,5 +806,5 @@
  • File 'SPPQuickStartGal.bnc'
    Purpose: Single Point Positioning in Quick-Start mode from observations of a static -receiver with precisely known position. +receiver with quite precisely known position. The configuration uses GPS, GLONASS and Galileo observations and a Broadcast Ephemeris stream. @@ -827,5 +823,5 @@ Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The Broadcast Correction stream is formally introduced in BNC's 'Combine -Corrections' table. The configuration leads to a SP3 file containing orbits referred also +Corrections' table. The configuration leads to a SP3 file containing orbits also referred to ETRF2000. Pulling in addition observations from a reference station at precisely known ETRF2000 position allows comparing an 'INTERNAL' PPP solution @@ -838,18 +834,18 @@ 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 upload them to +Corrections and encodes them to RTCM Version 3 SSR messages to finally upload them to an Ntrip Broadcaster. The Broadcast Correction stream is referred to satellite Antenna Phase Center (APC) and reference system IGS08. Orbits are saved on disk -in SP3 format and clocks in Clock RINEX format. +in SP3 format and clocks are saved in Clock RINEX format.

  • File 'Combi.bnc'
    Purpose: Pull several streams carrying Broadcast -Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to +Corrections and a Broadcast Ephemeris from an Ntrip Broadcaster to produce a combined Broadcast Correction stream. BNC encodes the combination product in RTCM Version 3 SSR messages and uploads that to an Ntrip -Broadcaster. The Broadcast Correction stream is not referred to satellite +Broadcaster. The Broadcast Correction stream is referred to satellite Antenna Phase Center (APC) and not to satellite Center of Mass (CoM). Its reference system is IGS08. Orbits are saved in SP3 -format and clocks in Clock RINEX format. +format (referred to CoM) and clocks in Clock RINEX format.

    • @@ -864,12 +860,12 @@
  • File 'UploadEph.bnc'
    Purpose: 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 with the sole purpose of providing -Broadcast Ephemeris with an update rate of 5 seconds. +stations to get hold of contained Broadcast Ephemeris messages. They are +encoded to RTCM Version 3 format and uploaded for the purpose of providing +a Broadcast Ephemeris stream with an update rate of 5 seconds.

  • File 'CompareSp3.bnc'
    Purpose: Compare two SP3 files to calculate -RMS values from orbit and clock differences. GPS satellite G05 and GLONASS +RMS values for orbit and clock differences. GPS satellite G05 and GLONASS satellite R18 are excluded from this comparison. Comparison results are saved in a logfile. @@ -1009,5 +1005,5 @@

    -

    Figure 7: BNC's 'Network' panel configured to ignore eventually occurring SSL error messages.

    +

    Figure 7: BNC's 'Network' panel configured to ignore eventually occurring SSL error messages

    2.3 General

    @@ -1117,5 +1113,5 @@

    -

    Figure 8: BNC translating incoming observation streams to 15 min RINEX Version 3 Observation files.

    +

    Figure 8: BNC translating incoming observation streams to 15 min RINEX Version 3 Observation files

    2.4.1 RINEX Filenames

    @@ -1395,5 +1391,5 @@

    -

    Figure 9: Converting Broadcast Ephemeris stream to RINEX Version 3 Navigation file.

    +

    Figure 9: BNC converting Broadcast Ephemeris stream to RINEX Version 3 Navigation files

    2.6 RINEX Editing & QC

    @@ -1718,20 +1714,20 @@

    -

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

    +

    Figure 10: Example for BNC's 'RINEX Editing Options' window

    -

    Figure 11: Example for RINEX file concatenation with BNC.

    +

    Figure 11: Example for RINEX file concatenation with BNC

    -

    Figure 12: Example for creating RINEX quality check analysis graphics output with BNC.

    +

    Figure 12: Example for creating RINEX quality check analysis graphics output with BNC

    -

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

    +

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

    -

    Figure 14: Sky plot examples for multipath, part of RINEX quality check analysis with BNC.

    +

    Figure 14: Sky plot examples for multipath, part of RINEX quality check analysis with BNC

    -

    Figure 15: Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC.

    +

    Figure 15: Sky plot examples for signal-to-noise ratio, part of RINEX quality check analysis with BNC

    2.6.8 Command Line, No Window - optional

    @@ -1929,5 +1925,5 @@

    -

    Figure 16: BNC configuration example for comparing two SP3 files with satellite orbit and clock data.

    +

    Figure 16: Example for comparing two SP3 files with satellite orbit and clock data using BNC

    2.8 Broadcast Corrections

    @@ -2285,5 +2281,5 @@

    -

    Figure 17: BNC configuration example for pulling, saving and output of Broadcast Corrections.

    +

    Figure 17: Example for pulling, saving and output of Broadcast Corrections using BNC

    2.9 Feed Engine

    @@ -2366,5 +2362,5 @@

    -

    Figure 18: Synchronized BNC output via IP port to feed a GNSS real-time engine.

    +

    Figure 18: Synchronized BNC output via IP port to feed a GNSS real-time engine

    2.9.1 Port - optional

    @@ -2408,5 +2404,5 @@

    -

    Figure 19: Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams.

    +

    Figure 19: Flowcharts, BNC forwarding a stream to a serial connected receiver; sending NMEA sentences is mandatory for VRS streams

    @@ -2415,5 +2411,5 @@

    -

    Figure 20: BNC pulling a VRS stream to feed a serial connected RTK rover.

    +

    Figure 20: BNC pulling a VRS stream to feed a serial connected RTK rover

    2.10.1 Mountpoint - optional

    @@ -2574,5 +2570,5 @@

    -

    Figure 21: RTCM message numbers, latencies and observation types.

    +

    Figure 21: RTCM message numbers, latencies and observation types logged by BNC

    @@ -2700,5 +2696,5 @@

    -

    Figure 22: Real-time Precise Point Positioning with BNC, PPP Panel 1.

    +

    Figure 22: Real-time Precise Point Positioning with BNC, PPP Panel 1

    2.13.1.1 Data Source - optional

    @@ -3172,5 +3168,5 @@

    -

    Figure 23: Precise Point Positioning with BNC, PPP Panel 2, using RTKPLOT for visualization.

    +

    Figure 23: Precise Point Positioning with BNC, PPP Panel 2, using RTKPLOT for visualization

    2.13.2.1 Station - mandatory

    @@ -3217,5 +3213,5 @@

    -

    Figure 24: Precise Point Positioning with BNC, PPP Panel 3.

    +

    Figure 24: Precise Point Positioning with BNC, PPP Panel 3

    2.13.3.1 Linear Combinations - mandatory

    @@ -3323,5 +3319,5 @@

    -

    Figure 25: BNC in 'Quick-Start' mode, PPP Panel 4.

    +

    Figure 25: Precise Point Positioning with BNC in 'Quick-Start' mode, PPP Panel 4

    2.13.4 PPP (4): Plots

    @@ -3358,5 +3354,5 @@

    -

    Figure 26: Track of positions from BNC with Google Maps in the background.

    +

    Figure 26: Track of positions from BNC with Google Maps in background

    2.13.4.3.1 Google/OSM - mandatory before pushing 'Open Map'

    @@ -3366,5 +3362,5 @@

    -

    Figure 27: Example for a background map from Google Maps and OpenStreetMap (OSM).

    +

    Figure 27: Example for background map from Google Maps and OpenStreetMap (OSM)

    2.13.4.4 Dot-properties - mandatory before pushing 'Open Map'

    @@ -3472,11 +3468,11 @@

    -

    Figure 28: BNC combining Broadcast Correction streams.

    +

    Figure 28: BNC combining Broadcast Correction streams

    -

    Figure 29: BNC uploading the combined Broadcast Correction stream.

    +

    Figure 29: BNC uploading the combined Broadcast Correction stream

    -

    Figure 30: 'INTERNAL' PPP with BNC using combined Broadcast Correction stream.

    +

    Figure 30: 'INTERNAL' PPP with BNC using combined Broadcast Correction stream

    2.14.1.2 Method - mandatory if 'Combine Corrections' table is populated

    @@ -3800,5 +3796,5 @@

    -

    Figure 31: Setting Custom Transformation Parameters window, example for 'ITRF2008->GDA94'.

    +

    Figure 31: Setting BNC's Custom Transformation Parameters window, example for 'ITRF2008->GDA94'

    2.15.4 Center of Mass - optional

    @@ -3899,5 +3895,5 @@

    -

    Figure 32: Producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster.

    +

    Figure 32: BNC producing Broadcast Corrections from incoming precise orbits and clocks and uploading them to an Ntrip Broadcaster

    2.15.10 ANTEX File - mandatory if 'SP3 File' is specified

    @@ -3946,5 +3942,5 @@

    -

    Figure 33: Producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an Ntrip Broadcaster.

    +

    Figure 33: BNC producing a Broadcast Ephemeris stream from navigation messages of globally distributed RTCM streams and uploading them in RTCM Version 3 format to an Ntrip Broadcaster

    2.17 Streams Canvas

    @@ -4013,5 +4009,5 @@

    -

    Figure 34: Bandwidth consumption of incoming streams.

    +

    Figure 34: Bandwidth consumption of RTCM streams received by BNC

    2.18.3 Latency

    @@ -4021,5 +4017,5 @@

    -

    Figure 35: Latency of incoming streams.

    +

    Figure 35: Latency of RTCM streams received by BNC

    2.18.4 PPP Plot

    @@ -4029,5 +4025,5 @@

    -

    Figure 36: Time series plot of PPP session showing displacements.

    +

    Figure 36: Example for time series plot of displacements produced by BNC

    2.19 Bottom Menu Bar

    @@ -4037,5 +4033,5 @@

    -

    Figure 37: Steam input communication links.

    +

    Figure 37: Steam input communication links accepted by BNC

    2.19.1 Add Stream

    @@ -4062,5 +4058,5 @@

    -

    Figure 38: Casters table.

    +

    Figure 38: BNC's 'Select Broadcaster' table

    2.19.1.1.3 User and Password - mandatory for protected streams

    @@ -4080,5 +4076,5 @@

    -

    Figure 39: Broadcaster source-table.

    +

    Figure 39: Broadcaster source-table shown by BNC

    2.19.1.1.5 Ntrip Version - mandatory

    @@ -4117,5 +4113,5 @@

    -

    Figure 40: Stream distribution map derived from Ntrip Broadcaster source-table.

    +

    Figure 40: Stream distribution map shown by BNC as derived from Ntrip Broadcaster source-table

    2.19.1.2 Add Stream - Coming from TCP/IP Port

    @@ -4191,5 +4187,5 @@

    -

    Figure 41: BNC setup for pulling a stream via serial port.

    +

    Figure 41: BNC configuration for pulling a stream via serial port

    2.19.2 Delete Stream

    @@ -4522,4 +4518,5 @@ [Add] Full integration of 'rtcm3torinex'
    [Add] Extended command line help
    +[Add] Version 2.12.0 published