This is a multi-part message in MIME format.
--part0_890429296_boundary
Content-ID: <0_890429296@inet_out.mail.aol.com.1>
Content-type: text/plain; charset=US-ASCII
>From NL7Z!
This is neat stuff!
Tks Kevin for sharing it!
73 Jeff K1ZM@aol.com
--part0_890429296_boundary
Content-ID: <0_890429296@inet_out.mail.aol.com.2>
Content-type: message/rfc822
Content-transfer-encoding: 7bit
Content-disposition: inline
Return-Path: <nl7z@alaska.net>
Received: from relay22.mx.aol.com (relay22.mail.aol.com [172.31.106.68]) by
air11.mail.aol.com (v40.16) with SMTP; Fri, 20 Mar 1998 15:50:19
-0500
Received: from calvino.alaska.net (calvino.alaska.net [209.112.130.6])
by relay22.mx.aol.com (8.8.5/8.8.5/AOL-4.0.0)
with ESMTP id PAA11776 for <K1ZM@aol.com>;
Fri, 20 Mar 1998 15:50:17 -0500 (EST)
Received: from nl7z (paq-p51-226.alaska.net [209.112.145.226]) by
calvino.alaska.net (8.8.8/8.7.3) with SMTP
id LAA00841 for <K1ZM@aol.com>; Fri, 20 Mar 1998 11:50:15 -0900 (AKST)
To: <topband@contesting.com>
Date: Fri, 20 Mar 1998 11:50:15 -0900 (AKST)
Message-Id: <199803202050.LAA00841@calvino.alaska.net>
X-Sender: nl7z@alaska.net (Unverified)
X-Mailer: Windows Eudora Light Version 1.5.2
To: K1ZM <K1ZM@aol.com>
From: Kevin Forster NL7Z <nl7z@alaska.net>
Subject: echo
Mime-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
>
>(Kevin - at what times did you work these other guys? Was it at their
sunrise
>times also? Or were these qso's soon after our QSO? In other words, when
>did this event start and end for you? Were all of us at our sunrise times?
>Can you pse give us a list of your log?)
>3) If it WAS multilayer illumination, do you have any idea why the signal
>would PEAK from another distinct DIRECTION very much away from the DIRECT NW
>path, eg: normal heading?
>
>Jeff, here is an extract from my log - feel free to repost to the
reflector if you want.
One interesting thing here - as iI was logging these in my new logging
program I put "foot notes"
in each entry - I did not notice this pattern until I extracted these qso.
1: It was a sure thing that the louder the signal - the more echo it had
i.e.:you were s-2 clg cq with some echo , I then called you and you switched
around and came up to a s-6 with ALOT more echo enough that I had trouble
with the report.
2: WV3B was maybe an s-1 but more like an s-0 with almost NO ECHO!
Let us assume it was long path indeed. Only the stations with enough
power/ant/takeoff would be able to send a signal long path right? (maybe)
and those stations with 100w and a dipole (WV3B, K2WI)? do not have enough
(ya know) to make a L.P. trip. Just an idea.....
The Log NL7Z 03/20/98 160m
10:14 VE1ZZ 559 MUCH ECHO
10:20 VE3DO 559-579 MORE ECHO
10:24 W8JI 579-599 SO MUCH ECHO I BLOW HIS CALL SEVERAL TIMES!
10:26 W7EKM 599 IN WA. MODERATE ECHO BUT NOT LIKE W8JI
10:40 KIZM S-3 CQ'ING SOME ECHO
10:41 K1ZM NOW S-7 A ALOT OF ECHO TROUBLE GETTING RST!
10:42 K2WI S-2 NOT MUCH ECHO
10:58 W3BGN S-2/S-3 NOT MICH ECHO
11:04 WV3B S-0/S-1 NO ECHO
11:06 5W0VD NO ECHO
I hope this helps
If 160 sounded like that all the time I think I
would go crazy crazy crazy crazy..... ad nauseium...
Kevin NL7Z
--part0_890429296_boundary--
--
FAQ on WWW: http://www.contesting.com/topband.html
Submissions: topband@contesting.com
Administrative requests: topband-REQUEST@contesting.com
Problems: owner-topband@contesting.com
|