Broken Callsign Thread

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #10599
    Andrew M0YMA
    Keymaster

    This thread should be used ONLY to claim one of the broken QSOs listed on https://wwff.co/2020/09/database-tidy-up-broken-callsigns/

    I need evidence to back up the claim…

    Any other posts will be deleted!

    • This topic was modified 1 month, 1 week ago by Andrew M0YMA.
    #10602
    RN3ANT
    Participant

    11914941 2018-09-10 RI0B RFF-0015 20m/SSB 1R4AZ — R4AZ is correct
    12635253 2019-04-19 UA3LDU/P RFF-0487 20m/CW 1RM6J — RM6J is correct

    Fixed M0YMA

    • This reply was modified 1 month, 1 week ago by RN3ANT.
    • This reply was modified 1 month, 1 week ago by Andrew M0YMA.
    #10625
    Andrew M0YMA
    Keymaster

    Thanks

    Sticked “1” in front of callsign is missed space between time and callsign when log was proceeding with FLE.

    That should now be trapped during log upload… any callsign with 0 or 1 as a prefix (stand fast 1A) is rejected; and am adding additional validation for 2 (UK “intermediate” calls)

    #10643
    RN3ANT
    Participant

    Thank you, Andrew!

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.
Translate »