Hi Paul, VLF, I changed the subject of the discussion... Am 06.12.2017 22:49, schrieb Paul Nicholson: Forest, Virginia, is reporting Eb/N0 = -7.5dB on the 4 char transmission. That's -38.55 dB in 1Hz
Unfortunately, no sign of the 3 char message at Forest. Eb/N0 measured -26.6 dB, so perhaps yesterday's -7.5 dB was just noise. Random noise has about 1 in 30 chance of hitting -7.5 dB. But I will k
Ah, ignore the last message. I just noticed a mistake I made with the sample rate!!! Forest, Virginia gives Eb/N0 = -4.8 dB on the 3 char message, which is -37.30 dB in 1Hz. Only something like 1 in
Repeating (with apologies) and adding to (see last paragraph: wondering about Forest/Arlington raw data correlation) a recent message on this perhaps more appropriate thread: Based on Marcus' request
I'll just summarise to bring Mike Smith at Forest VA into the loop. Measures Eb/N0 = -7.5dB with cross-correlation at Forest, that's -38.55 dB in 1Hz. Correlates at Eb/N0 = -4.8 dB at Forest, -37.30
You may be lucky but it'll be hard to beat Mike's E-field receiver, it is probably the best in North America and is in a good location. It is very similar to my new E-field rx, AD823 based. Correct,
Paul, Receiver is at 38.915547, -77.124948 8 hours raw data ~ 11 GB if I calculated correctly. OK to use raw data from SpecLab running in Windows? No need for EbNaut? Which program do you want to use
Well, most exciting stuff to read each hour these days. -4.8 dB is better than i expected. 1 character in a single night is in reach! Furthermore i'm running a carrier with 1.2 A antenna current sinc
Hi Jim, Paul, Am 07.12.2017 21:04, schrieb [email protected]: Receiver is at 38.915547, -77.124948 Or FM18KV59AS :-) As Paul suggested, i would agree that recording the audio is the best you can d
That may decode in one attempt if lucky, but likely two transmissions will be needed. If it does decode, then the chance of it being the correct decode from random noise is 0.02 %. Can you run until
45 minutes left before the message starts. I can change to CRC 12 but 08:08 UTC means that about the last 90 minutes are running in daylight here. Let me go to CRC 10, that's 9 hours and 36 minutes.
45 minutes left before the message starts. I can change to CRC 12 but 08:08 UTC means that about the last 90 minutes are running in daylight here. Let me go to CRC 10, that's 9 hours and 36 minutes.
I notice from recent T/A west to east, W4DEX + VO1NA continue with good S/N well into daylight. Also we don't see good S/N before 23:00 or 00:00. The path seems to start late and finish late. Perhaps
Am 07.12.2017 22:55, schrieb Paul Nicholson: I notice from recent T/A west to east, W4DEX + VO1NA continue with good S/N well into daylight. Also we don't see good S/N before 23:00 or 00:00. The path
A couple of American slow VLF-wideband grabbers showing HWU, JXN et al. might come in helpful... Laurence KL7 is seeing JXN strongly over the pole but that's probably too far north to serve as an ind
I just threw the vlf mid speed KL7 snapper back on http://kl7l.com/fast00000.jpg the 17470.1 is on slow00000.jpg it running on the "wrong" soundcard so there are unwanted artifacts - but im a little
Forest decoded '4' from the overnight transmission 21:30 to 07:06, Eb/N0 = +2.2 dB, rank 23. This is a false decode. The correct decode is down at Eb/N0 = -1.3 dB, -39.09 dB in 1Hz. Close, but it's g
OK, that's not ideal. False messages must be avoided. It is problematic with single character messages. At least the experienced RX station operator would have doubts with this result and interprete
Stefan and Paul, All up and running per details of your suggestions, thank you. Started 192 ksps .wav file at 1500 UT. Spectrogram integration time ~ 12 hours, centered at 17470.1000 Hz Antenna beari
