Hi VLF, I know now that there seem to be a number of newcomers trying to get a first detection in EbNaut on VLF, as well as carrier detection. So on one side, it makes sense to come back to shorter m
...correction (symbol length of the 2nd transmission) Am 24.02.2017 15:16, schrieb DK7FC: Hi VLF, I know now that there seem to be a number of newcomers trying to get a first detection in EbNaut on V
Good decode for the first transmission on 20170224 17:59:58 (message sent off list for confirmation) found rank 0 ber 3.4145e-01 Eb/N0 3.6 M -1.256115723e+01 [XXXXXXXXXX] ps [ 0 0 0 0 0] carrier phas
Thanks Eddie, Jackek and Paul for the EbNaut decodes on VLF! I'm excited if there is a decode in Italy or Russia :-) I confirm the messages sent to me are correct, of course, there can be no doubt wi
Thanks Eddie, Jacek and Paul for the decode. The message is correct :-) Alex/RN3AUS will have to search for 3 EbNaut messages now, 8ch, 10ch and 4 ch :-) The normal carrier on 8270.005 Hz is still ru
Another fantastic signal from Stefan today, very strong and stable in amplitude and phase. http://abelian.org/vlf/fbins.shtml#p=1488139200&b=120&s=sp This really is a great opportunity to test receiv
Good decode of the 12 Chr. message in Northampton UK IO92ng. Message XXXXXXXXXXXX PM sent to HQ for confirmation. found XXXXXXXXXXXX list rank 1005 reference phase 30 30 30 30 carrier RMS 4.7
Hello Eddie, I confirm the message :-) Thanks for the feedback, always good to know the message went out as expected. BTW it is useful to run the decode process until it is completed (= 25%, at 30 d
Decoded fine the 20170226 transmission (text send offline to Stefan). the Eb/N0 is small probably because of some problems with the receiver (it says that 9984s, or almost 3h were padded), probably b
Thanks Jacek, i confirm. BTW i remember there could have been an unintentional time offset, at least i took a screenshot from the beginning message and saw some anormalies. I can't check it on my own
Your message was decoded here as well, even though my recording covered only 78% of the 11.3 hour sequence. ebnaut-rx V0.5 input file 02270023.wav sample rate 0.514405 per second rx frequency 8270 fi
No problem with the decode here, Eb/N0 +7.8dB. The message has md5 hash = df2ba39b3842b67c23a71ebdf466b6cf echo -n 'XXXXXXXXXXXX' | md5sum Timing looks ok, best decode at offset +0.3 seconds. -- Paul
Thanks Paul and Markus for the decode. Everything seems to be fine! :-) Soon Alex will be there with his results, i'm curious! 73, Stefan Am 27.02.2017 14:53, schrieb Paul Nicholson: No problem with
Stefan, i've found the error, now decoded as 6.5 dB Eb/N0 prep [ 0 0 0 0 0] found rank 0 ber 2.7417e-01 Eb/N0 6.5 M -6.505279541e-01 [MEEEEEEEEEOW] ps [ 0 0 0 0 0] carrier phase: -11.6 carrier Eb/N0:
Hi Alex, thanks for the results. Pity, it looks like the last improvement rather lowered the sensitivity. We need to continue more systematic. More details in a private mail. At least one decode, to
Stefan wrote (22nd Feb) (28th Feb) The message is in there at Eb/N0 = -2.5 dB. Timing good. Not sure about frequency yet, still sweeping (slowly, the PC is full of 16K19 trials). Error map http://abe
Hi Paul, Great work, as usual. Thanks. -2.5 dB, that agrees with the Eb/N0 value of the 4 character message. Alex has re-optimised the system again. New attempts for a message longer than 7 character