Changeset 7485 in ntrip for trunk/BNC/src/bnchelp.html
- Timestamp:
- Oct 6, 2015, 12:53:08 PM (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/src/bnchelp.html
r7484 r7485 178 178 2.19.5 <a href=#stop>Stop</a><br> 179 179 2.20 <a href=#cmd>Command Line Options</a><br> 180 2.20.1 <a href=#nw>No Window Mode</a><br> 181 2.20.2 <a href=#post>File Mode</a><br> 182 2.20.3 <a href=#conffile>Configuration File</a><br> 183 2.20.4 <a href=#confopt>Configuration Options</a><br> 180 2.20.1 <a href=#cmdVersion>Version</a><br> 181 2.20.2 <a href=#cmdDisplay>Display</a><br> 182 2.20.3 <a href=#nw>No Window Mode</a><br> 183 2.20.4 <a href=#post>File Mode</a><br> 184 2.20.5 <a href=#conffile>Configuration File</a><br> 185 2.20.6 <a href=#confopt>Configuration Options</a><br> 184 186 3. <a href=#annex>Annex</a><br> 185 187 3.1. <a href=#history>Revision History</a><br> … … 270 272 <b><a name="authors">Authors</b><br><br> 271 273 The BKG Ntrip Client (BNC) and its Qt Graphical User Interface (GUI) has been developed for 272 </p> 273 <p> 274 Federal Agency for Cartography and Geodesy (BKG)<br> 275 c/o Dr. Axel Rülke<br> 276 Department of Geodesy, Section Navigation<br> 277 Frankfurt, Germany<br> 278 [axel.ruelke@bkg.bund.de] 279 </p> 280 281 <p> 274 <pre> 275 Federal Agency for Cartography and Geodesy (BKG) 276 c/o Dr. Axel Rülke 277 Department of Geodesy, Section Navigation 278 Frankfurt, Germany 279 [axel.ruelke@bkg.bund.de] 280 </pre> 281 282 282 The software has been written by 283 </p> 284 285 <p> 286 Prof. Dr. Leos Mervart<br> 287 Czech Technical University (CTU)<br> 288 Department of Geodesy<br> 289 Prague, Czech Republic 283 284 <pre> 285 Prof. Dr. Leos Mervart 286 Czech Technical University (CTU) 287 Department of Geodesy 288 Prague, Czech Republic 289 </pre> 290 290 </p> 291 291 … … 592 592 <li>Specifying the 'Reread configuration' option lets BNC reread its configuration from disk at pre-defined intervals.</li> 593 593 </ul> 594 <li>A certain BNC configuration can be started in 'no window' mode from scratch without anyconfiguration file if options for the active configuration level (2) are provided via command line.</li>594 <li>A specific BNC configuration can be started in 'no window' mode from scratch without a configuration file if options for the active configuration level (2) are provided via command line.</li> 595 595 </ul> 596 596 </p> … … 928 928 <p>SSL communication may involve queries coming from the Ntrip Broadcaster or from a HTTPS website hosting RINEX skeletons. Such a query could show up under BNC's 'Log' tab as follows: 929 929 <pre> 930 SSL Error931 Server Certificate Issued by:932 GNSS Data Center933 BKG (Bundesamt fuer Geodaesie und Kartographie)934 Cannot be verified935 936 The issuer certificate of a locally looked up certificate could not be found937 The root CA certificate is not trusted for this purpose938 No certificates could be verified930 SSL Error 931 Server Certificate Issued by: 932 GNSS Data Center 933 BKG (Bundesamt fuer Geodaesie und Kartographie) 934 Cannot be verified 935 936 The issuer certificate of a locally looked up certificate could not be found 937 The root CA certificate is not trusted for this purpose 938 No certificates could be verified 939 939 </pre> 940 940 Tick 'Ignore SSL authorization errors' if you generally trust the server and don't want to be bothered with this. Note that SSL communication is usually done over port 443. … … 1006 1006 </p> 1007 1007 <p> 1008 See BNC's command line option -nwfor an auto-start of BNC in 'no window' mode.1008 See BNC's command line option '-nw' for an auto-start of BNC in 'no window' mode. 1009 1009 </p> 1010 1010 … … 1016 1016 Data will be saved in blocks in the received format separated by ASCII time stamps like (example): 1017 1017 <pre> 1018 2010-08-03T18:05:28 RTCM3EPH RTCM_3 671018 2010-08-03T18:05:28 RTCM3EPH RTCM_3 67 1019 1019 </pre> 1020 1020 </p> … … 1057 1057 1058 1058 <pre> 1059 FRAN{ddd}{h}.{yy}O1060 WETT{ddd}{h}.{yy}O1059 FRAN{ddd}{h}.{yy}O 1060 WETT{ddd}{h}.{yy}O 1061 1061 </pre> 1062 1062 <p> … … 1066 1066 If there is more than one stream with identical 4Char Station ID (same first 4 characters for their mountpoints), the mountpoint strings are split into two sub-strings and both become part of the RINEX filename. For example, when simultaneously retrieving data from mountpoints FRANKFURT and FRANCE, their hourly RINEX Version 2 Observation files are named as</p> 1067 1067 <pre> 1068 FRAN{ddd}{h}_KFURT.{yy}O1069 FRAN{ddd}{h}_CE.{yy}O1068 FRAN{ddd}{h}_KFURT.{yy}O 1069 FRAN{ddd}{h}_CE.{yy}O 1070 1070 </pre> 1071 1071 <p> 1072 1072 If several streams show exactly the same mountpoint name (example: BRUS0 from <u>www.euref-ip.net</u> and BRUS0 from <u>www.igs-ip.net</u>), BNC adds an integer number to the filename leading i.e. to hourly RINEX Version 2 Observation files like</p> 1073 1073 <pre> 1074 BRUS{ddd}{h}_0.{yy}O1075 BRUS{ddd}{h}_1.{yy}O1074 BRUS{ddd}{h}_0.{yy}O 1075 BRUS{ddd}{h}_1.{yy}O 1076 1076 </pre> 1077 1077 <p> 1078 1078 Note that RINEX Version 2 filenames for all intervals less than 1 hour follow the filename convention for 15 minutes RINEX Version 2 Observation files i.e.</p> 1079 1079 <pre> 1080 FRAN{ddd}{h}{mm}.{yy}O1080 FRAN{ddd}{h}{mm}.{yy}O 1081 1081 </pre> 1082 1082 <p> … … 1103 1103 Example for Mixed RINEX Version 3 GNSS observation filename, file containing 1 hour of data, one observation every second, 'MO' standing for 'Mixed Observations': 1104 1104 <pre> 1105 ALGO00CAN_R_20121601000_01H_01S_MO.rnx1105 ALGO00CAN_R_20121601000_01H_01S_MO.rnx 1106 1106 </pre> 1107 1107 </p> … … 1136 1136 </p> 1137 1137 <pre> 1138 BRUS.skl1139 FRAN.skl1140 WETT.skl1138 BRUS.skl 1139 FRAN.skl 1140 WETT.skl 1141 1141 </pre> 1142 1142 <p> … … 1281 1281 The following is an example for a RINEX Version 3 Navigation filename. The file contains one days data. 'MN' stands for 'Multi Constellation Navigation' data. 1282 1282 <pre> 1283 BRDC00DEU_S_20121600000_01D_MN.rnx1283 BRDC00DEU_S_20121600000_01D_MN.rnx 1284 1284 </pre> 1285 1285 </p> … … 1514 1514 > 2015 06 15 00 00 30.0000000 39 0.6 1515 1515 ... 1516 1517 1516 </pre> 1518 1517 </p> … … 1601 1600 BNC applies options from the configuration file but allows updating every one of them on the command line while the contents of the configuration file remains unchanged, see section on 'Command Line Options'. The syntax for that looks as follows 1602 1601 </p> 1603 <p >1604 --key <keyName> <keyValue>1605 </p >1602 <pre> 1603 --key <keyName> <keyValue> 1604 </pre> 1606 1605 <p> 1607 1606 where <keyName> stands for the name of an option contained in the configuration file and <keyValue> stands for the value you want to assign to it. This functionality may be helpful in the 'RINEX Editing & QC' context when running BNC on a routine basis for maintaining a RINEX file archive. … … 1609 1608 The following example for a Linux platform calls BNC in 'no window' mode with a local configuration file 'rnx.conf' for concatenating four 15min RINEX files from station TLSE residing in the local directory to produce an hourly RINEX Version 3 file with 30 seconds sampling interval: 1610 1609 </p> 1611 <p >1612 ./bnc --nw --conf rnx.conf --key reqcAction Edit/Concatenate --key reqcObsFile "tlse119b00.12o,tlse119b15.12o,tlse119b30.12o,tlse119b45.12o" --key reqcOutObsFile tlse119b.12o --key reqcRnxVersion 3 --key reqcSampling 301613 </p >1610 <pre> 1611 ./bnc --nw --conf rnx.conf --key reqcAction Edit/Concatenate --key reqcObsFile "tlse119b00.12o,tlse119b15.12o,tlse119b30.12o,tlse119b45.12o" --key reqcOutObsFile tlse119b.12o --key reqcRnxVersion 3 --key reqcSampling 30 1612 </pre> 1614 1613 <p> 1615 1614 You may use asterisk '*' and/or question mark '?' wildcard characters as shown with the following globbing command line option to specify a selection of files in a local directory: 1616 < /p>1617 <p> 1618 --key reqcObsFile "tlse*"<br> 1619 or:<br> 1620 --key reqcObsFile tlse\* 1615 <pre> 1616 --key reqcObsFile "tlse*" 1617 or: 1618 --key reqcObsFile tlse\* 1619 </pre> 1621 1620 </p> 1622 1621 1623 1622 <p>The following Linux command line produces RINEX QC plots (see Estey and Meertens 1999) offline in 'no window' mode and saves them in directory '/home/user'. Introducing a dummy configuration file /dev/null makes sure that no configuration options previously saved on disc are used:</p> 1624 <p> 1625 /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key reqcPlotDir /home/user --nw 1626 </p> 1627 <p></p> 1628 <p>The following Linux command line produces the same RINEX QC plots in interactive autoStart mode:</p> 1629 <p> 1630 /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key --key startTab 4 --key autoStart 2 1623 <pre> 1624 /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key reqcPlotDir /home/user --nw 1625 </pre> 1626 </p> 1627 <p>The following Linux command line produces the same RINEX QC plots in interactive autoStart mode: 1628 </p> 1629 <pre> 1630 /home/user/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile CUT02070.12O --key reqcNavFile BRDC2070.12P --key reqcOutLogFile CUT0.txt --key --key startTab 4 --key autoStart 2 1631 </pre> 1631 1632 </p> 1632 1633 … … 2284 2285 </p> 2285 2286 <pre> 2286 Windows: COM1, COM22287 Linux: /dev/ttyS0, /dev/ttyS12288 FreeBSD: /dev/ttyd0, /dev/ttyd12289 Digital Unix: /dev/tty01, /dev/tty022290 HP-UX: /dev/tty1p0, /dev/tty2p02291 SGI/IRIX: /dev/ttyf1, /dev/ttyf22292 SunOS/Solaris: /dev/ttya, /dev/ttyb2287 Windows: COM1, COM2 2288 Linux: /dev/ttyS0, /dev/ttyS1 2289 FreeBSD: /dev/ttyd0, /dev/ttyd1 2290 Digital Unix: /dev/tty01, /dev/tty02 2291 HP-UX: /dev/tty1p0, /dev/tty2p0 2292 SGI/IRIX: /dev/ttyf1, /dev/ttyf2 2293 SunOS/Solaris: /dev/ttya, /dev/ttyb 2293 2294 </pre> 2294 2295 <p> … … 2396 2397 Examples for command line parameter strings passed on to the advisory 'Script' are: 2397 2398 <pre> 2398 FFMJ0 Begin_Outage 08-02-21 09:25:592399 FFMJ0 End_Outage 08-02-21 11:36:02 Begin was 08-02-21 09:25:592399 FFMJ0 Begin_Outage 08-02-21 09:25:59 2400 FFMJ0 End_Outage 08-02-21 11:36:02 Begin was 08-02-21 09:25:59 2400 2401 </pre> 2401 2402 </p> … … 2404 2405 </p> 2405 2406 <pre> 2406 #!/bin/bash2407 sleep $((60*RANDOM/32767))2408 cat > mail.txt <<EOF2409 Advisory Note to BNC User,2410 Please note the following advisory received from BNC.2411 Stream: $*2412 Regards, BNC2413 EOF2414 mail -s "NABU: $1" email@address < mail.txt2407 #!/bin/bash 2408 sleep $((60*RANDOM/32767)) 2409 cat > mail.txt <<EOF 2410 Advisory Note to BNC User, 2411 Please note the following advisory received from BNC. 2412 Stream: $* 2413 Regards, BNC 2414 EOF 2415 mail -s "NABU: $1" email@address < mail.txt 2415 2416 </pre> 2416 2417 </p> … … 2577 2578 <p> 2578 2579 <u>Debugging</u><br> 2579 Note that for debugging purposes BNC's real-time PPP functionality can also be used offline. Apply the 'File Mode' 'Command Line' option for that to read a file containing synchronized observations, orbit and clock correctors, and Broadcast Ephemeris. Example:<br><br> 2580 bnc.exe --conf c:\temp\PPP.bnc --file c:\temp\RAW<br><br> 2580 Note that for debugging purposes BNC's real-time PPP functionality can also be used offline. Apply the 'File Mode' 'Command Line' option for that to read a file containing synchronized observations, orbit and clock correctors, and Broadcast Ephemeris. Example: 2581 <pre> 2582 bnc.exe --conf c:\temp\PPP.bnc --file c:\temp\RAW 2583 </pre> 2581 2584 Such a file (here: 'RAW') must be saved beforehand using BNC's 'Raw output file' option. 2582 2585 </li> … … 2728 2731 2729 2732 <pre> 2730 /Users/pppDir/PPP_${STATION}_${DATE}.log2733 /Users/pppDir/PPP_${STATION}_${DATE}.log 2731 2734 </pre> 2732 2735 … … 2807 2810 2808 2811 <pre> 2809 /Users/pppDir/PPP_${STATION}_${DATE}.nmea2812 /Users/pppDir/PPP_${STATION}_${DATE}.nmea 2810 2813 </pre> 2811 2814 <p> … … 2852 2855 BNC estimates the tropospheric delay according to equation 2853 2856 <pre> 2854 T(z) = T_apr(z) + dT / cos(z)2857 T(z) = T_apr(z) + dT / cos(z) 2855 2858 </pre> 2856 2859 where T_apr is the a priori tropospheric delay derived from Saastamoinen model. … … 2860 2863 You can specify the full path to daily SINEX Troposphere files to save troposphere parameters on disk, see <u>https://igscb.jpl.nasa.gov/igscb/data/format/sinex_tropo.txt</u> for a documentation of the file format. Example: 2861 2864 <pre> 2862 /Users/pppDir/PPP_${STATION}${DOY}_${YY}.zpd2865 /Users/pppDir/PPP_${STATION}${DOY}_${YY}.zpd 2863 2866 </pre> 2864 2867 In this '${STATION}' stands for the observation's mountpoint or RINEX file, '${DOY}' for the Day Of Year, and '${YY}' for the year. For a RINEX observations file 'CUT0' it would lead to a troposphere file named 'PPP_CUT01810.15.zpd' with the following contents (example): … … 3102 3105 <p><u>Figure 25:</u> BNC in 'Quick-Start' mode (PPP, Panel 2)</p> 3103 3106 3104 <p><a name="pppaverage"><h4>2.13.3.NN Averaging - optional if XYZ is set</h4></p>3105 <p><a name="pppgap"><h4>2.13.3.NN Maximal Solution Gap - optional if Quick-Start is set</h4></p>3106 3107 3107 <p><a name="pppPlots"><h4>2.13.4 PPP (4): Plots</h4></p> 3108 3108 <p> … … 3425 3425 </p> 3426 3426 <pre> 3427 dC = (s - 1) / s * ρ / c3427 dC = (s - 1) / s * ρ / c 3428 3428 </pre> 3429 3429 <p> … … 3612 3612 </p> 3613 3613 <p> 3614 Specify a path for saving the generated clock corrections as Clock RINEX files. If the specified directory does not exist, BNC will not create Clock RINEX files. The following is a path example for a Linux system:<br>/home/user/BNC${GPSWD}.clk<br>Note that '${GPSWD}' produces the GPS Week and Day number in the filename. 3614 Specify a path for saving the generated clock corrections as Clock RINEX files. If the specified directory does not exist, BNC will not create Clock RINEX files. The following is a path example for a Linux system: 3615 <pre> 3616 /home/user/BNC${GPSWD}.clk 3617 </pre> 3618 Note that '${GPSWD}' produces the GPS Week and Day number in the filename. 3615 3619 </p> 3616 3620 <p> … … 3986 3990 <p><a name="cmd"><h4>2.20. Command Line Options</h4></p> 3987 3991 <p> 3988 Command line options are available to run BNC in 'no window' mode or let it read previously recorded input offline from one or several files for debugging purposes. The self-explaining contents of the configuration file can easily be edited. It is possible to introduce a specific configuration filename instead of using the default name 'BNC.bnc'.3989 </p> 3990 <p> 3991 In addition to reading processing options from the involved configuration file, BNC can optionally read a ll configuration optionsfrom command line. Running BNC with command line option 'help'3992 Command line options are available to run BNC in 'no window' mode or let it read previously recorded input offline from one or several files for debugging purposes. It is also possible to introduce a specific configuration filename instead of using the default filename 'BNC.bnc'. The self-explaining contents of the configuration file can easily be edited. 3993 </p> 3994 <p> 3995 In addition to reading processing options from the involved configuration file, BNC can optionally read any configuration option from command line. Running BNC with command line option 'help' 3992 3996 </p> 3993 3997 <p> 3994 3998 Example:<br><br> 3995 bnc.exe --help3999 bnc.exe --help 3996 4000 </p> 3997 4001 <p> … … 3999 4003 </p> 4000 4004 4001 <p><a name="nw"><h4>2.20.1 No Window Mode - optional</h4></p> 4005 <p><a name="cmdVersion"><h4>2.20.1 Version - optional</h4></p> 4006 <p> 4007 Command line option '--version' lets BNC print its version number. 4008 </p> 4009 <p> 4010 Example:<br><br> 4011 bnc.exe --version 4012 </p> 4013 4014 <p><a name="cmdDisplay"><h4>2.20.2 Display - optional</h4></p> 4015 <p> 4016 On systems which support graphics command line option '--display' forces BNC to present the BNC window on the specified display. 4017 </p> 4018 <p> 4019 Example:<br><br> 4020 bnc.exe --display localhost:10.0 4021 </p> 4022 4023 <p><a name="nw"><h4>2.20.3 No Window Mode - optional</h4></p> 4002 4024 <p> 4003 4025 Apart from its regular windows mode, BNC can be started on all systems as a batch job with command line option '-nw'. BNC will then run in 'no window' mode, using processing options from its configuration file on disk. Terminate BNC using Windows Task Manager when running it in 'no window' mode on Windows systems. … … 4005 4027 <p> 4006 4028 Example:<br><br> 4007 bnc.exe --nw4029 bnc.exe --nw 4008 4030 </p> 4009 4031 <p> … … 4017 4039 </p> 4018 4040 <pre> 4019 #!/bin/bash4020 4021 # Save string localhost4022 echo "localhost" > /home/user/hosts4023 4024 # Start virtual X-Server, save process ID4025 /usr/bin/Xvfb :29 -auth /home/user/hosts -screen 0 1280x1024x8 &4026 psID=`echo $!`4027 4028 # Run BNC application with defined display variable4029 /home/user/BNC/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile ons12090.12o --key reqcNavFile brdc2090.12p --key reqcOutLogFile multi.txt --key reqcPlotDir /home/user --display localhost:29 --nw4030 4031 # BNC done, kill X-server process4032 kill $psID4033 </pre> 4034 4035 <p><a name="post"><h4>2.20. 2File Mode - optional</h4></p>4041 #!/bin/bash 4042 4043 # Save string localhost 4044 echo "localhost" > /home/user/hosts 4045 4046 # Start virtual X-Server, save process ID 4047 /usr/bin/Xvfb :29 -auth /home/user/hosts -screen 0 1280x1024x8 & 4048 psID=`echo $!` 4049 4050 # Run BNC application with defined display variable 4051 /home/user/BNC/bnc --conf /dev/null --key reqcAction Analyze --key reqcObsFile ons12090.12o --key reqcNavFile brdc2090.12p --key reqcOutLogFile multi.txt --key reqcPlotDir /home/user --display localhost:29 --nw 4052 4053 # BNC done, kill X-server process 4054 kill $psID 4055 </pre> 4056 4057 <p><a name="post"><h4>2.20.4 File Mode - optional</h4></p> 4036 4058 <p> 4037 4059 Although BNC is primarily a real-time online tool, for debugging purposes it can be run offline to read data from a file previously saved through option 'Raw output file'. Enter the following command line option for that 4038 4060 </p> 4039 4061 <p> 4040 --file <<u>inputFileName</u>>4062 --file <<u>inputFileName</u>> 4041 4063 </p> 4042 4064 4043 4065 and specify the full path to an input file containing previously saved data. Example:<br><br> 4044 ./bnc --file /home/user/raw.output_1103014066 ./bnc --file /home/user/raw.output_110301 4045 4067 </p> 4046 4068 <p> … … 4050 4072 </p> 4051 4073 4052 <p><a name="conffile"><h4>2.20. 3Configuration File - optional</h4></p>4074 <p><a name="conffile"><h4>2.20.5 Configuration File - optional</h4></p> 4053 4075 The default configuration filename is 'BNC.bnc'. You may change this name at startup time using the command line option '--conf <<u>confFileName</u>>'. This allows running several BNC jobs in parallel on the same host using different sets of configuration options. <u>confFileName</u> stands either for the full path to a configuration file or just for a filename. If you introduce only a filename, the corresponding file will be saved in the current working directory from where BNC is started. 4054 4076 </p> 4055 4077 <p> 4056 4078 Example:<br><br> 4057 ./bnc --conf MyConfig.bnc4079 ./bnc --conf MyConfig.bnc 4058 4080 </p> 4059 4081 <p> … … 4061 4083 </p> 4062 4084 4063 <p><a name="confopt"><h4>2.20. 4Configuration Options - optional</h4></p>4085 <p><a name="confopt"><h4>2.20.6 Configuration Options - optional</h4></p> 4064 4086 <p> 4065 4087 BNC applies options from the configuration file but allows updating every one of them on the command line while the contents of the configuration file remains unchanged. The command line syntax for that looks as follows 4066 4088 </p> 4067 4089 <p> 4068 --key <keyName> <keyValue>4090 --key <keyName> <keyValue> 4069 4091 </p> 4070 4092 <p> … … 4072 4094 </p> 4073 4095 <p> 4074 bnc --nw --conf <confFileName> --key <keyName1> <keyValue1> --key <keyName2> <keyValue2> ... 4075 </p> 4076 <p> 4077 Example: 4078 </p> 4079 <p> 4080 ./bnc --conf CONFIG.bnc --key proxyPort 8001 --key rnxIntr "1 day" 4096 bnc --nw --conf <confFileName> --key <keyName1> <keyValue1> --key <keyName2> <keyValue2> ... 4097 </p> 4098 <p> 4099 Configuration options which are part of the configuration files PPP section must be prefixed by 'PPP/'. As an example, option 'minObs' from the PPP section of the BNC configuration file would be specified as 'PPP/minObs' on a command line. 4100 </p> 4101 <p> 4102 Values for configuration options can be introduced via command line exactly as they show up in the configuration file. However, any value containing one or more blank characters must be enclosed by quotation marks when specified on the command line. 4103 </p> 4104 <p> 4105 Example command lines: 4106 </p> 4107 <p> 4108 (1) /Applications/bnc.app/Contents/MacOS/bnc -- version<br> 4109 (2) ./bnc --conf CONFIG.bnc --key proxyPort 8001 --key rnxIntr "1 day"<br> 4110 (3) D:\BKG\bnc.exe --conf C:\Users\weber\Desktop\BNC.bnc --file C:\Users\weber\Desktop\rawfile<br> 4111 (4) /home/weber/bin/bnc --conf /home/weber/MyConfigFile.bnc<br> 4112 (5) bnc --conf /Users/weber/.config/BKG/BNC.bnc -nw<br> 4113 (6) bnc --conf /dev/null --key startTab 4 --key reqcAction Edit/Concatenate --key reqcObsFile AGAR.15O --key reqcOutObsFile AGAR_X.15O --key reqcRnxVersion 2 --key reqcSampling 30 --key reqcV2Priority CWPX_?<br> 4114 (7) bnc --key mountPoints "//user:pass@mgex.igs-ip.net:2101/CUT07 RTCM_3.0 ETH 9.03 38.74 no 2;//user:pass@www.igs-ip.net:2101/FFMJ1 RTCM_3.1 DEU 50.09 8.66 no 2"<br> 4115 (8) bnc --key cmbStreams "CLK11 BKG 1.0;CLK93 CNES 1.0"<br> 4116 (9) bnc --key PPP/staTable "FFMJ1,100.0,100.0,100.0,100.0,100.0,100.0,0.1,3e-6,7777;CUT07,100.0,100.0,100.0,100.0,100.0,100.0,0.1,3e-6,7778"<br> 4081 4117 </p> 4082 4118
Note:
See TracChangeset
for help on using the changeset viewer.