Index: trunk/BNC/bnchelp.html
===================================================================
--- trunk/BNC/bnchelp.html (revision 1371)
+++ trunk/BNC/bnchelp.html (revision 1409)
@@ -130,8 +130,9 @@
3.12.2. Caster Host and Port
3.12.3. Caster User and Password
- 3.12.4. Get Table
- 3.12.5. Delete Streams
- 3.12.6. Edit Streams
- 3.12.7. Reconfigure Streams On-the-fly
+ 3.12.4. NTRIP Version
+ 3.12.5. Get Table
+ 3.12.6. Delete Streams
+ 3.12.7. Edit Streams
+ 3.12.8. Reconfigure Streams On-the-fly
3.13. Start
3.14. Stop
@@ -736,9 +737,10 @@
+
Streams selected for retrieval are listed under the 'Streams' canvas section on BNC's main window. The list provides the following information extracted from source-table(s) produced by the NTRIP broadcasters:
+
-|
-| 'broadcaster:port' | NTRIP broadcaster URL and port. |
+| 'broadcaster:port' | NTRIP broadcaster URL and port. |
| 'mountpoint' | Mountpoint on NTRIP broadcaster. |
| 'decoder' | Type of decoder used to handle the incoming stream content according to its format; editable. |
@@ -746,4 +748,5 @@
| 'long' | Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'. |
| 'nmea' | Indicates whether or not streaming needs to be initiated by BNC through sending NMEA-GGA message carrying position coordinates in 'lat' and 'long'. |
+| 'ntrip' | Selected NTRIP transport protocol version. |
| 'bytes' | Number of bytes retrieved.
|
@@ -764,5 +767,21 @@
-3.12.4 Get Table
+3.12.4 NTRIP Version - mandatory
+
+Some limitations and deficiencies of the NTRIP version 1 stream transport protocol are solved in NTRIP version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Options implemented in BNC are:
+
+
+ 1: NTRIP version 1 in TCP/IP mode,
+ 2: NTRIP version 2 in TCP/IP mode.
+
+
+Try using option '2' if your streams are blocked by a proxy and protocol version 2 is supported by the broadcaster. Select option '1' if you not sure whether the broadcaster supports NTRIP version 2.
+
+
+
+
+
+
+3.12.5 Get Table
Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary.
@@ -775,9 +794,9 @@
-3.12.5 Delete Streams
+3.12.6 Delete Streams
To remove a stream from the 'Streams' canvas in the main window, highlight it by clicking on it and hit the 'Delete Streams' button. You can also remove multiple streams simultaneously by highlighting them using +Shift and +Ctrl.
-3.12.6 Edit Streams
+3.12.7 Edit Streams
-
@@ -789,10 +808,10 @@
-
BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA format to the NTRIP broadcaster. In return, a user-specific data stream is generated, typically by a Network-RTK software. VRS streams are indicated by a 'yes' in the source-table as well as in the 'nmea' column on the 'Streams' canvas in BNC's main window. They are customized exactly to the latitude and longitude transmitted to the NTRIP broadcaster via NMEA-GGA messages.
-
If NMEA-GGA messages are not coming from a serial connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'lon' columns on the 'Streams' canvas. However, in most cases you would probably want to change these defaults according to your requirement. Double-click on 'lat' and 'lon' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only streams with a 'yes' in their 'nmea' column can be edited. The position must preferably be a point within the VRS service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'lon' used.
+
If NMEA-GGA messages are not coming from a serial connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'long' columns on the 'Streams' canvas. However, in most cases you would probably want to change these defaults according to your requirement. Double-click on 'lat' and 'long' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only streams with a 'yes' in their 'nmea' column can be edited. The position must preferably be a point within the VRS service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'long' used.
Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner.
-3.12.7 Reconfigure Streams On-the-fly
+3.12.8 Reconfigure Streams On-the-fly
The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process.
@@ -916,7 +935,8 @@
8.1. History
8.2. RTCM
- 8.2.1 NTRIP
- 8.2.2 RTCM Version 2.x
- 8.2.3 RTCM Version 3.x
+ 8.2.1 NTRIP Version 1
+ 8.2.2 NTRIP Version 2
+ 8.2.3 RTCM Version 2.x
+ 8.2.4 RTCM Version 3.x
8.3. RTIGS
8.3.1 SOC
@@ -935,6 +955,5 @@
| Apr 2008 | Version 1.5 | [Add] Handle ephemeris from RTCM Version 3.x streams
[Add] Upgrade to Qt Version 4.3.2
[Add] Optional RINEX v3 output
[Add] SBAS support
[Bug] RINEX skeleton download following stream outage
[Add] Handle ephemeris from RTIGS streams
[Add] Monitor stream failure/recovery and latency
[Mod] Redesign of main window
[Bug] Freezing of About window on Mac systems
[Bug] Fixed problem with PRN 32 in RTCMv2 decoder
[Bug] Fix for Trimble 4000SSI receivers in RTCMv2 decoder
[Mod] Major revision of input buffer in RTCMv2 decoder |
| Dec 2008 | Version 1.6 | [Mod] Fill blanc columns in RINEXv3 with 0.000
[Add] RTCMv3 decoder for clock and orbit corrections
[Add] Check RTCMv3 streams for incoming message types
[Add] Decode RTCMv2 message types 3, 20, 21, and 22
[Add] Loss of lock and lock time indicator
[Bug] Rounding error in RTCMv3 decoder concerning GLONASS height
[Mod] Accept GLONASS in RTCMv3 when transmitted first
[Add] Leap second 1 January 2009
[Add] Offline mode, read data from file
[Add] Output antenna descriptor, coordinates and excentricities from RTCMv3
[Add] Reconfiguration on-the-fly
[Mod] Binary ouput of synchronized observations
[Add] Binary output of unsynchronized observations
[Bug] Fixed problem with joined RTCMv3 blocks |
-| Jan 2009 | Version 1.7 |
-[Add] Full proxy support
[Mod] Ntrip source-table request
[Bug] RINEX navigation file format
[Add] Support of NTRIP v2
[Add] Rover support via serial port |
+| Jan 2009 | Version 1.7 | [Mod] NTRIP v1 source-table request
[Bug] RINEX navigation file format
[Add] Support of NTRIP v2
[Add] Rover support via serial port |
@@ -948,5 +967,5 @@
-8.2.1 NTRIP
+8.2.1 NTRIP Version 1
@@ -987,6 +1006,23 @@
-
-8.2.2 RTCM Version 2.x
+8.2.1 NTRIP Version 2
+
+
+The major changes of NTRIP version 2.0 compared to Version 1.0 are:
+
+
+
+- cleared and fixed design problems and HTTP protocol violations;
+- replaced non standard directives;
+- chunked transfer encoding;
+- improvements in header records;
+- sourcetable filtering; and
+- RTSP communication.
+
+
+NTRIP version 2 allows to either communicate in TCP/IP mode or in RTSP/RTP mode. Note that RTSP/RTP support is not yet implemented in BNC.
+
+
+8.2.3 RTCM Version 2.x
Transmitting GNSS carrier phase data can be done through RTCM Version 2.x messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of some interest here are:
@@ -1026,5 +1062,5 @@
-
8.2.3 RTCM Version 3.x
+8.2.4 RTCM Version 3.x
RTCM Version 3.x has been developed as a more efficient alternative to RTCM Version 2.x. Service providers and vendors have asked for a standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the Version 2 parity scheme was wasteful of bandwidth. Another complaint was that the parity is not independent from word to word. Still another was that even with so many bits devoted to parity, the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. The Version 3.x standard is intended to correct these weaknesses.