[Lowfer] lowFERs on 10-29-20

[Garry]

Jay,

The earliest attempt I saved in 2010 was Sept 30 and it failed to 
produce any decodes of TAG. However, Sept 17, 2009 was successful for 
one of the 32 96 second intervals:

2013-09-17 06:53:50 >WOLF10  -r 11100.211 -f 400 -t 1.0 -w 0.0000 -ut
06:54:14 f: 0.772 a:-0.0 dp: 77.6 ci: 3 cj:163 UHX8XCK.Y4QDUVY ?
06:54:38 f:-0.417 a: 0.9 dp: 74.1 ci: 6 cj:162 8AXIPWM.CYFUIHQ ?
06:55:26 f:-0.601 a: 0.3 dp: 71.4 ci:12 cj:245 UOL2PF4WDA265R8 ?

06:57:02 f:-0.654 pm:5.805 jm:739 q:-13.7 -7.6 HFNBI W8 OIYYAQ ?

...

07:24:14 f:-0.010 pm:26.66 jm:206 q: -2.5 -7.8 Z1G???JI54N3QMA ?

07:25:50 f:-0.010 pm:26.73 jm:206 q: -2.3 -5.3 TAG RAYMOND ME  -

...

07:46:38 f:-0.010 pm:51.24 jm:206 q: -0.1 -3.7 TAG RAYMOND ME  -

An attempt as late as Oct 31, 2011 failed but at least it converged to 
and stayed on the correct frequency  after only about 11 minutes.Typical 
December decodes over several years averaged around 15 minutes to 
initial decode.

I'm not sure when I converted my sdr-iq receiver to run off an external 
gps-referenced clock. It might have been after TAG switched to QRSS 
transmissions. But I did always calibrate using GPS-referenced 10 MHz 
and 100 kHz signals so when decodes occurred they had frequency errors 
of 0.020 Hz or less and the error remained stable over time.I believe 
all the receptions were made with a rooftop eprobe for the antenna.

I'll keep trying and hopefully propagation will improve as winter kicks 
in. And of course a little more ERP is always helpful.

73, Garry, K3SIW