[OhQP-mail] OHQP LOGGING BEST PRACTICES
k9tm at buckeye-express.com
Mon Aug 17 12:22:59 CDT 2020
>From a log checking perspective, just log the callsign (k8mr or k8xx in
the below examples).
The log checking does not need to know /m, /r, /county-abbr from the
The log checking software gets the QTH from the QTH part of the exchange
(both sent and received).
Some logging software is brain dead with respect to duping and does not
look at QTH must match for dupe and that's why some people enter
call/county-abbr... to make their logging software happy for duping.
73, Tim K9TM
On 2020-08-17 12:29, Bob wrote:
> What are your recommended best practice for logging qso's with /m and /r stations?
> What saves the most time for the mrrc team when reviewing/editing logs?
> Hypotheical Examples:
> * Could a qso with k8mr/m be logged k8mr/m or k8mr/Athe?
> * Could a qso with k8xx/r be logged K8xx/r or k8xx/lake?
> Ive done all those at different times over the years.
> Or doesn't it matter?
> FWIW I use N1MM+ for logging purposes and during test entries, they all seem to work.
> The all-wire antenna farm in Licking County
> PS Bank cndx seem to be much improved the past couple of weeks for both dx and domestic sigs. Hope NVIS on 40m comes back this year and lets us hear most OH counties again, like it did a few years ago.
> Have a safe trip to all who will be out and about.
> Sent from Mail  for Windows 10
> OhQP-mail mailing list
> OhQP-mail at ohqp.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OhQP-mail