With egg on face, Paul DU2/WA8UGN writes:
Paul DU2/WA8UGN writes:
>
> Murray Curtis ...> writes:
>
> >
> > Hi Paul
> >
> Hi Murray
>
> > Thanks for spotting this. Do you recall if the station was using the
> > 'standard' CQ call? Currently the use of "CQ DX " will cause
this
> > type o
Murray Curtis writes:
>
> Hi Paul
>
Hi Murray
> Thanks for spotting this. Do you recall if the station was using the
> 'standard' CQ call? Currently the use of "CQ DX " will cause this
> type of error.
Yes, each station was using the "standard" CQ call. The use of "CQ DX
" causes more pr
Hi Paul
Thanks for spotting this. Do you recall if the station was using the
'standard' CQ call? Currently the use of "CQ DX " will cause this
type of error.
I have good intentions to address that and a couple of other minor
quirks. I'll get to that soon I hope.
Cheers
Murray
VK3ACF
On 1
Hi Paul,
Thanks for your report.
On 2/12/2015 2:51 PM, Paul DU2/WA8UGN wrote:
> Mode: JT9+JT
> Decode: Deepest
> Band: 10.138000
> Time: 1932 02-12-2105
>
> Anomaly: Decoding of station calling CQ as being "New DXCC" but have QSO'ed
> same station on 10.138000 three times prior. JTAlertX verifi
Mode: JT9+JT
Decode: Deepest
Band: 10.138000
Time: 1932 02-12-2105
Anomaly: Decoding of station calling CQ as being "New DXCC" but have QSO'ed
same station on 10.138000 three times prior. JTAlertX verified station
worked B4, and log check shows 3 out of 5 QSOs with this station being on
10.13
