Index: trunk/BNC/src/bnchelp.html =================================================================== --- trunk/BNC/src/bnchelp.html (revision 6832) +++ trunk/BNC/src/bnchelp.html (revision 6833) @@ -122,5 +122,5 @@

-BNC supports decoding the following GNSS stream formats and message types: +BNC supports the following GNSS stream formats and message types:

@@ -140,5 +140,5 @@

1.1 Supported Systems

-BNC is continuously completed in order to support all existing GNSS systems throughout all features of the program. The table below shows in detail which GNSS systems are so far supported by particular applications when using the latest BNC version. The applications named here are +BNC is continuously completed in order to support all existing GNSS systems throughout all features of the program. The table below shows in detail which GNSS systems are so far supported by particular applications when using the latest BNC version. Applications fields named here are:

-The table mentions if the Navigation, Observation, or SSR message implementation in BNC could so far only be based on a 'RTCM Proposal'. +
  • Combination/merging of SSR or ephemeris messages from various real-time sources
    • + +The table mentions if the message implementation in BNC could so far only be based on a 'RTCM Proposal'.

    Table: Status of RTCM Version 3 message implementation in BNC supporting various GNSS systems

    @@ -156,5 +156,5 @@ - + @@ -235,5 +235,8 @@

    -BNC can be used in different contexts with varying data flows. The first of the following figures shows a flow chart of BNC connected to a GNSS receiver providing observations via serial or TCP communication link for the purpose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX files. The third figure shows a flow chart of BNC feeding a real-time GNSS engine which estimates precise orbits and clocks. BNC is used in this scenario to encode correctors to RTCM Version 3 and upload them to an NTRIP Broadcaster. The fourth figure shows BNC combining several Broadcast Correction streams to disseminate the combination product while saving results in SP3 and Clock RINEX files. +BNC can be used in different contexts with varying data flows. Typical real-time communication follows the Ntrip protocol over TCP/IP (probably via SSL), RTSP/RTP or UDP, plain TCP/IP protocol, or serial communication links. Stream contents could be observations, ephemeris, satellite orbit/clock products or NMEA sentences. +

    +

    + The first of the following figures shows a flow chart of BNC connected to a GNSS receiver providing observations via serial or TCP communication link for the purpose of Precise Point Positioning. The second figure shows the conversion of RTCM streams to RINEX files. The third figure shows a flow chart of BNC feeding a real-time GNSS engine which estimates precise orbits and clocks. BNC is used in this scenario to encode correctors to RTCM Version 3 and upload them to an NTRIP Broadcaster. The fourth figure shows BNC combining several Broadcast Correction streams to disseminate the combination product while saving results in SP3 and Clock RINEX files.

    Message
    Type    		 Description System RTCM
    Proposal     		 Decoding   RINEX/ 
     SP3    		 Encoding  Upload   PPP      Combin. 
    Message
    Type #    		 Description System RTCM
    Proposal     		 Decoding   RINEX/ 
     SP3    		 Encoding  Upload   PPP      Combin. 

    General