VLF, Now the coil resonance is right on 6470 Hz. A + 5 Hz or a - 5 Hz step is leading to a lower antenna current. The carrier will stay on air for at least 1 day, that's the plan. An EbNaut message w
PS: Carrier on air since 20:05 UTC. 73 Am 17.04.2017 22:36, schrieb DK7FC: VLF, Now the coil resonance is right on 6470 Hz. A + 5 Hz or a - 5 Hz step is leading to a lower antenna current. The carrie
There was an interruption of the carrier between 5:28...5:48 UTC. This was again by reaching the -20 mA safety limit. It was just due to rain which pulled the resonance to much downwards, despite the
Getting good readings from the excellent signal. So far we have, S/N in 92.6 uHz and absolute phase 20:00 to 23:00 19.6 dB +14.5 deg 0.25 fT 23:00 to 02:00 14.5 dB -3.2 deg 0.22 fT 02:00 to 05:00 16.
Hello Alex, Indeed! Wow! Hm... It is hard to belive somehow. These few pixels are not weak at all. Can this be true? About 10 dB in 47 uHz. With such a signal we could even try EbNaut. I did not thin
...i decided to delay the start of the transmission to 08:00 UTC. Maybe this gives a better phase stability over the path and transmission period. 73, Stefan Am 18.04.2017 14:33, schrieb DK7FC: There
Well I thought yesterday that I could see nothing on 6470.005 Hz from that session but looking at my Grabber http://www.g3zjo.talktalk.net/vlfgrabber.htm VLF4 maybe there are a few coherent pixels. N
Here's the complete measurement: S/N in 92.6 uHz, absolute phase, flux density 20:00 to 23:00 19.6 dB +14.5 deg 0.25 fT 23:00 to 02:00 14.5 dB -3.2 deg 0.22 fT 02:00 to 05:00 16.5 dB +16.4 deg 0.18 f
Hi Paul, Thanks for the analysis. Well with 19.8 dB in 92.6 uHz, my currently running transmission is maybe to optimistic. Then we are very very very very close to the limit! http://abelian.org/ebnau
Yes it looks borderline. But the blanker setting I used for the carrier measurements was appropriate for nighttime. I can probably gain a dB or two when I decode the EbNaut by using a daytime thresho
Hello Paul, Something went wrong. The transmission should have stopped at 11:48:16 UTC. But the PSK continues. Obviously i made a mistake. The symbol time is correct, one can also see it by the psk s
I tweaked the blanker and got another 1.5 dB S/N. Ok, the 30 chars didn't decode. I guess it has stopped now if 40 chars. That will be interesting, still possible. Can you confirm it stopped at 12:52
Yes, i confirm, see attachment. 73, Stefan Am 19.04.2017 15:04, schrieb Paul Nicholson: I tweaked the blanker and got another 1.5 dB S/N. Ok, the 30 chars didn't decode. I guess it has stopped now if
OK, copied 40 chars:- "CQ CQ ON THE 46KM BAND DE DK7FC JN49IK K" Carrier Eb/N0: 0.0 dB BER: 33.8 % List rank: 0 Carrier S/N: 23.5 dB in 57.0 uHz Carrier phase: 66.2 degrees Reference phase: constant
Hi Paul, Alex, VLF, Am 19.04.2017 17:55, schrieb Paul Nicholson: OK, copied 40 chars:- "CQ CQ ON THE 46KM BAND DE DK7FC JN49IK K" The message is correct! :-) That's amazing. Now i thought back to 20
Received the ebnaut transmission on 20170419 19:00 UTC 6470.1Hz in Warsaw (text sent offline for verification): found rank 11 ber 4.3510e-01 Eb/N0 -0.1 M -1.023133636e+00 [xx] ps [ 32 -60 -60 -30 -30
On 20/04/2017 10:02, DK7FC wrote: Last night i run another message: f = 6470.100000 Hz Start time: 19.Apr.2017 19:00:00 UTC Symbol period: 30 s Characters: 2 CRC bits: 20 Coding 16K21A Duration: 6h
Hello Alex, Thank you for trying! I guess we will have much better results in November or December this year. But we keep on trying. The days become longer and longer, maybe we can make it during day
Hello Paul, Could you help us by analysing the wav file produced by Alex (.zip file)? I tried to get a decode (the offset between file start and transmission start is 1811.77 seconds) but my PC (RAM)
