Changeset 8086 in ntrip


Ignore:
Timestamp:
Mar 23, 2017, 1:14:12 PM (9 months ago)
Author:
stuerze
Message:

minor changes: IGS08 => IGS14

Location:
trunk/BNC/Example_Configs
Files:
4 edited

Legend:

Unmodified
Added
Removed
  • trunk/BNC/Example_Configs/00_Readme.txt

    r7802 r8086  
    11Configuration Examples
    22
    3 BNC comes with a number of configuration examples which can be used on all 
     3BNC comes with a number of configuration examples which can be used on all
    44operating systems. Copy the complete directory 'Example_Configs' which comes
    55with the software including sub-directories 'Input' and 'Output' to your disc.
    6 There are several ways to start BNC using one of the example configurations: 
    7 
    8 * On graphical systems (except for Mac systems) you may use the computer mouse 
     6There are several ways to start BNC using one of the example configurations:
     7
     8* On graphical systems (except for Mac systems) you may use the computer mouse
    99  to 'drag' a configuration file icon and 'drop' it on top of BNC's program icon.
    1010
    11 * You could also start BNC using a command line for naming a specific 
     11* You could also start BNC using a command line for naming a specific
    1212  configuration file (suggested e.g. for Mac systems):
    1313  bnc --conf <configFileName>
    1414
    1515* On non-graphical systems or when running BNC in batch mode in the background
    16   you may start the program using a command line with a configuration file 
     16  you may start the program using a command line with a configuration file
    1717  option in 'no window' mode (example for Windows systems):
    1818  bnc.exe --conf <configFileName> --nw
    1919
    2020Although it's not a must, we suggest that you always create BNC configuration
    21 files with the filename extension '.bnc'. 
     21files with the filename extension '.bnc'.
    2222
    2323We furthermore suggest for convenience reasons that you configure your system
    24 to automatically start BNC when you double-click a file with the filename 
    25 extension '.bnc'. The following describes what to do on Windows systems to 
    26 associate the BNC program to such configuration files: 
    27 
    28 
    29 1. Right-click a file that has the extension '.bnc' and then click 'Open'. If 
     24to automatically start BNC when you double-click a file with the filename
     25extension '.bnc'. The following describes what to do on Windows systems to
     26associate the BNC program to such configuration files:
     27
     28
     291. Right-click a file that has the extension '.bnc' and then click 'Open'. If
    3030   the 'Open' command is not available, click 'Open With' or double-click the
    3131   file.
    3232
    33 2. Windows displays a dialog box that says that the system cannot open this 
     332. Windows displays a dialog box that says that the system cannot open this
    3434   file. The dialog box offers several options for selecting a program.
    3535
     
    4646Some of the presented example configuration files contain a user ID 'Example'
    4747with a password 'Configs' for accessing a few GNSS streams from public Ntrip
    48 Broadcasters. This generic account is arranged for convenience reasons only. 
    49 Please be so kind as to replace the generic account details as well as the 
    50 place holders 'User' and 'Pass' by the personal user ID and password you 
     48Broadcasters. This generic account is arranged for convenience reasons only.
     49Please be so kind as to replace the generic account details as well as the
     50place holders 'User' and 'Pass' by the personal user ID and password you
    5151receive following an online registration through
    52 http://register.rtcm-ntrip.org. 
    53 
    54 Note that the account for an Ntrip Broadcaster is usually limited to 
     52http://register.rtcm-ntrip.org.
     53
     54Note that the account for an Ntrip Broadcaster is usually limited to
    5555pulling a specified maximum number of streams at the same time. As running
    56 some of the example configurations requires pulling several streams, it 
     56some of the example configurations requires pulling several streams, it
    5757is suggested to make sure that you don't exceed your account's limits.
    5858
    59 Make also sure that sub-directories 'Input' and 'Output' which are part of 
    60 the example configurations exist on your system or adjust the affected 
     59Make also sure that sub-directories 'Input' and 'Output' which are part of
     60the example configurations exist on your system or adjust the affected
    6161example configuration options according to your needs.
    6262
    63 Some BNC options require antenna phase center variations as made available 
    64 from IGS through so-called ANTEX files at ftp://igs.org/pub/station/general. 
     63Some BNC options require antenna phase center variations as made available
     64from IGS through so-called ANTEX files at ftp://igs.org/pub/station/general.
    6565An example ANTEX file 'igs08.atx' is part of the BNC package for convenience.
    6666
    67 The example configurations assume that no proxy protects your BNC host. 
    68 Should a proxy be operated in front of BNC then you need to introduce its 
     67The example configurations assume that no proxy protects your BNC host.
     68Should a proxy be operated in front of BNC then you need to introduce its
    6969name or IP and port number in the 'Network' panel.
    7070
    7171(A) Working with Configuration Files
    7272
    73 You should be able to run all configuration file examples without changing 
    74 contained options. However, configurations 'Upload.bnc' and 'UploadPPP.bnc' are 
    75 exceptions because they require an input stream from a connected network engine. 
     73You should be able to run all configuration file examples without changing
     74contained options. However, configurations 'Upload.bnc' and 'UploadPPP.bnc' are
     75exceptions because they require an input stream from a connected network engine.
    7676
    77771. Configuration File 'RinexObs.bnc'
    78 Purpose: Convert RTCM streams to RINEX Observation files. The configuration 
    79 pulls streams from Ntrip Broadcasters using Ntrip Version 1 to generate 15min 
    80 1Hz RINEX Version 3 Observation files. See 
     78Purpose: Convert RTCM streams to RINEX Observation files. The configuration
     79pulls streams from Ntrip Broadcasters using Ntrip Version 1 to generate 15min
     801Hz RINEX Version 3 Observation files. See
    8181http://igs.bkg.bund.de/ntrip/observations for observation stream resources.
    8282
    83832. Configuration File 'RinexEph.bnc'
    84 Purpose: Convert a RTCM stream with navigation messages to RINEX Navigation 
    85 files. The configuration pulls a RTCM Version 3 stream with Broadcast Ephemeris 
    86 coming from the real-time EUREF and IGS networks and saves hourly RINEX Version 
    87 3 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further 
     84Purpose: Convert a RTCM stream with navigation messages to RINEX Navigation
     85files. The configuration pulls a RTCM Version 3 stream with Broadcast Ephemeris
     86coming from the real-time EUREF and IGS networks and saves hourly RINEX Version
     873 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further
    8888real-time Broadcast Ephemeris resources.
    8989
    90903. Configuration File 'BrdcCorr.bnc'
    91 Purpose: Save Broadcast Corrections from RTCM SSR messages in hourly plain 
    92 ASCII files. See http://igs.bkg.bund.de/ntrip/orbits for various real-time IGS 
     91Purpose: Save Broadcast Corrections from RTCM SSR messages in hourly plain
     92ASCII files. See http://igs.bkg.bund.de/ntrip/orbits for various real-time IGS
    9393or EUREF orbit/clock correction products.
    9494
    95954. Configuration File 'RinexConcat.bnc'
    96 Purpose: Concatenate several RINEX Version 3 files to produce one compiled file 
    97 and edit the marker name in the file header. The sampling interval is set to 30 
    98 seconds. See section 'RINEX Editing & QC' in the documentation for examples on 
    99 how to call BNC from command line in 'no window' mode for RINEX file editing, 
     96Purpose: Concatenate several RINEX Version 3 files to produce one compiled file
     97and edit the marker name in the file header. The sampling interval is set to 30
     98seconds. See section 'RINEX Editing & QC' in the documentation for examples on
     99how to call BNC from command line in 'no window' mode for RINEX file editing,
    100100concatenation and quality check.
    101101
    1021025. Configuration File 'RinexQC.bnc'
    103 Purpose: Check the quality of a RINEX Version 3 file by means of a multipath 
    104 analysis. Results are saved on disk in terms of a plot in PNG format. See 
    105 section 'RINEX Editing & QC' in the documentation for examples on how to call 
    106 BNC from command line in 'no window' mode for RINEX file editing, concatenation 
     103Purpose: Check the quality of a RINEX Version 3 file by means of a multipath
     104analysis. Results are saved on disk in terms of a plot in PNG format. See
     105section 'RINEX Editing & QC' in the documentation for examples on how to call
     106BNC from command line in 'no window' mode for RINEX file editing, concatenation
    107107and quality check.
    108108
    1091096. Configuration File 'RTK.bnc'
    110 Purpose: Feed a serial connected receiver with observations from a nearby 
    111 reference station for conventional RTK. The stream is scanned for RTCM 
    112 messages. Message type numbers and latencies of incoming observations are 
     110Purpose: Feed a serial connected receiver with observations from a nearby
     111reference station for conventional RTK. The stream is scanned for RTCM
     112messages. Message type numbers and latencies of incoming observations are
    113113reported in BNC's logfile.
    114114
    1151157. Configuration File 'FeedEngine.bnc'
    116 Purpose: Feed a real-time GNSS engine with observations from remote reference 
    117 stations. The configuration pulls a single stream from an Ntrip Broadcaster. 
    118 You could also pull several streams from different casters. Incoming 
    119 observations are decoded, synchronized, output through a local IP port and also 
    120 saved into a file. Failure and recovery thresholds are specified to inform 
     116Purpose: Feed a real-time GNSS engine with observations from remote reference
     117stations. The configuration pulls a single stream from an Ntrip Broadcaster.
     118You could also pull several streams from different casters. Incoming
     119observations are decoded, synchronized, output through a local IP port and also
     120saved into a file. Failure and recovery thresholds are specified to inform
    121121about outages.
    122122
    1231238. Configuration File 'PPP.bnc'
    124 Purpose: Precise Point Positioning from observations of a rover receiver. The 
    125 configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream 
     124Purpose: Precise Point Positioning from observations of a rover receiver. The
     125configuration reads RTCM Version 3 observations, a Broadcast Ephemeris stream
    126126and a stream with Broadcast Corrections. Positions are saved in the logfile.
    127127
    1281289. Configuration File 'PPPNet.bnc'
    129 Purpose: Precise Point Positioning for several rovers or receivers from an 
    130 entire network of reference stations in one BNC job. The possible maximum 
    131 number of PPP solutions per job depends on the processing power of the hosting 
    132 computer. This example configuration reads two RTCM Version 3 observation 
    133 streams, a Broadcast Ephemeris stream and a stream with Broadcast Corrections. 
     129Purpose: Precise Point Positioning for several rovers or receivers from an
     130entire network of reference stations in one BNC job. The possible maximum
     131number of PPP solutions per job depends on the processing power of the hosting
     132computer. This example configuration reads two RTCM Version 3 observation
     133streams, a Broadcast Ephemeris stream and a stream with Broadcast Corrections.
    134134PPP Results for the two stations are saved in PPP logfiles.
    135135
    13613610. Configuration File 'PPPQuickStart.bnc'
    137 Purpose: Precise Point Positioning in Quick-Start mode from observations of a 
    138 static receiver with precisely known position. The configuration reads RTCM 
    139 Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream. 
    140 Positions are saved in NMEA format on disc. They are also output through IP 
    141 port for real-time visualization with tools like RTKPLOT. Positions are saved 
     137Purpose: Precise Point Positioning in Quick-Start mode from observations of a
     138static receiver with precisely known position. The configuration reads RTCM
     139Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream.
     140Positions are saved in NMEA format on disc. They are also output through IP
     141port for real-time visualization with tools like RTKPLOT. Positions are saved
    142142in the logfile.
    143143
    14414411. Configuration File 'PPPPostProc.bnc'
    145 Purpose: Precise Point Positioning in post processing mode. BNC reads RINEX 
    146 Version 3 Observation and 3 Navigation files and a Broadcast Correction file. 
    147 PPP processing options are set to support the Quick-Start mode. The output is 
    148 saved in a specific post processing logfile and contains coordinates derived 
     145Purpose: Precise Point Positioning in post processing mode. BNC reads RINEX
     146Version 3 Observation and 3 Navigation files and a Broadcast Correction file.
     147PPP processing options are set to support the Quick-Start mode. The output is
     148saved in a specific post processing logfile and contains coordinates derived
    149149over time following the implemented PPP filter algorithm.
    150150
    15115112. Configuration File 'PPPGoogleMaps.bnc'
    152 Purpose: Track BNC's point positioning solutions using Google Maps or 
    153 OpenStreetMap as background. BNC reads a RINEX Observation file and a RINEX 
    154 Navigation file to carry out a 'Standard Point Positioning' solution in post 
    155 processing mode. Although this is not a real-time application it requires the 
    156 BNC host to be connected to the Internet. Specify a computation speed, then hit 
    157 button 'Open Map' to open the track map, then hit 'Start' to visualize receiver 
     152Purpose: Track BNC's point positioning solutions using Google Maps or
     153OpenStreetMap as background. BNC reads a RINEX Observation file and a RINEX
     154Navigation file to carry out a 'Standard Point Positioning' solution in post
     155processing mode. Although this is not a real-time application it requires the
     156BNC host to be connected to the Internet. Specify a computation speed, then hit
     157button 'Open Map' to open the track map, then hit 'Start' to visualize receiver
    158158positions on top of GM/OSM maps.
    159159
    16016013. Configuration File 'SPPQuickStartGal.bnc'
    161 Purpose: Single Point Positioning in Quick-Start mode from observations of a 
    162 static receiver with quite precisely known position. The configuration uses 
     161Purpose: Single Point Positioning in Quick-Start mode from observations of a
     162static receiver with quite precisely known position. The configuration uses
    163163GPS, GLONASS and Galileo observations and a Broadcast Ephemeris stream.
    164164
    16516514. Configuration File 'SaveSp3.bnc'
    166 Purpose: Produces SP3 files from a Broadcast Ephemeris stream and a Broadcast 
    167 Correction stream. The Broadcast Correction stream is formally introduced in 
    168 BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX 
     166Purpose: Produces SP3 files from a Broadcast Ephemeris stream and a Broadcast
     167Correction stream. The Broadcast Correction stream is formally introduced in
     168BNC's 'Combine Corrections' table. Note that producing SP3 requires an ANTEX
    169169file because SP3 file content should be referred to CoM.
    170170
    17117115. Configuration File 'Sp3ETRF2000PPP.bnc'
    172 Purpose: Produce SP3 files from a Broadcast Ephemeris stream and a stream 
    173 carrying ETRF2000 Broadcast Corrections. The Broadcast Correction stream is 
    174 formally introduced in BNC's 'Combine Corrections' table. The configuration 
    175 leads to a SP3 file containing orbits also referred to ETRF2000. Pulling in 
    176 addition observations from a reference station at precisely known ETRF2000 
    177 position allows comparing an 'INTERNAL' PPP solution with a known ETRF2000 
     172Purpose: Produce SP3 files from a Broadcast Ephemeris stream and a stream
     173carrying ETRF2000 Broadcast Corrections. The Broadcast Correction stream is
     174formally introduced in BNC's 'Combine Corrections' table. The configuration
     175leads to a SP3 file containing orbits also referred to ETRF2000. Pulling in
     176addition observations from a reference station at precisely known ETRF2000
     177position allows comparing an 'INTERNAL' PPP solution with a known ETRF2000
    178178reference coordinate.
    179179
    18018016. Configuration File 'Upload.bnc'
    181 Purpose: Upload orbits and clocks from a real-time GNSS engine to an Ntrip 
    182 Broadcaster. For that the configuration reads precise orbits and clocks in 
    183 RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts 
    184 the orbits and clocks into Broadcast Corrections and encodes them to RTCM 
    185 Version 3 SSR messages to finally upload them to an Ntrip Broadcaster. The 
    186 Broadcast Correction stream is referred to satellite Antenna Phase Center (APC) 
    187 and reference system IGS08. Orbits are saved on disk in SP3 format and clocks
     181Purpose: Upload orbits and clocks from a real-time GNSS engine to an Ntrip
     182Broadcaster. For that the configuration reads precise orbits and clocks in
     183RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts
     184the orbits and clocks into Broadcast Corrections and encodes them to RTCM
     185Version 3 SSR messages to finally upload them to an Ntrip Broadcaster. The
     186Broadcast Correction stream is referred to satellite Antenna Phase Center (APC)
     187and reference system IGS14. Orbits are saved on disk in SP3 format and clocks
    188188are saved in Clock RINEX format.
    189189
    19019017. Configuration File 'Combi.bnc'
    191 Purpose: Pull several streams carrying Broadcast Corrections and a Broadcast 
    192 Ephemeris from an Ntrip Broadcaster to produce a combined Broadcast Correction 
    193 stream. BNC encodes the combination product in RTCM Version 3 SSR messages and 
    194 uploads that to an Ntrip Broadcaster. The Broadcast Correction stream is 
    195 referred to satellite Antenna Phase Center (APC) and not to satellite Center of 
    196 Mass (CoM). Its reference system is IGS08. Orbits are saved in SP3 format
     191Purpose: Pull several streams carrying Broadcast Corrections and a Broadcast
     192Ephemeris from an Ntrip Broadcaster to produce a combined Broadcast Correction
     193stream. BNC encodes the combination product in RTCM Version 3 SSR messages and
     194uploads that to an Ntrip Broadcaster. The Broadcast Correction stream is
     195referred to satellite Antenna Phase Center (APC) and not to satellite Center of
     196Mass (CoM). Its reference system is IGS14. Orbits are saved in SP3 format
    197197(referred to CoM) and clocks in Clock RINEX format.
    198198
    19919918. Configuration File 'CombiPPP.bnc'
    200 Purpose: This configuration equals the 'Combi.bnc' configuration. However, the 
    201 combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP 
    202 solutions based on observations from a static reference station with known 
    203 precise coordinates. This allows a continuous quality check of the combination 
     200Purpose: This configuration equals the 'Combi.bnc' configuration. However, the
     201combined Broadcast Corrections are in addition used for an 'INTERNAL' PPP
     202solutions based on observations from a static reference station with known
     203precise coordinates. This allows a continuous quality check of the combination
    204204product through observing coordinate displacements.
    205205
    20620619. Configuration File 'UploadEph.bnc'
    207 Purpose: Pull a number of streams from reference stations to get hold of 
    208 contained Broadcast Ephemeris messages. They are encoded to RTCM Version 3 
    209 format and uploaded for the purpose of providing a Broadcast Ephemeris stream 
     207Purpose: Pull a number of streams from reference stations to get hold of
     208contained Broadcast Ephemeris messages. They are encoded to RTCM Version 3
     209format and uploaded for the purpose of providing a Broadcast Ephemeris stream
    210210with an update rate of 5 seconds.
    211211
    21221220. Configuration File 'CompareSp3.bnc'
    213 Purpose: Compare two SP3 files to calculate RMS values for orbit and clock 
    214 differences. GPS satellite G05 and GLONASS satellite R18 are excluded from this 
     213Purpose: Compare two SP3 files to calculate RMS values for orbit and clock
     214differences. GPS satellite G05 and GLONASS satellite R18 are excluded from this
    215215comparison. Comparison results are saved in a logfile.
    216216
    21721721. Configuration File 'Empty.bnc'
    218 Purpose: Provide an empty example configuration file for BNC which only 
     218Purpose: Provide an empty example configuration file for BNC which only
    219219contains the default settings.
    220220
    221221(B) Working with Command Line configuration options
    222222
    223 The following configuration examples make use of BNC's 'Command Line Interface' 
    224 (CLI). Configuration options are exclusively specified via command line. No 
     223The following configuration examples make use of BNC's 'Command Line Interface'
     224(CLI). Configuration options are exclusively specified via command line. No
    225225configuration file is used. Examples are provided as shell scripts for a Linux
    226 system. They call BNC in 'no window' batch mode (command line option -nw). 
     226system. They call BNC in 'no window' batch mode (command line option -nw).
    227227The scripts expect 'Example_Configs' to be the current working directory.
    228228
    22922922. Shell Script 'RinexQC.sh'
    230230Purpose: Equals configuration file example 'RinexQC.bnc', checks the quality of
    231 a RINEX Version 3 file by means of a multipath analysis. Virtual X-Server 
    232 'Xvfb' is operated while producing plot files in PNG format. BNC is offline. 
    233 All results are saved on disk. 
     231a RINEX Version 3 file by means of a multipath analysis. Virtual X-Server
     232'Xvfb' is operated while producing plot files in PNG format. BNC is offline.
     233All results are saved on disk.
    234234
    23523523. Shell Script 'RinexConcat.sh'
     
    239239offline.
    240240
    241 24. Shell Script 'RinexEph.sh' 
    242 Purpose: Equals configuration file example 'RinexEph.bnc', converts a RTCM 
    243 stream with navigation messages to RINEX Navigation files. The configuration 
    244 pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the 
     24124. Shell Script 'RinexEph.sh'
     242Purpose: Equals configuration file example 'RinexEph.bnc', converts a RTCM
     243stream with navigation messages to RINEX Navigation files. The configuration
     244pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the
    245245real-time EUREF and IGS networks and saves hourly RINEX Version 3 Navigation
    246 files. BNC runs online until it's terminated after 10 seconds.  See 
    247 http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast 
    248 Ephemeris resources. 
     246files. BNC runs online until it's terminated after 10 seconds.  See
     247http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast
     248Ephemeris resources.
    249249
    25025025. Shell Script 'ScanLate.sh'
    251251Purpose: Scan an observation stream for contained RTCM message types, print
    252 observation latencies. The output is saved in a logfile. Latencies are 
     252observation latencies. The output is saved in a logfile. Latencies are
    253253reported every 10 seconds. BNC runs online until it's terminated after 20
    254254seconds.
     
    258258streams to RINEX Observation files. The configuration pulls streams from two
    259259Ntrip Broadcasters using Ntrip Version 1 to generate 15min 1Hz RINEX Version 3
    260 Observation files. See http://igs.bkg.bund.de/ntrip/observations for 
     260Observation files. See http://igs.bkg.bund.de/ntrip/observations for
    261261observation stream resources. BNC runs online until it's terminated after 30
    262262seconds.
     
    264264(C) Command Line configuration options overwriting Configuration File options
    265265
    266 For specific applications you may like to use your own set of standard 
    267 configuration options from a configuration file and update some of its content 
     266For specific applications you may like to use your own set of standard
     267configuration options from a configuration file and update some of its content
    268268via command line. When using a configuration file and command line configuration
    269 options together in one BNC call, the command line configuration options will 
     269options together in one BNC call, the command line configuration options will
    270270always overrule options contained in the configuration file.
    271271
    27227227. Shell Script 'CompareSp3.sh'
    273 Purpose: Equals configuration file example 'CompareSp3.bnc', compares two SP3 
    274 files to calculate RMS values for orbit and clock differences. However, instead 
    275 of excluding GPS satellite G05 and GLONASS satellite R18 from the comparison as 
    276 specified in 'CompareSp3.bnc', GPS satellite G06 and all GLONASS satellites are 
     273Purpose: Equals configuration file example 'CompareSp3.bnc', compares two SP3
     274files to calculate RMS values for orbit and clock differences. However, instead
     275of excluding GPS satellite G05 and GLONASS satellite R18 from the comparison as
     276specified in 'CompareSp3.bnc', GPS satellite G06 and all GLONASS satellites are
    277277excluded via command line option. BNC runs offline. Comparison results are saved
    278278in a logfile.
  • trunk/BNC/Example_Configs/16_Upload.bnc

    r8062 r8086  
    116116uploadEphSample=5
    117117uploadIntr=1 day
    118 uploadMountpointsOut="products.igs-ip.net,2101,CLOCK,Pass,IGS08,0,Output/BNC${GPSWD}.sp3,Output/BNC${GPSWD}.clk,,,,0 byte(s),"
     118uploadMountpointsOut="products.igs-ip.net,2101,CLOCK,Pass,IGS14,0,Output/BNC${GPSWD}.sp3,Output/BNC${GPSWD}.clk,,,,0 byte(s),"
    119119uploadSamplClkRnx=0
    120120uploadSamplRtcmEphCorr=0
  • trunk/BNC/Example_Configs/17_Combi.bnc

    r8062 r8086  
    116116uploadEphSample=5
    117117uploadIntr=1 day
    118 uploadMountpointsOut="products.igs-ip.net,2101,CLOCK,Pass,IGS08,0,Output/BNC${GPSWD}.sp3,Output/BNC${GPSWD}.clk,,,,0 byte(s),"
     118uploadMountpointsOut="products.igs-ip.net,2101,CLOCK,Pass,IGS14,0,Output/BNC${GPSWD}.sp3,Output/BNC${GPSWD}.clk,,,,0 byte(s),"
    119119uploadSamplClkRnx=0
    120120uploadSamplRtcmEphCorr=0
  • trunk/BNC/Example_Configs/18_CombiPPP.bnc

    r8062 r8086  
    116116uploadEphSample=5
    117117uploadIntr=1 day
    118 uploadMountpointsOut="products.igs-ip.net,2101,CLOCK,Pass,IGS08,0,Output/BNC${GPSWD}.sp3,Output/BNC${GPSWD}.clk,,,,0 byte(s),"
     118uploadMountpointsOut="products.igs-ip.net,2101,CLOCK,Pass,IGS14,0,Output/BNC${GPSWD}.sp3,Output/BNC${GPSWD}.clk,,,,0 byte(s),"
    119119uploadSamplClkRnx=0
    120120uploadSamplRtcmEphCorr=0
Note: See TracChangeset for help on using the changeset viewer.