My guess on this is that the a2 decode you received with your report was not real. It was on 752hz offset, not ~304hz where they were transmitting.
On Fri, Feb 17, 2023 at 8:55 AM Erik Icket via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi dear developers, > > Below is a ** correct ** sequence of fox/hound messages which are taken > from > my ALL.TXT file, but which did not make if to a full QSO in the expedition > log (snif, snif, ..) : > > 230211_170145 18.107 Tx FT8 0 0.0 1857 3Y0J ON4PB JO20 > 230211_170130 18.107 Rx FT8 -17 -1.0 752 AE8WIF RR73; ON4PB <3Y0J> > +06 ? a2 > 230211_170130 18.107 Rx FT8 -17 0.1 330 CQ KI5QQG EM46 > 230211_170200 18.107 Rx FT8 6 0.1 2090 3Y0J G0FUV IO70 > 230211_170200 18.107 Rx FT8 -9 0.5 303 RA4CA RR73; EA5ZR <3Y0J> > -12 > 230211_170215 18.107 Tx FT8 0 0.0 752 3Y0J ON4PB R-17 > 230211_170230 18.107 Rx FT8 8 0.2 2090 3Y0J G0FUV IO70 > 230211_170230 18.107 Rx FT8 -5 0.5 304 EA5ZR RR73; SP6JZL <3Y0J> > -16 > 230211_170245 18.107 Tx FT8 0 0.0 452 3Y0J ON4PB R-17 > 230211_170300 18.107 Rx FT8 6 0.2 2090 3Y0J G0FUV IO70 > 230211_170300 18.107 Rx FT8 17 0.2 1709 CQ CT1EEX IM58 > 230211_170300 18.107 Rx FT8 -9 0.5 304 SP6JZL RR73; R7MA <3Y0J> > -12 > 230211_170315 18.107 Tx FT8 0 0.0 452 3Y0J ON4PB R-17 > 230211_170330 18.107 Rx FT8 8 0.1 2090 3Y0J G0FUV IO70 > 230211_170330 18.107 Rx FT8 22 0.2 1709 CQ CT1EEX IM58 > 230211_170330 18.107 Rx FT8 -10 0.4 995 3Y0J M1ASR IO93 > 230211_170345 18.107 Tx FT8 0 0.0 452 3Y0J ON4PB R-17 > 230211_170400 18.107 Rx FT8 20 0.2 1709 CQ CT1EEX IM58 > 230211_170400 18.107 Rx FT8 5 0.1 2090 3Y0J G0FUV IO70 > 230211_170400 18.107 Rx FT8 -13 0.4 994 3Y0J M1ASR IO93 > 230211_170400 18.107 Rx FT8 -9 0.5 304 OZ3BEN RR73; OH1LEU <3Y0J> > -20 > 230211_170416 18.107 Tx FT8 0 0.0 452 3Y0J ON4PB R-17 > 230211_170430 18.107 Rx FT8 21 0.2 1709 CQ CT1EEX IM58 > 230211_170430 18.107 Rx FT8 -14 0.4 994 3Y0J M1ASR IO93 > 230211_170430 18.107 Rx FT8 -8 0.3 1583 3Y0J IV3FVM JN65 > 230211_170430 18.107 Rx FT8 -13 0.5 304 OH1LEU 3Y0J -19 > 230211_170430 18.107 Rx FT8 -13 0.5 364 OZ1JDA 3Y0J -19 > 230211_170447 18.107 Tx FT8 0 0.0 452 3Y0J ON4PB R-17 > 230211_170500 18.107 Rx FT8 18 0.2 1709 CQ CT1EEX IM58 > 230211_170500 18.107 Rx FT8 3 0.7 1497 3Y0J SV1CVV KM18 > 230211_170500 18.107 Rx FT8 -8 0.3 1583 3Y0J IV3FVM JN65 > 230211_170500 18.107 Rx FT8 -14 0.5 365 OZ1JDA 3Y0J -19 > 230211_170500 18.107 Rx FT8 -9 0.3 1544 3Y0J IK5BQW JN53 > 230211_170515 18.107 Tx FT8 0 0.0 452 3Y0J ON4PB R-17 > > 3Y0J sends my report at 752 Hz, and my first R-17 reply is sent at 752 Hz. > There is no reply from the Fox, and according to the protocol specification > "If a Hound needs to send "R+rpt" more than once, subsequent transmissions > will be moved 300 Hz higher or lower", I continue to send my R-17 report at > 452 Hz. > So far so good. > My question is how long can I send my R+rpt for it to provoke a valid "log > QSO" event ? Can a situation arise, whereby my R+rpt report has been > received but was not honored a valid QSO ? > > And a unconditional thumbs up for the 3Y0J expedition ! > > 73's Erik > ON4PB > > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
