March 22, 2022 at 07:56 #12201
Error: reference (LZFF-0574 v LZFF-0584) for DH5ST/P working LZ2HT
… QSO #17052052 (2022-05-05 15:05:00) DH5ST/P on 20m/CW(CW) @ DLFF-0124 claiming LZFF-0574
Reference should be LZFF-0584April 26, 2022 at 12:16 #12290
Another DLFF invalid/Not yet valid Reference as in the past:
[ERROR] 20220412:092800 on 40M/CW between HB9BCK/P (HB9BCK) @ HBFF-0139 and DL6MST/P @ DLFF-0063
——> Invalid date 20220412 for reference DLFF-0063;
End of File… 98 of 99 QSOs valid
… please correct logfile then resubmit.
[ERROR] Logfile NOT uploaded
Should I delete the P2P Ref and reload? ThanksApril 26, 2022 at 13:02 #12291
WWFF Directory says that DLFF-0063 was walid until 31st March 2022 so it won’t be valid activation for DL6MST too. I think you should remove his reference from the logApril 26, 2022 at 13:27 #12292
Thank you, 73 44 AugustoApril 26, 2022 at 14:26 #12293Luk ON4BBParticipant
yes is it deleted from the DLFF list starting from 31-03-2022.
So, wipe the cross ref out of the log.April 27, 2022 at 11:51 #12296
Done. Tnx!August 8, 2022 at 19:58 #12552Enno (PF5X)Participant
Typo in DL6AP/P, 2022-08-03, DLFF-0178, log.
He claims P2P QSO with with DL/PF5X/P as being in DLFF-0657. This must be DLFF-0567. Seems like a typo.
Please correct …
Enno, PF5XAugust 29, 2022 at 11:40 #12616
Error: mode (Data(PKT) v Phone(SSB)) mismatch for DL4EAM working LZ2HT/P
… QSO #17695654
(2022-05-29 10:28:00) DL4EAM @ DLFF-0110 claiming mode Data(PKT).
Mode must be Phone(SSB)September 15, 2022 at 07:36 #12691
Error: reference (LZFF-0590 v LZFF-0584) mismatch for OM1AEG/P working LZ2HT
… QSO #17534850 (2022-03-26 16:23:00) OM1AEG/P on 40m/PH(SSB) @ OMFF-1047 claiming LZFF-0580
Correct reference is LZFF-0584October 13, 2022 at 10:58 #12797
SIG_INFO and MY_SIG_INFO missing for P2P for G0BON/P working DK3RV
… log #00132358 (2012-10-11 15:23:00) G0BON/P on 40m/Phone(SSB) @ GFF-0232 working DK3RV claiming DLFF-0110
Missing worked WWFF Reference DLFF-0110, please correctOctober 13, 2022 at 11:00 #12798
SIG_INFO and MY_SIG_INFO missing for P2P for G0BON/P working DK0NL
… log #00132358 (2012-10-11 15:23:00) G0BON/P on 40m/Phone(SSB) @ GFF-0232 working DK0NL claiming DLFF-0110
Missing worked WWFF Reference DLFF-0110, please correctOctober 13, 2022 at 11:01 #12799
SIG_INFO and MY_SIG_INFO missing for P2P for G0BON/P working DL1ASF
… log #00132358 (2012-10-11 15:30:00) G0BON/P on 40m/Phone(SSB) @ GFF-0232 working DL1ASF claiming DLFF-0127
Missing worked WWFF Reference DLFF-0127, please correctDecember 31, 2022 at 20:56 #13058MalParticipant
I’d like to request a correction to a P2P log I submitted for the 26th of November 2022. I’ve read the instrctions at the start of this thread, but I can’t work out where to get the required detail with the QSO number from.
Is it something I should be able to see in LogSearch, or do I need to contact my local co-ordinator?
Thanks for your help.January 1, 2023 at 16:50 #13061Luk ON4BBParticipant
sri to tell you but there is NO log uploaded used VK3MEL as activator in our system for date 26 11 2022.January 2, 2023 at 02:23 #13064MalParticipant
The call I used on the 26-11-2022 was VK3OAK. I was in VKFF-2048 and logged a contact with VK4FDJL and logged him in VKFF-0933 in error.
I should have logged the contact with VK4FDJL as being in park VKFF-1611.
May I request that my log be changed to show VK4FDJL as being in park VKFF-1611?
- You must be logged in to reply to this topic.