4.4.3 Reference System - mandatory
-BNS refers its final clock and orbit corrections to a specific reference system. Available options are -
-
-IGS05: -As the clocks and orbits coming from real-time GNSS engine are expected to be in the IGS05 system, no transformation is carried out if this option is selected. -
--ETRS89: -From the complete transformation chain 'IGS05->ITRF2005->ITRF2000->ETRS89' only the transformation 'ITRF2000->ETRS89' has been implemented. The formulas for that are taken from 'Boucher and Altamimi 2007: Specifications for reference frame fixing in the analysis of EUREF GPS campaign', see http://etrs89.ensg.ign.fr/memo2007.pdf. The following 6 Helmert transformation parameters were introduced: -
--
-Translation in X: 0.054 m -Translation in Y: 0.051 m -Translation in Z: -0.048 m -Rotation in X: 0.081 mas/y -Rotation in Y: 0.490 mas/y -Rotation in Z: -0.792 mas/y -- -
-Note that the neglect of transformations 'IGS05->ITRF2005->ITRF2000' in BNS may cause discrepancies up to a maximum of 2 centimenters. -
- -
--BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system and Broadcast Ephemeris in RINEX Navigation file format. -
- - --BNS reads GNSS Broadcast Ephemeris in RINEX Version 3 Navigation file format from an IP address and port. This information can be provided in real-time by the 'BKG Ntrip Client' (BNC) program. Note that whenever a new set of Broadcast Ephemeris becomes available, it has to be transmitted immediately. Enter the respective servers IP address and port number to establish a persistent socket connection, see section 'Flow Chart' under 'Help' for socket communication details. If BNS runs on the same host as BNC, 127.0.0.1 should be used as the server's IP address. Make sure that this server is up and running before you start BNS. -
- -The following is an example of Broadcast Ephemeris records in RINEX Version 3 Navigation file format for satellite GPS PRN32 and GLONASS PRN04: + ++BNS requires GNSS Broadcast Ephemeris in RINEX Version 3 Navigation file format from an IP address and port. This information can be provided in real-time by the 'BKG Ntrip Client' (BNC) program. Note that whenever a new set of Broadcast Ephemeris becomes available, BNS needs it immediately. +
+ + ++Enter the IP address and port number of a Broadcast Ephemeris server like BNC to establish a persistent socket connection, see section 'Flow Chart' under 'Help' for socket communication details. If BNS runs on the same host as BNC, 127.0.0.1 should be used as the server's IP address. Make sure that this server is up and running before you start BNS. +
+ + + +Specify the full path to a file where received Broadcast Ephemeris will logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled. + ++The following is an example log of Broadcast Ephemeris records in RINEX Version 3 Navigation file format for satellite GPS PRN32 and GLONASS PRN04:
@@ -239,10 +215,21 @@ -4.5.2 Clocks & Orbits - mandatory
-BNS is listening at an IP port for incoming GNSS clocks and orbits in a plain ASCII format. They can be provided by a real-time GNSS engine such as RTNet and are expected to refer to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. Enter the respective IP port number to setup a server socket for incoming data, see section 'Flow Chart' under 'Help' for socket communication details. Make sure that the software providing clocks and orbits is up and running before you start BNS. -
--Below you will find an example of precise clocks and orbits coming in plain ASCII format from a real-time GNSS engine. Each epoch starts with an asterisk character followed by GPS Week, Second in GPS Week and Number of satellites. Subsequent records provide the following set of parameters for each satellite: +
++BNS requires GNSS clocks and orbits in the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. They can be provided by a real-time GNSS engine such as RTNet and are expected to refer to the IGS Earth-Centered-Earth-Fixed (ECEF) reference system. +
+ +4.6.1 Listening Port - mandatory
+BNS is listening at an IP port for incoming GNSS clocks and orbits in a plain ASCII format. Enter the respective IP port number to setup a server socket for incoming data, see section 'Flow Chart' under 'Help' for socket communication details. Make sure that the software providing clocks and orbits is up and running before you start BNS. +
+ + ++Specify the full path to a file where received clocks and orbits from a real-time engine will logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled. +
+ ++Below you find an example of precise clocks and orbits coming in plain ASCII format from a real-time GNSS engine. Each epoch starts with an asterisk character followed by GPS Week, Second in GPS Week and Number of satellites. Subsequent records provide the following set of parameters for each satellite:
@@ -290,13 +277,10 @@ -4.5.3 Save Clocks & Orbits - optional
-Specify the full path to a file where received clocks and orbits from a real-time engine will logged. Beware that the size of this file can rapidly increase. Default is an empty option field meaning that logging is disabled.
- - --BNS can upload the resulting stream of cock and orbit corrections to Broadcast Ephemeris to an Ntrip Broadcaster. Both EUREF and IGS operate an NTRIP broadcaster at http://www.euref-ip.net/home and http://www.igs-ip.net/home which can be used for stream upload. The stream's format is RTCM Version 3.x. Note that it only carries the thentative message Types 4056 and 4057 for combined GPS and GLONASS clock and orbit corrections. - -
+ ++BNS can upload the resulting stream(s) of clock and orbit corrections to Broadcast Ephemeris to an Ntrip Broadcaster. Both EUREF and IGS operate an NTRIP broadcaster at http://www.euref-ip.net/home and http://www.igs-ip.net/home which can be used for stream upload. The stream's format is RTCM Version 3.x. Note that it only carries the thentative message Types 4056 and 4057 for combined GPS and GLONASS clock and orbit corrections. +
+ +4.7.1 Host & Port, Password - optional
Enter the NTRIP Caster's 'Host' IP name or number for stream upload. @@ -305,14 +289,47 @@ Enter the NTRIP Caster's IP 'Port' number for stream upload. Note that NTRIP Casters are often configured to provide access on more than one port, usually port 80 and 2101. If you experience communication problems on port 80, you should try to use the alternative port(s).
- -4.6.2 Mountpoint & Password - mandatory if 'Host' is set
4.7.2 Mountpoint - mandatory if 'Host' is set
Each stream on an NTRIP Caster is defined using a unique source ID called mountpoint. An NTRIP Server like BNS upload a stream to the Caster by referring to a dedicated mountpoint that has been set by the Caster operator. Specify here the mountpoint based on the detail you received from the operator for your stream. It is often a four character ID (capital letters) plus an integer number.
-
-In NTRIP Version 1.0 stream upload is only protected through a generic upload 'Password'. Enter the password you received from the Caster operator along with the mountpoint. - - - + +4.7.3 Reference System - mandatory if 'Host' is set
+BNS refers its final clock and orbit corrections to a specific reference system. Available options are +
+
+IGS05: +As the clocks and orbits coming from real-time GNSS engine are expected to be in the IGS05 system, no transformation is carried out if this option is selected. +
++ETRS89: +From the complete transformation chain 'IGS05->ITRF2005->ITRF2000->ETRS89' only the transformation 'ITRF2000->ETRS89' has been implemented. The formulas for that are taken from 'Boucher and Altamimi 2007: Specifications for reference frame fixing in the analysis of EUREF GPS campaign', see http://etrs89.ensg.ign.fr/memo2007.pdf. The following 6 Helmert transformation parameters were introduced: +
++
+Translation in X: 0.054 m +Translation in Y: 0.051 m +Translation in Z: -0.048 m +Rotation in X: 0.081 mas/y +Rotation in Y: 0.490 mas/y +Rotation in Z: -0.792 mas/y ++ +
+Note that the neglect of transformations 'IGS05->ITRF2005->ITRF2000' in BNS may cause discrepancies up to a maximum of 2 centimenters. +
+ + +
The clock and orbit corrections streamed by BNS to the NTRIP Caster can be logged locally. Specify a full 'Save stream' path here to save this information to a local file. Default value for 'Save stream' is an empty option field, meaning that logging is disabled. @@ -351,15 +368,15 @@
- +The clock corrections generated by BNS can be logged separately in Clock RINEX format. The file naming follows the RINEX convention.
- +Here you can specify the path to where the Clock RINEX files will be stored. If the specified directory does not exist, BNS will not create Clock RINEX files. Default value for 'Directory' is an empty option field, meaning that logging of Clock RINEX files is disabled.
-4.7.2 Interval & Sampling - mandatory if 'Directory' is set
4.8.2 Interval & Sampling - mandatory if 'Directory' is set
Select the length of the Clock RINEX file generated. The default value is 1 day. @@ -370,15 +387,15 @@
- +The orbit corrections generated by BNS can be logged separately in SP3 Orbit files. The file naming follows the IGS convention.
- +Here you can specify the path to where the SP3 Orbit files will be stored. If the specified directory does not exist, BNS will not create SP3 Orbit files. Default value for 'Directory' is an empty option field, meaning that logging of SP3 Orbit files is disabled.
-4.8.2 Interval & Sampling - mandatory if 'Directory' is set
4.9.2 Interval & Sampling - mandatory if 'Directory' is set
Select the length of the SP3 Orbit file generated. The default value is 1 day. @@ -388,15 +405,15 @@
- +Hit 'Start' to start receiving IGS orbits and clocks and convert them into corrections to Broadcast Ephemeris. Note that when started BNS by default will begin with new files which might overwrite existing files when necessary unless the option 'Append files' is ticked.
- +Hit the 'Stop' button in order to stop BNS.
- +On all systems BNS can be started in batch mode with the command line option '-nw'. BNS will then run in 'no window' mode, using options from the configuration file ${HOME}/.config/BKG/BNC_NTRIP_Server.conf (Unix/Linux, see Config File example in the Annex) or from the register BKG_NTRIP_Server (Windows). @@ -507,35 +524,34 @@
-The following is an example of the contents of a Unix/Linux configuration file ${HOME}/.config/BKG/BKG_NTRIP_Server.conf. It enables the upload of stream CLCK1 to www.euref-ip.net. Clock RINEX files and SP3 Orbit files are uploaded to a directory /home/weber/rinex : +The following is an example of the contents of a Unix/Linux configuration file ${HOME}/.config/BKG/BKG_NTRIP_Server.conf. It enables the upload of streams CLCK1 and CLCK2 to www.igs-ip.net. Clock RINEX files and SP3 Orbit files are saved to a directory /home/weber/rinex :
[General] -clkFile=/home/weber/clocks.txt -clkHost=142.71.30.12 -clkPort=2067 -clkProxy=2 -ephHost=141.71.30.13 -ephPort=2066 -ephProxy=2 +clkPort=7000 +ephEcho=/home/weber/rinex/eph.rnx +ephHost=clock-ip.bkg.bund.de +ephPort=6000 fileAppend=0 -font="Andale Sans,9,-1,5,75,0,0,0,0,0" -logFile=/home/weber/rinex/log.txt -mountpoint=CLCK1 -outFile=/home/weber/rinex/CLCK1.txt +font="Helvetica [Adobe],8,-1,5,75,0,0,0,0,0" +inpEcho=/home/weber/rinex/ClocksOrbits.dat +logFile=/home/weber/rinex/bns.log +mountpoint_1=CLCK1 +mountpoint_2=CLCK2 +outFile_1=/home/weber/rinex/CLCK1 +outFile_2=/home/weber/rinex/CLCK2 outHost=www.igs-ip.net outPort=2101 -outProxy=2 -password=uploadPass -proxyHost=gate-f -proxyPort=8000 -refSys=IGS05 -rnxAppend=2 +password=serverPass +proxyHost= +proxyPort= +refSys_1=IGS05 +refSys_2=ETRS89 rnxIntr=1 day rnxPath=/home/weber/rinex rnxSampl=30 -sp3Intr=1 hour -sp3Path=/home/weber/sp3 -sp3Sampl=0 +sp3Intr=1 day +sp3Path=/home/weber/rinex +sp3Sampl=300