To: | [email protected] |
---|---|
Subject: | Re: VLF: WOLF, next step.. |
From: | Stefan Schäfer <[email protected]> |
Date: | Mon, 30 Jan 2012 19:57:58 +0100 |
In-reply-to: | <[email protected]> |
References: | <[email protected]> <EB550E30D4E84FCEBDEACF07F9E2A7A4@White> <CAK59VFOT_JoAbOjxGxdz3NB4XWRodyN54=EgutPgb9YowueA9Q@mail.gmail.com> <50DDDC5E26754BC284D529DCB4A1C2C3@White> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> <[email protected]> |
Reply-to: | [email protected] |
Sender: | [email protected] |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 |
Bill,Thought about the zero-crosings. Does it actually make sense to change the phase reversal time? Since the samplerate is drifting anyway, there will be a small time difference between a phase shift and there zero-crossing. Also -if the samplerate would be exactly 24 kS/s-, the time when the phase shift occurrs can be somewhere, i.e. wouldn't be sync'ed to the zero-crossing. Right? So it may be easier (also for the receiving side) to let it remain at 0.1 seconds. Comments welcome. 73, Stefan/DK7FC Am 30.01.2012 19:24, schrieb Stefan Schäfer: Changed the phase reversal time from 0.1 s to 0.111482720178372 s (=1000/8970Hz) Seems to work. Am 30.01.2012 01:37, schrieb Bill de Carle: Can your Tx handle abrupt phase shifts every 100 msec? We can arrange for the phase shifts to occur only at zero-crossings of the 8970-Hz sinewave. |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: LF: 136 Opera, Graham |
---|---|
Next by Date: | LF: WE2XGR/2 WOLF 506.5 kHz, jrusgrove |
Previous by Thread: | Re: VLF: WOLF, next step.., Stefan Schäfer |
Next by Thread: | Re: VLF: WOLF, next step.., Bill de Carle |
Indexes: | [Date] [Thread] [Top] [All Lists] |