Changeset 9160 in ntrip
- Timestamp:
- Oct 1, 2020, 3:52:14 PM (4 years ago)
- Location:
- branches/BNC_2.12/src
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/BNC_2.12/src/bnchelp.html
r9091 r9160 1252 1252 <p><h4>2.3.1 <a name="genlog">Logfile - optional</h4></p> 1253 1253 <p> 1254 Records of BNC's activities are shown in the 'Log' tab on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. The logfile name will automatically be extended by a string '_YYMMDD' for the current date. This leads to series of daily logfiles when running BNC continuously. Message logs cover the communication status between BNC and the Ntrip Broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. The time stamps within the 'Log' tab are given in UTC. The time stamps within the logfile are given in GPS Time. The default value for 'Logfile (full path)' is an empty option field, meaning that BNC logs will not be saved into a file. 1254 Records of BNC's activities are shown in the 'Log' tab on the bottom of the main window. These logs can be saved into a file when a valid path is specified in the 'Logfile (full path)' field. The logfile name will automatically be extended by a string '_YYMMDD' for the current date. This leads to series of daily logfiles when running BNC continuously. Message logs cover the communication status between BNC and the Ntrip Broadcaster as well as problems that may occur in the communication link, stream availability, stream delay, stream conversion etc. The time stamps within the 'Log' tab are given in UTC. The time stamps within the logfile are given in GPS Time. The default value for 'Logfile (full path)' is an empty option field, meaning that BNC logs will not be saved into a file. 1255 1255 </p> 1256 1256 <p> … … 1430 1430 <p><h4>2.4.5 <a name="rnxskl">Skeleton Extension - optional</h4></p> 1431 1431 <p> 1432 Whenever BNC starts to generate RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. An HTTP or HTTPS link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See <a href="https://igs.bkg.bund.de/root_ftp/IGS/station/rnxskl/BRUX00BEL.skl" target="_blank">https://igs.bkg.bund.de/root_ftp/IGS/station/rnxskl/BRUX00BEL.skl</a> 1432 Whenever BNC starts to generate RINEX Observation files (and then once every day at midnight), it first tries to retrieve information needed for RINEX headers from so-called public RINEX header skeleton files which are derived from sitelogs. An HTTP or HTTPS link to a directory containing these skeleton files may be available through data field number 7 of the affected NET record in the source-table. See <a href="https://igs.bkg.bund.de/root_ftp/IGS/station/rnxskl/BRUX00BEL.skl" target="_blank">https://igs.bkg.bund.de/root_ftp/IGS/station/rnxskl/BRUX00BEL.skl</a> 1433 1433 for an example of a public RINEX header skeleton file for EPN station Brussels. Note that the download of RINEX skeleton files from HTTPS websites requires the exchange of client and/or server certificates. Clarify 'SSL' options offered through panel 'Network' for details. 1434 1434 </p> … … 1950 1950 </pre> 1951 1951 <p> 1952 contains 1952 contains 1953 1953 </p> 1954 1954 <ul> … … 1971 1971 <p><h4 id="reqcplots">2.6.5 Plots for Signals - mandatory if 'Action' is set to 'Analyze'</h4></p> 1972 1972 <p> 1973 BNC can produce plots for multipath, signal-to-noise ratio, satellite availability, satellite elevation, and PDOP values. The 'Plots for signals' option lets you exactly specify the observation signals to be used for that and also enables the plot production. 1974 You can specify the navigation system (C = BDS, E = Galileo, G = GPS, J = QZSS, R = GLONASS, S = SBAS), the frequency, and the tracking mode or channel as defined in RINEX Version 3. Specifications for frequency 1975 and tracking mode or channel must be separated by ampersand character '&'. Specifications for each navigation systems must be separated by blank character ' '. 1973 BNC can produce plots for multipath, signal-to-noise ratio, satellite availability, satellite elevation, and PDOP values. The 'Plots for signals' option lets you exactly specify the observation signals to be used for that and also enables the plot production. 1974 You can specify the navigation system (C = BDS, E = Galileo, G = GPS, J = QZSS, R = GLONASS, S = SBAS), the frequency, and the tracking mode or channel as defined in RINEX Version 3. Specifications for frequency 1975 and tracking mode or channel must be separated by ampersand character '&'. Specifications for each navigation systems must be separated by blank character ' '. 1976 1976 1977 1977 <p>Examples for 'Plots for signals' option:<ul><li> G:1&2 R:1&2 J:1&2 E:1&7 C:1&6 S:1<br> 1978 (Plots will be based on GPS observations on 1st and 2nd frequency, GLONASS observations on 1st and 2nd frequency, 1979 QZSS observations on 1st and 2nd frequency, Galileo observations on 1st and 7th frequency, BeiDou observations on 1978 (Plots will be based on GPS observations on 1st and 2nd frequency, GLONASS observations on 1st and 2nd frequency, 1979 QZSS observations on 1st and 2nd frequency, Galileo observations on 1st and 7th frequency, BeiDou observations on 1980 1980 1st and 6th frequency, SBAS observations on 1st frequency.) 1981 1981 </li> … … 1986 1986 </p> 1987 1987 <p> 1988 Default is 'C:2&7 E:1&5 G:1&2 J:1&2 R:1&2 S:1&5 I:5&9'. Specifying an empty option string would be overruled by this default. 1988 Default is 'C:2&7 E:1&5 G:1&2 J:1&2 R:1&2 S:1&5 I:5&9'. Specifying an empty option string would be overruled by this default. 1989 1989 </p> 1990 1990 … … 2610 2610 2611 2611 <p> 2612 Each epoch in the synchronized output begins with a line containing the GPS Week Number and the seconds within the GPS Week. Following lines begin with the mountpoint string of the stream which provides the observations followed by a satellite number. Specifications for satellite number, code, phase, Doppler and signal strength data follow definitions presented in the RINEX Version 3 documentation. In case of phase observations, a 'Slip Counter' is added. The end of an epoch is indicated by an empty line. 2612 Each epoch in the synchronized output begins with a line containing the GPS Week Number and the seconds within the GPS Week. Following lines begin with the mountpoint string of the stream which provides the observations followed by a satellite number. Specifications for satellite number, code, phase, Doppler and signal strength data follow definitions presented in the RINEX Version 3 documentation. In case of phase observations, a 'Slip Counter' is added. The end of an epoch is indicated by an empty line. 2613 2613 </p> 2614 2614 … … 4997 4997 rnxV2Priority {Priority of signal attributes [character string, list separated by blank character, example: G:CWPX_? R:CP]} 4998 4998 rnxV3 {Produce version 3 file content [integer number: 0=no,2=yes]} 4999 rnxV3filenames {Produce version 3 filenames [integer number: 0=no,2=yes]}5000 4999 5001 5000 <b>RINEX Ephemeris Panel keys:</b> … … 5004 5003 ephOutPort {Output port [integer number]} 5005 5004 ephV3 {Produce version 3 file content [integer number: 0=no,2=yes]} 5006 ephV3filenames {Produce version 3 filenames [integer number: 0=no,2=yes]}5007 5005 5008 5006 <b>RINEX Editing and QC Panel keys:</b> -
branches/BNC_2.12/src/bncmain.cpp
r9157 r9160 399 399 bncGetThread* getThread = 0; 400 400 401 #ifndef WIN32 401 402 signal(SIGPIPE, catch_SIGPIPE); 403 #endif 402 404 403 405 // Interactive Mode - open the main window
Note:
See TracChangeset
for help on using the changeset viewer.