[Lowfer] Lowfer TAG?

[John Hamer]

After reading all of this and glancing over the wolf specification, I had
an idea. What if you had a simple program similar to argo that would let
you set the total message length you were trying to receive in time.  So,
it would scroll the waterfall like normal until the set time was met, then
it would start the waterfall from the beginning,  but instead of
overwriting the previous waterfall,  would average them as it swept across.
As more and more averages passed, you should really start to see weak
messages come through.  This would not have error detection or get to take
advantage of multiple frequencies, but it could allow people to receive
stations they couldn't before.  And, stations wouldn't have to slow down
more to get farther receptions. Does anything like that exist? Plus, it
gives you more sliders to play with.

I think the neat thing about lowfers using qrss is how it makes it easy to
build your own equipment. Converting a tone output from a computer to a
transmittable signal is not the most straight forward thing. I was
interested in truly understanding how radio worked and that's why I made a
lowfer station. Where else are you going to build a simple transmitter
license free and have a network of people watching to see if it works.

John Hamer


On Tue, Oct 20, 2020, 9:37 PM John Andrews <w1tag at charter.net> wrote:

> Jay,
>
> Well, thanks. I should have been more clear in the original post that the
> equipment would have to run on its own for 6 months. Add to that - I have
> one week to pull this off. The existing transmitter was built in 2008,
> primarily for WOLF. If you recall, this was a bpsk mode at a data rate of
> 10 bits/second, with the bit timing being very critical. So I derived the
> timing from a divider chain off of the very accurate 10MHz oven controlled
> oscillator I was using. Worked perfectly. And like Chicago, it doesn’t care
> what time it is. I threw in the QRSS60 option as an afterthought, and then
> began using it after WOLF fell out of favor.
>
> Since the transmitter frequency comes from a DDS, the microcontroller
> could be reprogrammed to do the FSK needed for the newer modes, sending a
> static message. The timing and clock-awareness could be derived from GPS
> without involving a computer or the Internet. Too much of a project for a
> week.
>
> The real reason for putting the beacon back on is to keep track of the
> power at the camp. In the winter, my wife is addicted to the outside web
> cam at the cottage, and it depends on power and Internet. When the camera
> goes down, it’s nice to know if the cause is power-related.
>
> And it’s nice to sometimes do radio stuff that’s not Internet-dependent.
>
> John, W1TAG
>
>
> >
> > This list hosted by: http://www.qsl.net
> > Please help support this email list: http://www.qsl.net/donate.html
>
> ______________________________________________________________
> Lowfer mailing list
> Home: http://mailman.qth.net/mailman/listinfo/lowfer
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:Lowfer at mailman.qth.net
> Post must be less than 50KB total for message plus attachment!
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html