|
Thanks for that Markus
That info could be gathered at the RX
stations and shared via the web beacon , but
would only be of use is the 'audio'
tx drive was used ..
For such a short tx time , 4 mins of
'carrier' and anything over 2 mins
needed for a decode , OP8 seems to
be producing some very good results , unless
there is some 'flutter' , which the
shorter cycle is able to make use of ? if
nothing else , the power bill is 25% of
op32 !
W1VD is also showing on the PSK map
, Gus is running higher power than at
the start , so may be W1VD is in range ?
73-G,
Sent: Wednesday, September 18, 2013 9:15 PM
Subject: Re: LF: VO1NA Op-32
Yes op-8 would have been in easy reach. This
morning, Joe's dashes were well discernible even in the 0.7 Hz grabber window.
Having said that, my personal
preference regarding overnight beaconing is more towards "the slower the
better" ;-) In the morning I'd rather be greeted
by 10 really deep detections than by a long list of spots with
intermediate sensitivity.
As for frequency, using 137650 exactly might
not be ideal, as observers in East Europe would likely be affected by the
Russian Loran / Chayka chain. Actually here in Central Europe the 6.25 Hz
multiples reappeared today when Slonim (the most westerly station in the
chain) came back on air after several weeks outage. Staying away from
the Loran lines by a Hz or so will avoid that problem.
Best 73,
Markus (DF6NM)
Sent: Wednesday, September 18, 2013 5:36 PM
Subject: Re: LF: VO1NA Op-32
Joe,
Looking at the psk-map
, Its quite possible , all the monitors where
looking for OP8 signals ve7bdq
<> we2xpq is also showing as OP8
as
well
No reason why OP8 should not decode from
you , just need to qsy
to
the OP8 centre qrg 137.650 KHz
73
-G,
|
