[Lowfer] QRSS Alternative?

[lowfer@mailman.qth.net]

Hello Folks,


Below is a copy of an Email that I sent to ALberto.
I am sending it along to reflector to see if it will generate any comments.

Also I have a small JPEG of beacon "USA"  that is an actual capture that I
can send to anyone interested in it.

I also believe that Larry has copied my signal with less about 75 milliwatts




Hello Alberto,

First I would to thank you for the fine programs you have produced for the
ham community.  Further I believe they have gone a long way toward
increasing the experimentation in the LF bands, especially here in the
states where part 15 rules hold us to a 1 watt limit.

I hope you will find time to read this in your busy schedule and perhaps
make a few comments.

ARGO is a fantastic tool for receiving slow CW.  There are many obvious
advantages to sending QRSS CW in LF.
A problem that I see is that much of the time the carrier is in the off
mode.

Looking forward to the time when the US gets a ham allocation in the
vicinity of 137 Khz my beacon ID would need to be my callsign.
To send my call sign  W1VLF  at QRSS 60 it will take 1 hour.

Much of that 1 hour is idle time when the carrier is off.   To shorten the
time I thought using  slightly different frequencies to represent a dot and
a dash.

The problem that then presents itself is if there is a situation where there
is multiple dots or dashes in succession it may be difficult to distinguish
between them.

Using QRSS and ARGO I have been experimenting with something that I would
greatly appreciate your comments on.

It consists of using 5 seperate frequences  .2 Hz apart IE  185.298.0,
298.2,   298.4,   298.6,   298.8 Khz.

The coding scheme goes like this.  There is only a few rules. The first dot
or dash always uses the freq. furthest from the center.  The next dot or
dash would use the only other freq.  The space would be represented by a
element at the freq 185.298.8 Khz


                                    W                                    1

Space 185.298.8                  -----
Dash 185.298.6       -----                      -----       -----
Dash 185.298.4              -----                      -----       -----
Dot  185.298.2
Dot   185.298.0 ------                    -----


Above I have started to send my callsing but have not finished since this
all you probably need for clarity.
With a few simple rules and a little organic processor power, it seems to me
that a lot of time could be saved....  or used to incorporate longer
integration time.

I am sure someone has come up with this before, but it is new to me.  I have
send this code and could email you a ARGO capture if you like.

So Alberto...  Do you think there is any merit in pursue this avenue or
should I just stick with normal QRSS.

I did a little math.  Assuming 60 sec element lengths, 60 sec spaces between
elements,  dashes equal 3 element lengths and spaces also equal 3 element
lengths

The time needed to send W1VLF is 1 hour  or 60 element lengths
Using the above format the time is reduced to 27 minutes  using the same
element length.

This means an operator could either send his call 2 times as fast as
QRSS(depending on the dot/dash ratio) or he could double the integration
time for increased SNR.

Please comment Alberto?
Thank you for your time

Paul Cianciolo
W1VLF
Beacon  " USA"  185.298.00 Khz