To: | [email protected] |
---|---|
Subject: | Re: LF: 3 mode Beacon 503.00 502.700 503.2 1800 gmt > later |
From: | John Andrews <[email protected]> |
Date: | Sun, 10 May 2009 15:54:25 -0400 |
In-reply-to: | <[email protected]> |
References: | <006e01c9d0e4$d6af66b0$6401a8c0@asus> <5086F7980B3E4BB0AF60D8620D735B5E@JimPC> <008901c9d0ea$1dc16cb0$6401a8c0@asus> <61ECB87CADD94B23BE3BBFF76DBCE7C3@AGB> <4C4336FD5157446E84F89E666407F64C@AGB> <1FD7913FE62A449BA85637178BF518B1@AGB> <[email protected]> |
Reply-to: | [email protected] |
Sender: | [email protected] |
User-agent: | Thunderbird 2.0.0.21 (Windows/20090302) |
Rik,Experience with MFSK4 over here showed that it held together very well as a signal dropped in a fade, but the resync was nasty if copy was lost. So in a bench test where you start out with a strong signal and attenuate it until copy is lost, MFSK4 will show a great signal range. But starting from a weak signal is tough, as is recovering from a fade. Resync with MFSK8 seems much better, but it's pretty wideband for this application. John, W1TAG |
Previous by Date: | Re: LF: 3 mode Beacon 503.00 502.700 503.2 1800 gmt > later, Rik Strobbe |
---|---|
Next by Date: | LF: RE: 3 mode Beacon 503.00 502.700 503.2 1800 gmt > later, Gary - G4WGT |
Previous by Thread: | Re: LF: 3 mode Beacon 503.00 502.700 503.2 1800 gmt > later, Rik Strobbe |
Next by Thread: | Re: LF: 3 mode Beacon 503.00 502.700 503.2 1800 gmt > later, Graham |
Indexes: | [Date] [Thread] [Top] [All Lists] |