After some CPU-sweat, the first decode happened after 21 UT: Eb/N0 1.8 dB, 607/2144 bit errors, rank 0. 39 characters in just under 18 minutes - not too bad ;-) 73, Markus --Ursprüngliche Mitteilung-
A plot of the daytime correlation of I/Q against the known encoded message http://abelian.org/vlf/tmp/151204a.gif shows significant spikes with each half-hour message, up to 14:00. Only the first two
Hi Markus and Paul, Group, Thank-you for the reports. I'll try 0.2 s symbols, 131 characters tonight starting 2000. I's better get out and deal with the snow in the drive before it gets too dark. 73
At 20:00 and 20:30 I only got carrier. It decoded well with 131 chars and 0.2S symbols, Eb/N0 = 1.7 but no modulation. Looks like ebkey is limited to 5000 symbols and this one needs 6560. I've modifi
Hi Paul, compiled v0.3 but got a bailout 5000 symbols for 8K19A so tried 4K19A. Set to go in 8-1/2 mins. 0.2s symbols 131 chars. Joe At 20:00 and 20:30 I only got carrier. It decoded well with 131 ch
For some reason, you're still running the earlier version. ebkey -? gives you the version. Check the execution path and the gcc -o option. That might be about 3dB too weak. I made a spectrogram of on
Joe, Copied your 131 char 4K19A 0.2S 21:00 message fine, Eb/N0=7.2 and I think that's a record for message length but not for capacity. -- Paul Nicholson --
Something taking up your RAM, the decoder needs 3.8 Gbytes for this one which should fit ok. The 4K19A 0.2S signal is much stronger than I expected and decodes easily with uniform phase. We're stret
The timing of these 0.2S messages appears to be spot on, I'm getting about a 10mS lag which would be roughly the propagation delay. So far, VO1NA 2015-12-04/05 4K19A 0.2S 131C QRO start Eb/N0 BER ran
Just looking at various TA grabbers at this point, and wondering if this higher BW stuff should be moved away from the TA window near 137.780 kHz. Perhaps with the lower activity it doesn't make as m
