another wrong QSO case - Githubissues

d3m3vilurr commented 4 months ago

when a message reseived multiple QSO in the 1 message, it wouldn't work correctly

# I just changed all callsign except mine
# this is actual case
CQ DS1ABC/2
DS1ABC/2 DS1UFX PM37
DS1UFX <DS1ABC/2> -06 # he used multiple rig at the same time
JR2BCD <DS1ABC/2> -12
DS1ABC/2 DS1UFX R-5
DS1UFX RR73; DS2CDE <DS1ABC/2> +4
JR2BCD RR73; <...> <DS1ABC/2> -18
DS1ABC/2 DS1UFX -5        # this time app wouldn't detect step correctly,
                                          # so, i stopped the TX & changed step manully but too late
                                          # (all message was sent)
                                          # IMO, this time only need to send `DS1ABC/2 DS1UFX 73`
DS2CDE RR73; DS1UFX <DS1ABC/2> -14 # he recalled report that I sent the my signal again
CQ POTA DS1UFX PM37    # It would be my mistake I think I changed to TX5 step but.... idk
                                          # anyway I stopped TX again
                                          # then send message to him with messenger to check the log correctly.

I thought this QSO is F/H style, but he explained me, it's just normal qso. anyway I also got a little trouble in WSJT-Z when I contect with this style QSO. but it sent 73 message correctly, just automatically moves to CQ step without my action

bg7yoz commented 4 months ago

hi, @d3m3vilurr

这个消息就是远征模式(DXpedition)的消息（i3=0,n3=1）

DS1UFX RR73; DS2CDE <DS1ABC/2> +4 JR2BCD RR73; <...> <DS1ABC/2> -18

目前，ft8cn没有针对远征模式开发自动程序，所以，可能不会正常QSO.

73！ DE BG7YOZ

d3m3vilurr commented 4 months ago

Hello @bg7yoz

I see and I also expected that. I just hope to implement this feature soon :) (if app also support sending this message type, pretty useful to *OTA & WWFF activators.)

Thank you

DE DS1UFX

N0BOY / FT8CN

another wrong QSO case #98