|Subject:||Re: LF: EbNaut on LF|
|From:||Markus Vester <[email protected]>|
|Date:||Sat, 20 Aug 2016 09:11:23 -0400|
|Dkim-signature:||v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1471698685; bh=BTKlIhGjtjO3d0osKMkBPhwCP5wuXrvtPDxYdc4NhkE=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=GHMlZBCPLOkX/7NuVSxUsgLmFZ5mqcsyA0bQpzU7i2clV/mPcQBMyODInbCe1wYOn K5naM5Z+Mom2KVb5FSa1y/zws8rtwDcTiMdNsf5euv/SLCdMfvyExPjUp+vUbg3hUU dkQMI60SRMsXu+Divih0hUtMFTu/8kxw/6phEz8U=|
yesterday night (Aug 18/19) there was high QRN well into the wee hours. After some tweaking of the time offset, I managed to extract a single marginal decode from the 4:15 sequence.
I was still wondering why the decode was weak in terms of EbN0, despite an already visible agglomeration of dots in the phase plot. Comparing the carrier phase before and after the sequence allowed me to rule out receiver glitches. The real reason is probably that compared to the mostly used 8K19 code, 4K19 has less spread and longer symbols, which at same EbN0 shows up better in the constellation plot and squared-symbol spectrum. Shorter codes are also easier on timing accuracy, CPU and memory, but don't go down quite as deep in EbN0 as longer codes do. In any case, your net data rate of about 20 characters per minute is quite impressive...
Last night conditions were much better, with stronger sigs and low statics from the beginning. The 00:15 (Aug 20) transmission immediately came up with EbN0 = 7.7 dB.
Von: jcraig <[email protected]>
An: rsgb_lf_group <[email protected]>
Verschickt: Sa, 20 Aug 2016 12:00 am
Betreff: Re: LF: EbNaut on LF
One more operation tonight starting 2300 and every 15 mins.
150 watts 2 amps RF. 137.477 kHz, 1432 0.2s symbols, 4K19A.
|<Prev in Thread]||Current Thread||[Next in Thread>|