Skip to content

Commit a7fbd62

Browse files
committed
@mbridak Add remarks on call history
1 parent 708406c commit a7fbd62

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

README.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -102,6 +102,7 @@
102102
- [If no exchange entered send AGN](#if-no-exchange-entered-send-agn)
103103
- [With exchange entered, send your exchange and log it](#with-exchange-entered-send-your-exchange-and-log-it)
104104
- [Call History Files](#call-history-files)
105+
- [Creating your own Call History files](#creating-your-own-call-history-files)
105106
- [Contest specific notes](#contest-specific-notes)
106107
- [ARRL Sweekstakes](#arrl-sweekstakes)
107108
- [The exchange parser](#the-exchange-parser)
@@ -889,13 +890,16 @@ QRZ (for Run) or Exchange (for S&P) is sent.
889890

890891
## Call History Files
891892

892-
I've started work on using 'call history files'. To test it, you can
893-
go to `FILE -> Configuration Settings`
893+
To use Call History files, go to `FILE -> Configuration Settings`
894894

895895
![Config Screen](https://github.com/mbridak/not1mm/raw/master/pic/configuration_options.png)
896896

897897
Place a check in the `Use Call History` box. Call history files are very specific to the contest you are working. Example files can be obtained from [n1mm's](https://n1mmwp.hamdocs.com/mmfiles/categories/callhistory/?) website. They have a searchbox so you can find the contest you are looking for. If you are feeling masocistic, you can craft your own. The general makeup of the file is a header defining the fields to be used, followed by by lines of comma separated data.
898898

899+
### Creating your own Call History files
900+
901+
You can use [adif2callhistory](https://github.com/mbridak/adif2callhistory) to generate your own call history file from your ADIF files. You can use a list of call history keys used for each contest [here](https://github.com/mbridak/not1mm/blob/master/call_history_keys.md).
902+
899903
An example file excerpt looks like:
900904

901905
```text

0 commit comments

Comments
 (0)