Changeset 1409 in ntrip


Ignore:
Timestamp:
Dec 30, 2008, 8:53:34 PM (16 years ago)
Author:
weber
Message:

* empty log message *

Location:
trunk/BNC
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • trunk/BNC/bnchelp.html

    r1371 r1409  
    130130&nbsp; &nbsp; &nbsp; 3.12.2. <a href=#streamhost>Caster Host and Port</a><br>
    131131&nbsp; &nbsp; &nbsp; 3.12.3. <a href=#streamuser>Caster User and Password</a><br>
    132 &nbsp; &nbsp; &nbsp; 3.12.4. <a href=#streamtable>Get Table</a><br>
    133 &nbsp; &nbsp; &nbsp; 3.12.5. <a href=#streamdelete>Delete Streams</a><br>
    134 &nbsp; &nbsp; &nbsp; 3.12.6. <a href=#streamedit>Edit Streams</a><br>
    135 &nbsp; &nbsp; &nbsp; 3.12.7. <a href=#streamconf>Reconfigure Streams On-the-fly</a><br>
     132&nbsp; &nbsp; &nbsp; 3.12.4. <a href=#streamntrip>NTRIP Version</a><br>
     133&nbsp; &nbsp; &nbsp; 3.12.5. <a href=#streamtable>Get Table</a><br>
     134&nbsp; &nbsp; &nbsp; 3.12.6. <a href=#streamdelete>Delete Streams</a><br>
     135&nbsp; &nbsp; &nbsp; 3.12.7. <a href=#streamedit>Edit Streams</a><br>
     136&nbsp; &nbsp; &nbsp; 3.12.8. <a href=#streamconf>Reconfigure Streams On-the-fly</a><br>
    1361373.13. <a href=#start>Start</a><br>
    1371383.14. <a href=#stop>Stop</a><br>
    … …  
    736737</p>
    737738
     739<p>
    738740Streams selected for retrieval are listed under the 'Streams' canvas section on BNC's main window. The list provides the following information extracted from source-table(s) produced by the NTRIP broadcasters:
     741</p>
    739742 
    740743<table>
    741 <tr></tr>
    742 <tr><td>'broadcaster:port' &nbsp;</td><td>NTRIP broadcaster URL and port.</td></tr>
     744<tr><td>'broadcaster:port'&nbsp; </td><td>NTRIP broadcaster URL and port.</td></tr>
    743745<tr><td>'mountpoint' &nbsp;</td><td>Mountpoint on NTRIP broadcaster.</td></tr>
    744746<tr><td>'decoder' &nbsp;</td><td>Type of decoder used to handle the incoming stream content according to its format; editable.</td></tr>
    … …  
    746748<tr><td>'long' &nbsp;</td><td>Approximate longitude of reference station, in degrees, east; editable if 'nmea' = 'yes'.</td></tr>
    747749<tr><td>'nmea' &nbsp;</td><td>Indicates whether or not streaming needs to be initiated by BNC through sending NMEA-GGA message carrying position coordinates in 'lat' and 'long'.</td></tr>
     750<tr><td>'ntrip' &nbsp;</td><td>Selected NTRIP transport protocol version.</td></tr>
    748751<tr><td>'bytes' &nbsp;</td><td>Number of bytes retrieved.
    749752</table>
    … …  
    764767</p>
    765768
    766 <p><a name="streamtable"><h4>3.12.4 Get Table</h4></p>
     769<p><a name="streamntrip"><h4>3.12.4 NTRIP Version - mandatory</h4></p>
     770<p>
     771Some limitations and deficiencies of the NTRIP version 1 stream transport protocol are solved in NTRIP version 2. Improvements mainly concern a full HTTP compatibility in view of requirements coming from proxy servers. Options implemented in BNC are:
     772</p>
     773<p>
     774&nbsp; 1:&nbsp; NTRIP version 1 in TCP/IP mode,<br>
     775&nbsp; 2:&nbsp; NTRIP version 2 in TCP/IP mode.
     776</p>
     777<p>
     778Try using option '2' if your streams are blocked by a proxy and protocol version 2 is supported by the broadcaster. Select option '1' if you not sure whether the broadcaster supports NTRIP version 2.
     779</p>
     780
     781
     782
     783</p>
     784
     785<p><a name="streamtable"><h4>3.12.5 Get Table</h4></p>
    767786<p>
    768787Use the 'Get Table' button to download the source-table from the NTRIP broadcaster. Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message types 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message types 1002 or 1004 and may contain GLONASS message types 1010 or 1012, see data field 'format-details' for available message types and their repetition rates in brackets. Note that in order to produce RINEX Navigation files RTCM Version 3.x streams containing message types 1019 (GPS) and 1020 (GLONASS) are required. Select your streams line by line, use +Shift and +Ctrl when necessary.
    … …  
    775794</p>
    776795
    777 <p><a name="streamdelete"><h4>3.12.5 Delete Streams</h4></p>
     796<p><a name="streamdelete"><h4>3.12.6 Delete Streams</h4></p>
    778797<p>
    779798To remove a stream from the 'Streams' canvas in the main window, highlight it by clicking on it and hit the 'Delete Streams' button. You can also remove multiple streams simultaneously by highlighting them using +Shift and +Ctrl.</p>
    780799
    781 <p><a name="streamedit"><h4>3.12.6 Edit Streams</h4></p>
     800<p><a name="streamedit"><h4>3.12.7 Edit Streams</h4></p>
    782801<ul>
    783802<li>
    … …  
    789808<li>
    790809BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA format to the NTRIP broadcaster. In return, a user-specific data stream is generated, typically by a Network-RTK software. VRS streams are indicated by a 'yes' in the source-table as well as in the 'nmea' column on the 'Streams' canvas in BNC's main window. They are customized exactly to the latitude and longitude transmitted to the NTRIP broadcaster via NMEA-GGA messages.
    791 <br>If NMEA-GGA messages are not coming from a serial connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'lon' columns on the 'Streams' canvas. However, in most cases you would probably want to change these defaults according to your requirement. Double-click on 'lat' and 'lon' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only streams with a 'yes' in their 'nmea' column can be edited. The position must preferably be a point within the VRS service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'lon' used.
     810<br>If NMEA-GGA messages are not coming from a serial connected GNSS rover, BNC simulates them from the default latitude and longitude of the source-table as shown in the 'lat' and 'long' columns on the 'Streams' canvas. However, in most cases you would probably want to change these defaults according to your requirement. Double-click on 'lat' and 'long' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (example: 358.872 or -1.128). Only streams with a 'yes' in their 'nmea' column can be edited. The position must preferably be a point within the VRS service area of the network. RINEX files generated from these streams will contain an additional COMMENT line in the header beginning with 'NMEA' showing the 'lat' and 'long' used.
    792811<br>Note that when running BNC in a Local Area Network (LAN), NMEA strings may be blocked by a proxy server, firewall or virus scanner.
    793812</li>
    794813</ul>
    795814
    796 <p><a name="streamconf"><h4>3.12.7 Reconfigure Streams On-the-fly</h4></p>
     815<p><a name="streamconf"><h4>3.12.8 Reconfigure Streams On-the-fly</h4></p>
    797816<p>
    798817The streams selection can be changed on-the-fly without interrupting uninvolved threads in the running BNC process.
    … …  
    9169358.1. <a href=#history>History</a><br>
    9179368.2. <a href=#rtcm>RTCM</a><br>
    918 &nbsp; &nbsp; &nbsp; 8.2.1 <a href=#ntrip>NTRIP</a><br>
    919 &nbsp; &nbsp; &nbsp; 8.2.2 RTCM <a href=#rtcm2>Version 2.x</a><br>
    920 &nbsp; &nbsp; &nbsp; 8.2.3 RTCM <a href=#rtcm3>Version 3.x</a><br>
     937&nbsp; &nbsp; &nbsp; 8.2.1 NTRIP <a href=#ntrip1>Version 1</a><br>
     938&nbsp; &nbsp; &nbsp; 8.2.2 NTRIP <a href=#ntrip2>Version 2</a><br>
     939&nbsp; &nbsp; &nbsp; 8.2.3 RTCM <a href=#rtcm2>Version 2.x</a><br>
     940&nbsp; &nbsp; &nbsp; 8.2.4 RTCM <a href=#rtcm3>Version 3.x</a><br>
    9219418.3. <a href=#rtigs>RTIGS</a><br>
    922942&nbsp; &nbsp; &nbsp; 8.3.1 <a href=#soc>SOC</a><br>
    … …  
    935955<tr><td>Apr 2008 &nbsp;</td><td>Version 1.5 &nbsp;</td><td>[Add] Handle ephemeris from RTCM Version 3.x streams<br> [Add] Upgrade to Qt Version 4.3.2<br> [Add] Optional RINEX v3 output<br> [Add] SBAS support<br> [Bug] RINEX skeleton download following stream outage<br> [Add] Handle ephemeris from RTIGS streams<br> [Add] Monitor stream failure/recovery and latency<br> [Mod] Redesign of main window<br> [Bug] Freezing of About window on Mac systems<br> [Bug] Fixed problem with PRN 32 in RTCMv2 decoder<br> [Bug] Fix for Trimble 4000SSI receivers in RTCMv2 decoder<br> [Mod] Major revision of input buffer in RTCMv2 decoder</td></tr>
    936956<tr><td>Dec 2008 &nbsp;</td><td>Version 1.6 &nbsp;</td><td>[Mod] Fill blanc columns in RINEXv3 with 0.000<br> [Add] RTCMv3 decoder for clock and orbit corrections<br>[Add] Check RTCMv3 streams for incoming message types<br> [Add] Decode RTCMv2 message types 3, 20, 21, and 22<br> [Add] Loss of lock and lock time indicator<br> [Bug] Rounding error in RTCMv3 decoder concerning GLONASS height<br> [Mod] Accept GLONASS in RTCMv3 when transmitted first<br> [Add] Leap second 1 January 2009<br> [Add] Offline mode, read data from file<br> [Add] Output antenna descriptor, coordinates and excentricities from RTCMv3<br> [Add] Reconfiguration on-the-fly<br> [Mod] Binary ouput of synchronized observations<br> [Add] Binary output of unsynchronized observations<br> [Bug] Fixed problem with joined RTCMv3 blocks</td></tr>
    937 <tr><td>Jan 2009 &nbsp;</td><td>Version 1.7 &nbsp;</td><td>
    938 [Add] Full proxy support<br> [Mod] Ntrip source-table request<br> [Bug] RINEX navigation file format<br> [Add] Support of NTRIP v2<br> [Add] Rover support via serial port</td></tr>
     957<tr><td>Jan 2009 &nbsp;</td><td>Version 1.7 &nbsp;</td><td>[Mod] NTRIP v1 source-table request<br> [Bug] RINEX navigation file format<br> [Add] Support of NTRIP v2<br> [Add] Rover support via serial port</td></tr>
    939958</table>
    940959</p>
    … …  
    948967</p>
    949968
    950 <p><a name="ntrip"><h4>8.2.1 NTRIP</h4></p>
     969<p><a name="ntrip1"><h4>8.2.1 NTRIP Version 1</h4></p>
    951970
    952971<p>
    … …  
    9871006</p>
    9881007
    989 
    990 <p><a name="rtcm2"><h4>8.2.2 RTCM Version 2.x</h4></p>
     1008<p><a name="ntrip2"><h4>8.2.1 NTRIP Version 2</h4></p>
     1009
     1010<p>
     1011The major changes of NTRIP version 2.0 compared to Version 1.0 are:
     1012</p>
     1013
     1014<ul>
     1015<li>cleared and fixed design problems and HTTP protocol violations;</li>
     1016<li>replaced non standard directives;</li>
     1017<li>chunked transfer encoding;</li>
     1018<li>improvements in header records;</li>
     1019<li>sourcetable filtering; and</li>
     1020<li>RTSP communication.</li>
     1021</ul>
     1022
     1023<p>NTRIP version 2 allows to either communicate in TCP/IP mode or in RTSP/RTP mode. Note that RTSP/RTP support is not yet implemented in BNC.
     1024</p>
     1025
     1026<p><a name="rtcm2"><h4>8.2.3 RTCM Version 2.x</h4></p>
    9911027<p>
    9921028Transmitting GNSS carrier phase data can be done through RTCM Version 2.x messages. Please note that only RTCM Version 2.2 and 2.3 streams may include GLONASS data. Messages that may be of some interest here are:
    … …  
    10261062</ul>
    10271063
    1028 <p><a name="rtcm3"><h4>8.2.3 RTCM Version 3.x</h4></p>
     1064<p><a name="rtcm3"><h4>8.2.4 RTCM Version 3.x</h4></p>
    10291065<p>
    10301066RTCM Version 3.x has been developed as a more efficient alternative to RTCM Version 2.x. Service providers and vendors have asked for a standard that would be more efficient, easy to use, and more easily adaptable to new situations. The main complaint was that the Version 2 parity scheme was wasteful of bandwidth. Another complaint was that the parity is not independent from word to word. Still another was that even with so many bits devoted to parity, the actual integrity of the message was not as high as it should be. Plus, 30-bit words are awkward to handle. The Version 3.x standard is intended to correct these weaknesses.

  • trunk/BNC/bnctabledlg.cpp

    r1387 r1409  
    5252
    5353  setMinimumSize(600,400);
    54   setWindowTitle(tr("Add Mountpoints"));
     54  setWindowTitle(tr("Add Streams"));
    5555
    5656  QVBoxLayout* mainLayout = new QVBoxLayout(this);
    … …  
    106106  mainLayout->addLayout(editLayout);
    107107
     108  _ntripVersionComboBox->setWhatsThis(tr("<p>Select the NTRIP transport protocol version you want to use. Implemented options are:<br>&nbsp; 1:&nbsp; NTRIP version 1, TCP/IP<br>&nbsp; 2:&nbsp; NTRIP version 2, TCP/IP<br>Select option '1' if you not sure whether the NTRIP broadcaster supports NTRIP version 2.</p>"));
     109
    108110  _table = new QTableWidget(this);
    109   _table->setWhatsThis(tr("<p>Use the 'Get Table' button to download the sourcetable from the NTRIP broadcaster. Select the desired streams line by line, using +Shift and +Ctrl when necessary. Hit 'OK' to return to the main window.</p><p>Pay attention to data fields 'format' and 'format-details'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. RTCM Version 2.x streams must contain message Type 18 and 19 or 20 and 21 while RTCM Version 3.x streams must contain GPS or SBAS message Type 1002 or 1004 and may contain GLONASS message types 1010 or 1012. See data field 'format-details' for available message types and their repetition rates in brackets.</p><p>Note that in order to produce RINEX Navigation files, RTCM Version 3.x streams containing message Type 1019 (GPS) and 1020 (GLONASS) or RTIGS streams are required.</p><p>Search for RTCM Version 3.x streams containing (premature) message Types 4056 and 4057 if you need corrections to Broadcast Ephemeris.</p><p>The content of data field 'nmea' tells you whether a stream retrieval needs to be initiated by BNC by sending an NMEA-GGA message containing the user (or virtual reference station)'s coordinate.</p>"));
     111  _table->setWhatsThis(tr("<p>Use the 'Get Table' button to download the sourcetable from the NTRIP broadcaster. Select the desired streams line by line, using +Shift and +Ctrl when necessary. Hit 'OK' to return to the main window.</p><p>Pay attention to data field 'format'. Keep in mind that BNC can only decode and convert streams that come in RTCM Version 2.x, RTCM Version 3.x, or RTIGS format. See data field 'format-details' for available message types and their repetition rates in brackets.</p><p>The content of data field 'nmea' tells you whether a stream comes from a virtual reference station (VRS).</p>"));
    110112  connect(_table, SIGNAL(itemSelectionChanged()),
    111113          this, SLOT(slotSelectionChanged()));

  • trunk/BNC/bncwindow.cpp

    r1405 r1409  
    6060  int ww = QFontMetrics(this->font()).width('w');
    6161 
    62   static const QStringList labels = QString("account,broadcaster:port / mountpoint,decoder,lat,long,nmea,ntrip,bytes").split(",");
     62  static const QStringList labels = QString("account, Streams:     broadcaster:port/mountpoint,decoder,lat,long,nmea,ntrip,bytes").split(",");
    6363
    6464  setMinimumSize(80*ww, 65*ww);
    … …  
    8989  connect(_actQuit, SIGNAL(triggered()), SLOT(close()));
    9090
    91   _actAddMountPoints = new QAction(tr("Add &Mountpoints"),this);
     91  _actAddMountPoints = new QAction(tr("Add &Streams"),this);
    9292  connect(_actAddMountPoints, SIGNAL(triggered()), SLOT(slotAddMountPoints()));
    9393
    94   _actDeleteMountPoints = new QAction(tr("&Delete Mountpoints"),this);
     94  _actDeleteMountPoints = new QAction(tr("&Delete Streams"),this);
    9595  connect(_actDeleteMountPoints, SIGNAL(triggered()), SLOT(slotDeleteMountPoints()));
    9696  _actDeleteMountPoints->setEnabled(false);
    … …  
    114114  _proxyPortLineEdit->setMaximumWidth(9*ww);
    115115  _miscMountLineEdit  = new QLineEdit(settings.value("miscMount").toString());
    116   _miscMountLineEdit->setMaximumWidth(20*ww);
    117116  _scanRTCMCheckBox  = new QCheckBox();
    118117  _scanRTCMCheckBox->setCheckState(Qt::CheckState(
    … …  
    330329  _adviseFailSpinBox->setWhatsThis(tr("<p>An advisory note is generated when no (or only corrupted) observations are seen throughout the 'Failure threshold' time span. A value of 15 min (default) is recommended.</p><p>A value of zero '0' means that for any stream failure, however short, BNC immediately generates an advisory note.</p><p>Note that for using this function you need to specify the 'Observation rate'.</p>"));
    331330  _makePauseCheckBox->setWhatsThis(tr("<p>In case of a continuously corrupted stream, the decoding process can be paused and decodings are then attempted again at decreasing rate till the stream hopefully recovers. Tick 'Pause' to activate this function.</p><p>Do not tick 'Pause' (default) in order to prevent BNC from making any decoding pause. Be aware that this may incur an unnecessary workload.</p><p>Note that this function is only effective if an 'Observation rate' is specified.</p>"));
    332   _logFileLineEdit->setWhatsThis(tr("Records of BNC's activities are shown in the Log section on the bottom of this window. They can be saved into a file when a valid path is specified in the 'Logfile (full path)' field."));
     331  _logFileLineEdit->setWhatsThis(tr("Records of BNC's activities are shown in the 'Logs' section on the bottom of this window. They can be saved into a file when a valid path is specified in the 'Logfile (full path)' field."));
    333332  _adviseScriptLineEdit->setWhatsThis(tr("<p>Specify the full path to a script or batch file to handle advisory notes generated in the event of corrupted streams or stream outages. The affected mountpoint and one of the comments 'Begin_Outage', 'End_Outage', 'Begin_Corrupted', or 'End_Corrupted' are passed on to the script as command line parameters.</p><p>The script can be configured to send an email to BNC's operator and/or to the affected stream provider. An empty option field (default) or invalid path means that you don't want to use this option.</p><p> Note that for using this function you need to specify the 'Observation rate'.</p>"));
    334   _perfIntrComboBox->setWhatsThis(tr("<p>BNC can average latencies per stream over a certain period of GPS time. The resulting mean latencies are recorded in the Log file/section at the end of each 'Log latency' interval together with results of a statistical evaluation (approximate number of covered epochs, data gaps).</p><p>Select a 'Log latency' interval or select the empty option field if you do not want BNC to log latencies and statistical information.</p>"));
    335   _mountPointsTable->setWhatsThis(tr("<p>Streams selected for retrieval are listed in the 'Mountpoints' section. Clicking on 'Add Mountpoints' button will open a window that allows the user to select data streams from an NTRIP broadcaster according to their mountpoints. To remove a stream from the 'Mountpoints' list, highlight it by clicking on it and hit the 'Delete Mountpoints' button. You can also remove multiple mountpoints by highlighting them using +Shift and +Ctrl.</p><p>BNC automatically allocates one of its internal decoders to a stream based on the stream's 'format' and 'format-details' as given in the sourcetable. However, there might be cases where you need to override the automatic selection due to incorrect sourcetable for example. BNC allows users to manually select the required decoder by editing the decoder string. Double click on the 'decoder' field, enter your preferred decoder and then hit Enter. The accepted decoder strings are 'RTCM_2.x', 'RTCM_3.x', and 'RTIGS'.</p><p>In case you need to log the raw data as is, BNC allows users to by-pass its decoders and and directly save the input in daily log files. To do this specify the decoder string as 'ZERO'.</p><p>BNC can also retrieve streams from virtual reference stations (VRS). To initiate these streams, an approximate rover position needs to be sent in NMEA GGA message to the NTRIP broadcaster. In return, a user-specific data stream is generated, typically by a Network-RTK software. This stream is customized to the exact latitude and longitude as shown in the 'lat' and 'long' columns under 'Mountpoints'. These VRS streams are indicated by a 'yes' in the 'nmea' column under 'Mountpoints' as well as in the sourcetable. The default 'lat' and 'long' values are taken from the sourcetable. However, in most cases you would probably want to change this according to your requirement. Double click on 'lat' and 'long' fields, enter the values you wish to send and then hit Enter. The format is in positive north latitude degrees (e.g. for northern hemisphere: 52.436, for southern hemisphere: -24.567) and eastern longitude degrees (e.g.: 358.872 or -1.128). Only mountpoints with a 'yes' in its 'nmea' column can be edited. The position should preferably be a point within the coverage of the network.</p>"));
    336   _log->setWhatsThis(tr("Records of BNC's activities are shown in the Log section. The message log covers the communication status between BNC and the NTRIP broadcaster as well as any problems that occur in the communication link, stream availability, stream delay, stream conversion etc."));
     333  _perfIntrComboBox->setWhatsThis(tr("<p>BNC can average latencies per stream over a certain period of GPS time. The resulting mean latencies are recorded in the 'Logs' section at the end of each 'Log latency' interval together with results of a statistical evaluation (approximate number of covered epochs, data gaps).</p><p>Select a 'Log latency' interval or select the empty option field if you do not want BNC to log latencies and statistical information.</p>"));
     334  _mountPointsTable->setWhatsThis(tr("<p>Streams selected for retrieval are listed in the 'Streams' section. Clicking on 'Add Streams' button will open a window that allows the user to select data streams from an NTRIP broadcaster according to their mountpoints. To remove a stream from the 'Streams' list, highlight it by clicking on it and hit the 'Delete Streams' button. You can also remove multiple streams by highlighting them using +Shift and +Ctrl.</p><p>BNC automatically allocates one of its internal decoders to a stream based on the stream's 'format' as given in the sourcetable. BNC allows users to change this selection by editing the decoder string. Double click on the 'decoder' field, enter your preferred decoder and then hit Enter. The accepted decoder strings are 'RTCM_2.x', 'RTCM_3.x', and 'RTIGS'.</p><p>In case you need to log the raw data as is, BNC allows users to by-pass its decoders and and directly save the input in daily log files. To do this specify the decoder string as 'ZERO'.</p><p>BNC can also retrieve streams from virtual reference stations (VRS). VRS streams are indicated by a 'yes' in the 'nmea' column. To initiate these streams, the approximate latitude/longitude rover position is sent to the NTRIP broadcaster. The default values can be change according to your requirement. Double click on 'lat' and 'long' fields, enter the values you wish to send and then hit Enter.</p>"));
     335  _log->setWhatsThis(tr("Records of BNC's activities are shown in the 'Logs' section. The message log covers the communication status between BNC and the NTRIP broadcaster as well as any problems that occur in the communication link, stream availability, stream delay, stream conversion etc."));
    337336  _ephV3CheckBox->setWhatsThis(tr("The default format for RINEX Navigation files containing Broadcast Ephemeris is RINEX Version 2.11. Select 'Version 3' if you want to save the ephemeris in RINEX Version 3 format."));
    338337  _rnxV3CheckBox->setWhatsThis(tr("The default format for RINEX Observation files is RINEX Version 2.11. Select 'Version 3' if you want to save the observations in RINEX Version 3 format."));
    … …  
    352351  setCentralWidget(_canvas);
    353352
    354   QTabWidget* aogroup = new QTabWidget();
     353//QTabWidget* aogroup = new QTabWidget();
     354  aogroup = new QTabWidget();
    355355  QWidget* pgroup = new QWidget();
    356356  QWidget* ggroup = new QWidget();
    … …  
    373373
    374374  QGridLayout* pLayout = new QGridLayout;
    375   pLayout->setColumnMinimumWidth(0,14*ww);
    376   pLayout->addWidget(new QLabel("Proxy host"),0,0, Qt::AlignLeft);
    377   pLayout->addWidget(_proxyHostLineEdit,0, 1);
    378   pLayout->addWidget(new QLabel("Proxy port"),1,0, Qt::AlignLeft);
    379   pLayout->addWidget(_proxyPortLineEdit,1,1);
    380   pLayout->addWidget(new QLabel("Settings for the proxy in protected networks, leave the boxes blank if none."),2, 0, 1, 2, Qt::AlignLeft);
     375  pLayout->setColumnMinimumWidth(0,13*ww);
     376  pLayout->addWidget(new QLabel("Proxy host"),                   0, 0);
     377  pLayout->addWidget(_proxyHostLineEdit,                         0, 1, 1,10);
     378  pLayout->addWidget(new QLabel("Proxy port"),                   1, 0);
     379  pLayout->addWidget(_proxyPortLineEdit,                         1, 1);
     380  pLayout->addWidget(new QLabel("Settings for the proxy in protected networks, leave boxes blank if none."),2, 0, 1, 50, Qt::AlignLeft);
    381381  pLayout->addWidget(new QLabel("    "),3,0);
    382382  pLayout->addWidget(new QLabel("    "),4,0);
    … …  
    445445  QGridLayout* rLayout = new QGridLayout;
    446446  rLayout->setColumnMinimumWidth(0,14*ww);
    447   rLayout->addWidget(new QLabel("Mountpoint"),                    0, 0, Qt::AlignLeft);
    448   rLayout->addWidget(_miscMountLineEdit,                          0, 1,1,15,Qt::AlignLeft);
     447  rLayout->addWidget(new QLabel("Mountpoint"),                    0, 0);
     448  rLayout->addWidget(_miscMountLineEdit,                          0, 1, 1,7);
    449449  rLayout->addWidget(new QLabel("Log latency"),                   1, 0);
    450450  rLayout->addWidget(_perfIntrComboBox,                           1, 1);
    451451  rLayout->addWidget(new QLabel("Scan RTCM"),                     2, 0);
    452452  rLayout->addWidget(_scanRTCMCheckBox,                           2, 1);
    453   rLayout->addWidget(new QLabel("Log latencies or scan RTCM streams for numbers of message types and antenna information."),3, 0, 1, 4, Qt::AlignLeft);
     453  rLayout->addWidget(new QLabel("Log latencies or scan RTCM streams for numbers of message types and antenna information."),3, 0,1,30);
    454454  rLayout->addWidget(new QLabel("    "),                          4, 0);
    455455  rLayout->addWidget(new QLabel("    "),                          5, 0);
    … …  
    508508  sergroup->setLayout(serLayout);
    509509
    510   QVBoxLayout* mLayout = new QVBoxLayout;
    511   mLayout->addWidget(aogroup);
    512   mLayout->addWidget(_mountPointsTable);
    513   mLayout->addWidget(_log);
     510//QVBoxLayout* mLayout = new QVBoxLayout;
     511//mLayout->addWidget(aogroup);
     512//mLayout->addWidget(_mountPointsTable);
     513//mLayout->addWidget(_log);
     514  QGridLayout* mLayout = new QGridLayout;
     515  aogroup->setCurrentIndex(settings.value("startTab").toInt());
     516  mLayout->addWidget(aogroup,             0,0);
     517  mLayout->addWidget(_mountPointsTable,   1,0);
     518  mLayout->addWidget(new QLabel(" Logs:"),2,0);
     519  mLayout->addWidget(_log,                3,0);
    514520
    515521  _canvas->setLayout(mLayout);
    … …  
    759765  settings.setValue("miscMount",   _miscMountLineEdit->text());
    760766  settings.setValue("scanRTCM",    _scanRTCMCheckBox->checkState());
    761   settings.setValue("serialPortName", _serialPortNameLineEdit->text());
    762   settings.setValue("serialMountPoint", _serialMountPointLineEdit->text());
    763   settings.setValue("serialBaudRate", _serialBaudRateComboBox->currentText());
    764   settings.setValue("serialParity",   _serialParityComboBox->currentText());
    765   settings.setValue("serialDataBits", _serialDataBitsComboBox->currentText());
    766   settings.setValue("serialStopBits", _serialStopBitsComboBox->currentText());
    767   settings.setValue("serialAutoNMEA", _serialAutoNMEACheckBox->checkState());
     767  settings.setValue("serialPortName",  _serialPortNameLineEdit->text());
     768  settings.setValue("serialMountPoint",_serialMountPointLineEdit->text());
     769  settings.setValue("serialBaudRate",  _serialBaudRateComboBox->currentText());
     770  settings.setValue("serialParity",    _serialParityComboBox->currentText());
     771  settings.setValue("serialDataBits",  _serialDataBitsComboBox->currentText());
     772  settings.setValue("serialStopBits",  _serialStopBitsComboBox->currentText());
     773  settings.setValue("serialAutoNMEA",  _serialAutoNMEACheckBox->checkState());
     774  settings.setValue("startTab",    aogroup->currentIndex());
    768775 
    769776  QStringList mountPoints;
Note: See TracChangeset for help on using the changeset viewer.