|
|
|
### **Is GridTracker a "Logging Program"?**
|
|
|
|
|
|
|
|
No it is not. It does keep a log in the form of an .adif file _if you choose to send QSO information to it_ but GridTracker is primarily designed to **_display_** QSO/QSL information, **not to create a permanent database** of your radio contacts. See the [GridTracker Data Files](https://docs.google.com/document/d/1ZYOQZ060W4E2uim1y_dX4xfV0kA_WujFKEKsYiGMUOk/edit#heading=h.6dsn396y4vc7) section of this manual for where the GridTracker .adif file is stored. _(Hint: in the cloud.)_
|
|
|
|
No it is not. It does keep a log in the form of an .adif file _if you choose to send QSO information to it_ but GridTracker is primarily designed to **_display_** QSO/QSL information, **not to create a permanent database** of your radio contacts. See the [GridTracker Data Files](GridTracker-File-Storage#gridtracker-data-files) section of this manual for where the GridTracker .adif file is stored.
|
|
|
|
|
|
|
|
### **QSO/Logging Records Stored by GridTracker**
|
|
|
|
|
|
|
|
### ****
|
|
|
|
|
|
|
|
|
|
|
|
The first row in the table presented in the **Settings > Logging** menu provides the limited control options for GridTracker's internal logging functions. It allows you to do _two and only two_ things:
|
|
|
|
|
|
|
|
1. Automatically load whatever content the GridTracker_QSO.adif file contains when you start up GridTracker. This file is saved in the cloud (at least for Windows 10). _See_ [_the GridTracker Data Files_](https://docs.google.com/document/d/1ZYOQZ060W4E2uim1y_dX4xfV0kA_WujFKEKsYiGMUOk/edit#heading=h.6dsn396y4vc7) _section at the end of this manual for more information on that._
|
|
|
|
1. Automatically load whatever content the GridTracker_QSO.adif file contains when you start up GridTracker. This file is saved in the cloud (at least for Windows 10). _See_ [_the GridTracker Data Files_](GridTracker-File-Storage#gridtracker-data-files) _section._
|
|
|
|
2. Add data from any new QSOs made with WSJT-X to the GridTracker_QSO.adif file.
|
|
|
|
|
|
|
|
Remember: GridTracker will always automatically import your WSJT-X_log.adi file every time you start up. So why would you want or need to open and import your GridTracker_QSO.adif file at start-up if GridTracker is always going to go out and grab the data in the WSJT-X_log.adi file? Possibly because:
|
|
|
|
Remember: GridTracker will always automatically import your WSJT-X_log.adi file every time you start up. So why would you want or need to open and import your GridTracker_QSO.adif file at start-up if GridTracker is always going to go out and grab the data in the WSJT-X_log.adi file? Possibly because:
|
|
|
|
|
|
|
|
a) You want to import QSO records for digital contacts you've made on apps _other than_ WSJT-X; or perhaps contacts made with phone or CW that you have manually added to the GridTracker_QSO.adif file, and/or
|
|
|
|
|
| ... | ... | @@ -23,12 +23,13 @@ Before getting into GridTracker's options for importing QSO data we'll address h |
|
|
|
|
|
|
|
### **Sending Logging Information OUT from GridTracker**
|
|
|
|
|
|
|
|
GridTracker can and will import and export QSO logging data from external applications and websites if you choose. The options to export data are slightly simpler than those to import data so we'll address those first. \
|
|
|
|
|
|
|
|
GridTracker can and will import and export QSO logging data from external applications and websites if you choose. The options to export data are slightly simpler than those to import data so we'll address those first.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TheGridTracker will send the QSO information it detects from WSJT-X out to a number of different, dedicated logging programs if you choose to do so. Here's what the **Settings > Logging** menu looks like with NO options selected:
|
|
|
|
|
|
|
|
You have the option to send QSO or logging information to a GridTracker log but also to QRZ.com, LotW, and 10 other outside programs or websites. You have to enter password or IP address information to do that but once you set it up you can forget it.
|
|
|
|
You have the option to send QSO or logging information to a GridTracker log but also to QRZ.com, LotW, and 10 other outside programs or websites. You have to enter password or IP address information to do that but once you set it up you can mostly forget it.
|
|
|
|
|
|
|
|
### **Importing Logging Information INTO GridTracker**
|
|
|
|
|
| ... | ... | @@ -36,48 +37,49 @@ Managing QSO log imports into GridTracker is a slightly more complicated than ex |
|
|
|
|
|
|
|
#### **_Importing Log Data at Startup_**
|
|
|
|
|
|
|
|
\
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The options to import Local Files, PSK-Reporter info, QRZ, ClubLog and/or LoTW data to the main GridTracker control panel are in the **Settings > Logging** menu at the far left side of that table.
|
|
|
|
|
|
|
|
Simply click on one or more of those buttons in the **Startup?** column to add that data.
|
|
|
|
|
|
|
|
**● Local Files:** a "Local" file is one that is stored on your computer or network as opposed to a data file that is retrieved from a **web** site. In order to add a local file you simply click on the "Add" button and enter the path and file name. Note: in a Windows system when you click the "Add File" button a Windows File Explorer window automatically opens which allows you to easily search for an existing file. In the example below the user is instructing GridTracker to import a local file named "FieldDay2021.adi" at start up.
|
|
|
|
##### **Local Files:**
|
|
|
|
A "Local" file is one that is stored on your computer or network as opposed to a data file that is retrieved from a **web** site. In order to add a local file you simply click on the "Add" button and enter the path and file name. Note: in a Windows system when you click the "Add File" button a Windows File Explorer window automatically opens which allows you to easily search for an existing file. In the example below the user is instructing GridTracker to import a local file named "FieldDay2021.adi" at start up.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* **Web Site Data:** If you choose to import data from the QRZ, ClubLog, or LoTW websites you will have to provide the necessary log in data for the site: login name or callsign, passwords, etc.
|
|
|
|
##### **Web Site Data:**
|
|
|
|
If you choose to import data from the QRZ, ClubLog, or LoTW websites you will have to provide the necessary log in data for the site: login name or callsign, passwords, etc.
|
|
|
|
|
|
|
|
GridTracker will retrieve QSO data from the site, create a **temporary** .adif file for it, and save that file in the same place where your GridTracker_QSO.adif file is saved. In a Windows 10 system that will be on One Drive, a cloud service. Once you close the GridTracker app that temporary file will be deleted from the cloud.
|
|
|
|
GridTracker will retrieve QSO data from the site, create a **temporary** .adif file for it, and save that file in the same place where your GridTracker_QSO.adif file is saved. Once you close the GridTracker app that temporary file will be deleted from the cloud.
|
|
|
|
|
|
|
|
#### **_Importing Logs on the Fly / At Will_**
|
|
|
|
|
|
|
|
You use essentially the same process as that for importing logs on the fly to, instead, import log data when you start up GridTracker. The only change is clicking buttons in the **Startup?** column to make your choices.
|
|
|
|
You use essentially the same process as that for importing logs on the fly to, instead, import log data when you start up GridTracker. The only change is clicking the check-boxes in the **Startup?** column to make your choices.
|
|
|
|
|
|
|
|
You can then use some or all of those buttons to import "external" data into GridTracker on the fly.
|
|
|
|
|
|
|
|
Earlier in this manual we discussed the option to add buttons for importing [Local](https://docs.google.com/document/d/1ZYOQZ060W4E2uim1y_dX4xfV0kA_WujFKEKsYiGMUOk/edit#heading=h.uviivc58aoc6), [QRZ.com](https://docs.google.com/document/d/1ZYOQZ060W4E2uim1y_dX4xfV0kA_WujFKEKsYiGMUOk/edit#heading=h.ctdhdxm0czpd), [ClubLog](https://docs.google.com/document/d/1ZYOQZ060W4E2uim1y_dX4xfV0kA_WujFKEKsYiGMUOk/edit#heading=h.a1z2zayhjl02) and [LoTW](https://docs.google.com/document/d/1ZYOQZ060W4E2uim1y_dX4xfV0kA_WujFKEKsYiGMUOk/edit#heading=h.mcvsq715han2) data to the main GridTracker Control Panel. (The button to [Load ADIF](https://docs.google.com/document/d/1ZYOQZ060W4E2uim1y_dX4xfV0kA_WujFKEKsYiGMUOk/edit#heading=h.mftwyl3xjw64) file is part of the GridTracker Control Panel by default.)
|
|
|
|
Earlier in this manual we discussed the option to add buttons for importing [Local](GridTracker-Overview/Control-Panel#load-local-log), [QRZ.com](GridTracker-Overview/Control-Panel#download-qrz-log), [ClubLog](GridTracker-Overview/Control-Panel#download-clublog) and [LoTW](GridTracker-Overview/Control-Panel#download-lotw-log) data to the main GridTracker Control Panel. (The button to [Load ADIF](GridTracker-Overview/Control-Panel#load-adif-log-hotkey-l) file is part of the GridTracker Control Panel by default.)
|
|
|
|
|
|
|
|
You can then use some or all of those buttons to import "external" data into GridTracker if and whenever you choose, on the fly.
|
|
|
|
|
|
|
|
**Note:** Again, if you choose to import data from QRZ, ClubLog, or LoTW websites GridTracker will retrieve QSO data from the site, create a **temporary** .adif file for it, and save that file in the same place where your GridTracker_QSO.adif file is saved. In a Windows 10 system that will be on One Drive, a cloud service. Once you close the GridTracker app that temporary file will be deleted from the cloud.
|
|
|
|
**Note:** Again, if you choose to import data from QRZ, ClubLog, or LoTW websites GridTracker will retrieve QSO data from the site, create a **temporary** .adif file for it, and save that file in the same place where your GridTracker_QSO.adif file is saved.
|
|
|
|
|
|
|
|
**Note:** The GridTracker Control Panel buttons to Load ADIF and Log Local do two different things.
|
|
|
|
|
|
|
|
 The Load ADIF button loads your local GridTracker_QSO.adif\
|
|
|
|
 The Load Local Log button loads whatever local file(s) you've identified in **Settings** **> Logging**
|
|
|
|
 The Load ADIF button loads your local GridTracker_QSO.adif
|
|
|
|
|
|
|
|
!["Load Local Logs button"]("/img/GT_LoadLocal.png) The Load Local Log button loads whatever local file(s) you've identified in **Settings** **> Logging**
|
|
|
|
|
|
|
|
### **Using the "Clear Log" and "Load Logs" Buttons**
|
|
|
|
|
|
|
|
Having discussed importing and exporting log data it's worth reviewing what happens when you use the **Clear Log** and **Load Logs** buttons in the **QSO Status** section of the main GridTracker Control Panel
|
|
|
|
|
|
|
|
If you clear log data by clicking on the **Clear Log** button in the QSO Data section of the Control Panel GridTracker:\
|
|
|
|
|
|
|
|
If you clear log data by clicking on the **Clear Log** button in the QSO Data section of the Control Panel GridTracker:
|
|
|
|
|
|
|
|
Ta Da!: the QSO Data
|
|
|
|
Ta Da!: the QSO Data record now looks like this:
|
|
|
|
|
|
|
|
record now looks like this:
|
|
|
|
|
|
|
|
|
|
|
|
#### **_Clicking the "Clear Log" Button_**
|
|
|
|
|
| ... | ... | |
