AW: [Meteor-Scatter] Perseids and operating procedures!

Thu, 15 Aug 2002 13:53:29 +0200

Hi,

I just have to react on the below :

Ad 1. I fully agree that QSO info should not being exchanged in the cluster;
I do see however
an advantage on self spotting - if not using the "calling" frequency.

The use of the convers channel is not available at all times, and thanks to
murphy, especially not
if you need it most, like for example during dx-peditions. The delay on the
pure packet network is too
high to meaningfully use it. So we would need the cluster for self spotting
CQ's, were timing is not that important only.

I fully agree that there are several means of using the internet, which are
by far prefered. (e-mail, chat cahnnels like
ON4ANT's or ww convers etc)

Ad 2. QTF depending frequencies. I still see an advantage here; it will
simply avoid listening
periods being spoiled by other ones calling. Most definietly on the
"calling" QRG

Ad 3. Fully agree here; there is a section of the band typically used for
dx; it is a good proposition to limit WSJT
from 144220 (or whatever) upwards. And indeed, bandwidth segmentation is
another way of defining a bandplan, but also
a way of defining a bandplan is by the use. Actually this is already done
more or less, as the beacon band is a
typical application and so are the EME segments; the repeater segments and
the sat segments. (the latter one being mode independant !)

Ad 4. Whether the changes were good or bad is not relevant today ; at that
time nobody could have foreseen the development
of JT44 and FSK441. So I would tend indeed for application dependant band
planning. One could agrue a lot about the applications
used (I don't like APRS for example) but we still will have to accept that
there are other users as well; so leave the lowest 500 KHz
to us, the DX-ers and leave it up to the DX-ers to make a bandplan for that
segment.

But as you stated correct, ...for Christ sake, keep out of the beacon band !

73 - franz

-> -----Ursprungliche Nachricht-----
-> Von: [email protected]
-> [mailto:[email protected]]Im Auftrag von Ulrich
-> Hilsinger
-> Gesendet: Donnerstag, 15. August 2002 12:26
-> An: [email protected]
-> Betreff: Re: [Meteor-Scatter] Perseids and operating procedures!
->
->
-> Hello,
->
-> just another few words about this subject and some ideas about the
-> statements which I've seen yet.
->
->
-> 1. Usage of DX-Cluster
-> Even if I'm not a friend of self-spotting, during times of low activity
-> this could be usefull. If we find a good solution for random QSOs, we
-> don't need selfspotting during higher activity at all.
-> Another thing should be strictly stopped: Exchanging QSO informations on
-> the cluster. Even if you just tell someone "I'm calling you", that's too
-> much information. That's the same with many others things which are
-> exchanged via the cluster. The information one needs still rrr or a
-> report, etc, may NEVER be transmitted on another way than within the QSO
-> with the usual QSO procedure. Otherwise, QSOs are not complete. The
-> actual chaos on the cluster is one of the main reasons why I do not make
-> any QSO in WSJT.
-> Also, one should try to make skeds not by using ann/full, which is very
-> enoying to all other cluster users. There are a lot of other
-> possibilities: By e-mail, by using the VHF net on 20m (14345kHz), or by
-> using the digital VHF net (WWC channel 14345). Look at
-> www.meteorscatter.net, you'll find a big list of e-mails there. Of
-> course, this hints are valid for all modes - SSB, HSCW and WSJT.
->
->
-> 2. QTF-dependent calling frequencies
-> They don't help getting rid of the "frequency already in use"-problem.
-> The risk to be on a busy frequency is even higher than with a letter
-> system
-> The letter system is used with much success in CW for many years now,
-> why not just adopt it, perhaps with some minor modifications ?
->
->
-> 3. Skeds everywhere in the band
-> This might work well in areas which see only a moderate activity on
-> Meteorscatter.
-> In central europe, we have hundreds of stations within tropo range, so
-> it is dangerous to have too many non synchronous transmissions at nearby
-> frequencies (one has to consider the intermodulation spectrum of typical
-> ham transmitters, hi). Nevertheless I can imagine to make skeds just
-> down to let's say 144.240, but not below. I don't think that HSCW and
-> SSB will die out, just because many people don't want to miss the fact
-> they can decode a burst themself by ear. For them, MS is more than only
-> squarehunting, it's also the fun to listen into the signals.
-> So, one should at least not use WSJT near to the SSB random area and
-> within the CW subband.
-> Of course, there is a need to integrate new digital modes - I think the
-> future will bring us a bandplan which is more depending on bandwidth and
-> signal levels, not on modes itself. For example 144.150-144.400 could be
-> for modes with approx. SSB bandwidth (WSJT, SSB, MT63, SSTV, etc etc),
-> 144.000 - 144.150 could be for CW, PSK31, etc). Of course with some
-> extra regulations in order to prevent us from (f.ex.) MT63 at 144.300,
-> PSK31 at 144.050, etc.
->
->
-> 4. Extra segments such as beacon band
-> Please don't start doing QSOs in the beacon band. Many people observe
-> the beacon band to get an idea about the MS condx which is not
-> influenced by activity, power etc. beacons are there all the time with
-> almost the same configuration, so they are an ideal indicator for MS
-> activity. Additionally, just during Perseids we had some tropo in parts
-> of Europe, which has been found partially by the help of beacons !
->
-> Nowadays, we see that it was an error to kill 100 kHz of the Region 1
-> weak signal subband in 1997... Within the last few years, we've seen a
-> lot of new digital modes which now seek for spectrum. Unfortunately,
-> also the 144.500 - 144.9875 subband has been flooded with mostly
-> channelized traffic (Packet, chats, etc), so it would be difficult to
-> get some frequencies there. Nevertheless: In the whole allmode segment,
-> WSJT is allowed, and as it is a digital mode, even in the digimode
-> segment 144.800-144.990 MHz....
->
->
-> 73 & good DX,
-> Ulrich DH0GHU
-> dh0ghu@db0cz.#bw.deu.eu
-> [email protected]
-> http://www.dh0ghu.de/
-> _______________________________________________
-> Meteor-Scatter mailing list
-> [email protected]
-> http://mailman.qth.net/mailman/listinfo/meteor-scatter
->