[ADXA] A52CI FT8 decode

[w5znjoel at gmail.com]

Not to distract from Pat's inquiry, but if anyone see's or hears A5 on 10
meters please post here immediately. I only need A5 on two bands, 160 and
10. A snowball has a better chance of surviving in hell that I do working
them on 160 this time of year simply because we have no common window. 10 is
doable. The other evening when they were on 12 meters the sig was strong and
a 10 meter path was very possible.

 

Anyway, please post any A5 10 meter sigs you hear (or see for you FT8 folks)
on our reflector!

 

73 Joel W5ZN

 

From: adxa-bounces at mailman.qth.net <adxa-bounces at mailman.qth.net> On Behalf
Of patw5vy at gmail.com
Sent: Monday, April 22, 2024 10:22 AM
To: adxa at mailman.qth.net
Subject: [ADXA] A52CI FT8 decode

 

Dennis, W5RZ, reported difficulty with decoding A25CI on 17M FT8.  I've got
the same issue.  In the morning (12-14Z) A52CI has been relatively strong
here on long path.  The multiple streams blend into one "blob" and I have no
decodes.  I've tried pointing east and west of the direct heading with no
change.  I've turned AGC off, NB off, etc.  Tried Fast, Normal and Deep
decode with no change.  As conditions change and the A25CI signal becomes
weaker I start seeing decodes and right before propagation ends I get a
decode almost every cycle.  During that time they seem to only hear EU and I
haven't been able to get their attention.  They are in and out right
now.just about gone for me (1512Z).  At times they are strong enough for CW
but I haven't seen them on CW yet?

 

I have A5 on 30 and 15M CW from previous activations.  Just curious if
others are seeing this destructive multipath prop?  I think FT4 would work
better during the multipath..tone spacing is wider.  You lose a few db of
sensitivity but I think the improved decode of FT4 would make up for it.
I've seen this multipath on 432 FT8 during my roving activity in VHF
contests.  FT4 usually works much better.   

 

Pat, W5VY

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/adxa/attachments/20240422/9c87c27e/attachment-0001.html>