Forum Replies Created
-
Posts
-
It was a 2 day activation (14th and 15th).
For Log entries with date of Oct 4th (20201004), the correct date is 14th (20201014).
For 8 Log entries with date of Oct 5th (20201005), the correct date is Oct 15th (20201015).
Since it involved 2 dates, I thought it might be easier for you if we re-upload a new file. However, it sounds as thought you can make the changes this way.
Thank you.
73,
Steve, N1TYHI should have noted that the log file for WA5KBH is “WA5KBH@KFF-2366 20191008.adi” (he was at KFF-2366).
73 & 44,
Steve, N1TYHHi Manfred,
The log for KFF-3671 with 20 contacts is correct. It was for year 2019 as uploaded.
Thanks for helping Terry.
73 & 44,
Steve, N1TYHManfred,
WB3GCK was not at a WWFF-KFF park in 2017 for the contact with KM1CC.
No changes required for the 2017 QSO.
Thanks for the support.
73,
Steve, N1TYHHi Manfred,
For 20180421, The KM1CC log did not have the P2P fields listed. So, I’m surprised that there was a Park-to-Park match. Is the system automatically detecting P2P matches now? Do we need to add the SIG & SIG_INFO fields?
I was not loading logs for WB3GCK in 2017, so I do not have a copy of the log. I can e-mail the operator.
73,
Steve, N1TYHHi Manfred,
I responded via e-mail as well, but will do so here too in case you check this first.
Yes the other dates for KFF-3054 are okay. We only made the mistake for QSOs on Jan 19th and Jan 20th (which should be KFF-3059).
73,
Steve, N1TYHHello Nobi,
I sent an e-mail to Andrew asking if this is how we should do it moving forward. We have actually suggested this in the past and were told to upload corrections to the Helpdesk forum here. It would be much quicker for me to upload a file. So, we’ll wait to see what Andrew says.
73 & 44,
Steve, N1TYH
