Hi EbNaut, For the next 24 hours will be transmitting an EbNaut Beacon (weather permitting) on 2200m Freq: 137470.00 Hz Code: 8K19A Symbol Period: 3 sec CRC: 16 Characters: 5 Duration: 00:25:36.0 Sta
Rob Local verification that all looks good ... despite lots of noise from TS Florence. Thanks for the EbNaut practice. Decode sent direct. Jay W1VD WD2XNS WE2XGR/2 Attachment: K3RWR091418A.png Descri
Hi Rob It was too late for me too and my Rx was not correctly configured last night Will be recording files the next two ningts and see if we have luck 73 de Luis EA5DOM De: owner-rsgb_lf_group@black
Hi Rob and Luis, ...and here, i found a suboptimal configuration in my settings for the FFT export (took the old 10 kHz ref signal instead of the new PPS method). Settings changed. From now on there
Nothing decode last night, Rob Are you using Slabs for Tx ? I understand than if you are using SLabs the timeshift must be increased by 0.3 + 4/Sample Rate seconds I have tried to decode the files wi
Hello Rob and EbNauters, With pleasure, i got one T/A decode at 04:00 UTC of today : 2018-09-16_04:00:00 137470.000Hz N=5 T=3s 8K19A CRC=16 list=5000 sym=512 Duration=1536s found rank 650 ber 3.574
Hi EbNaut Congratulations for the TA decodes of previous night (15 to 16th), Rob and Domenico ! No luck here last nigh And I can see at Domenico grabber, EbNaut auto decoder log, that there were no d
Hi Rob, A late report from here, see attachment. I tried all transmissions from 0...4 UTC. Two of them were strong enough to decode here (1 UTC and 4 UTC). Best result attached. 73, Stefan (JN49IK) A
Hello 2200m EbNaut, The results of the EbNaut beacon tests are very encouraging for the domestic and TA paths. Thank you to all who listened, decoded, reported and commented Seeking a practicable EbN
Another belated report: Three decodes in Nürnberg in the morning of Sep 16: start EbN0 rank UT dB 03:00 1.0 89 03:30 0.7 17 04:00 3.9 0 At DL0AO in Amberg, we picked up pieces of carrier before and a
Hi EbNaut LF Good idea Rob ! We need to standarize a message format for QSOs. You proposal looks right for that I assume you will keep using 137.470 Hope to decode you soon. I need to improve my Rx 7
Hi Luis, Rob, I would vote for 15 characters rather than just 12. In JT-9 there are 13 characters which is often a bit short and limits the fun of the mode. For practical reasons it is necessary to u
Although it will be some years before I can have the necessary equipment to run EbNaut I am *very* interested in QSO modes, so I want to comment on this. Please use more than 12 character messages. R
Using the known message I searched Time-Doppler-space in the DL0AO 4 UT file. The peak occured at 1.1 s time delay (presumably due to latency of the virtual audio cable between cascaded SpecLab insta
Hi Stefan, Luis, Paul, Markus and 2200 meter EbNaut, Thank you all for the comments and suggestions. Lots of good ideas. Stefan & Paul: Agree that 15 characters is a better choice. Expanding the text
