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 - 16 through 30 (of 36 total)
  • Author
    Posts
  • #9787
    on4ro
    Participant

    Error: band (20m v ?) mismatch for DK7DE working ON4RO/P
    … QSO (2017-08-09 08:58) ON4RO/P on 40m/Phone(SSB) @ ONFF-0589

    Band should be 20m

    • This reply was modified 1 year, 2 months ago by on4ro. Reason: sri must be 20m band
    #9789
    on4ro
    Participant

    Error: band (20m v ?) mismatch for DL1ASF working ON4RO/P
    … QSO (2017-08-09 09:01) ON4RO/P on 20m/Phone(SSB) @ ONFF-0589

    Band should be 20m

    • This reply was modified 1 year, 2 months ago by on4ro. Reason: sri must be 20m band
    #9790
    on4ro
    Participant

    Error: band (20m v ?) mismatch for SE5B working ON4RO/P
    … QSO (2017-08-09 08:56) ON4RO/P on 20m/Phone(SSB) @ ONFF-0589

    Band should be 20m

    #9792
    on4ro
    Participant

    Band should be 40m

    Fixed

    • This reply was modified 11 months, 2 weeks ago by Andrew M0YMA.
    #9836
    LZ2HT
    Participant

    Error: Activator reference (LZFF-0200 v LZFF-0584) mismatch for LZ2HT working SM7FSK/P @SMFF-3300
    … QSO #13154380 (2019-08-25 08:32:41) LZ2HT on 20m/CW(CW) @ LZFF-0584 claiming LZFF-0200

    Correct activated reference by LZ2HT is LZFF-0584

    #9839
    LZ2HT
    Participant

    Error: Reference ( v LZFF-0584) mismatch for OU7M/P working LZ2HT/1 @ LZFF-0584
    … QSO #13190844 (2019-08-07 14:16:00) OU7M/P on 20m/Data(RTTY) @ ONFF-0012 claiming none

    LZ2HT/1 reference LZFF-0584

    #9840
    LZ2HT
    Participant

    Error: Reference ( v LZFF-0584) mismatch for R7KFF/P working LZ2HT/1 @ LZFF-0584
    … QSO #13205254 (2019-08-07 07:45:00) R7KFF/P on 20m/CW(CW) @ RFF-0404 claiming none

    LZ2HT/1 reference LZFF-0584

    #9946
    LZ2HT
    Participant

    Error: reference (LZFF-0548 v LZFF-0549) mismatch for LZ2HT/P working DL4EAM
    … QSO #13367098 (2017-06-04 13:49:00) LZ2HT/P on 40m/CW(CW) @ LZFF-0549 claiming DLFF-0110

    Reference must be LZFF-0549

    #9947
    LZ2HT
    Participant

    Bad copy-paste… Correct date is 2019-09-23

    #10155
    LZ2HT
    Participant

    Error: Callsign ( ON6VG/P v ON7VG/P) mismatch for LZ2HT/P working ON7VT/P
    … QSO #13790127 (2020-02-15 11:40:00) LZ2HT/P on 20m/PH(SSB) @ LZFF-0669 claiming ON6VG/P

    Correct callsign is ON7VG/P

    #10190
    LZ2HT
    Participant

    Error: reference (LZFF-0764 v LZFF-0864) mismatch for OH/R5AF/P working LZ2HT/P
    … QSO #138694427 (2020-03-06 08:46:00) OH/R5AF/P on 20m/CW(CW) @ OHFF-0097 claiming LZFF-0764

    Correct reference is LZFF-0864

    #10249
    HB9TZA
    Participant

    Loading the Log from HB9CBR from HBFF.0104 on April 8, 2020, gaave these 3 erors:

    [ERROR] 20200408:101242 on 30M/CW between HB9CBR/P (HB9CBR) @ and R5AF/P @ UAFF-0911
    ——> Invalid hunter reference UAFF-0911;
    [ERROR] 20200408:105300 on 20M/CW between HB9CBR/P (HB9CBR) @ HBFF-0104 and R5AF/P @ UAFF-0911
    ——> Invalid hunter reference UAFF-0911;
    [ERROR] 20200408:113338 on 20M/CW between HB9CBR/P (HB9CBR) @ HBFF-0104 and UA3LMR/P @ UAFF-0911
    ——> Invalid hunter reference UAFF-0911;

    The Hunter Reference is to be coorected from UAFF-0911 to RFF-0911 , thanks
    73 44 Augusto HB9TZA

    #10272
    LZ2HT
    Participant

    Error: Reference ( v DLFF-0128) mismatch for LZ2HT working DM30RSV
    … QSO #13616224 (2020-03-29 05:08:00) LZ2HT on 20m/CW(CW) @ LZFF-0584 claiming Unknown

    DM30RSV reference must be DLFF-0128

    #10283
    LZ2HT
    Participant

    QSO #13983485
    (13983485
    2020-05-01 09:09:00) LY2BIS/P on 20m/PH(SSB) @ LYFF-0317 claiming Unknown

    P2P QSO LZ2HT @LZFF-0584

    #10350
    LZ2HT
    Participant

    Error: reference (FFF-2574 v FFF-2754) mismatch for LZ2HT working F8NUH
    … QSO #14101600
    (2020-06-07 08:45:00) LZ2HT on 20m/CW(CW) @ LZFF-0584 claiming FFF-2574

    Reference of F8NUH must be FFF-2754

Viewing 15 posts - 16 through 30 (of 36 total)
  • You must be logged in to reply to this topic.
Translate »