Changeset 4204 in ntrip for trunk/BNC/bnchelp.html
- Timestamp:
- May 22, 2012, 10:04:13 AM (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/BNC/bnchelp.html
r4203 r4204 1445 1445 </p> 1446 1446 <p> 1447 Note that Tomoji Takasu has written a program called RTKP lotfor visualizing NMEA strings. It is available from <u>http://gpspp.sakura.ne.jp/rtklib/rtklib.htm</u> and compatible with the NMEA file and port output of BNC's 'PPP' client option.1447 Note that Tomoji Takasu has written a program called RTKPLOT for visualizing NMEA strings. It is available from <u>http://gpspp.sakura.ne.jp/rtklib/rtklib.htm</u> and compatible with the NMEA file and port output of BNC's 'PPP' client option. 1448 1448 </p> 1449 1449 … … 1780 1780 1781 1781 <p> 1782 Below you find an example of precise clocks and orbits coming in ASCII format (named 'RTNET' in this document) from a real-time GNSS engine. Each epoch starts with an asterisk character followed by the time as year, month, day of month, hour, minute and second. Subsequent records provide the following set of parameters for each satellite: 1782 Below you find an example of precise clocks and orbits coming in ASCII format (which is named 'RTNET' in this document) from a real-time GNSS engine. Each epoch starts with an asterisk character followed by the time as year, month, day of month, hour, minute and second. Subsequent records provide the following set of parameters for each satellite: 1783 1783 </p> 1784 1784 … … 2591 2591 <li>chunked transfer encoding;</li> 2592 2592 <li>improvements in header records;</li> 2593 <li>source-table filtering; and</li>2593 <li>source-table filtering;</li> 2594 2594 <li>RTSP communication.</li> 2595 2595 </ul> … … 2600 2600 <p><a name="rtcm2"><h4>5.2.3 RTCM Version 2</h4></p> 2601 2601 <p> 2602 Transmitting GNSS carrier phase data can be done through RTCM Version 2 messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of someinterest here are:2602 Transmitting GNSS carrier phase data can be done through RTCM Version 2 messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of interest here are: 2603 2603 </p> 2604 2604 … … 2661 2661 <li>Type 4088 and 4095, Proprietary messages (under development). 2662 2662 </li> 2663 </ul> 2664 </p> 2665 2666 <p> 2667 The following are so-called 'State Space Representation' (SSR) messages: 2668 <ul> 2669 <li>Type 1057, GPS orbit corrections to Broadcast Ephemeris</li> 2670 <li>Type 1058, GPS clock corrections to Broadcast Ephemeris</li> 2671 <li>Type 1059, GPS code biases</li> 2672 <li>Type 1060, Combined orbit and clock corrections to GPS Broadcast Ephemeris</li> 2673 <li>Type 1061, GPS User Range Accuracy (URA)</li> 2674 <li>Type 1062, High-rate GPS clock corrections to Broadcast Ephemeris</li> 2675 <li>Type 1063, GLONASS orbit corrections to Broadcast Ephemeris</li> 2676 <li>Type 1064, GLONASS clock corrections to Broadcast Ephemeris</li> 2677 <li>Type 1065, GLONASS code biases</li> 2678 <li>Type 1066, Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li> 2679 <li>Type 1067, GLONASS User Range Accuracy (URA)</li> 2680 <li>Type 1068, High-rate GLONASS clock corrections to Broadcast Ephemeris</li> 2663 2681 </ul> 2664 2682 </p> … … 2692 2710 </p> 2693 2711 2694 <p>2695 The following are so-called 'State Space Representation' (SSR) messages:2696 <ul>2697 <li>Type 1057, GPS orbit corrections to Broadcast Ephemeris</li>2698 <li>Type 1058, GPS clock corrections to Broadcast Ephemeris</li>2699 <li>Type 1059, GPS code biases</li>2700 <li>Type 1060, Combined orbit and clock corrections to GPS Broadcast Ephemeris</li>2701 <li>Type 1061, GPS User Range Accuracy (URA)</li>2702 <li>Type 1062, High-rate GPS clock corrections to Broadcast Ephemeris</li>2703 <li>Type 1063, GLONASS orbit corrections to Broadcast Ephemeris</li>2704 <li>Type 1064, GLONASS clock corrections to Broadcast Ephemeris</li>2705 <li>Type 1065, GLONASS code biases</li>2706 <li>Type 1066, Combined orbit and clock corrections to GLONASS Broadcast Ephemeris</li>2707 <li>Type 1067, GLONASS User Range Accuracy (URA)</li>2708 <li>Type 1068, High-rate GLONASS clock corrections to Broadcast Ephemeris</li>2709 </ul>2710 </p>2711 2712 2712 <p><a name="config"><h4>5.3. Configuration Examples</h4></p> 2713 2713 … … 2716 2716 <li> On graphical systems you may use the computer mouse to 'drag' a configuration file icon and 'drop' it on top of BNC's program icon. 2717 2717 </li> 2718 <li> On non-graphical systems you may start BNC using a command line with the following option for a configuration file (example for Windows systems):<br>bnc.exe --conf <configFileName>2718 <li> On non-graphical systems you may start BNC using a command line with the following option for a configuration file (example for Windows systems):<br>bnc.exe --conf <configFileName> 2719 2719 </li> 2720 2720 </ul> … … 2725 2725 </p> 2726 2726 <p> 2727 Make also sure that directories which are part of the example configurations exist on your system or adjust the affected configuration according to your needs. 2728 </p> 2729 <p> 2730 Some BNC options require antenna phase center variations as made available from IGS through so-called ANTEX files in directory<u>ftp://igs.org/pub/station/general</u>. An example ANTEX file is also part of the BNC package for convenience.2731 </p> 2732 <p> 2733 The example configurations assume that no proxy protects your host. Should a proxy be operated in front of BNC then you need to introduce its IP and port in the 'Network' tab. 2727 Make also sure that directories which are part of the example configurations exist on your system or adjust the affected configuration options according to your needs. 2728 </p> 2729 <p> 2730 Some BNC options require antenna phase center variations as made available from IGS through so-called ANTEX files at <u>ftp://igs.org/pub/station/general</u>. An example ANTEX file is also part of the BNC package for convenience. 2731 </p> 2732 <p> 2733 The example configurations assume that no proxy protects your BNC host. Should a proxy be operated in front of BNC then you need to introduce its IP and port in the 'Network' tab. 2734 2734 </p> 2735 2735 2736 2736 <ol type=b> 2737 2737 <li>File 'RinexObs.bnc'<br> 2738 The purpose of this configuration is to convert RTCM streams to RINEX Observation files. The configuration pulls streams from several Ntrip Broadcasters using differen Ntrip versions and generate 1sec/15minRINEX Version 3 Observation files. See <u>http://igs.bkg.bund.de/ntrip/observations</u> for observation stream resources.2738 The purpose of this configuration is to convert RTCM streams to RINEX Observation files. The configuration pulls streams from several Ntrip Broadcasters using different Ntrip versions and generate 15min 1Hz RINEX Version 3 Observation files. See <u>http://igs.bkg.bund.de/ntrip/observations</u> for observation stream resources. 2739 2739 </li> 2740 2740 <br> 2741 <li>File 'RinexEp n.bnc'<br>2742 The purpose of this configuration is to convert RTCM streams to RINEX Navigation files. The configuration pulls an RTCM Version 3 stream carrying Broadcast Ephemeris coming from the real-time EUREF and IGS network. It saves hourly RINEX Version 3 Navigation files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time Broadcast Ephemeris resources. 2741 <li>File 'RinexEph.bnc'<br> 2742 The purpose of this configuration is to convert RTCM streams to RINEX Navigation files. The configuration pulls an RTCM Version 3 stream carrying Broadcast Ephemeris coming from the real-time EUREF and IGS network. It saves hourly RINEX Version 3 Navigation files. See <u>http://igs.bkg.bund.de/ntrip/ephemeris</u> for further real-time Broadcast Ephemeris resources. 2743 2743 </li> 2744 2744 <br> 2745 2745 <li>File 'SSR.bnc'<br> 2746 The purpose of this configuration is to save Broadcast Eorrections from RTCM SSR messages in a plain ASCII format as hourly files. See <u>http://igs.bkg.bund.de/ntrip/orbits</u> for further real-time IGS or EUREF orbit/clock products.2746 The purpose of this configuration is to save Broadcast Corrections from RTCM SSR messages in a plain ASCII format as hourly files. See <u>http://igs.bkg.bund.de/ntrip/orbits</u> for further real-time IGS or EUREF orbit/clock products. 2747 2747 </li> 2748 2748 <br> … … 2760 2760 <br> 2761 2761 <li>File 'PPP.bnc'<br> 2762 The purpose of this configuration is Precise Point Positioning from observations of a rover receiver. The configuration reads RTCM Version 3 observations, a stream of orbit and clock correctors and a Broadcast Ephemeris stream. Positions are saved in the logfile.2762 The purpose of this configuration is Precise Point Positioning from observations of a rover receiver. The configuration reads RTCM Version 3 observations, a stream of Broadcast Corrections and a Broadcast Ephemeris stream. Positions are saved in the logfile. 2763 2763 </li> 2764 2764 <br> 2765 2765 <li>File 'QuickStartPPP.bnc'<br> 2766 The purpose of this configuration is Precise Point Positioning in Quick-Start mode from observations of a static receiver with precisely known position. The configuration reads RTCM Version 3 observations, orbit and clock correctors and a Broadcast Ephemeris stream. Positions are saved in NMEA format on discandoutput through IP port for real-time visualization with tools like RTKNAVI.2766 The purpose of this configuration is Precise Point Positioning in Quick-Start mode from observations of a static receiver with precisely known position. The configuration reads RTCM Version 3 observations, Broadcast Corrections and a Broadcast Ephemeris stream. Positions are saved in NMEA format on disc. Positions are also output through IP port for real-time visualization with tools like RTKPLOT. 2767 2767 </li> 2768 2768 <br> 2769 2769 <li>File 'PPPPostProc.bnc<br> 2770 The purpose of this configuration is Precise Point Positioning in Post Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation files and a Broadcast Corrections files. PPP processing otions are set in support ofthe Quick-Start mode. The output is saved in a specific Post Processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm.2770 The purpose of this configuration is Precise Point Positioning in Post Processing mode. BNC reads a RINEX Observation and a RINEX Version 3 Navigation files and a Broadcast Corrections files. PPP processing otions are set to support the Quick-Start mode. The output is saved in a specific Post Processing logfile and contains the coordinates derived over time following the implemented PPP filter algorithm. 2771 2771 </li> 2772 2772 <br> … … 2776 2776 <br> 2777 2777 <li>File 'Sp3ETRF2000PPP.bnc'<br> 2778 The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The Broadcast Corrections stream is formally introduced in BNC's 'Combin ation' option. This all together leads to an SP3 file containing orbits referrd also to ETRF2000. Pulling in addition observations from a reference station at precisely known ETRF2000 position allows to compare an 'INTERNAL' PPP solution with ETRF2000 reference coordinates.2778 The purpose of this configuration is to produce SP3 files from a Broadcast Ephemeris stream and a stream carrying ETRF2000 Broadcast Corrections. The Broadcast Corrections stream is formally introduced in BNC's 'Combine Corrections' table. This leads to an SP3 file containing orbits referred also to ETRF2000. Pulling in addition observations from a reference station at precisely known ETRF2000 position allows to compare an 'INTERNAL' PPP solution with ETRF2000 reference coordinates. 2779 2779 </li> 2780 2780 <br> 2781 2781 <li>File 'Upload.bnc'<br> 2782 The purpose of this configuration is to upload orbits and clocks from a real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads precise orbits and clocks in RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast Corrections and encodes them in RTCM Version 3 SSR messages messagesto uploads them to an Ntrip Broadcaster. The Broadcast Corrections stream is referred to satelliteCenter of Mass (CoM) and IGS08. Orbits are saved on disk in SP3 format and clocks inclock RINEX format.2782 The purpose of this configuration is to upload orbits and clocks from a real-time GNSS engine to an Ntrip Broadcaster. For that the configuration reads precise orbits and clocks in RTNET format. It also reads a stream carrying Broadcast Ephemeris. BNC converts the orbits and clocks into Broadcast Corrections and encodes them in RTCM Version 3 SSR messages to uploads them to an Ntrip Broadcaster. The Broadcast Corrections stream is referred to satellite Antenna Phase Center (APC) and IGS08. Orbits are saved on disk in SP3 format and clocks in Clock RINEX format. 2783 2783 </li> 2784 2784 <br> 2785 2785 <li>File 'UploadPPP.bnc'<br> 2786 This configuration equals the 'Upload.bnc' configuration. However, the Broadcast Corrections are in addition used for an 'INTERNAL' PPP soltution based on observations from a static reference station with known precise coordinates. This allows a continuous quality c keck of the Broadcast Corrections through observing coordinate displacements.2786 This configuration equals the 'Upload.bnc' configuration. However, the Broadcast Corrections are in addition used for an 'INTERNAL' PPP soltution based on observations from a static reference station with known precise coordinates. This allows a continuous quality check of the Broadcast Corrections through observing coordinate displacements. 2787 2787 </li> 2788 2788 <br> 2789 2789 <li>File 'Combi.bnc'<br> 2790 The purpose of this configuration is to pull sseveral streams carrying Broadcast Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the combination product in RTCM Version 3 SSR messages and uploadsit to an Ntrip Broadcaster. The Broadcast Corrections stream is not referred to satellite Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format and clocks inclock RINEX format.2790 The purpose of this configuration is to pull several streams carrying Broadcast Corrections and a Broadcast Ephemeris stream from an Ntrip Broadcaster to produce a combined Broadcast Corrections stream. BNC encodes the combination product in RTCM Version 3 SSR messages and uploads that to an Ntrip Broadcaster. The Broadcast Corrections stream is not referred to satellite Center of Mass (CoM). It is referred to IGS08. Orbits are saved in SP3 format and clocks in Clock RINEX format. 2791 2791 </li> 2792 2792 <br> … … 2796 2796 <br> 2797 2797 <li>File 'UploadEph.bnc'<br> 2798 The purpose of this configuration is to pull a number of streams from reference stations to get hold of contained Broadcast Ephemeris messages. These are encoded then in a specificRTCM Version 3 stream which only provides Broadcast Ephemeris with an update rate of 5 seconds.2798 The purpose of this configuration is to pull a number of streams from reference stations to get hold of contained Broadcast Ephemeris messages. These are encoded then in a RTCM Version 3 stream which only provides Broadcast Ephemeris with an update rate of 5 seconds. 2799 2799 </li> 2800 2800 </ol> … … 2802 2802 2803 2803 <p> 2804 The following table's left column is a n example for the contents of aconfiguration file'BNC.bnc'. It enables the retrieval of an observations stream via NTRIP for the generation of 15 min RINEX files:2804 The following table's left column is a list options as contained in BNC's configuration files (default: BNC.bnc). 2805 2805 </p> 2806 2806 <table> … … 2808 2808 <tr><td><b>Option</b></td><td><b>Affiliation</b></td></tr> 2809 2809 <tr><td>[General]</td><td>Settings: Group</td></tr> 2810 <tr><td>startTab= 0</td><td>Internal: Top tab index</td></tr>2811 <tr><td>statusTab= 0</td><td>Internal: Bottom tab index</td></tr>2810 <tr><td>startTab=</td><td>Internal: Top tab index</td></tr> 2811 <tr><td>statusTab=</td><td>Internal: Bottom tab index</td></tr> 2812 2812 <tr><td>font=</td><td>Internal: Used font</td></tr> 2813 <tr><td>casterUrlList= http://user:pass@euref-ip:2101</td><td>Internal: Visited URLs</td></tr>2814 <tr><td>mountPoints= //user:pass@www.euref-ip.net:2101<br>/ACOR0 RTCM_2.3 43.36 351.60 no 1</td><td>Add Streams: broadcaster:port/mountpoint</td></tr>2815 <tr><td>ntripVersion= 1</td><td>Add Stream: NTRIP Version</td></tr>2813 <tr><td>casterUrlList=</td><td>Internal: Visited URLs</td></tr> 2814 <tr><td>mountPoints=</td><td>Add Streams: broadcaster:port/mountpoint</td></tr> 2815 <tr><td>ntripVersion=</td><td>Add Stream: NTRIP Version</td></tr> 2816 2816 2817 2817 <tr><td>proxyHost=</td><td>Network: Proxy host</td></tr> … … 2820 2820 <tr><td>ignoreSslErrors=0</td><td>Network: Ignore ssl authorization errors</td></tr> 2821 2821 2822 <tr><td>logFile= /home/weber/bnc.log</td><td>General: Logfile (full path)</td></tr>2823 <tr><td>rnxAppend= 2</td><td>General: Append files</td></tr>2824 <tr><td>onTheFlyInterval= 1 day</td><td>General: Reread configuration</td></tr>2825 <tr><td>autoStart= 0</td><td>General: Auto start</td></tr>2822 <tr><td>logFile=</td><td>General: Logfile (full path)</td></tr> 2823 <tr><td>rnxAppend=</td><td>General: Append files</td></tr> 2824 <tr><td>onTheFlyInterval=</td><td>General: Reread configuration</td></tr> 2825 <tr><td>autoStart=</td><td>General: Auto start</td></tr> 2826 2826 <tr><td>rawOutFile=</td><td>General: Raw output file (full path)</td></tr> 2827 2827 2828 <tr><td>rnxPath= /home/user/rinex</td><td>RINEX Observations: Directory</td></tr>2829 <tr><td>rnxIntr= 15 min</td><td>RINEX Observations: Interval</td></tr>2830 <tr><td>rnxSample= 0</td><td>RINEX Observations: Sampling</td></tr>2828 <tr><td>rnxPath=</td><td>RINEX Observations: Directory</td></tr> 2829 <tr><td>rnxIntr=</td><td>RINEX Observations: Interval</td></tr> 2830 <tr><td>rnxSample=</td><td>RINEX Observations: Sampling</td></tr> 2831 2831 <tr><td>rnxSkel=</td><td>RINEX Observations: Skeleton extension</td></tr> 2832 2832 <tr><td>rnxScript=</td><td>RINEX Observations: Uplod script</td></tr> 2833 <tr><td>rnxV3= 0</td><td>RINEX Observation: Version 3</td></tr>2833 <tr><td>rnxV3=</td><td>RINEX Observation: Version 3</td></tr> 2834 2834 2835 2835 <tr><td>ephPath=</td><td>RINEX Ephemeris: Directory</td></tr> 2836 <tr><td>ephIntr= 15 min</td><td>RINEX Ephemeris: Interval</td></tr>2836 <tr><td>ephIntr=</td><td>RINEX Ephemeris: Interval</td></tr> 2837 2837 <tr><td>outEphPort=</td><td>RINEX Ephemeris: Port</td></tr> 2838 <tr><td>ephV3= 0</td><td>RINEX Ephemeris: Version 3</td></tr>2838 <tr><td>ephV3=</td><td>RINEX Ephemeris: Version 3</td></tr> 2839 2839 2840 2840 <tr><td>corrPath=</td><td>Broadcast Corrections: Directory, ASCII </td></tr> 2841 <tr><td>corrIntr= 1 day</td><td>Broadcast Corrections: Interval</td></tr>2841 <tr><td>corrIntr=</td><td>Broadcast Corrections: Interval</td></tr> 2842 2842 <tr><td>corrPort=</td><td>Broadcast Corrections: Port</td></tr> 2843 <tr><td>corrTime= 5</td><td>Broadcast Corrections: Wait for full corr epoch</td></tr>2843 <tr><td>corrTime=</td><td>Broadcast Corrections: Wait for full corr epoch</td></tr> 2844 2844 2845 2845 <tr><td>outPort=</td><td>Feed Engine: Port</td></tr> 2846 <tr><td>waitTime= 5</td><td>Feed Engine: Wait for full obs epoch</td></tr>2847 <tr><td>binSampl= 0</td><td>Feed Engine: Sampling</td></tr>2846 <tr><td>waitTime=</td><td>Feed Engine: Wait for full obs epoch</td></tr> 2847 <tr><td>binSampl=</td><td>Feed Engine: Sampling</td></tr> 2848 2848 <tr><td>outFile=</td><td>Feed Engine: File (full path)</td></tr> 2849 2849 <tr><td>outUPort=</td><td>Feed Engine: Port (unsynchronized)</td></tr> … … 2851 2851 <tr><td>serialMountPoint=</td><td>Serial Output: Mountpoint</td></tr> 2852 2852 <tr><td>serialPortName=</td><td>Serial Output: Port name</td></tr> 2853 <tr><td>serialBaudRate= 9600</td><td>Serial Output: Baud rate</td></tr>2853 <tr><td>serialBaudRate=</td><td>Serial Output: Baud rate</td></tr> 2854 2854 <tr><td>serialFlowControl=</td><td>Serial Output: Flow control</td></tr> 2855 <tr><td>serialDataBits= 8</td><td>Serial Output: Data bits</td></tr>2856 <tr><td>serialParity= NONE</td><td>Serial Output: Parity</td></tr>2857 <tr><td>serialStopBits= 1</td><td>Serial Output: Stop bits</td></tr>2858 <tr><td>serialAutoNMEA= Auto</td><td>Serial Output: NMEA</td></tr>2855 <tr><td>serialDataBits=</td><td>Serial Output: Data bits</td></tr> 2856 <tr><td>serialParity=</td><td>Serial Output: Parity</td></tr> 2857 <tr><td>serialStopBits=</td><td>Serial Output: Stop bits</td></tr> 2858 <tr><td>serialAutoNMEA=</td><td>Serial Output: NMEA</td></tr> 2859 2859 <tr><td>serialFileNMEA=</td><td>Serial Output: NMEA file name</td></tr> 2860 2860 <tr><td>serialHeightNMEA=</td><td>Serial Output: Height</td></tr> 2861 2861 2862 2862 <tr><td>obsRate=</td><td>Outages: Observation rate</td></tr> 2863 <tr><td>adviseFail= 15</td><td>Outages: Failure threshold</td></tr>2864 <tr><td>adviseReco= 5</td><td>Outages: Recovery threshold</td></tr>2863 <tr><td>adviseFail=</td><td>Outages: Failure threshold</td></tr> 2864 <tr><td>adviseReco=</td><td>Outages: Recovery threshold</td></tr> 2865 2865 <tr><td>adviseScript=</td><td>Outages: Script (full path)</td></tr> 2866 2866 2867 2867 <tr><td>miscMount=</td><td>Miscellaneous: Mountpoint</td></tr> 2868 2868 <tr><td>perfIntr=</td><td>Miscellaneous: Log latency</td></tr> 2869 <tr><td>scanRTCM= 0</td><td>Miscellaneous: Scan RTCM</td></tr>2870 2871 <tr><td>pppSPP= PPP</td><td>PPP Client: PPP/SPP</td></tr>2869 <tr><td>scanRTCM=</td><td>Miscellaneous: Scan RTCM</td></tr> 2870 2871 <tr><td>pppSPP=</td><td>PPP Client: PPP/SPP</td></tr> 2872 2872 <tr><td>pppMount=</td><td>PPP Client: Observations Mountpoint</td></tr> 2873 2873 <tr><td>pppCorrMount=</td><td>PPP Client: Corrections Mountpoint</td></tr> … … 2888 2888 <tr><td>pppAntex=</td><td>PPP Client: Path to ANTEX file</td></tr> 2889 2889 <tr><td>pppApplySatAnt=</td><td>PPP Client: Apply sat antenna phase center Offset</td></tr> 2890 <tr><td>pppUsePhase= 0</td><td>PPP Client: Use phase data </td></tr>2891 <tr><td>pppEstTropo= 0</td><td>PPP Client: Estimate troposphere</td></tr>2892 <tr><td>pppGLONASS= 0</td><td>PPP Client: Use GLONASS</td></tr>2893 <tr><td>pppGalileo= 0</td><td>PPP Client: Use Galileo</td></tr>2890 <tr><td>pppUsePhase=</td><td>PPP Client: Use phase data </td></tr> 2891 <tr><td>pppEstTropo=</td><td>PPP Client: Estimate troposphere</td></tr> 2892 <tr><td>pppGLONASS=</td><td>PPP Client: Use GLONASS</td></tr> 2893 <tr><td>pppGalileo=</td><td>PPP Client: Use Galileo</td></tr> 2894 2894 <tr><td>pppSync=</td><td>PPP Client: Sync observations and corrections</td></tr> 2895 2895 <tr><td>pppAverage=</td><td>PPP Client: Lenght of time window for moving average</td></tr> 2896 2896 <tr><td>pppQuickStart=200</td><td>PPP Client: Quick-Start period</td></tr> 2897 2897 <tr><td>pppMaxSolGap=</td><td>PPP Client: Maximal Solution Gap</td></tr> 2898 <tr><td>pppSigmaCode= 5.0</td><td>PPP Client: Sigma for Code observations</td></tr>2899 <tr><td>pppSigmaPhase= 0.02</td><td>PPP Client: Sigma for Phase observations</td></tr>2900 <tr><td>pppSigmaCrd0= 100.0</td><td>PPP Client: Sigma for initial XYZ coordinate</td></tr>2901 <tr><td>pppSigmaCrdP= 100.0</td><td>PPP Client: White noise for XYZ</td></tr>2902 <tr><td>pppSigmaTrp0= 0.1</td><td>PPP Client: Sigma for initial tropospheric delay</td></tr>2903 <tr><td>pppSigmaTrpP= 1e-6</td><td>PPP Client: White noise for tropospheric delay</td></tr>2898 <tr><td>pppSigmaCode=</td><td>PPP Client: Sigma for Code observations</td></tr> 2899 <tr><td>pppSigmaPhase=</td><td>PPP Client: Sigma for Phase observations</td></tr> 2900 <tr><td>pppSigmaCrd0=</td><td>PPP Client: Sigma for initial XYZ coordinate</td></tr> 2901 <tr><td>pppSigmaCrdP=</td><td>PPP Client: White noise for XYZ</td></tr> 2902 <tr><td>pppSigmaTrp0=</td><td>PPP Client: Sigma for initial tropospheric delay</td></tr> 2903 <tr><td>pppSigmaTrpP=</td><td>PPP Client: White noise for tropospheric delay</td></tr> 2904 2904 2905 2905 <tr><td>reqcAction=</td><td>Reqc: Action</td></tr> … … 2927 2927 <tr><td>cmbSampl=</td><td>Combination: Orbit and clock sampling</td></tr> 2928 2928 2929 <tr><td>uploadIntr= 1 day</td><td>Upload Corrections: File interval</td></tr>2929 <tr><td>uploadIntr=</td><td>Upload Corrections: File interval</td></tr> 2930 2930 <tr><td>uploadMountpointsOut=</td><td>Upload Corrections: Upload streams</td></tr> 2931 <tr><td>uploadSamplClkRnx= 10</td><td>Upload Corrections: Clock sampling</td></tr>2932 <tr><td>uploadSamplSp3= 1</td><td>Upload Corrections: Orbit sampling</td></tr>2933 <tr><td>uploadSamplRtcmEphCorr= 0</td><td>Upload Corrections: Orbit sampling</td></tr>2931 <tr><td>uploadSamplClkRnx=</td><td>Upload Corrections: Clock sampling</td></tr> 2932 <tr><td>uploadSamplSp3=</td><td>Upload Corrections: Orbit sampling</td></tr> 2933 <tr><td>uploadSamplRtcmEphCorr=</td><td>Upload Corrections: Orbit sampling</td></tr> 2934 2934 <tr><td>trafo_dx=</td><td>Upload Corrections: Translation X</td></tr> 2935 2935 <tr><td>trafo_dy=</td><td>Upload Corrections: Translation Y</td></tr> … … 2951 2951 <tr><td>uploadEphMountpoint=</td><td>Upload Ephemeris: Moutpoint</td></tr> 2952 2952 <tr><td>uploadEphPassword=</td><td>Upload Ephemeris: Password</td></tr> 2953 <tr><td>uploadEphSample= 5</td><td>Upload Ephemeris: Samplig</td></tr>2953 <tr><td>uploadEphSample=</td><td>Upload Ephemeris: Samplig</td></tr> 2954 2954 </table> 2955 2955 </p>
Note:
See TracChangeset
for help on using the changeset viewer.