To: | [email protected] |
---|---|
Subject: | RE: LF: 74.5495 QRSS 60 starts at 2330 till 0500 at least... |
From: | [email protected] |
Date: | Thu, 10 Oct 2013 19:47:09 -0230 (NDT) |
Authentication-results: | mx.google.com; spf=neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of [email protected]) smtp.mail=[email protected] |
Delivered-to: | [email protected] |
In-reply-to: | <[email protected]> |
References: | <[email protected]>, <[email protected]>, <[email protected]> <[email protected]> <[email protected]> |
Reply-to: | [email protected] |
Sender: | [email protected] |
Hi Jim, Bob, Group. The clock was UTC. The sigs increased until the capture then suddenly disappeared. Thanks for the confirmation, Bob. The RX seems to work wellexcept the HFO needs work. A plan is to tap the 10.7 MHz OCXO LO to clock an AD 9851 dds at 6x and use the output as the HFO. I think this will be more stable, but it could be a silly idea. Comments are welcomed. 73 Joe VO1NA If the clocks on Mike and Joe's spectrograms are both in UTC, the terminator idea is probably wrong. If the clocks on Mike and Joe's spectrograms are both in local time, I This electronic communication is governed by the terms and conditions at http://www.mun.ca/cc/policies/electronic_communications_disclaimer_2012.php |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | LF: OT: Failed Windows update hogs CPU, Markus Vester |
---|---|
Next by Date: | RE: LF: 74.5495 QRSS 60 starts at 2330 till 0500 at least..., Bob Raide |
Previous by Thread: | RE: LF: 74.5495 QRSS 60 starts at 2330 till 0500 at least..., hvanesce |
Next by Thread: | RE: LF: 74.5495 QRSS 60 starts at 2330 till 0500 at least..., Bob Raide |
Indexes: | [Date] [Thread] [Top] [All Lists] |