Re: [Elecraft] ECN/30 Report

2005-04-08 Thread vze3v8dt
that contact (thanks to a photo from Ed, WA3WSJ). Hopefully I'll check in next week again! Mark, NK8Q >Subject: [Elecraft] ECN/30 Report >Just a quick note to acknowledge all who checked in last evening. This was our >second week operating at 0100z - but with daylight savings

Re: [Elecraft] ECN/30 Report

2005-04-08 Thread Fred Jensen
K6DGW's KX1 S/N is #897. I guess it got lost in transmission. I was surprised at the signal strengths out here on the frontier ... NK8Q was easily a "real" 569 as was Daniel. 0100Z works pretty good for us PDT types unless we have family or friends over for dinner. 73, Fred K6DGW Auburn CA CM9

[Elecraft] ECN/30 Report

2005-04-08 Thread Daniel Reynolds
Just a quick note to acknowledge all who checked in last evening. This was our second week operating at 0100z - but with daylight savings time, it looks like quite a few more folks from the west coast checked in. CALL NAME ST RIG SNRST Sent == = == = = WA7B

[Elecraft] ECN/30 report

2005-03-25 Thread Daniel Reynolds
Last night, I ended up calling on 10.112.7 because I was hearing some occasional broadband digital QRM on 10.102.7, and someone was calling near 10.107.2 just before the net started. The one and only check-in was Rick/WA3TUU in Michigan. Next week, I'm going to try calling the net one hour later (

[Elecraft] ECN/30 report

2005-03-11 Thread Daniel Reynolds
Someone once wisely suggested picking a non-cardinal frequency for the ECN - and I think I really need to heed that advice next week - so watch for an odd frequency (e.g. 10118.7) for the net next week. Running QRP-10W has it's disadvantages - especially when a DX station (TO7K/TO7C?) starts calli