[Moon] QSO or not?

[YU7XL]

Hi, all,
Following Jimmy`s (SV1BTR) letter, one example how the things can go wrong 
leading to a false qso (it was in JT65b, but it might be any mode):
Line 1:              CQ DL7***
I am TXing:      DL7*** YU7XL
Line 2:             YU7XL DL7*** OOO
I am TXing:     RO
Line 3:            73 (obviously, he made a mistake omitting to send RRR 
confirmation)
I am TXing::    RO
Line 4:            73
Line 5, 6, 7.....73
I am TXing:     RO
Line 8             ???? (not decoded)
I am TXing:     RO
Line 9             RRR (Fine! He wrote on MoonNet just: "grrrr, mistake...")
I am TXing:     73
Line 10...........73
The QSO had not been skeded, and I went to the MoonNet for the first time, 
saying: "DL7***, tnx fr QSO..."
The answer was: "No, our qso is not correct; I just worked YO5***...."
This happened three days ago.
The reader can come to an explanation easily. I was not guilthy, DL7*** not 
guilthy, neither WSJT!!!
But, QSO is not OK, It happens!
73 Boban, YU7XL
----- Original Message ----- 
From: <jimmyv at hol.gr>
To: <moon at moonbounce.info>; <moon-net at list-serv.davidv.net>
Sent: Wednesday, May 02, 2007 10:19 AM
Subject: [Moon] QSO or not?


> Hello all
>
> I am trying to understand how JT65 works sometimes (even without Deep 
> Search!),
> especially when it comes to expeditions. I am confused.
> Could you please explain to me how is possible to have a QSO as complete 
> in the
> log of an expedition, when the station calling them says it is not 
> complete?
> However, expedition says it has data files for all QSOs. So does the 
> station
> trying to work them. So where is the error?
> This is even more profound because in the case of JT65 it is even more 
> difficult
> to make a personal judgement mistake. Since software algorithms do the 
> decision
> making for you and we have been told that reliability of a contact remains
> intact. Regardless of signal level.
>
> As i do not question the integrity and experience of operators in the 
> specific
> expedition (in fact they are experienced operators with good operating
> standards), neither do i question the experience and integrity of the
> particular station calling them, then is it the JT65 software generating 
> the
> error? I think, and hope, not.
>
> Perhaps is it the plain shorthand messages? To me, it looks like this 
> being the
> reason, because shorthand messages are not accompanied with callsigns 
> (unless
> the Big exception of someone transferring both reports and callsigns as 
> unknown
> text). Therefore, using the standard format of shorthand messages, in a 
> pileup
> situation, one can not be sure if the RO or Rs received was for him or
> not...(as logger extract shows below at 5:19)
> We have seen situations with other expeditions in the past.
>
> To substantiate my argument and subsequent confusion with facts, pls find 
> below
> extracts of ON4KST logger showing PE1BTX saying to ZB2/DH7FB he did not 
> have
> complete QSO with ZB2 expedition. At the end of this mail, pls see the log 
> of
> ZB2 expedition where QSO is listed as complete.
>
> Once more, i will repeat this is nothing personal and NOT aiming the 
> operators
> involved; the specific case is merely used as another example. But just
> scratching my head as to how some QSOs eventually take place and the 
> totally
> different outcomes reached. Your help in understanding what is happening 
> is
> appreciated!
>
> Thanks in advance & 73,
> Jimmy SV1BTR
>
> ON4KST logger:
> 05:26:40 PE1BTX Gerard 4X12/QRO Frank, but despite my NC congrats on your 
> FB
> operation, you gave a lot of stations a new DXCC
> 05:24:05 DH7FB frank gerard, yes in next time we will also do this
> 05:19:50 PE1BTX Gerard 4X12/QRO Frank, could be, pse look my EME log
> http://www.pe1btx.nl/EME%20initials%20all%20bands.htm
> 05:19:16 DH7FB frank gerard, so the received "ro" came fm another stn 
> maybe
> 05:16:17 PE1BTX Gerard 4X12/QRO Yep, NC for me, but already wkd ZB2IQ back 
> in
> 1983 on ES, and confirmed
> 05:13:57 PE1BTX Gerard 4X12/QRO Found my QSO complete in the log, but 
> never
> send RO to him on 21st, so not complete for me, did not even had a decent 
> decode
> on 21st, very strange
>
>
> PE1BTX Log (bottom of his webpage)
> http://www.pe1btx.nl/EME%20initials%20all%20bands.htm
>
> ZB2 log:
> http://www.df2zc.de/hamradioresults/seite5/022c0a991e127580c/index.html#022c0a992008a0a01
> EME
> 21.04.2007
> 1110-1113 PE1BTX O/RO -21 dB C 9
>
>
>
>
> _______________________________________________
> Moon mailing list
> Moon at moonbounce.info
> http://www.moonbounce.info/mailman/listinfo/moon
>
> Please enter/update your standings: http://www.vhf-dx.net/top.html
>