[ADXA] Some V84SAA frustrations

Fri Feb 15 22:20:20 EST 2019

I had V8 on 15, 12 and 10M CW before this DXpediton.  I struggled the first
few days to hear them but have managed to work them on 40, 30, 20 and 17CM
and 40M FT8.  The 30M CW QSO isn't in the log so I'll try to catch them
again before they leave.  It's a great team of operators and I give them
high marks for digging out the weak ones and hanging in there until a Q is
completed.

I've also been chasing XX9D for an ATNO.  Looked at prop charts and watched
spots from NA - Midwest and though I'd catch them early in the morning on
40 or 30.  Got up at five a couple of mornings and only heard them weakly
one morning on FT8.  So, Thursday morning I got up at 2:15am and found they
were working EU/AS on the higher bands and weren't on 40 or 30.  Kept
watching/listening and saw V84SAA pop up on 40M FT8 and made a Q.  About
7:30am XX9D came up on 40M FT8 with a decent signal.  I worked them just
before 8:00am and did a happy dance.  I crashed for about four hours then
got up and did some home maintenance chores.  After dinner I walked into
the shack and found they were on 30M CW with a decent sig.  I worked them
in about 10 mins....quite a contrast to the up at 2am routine!  The 40M FT8
Q is in Club Log now so I'm at 329 confirmed.  One of the non-rare entities
on my list is AP.  I'll have to bear down and try to snag one!  The rest
are 1S, 3Y-B, BS7, BV9P, EZ, FT8W, JD1-M, KH3, P5 and YK.   I missed the
last Spratly activation (last year).  I remember Bernie, W3UR, commenting
that activation of FT8W, Crozet Isle, is not likely to be on for a while
due to protected status of flora/fauna.  EZ is about like P5 now....very
oppressive government. JG8NQJ, who was the weatherman that visited JD1-M
regularly is no longer making that trip.  Hopefully someone will get
permission to operate from there one of theses day.  Can't remember what
Bernie said about KH3, Johnston Is.  Just hoping to achieve HR before
senility completely takes over!

Happy hunting/73,
Pat, W5VY

On Fri, Feb 15, 2019 at 5:57 PM J. Setcer <j.setcer at gmail.com> wrote:

> With regard to V84Saa, and their dismal QSO percentage....
> I'm going to throw my experiences into the ring.
> My story was the same as some of you other guys.
>  I was 97% SURE I made the contact with V84SAA,,, But when I checked the
> Club Log,,, I had NO GREEN CHECK MARKS
> I kept trying to work them again. I did keep checking their OQRS page.
> SUDDENLY, i HAD a green check mark. Many days after they uploaded, but
> without Mine.
>
> I asked RZ, Dennis, how this could happen. He says "All their Computers
> are networked, but some are more networked than others." (1984)
>
> Anyway, I said all that to say this... Keep checking
> https://clublog.org/charts/?c=V84SAA
> You may be suprised that they FOUND your QSO.
>
> I'll say One More Thing.... I did NOT wait until after the DXpedition was
> over to request my QSL like I usually do.
> Dude, If they lost it twice,,,, I'll take mine while the Getting is good.
>
> 73, QJ
>
>
> On Thu, Feb 14, 2019 at 8:19 AM David Norris via ADXA <
> adxa at mailman.qth.net> wrote:
>
>> I think - I worked them on 40 CW this AM- they came back to me - whether
>> or not I show up in the log is anyone’s guess...
>>
>> 73
>>
>> David A. Norris, K5UZ
>> Director, Delta Division
>>
>> Sent from my iPhone
>>
>> On Feb 14, 2019, at 8:13 AM, Paul Dixon <kk5ii at cox.net> wrote:
>>
>> Amen to hearing them, much less working them (even on ft8-San).
>> Thanks for the info.  I’ve been in the shack at 4:00 am the last 2 days.
>> Will keep trying, for sure.
>> Paul, kk5ii
>>
>> Sent from my iPhone
>>
>> On Feb 13, 2019, at 3:26 PM, HamOP <k5yy1 at cox.net> wrote:
>>
>> There have been many missed log “QSOs” on the recent V84SAA ClubLog
>> updates. I feel badly for those ADXA members who have missed the V84 for an
>> ATNO, especially if you have chased, supposedly worked them, and then find
>> you are *not* in the log updates.
>>
>>
>>
>> I have chased for the fun of it, not needing V84 on any band per se. But
>> I have gotten up 3 straight days at 5:15AM and looked for them on 3.5 to
>> fill in a couple of spots, at our SR timeframe, and I *constantly listen*
>> on 18mc and 10mc CW during the 2200-0000Z propagation peaks EACH day. I
>> felt sure I worked them on 3.5 only to find I was logged as a non DXer
>> K4YY, despite correcting the operator 3 times in the QRM, getting the YY
>> correct and then being told RRR on the K5 correction. Still not in log. On
>> 10mc yesterday I was 90% sure he got all OK but I did “dupe” them (God
>> forbid) 15 minutes later when he peaked and I was a little unsure of the
>> first “QSO”. This time all was received OK but still NOT in log on recent
>> update. On 18mc 2 days ago, a “clear QSO” was met with not in log on recent
>> updates. So, 3 bands I thought I had them on and still only have credit for
>> 40m and 20m..
>>
>>
>>
>> So, do not be threatened with a “mis-logged” situation. Get in there and
>> *try* to spend some time and perhaps get up before our SR, hoping to
>> catch *another* “QSO” on low bands.. If they have as much QRN and QSB as
>> we do, along with *weak* signals, then I understand there will be
>> mis-logging. But, many recent posts on DX Summit are full of “not in log!”
>> or “good QSO nil” etc. There are just 3 more days and the DXped is over.
>> This morning signals were so weak on 80CW that I did not even call. This
>> afternoon I will be looking on 30m and 18mc again for a “valid QSO” … Hope
>> 3 times is a charm, as they say. GL to ADXA guys who need this for an ATNO
>> or even a new band-mode. The XX9D has even been harder to hear!!!
>>
>>
>>
>> San YY
>>
>>
>>
>>
>>
>>
>>
>> Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
>> Windows 10
>>
>>
>>
>> ______________________________________________________________
>> ADXA mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/adxa
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:ADXA at mailman.qth.net <ADXA at mailman.qth.net>
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>>
>> ______________________________________________________________
>> ADXA mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/adxa
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:ADXA at mailman.qth.net <ADXA at mailman.qth.net>
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>>
>> ______________________________________________________________
>> ADXA mailing list
>> Home: http://mailman.qth.net/mailman/listinfo/adxa
>> Help: http://mailman.qth.net/mmfaq.htm
>> Post: mailto:ADXA at mailman.qth.net
>>
>> This list hosted by: http://www.qsl.net
>> Please help support this email list: http://www.qsl.net/donate.html
>
> ______________________________________________________________
> ADXA mailing list
> Home: http://mailman.qth.net/mailman/listinfo/adxa
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:ADXA at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/adxa/attachments/20190215/c59c4f30/attachment-0001.html>