P2P Correction Thread – 2018-09-22

World Wide Flora & Fauna in Amateur Radio Forums WWFF HelpDesk Log Corrections P2P Correction Thread – 2018-09-22

Viewing 15 posts - 31 through 45 (of 65 total)
  • Author
    Posts
  • #12201
    Ivan LZ2HT
    Participant

    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-0584

    #12290
    HB9TZA
    Participant

    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? Thanks

    #12291
    Ivan LZ2HT
    Participant

    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 log

    #12292
    HB9TZA
    Participant

    Thank you, 73 44 Augusto

    #12293
    Luk ON4BB
    Participant

    Augusto,

    yes is it deleted from the DLFF list starting from 31-03-2022.
    So, wipe the cross ref out of the log.

    #12296
    HB9TZA
    Participant

    Done. Tnx!

    #12552
    Enno (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, PF5X

    #12616
    Ivan LZ2HT
    Participant

    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)

    #12691
    Ivan LZ2HT
    Participant

    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-0584

    #12797
    (G0BON)
    Participant

    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 correct

    #12798
    (G0BON)
    Participant

    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 correct

    #12799
    (G0BON)
    Participant

    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 correct

    #13058
    Mal
    Participant

    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.

    #13061
    Luk ON4BB
    Participant

    Hi Mal,
    sri to tell you but there is NO log uploaded used VK3MEL as activator in our system for date 26 11 2022.

    #13064
    Mal
    Participant

    Thanks Luk.
    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?

    Thanks

Viewing 15 posts - 31 through 45 (of 65 total)
  • You must be logged in to reply to this topic.
Translate »