[Lowfer] IDing
N1BUG
paul at n1bug.com
Sat Dec 16 10:21:22 EST 2017
I agree about CW IDing.
I can only speak for myself and I am probably not typical. ;-)
When I was monitoring Lowfers last winter, and when I monitor 2200m
now, I always have audio routed to a speaker and turned up just
enough so I can tell if there is anything to hear. If and when there
is I often turn it up a bit more hoping I may catch a CW ID!
Sometimes I do on 2200m. I can't say that I ever heard a Lowfer CW ID.
Actually on 2200m it's a bit tough as there is one station I hear
24/7 and that makes it hard to pick out other audible signals. But I
still try.
73,
Paul N1BUG
On 12/16/2017 10:02 AM, N8OOU wrote:
> Dave,
>
> You make a good point about the CW ID. I do have that mode incorporated
> in my WM Hifer beacon. Since I implemented it a while back, I have had
> at least an equal number of CW reports to Digital reports. With the
> Hifer sending the digital ID at FSK-3 it switches fairly quickly between
> the two.
>
> Incorporating CW into my Lowfer beacon is not hard. I do have a question
> about the timing which is the main reason I don't have it implemented.
>
> I currently send an analog looking graphic ID on the Lowfer followed by
> the digital FSK ID. That takes about 35 minutes to send, then that
> sequence gets repeated..... A CW ID would occur about 35 minutes apart.
>
> Would a listener know to hang on that long to catch an ID? Did the
> propagation window last that long?
>
> With older beacon technology adding an additional mode would be very
> hard to do. With today's hardware it is much easier. I have gotten more
> reports on my Hifer sending CW. Would that also apply to the Lowfer???
>
> What say the group?
More information about the Lowfer
mailing list