[ADXA] V84SAA today... STRONG for about 10 minutes at 1330Z..

[HamOP]

This morning the V84 peaked from a 329 to 599 at 1335Z, LOUD for 10 minutes. Then he faded to ZERO within 15 minutes. I promise if any of the ADXA members need V84, especially on 80m, get up and going by 7AM, not 5:30 like I did again today for 5th day.. Called for an hour or so and then in that 599 period got him so quickly. Still said K4 once and K6YY once. So I thought “here we go again”.. Nice to hear him give my complete, correct call and then RR my report to him.. 

I was on my small 24 foot vertical since he was weaker on my 35 foot 80/160m dipole. Same yesterday, vertical was better, but if a dipole is at 66 feet, I think it will outdo the vertical, as pointed out at the ADXA December forum on what antennas to use, especially on lower bands. Horizontal vs Vertical polarized.

Hang in there Paul. Get on tomorrow at 7 ish and they are on 3503 usually, listening up 1-1.5kc.. Only 3-4 more days but I am sure will tear down the low band antennas first. 
San

Sent from Mail for Windows 10

From: Paul Dixon
Sent: Thursday, February 14, 2019 8:13 AM
To: HamOP
Cc: ADXA at mailman.qth.net
Subject: Re: [ADXA] Some V84SAA frustrations

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 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

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/20190214/d2757255/attachment.html>