+10Mar01=======================================================================
+1. minor changes to the admin manual to reflect differences in distibutions
+thanks to pa3ezl (g0vgs)
+2. add (finally) the first draft of the usermanual (g0vgs)
05Mar01=======================================================================
1. do some major surgery on the connect logic to shorten the possibility of
duplicate connects happening
perl -d cluster.pl
It will interrupt the cluster just after the debug command has finished.
+
=== 0^DIRECTORY^List messages
=== 0^DIRECTORY ALL^List all messages
=== 0^DIRECTORY OWN^List your own messages
</PRE>
</CODE></BLOCKQUOTE>
<P>
+<P>This line works fine for RedHat and SuSE distributions. The line required for
+Slackware distributions is slightly different. My thanks to Aurelio, PA3EZL for
+this information.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
<P>This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
it should it crash for any reason.
<P>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Introduction</TITLE>
+ <LINK HREF="usermanual-2.html" REL=next>
+
+ <LINK HREF="usermanual.html#toc1" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-2.html">Next</A>
+Previous
+<A HREF="usermanual.html#toc1">Contents</A>
+<HR>
+<H2><A NAME="s1">1. Introduction</A></H2>
+
+<H2><A NAME="ss1.1">1.1 What is a DX Cluster?</A>
+</H2>
+
+<P>A DX Cluster is a packet node where DX chasers on any band or mode can
+post rare or interesting stations that they have worked or heard. Of
+course other people are doing the same thing too, so you can find new
+DX as well as telling others about the stations you have worked.
+Clusters tend to be linked to each other so that the amount of people
+using them is increased, thereby increasing the amount of posted DX.
+Other information can be found on clusters such as on-line call books,
+mail etc. You can talk to other stations connected to the cluster
+network too, in real time, whether at the node you are logged into or
+on another node connected to the network. You can also use converse
+mode, where several stations can talk to each other in the same way.
+Of course, the DX is still posted to you all the while!
+<P>
+<H2><A NAME="ss1.2">1.2 So what is DXSpider?</A>
+</H2>
+
+<P>PacketCluster nodes have been around since roughly 1985. The original
+PacketCluster idea came from Dick Newell, AK1A, and ran under DOS.
+In about 1992 Dick stopped the development of the PacketCluster
+software for amateur radio. Many systems are still using this
+relatively old DOS software today.
+<P>There are several new compatible cluster programs around now,
+including DXSpider. DXSpider is a clone of PacketCluster software that runs
+under the Linux operating system. Linux is fast becoming the choice
+for amateur radio stations because of it's flexibility, reliability
+and the lack of the memory limitations of DOS. Linux supports
+multitasking and is also multiuser. It has support for AX25, ROSE,
+NetROM and TCPIP built in, making it the ideal choice for amateur
+radio. It is also totally free!
+<P>DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
+exercise in perl programming. It has developed rapidly and today is a
+very powerful cluster program. It was designed to be totally compatible
+with the AK1A program, although several commands have been extended to
+try and improve functionality.
+<P>This manual is designed to help you become familiar with the commands
+that DXSpider supports and to help you get the best from the program so
+you can enjoy working that rare DX! As DXSpider is being improved all the
+time, commands will be added as time goes by, so make sure you have
+the most upto date version of this manual. The latest version will
+always be included with the cluster program so if you are unsure, simply
+ask your sysop. The manual will also be available on the wesite.
+<P>
+<P>
+<HR>
+<A HREF="usermanual-2.html">Next</A>
+Previous
+<A HREF="usermanual.html#toc1">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Filtering (From version 1.45)</TITLE>
+ <LINK HREF="usermanual-11.html" REL=next>
+ <LINK HREF="usermanual-9.html" REL=previous>
+ <LINK HREF="usermanual.html#toc10" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-11.html">Next</A>
+<A HREF="usermanual-9.html">Previous</A>
+<A HREF="usermanual.html#toc10">Contents</A>
+<HR>
+<H2><A NAME="s10">10. Filtering (From version 1.45)</A></H2>
+
+<H2><A NAME="ss10.1">10.1 General filter rules</A>
+</H2>
+
+<P>Upto v1.44 it was not possible for the user to set their own filters. From
+v1.45 though that has all changed. It is now possible to set filters for just
+about anything you wish. If you have just updated from an older version of
+DXSpider you will need to update your new filters. You do not need to do
+anything with your old filters, they will be renamed as you update.
+<P>
+<P>There are 3 basic commands involved in setting and manipulating filters. These
+are <EM>accept</EM>, <EM>reject</EM> and <EM>clear</EM>. First we will look
+generally at filtering. There are a number of things you can filter in the
+DXSpider system. They all use the same general mechanism.
+<P>
+<P>In general terms you can create a 'reject' or an 'accept' filter which can have
+up to 10 lines in it. You do this using, for example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+accept/spots .....
+reject/spots .....
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>where ..... are the specific commands for that type of filter. There are
+filters for spots, wwv, announce, wcy and (for sysops) connects. See each
+different accept or reject command reference for more details.
+<P>There is also a command to clear out one or more lines in a filter. They are ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+clear/spots 1
+clear/spots all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>There is clear/xxxx command for each type of filter.
+<P>
+<P>and you can check that your filters have worked by the command ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+show/filter
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>For now we are going to use spots for the examples, but you can apply the same
+principles to all types of filter.
+<P>
+<H2><A NAME="ss10.2">10.2 Types of filter</A>
+</H2>
+
+<P>There are two main types of filter, <EM>accept</EM> or <EM>reject</EM>. You
+can use either to achieve the result you want dependent on your own preference
+and which is more simple to do. It is pointless writing 8 lines of reject
+filters when 1 accept filter would do the same thing! Each filter has 10
+lines (of any length) which are tried in order. If a line matches then the
+action you have specified is taken (ie reject means ignore it and accept
+means take it)
+<P>
+<P>If you specify reject filters, then any lines that arrive that match the filter
+will be dumped but all else will be accepted. If you use an accept filter,
+then ONLY the lines in the filter will be accepted and all else will be dumped.
+For example if you have a single line <EM>accept</EM> filter ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>then you will <EM>ONLY</EM> get VHF spots <EM>from</EM> or <EM>to</EM> CQ zones
+14, 15 and 16.
+<P>
+<P>If you set a reject filter like this ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reject/spots on hf/cw
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Then you will get everything <EM>EXCEPT</EM> HF CW spots. You could make this
+single filter even more flexible. For example, if you are interested in IOTA
+and will work it even on CW even though normally you are not interested in
+CW, then you could say ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reject/spots on hf/cw and not info iota
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>But in that case you might only be interested in iota and say:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+accept/spots not on hf/cw or info iota
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>which achieves exactly the same thing. You should choose one or the other
+until you are comfortable with the way it works. You can mix them if you
+wish (actually you can have an accept AND a reject on the same line) but
+don't attempt this until you are sure you know what you are doing!
+<P>
+<P>You can arrange your filter lines into logical units, either for your own
+understanding or simply convenience. Here is an example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reject/spots 1 on hf/cw
+reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>What this does is to ignore all HF CW spots and also rejects any spots on VHF
+which don't either originate or spot someone in Europe.
+<P>
+<P>This is an example where you would use a line number (1 and 2 in this case), if
+you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
+This make it easier to see just what filters you have set. It also makes it
+more simple to remove individual filters, during a contest for example.
+<P>
+<P>You will notice in the above example that the second line has brackets. Look
+at the line logically. You can see there are 2 separate sections to it. We
+are saying reject spots that are VHF or above <EM>APART</EM> from those in
+zones 14, 15 and 16 (either spotted there or originated there). If you did
+not have the brackets to separate the 2 sections, then Spider would read it
+logically from the front and see a different expression entirely ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The simple way to remember this is, if you use OR - use brackets. Whilst we are
+here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'.
+<P>As mentioned earlier, setting several filters can be more flexible than
+simply setting one complex one. Doing it in this way means that if you want
+to alter your filter you can just redefine or remove one or more lines of it or
+one line. For example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reject/spots 1 on hf/ssb
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>would redefine our earlier example, or
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+clear/spots 1
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To remove all the filter lines in the spot filter ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+clear/spots all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss10.3">10.3 Filter options</A>
+</H2>
+
+<P>You can filter in several different ways. The options are listed in the
+various helpfiles for accept, reject and filter.
+<P>
+<H2><A NAME="ss10.4">10.4 Advanced filtering</A>
+</H2>
+
+<P>Once you are happy with the results you get, you may like to experiment.
+<P>
+<P>The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
+can be written with a mixed filter, for example ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+rej/spot on hf/cw
+acc/spot on 0/30000
+acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Note that the first filter has not been specified with a number. This
+will automatically be assumed to be number 1. In this case, we have
+said <EM>reject all HF spots in the CW section of the bands but accept
+all others at HF. Also accept anything in VHF and above spotted in or
+by operators in the zones 14, 15 and 16</EM>. Each filter slot actually
+has a 'reject' slot and an 'accept' slot. The reject slot is executed
+BEFORE the accept slot.
+<P>
+<P>It was mentioned earlier that after a reject test that doesn't match, the
+default for following tests is 'accept', the reverse is true for 'accept'.
+In the example what happens is that the reject is executed first, any non
+hf/cw spot is passed to the accept line, which lets through everything
+else on HF. The next filter line lets through just VHF/UHF spots from EU.
+<P>
+<P>
+<HR>
+<A HREF="usermanual-11.html">Next</A>
+<A HREF="usermanual-9.html">Previous</A>
+<A HREF="usermanual.html#toc10">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Hints, tips and common questions.</TITLE>
+ <LINK HREF="usermanual-12.html" REL=next>
+ <LINK HREF="usermanual-10.html" REL=previous>
+ <LINK HREF="usermanual.html#toc11" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-12.html">Next</A>
+<A HREF="usermanual-10.html">Previous</A>
+<A HREF="usermanual.html#toc11">Contents</A>
+<HR>
+<H2><A NAME="s11">11. Hints, tips and common questions.</A></H2>
+
+<P><B>Q.</B>These commands seem very long! Can I shorten them?
+<P><B>A.</B>Of course you can and the usual abbreviations work. If you
+are unsure, try it.
+<P><B>Q.</B>I am not sure if this command is correct. Can I cause any
+harm if I try it?
+<P><B>A.</B>Do not be afraid to try a command to see if it will work,
+at the worst you will get an error message. If you require any
+help on a command, just type help followed by the command you
+want help on. Look at the "DXSpider Command Reference" section to see
+what help can be found.
+<P><B>Q.</B>How should I use the announce command?
+<P><B>A.</B>With respect. Use the command by all means, but please
+only use the "full" extension if absolutely necessary. It can
+create a LOT of messages passing between clusters.
+<P><B>Q.</B>I like to be working in the shack while logged into the
+cluster but I can't be looking at the screen all the time. How
+can I be alerted when anything happens?
+<P><B>A.</B>Use the <B>SET/BEEP</B> command. You can find information
+on this in the "DXSpider Command Reference" section.
+<P><B>Q.</B>I keep getting disconnected from the cluster, what is
+happening and how can I stop it?
+<P><B>Q.</B>I got disconnected from the cluster and now I can't log
+back in again. What is wrong?
+<P><B>A.</B>Probably the cluster thinks you are still logged on and
+will not let you reconnect using the same call to prevent loops.
+Try logging on again adding an ssid to your callsign as DXSpider
+treats G0YLM and G0YLM-1 as different users.
+<P><B>Q.</B>I notice that all the commands are shown in lower case in
+the main section of this manual, but in upper case in the "DXSpider
+Command Reference" section. Why is that?
+<P><B>Q.</B>How do I know if I have got the latest version of this
+user manual?
+<P><B>A.</B>The latest and greatest will always be on the Website. It will
+also be included with every release of DXSpider. As always, if unsure,
+ask your sysop what version number is the latest.
+<P>
+<HR>
+<A HREF="usermanual-12.html">Next</A>
+<A HREF="usermanual-10.html">Previous</A>
+<A HREF="usermanual.html#toc11">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : The DXSpider command reference</TITLE>
+ <LINK HREF="usermanual-11.html" REL=previous>
+ <LINK HREF="usermanual.html#toc12" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+Next
+<A HREF="usermanual-11.html">Previous</A>
+<A HREF="usermanual.html#toc12">Contents</A>
+<HR>
+<H2><A NAME="s12">12. The DXSpider command reference</A></H2>
+
+<P>Below is a complete list of commands available from the cluster prompt.
+These are listed below in alphabetical order.
+<P>
+<H2><A NAME="ss12.1">12.1 accept/announce</A>
+</H2>
+
+<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
+line for announce</CODE>
+<P>
+<P>Create an 'accept this announce' line for a filter.
+<P>An accept filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann dest 6MUK
+ acc/ann 2 by_zone 14,15,16
+ (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>or
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This filter would only allow announces that were posted buy UK stations.
+You can use the tag 'all' to accept everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/ann all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss12.2">12.2 accept/spots </A>
+</H2>
+
+<P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter line for spots</CODE>
+<P>
+<P>Create an 'accept this spot' line for a filter.
+<P>
+<P>An accept filter line means that if the spot matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: freq HF (but don't get
+too hung up about that)
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to accept everything, eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 3 all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss12.3">12.3 accept/wcy </A>
+</H2>
+
+<P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+<P>This command is really provided for future use.
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss12.4">12.4 accept/wwv </A>
+</H2>
+
+<P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>for example
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ accept/wwv by_zone 4
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss12.5">12.5 announce </A>
+</H2>
+
+<P><CODE><B>announce <text></B> Send an announcement to local users</CODE>
+<P>
+<P>Send an announcement to LOCAL users only, where <text> is the text
+of the announcement you wish to broadcast
+<P>
+<H2><A NAME="ss12.6">12.6 announce full </A>
+</H2>
+
+<P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE>
+<P>
+<P>This command will send your announcement across the whole cluster
+network.
+<P>
+<H2><A NAME="ss12.7">12.7 apropos </A>
+</H2>
+
+<P><CODE><B>apropos <string></B> Search the help database</CODE>
+<P>
+<P>Search the help database for <string> (it isn't case sensitive),
+and print the names of all the commands that may be relevant.
+<P>
+<H2><A NAME="ss12.8">12.8 bye </A>
+</H2>
+
+<P><CODE><B>bye</B> Exit from the cluster</CODE>
+<P>
+<P>This will disconnect you from the cluster
+<P>
+<H2><A NAME="ss12.9">12.9 clear/spots </A>
+</H2>
+
+<P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE>
+<P>
+<P>This command allows you to clear (remove) a line in a spot filter or to
+remove the whole filter.
+<P>If you have a filter:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>and you say:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ clear/spot 1
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>you will be left with:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>If you do:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ clear/spot all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>the filter will be completely removed.
+<P>
+<H2><A NAME="ss12.10">12.10 dbavail </A>
+</H2>
+
+<P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE>
+<P>
+<P>The title says it all really, this command lists all the databases defined
+in the system. It is also aliased to SHOW/COMMAND.
+<P>
+<H2><A NAME="ss12.11">12.11 dbshow </A>
+</H2>
+
+<P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE>
+<P>
+<P>This is the generic user interface to the database to the database system.
+It is expected that the sysop will add an entry to the local Aliases file
+so that users can use the more familiar AK1A style of enquiry such as:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/BUCK G1TLH
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but if he hasn't and the database really does exist (use DBAVAIL or
+SHOW/COMMAND to find out) you can do the same thing with:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DBSHOW buck G1TLH
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.12">12.12 directory </A>
+</H2>
+
+<P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
+<B>directory own</B> List your own messages<BR>
+<B>directory new</B> List all new messages<BR>
+<B>directory to <call></B> List all messages to <call><BR>
+<B>directory from <call></B> List all messages from <call><BR>
+<B>directory subject <string></B> List all messages with <string> in subject<BR>
+<B>directory <nn></B> List last <nn> messages<BR>
+<B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE>
+<P>
+<P>List the messages in the messages directory.
+<P>If there is a 'p' one space after the message number then it is a
+personal message. If there is a '-' between the message number and the
+'p' then this indicates that the message has been read.
+<P>You can use shell escape characters such as '*' and '?' in the <call>
+fields.
+<P>You can combine some of the various directory commands together eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DIR TO G1TLH 5
+or
+ DIR SUBJECT IOTA 200-250
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can abbreviate all the commands to one letter and use ak1a syntax:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DIR/T G1* 10
+ DIR/S QSL 10-100 5
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.13">12.13 dx </A>
+</H2>
+
+<P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE>
+<P>
+<P>This is how you send a DX Spot to other users. You can, in fact, now
+enter the <freq> and the <call> either way round.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX FR0G 144.600
+ DX 144.600 FR0G
+ DX 144600 FR0G
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will all give the same result. You can add some remarks to the end
+of the command and they will be added to the spot.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX FR0G 144600 this is a test
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can credit someone else by saying:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The <freq> is compared against the available bands set up in the
+cluster. See SHOW/BANDS for more information.
+<P>
+<H2><A NAME="ss12.14">12.14 help </A>
+</H2>
+
+<P><CODE><B>help <cmd></B> Get help on a command</CODE>
+<P>
+<P>All commands can be abbreviated, so SHOW/DX can be abbreviated
+to SH/DX, ANNOUNCE can be shortened to AN and so on.
+<P>Look at the APROPOS <string> command which will search the help database
+for the <string> you specify and give you a list of likely commands
+to look at with HELP.
+<P>
+<H2><A NAME="ss12.15">12.15 kill </A>
+</H2>
+
+<P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE>
+<P>
+<P>Delete a message from the local system. You will only be able to
+delete messages that you have originated or been sent (unless you are
+the sysop).
+<P>
+<H2><A NAME="ss12.16">12.16 links </A>
+</H2>
+
+<P><CODE><B>links</B> Show which nodes are physically connected</CODE>
+<P>
+<P>This is a quick listing that shows which links are connected and
+some information about them. See WHO for a list of all connections.
+<P>
+<H2><A NAME="ss12.17">12.17 read </A>
+</H2>
+
+<P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
+<B>read <msgno></B> Read the specified message<BR></CODE>
+<P>
+<P>You can read any messages that are sent as 'non-personal' and also any
+message either sent by or sent to your callsign.
+<P>
+<H2><A NAME="ss12.18">12.18 reject/announce</A>
+</H2>
+
+<P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
+for announce</CODE>
+<P>
+<P>Create an 'reject this announce' line for a filter.
+<P>An reject filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/ann by_zone 14,15,16 and not by G,M,2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to reject everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/ann all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss12.19">12.19 reject/spots </A>
+</H2>
+
+<P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE>
+<P>
+<P>Create a 'reject this spot' line for a filter.
+<P>A reject filter line means that if the spot matches this filter it is
+dumped (not passed on). See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+<P>You can use any of the following things in this line:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: on HF (but don't get
+too hung up about that)
+<P>some examples:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can use the tag 'all' to reject everything eg:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ rej/spot 3 all
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>but this probably for advanced users...
+<P>
+<H2><A NAME="ss12.20">12.20 reject/wcy </A>
+</H2>
+
+<P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+<P>This command is really provided for future use.
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss12.21">12.21 reject/wwv </A>
+</H2>
+
+<P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE>
+<P>
+<P>It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>for example
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ reject/wwv by_zone 14,15,16
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+<P>See HELP FILTER for information.
+<P>
+<H2><A NAME="ss12.22">12.22 reply </A>
+</H2>
+
+<P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
+<B>reply <msgno></B> Reply (privately) to the specified message<BR>
+<B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
+<B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
+message<BR>
+<B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE>
+<P>
+<P>You can reply to a message and the subject will automatically have
+"Re:" inserted in front of it, if it isn't already present.
+<P>You can also use all the extra qualifiers such as RR, PRIVATE,
+NOPRIVATE, B that you can use with the SEND command (see SEND
+for further details)
+<P>
+<H2><A NAME="ss12.23">12.23 send </A>
+</H2>
+
+<P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
+<B>send RR <call></B> Send a message and ask for a read receipt<BR>
+<B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
+<B>send PRIVATE <call></B> Send a personal message<BR>
+<B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE>
+<P>
+<P>All the SEND commands will create a message which will be sent either to
+an individual callsign or to one of the 'bulletin' addresses.
+<P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
+it will mark the message as personal and send it to the cluster node that
+that callsign is connected to.
+<P>You can have more than one callsign in all of the SEND commands.
+<P>You can have multiple qualifiers so that you can have for example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>which should send a copy of message 123 to G1TLH and G0RDI and you will
+receive a read receipt when they have read the message.
+<P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
+SP is an alias for SEND PRIVATE
+<P>
+<H2><A NAME="ss12.24">12.24 set/address </A>
+</H2>
+
+<P><CODE><B>set/address <your_address></B> Record your postal address</CODE>
+<P>
+<P>Literally, record your address details on the cluster.
+<P>
+<H2><A NAME="ss12.25">12.25 set/announce </A>
+</H2>
+
+<P><CODE><B>set/announce</B> Allow announce messages</CODE>
+<P>
+<P>Allow announce messages to arrive at your terminal.
+<P>
+<H2><A NAME="ss12.26">12.26 set/beep </A>
+</H2>
+
+<P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE>
+<P>
+<P>Add a beep to DX and other terminal messages.
+<P>
+<H2><A NAME="ss12.27">12.27 set/dx </A>
+</H2>
+
+<P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE>
+<P>
+<P>You can stop DX messages with the <EM>unset/dx</EM> command
+<P>
+<H2><A NAME="ss12.28">12.28 set/dxgrid</A>
+</H2>
+
+<P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE>
+<P>
+<P>Some logging programs do not like the additional information at
+the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
+command to remove the grid squares.
+<P>
+<H2><A NAME="ss12.29">12.29 set/echo </A>
+</H2>
+
+<P><CODE><B>set/echo</B> Make the cluster echo your input</CODE>
+<P>
+<P>If you are connected via a telnet session, different implimentations
+of telnet handle echo differently depending on whether you are
+connected via port 23 or some other port. You can use this command
+to change the setting appropriately.
+<P>You can remove the echo with the <EM>unset/echo</EM> command
+<P>The setting is stored in your user profile.
+<P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+<P>
+<H2><A NAME="ss12.30">12.30 set/here</A>
+</H2>
+
+<P><CODE><B>set/here</B> Set the here flag</CODE>
+<P>
+<P>Let others on the cluster know you are here by only displaying your
+callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
+command to let people know you are away. This simply puts brackets
+around your callsign to indicate you are not available.
+<P>
+<H2><A NAME="ss12.31">12.31 set/homenode </A>
+</H2>
+
+<P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE>
+<P>
+<P>Tell the cluster system where you normally connect to. Any Messages sent
+to you will normally find their way there should you not be connected.
+eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/HOMENODE gb7djk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.32">12.32 set/language </A>
+</H2>
+
+<P><CODE><B>set/language <language></B> Set the language you wish to use</CODE>
+<P>
+<P>You can select the language that you want the cluster to use. Currently
+the languages available are <EM>en</EM> (English) <EM>sp</EM> (Spanish)
+and <EM>nl</EM> (Dutch).
+<P>
+<H2><A NAME="ss12.33">12.33 set/location </A>
+</H2>
+
+<P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE>
+<P>
+<P>You can set your latitude and longitude manually or alternatively use the
+<EM>set/qra</EM> command which will do the conversion for you.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/location 54 04 N 2 02 E
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.34">12.34 set/logininfo </A>
+</H2>
+
+<P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE>
+<P>
+<P>Show users and nodes when they log in and out of the local cluster. You
+can stop these messages by using the <EM>unset/logininfo</EM> command.
+<P>
+<H2><A NAME="ss12.35">12.35 set/name </A>
+</H2>
+
+<P><CODE><B>set/name <your_name></B> Set your name</CODE>
+<P>
+<P>Tell the cluster what your name is, eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/name Dirk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.36">12.36 set/page </A>
+</H2>
+
+<P><CODE><B>set/page <n></B> Set the number of lines per page</CODE>
+<P>
+<P>Tell the system how many lines you wish on a page when the number of lines
+of output from a command is more than this. The default is 20. Setting it
+explicitly to 0 will disable paging.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/PAGE 30
+ SET/PAGE 0
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The setting is stored in your user profile.
+<P>
+<H2><A NAME="ss12.37">12.37 set/qra </A>
+</H2>
+
+<P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE>
+<P>
+<P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
+done a SET/LOCATION then your latitude and longitude will be set roughly
+correctly (assuming your locator is correct ;-). For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SET/QRA JO02LQ
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.38">12.38 set/qth</A>
+</H2>
+
+<P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE>
+<P>
+<P>Tell the system where your are. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ set/qth East Dereham, Norfolk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.39">12.39 set/talk</A>
+</H2>
+
+<P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE>
+<P>
+<P>Allow talk messages to arrive at your console. You can switch off
+talks with the <EM>unset/talk</EM> command.
+<P>
+<H2><A NAME="ss12.40">12.40 set/wcy</A>
+</H2>
+
+<P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE>
+<P>
+<P>Allow WCY information to be seen at your console. You can switch off
+WCY messages with the <EM>unset/wcy</EM> command.
+<P>
+<H2><A NAME="ss12.41">12.41 set/wwv</A>
+</H2>
+
+<P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE>
+<P>
+<P>Allow WWV information to be seen at your console. You can switch off
+WWV messages with the <EM>unset/wwv</EM> command.
+<P>
+<H2><A NAME="ss12.42">12.42 set/wx </A>
+</H2>
+
+<P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE>
+<P>
+<P>Allow WX information to be seen at your console. You can switch off
+WX messages with the <EM>unset/wx</EM> command.
+<P>
+<H2><A NAME="ss12.43">12.43 show/date </A>
+</H2>
+
+<P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
+the local time</CODE>
+<P>
+<P>This is very nearly the same as SHOW/TIME, the only difference the format
+of the date string if no arguments are given.
+<P>If no prefixes or callsigns are given then this command returns the local
+time and UTC as the computer has it right now. If you give some prefixes
+then it will show UTC and UTC + the local offset (not including DST) at
+the prefixes or callsigns that you specify.
+<P>
+<H2><A NAME="ss12.44">12.44 show/dx </A>
+</H2>
+
+<P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE>
+<P>
+<P>If you just type SHOW/DX you will get the last so many spots
+(sysop configurable, but usually 10).
+<P>In addition you can add any number of these options in very nearly
+any order to the basic SHOW/DX command, they are:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+on <band> - eg 160m 20m 2m 23cm 6mm
+on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+
+<number> - the number of spots you want
+<from>-<to> - <from> spot no <to> spot no in
+ the selected list
+
+<prefix> - for a spotted callsign beginning with <prefix>
+*<suffix> - for a spotted callsign ending in <suffix>
+*<string>* - for a spotted callsign containing <string>
+
+day <number> - starting <number> days ago
+day <from>-<to> - <from> days <to> days ago
+
+info <text> - any spots containing <text> in the info or remarks
+
+by <call> - any spots spotted by <call> (spotter <call>
+ is the same).
+
+qsl - this automatically looks for any qsl info on the call
+ held in the spot database.
+
+iota [<iota>] - If the iota island number is missing it will
+ look for the string iota and anything which looks like
+ an iota island number. If you specify then it will look
+ for that island.
+
+qra [<locator>] - this will look for the specific locator if
+ you specify one or else anything that looks like a locator.
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>e.g.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.45">12.45 show/dxcc </A>
+</H2>
+
+<P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE>
+<P>
+<P>This command takes the <prefix> (which can be a full or partial
+callsign if desired), looks up which internal country number it is
+and then displays all the spots as per SH/DX for that country.
+<P>The options for SHOW/DX also apply to this command.
+e.g.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+ SH/DXCC G
+ SH/DXCC W on 20m info iota
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.46">12.46 show/files </A>
+</H2>
+
+<P><CODE><B>show/files [<filearea> [<string>]]</B> List
+the contents of a filearea</CODE>
+<P>
+<P>SHOW/FILES on its own will show you a list of the various fileareas
+available on the system. To see the contents of a particular file
+area type:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/FILES <filearea>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>where <filearea> is the name of the filearea you want to see the
+contents of.
+<P>You can also use shell globbing characters like '*' and '?' in a
+string to see a selection of files in a filearea eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/FILES bulletins arld*
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>See also TYPE - to see the contents of a file.
+<P>
+<H2><A NAME="ss12.47">12.47 show/filter </A>
+</H2>
+
+<P><CODE><B>show/filter</B> Show the filters you have set</CODE>
+<P>
+<P>Show the contents of all the filters that are set by you. This command
+displays all the filters set - for all the various categories.
+<P>
+<H2><A NAME="ss12.48">12.48 show/moon </A>
+</H2>
+
+<P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
+rise and set times</CODE>
+<P>
+<P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+<P>If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+<P>In addition, it will show the gain or loss dB relative to the nominal
+distance of 385,000Km due to the ellipsoidal nature of the orbit.
+<P>If all else fails it will show the Moonrise and set times for the node
+that you are connected to.
+<P>For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MOON
+ SH/MOON G1TLH W5UN
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.49">12.49 show/muf </A>
+</H2>
+
+<P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
+the likely propagation to <prefix></CODE>
+<P>
+<P>This command allow you to estimate the likelihood of you contacting
+a station with the prefix you have specified. The output assumes a modest
+power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
+<P>The result predicts the most likely operating frequencies and signal
+levels for high frequency (shortwave) radio propagation paths on
+specified days of the year and hours of the day. It is most useful for
+paths between 250 km and 6000 km, but can be used with reduced accuracy
+for paths shorter or longer than this.
+<P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
+used to predict the MUF given the predicted flux, day of the year,
+hour of the day and geographic coordinates of the transmitter and
+receiver. This routine is reasonably accurate for the purposes here,
+with a claimed RMS error of 3.8 MHz, but much smaller and less complex
+than the programs used by major shortwave broadcasting organizations,
+such as the Voice of America.
+<P>The command will display some header information detailing its
+assumptions, together with the locations, latitude and longitudes and
+bearings. It will then show UTC (UT), local time at the other end
+(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
+(Zen) and the likely signal strengths. Then for each frequency for which
+the system thinks there is a likelihood of a circuit it prints a value.
+<P>The value is currently a likely S meter reading based on the conventional
+6dB / S point scale. If the value has a '+' appended it means that it is
+1/2 an S point stronger. If the value is preceeded by an 'm' it means that
+there is likely to be much fading and by an 's' that the signal is likely
+to be noisy.
+<P>By default SHOW/MUF will show the next two hours worth of data. You
+can specify anything up to 24 hours worth of data by appending the no of
+hours required after the prefix. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MUF W
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>produces:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
+ Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
+ Location Lat / Long Azim
+ East Dereham, Norfolk 52 41 N 0 57 E 47
+ United-States-W 43 0 N 87 54 W 299
+ UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
+ 18 23 11.5 -35 mS0+ mS2 S3
+ 19 0 11.2 -41 mS0+ mS2 S3
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>indicating that you will have weak, fading circuits on top band and
+80m but usable signals on 40m (about S3).
+<P>inputing:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MUF W 24
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will get you the above display, but with the next 24 hours worth of
+propagation data.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/MUF W L 24
+ SH/MUF W 24 Long
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Gives you an estimate of the long path propagation characterics. It
+should be noted that the figures will probably not be very useful, nor
+terrible accurate, but it is included for completeness.
+<P>
+<H2><A NAME="ss12.50">12.50 show/prefix </A>
+</H2>
+
+<P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE>
+<P>
+<P>This command takes the <callsign> (which can be a full or partial
+callsign or a prefix), looks up which internal country number
+it is and then displays all the relevant prefixes for that country
+together with the internal country no, the CQ and ITU regions.
+<P>See also SHOW/DXCC
+<P>
+<H2><A NAME="ss12.51">12.51 show/qra </A>
+</H2>
+
+<P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
+between locators<BR>
+<B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE>
+<P>
+<P>This is a multipurpose command that allows you either to calculate the
+distance and bearing between two locators or (if only one locator is
+given on the command line) the distance and beraing from your station
+to the locator. For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+SH/QRA IO92QL
+SH/QRA JN06 IN73
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The first example will show the distance and bearing to the locator from
+yourself, the second example will calculate the distance and bearing from
+the first locator to the second. You can use 4 or 6 character locators.
+<P>It is also possible to convert a latitude and longitude to a locator by
+using this command with a latitude and longitude as an argument, for
+example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+SH/QRA 52 41 N 0 58 E
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.52">12.52 show/qrz</A>
+</H2>
+
+<P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE>
+<P>
+<P>This command queries the QRZ callbook server on the internet
+and returns any information available for that callsign. This service
+is provided for users of this software by http://www.qrz.com
+<P>
+<H2><A NAME="ss12.53">12.53 show/route </A>
+</H2>
+
+<P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE>
+<P>
+<P>This command allows you to see to which node the callsigns specified are
+connected. It is a sort of inverse sh/config.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ sh/route n2tly
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.54">12.54 show/satellite </A>
+</H2>
+
+<P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
+Show satellite tracking data</CODE>
+<P>
+<P>Show the tracking data from your location to the satellite of your choice
+from now on for the next few hours.
+<P>If you use this command without a satellite name it will display a list
+of all the satellites known currently to the system.
+<P>If you give a name then you can obtain tracking data of all the passes
+that start and finish 5 degrees below the horizon. As default it will
+give information for the next three hours for every five minute period.
+<P>You can alter the number of hours and the step size, within certain
+limits.
+<P>Each pass in a period is separated with a row of '-----' characters
+<P>So for example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+SH/SAT AO-10
+SH/SAT FENGYUN1 12 2
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.55">12.55 show/sun </A>
+</H2>
+
+<P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
+sun rise and set times</CODE>
+<P>
+<P>Show the sun rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+<P>If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+<P>If all else fails it will show the sunrise and set times for the node
+that you are connected to.
+<P>For example:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ SH/SUN
+ SH/SUN G1TLH K9CW ZS
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.56">12.56 show/time </A>
+</H2>
+
+<P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
+the local time</CODE>
+<P>
+<P>If no prefixes or callsigns are given then this command returns the local
+time and UTC as the computer has it right now. If you give some prefixes
+then it will show UTC and UTC + the local offset (not including DST) at
+the prefixes or callsigns that you specify.
+<P>
+<H2><A NAME="ss12.57">12.57 show/wcy </A>
+</H2>
+
+<P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
+<B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE>
+<P>
+<P>Display the most recent WCY information that has been received by the system
+<P>
+<H2><A NAME="ss12.58">12.58 show/wwv</A>
+</H2>
+
+<P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
+<B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE>
+<P>
+<P>Display the most recent WWV information that has been received by the system
+<P>
+<H2><A NAME="ss12.59">12.59 sysop </A>
+</H2>
+
+<P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE>
+<P>
+<P>The system automatically reduces your privilege level to that of a
+normal user if you login in remotely. This command allows you to
+regain your normal privilege level. It uses the normal system: five
+numbers are returned that are indexes into the character array that is
+your assigned password (see SET/PASSWORD). The indexes start from
+zero.
+<P>You are expected to return a string which contains the characters
+required in the correct order. You may intersperse those characters
+with others to obscure your reply for any watchers. For example (and
+these values are for explanation :-):
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>you type:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>They will all match. If there is no password you will still be offered
+numbers but nothing will happen when you input a string. Any match is
+case sensitive.
+<P>
+<H2><A NAME="ss12.60">12.60 talk </A>
+</H2>
+
+<P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
+<B>talk <callsign> <text></B> Send a text message to <callsign><BR>
+<B>talk <callsign> > <node_call> [<text>]</B>
+Send a text message to <callsign> via <node_call></CODE>
+<P>
+<P>Send a short message to any other station that is visible on the cluster
+system. You can send it to anyone you can see with a SHOW/CONFIGURATION
+command, they don't have to be connected locally.
+<P>The second form of TALK is used when other cluster nodes are connected
+with restricted information. This usually means that they don't send
+the user information usually associated with logging on and off the cluster.
+<P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
+see GB7TLH in the SH/C list but with no users, then you would use the
+second form of the talk message.
+<P>If you want to have a ragchew with someone you can leave the text message
+out and the system will go into 'Talk' mode. What this means is that a
+short message is sent to the recipient telling them that you are in a 'Talking'
+frame of mind and then you just type - everything you send will go to the
+station that you asked for.
+<P>All the usual announcements, spots and so on will still come out on your
+terminal.
+<P>If you want to do something (such as send a spot) you precede the normal
+command with a '/' character, eg:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
+ /HELP talk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To leave talk mode type:
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ /EX
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss12.61">12.61 type </A>
+</H2>
+
+<P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE>
+<P>
+<P>Type out the contents of a file in a filearea. So, for example, in
+filearea 'bulletins' you want to look at file 'arld051' you would
+enter:-
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+ TYPE bulletins/arld051
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>See also SHOW/FILES to see what fileareas are available and a
+list of content.
+<P>
+<H2><A NAME="ss12.62">12.62 who </A>
+</H2>
+
+<P><CODE><B>who</B> Show who is physically connected locally</CODE>
+<P>
+<P>This is a quick listing that shows which callsigns are connected and
+what sort of connection they have
+<P>
+<H2><A NAME="ss12.63">12.63 wx </A>
+</H2>
+
+<P><CODE><B>wx <text></B> Send a weather message to local users<BR>
+<B>wx full <text> </B> Send a weather message to all cluster users</CODE>
+<P>
+<P>Weather messages can sometimes be useful if you are experiencing an extreme
+that may indicate enhanced conditions
+<P>
+<HR>
+Next
+<A HREF="usermanual-11.html">Previous</A>
+<A HREF="usermanual.html#toc12">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Logins and logouts.</TITLE>
+ <LINK HREF="usermanual-3.html" REL=next>
+ <LINK HREF="usermanual-1.html" REL=previous>
+ <LINK HREF="usermanual.html#toc2" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-3.html">Next</A>
+<A HREF="usermanual-1.html">Previous</A>
+<A HREF="usermanual.html#toc2">Contents</A>
+<HR>
+<H2><A NAME="s2">2. Logins and logouts.</A></H2>
+
+<P>You might not think that there is a lot of point of including a
+section on how to log in and out of DXSpider. However, you would be
+suprised at the difficulties some people have in simply getting in
+and out of the cluster!
+<P>There are several ways a login might be achieved, dependant on how
+the sysop has DXSpider configured. It is impossible for me to cover all
+variations but here are the basic ones.
+<P>
+<H2><A NAME="ss2.1">2.1 AX25 logins.</A>
+</H2>
+
+<P>Simplicity itself. The usual <B>CONNECT</B> command will log you straight
+into the cluster and you will not have to do anything else.
+Obviously, you will have to connect to the correct callsign. Some
+nodes use an SSID with their call so you would have to add that.
+<P><B>Examples:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+connect GB7MBC
+connect GB7MBC-1
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss2.2">2.2 Netrom logins.</A>
+</H2>
+
+<P>There are several possibilities here, dependant on how the sysop has
+configured his system. If you are connecting via netrom then you are
+most probably connecting from another station. Listing the nodes in
+that station with the <B>NODES</B> command will tell you what callsign
+or netrom alias to connect to. Then just issue the connect command
+from there. It is possible that the netrom alias may connect you to
+a node with an alias for the cluster, such as DXC. Just type this
+and you will be connected.
+<P><B>Example:</B>
+<BLOCKQUOTE><CODE>
+<PRE>
+connect MBCDX
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss2.3">2.3 Telnet logins.</A>
+</H2>
+
+<P>Because DXSpider runs under the Linux operating system, it is possible to
+make a direct telnet connection into the cluster. With telnet
+connections, the source callsign is not seen by DXSpider, so you will be
+asked to login with your callsign.
+To telnet to DXSpider, you would connect to a specific port. There is no
+standard at the moment for a cluster telnet port but ask the sysop if
+you are unsure.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+telnet gb7mbc 8000
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>All the above are possible ways of connecting to a DXSpider cluster. You
+may have some or all of these available to you. There may be one or
+two additional ways to connect dependant on the network local to you.
+However I am sure you get the idea.
+<P>
+<H2><A NAME="ss2.4">2.4 Logouts.</A>
+</H2>
+
+<P>Logging out can be done by simply issuing the standard <B>BYE</B>
+command.
+<P>You could also send a disconnect if you are using AX25, or a <B>CLOSE</B>
+command if you are connected via telnet.
+If you do not log out gracefully using one of the above commands,
+you may find you are unable to get a full connect next time. This
+may also happen if a NETRom connection drops. You may get connected,
+but nothing else will happen because the program thinks you are still
+connected and will not let you connect twice under the same call.
+However you could reconnect by adding a number to the end of your call,
+for example G0YLM2.
+This can be done by either altering your MYCALL setting in the TNC or
+by altering your program configuration.
+<P>
+<P>
+<HR>
+<A HREF="usermanual-3.html">Next</A>
+<A HREF="usermanual-1.html">Previous</A>
+<A HREF="usermanual.html#toc2">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Setting your personal details.</TITLE>
+ <LINK HREF="usermanual-4.html" REL=next>
+ <LINK HREF="usermanual-2.html" REL=previous>
+ <LINK HREF="usermanual.html#toc3" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-4.html">Next</A>
+<A HREF="usermanual-2.html">Previous</A>
+<A HREF="usermanual.html#toc3">Contents</A>
+<HR>
+<H2><A NAME="s3">3. Setting your personal details.</A></H2>
+
+<P>Once logged in to the cluster, you should set your details so that
+anybody who wishes to contact you can find out who and where you are.
+There are four items to set, your name, qth, location and home node.
+Setting these details also allows the use of the SHOW/HEADING and
+SHOW/SUN commands from within the cluster. Unless you set your QTH
+and location, these commands cannot function.
+Once you have set your name, DXSpider will greet you with it next time
+you login. Your QTH setting is where you live and it is a good idea
+to add your locator to this as the location setting is converted to
+latitude and longitude once inputted. You can actually set your location
+in latitude/longitude or as a locator. Setting your home node will
+tell the program where you wish mail to be sent to you.
+<P><B>Examples:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+set/name Ian
+set/qth Morecambe, Lancashire IO84NB
+set/location 48 34 n 12 12 e
+set/qra IO84NB
+set/home gb7mbc
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<HR>
+<A HREF="usermanual-4.html">Next</A>
+<A HREF="usermanual-2.html">Previous</A>
+<A HREF="usermanual.html#toc3">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Getting and posting DX.</TITLE>
+ <LINK HREF="usermanual-5.html" REL=next>
+ <LINK HREF="usermanual-3.html" REL=previous>
+ <LINK HREF="usermanual.html#toc4" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-5.html">Next</A>
+<A HREF="usermanual-3.html">Previous</A>
+<A HREF="usermanual.html#toc4">Contents</A>
+<HR>
+<H2><A NAME="s4">4. Getting and posting DX.</A></H2>
+
+<P>When all is said and done, this is the main function of a DX cluster.
+In its simplest form you can just connect to the node and you will
+start to receive DX spots almost immediately! You can check on
+recent postings in either a general manner or on a particular band or
+mode. You can even check DX by callsign or a fragment of a callsign.
+Of course, once you get the hang of things, it is expected that you
+start posting some yourself! After all, there would be no clusters
+if people did not post DX and you get the added thrill of the hunt!
+<P>
+<H2><A NAME="ss4.1">4.1 Receiving DX.</A>
+</H2>
+
+<P>As we have already said, it is possible just to connect to the
+cluster and you will receive spots automatically. However, you may
+wish to check on spots just posted. Maybe you wish to see if a
+particular band is open or if a certain callsign is active, perhaps a
+DXpedition. The command to do this is <B>SHOW/DX</B>. Without any
+other arguments, this command will output the last 10 spots
+posted. It is possible to look at more than this, for example the
+last 20 or 50 spots, by adding the number to the command. You can
+make it even more specific by adding a band in either wavelength or
+frequency, and/or any additional information such as QSL details.
+<P><B>Examples:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/dx
+show/dx 5
+show/dx 20
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will show the last 10, 5 and 20 spots received by the cluster
+respectively.
+<P><B>Examples</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/dx on 20m
+show/dx 10 on 20m
+show/dx 20 on 20m
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will show the last 5, 10 or 20 spots on 20 metres only.
+<P>It is also possible to check for certain callsigns, or fragments of
+callsigns in the same way.
+<P><B>Examples:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/dx g0vgs
+show/dx 10 g0vgs
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>would show the last 5 or 10 dx spots containing the callsign g0vgs.
+<P>
+<P>You can check for DX by offset and also by specifying a comment to
+search for.
+<P><B>Examples:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/dx 30-40
+show/dx 14000-14033
+show/dx iota
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>would show the spots that arrived between 30 and 40 spots ago and any
+spots with the word <EM>iota</EM> in the comment field. The case of
+the comment is not important.
+<P>Checking DX posted on a certain day is possible too. All you have
+to do here is to specify how many days ago it was like this ...
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/dx day 30
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>It is of course possible to specify multiple arguments.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/dx 20 prefix 9a on vhf day 30
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This would show the last 20 spots posted by or about calls with the prefix
+9a on vhf 30 days ago.
+<P>As you can see the <B>SHOW/DX</B> command is very flexible, so if you are
+not sure whether something will work or not, try it and see! More
+information can be found in the Command Set section.
+<P>
+<H2><A NAME="ss4.2">4.2 Posting DX.</A>
+</H2>
+
+<P>To post DX you use the <B>DX</B> command. The syntax is shown below.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dx (frequency) (callsign) (remarks)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Where frequency is in kilohertz and the callsign is the callsign of
+the station you have worked or heard, (ie not your own callsign!).
+The remarks section allows you to add information like the operators
+name or perhaps a location. Actually DXSpider will allow the frequency
+and callsign fields to be entered in any order.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dx 14004 pa3ezl OP Aurelio 599
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>In fact, all the following will give the same result...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+dx 14004 pa3ezl OP Aurelio 599
+dx pa3ezl 14004 OP Aurelio 599
+dx pa3ezl 14.004 OP Aurelio 599
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This posting, or callout as it is known, will be forwarded to all
+other connected stations both at the cluster you are connected to and
+other active clusters in the network. The callout will also be sent
+to you as proof of receipt.
+<P>
+<HR>
+<A HREF="usermanual-5.html">Next</A>
+<A HREF="usermanual-3.html">Previous</A>
+<A HREF="usermanual.html#toc4">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Headings and propagation</TITLE>
+ <LINK HREF="usermanual-6.html" REL=next>
+ <LINK HREF="usermanual-4.html" REL=previous>
+ <LINK HREF="usermanual.html#toc5" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-6.html">Next</A>
+<A HREF="usermanual-4.html">Previous</A>
+<A HREF="usermanual.html#toc5">Contents</A>
+<HR>
+<H2><A NAME="s5">5. Headings and propagation</A></H2>
+
+<P>There are three commands in DXSpider to help you get the best DX possible.
+These are <B>SHOW/SUN</B>, <B>SHOW/MOON</B> and
+<B>SHOW/HEADING</B>. These commands will only work for you if you
+have entered your personal details. They use your entered location as
+a reference, so if you have not entered it or have entered it incorrectly
+they will not return the correct information.
+<P>
+<H2><A NAME="ss5.1">5.1 Sun</A>
+</H2>
+
+<P>The <B>SHOW/SUN</B> command can be used in three different ways. It
+can be used to show sunrise and sunset times for your own station, a
+particular callsign or a prefix.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/sun
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The output from this would look something like this ..
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+sh/sun Location Rise Set Azim Elev
+G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+sh/sun 5b4
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>would look like this ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+sh/sun 5b4 Location Rise Set Azim Elev 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can also specify multiple arguments like this ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+sh/sun gw4veq 5b4ab zs
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>and then the output would look like this ...
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+sh/sun gw4veq 5b4ab zs
+Location Rise Set Azim Elev
+GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9 5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
+ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
+ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
+ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss5.2">5.2 Moon</A>
+</H2>
+
+<P>The <B>SHOW/MOON</B> command works in the same way as the
+<B>SHOW/SUN</B> command. This program however, calculates the
+rise and set times of the moon for a prefix or callsign, together
+with the current azimuth and elevation of the sun at these
+locations.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/moon ea
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The output from this command would look like this ..
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+sh/moon ea
+Location Rise Set Azim Elev RGain dB
+EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>You can see that the output is similar to the <B>SHOW/SUN</B>
+command, with slightly different fields.
+<P>
+<H2><A NAME="ss5.3">5.3 Heading</A>
+</H2>
+
+<P>The <B>SHOW/HEADING</B> command works in the same way as the
+<B>SHOW/SUN</B> and <B>SHOW/MOON</B> commands but outputs beam
+headings for a specified callsign or prefix. Reciprocal beam headings
+are also calculated.
+<P><B>Example</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/heading zl
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The output from this command would look like this ..
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+sh/heading zl
+ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
+ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
+ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
+ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<HR>
+<A HREF="usermanual-6.html">Next</A>
+<A HREF="usermanual-4.html">Previous</A>
+<A HREF="usermanual.html#toc5">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Announcements.</TITLE>
+ <LINK HREF="usermanual-7.html" REL=next>
+ <LINK HREF="usermanual-5.html" REL=previous>
+ <LINK HREF="usermanual.html#toc6" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-7.html">Next</A>
+<A HREF="usermanual-5.html">Previous</A>
+<A HREF="usermanual.html#toc6">Contents</A>
+<HR>
+<H2><A NAME="s6">6. Announcements.</A></H2>
+
+<H2><A NAME="ss6.1">6.1 Making announcements.</A>
+</H2>
+
+<P>Occasionally, you may wish to post something that does not fall into
+the normal parameters for a DX callout. You may wish to tell
+everybody connected that 10 FM is open for example, or ask if anyone
+knows the QSL manager for a certain callsign etc. You can do this
+using the <B>ANNOUNCE</B> command.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+announce 10 FM is open in IO84NB to europe.
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>That would let everyone know locally that this was the case, however
+it would not be forwarded to other nodes connected. To send
+announcements to other connected nodes as well, you would use the
+<B>FULL</B> extension.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+announce full Anyone seen EA7WA today?
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Be cautious in your use of announce full. There are many other tools
+available to get the information you require and the judicious use of
+this command is frowned upon as it creates a great deal of traffic
+across the network.
+<P>
+<H2><A NAME="ss6.2">6.2 Listing announcements.</A>
+</H2>
+
+<P>You can list previous announcements in the standard format with the
+<B>SHOW</B> command. As before you can list just the last 5 or as
+many as you wish.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/announcements
+show/announcements 10
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<HR>
+<A HREF="usermanual-7.html">Next</A>
+<A HREF="usermanual-5.html">Previous</A>
+<A HREF="usermanual.html#toc6">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Nodes and users.</TITLE>
+ <LINK HREF="usermanual-8.html" REL=next>
+ <LINK HREF="usermanual-6.html" REL=previous>
+ <LINK HREF="usermanual.html#toc7" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-8.html">Next</A>
+<A HREF="usermanual-6.html">Previous</A>
+<A HREF="usermanual.html#toc7">Contents</A>
+<HR>
+<H2><A NAME="s7">7. Nodes and users.</A></H2>
+
+<P>You can check which nodes are connected in the network, who is
+logged on locally, who is logged on at all the nodes or even
+just one node in particular. This is handy if you wish to see whether
+a friend is connected at the node they use. To see who is connected
+to the nodes, the <B>SHOW/CONFIGURATION</B> command is used.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/configuration
+show/configuration/nodes
+show/configuration (node_call)
+show/configuration (prefix)
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The first of our three examples would output something like this,
+<P>
+<PRE>
+sh/c
+Node Callsigns
+EI5TCR (7 users)
+GB7ADX
+GB7BAA G4FPV G8TIC
+GB7BIG (GD0TEP) GD3UMW
+GB7BPQ (G0INA) G0RCI G3AKU G3OCA
+(GB7CDX) G3JNB G4ALR
+GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
+ G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
+ ON7WP
+GB7DXA G0RDI G8SJP
+GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
+ G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
+GB7DXE G1NNB
+(GB7DXG) GU6EFB GU7DHI
+GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
+ G4XQY G7GAN
+GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
+ M0BCT M1EMF
+</PRE>
+<P>You will notice that EI5TCR is showing only that it has 7 users and not
+giving the actual callsigns. This means that this node is on a limited
+protocol of some kind, probably because of a contest situation where
+slow radio links can block up and fail if too much information is sent
+between nodes.
+<P>The second example would just show the nodes connected in the
+network, like this,
+<P>
+<PRE>
+sh/c/n
+Node Callsigns
+GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
+ GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
+ GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
+ GB7YDX KL7G N2TLY (ON0DXK)
+GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
+GB7MBC
+PA4AB-14 PA4AB-14
+PI4TUE-8 PI4TUE-8
+</PRE>
+<P>If we insert the node_call pi4tue-8 into the third example, then
+this would be the output,
+<P>
+<PRE>
+Node Callsigns
+PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
+ F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
+ ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
+ PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
+ YT1XX
+</PRE>
+<P>As you can see, only the users of the requested node are shown.
+<P>You can also use a prefix to show only a group of nodes. For example
+you may only wish to see who is connected to the nodes in the UK. To
+do this simply use a prefix like this ...
+<P>
+<PRE>
+show/configuration gb7
+</PRE>
+<P>To show the locally connected users, the <B>SHOW/USERS</B> command is
+used
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+show/users
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>The output of this command would look like this,
+<P>
+<PRE>
+Callsigns connected to GB7MBC
+G0JHC G0NEI G0VGS G0VGS-2 G0YLM
+G3JAG G3OWO G3UEU
+</PRE>
+<P>
+<HR>
+<A HREF="usermanual-8.html">Next</A>
+<A HREF="usermanual-6.html">Previous</A>
+<A HREF="usermanual.html#toc7">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Talk mode.</TITLE>
+ <LINK HREF="usermanual-9.html" REL=next>
+ <LINK HREF="usermanual-7.html" REL=previous>
+ <LINK HREF="usermanual.html#toc8" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-9.html">Next</A>
+<A HREF="usermanual-7.html">Previous</A>
+<A HREF="usermanual.html#toc8">Contents</A>
+<HR>
+<H2><A NAME="s8">8. Talk mode.</A></H2>
+
+<P>You can send a single comment or start a dedicated talk session to
+another user by using the <B>TALK</B> command.
+<P>
+<P>Talk mode is used to send a one line comment or greeting to a
+specific user connected either at your node or another in the
+network. You can also enter into a dedicated talk session with
+another user. Talks will be automatically forwarded to other nodes
+if the station you are talking to is not connected locally.
+You can find out who is connected by using the
+<B>SHOW/CONFIGURATION</B> command, (described earlier).
+<P><B>Examples:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+
+talk g0rdi Having a good day Iain?
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>This example would send the line "Having a good day Iain?" to the
+user g0rdi but would leave you in normal mode.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+talk g0rdi
+Entering Talkmode, /EX to end, /<cmd> to run a command
+Talk (G0RDI)>
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>As you can see, you can still run commands whilst in talk mode.
+Simply prefix the command with a / like /sh/dx and you will get
+the expected output.
+If the user is connected to another node, you may have to use a
+slightly extended version of the <B>TALK</B> command.
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+talk g0rdi > gb7djk
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>To exit talk mode, you issue the command <B>/ex</B>.
+<P>Whilst in talk mode you will still receive DX spots. This means that
+you can chat to a friend whilst working DX.
+<P>
+<HR>
+<A HREF="usermanual-9.html">Next</A>
+<A HREF="usermanual-7.html">Previous</A>
+<A HREF="usermanual.html#toc8">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual : Mail.</TITLE>
+ <LINK HREF="usermanual-10.html" REL=next>
+ <LINK HREF="usermanual-8.html" REL=previous>
+ <LINK HREF="usermanual.html#toc9" REL=contents>
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-10.html">Next</A>
+<A HREF="usermanual-8.html">Previous</A>
+<A HREF="usermanual.html#toc9">Contents</A>
+<HR>
+<H2><A NAME="s9">9. Mail.</A></H2>
+
+<P>You can send and receive both personal mail and bulletins with DXSpider
+quite easily.
+<P>
+<H2><A NAME="ss9.1">9.1 The "directory" command.</A>
+</H2>
+
+<P>To list mail you would use the <B>DIRECTORY</B> command. On its
+own, this command will output the last ten messages received by the
+node, either to or from yourself or bulletins such as "DX" and "ALL".
+As with other commands you can display more by specifying a number
+with the command. You should be aware that Spider will accept
+these commands by separating with either a slash or a space, so
+<EM>dir new</EM> and <EM>dir/new</EM> work in the same way.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+directory
+directory/20
+directory 20
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>Of course most of the time you will only want to list new mail sent
+to you personally since your last login. However you might also like
+to check for general mail received by the node. In fact if there is
+new mail for you, the cluster will tell you when you login. You will
+also be informed if new mail arrives for you during the time you are
+logged in.
+Mail is not only sent to callsigns though. Mail can also be sent to
+subjects like "all" or "local" or "dx" etc. You can treat these
+bulletins in the same way as personal mail with the directory
+command.
+<P><B>Examples:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+directory/new
+directory/own
+directory/own/10
+directory/all
+directory/from <call>
+</PRE>
+</CODE></BLOCKQUOTE>
+
+<P>The last option will only show mail from a callsign if it was sent to
+you personally or was sent as a bulletin. There are some additional
+commands and these can be found in the DXSpider Command Reference section.
+<P>
+<H2><A NAME="ss9.2">9.2 Reading mail.</A>
+</H2>
+
+<P>The output of the <B>DIRECTORY</B> command could be something like
+this.
+<P>
+<PRE>
+dir
+ 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
+ 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
+ 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
+ 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
+ 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
+ 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
+ 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
+ 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
+ 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
+ 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
+ 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
+</PRE>
+<P>The first column is the actual message number. If the message is a
+personal one to you, you will see a letter 'p' after this number. If
+the message has been read, there will be a '-' between the message
+number and the 'p'. This only works for personal messages. The next
+column shows the file size of the message. The third column shows the
+address the message was sent to and the next column shows who sent it.
+The rest is fairly self-explanatory.
+<P>Reading a message is as simple as typing read, followed by the
+message number that you wish to read.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+read 25
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>will read message number 25. However the mail will be displayed in it's
+entirety unless you specify a page length. You can set your page length
+to any number you like and when the message reaches that number of lines
+you will get a prompt giving you options.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+set/page 20
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<P>
+<H2><A NAME="ss9.3">9.3 Sending mail.</A>
+</H2>
+
+<P>Sending mail is done in the time honoured way. First you specify
+a recipient for the message, then you will be prompted for a subject.
+Once you have done this you will be asked to type your message.
+Please remember that there is no automatic word wrap, so unless you
+are using a client that wraps lines automatically, remember to hit
+return at the end of each line.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+send m0azm
+Enter Subject (30 characters):
+See you Thursday
+Enter Message /EX to send or /ABORT to exit
+Hi Ian,
+Just a quick note to say that I can make Thursday after all. The
+appointment I had has cancelled so we are go!
+Cheers
+Ian
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>At this point you can either hit return and enter /ex to send the
+message or use /abort at any time to abort it. You can now display
+the message in the normal way. There are several send options and
+these are listed in the Command Set section. These include sending
+mail to several recipients and asking for a return receipt.
+<P>
+<P>
+<H2><A NAME="ss9.4">9.4 Replying to mail.</A>
+</H2>
+
+<P>If mail is addressed to you or to a bulletin address, you can use the
+<B>REPLY</B> command to reply to it. Using this command, the
+subject will be automatically set for you as "Re: subject", whatever
+the subject was.
+<P><B>Example:</B>
+<P>
+<BLOCKQUOTE><CODE>
+<PRE>
+reply 2500
+</PRE>
+</CODE></BLOCKQUOTE>
+<P>
+<H2><A NAME="ss9.5">9.5 Deleting mail</A>
+To delete a message, you use the <EM>delete</EM> command.You can only delete messages sent to or received by yourself. Bulletins are dealt with automatically or by the sysop.</H2>
+
+<HR>
+<A HREF="usermanual-10.html">Next</A>
+<A HREF="usermanual-8.html">Previous</A>
+<A HREF="usermanual.html#toc9">Contents</A>
+</BODY>
+</HTML>
--- /dev/null
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<HTML>
+<HEAD>
+ <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
+ <TITLE>The DXSpider User Manual </TITLE>
+ <LINK HREF="usermanual-1.html" REL=next>
+
+
+<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
+</HEAD>
+<BODY>
+<A HREF="usermanual-1.html">Next</A>
+Previous
+Contents
+<HR>
+<H1>The DXSpider User Manual </H1>
+
+<H2>Ian Maude, G0VGS, (ianmaude@btinternet.com)</H2>Version 1.0, March 2001
+<P><HR>
+<EM>A complete reference for users of the DXSpider DXCluster program.</EM>
+<HR>
+<P>
+<H2><A NAME="toc1">1.</A> <A HREF="usermanual-1.html">Introduction</A></H2>
+
+<UL>
+<LI><A HREF="usermanual-1.html#ss1.1">1.1 What is a DX Cluster?</A>
+<LI><A HREF="usermanual-1.html#ss1.2">1.2 So what is DXSpider?</A>
+</UL>
+<P>
+<H2><A NAME="toc2">2.</A> <A HREF="usermanual-2.html">Logins and logouts.</A></H2>
+
+<UL>
+<LI><A HREF="usermanual-2.html#ss2.1">2.1 AX25 logins.</A>
+<LI><A HREF="usermanual-2.html#ss2.2">2.2 Netrom logins.</A>
+<LI><A HREF="usermanual-2.html#ss2.3">2.3 Telnet logins.</A>
+<LI><A HREF="usermanual-2.html#ss2.4">2.4 Logouts.</A>
+</UL>
+<P>
+<H2><A NAME="toc3">3.</A> <A HREF="usermanual-3.html">Setting your personal details.</A></H2>
+
+<P>
+<H2><A NAME="toc4">4.</A> <A HREF="usermanual-4.html">Getting and posting DX.</A></H2>
+
+<UL>
+<LI><A HREF="usermanual-4.html#ss4.1">4.1 Receiving DX.</A>
+<LI><A HREF="usermanual-4.html#ss4.2">4.2 Posting DX.</A>
+</UL>
+<P>
+<H2><A NAME="toc5">5.</A> <A HREF="usermanual-5.html">Headings and propagation</A></H2>
+
+<UL>
+<LI><A HREF="usermanual-5.html#ss5.1">5.1 Sun</A>
+<LI><A HREF="usermanual-5.html#ss5.2">5.2 Moon</A>
+<LI><A HREF="usermanual-5.html#ss5.3">5.3 Heading</A>
+</UL>
+<P>
+<H2><A NAME="toc6">6.</A> <A HREF="usermanual-6.html">Announcements.</A></H2>
+
+<UL>
+<LI><A HREF="usermanual-6.html#ss6.1">6.1 Making announcements.</A>
+<LI><A HREF="usermanual-6.html#ss6.2">6.2 Listing announcements.</A>
+</UL>
+<P>
+<H2><A NAME="toc7">7.</A> <A HREF="usermanual-7.html">Nodes and users.</A></H2>
+
+<P>
+<H2><A NAME="toc8">8.</A> <A HREF="usermanual-8.html">Talk mode.</A></H2>
+
+<P>
+<H2><A NAME="toc9">9.</A> <A HREF="usermanual-9.html">Mail.</A></H2>
+
+<UL>
+<LI><A HREF="usermanual-9.html#ss9.1">9.1 The "directory" command.</A>
+<LI><A HREF="usermanual-9.html#ss9.2">9.2 Reading mail.</A>
+<LI><A HREF="usermanual-9.html#ss9.3">9.3 Sending mail.</A>
+<LI><A HREF="usermanual-9.html#ss9.4">9.4 Replying to mail.</A>
+<LI><A HREF="usermanual-9.html#ss9.5">9.5 Deleting mail</A>
+</UL>
+<P>
+<H2><A NAME="toc10">10.</A> <A HREF="usermanual-10.html">Filtering (From version 1.45)</A></H2>
+
+<UL>
+<LI><A HREF="usermanual-10.html#ss10.1">10.1 General filter rules</A>
+<LI><A HREF="usermanual-10.html#ss10.2">10.2 Types of filter</A>
+<LI><A HREF="usermanual-10.html#ss10.3">10.3 Filter options</A>
+<LI><A HREF="usermanual-10.html#ss10.4">10.4 Advanced filtering</A>
+</UL>
+<P>
+<H2><A NAME="toc11">11.</A> <A HREF="usermanual-11.html">Hints, tips and common questions.</A></H2>
+
+<P>
+<H2><A NAME="toc12">12.</A> <A HREF="usermanual-12.html">The DXSpider command reference</A></H2>
+
+<UL>
+<LI><A HREF="usermanual-12.html#ss12.1">12.1 accept/announce</A>
+<LI><A HREF="usermanual-12.html#ss12.2">12.2 accept/spots </A>
+<LI><A HREF="usermanual-12.html#ss12.3">12.3 accept/wcy </A>
+<LI><A HREF="usermanual-12.html#ss12.4">12.4 accept/wwv </A>
+<LI><A HREF="usermanual-12.html#ss12.5">12.5 announce </A>
+<LI><A HREF="usermanual-12.html#ss12.6">12.6 announce full </A>
+<LI><A HREF="usermanual-12.html#ss12.7">12.7 apropos </A>
+<LI><A HREF="usermanual-12.html#ss12.8">12.8 bye </A>
+<LI><A HREF="usermanual-12.html#ss12.9">12.9 clear/spots </A>
+<LI><A HREF="usermanual-12.html#ss12.10">12.10 dbavail </A>
+<LI><A HREF="usermanual-12.html#ss12.11">12.11 dbshow </A>
+<LI><A HREF="usermanual-12.html#ss12.12">12.12 directory </A>
+<LI><A HREF="usermanual-12.html#ss12.13">12.13 dx </A>
+<LI><A HREF="usermanual-12.html#ss12.14">12.14 help </A>
+<LI><A HREF="usermanual-12.html#ss12.15">12.15 kill </A>
+<LI><A HREF="usermanual-12.html#ss12.16">12.16 links </A>
+<LI><A HREF="usermanual-12.html#ss12.17">12.17 read </A>
+<LI><A HREF="usermanual-12.html#ss12.18">12.18 reject/announce</A>
+<LI><A HREF="usermanual-12.html#ss12.19">12.19 reject/spots </A>
+<LI><A HREF="usermanual-12.html#ss12.20">12.20 reject/wcy </A>
+<LI><A HREF="usermanual-12.html#ss12.21">12.21 reject/wwv </A>
+<LI><A HREF="usermanual-12.html#ss12.22">12.22 reply </A>
+<LI><A HREF="usermanual-12.html#ss12.23">12.23 send </A>
+<LI><A HREF="usermanual-12.html#ss12.24">12.24 set/address </A>
+<LI><A HREF="usermanual-12.html#ss12.25">12.25 set/announce </A>
+<LI><A HREF="usermanual-12.html#ss12.26">12.26 set/beep </A>
+<LI><A HREF="usermanual-12.html#ss12.27">12.27 set/dx </A>
+<LI><A HREF="usermanual-12.html#ss12.28">12.28 set/dxgrid</A>
+<LI><A HREF="usermanual-12.html#ss12.29">12.29 set/echo </A>
+<LI><A HREF="usermanual-12.html#ss12.30">12.30 set/here</A>
+<LI><A HREF="usermanual-12.html#ss12.31">12.31 set/homenode </A>
+<LI><A HREF="usermanual-12.html#ss12.32">12.32 set/language </A>
+<LI><A HREF="usermanual-12.html#ss12.33">12.33 set/location </A>
+<LI><A HREF="usermanual-12.html#ss12.34">12.34 set/logininfo </A>
+<LI><A HREF="usermanual-12.html#ss12.35">12.35 set/name </A>
+<LI><A HREF="usermanual-12.html#ss12.36">12.36 set/page </A>
+<LI><A HREF="usermanual-12.html#ss12.37">12.37 set/qra </A>
+<LI><A HREF="usermanual-12.html#ss12.38">12.38 set/qth</A>
+<LI><A HREF="usermanual-12.html#ss12.39">12.39 set/talk</A>
+<LI><A HREF="usermanual-12.html#ss12.40">12.40 set/wcy</A>
+<LI><A HREF="usermanual-12.html#ss12.41">12.41 set/wwv</A>
+<LI><A HREF="usermanual-12.html#ss12.42">12.42 set/wx </A>
+<LI><A HREF="usermanual-12.html#ss12.43">12.43 show/date </A>
+<LI><A HREF="usermanual-12.html#ss12.44">12.44 show/dx </A>
+<LI><A HREF="usermanual-12.html#ss12.45">12.45 show/dxcc </A>
+<LI><A HREF="usermanual-12.html#ss12.46">12.46 show/files </A>
+<LI><A HREF="usermanual-12.html#ss12.47">12.47 show/filter </A>
+<LI><A HREF="usermanual-12.html#ss12.48">12.48 show/moon </A>
+<LI><A HREF="usermanual-12.html#ss12.49">12.49 show/muf </A>
+<LI><A HREF="usermanual-12.html#ss12.50">12.50 show/prefix </A>
+<LI><A HREF="usermanual-12.html#ss12.51">12.51 show/qra </A>
+<LI><A HREF="usermanual-12.html#ss12.52">12.52 show/qrz</A>
+<LI><A HREF="usermanual-12.html#ss12.53">12.53 show/route </A>
+<LI><A HREF="usermanual-12.html#ss12.54">12.54 show/satellite </A>
+<LI><A HREF="usermanual-12.html#ss12.55">12.55 show/sun </A>
+<LI><A HREF="usermanual-12.html#ss12.56">12.56 show/time </A>
+<LI><A HREF="usermanual-12.html#ss12.57">12.57 show/wcy </A>
+<LI><A HREF="usermanual-12.html#ss12.58">12.58 show/wwv</A>
+<LI><A HREF="usermanual-12.html#ss12.59">12.59 sysop </A>
+<LI><A HREF="usermanual-12.html#ss12.60">12.60 talk </A>
+<LI><A HREF="usermanual-12.html#ss12.61">12.61 type </A>
+<LI><A HREF="usermanual-12.html#ss12.62">12.62 who </A>
+<LI><A HREF="usermanual-12.html#ss12.63">12.63 wx </A>
+</UL>
+<HR>
+<A HREF="usermanual-1.html">Next</A>
+Previous
+Contents
+</BODY>
+</HTML>
# Makefile for Ian, 2.1.2001
#
-all: ../html/adminmanual.html ../txt/adminmanual.txt ../html/spiderFAQ.html ../txt/spiderFAQ.txt
+all: ../html/adminmanual.html ../txt/adminmanual.txt ../html/spiderFAQ.html ../txt/spiderFAQ.txt ../html/usermanual.html ../txt/usermanual.txt
# ../txt/adminmanual.txt: adminmanual.sgml
sgml2txt adminmanual.sgml
- mv adminmanual.txt ../txt/
# ../html/adminmanual.html: adminmanual.sgml
sgml2html adminmanual.sgml
# ../html/spiderFAQ.html: spiderFAQ.sgml
sgml2txt spiderFAQ.sgml
- mv spid*.txt ../txt
# ../html/spiderFAQ.html: spiderFAQ.sgml
sgml2html spiderFAQ.sgml
+
+# ../html/usermanual.html: usermanual.sgml
+ sgml2html usermanual.sgml
+
+# ../txt/usermanual.txt: usermanual.sgml
+ sgml2txt usermanual.sgml
+
perl -pi.bak -e 's|</HEAD>|<link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">\n</HEAD>|' *.html
mv *.html ../html
+ mv *.txt ../txt
rm -f *.bak
DX:3:respawn:/bin/su -c "/usr/bin/perl -w /spider/perl/cluster.pl" sysop >/dev/tty7
</verb></tscreen>
+<P>
+This line works fine for RedHat and SuSE distributions. The line required for
+Slackware distributions is slightly different. My thanks to Aurelio, PA3EZL for
+this information.
+
+<tscreen><verb>
+DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
+</verb></tscreen>
+
<P>
This will automatically start DXSpider on tty7 (ALT-F7) on bootup and restart
it should it crash for any reason.
--- /dev/null
+<!doctype linuxdoc system>
+
+<article>
+
+<!-- Title information -->
+
+<title>The DXSpider User Manual
+<author>Ian Maude, G0VGS, (ianmaude@btinternet.com)
+<date>Version 1.0, March 2001
+<abstract>
+A complete reference for users of the DXSpider DXCluster program.
+</abstract>
+
+<!-- Table of contents -->
+<toc>
+
+<!-- Begin the document -->
+
+<sect>Introduction
+
+<sect1>What is a DX Cluster?
+
+<p>
+A DX Cluster is a packet node where DX chasers on any band or mode can
+post rare or interesting stations that they have worked or heard. Of
+course other people are doing the same thing too, so you can find new
+DX as well as telling others about the stations you have worked.
+Clusters tend to be linked to each other so that the amount of people
+using them is increased, thereby increasing the amount of posted DX.
+Other information can be found on clusters such as on-line call books,
+mail etc. You can talk to other stations connected to the cluster
+network too, in real time, whether at the node you are logged into or
+on another node connected to the network. You can also use converse
+mode, where several stations can talk to each other in the same way.
+Of course, the DX is still posted to you all the while!
+
+<sect1>So what is DXSpider?
+
+<p>
+PacketCluster nodes have been around since roughly 1985. The original
+PacketCluster idea came from Dick Newell, AK1A, and ran under DOS.
+In about 1992 Dick stopped the development of the PacketCluster
+software for amateur radio. Many systems are still using this
+relatively old DOS software today.
+
+There are several new compatible cluster programs around now,
+including DXSpider. DXSpider is a clone of PacketCluster software that runs
+under the Linux operating system. Linux is fast becoming the choice
+for amateur radio stations because of it's flexibility, reliability
+and the lack of the memory limitations of DOS. Linux supports
+multitasking and is also multiuser. It has support for AX25, ROSE,
+NetROM and TCPIP built in, making it the ideal choice for amateur
+radio. It is also totally free!
+
+DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
+exercise in perl programming. It has developed rapidly and today is a
+very powerful cluster program. It was designed to be totally compatible
+with the AK1A program, although several commands have been extended to
+try and improve functionality.
+
+This manual is designed to help you become familiar with the commands
+that DXSpider supports and to help you get the best from the program so
+you can enjoy working that rare DX! As DXSpider is being improved all the
+time, commands will be added as time goes by, so make sure you have
+the most upto date version of this manual. The latest version will
+always be included with the cluster program so if you are unsure, simply
+ask your sysop. The manual will also be available on the wesite.
+
+
+<sect>Logins and logouts.
+
+<p>
+You might not think that there is a lot of point of including a
+section on how to log in and out of DXSpider. However, you would be
+suprised at the difficulties some people have in simply getting in
+and out of the cluster!
+
+There are several ways a login might be achieved, dependant on how
+the sysop has DXSpider configured. It is impossible for me to cover all
+variations but here are the basic ones.
+
+<sect1>AX25 logins.
+
+<p>
+Simplicity itself. The usual <bf>CONNECT</bf> command will log you straight
+into the cluster and you will not have to do anything else.
+Obviously, you will have to connect to the correct callsign. Some
+nodes use an SSID with their call so you would have to add that.
+
+<bf>Examples:</bf>
+
+<tscreen><verb>
+connect GB7MBC
+connect GB7MBC-1
+</verb></tscreen>
+
+<sect1>Netrom logins.
+
+<p>
+There are several possibilities here, dependant on how the sysop has
+configured his system. If you are connecting via netrom then you are
+most probably connecting from another station. Listing the nodes in
+that station with the <bf>NODES</bf> command will tell you what callsign
+or netrom alias to connect to. Then just issue the connect command
+from there. It is possible that the netrom alias may connect you to
+a node with an alias for the cluster, such as DXC. Just type this
+and you will be connected.
+
+<bf>Example:</bf>
+<tscreen><verb>
+connect MBCDX
+</verb></tscreen>
+
+<sect1>Telnet logins.
+
+<p>
+Because DXSpider runs under the Linux operating system, it is possible to
+make a direct telnet connection into the cluster. With telnet
+connections, the source callsign is not seen by DXSpider, so you will be
+asked to login with your callsign.
+To telnet to DXSpider, you would connect to a specific port. There is no
+standard at the moment for a cluster telnet port but ask the sysop if
+you are unsure.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+telnet gb7mbc 8000
+</verb></tscreen>
+
+All the above are possible ways of connecting to a DXSpider cluster. You
+may have some or all of these available to you. There may be one or
+two additional ways to connect dependant on the network local to you.
+However I am sure you get the idea.
+
+<sect1>Logouts.
+
+<p>
+Logging out can be done by simply issuing the standard <bf>BYE</bf>
+command.
+
+You could also send a disconnect if you are using AX25, or a <bf>CLOSE</bf>
+command if you are connected via telnet.
+If you do not log out gracefully using one of the above commands,
+you may find you are unable to get a full connect next time. This
+may also happen if a NETRom connection drops. You may get connected,
+but nothing else will happen because the program thinks you are still
+connected and will not let you connect twice under the same call.
+However you could reconnect by adding a number to the end of your call,
+for example G0YLM2.
+This can be done by either altering your MYCALL setting in the TNC or
+by altering your program configuration.
+
+
+<sect>Setting your personal details.
+
+<p>
+Once logged in to the cluster, you should set your details so that
+anybody who wishes to contact you can find out who and where you are.
+There are four items to set, your name, qth, location and home node.
+Setting these details also allows the use of the SHOW/HEADING and
+SHOW/SUN commands from within the cluster. Unless you set your QTH
+and location, these commands cannot function.
+Once you have set your name, DXSpider will greet you with it next time
+you login. Your QTH setting is where you live and it is a good idea
+to add your locator to this as the location setting is converted to
+latitude and longitude once inputted. You can actually set your location
+in latitude/longitude or as a locator. Setting your home node will
+tell the program where you wish mail to be sent to you.
+
+<bf>Examples:</bf>
+
+<tscreen><verb>
+set/name Ian
+set/qth Morecambe, Lancashire IO84NB
+set/location 48 34 n 12 12 e
+set/qra IO84NB
+set/home gb7mbc
+</verb></tscreen>
+
+<sect>Getting and posting DX.
+
+<p>
+When all is said and done, this is the main function of a DX cluster.
+In its simplest form you can just connect to the node and you will
+start to receive DX spots almost immediately! You can check on
+recent postings in either a general manner or on a particular band or
+mode. You can even check DX by callsign or a fragment of a callsign.
+Of course, once you get the hang of things, it is expected that you
+start posting some yourself! After all, there would be no clusters
+if people did not post DX and you get the added thrill of the hunt!
+
+<sect1>Receiving DX.
+
+<p>
+As we have already said, it is possible just to connect to the
+cluster and you will receive spots automatically. However, you may
+wish to check on spots just posted. Maybe you wish to see if a
+particular band is open or if a certain callsign is active, perhaps a
+DXpedition. The command to do this is <bf>SHOW/DX</bf>. Without any
+other arguments, this command will output the last 10 spots
+posted. It is possible to look at more than this, for example the
+last 20 or 50 spots, by adding the number to the command. You can
+make it even more specific by adding a band in either wavelength or
+frequency, and/or any additional information such as QSL details.
+
+<bf>Examples:</bf>
+
+<tscreen><verb>
+show/dx
+show/dx 5
+show/dx 20
+</verb></tscreen>
+
+will show the last 10, 5 and 20 spots received by the cluster
+respectively.
+
+<bf>Examples</bf>
+
+<tscreen><verb>
+show/dx on 20m
+show/dx 10 on 20m
+show/dx 20 on 20m
+</verb></tscreen>
+
+will show the last 5, 10 or 20 spots on 20 metres only.
+
+It is also possible to check for certain callsigns, or fragments of
+callsigns in the same way.
+
+<bf>Examples:</bf>
+
+<tscreen><verb>
+show/dx g0vgs
+show/dx 10 g0vgs
+</verb></tscreen>
+
+would show the last 5 or 10 dx spots containing the callsign g0vgs.
+
+<p>
+You can check for DX by offset and also by specifying a comment to
+search for.
+
+<bf>Examples:</bf>
+
+<tscreen><verb>
+show/dx 30-40
+show/dx 14000-14033
+show/dx iota
+</verb></tscreen>
+
+would show the spots that arrived between 30 and 40 spots ago and any
+spots with the word <em>iota</em> in the comment field. The case of
+the comment is not important.
+
+Checking DX posted on a certain day is possible too. All you have
+to do here is to specify how many days ago it was like this ...
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+show/dx day 30
+</verb></tscreen>
+
+It is of course possible to specify multiple arguments.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+show/dx 20 prefix 9a on vhf day 30
+</verb></tscreen>
+
+This would show the last 20 spots posted by or about calls with the prefix
+9a on vhf 30 days ago.
+
+As you can see the <bf>SHOW/DX</bf> command is very flexible, so if you are
+not sure whether something will work or not, try it and see! More
+information can be found in the Command Set section.
+
+<sect1>Posting DX.
+
+<p>
+To post DX you use the <bf>DX</bf> command. The syntax is shown below.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+dx (frequency) (callsign) (remarks)
+</verb></tscreen>
+
+Where frequency is in kilohertz and the callsign is the callsign of
+the station you have worked or heard, (ie not your own callsign!).
+The remarks section allows you to add information like the operators
+name or perhaps a location. Actually DXSpider will allow the frequency
+and callsign fields to be entered in any order.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+dx 14004 pa3ezl OP Aurelio 599
+</verb></tscreen>
+
+In fact, all the following will give the same result...
+
+<tscreen><verb>
+dx 14004 pa3ezl OP Aurelio 599
+dx pa3ezl 14004 OP Aurelio 599
+dx pa3ezl 14.004 OP Aurelio 599
+</verb></tscreen>
+
+This posting, or callout as it is known, will be forwarded to all
+other connected stations both at the cluster you are connected to and
+other active clusters in the network. The callout will also be sent
+to you as proof of receipt.
+
+<sect>Headings and propagation
+
+<p>
+There are three commands in DXSpider to help you get the best DX possible.
+These are <bf>SHOW/SUN</bf>, <bf>SHOW/MOON</bf> and
+<bf>SHOW/HEADING</bf>. These commands will only work for you if you
+have entered your personal details. They use your entered location as
+a reference, so if you have not entered it or have entered it incorrectly
+they will not return the correct information.
+
+<sect1>Sun
+
+<p>
+The <bf>SHOW/SUN</bf> command can be used in three different ways. It
+can be used to show sunrise and sunset times for your own station, a
+particular callsign or a prefix.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+show/sun
+</verb></tscreen>
+
+The output from this would look something like this ..
+
+<tscreen><verb>
+sh/sun Location Rise Set Azim Elev
+G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
+</verb></tscreen>
+
+<tscreen><verb>
+sh/sun 5b4
+</verb></tscreen>
+
+would look like this ...
+
+<tscreen><verb>
+sh/sun 5b4 Location Rise Set Azim Elev 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
+</verb></tscreen>
+
+You can also specify multiple arguments like this ...
+
+<tscreen><verb>
+sh/sun gw4veq 5b4ab zs
+</verb></tscreen>
+
+and then the output would look like this ...
+
+<tscreen><verb>
+sh/sun gw4veq 5b4ab zs
+Location Rise Set Azim Elev
+GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9 5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
+ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
+ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
+ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
+</verb></tscreen>
+
+<sect1>Moon
+
+<p>
+The <bf>SHOW/MOON</bf> command works in the same way as the
+<bf>SHOW/SUN</bf> command. This program however, calculates the
+rise and set times of the moon for a prefix or callsign, together
+with the current azimuth and elevation of the sun at these
+locations.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+show/moon ea
+</verb></tscreen>
+
+The output from this command would look like this ..
+
+<tscreen><verb>
+sh/moon ea
+Location Rise Set Azim Elev RGain dB
+EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
+</verb></tscreen>
+
+You can see that the output is similar to the <bf>SHOW/SUN</bf>
+command, with slightly different fields.
+
+<sect1>Heading
+
+<p>
+The <bf>SHOW/HEADING</bf> command works in the same way as the
+<bf>SHOW/SUN</bf> and <bf>SHOW/MOON</bf> commands but outputs beam
+headings for a specified callsign or prefix. Reciprocal beam headings
+are also calculated.
+
+<bf>Example</bf>
+
+<tscreen><verb>
+show/heading zl
+</verb></tscreen>
+
+The output from this command would look like this ..
+
+<tscreen><verb>
+sh/heading zl
+ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
+ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
+ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
+ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
+</verb></tscreen>
+
+<sect>Announcements.
+
+<sect1>Making announcements.
+
+<p>
+Occasionally, you may wish to post something that does not fall into
+the normal parameters for a DX callout. You may wish to tell
+everybody connected that 10 FM is open for example, or ask if anyone
+knows the QSL manager for a certain callsign etc. You can do this
+using the <bf>ANNOUNCE</bf> command.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+announce 10 FM is open in IO84NB to europe.
+</verb></tscreen>
+
+That would let everyone know locally that this was the case, however
+it would not be forwarded to other nodes connected. To send
+announcements to other connected nodes as well, you would use the
+<bf>FULL</bf> extension.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+announce full Anyone seen EA7WA today?
+</verb></tscreen>
+
+Be cautious in your use of announce full. There are many other tools
+available to get the information you require and the judicious use of
+this command is frowned upon as it creates a great deal of traffic
+across the network.
+
+<sect1>Listing announcements.
+
+<p>
+You can list previous announcements in the standard format with the
+<bf>SHOW</bf> command. As before you can list just the last 5 or as
+many as you wish.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+show/announcements
+show/announcements 10
+</verb></tscreen>
+
+<sect>Nodes and users.
+
+<p>
+You can check which nodes are connected in the network, who is
+logged on locally, who is logged on at all the nodes or even
+just one node in particular. This is handy if you wish to see whether
+a friend is connected at the node they use. To see who is connected
+to the nodes, the <bf>SHOW/CONFIGURATION</bf> command is used.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+show/configuration
+show/configuration/nodes
+show/configuration (node_call)
+show/configuration (prefix)
+</verb></tscreen>
+
+The first of our three examples would output something like this,
+
+<verb>
+sh/c
+Node Callsigns
+EI5TCR (7 users)
+GB7ADX
+GB7BAA G4FPV G8TIC
+GB7BIG (GD0TEP) GD3UMW
+GB7BPQ (G0INA) G0RCI G3AKU G3OCA
+(GB7CDX) G3JNB G4ALR
+GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
+ G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
+ ON7WP
+GB7DXA G0RDI G8SJP
+GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
+ G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
+GB7DXE G1NNB
+(GB7DXG) GU6EFB GU7DHI
+GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
+ G4XQY G7GAN
+GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
+ M0BCT M1EMF
+</verb>
+
+You will notice that EI5TCR is showing only that it has 7 users and not
+giving the actual callsigns. This means that this node is on a limited
+protocol of some kind, probably because of a contest situation where
+slow radio links can block up and fail if too much information is sent
+between nodes.
+
+The second example would just show the nodes connected in the
+network, like this,
+
+<verb>
+sh/c/n
+Node Callsigns
+GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
+ GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
+ GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
+ GB7YDX KL7G N2TLY (ON0DXK)
+GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
+GB7MBC
+PA4AB-14 PA4AB-14
+PI4TUE-8 PI4TUE-8
+</verb>
+
+If we insert the node_call pi4tue-8 into the third example, then
+this would be the output,
+
+<verb>
+Node Callsigns
+PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
+ F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
+ ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
+ PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
+ YT1XX
+</verb>
+
+As you can see, only the users of the requested node are shown.
+
+You can also use a prefix to show only a group of nodes. For example
+you may only wish to see who is connected to the nodes in the UK. To
+do this simply use a prefix like this ...
+
+<verb>
+show/configuration gb7
+</verb>
+
+To show the locally connected users, the <bf>SHOW/USERS</bf> command is
+used
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+show/users
+</verb></tscreen>
+
+The output of this command would look like this,
+
+<verb>
+Callsigns connected to GB7MBC
+G0JHC G0NEI G0VGS G0VGS-2 G0YLM
+G3JAG G3OWO G3UEU
+</verb>
+
+<sect>Talk mode.
+
+<p>
+You can send a single comment or start a dedicated talk session to
+another user by using the <bf>TALK</bf> command.
+
+<p>
+Talk mode is used to send a one line comment or greeting to a
+specific user connected either at your node or another in the
+network. You can also enter into a dedicated talk session with
+another user. Talks will be automatically forwarded to other nodes
+if the station you are talking to is not connected locally.
+You can find out who is connected by using the
+<bf>SHOW/CONFIGURATION</bf> command, (described earlier).
+
+<bf>Examples:</bf>
+
+<tscreen><verb>
+talk g0rdi Having a good day Iain?
+</verb></tscreen>
+
+This example would send the line "Having a good day Iain?" to the
+user g0rdi but would leave you in normal mode.
+
+<tscreen><verb>
+talk g0rdi
+Entering Talkmode, /EX to end, /<cmd> to run a command
+Talk (G0RDI)>
+</verb></tscreen>
+
+As you can see, you can still run commands whilst in talk mode.
+Simply prefix the command with a / like /sh/dx and you will get
+the expected output.
+If the user is connected to another node, you may have to use a
+slightly extended version of the <bf>TALK</bf> command.
+
+<tscreen><verb>
+talk g0rdi > gb7djk
+</verb></tscreen>
+
+To exit talk mode, you issue the command <bf>/ex</bf>.
+
+Whilst in talk mode you will still receive DX spots. This means that
+you can chat to a friend whilst working DX.
+
+<sect>Mail.
+
+<p>
+You can send and receive both personal mail and bulletins with DXSpider
+quite easily.
+
+<sect1>The "directory" command.
+
+<p>
+To list mail you would use the <bf>DIRECTORY</bf> command. On its
+own, this command will output the last ten messages received by the
+node, either to or from yourself or bulletins such as "DX" and "ALL".
+As with other commands you can display more by specifying a number
+with the command. You should be aware that Spider will accept
+these commands by separating with either a slash or a space, so
+<em>dir new</em> and <em>dir/new</em> work in the same way.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+directory
+directory/20
+directory 20
+</verb></tscreen>
+
+Of course most of the time you will only want to list new mail sent
+to you personally since your last login. However you might also like
+to check for general mail received by the node. In fact if there is
+new mail for you, the cluster will tell you when you login. You will
+also be informed if new mail arrives for you during the time you are
+logged in.
+Mail is not only sent to callsigns though. Mail can also be sent to
+subjects like "all" or "local" or "dx" etc. You can treat these
+bulletins in the same way as personal mail with the directory
+command.
+
+<bf>Examples:</bf>
+
+<tscreen><verb>
+directory/new
+directory/own
+directory/own/10
+directory/all
+directory/from <call>
+</verb></tscreen>
+
+The last option will only show mail from a callsign if it was sent to
+you personally or was sent as a bulletin. There are some additional
+commands and these can be found in the DXSpider Command Reference section.
+
+<sect1>Reading mail.
+
+<p>
+The output of the <bf>DIRECTORY</bf> command could be something like
+this.
+
+<verb>
+dir
+ 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
+ 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
+ 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
+ 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
+ 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
+ 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
+ 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
+ 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
+ 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
+ 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
+ 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
+</verb>
+
+The first column is the actual message number. If the message is a
+personal one to you, you will see a letter 'p' after this number. If
+the message has been read, there will be a '-' between the message
+number and the 'p'. This only works for personal messages. The next
+column shows the file size of the message. The third column shows the
+address the message was sent to and the next column shows who sent it.
+The rest is fairly self-explanatory.
+
+Reading a message is as simple as typing read, followed by the
+message number that you wish to read.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+read 25
+</verb></tscreen>
+
+will read message number 25. However the mail will be displayed in it's
+entirety unless you specify a page length. You can set your page length
+to any number you like and when the message reaches that number of lines
+you will get a prompt giving you options.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+set/page 20
+</verb></tscreen>
+
+
+<sect1>Sending mail.
+
+<p>
+Sending mail is done in the time honoured way. First you specify
+a recipient for the message, then you will be prompted for a subject.
+Once you have done this you will be asked to type your message.
+Please remember that there is no automatic word wrap, so unless you
+are using a client that wraps lines automatically, remember to hit
+return at the end of each line.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+send m0azm
+Enter Subject (30 characters):
+See you Thursday
+Enter Message /EX to send or /ABORT to exit
+Hi Ian,
+Just a quick note to say that I can make Thursday after all. The
+appointment I had has cancelled so we are go!
+Cheers
+Ian
+</verb></tscreen>
+
+At this point you can either hit return and enter /ex to send the
+message or use /abort at any time to abort it. You can now display
+the message in the normal way. There are several send options and
+these are listed in the Command Set section. These include sending
+mail to several recipients and asking for a return receipt.
+
+
+<sect1>Replying to mail.
+
+<p>
+If mail is addressed to you or to a bulletin address, you can use the
+<bf>REPLY</bf> command to reply to it. Using this command, the
+subject will be automatically set for you as "Re: subject", whatever
+the subject was.
+
+<bf>Example:</bf>
+
+<tscreen><verb>
+reply 2500
+</verb></tscreen>
+
+<sect1>Deleting mail
+
+To delete a message, you use the <em>delete</em> command.
+You can only delete messages sent to or received by yourself.
+Bulletins are dealt with automatically or by the sysop.
+
+<sect>Filtering (From version 1.45)
+
+<sect1>General filter rules
+
+<P>
+Upto v1.44 it was not possible for the user to set their own filters. From
+v1.45 though that has all changed. It is now possible to set filters for just
+about anything you wish. If you have just updated from an older version of
+DXSpider you will need to update your new filters. You do not need to do
+anything with your old filters, they will be renamed as you update.
+
+<P>
+There are 3 basic commands involved in setting and manipulating filters. These
+are <em>accept</em>, <em>reject</em> and <em>clear</em>. First we will look
+generally at filtering. There are a number of things you can filter in the
+DXSpider system. They all use the same general mechanism.
+
+<P>
+In general terms you can create a 'reject' or an 'accept' filter which can have
+up to 10 lines in it. You do this using, for example ...
+
+<tscreen><verb>
+accept/spots .....
+reject/spots .....
+</verb></tscreen>
+
+where ..... are the specific commands for that type of filter. There are
+filters for spots, wwv, announce, wcy and (for sysops) connects. See each
+different accept or reject command reference for more details.
+
+There is also a command to clear out one or more lines in a filter. They are ...
+
+<tscreen><verb>
+clear/spots 1
+clear/spots all
+</verb></tscreen>
+
+There is clear/xxxx command for each type of filter.
+
+<P>
+and you can check that your filters have worked by the command ...
+
+<tscreen><verb>
+show/filter
+</verb></tscreen>
+
+<P>
+For now we are going to use spots for the examples, but you can apply the same
+principles to all types of filter.
+
+<sect1>Types of filter
+
+<P>
+There are two main types of filter, <em>accept</em> or <em>reject</em>. You
+can use either to achieve the result you want dependent on your own preference
+and which is more simple to do. It is pointless writing 8 lines of reject
+filters when 1 accept filter would do the same thing! Each filter has 10
+lines (of any length) which are tried in order. If a line matches then the
+action you have specified is taken (ie reject means ignore it and accept
+means take it)
+
+<P>
+If you specify reject filters, then any lines that arrive that match the filter
+will be dumped but all else will be accepted. If you use an accept filter,
+then ONLY the lines in the filter will be accepted and all else will be dumped.
+For example if you have a single line <em>accept</em> filter ...
+
+<tscreen><verb>
+accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</verb></tscreen>
+
+then you will <em>ONLY</em> get VHF spots <em>from</em> or <em>to</em> CQ zones
+14, 15 and 16.
+
+<P>
+If you set a reject filter like this ...
+
+<tscreen><verb>
+reject/spots on hf/cw
+</verb></tscreen>
+
+Then you will get everything <em>EXCEPT</em> HF CW spots. You could make this
+single filter even more flexible. For example, if you are interested in IOTA
+and will work it even on CW even though normally you are not interested in
+CW, then you could say ...
+
+<tscreen><verb>
+reject/spots on hf/cw and not info iota
+</verb></tscreen>
+
+But in that case you might only be interested in iota and say:-
+
+<tscreen><verb>
+accept/spots not on hf/cw or info iota
+</verb></tscreen>
+
+which achieves exactly the same thing. You should choose one or the other
+until you are comfortable with the way it works. You can mix them if you
+wish (actually you can have an accept AND a reject on the same line) but
+don't attempt this until you are sure you know what you are doing!
+
+<P>
+You can arrange your filter lines into logical units, either for your own
+understanding or simply convenience. Here is an example ...
+
+<tscreen><verb>
+reject/spots 1 on hf/cw
+reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+</verb></tscreen>
+
+What this does is to ignore all HF CW spots and also rejects any spots on VHF
+which don't either originate or spot someone in Europe.
+
+<P>
+This is an example where you would use a line number (1 and 2 in this case), if
+you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
+This make it easier to see just what filters you have set. It also makes it
+more simple to remove individual filters, during a contest for example.
+
+<P>
+You will notice in the above example that the second line has brackets. Look
+at the line logically. You can see there are 2 separate sections to it. We
+are saying reject spots that are VHF or above <em>APART</em> from those in
+zones 14, 15 and 16 (either spotted there or originated there). If you did
+not have the brackets to separate the 2 sections, then Spider would read it
+logically from the front and see a different expression entirely ...
+
+<tscreen><verb>
+(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+</verb></tscreen>
+
+The simple way to remember this is, if you use OR - use brackets. Whilst we are
+here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'.
+
+As mentioned earlier, setting several filters can be more flexible than
+simply setting one complex one. Doing it in this way means that if you want
+to alter your filter you can just redefine or remove one or more lines of it or
+one line. For example ...
+
+<tscreen><verb>
+reject/spots 1 on hf/ssb
+</verb></tscreen>
+
+would redefine our earlier example, or
+
+<tscreen><verb>
+clear/spots 1
+</verb></tscreen>
+
+To remove all the filter lines in the spot filter ...
+
+<tscreen><verb>
+clear/spots all
+</verb></tscreen>
+
+<sect1>Filter options
+
+<P>
+You can filter in several different ways. The options are listed in the
+various helpfiles for accept, reject and filter.
+
+<sect1>Advanced filtering
+
+<P>
+Once you are happy with the results you get, you may like to experiment.
+
+<P>
+The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
+can be written with a mixed filter, for example ...
+
+<tscreen><verb>
+rej/spot on hf/cw
+acc/spot on 0/30000
+acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+</verb></tscreen>
+
+Note that the first filter has not been specified with a number. This
+will automatically be assumed to be number 1. In this case, we have
+said <em>reject all HF spots in the CW section of the bands but accept
+all others at HF. Also accept anything in VHF and above spotted in or
+by operators in the zones 14, 15 and 16</em>. Each filter slot actually
+has a 'reject' slot and an 'accept' slot. The reject slot is executed
+BEFORE the accept slot.
+
+<P>
+It was mentioned earlier that after a reject test that doesn't match, the
+default for following tests is 'accept', the reverse is true for 'accept'.
+In the example what happens is that the reject is executed first, any non
+hf/cw spot is passed to the accept line, which lets through everything
+else on HF. The next filter line lets through just VHF/UHF spots from EU.
+
+
+<sect>Hints, tips and common questions.
+
+<p>
+<bf/Q./These commands seem very long! Can I shorten them?
+
+<bf/A./Of course you can and the usual abbreviations work. If you
+are unsure, try it.
+
+<bf/Q./I am not sure if this command is correct. Can I cause any
+harm if I try it?
+
+<bf/A./Do not be afraid to try a command to see if it will work,
+at the worst you will get an error message. If you require any
+help on a command, just type help followed by the command you
+want help on. Look at the "DXSpider Command Reference" section to see
+what help can be found.
+
+<bf/Q./How should I use the announce command?
+
+<bf/A./With respect. Use the command by all means, but please
+only use the "full" extension if absolutely necessary. It can
+create a LOT of messages passing between clusters.
+
+<bf/Q./I like to be working in the shack while logged into the
+cluster but I can't be looking at the screen all the time. How
+can I be alerted when anything happens?
+
+<bf/A./Use the <bf>SET/BEEP</bf> command. You can find information
+on this in the "DXSpider Command Reference" section.
+
+<bf/Q./I keep getting disconnected from the cluster, what is
+happening and how can I stop it?
+
+<bf/Q./I got disconnected from the cluster and now I can't log
+back in again. What is wrong?
+
+<bf/A./Probably the cluster thinks you are still logged on and
+will not let you reconnect using the same call to prevent loops.
+Try logging on again adding an ssid to your callsign as DXSpider
+treats G0YLM and G0YLM-1 as different users.
+
+<bf/Q./I notice that all the commands are shown in lower case in
+the main section of this manual, but in upper case in the "DXSpider
+Command Reference" section. Why is that?
+
+<bf/Q./How do I know if I have got the latest version of this
+user manual?
+
+<bf/A./The latest and greatest will always be on the Website. It will
+also be included with every release of DXSpider. As always, if unsure,
+ask your sysop what version number is the latest.
+
+<sect>The DXSpider command reference
+
+<P>
+Below is a complete list of commands available from the cluster prompt.
+These are listed below in alphabetical order.
+
+<sect1>accept/announce
+
+<P>
+<tt>
+<bf>accept/announce [0-9] <pattern></bf> Set an accept filter
+ line for announce
+</tt>
+
+<P>
+Create an 'accept this announce' line for a filter.
+
+An accept filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+
+You can use any of the following things in this line:-
+
+<tscreen><verb>
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+</verb></tscreen>
+
+some examples:-
+
+<tscreen><verb>
+ acc/ann dest 6MUK
+ acc/ann 2 by_zone 14,15,16
+ (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+</verb></tscreen>
+
+or
+
+<tscreen><verb>
+ acc/ann by G,M,2
+</verb></tscreen>
+
+This filter would only allow announces that were posted buy UK stations.
+You can use the tag 'all' to accept everything eg:
+
+<tscreen><verb>
+ acc/ann all
+</verb></tscreen>
+
+but this probably for advanced users...
+
+<sect1>accept/spots
+
+<P>
+<tt>
+<bf>accept/announce [0-9] <pattern></bf> Set an accept filter
+line for spots
+</tt>
+
+<P>
+Create an 'accept this spot' line for a filter.
+
+<P>
+An accept filter line means that if the spot matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+
+You can use any of the following things in this line:-
+
+<tscreen><verb>
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+</verb></tscreen>
+
+<P>
+For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: freq HF (but don't get
+too hung up about that)
+
+some examples:-
+
+<tscreen><verb>
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</verb></tscreen>
+
+You can use the tag 'all' to accept everything, eg:
+
+<tscreen><verb>
+ acc/spot 3 all
+</verb></tscreen>
+
+but this probably for advanced users...
+
+<sect1>accept/wcy
+
+<P>
+<tt>
+<bf>accept/wcy [0-9] <pattern></bf> set an accept WCY filter
+</tt>
+
+<P>
+It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+<tscreen><verb>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</verb></tscreen>
+
+<P>
+There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+
+This command is really provided for future use.
+
+See HELP FILTER for information.
+
+<sect1>accept/wwv
+
+<P>
+<tt>
+<bf>accept/wwv [0-9] <pattern></bf> Set an accept WWV filter
+</tt>
+
+<P>
+It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+<tscreen><verb>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</verb></tscreen>
+
+for example
+
+<tscreen><verb>
+ accept/wwv by_zone 4
+</verb></tscreen>
+
+is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+
+See HELP FILTER for information.
+
+<sect1>announce
+
+<P>
+<tt>
+<bf>announce <text></bf> Send an announcement to local users
+</tt>
+
+<P>
+Send an announcement to LOCAL users only, where <text> is the text
+of the announcement you wish to broadcast
+
+<sect1>announce full
+
+<P>
+<tt>
+<bf>announce full <text></bf> Send an announcement cluster wide
+</tt>
+
+<P>
+This command will send your announcement across the whole cluster
+network.
+
+<sect1>apropos
+
+<P>
+<tt>
+<bf>apropos <string></bf> Search the help database
+</tt>
+
+<P>
+Search the help database for <string> (it isn't case sensitive),
+and print the names of all the commands that may be relevant.
+
+<sect1>bye
+
+<P>
+<tt>
+<bf>bye</bf> Exit from the cluster
+</tt>
+
+<P>
+This will disconnect you from the cluster
+
+<sect1>clear/spots
+
+<P>
+<tt>
+<bf>clear/spots [1|all]</bf> Clear a spot filter line
+</tt>
+
+<P>
+This command allows you to clear (remove) a line in a spot filter or to
+remove the whole filter.
+
+If you have a filter:-
+
+<tscreen><verb>
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</verb></tscreen>
+
+and you say:-
+
+<tscreen><verb>
+ clear/spot 1
+</verb></tscreen>
+
+you will be left with:-
+
+<tscreen><verb>
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+</verb></tscreen>
+
+If you do:
+
+<tscreen><verb>
+ clear/spot all
+</verb></tscreen>
+
+the filter will be completely removed.
+
+<sect1>dbavail
+
+<P>
+<tt>
+<bf>dbavail</bf> Show a list of all the databases in the system
+</tt>
+
+<P>
+The title says it all really, this command lists all the databases defined
+in the system. It is also aliased to SHOW/COMMAND.
+
+<sect1>dbshow
+
+<P>
+<tt>
+<bf>dbshow <dbname> <key></bf> Display an entry, if it exists,
+in a database
+</tt>
+
+<P>
+This is the generic user interface to the database to the database system.
+It is expected that the sysop will add an entry to the local Aliases file
+so that users can use the more familiar AK1A style of enquiry such as:
+
+<tscreen><verb>
+ SH/BUCK G1TLH
+</verb></tscreen>
+
+but if he hasn't and the database really does exist (use DBAVAIL or
+SHOW/COMMAND to find out) you can do the same thing with:
+
+<tscreen><verb>
+ DBSHOW buck G1TLH
+</verb></tscreen>
+
+<sect1>directory
+
+<P>
+<tt>
+<bf>directory</bf> List messages<newline>
+<bf>directory all</bf> List all messages<newline>
+<bf>directory own</bf> List your own messages<newline>
+<bf>directory new</bf> List all new messages<newline>
+<bf>directory to <call></bf> List all messages to <call><newline>
+<bf>directory from <call></bf> List all messages from <call><newline>
+<bf>directory subject <string></bf> List all messages with <string>
+in subject<newline>
+<bf>directory <nn></bf> List last <nn> messages<newline>
+<bf>directory <from>-<to></bf> List messages <from> message <to> message <newline>
+</tt>
+
+<P>
+List the messages in the messages directory.
+
+If there is a 'p' one space after the message number then it is a
+personal message. If there is a '-' between the message number and the
+'p' then this indicates that the message has been read.
+
+You can use shell escape characters such as '*' and '?' in the <call>
+fields.
+
+You can combine some of the various directory commands together eg:-
+
+<tscreen><verb>
+ DIR TO G1TLH 5
+or
+ DIR SUBJECT IOTA 200-250
+</verb></tscreen>
+
+You can abbreviate all the commands to one letter and use ak1a syntax:-
+
+<tscreen><verb>
+ DIR/T G1* 10
+ DIR/S QSL 10-100 5
+</verb></tscreen>
+
+<sect1>dx
+
+<P>
+<tt>
+<bf>dx [by <call>] <freq> <call> <remarks></bf> Send a DX spot
+</tt>
+
+<P>
+This is how you send a DX Spot to other users. You can, in fact, now
+enter the <freq> and the <call> either way round.
+
+<tscreen><verb>
+ DX FR0G 144.600
+ DX 144.600 FR0G
+ DX 144600 FR0G
+</verb></tscreen>
+
+will all give the same result. You can add some remarks to the end
+of the command and they will be added to the spot.
+
+<tscreen><verb>
+ DX FR0G 144600 this is a test
+</verb></tscreen>
+
+You can credit someone else by saying:-
+
+<tscreen><verb>
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
+</verb></tscreen>
+
+The <freq> is compared against the available bands set up in the
+cluster. See SHOW/BANDS for more information.
+
+<sect1>help
+
+<P>
+<tt>
+<bf>help <cmd></bf> Get help on a command
+</tt>
+
+<P>
+All commands can be abbreviated, so SHOW/DX can be abbreviated
+to SH/DX, ANNOUNCE can be shortened to AN and so on.
+
+Look at the APROPOS <string> command which will search the help database
+for the <string> you specify and give you a list of likely commands
+to look at with HELP.
+
+<sect1>kill
+
+<P>
+<tt>
+<bf>kill <msgno> [<msgno> ..]</bf> Delete a message
+from the local system
+</tt>
+
+<P>
+Delete a message from the local system. You will only be able to
+delete messages that you have originated or been sent (unless you are
+the sysop).
+
+<sect1>links
+
+<P>
+<tt>
+<bf>links</bf> Show which nodes are physically connected
+</tt>
+
+<P>
+This is a quick listing that shows which links are connected and
+some information about them. See WHO for a list of all connections.
+
+<sect1>read
+
+<P>
+<tt>
+<bf>read</bf> Read the next unread personal message addressed to you<newline>
+<bf>read <msgno></bf> Read the specified message<newline>
+</tt>
+
+<P>
+You can read any messages that are sent as 'non-personal' and also any
+message either sent by or sent to your callsign.
+
+<sect1>reject/announce
+
+<P>
+<tt>
+<bf>reject/announce [0-9] <pattern></bf> Set a reject filter
+for announce
+</tt>
+
+<P>
+Create an 'reject this announce' line for a filter.
+
+An reject filter line means that if the announce matches this filter it is
+passed onto the user. See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+
+You can use any of the following things in this line:-
+
+<tscreen><verb>
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+</verb></tscreen>
+
+some examples:-
+
+<tscreen><verb>
+ rej/ann by_zone 14,15,16 and not by G,M,2
+</verb></tscreen>
+
+You can use the tag 'all' to reject everything eg:
+
+<tscreen><verb>
+ rej/ann all
+</verb></tscreen>
+
+but this probably for advanced users...
+
+<sect1>reject/spots
+
+<P>
+<tt>
+<bf>reject/spots [0-9] <pattern></bf> Set a reject filter
+line for spots
+</tt>
+
+<P>
+Create a 'reject this spot' line for a filter.
+
+A reject filter line means that if the spot matches this filter it is
+dumped (not passed on). See HELP FILTERS for more info. Please read this
+to understand how filters work - it will save a lot of grief later on.
+
+You can use any of the following things in this line:-
+
+<tscreen><verb>
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+</verb></tscreen>
+
+For frequencies, you can use any of the band names defined in
+SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+this is more efficient than saying simply: on HF (but don't get
+too hung up about that)
+
+some examples:-
+
+<tscreen><verb>
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+</verb></tscreen>
+
+You can use the tag 'all' to reject everything eg:
+
+<tscreen><verb>
+ rej/spot 3 all
+</verb></tscreen>
+
+but this probably for advanced users...
+
+<sect1>reject/wcy
+
+<P>
+<tt>
+<bf>reject/wcy [0-9] <pattern></bf> Set a reject WCY filter
+</tt>
+
+<P>
+It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+<tscreen><verb>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</verb></tscreen>
+
+There are no examples because WCY Broadcasts only come from one place and
+you either want them or not (see UNSET/WCY if you don't want them).
+
+This command is really provided for future use.
+
+See HELP FILTER for information.
+
+<sect1>reject/wwv
+
+<P>
+<tt>
+<bf>reject/wwv [0-9] <pattern></bf> Set a reject WWV filter
+</tt>
+
+<P>
+It is unlikely that you will want to do this, but if you do then you can
+filter on the following fields:-
+
+<tscreen><verb>
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+</verb></tscreen>
+
+for example
+
+<tscreen><verb>
+ reject/wwv by_zone 14,15,16
+</verb></tscreen>
+
+is probably the only useful thing to do (which will only show WWV broadcasts
+by stations in the US).
+
+See HELP FILTER for information.
+
+<sect1>reply
+
+<P>
+<tt>
+<bf>reply</bf> Reply (privately) to the last message that you have read<newline>
+<bf>reply <msgno></bf> Reply (privately) to the specified message<newline>
+<bf>reply B <msgno></bf> Reply as a Bulletin to the specified message<newline>
+<bf>reply NOPrivate <msgno></bf> Reply as a Bulletin to the specified
+message<newline>
+<bf>reply RR <msgno></bf> Reply to the specified message with read
+receipt<newline>
+</tt>
+
+<P>
+You can reply to a message and the subject will automatically have
+"Re:" inserted in front of it, if it isn't already present.
+
+You can also use all the extra qualifiers such as RR, PRIVATE,
+NOPRIVATE, B that you can use with the SEND command (see SEND
+for further details)
+
+<sect1>send
+
+<P>
+<tt>
+<bf>send <call> [<call> ...]</bf> Send a message to
+one or more callsigns<newline>
+<bf>send RR <call></bf> Send a message and ask for a read receipt<newline>
+<bf>send COPY <msgno> <call></bf> Send a copy of a message
+to someone<newline>
+<bf>send PRIVATE <call></bf> Send a personal message<newline>
+<bf>send NOPRIVATE <call></bf> Send a message to all stations<newline>
+</tt>
+
+<P>
+All the SEND commands will create a message which will be sent either to
+an individual callsign or to one of the 'bulletin' addresses.
+
+SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
+it will mark the message as personal and send it to the cluster node that
+that callsign is connected to.
+
+You can have more than one callsign in all of the SEND commands.
+
+You can have multiple qualifiers so that you can have for example:-
+
+<tscreen><verb>
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
+</verb></tscreen>
+
+which should send a copy of message 123 to G1TLH and G0RDI and you will
+receive a read receipt when they have read the message.
+
+SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
+SP is an alias for SEND PRIVATE
+
+<sect1>set/address
+
+<P>
+<tt>
+<bf>set/address <your_address></bf> Record your postal address
+</tt>
+
+<P>
+Literally, record your address details on the cluster.
+
+<sect1>set/announce
+
+<P>
+<tt>
+<bf>set/announce</bf> Allow announce messages
+</tt>
+
+<P>
+Allow announce messages to arrive at your terminal.
+
+<sect1>set/beep
+
+<P>
+<tt>
+<bf>set/beep</bf> Add beeps to terminal messages
+</tt>
+
+<P>
+Add a beep to DX and other terminal messages.
+
+<sect1>set/dx
+
+<P>
+<tt>
+<bf>set/dx</bf>Allow DX messages to arrive at your terminal
+</tt>
+
+<P>
+You can stop DX messages with the <em>unset/dx</em> command
+
+<sect1>set/dxgrid
+
+<P>
+<tt>
+<bf>set/dxgrid</bf>Allow grid squares on the end of DX messages
+</tt>
+
+<P>
+Some logging programs do not like the additional information at
+the end of a DX spot. If this is the case, use the <em>unset/dxgrid</em>
+command to remove the grid squares.
+
+<sect1>set/echo
+
+<P>
+<tt>
+<bf>set/echo</bf> Make the cluster echo your input
+</tt>
+
+<P>
+If you are connected via a telnet session, different implimentations
+of telnet handle echo differently depending on whether you are
+connected via port 23 or some other port. You can use this command
+to change the setting appropriately.
+
+You can remove the echo with the <em>unset/echo</em> command
+
+The setting is stored in your user profile.
+
+YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+
+<sect1>set/here
+
+<P>
+<tt>
+<bf>set/here</bf> Set the here flag
+</tt>
+
+<P>
+Let others on the cluster know you are here by only displaying your
+callsign. If you are away from your terminal you can use the <em>unset/here</em>
+command to let people know you are away. This simply puts brackets
+around your callsign to indicate you are not available.
+
+<sect1>set/homenode
+
+<P>
+<tt>
+<bf>set/homenode <node_call></bf> Set your home cluster
+</tt>
+
+<P>
+Tell the cluster system where you normally connect to. Any Messages sent
+to you will normally find their way there should you not be connected.
+eg:-
+
+<tscreen><verb>
+ SET/HOMENODE gb7djk
+</verb></tscreen>
+
+<sect1>set/language
+
+<P>
+<tt>
+<bf>set/language <language></bf> Set the language you wish to use
+</tt>
+
+<P>
+You can select the language that you want the cluster to use. Currently
+the languages available are <em>en</em> (English) <em>sp</em> (Spanish)
+and <em>nl</em> (Dutch).
+
+<sect1>set/location
+
+<P>
+<tt>
+<bf>set/location <lat and long></bf> Set your latitude and longitude
+</tt>
+
+<P>
+You can set your latitude and longitude manually or alternatively use the
+<em>set/qra</em> command which will do the conversion for you.
+
+<tscreen><verb>
+ set/location 54 04 N 2 02 E
+</verb></tscreen>
+
+<sect1>set/logininfo
+
+<P>
+<tt>
+<bf>set/logininfo</bf> Show logins and logouts of nodes and users
+</tt>
+
+<P>
+Show users and nodes when they log in and out of the local cluster. You
+can stop these messages by using the <em>unset/logininfo</em> command.
+
+<sect1>set/name
+
+<P>
+<tt>
+<bf>set/name <your_name></bf> Set your name
+</tt>
+
+<P>
+Tell the cluster what your name is, eg:-
+
+<tscreen><verb>
+ set/name Dirk
+</verb></tscreen>
+
+<sect1>set/page
+
+<P>
+<tt>
+<bf>set/page <n></bf> Set the number of lines per page
+</tt>
+
+<P>
+Tell the system how many lines you wish on a page when the number of lines
+of output from a command is more than this. The default is 20. Setting it
+explicitly to 0 will disable paging.
+
+<tscreen><verb>
+ SET/PAGE 30
+ SET/PAGE 0
+</verb></tscreen>
+
+The setting is stored in your user profile.
+
+<sect1>set/qra
+
+<P>
+<tt>
+<bf>set/qra <locator></bf> Set your QRA locator
+</tt>
+
+<P>
+Tell the system what your QRA (or Maidenhead) locator is. If you have not
+done a SET/LOCATION then your latitude and longitude will be set roughly
+correctly (assuming your locator is correct ;-). For example:-
+
+<tscreen><verb>
+ SET/QRA JO02LQ
+</verb></tscreen>
+
+<sect1>set/qth
+
+<P>
+<tt>
+<bf>set/qth <your QTH></bf> Set your QTH
+</tt>
+
+<P>
+Tell the system where your are. For example:-
+
+<tscreen><verb>
+ set/qth East Dereham, Norfolk
+</verb></tscreen>
+
+<sect1>set/talk
+
+<P>
+<tt>
+<bf>set/talk</bf> Allow talk messages to be seen at your console
+</tt>
+
+<P>
+Allow talk messages to arrive at your console. You can switch off
+talks with the <em>unset/talk</em> command.
+
+<sect1>set/wcy
+
+<P>
+<tt>
+<bf>set/wcy</bf> Allow WCY messages to be seen at your console
+</tt>
+
+<P>
+Allow WCY information to be seen at your console. You can switch off
+WCY messages with the <em>unset/wcy</em> command.
+
+<sect1>set/wwv
+
+<P>
+<tt>
+<bf>set/wwv</bf> Allow WWV messages to be seen at your console
+</tt>
+
+<P>
+Allow WWV information to be seen at your console. You can switch off
+WWV messages with the <em>unset/wwv</em> command.
+
+<sect1>set/wx
+
+<P>
+<tt>
+<bf>set/wx</bf> Allow WX messages to be seen at your console
+</tt>
+
+<P>
+Allow WX information to be seen at your console. You can switch off
+WX messages with the <em>unset/wx</em> command.
+
+<sect1>show/date
+
+<P>
+<tt>
+<bf>show/date [<prefix>|<callsign>]</bf> Show
+the local time
+</tt>
+
+<P>
+This is very nearly the same as SHOW/TIME, the only difference the format
+of the date string if no arguments are given.
+
+If no prefixes or callsigns are given then this command returns the local
+time and UTC as the computer has it right now. If you give some prefixes
+then it will show UTC and UTC + the local offset (not including DST) at
+the prefixes or callsigns that you specify.
+
+<sect1>show/dx
+
+<P>
+<tt>
+<bf>show/dx [options]</bf> interrogate the spot database
+</tt>
+
+<P>
+If you just type SHOW/DX you will get the last so many spots
+(sysop configurable, but usually 10).
+
+In addition you can add any number of these options in very nearly
+any order to the basic SHOW/DX command, they are:-
+
+<tscreen><verb>
+on <band> - eg 160m 20m 2m 23cm 6mm
+on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+
+<number> - the number of spots you want
+<from>-<to> - <from> spot no <to> spot no in
+ the selected list
+
+<prefix> - for a spotted callsign beginning with <prefix>
+*<suffix> - for a spotted callsign ending in <suffix>
+*<string>* - for a spotted callsign containing <string>
+
+day <number> - starting <number> days ago
+day <from>-<to> - <from> days <to> days ago
+
+info <text> - any spots containing <text> in the info or remarks
+
+by <call> - any spots spotted by <call> (spotter <call>
+ is the same).
+
+qsl - this automatically looks for any qsl info on the call
+ held in the spot database.
+
+iota [<iota>] - If the iota island number is missing it will
+ look for the string iota and anything which looks like
+ an iota island number. If you specify then it will look
+ for that island.
+
+qra [<locator>] - this will look for the specific locator if
+ you specify one or else anything that looks like a locator.
+</verb></tscreen>
+
+e.g.
+
+<tscreen><verb>
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
+</verb></tscreen>
+
+<sect1>show/dxcc
+
+<P>
+<tt>
+<bf>show/dxcc <prefix></bf> Interrogate the spot database by country
+</tt>
+
+<P>
+This command takes the <prefix> (which can be a full or partial
+callsign if desired), looks up which internal country number it is
+and then displays all the spots as per SH/DX for that country.
+
+The options for SHOW/DX also apply to this command.
+e.g.
+
+<tscreen><verb>
+ SH/DXCC G
+ SH/DXCC W on 20m info iota
+</verb></tscreen>
+
+<sect1>show/files
+
+<P>
+<tt>
+<bf>show/files [<filearea> [<string>]]</bf> List
+the contents of a filearea
+</tt>
+
+<P>
+SHOW/FILES on its own will show you a list of the various fileareas
+available on the system. To see the contents of a particular file
+area type:-
+
+<tscreen><verb>
+ SH/FILES <filearea>
+</verb></tscreen>
+
+where <filearea> is the name of the filearea you want to see the
+contents of.
+
+You can also use shell globbing characters like '*' and '?' in a
+string to see a selection of files in a filearea eg:-
+
+<tscreen><verb>
+ SH/FILES bulletins arld*
+</verb></tscreen>
+
+See also TYPE - to see the contents of a file.
+
+<sect1>show/filter
+
+<P>
+<tt>
+<bf>show/filter</bf> Show the filters you have set
+</tt>
+
+<P>
+Show the contents of all the filters that are set by you. This command
+displays all the filters set - for all the various categories.
+
+<sect1>show/moon
+
+<P>
+<tt>
+<bf>show/moon [<prefix>|<callsign>]</bf> Show moon
+rise and set times
+</tt>
+
+<P>
+Show the Moon rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+
+If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+
+In addition, it will show the gain or loss dB relative to the nominal
+distance of 385,000Km due to the ellipsoidal nature of the orbit.
+
+If all else fails it will show the Moonrise and set times for the node
+that you are connected to.
+
+For example:-
+
+<tscreen><verb>
+ SH/MOON
+ SH/MOON G1TLH W5UN
+</verb></tscreen>
+
+<sect1>show/muf
+
+<P>
+<tt>
+<bf>show/muf <prefix> [<hours>][long]</bf> Show
+the likely propagation to <prefix>
+</tt>
+
+<P>
+This command allow you to estimate the likelihood of you contacting
+a station with the prefix you have specified. The output assumes a modest
+power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
+
+The result predicts the most likely operating frequencies and signal
+levels for high frequency (shortwave) radio propagation paths on
+specified days of the year and hours of the day. It is most useful for
+paths between 250 km and 6000 km, but can be used with reduced accuracy
+for paths shorter or longer than this.
+
+The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
+used to predict the MUF given the predicted flux, day of the year,
+hour of the day and geographic coordinates of the transmitter and
+receiver. This routine is reasonably accurate for the purposes here,
+with a claimed RMS error of 3.8 MHz, but much smaller and less complex
+than the programs used by major shortwave broadcasting organizations,
+such as the Voice of America.
+
+The command will display some header information detailing its
+assumptions, together with the locations, latitude and longitudes and
+bearings. It will then show UTC (UT), local time at the other end
+(LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
+(Zen) and the likely signal strengths. Then for each frequency for which
+the system thinks there is a likelihood of a circuit it prints a value.
+
+The value is currently a likely S meter reading based on the conventional
+6dB / S point scale. If the value has a '+' appended it means that it is
+1/2 an S point stronger. If the value is preceeded by an 'm' it means that
+there is likely to be much fading and by an 's' that the signal is likely
+to be noisy.
+
+By default SHOW/MUF will show the next two hours worth of data. You
+can specify anything up to 24 hours worth of data by appending the no of
+hours required after the prefix. For example:-
+
+<tscreen><verb>
+ SH/MUF W
+</verb></tscreen>
+
+produces:
+
+<tscreen><verb>
+ RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
+ Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
+ Location Lat / Long Azim
+ East Dereham, Norfolk 52 41 N 0 57 E 47
+ United-States-W 43 0 N 87 54 W 299
+ UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
+ 18 23 11.5 -35 mS0+ mS2 S3
+ 19 0 11.2 -41 mS0+ mS2 S3
+</verb></tscreen>
+
+indicating that you will have weak, fading circuits on top band and
+80m but usable signals on 40m (about S3).
+
+inputing:-
+
+<tscreen><verb>
+ SH/MUF W 24
+</verb></tscreen>
+
+will get you the above display, but with the next 24 hours worth of
+propagation data.
+
+<tscreen><verb>
+ SH/MUF W L 24
+ SH/MUF W 24 Long
+</verb></tscreen>
+
+Gives you an estimate of the long path propagation characterics. It
+should be noted that the figures will probably not be very useful, nor
+terrible accurate, but it is included for completeness.
+
+<sect1>show/prefix
+
+<P>
+<tt>
+<bf>show/prefix <callsign></bf> Interrogate the prefix database
+</tt>
+
+<P>
+This command takes the <callsign> (which can be a full or partial
+callsign or a prefix), looks up which internal country number
+it is and then displays all the relevant prefixes for that country
+together with the internal country no, the CQ and ITU regions.
+
+See also SHOW/DXCC
+
+<sect1>show/qra
+
+<P>
+<tt>
+<bf>show/qra <locator> [<locator>]</bf> Show the distance
+between locators<newline>
+<bf>show/qra <lat> <long></bf> Convert latitude and longitude to
+a locator
+</tt>
+
+<P>
+This is a multipurpose command that allows you either to calculate the
+distance and bearing between two locators or (if only one locator is
+given on the command line) the distance and beraing from your station
+to the locator. For example:-
+
+<tscreen><verb>
+SH/QRA IO92QL
+SH/QRA JN06 IN73
+</verb></tscreen>
+
+The first example will show the distance and bearing to the locator from
+yourself, the second example will calculate the distance and bearing from
+the first locator to the second. You can use 4 or 6 character locators.
+
+It is also possible to convert a latitude and longitude to a locator by
+using this command with a latitude and longitude as an argument, for
+example:-
+
+<tscreen><verb>
+SH/QRA 52 41 N 0 58 E
+</verb></tscreen>
+
+<sect1>show/qrz
+
+<P>
+<tt>
+<bf>show/qrz <callsign></bf> Show any callbook details on a callsign
+</tt>
+
+<P>
+This command queries the QRZ callbook server on the internet
+and returns any information available for that callsign. This service
+is provided for users of this software by http://www.qrz.com
+
+<sect1>show/route
+
+<P>
+<tt>
+<bf>show/route <callsign></bf> Show the route to <callsign>
+</tt>
+
+<P>
+This command allows you to see to which node the callsigns specified are
+connected. It is a sort of inverse sh/config.
+
+<tscreen><verb>
+ sh/route n2tly
+</verb></tscreen>
+
+<sect1>show/satellite
+
+<P>
+<tt>
+<bf>show/satellite <name> [<hours> <interval>]</bf>
+Show satellite tracking data
+</tt>
+
+<P>
+Show the tracking data from your location to the satellite of your choice
+from now on for the next few hours.
+
+If you use this command without a satellite name it will display a list
+of all the satellites known currently to the system.
+
+If you give a name then you can obtain tracking data of all the passes
+that start and finish 5 degrees below the horizon. As default it will
+give information for the next three hours for every five minute period.
+
+You can alter the number of hours and the step size, within certain
+limits.
+
+Each pass in a period is separated with a row of '-----' characters
+
+So for example:-
+
+<tscreen><verb>
+SH/SAT AO-10
+SH/SAT FENGYUN1 12 2
+</verb></tscreen>
+
+<sect1>show/sun
+
+<P>
+<tt>
+<bf>show/sun [<prefix>|<callsign>]</bf> Show
+sun rise and set times
+</tt>
+
+<P>
+Show the sun rise and set times for a (list of) prefixes or callsigns,
+together with the azimuth and elevation of the sun currently at those
+locations.
+
+If you don't specify any prefixes or callsigns, it will show the times for
+your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
+together with the current azimuth and elevation.
+
+If all else fails it will show the sunrise and set times for the node
+that you are connected to.
+
+For example:-
+
+<tscreen><verb>
+ SH/SUN
+ SH/SUN G1TLH K9CW ZS
+</verb></tscreen>
+
+<sect1>show/time
+
+<P>
+<tt>
+<bf>show/time [<prefix>|<callsign>]</bf> Show
+the local time
+</tt>
+
+<P>
+If no prefixes or callsigns are given then this command returns the local
+time and UTC as the computer has it right now. If you give some prefixes
+then it will show UTC and UTC + the local offset (not including DST) at
+the prefixes or callsigns that you specify.
+
+<sect1>show/wcy
+
+<P>
+<tt>
+<bf>show/wcy</bf> Show the last 10 WCY broadcasts<newline>
+<bf>show/wcy <n></bf> Show the last <n> WCY broadcasts
+</tt>
+
+<P>
+Display the most recent WCY information that has been received by the system
+
+<sect1>show/wwv
+
+<P>
+<tt>
+<bf>show/wwv</bf> Show the last 10 WWV broadcasts<newline>
+<bf>show/wwv <n></bf> Show the last <n> WWV broadcasts
+</tt>
+
+<P>
+Display the most recent WWV information that has been received by the system
+
+<sect1>sysop
+
+<P>
+<tt>
+<bf>sysop</bf> Regain your privileges if you login remotely
+</tt>
+
+<P>
+The system automatically reduces your privilege level to that of a
+normal user if you login in remotely. This command allows you to
+regain your normal privilege level. It uses the normal system: five
+numbers are returned that are indexes into the character array that is
+your assigned password (see SET/PASSWORD). The indexes start from
+zero.
+
+You are expected to return a string which contains the characters
+required in the correct order. You may intersperse those characters
+with others to obscure your reply for any watchers. For example (and
+these values are for explanation :-):
+
+<tscreen><verb>
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
+</verb></tscreen>
+
+you type:-
+
+<tscreen><verb>
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
+</verb></tscreen>
+
+They will all match. If there is no password you will still be offered
+numbers but nothing will happen when you input a string. Any match is
+case sensitive.
+
+<sect1>talk
+
+<P>
+<tt>
+<bf>talk <callsign></bf> Enter talk mode with <callsign><newline>
+<bf>talk <callsign> <text></bf> Send a text message to <callsign><newline>
+<bf>talk <callsign> > <node_call> [<text>]</bf>
+Send a text message to <callsign> via <node_call>
+</tt>
+
+<P>
+Send a short message to any other station that is visible on the cluster
+system. You can send it to anyone you can see with a SHOW/CONFIGURATION
+command, they don't have to be connected locally.
+
+The second form of TALK is used when other cluster nodes are connected
+with restricted information. This usually means that they don't send
+the user information usually associated with logging on and off the cluster.
+
+If you know that G3JNB is likely to be present on GB7TLH, but you can only
+see GB7TLH in the SH/C list but with no users, then you would use the
+second form of the talk message.
+
+If you want to have a ragchew with someone you can leave the text message
+out and the system will go into 'Talk' mode. What this means is that a
+short message is sent to the recipient telling them that you are in a 'Talking'
+frame of mind and then you just type - everything you send will go to the
+station that you asked for.
+
+All the usual announcements, spots and so on will still come out on your
+terminal.
+
+If you want to do something (such as send a spot) you precede the normal
+command with a '/' character, eg:-
+
+<tscreen><verb>
+ /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
+ /HELP talk
+</verb></tscreen>
+
+To leave talk mode type:
+
+<tscreen><verb>
+ /EX
+</verb></tscreen>
+
+<sect1>type
+
+<P>
+<tt>
+<bf>type <filearea>/<name></bf> Look at a file in one of the fileareas
+</tt>
+
+<P>
+Type out the contents of a file in a filearea. So, for example, in
+filearea 'bulletins' you want to look at file 'arld051' you would
+enter:-
+
+<tscreen><verb>
+ TYPE bulletins/arld051
+</verb></tscreen>
+
+See also SHOW/FILES to see what fileareas are available and a
+list of content.
+
+<sect1>who
+
+<P>
+<tt>
+<bf>who</bf> Show who is physically connected locally
+</tt>
+
+<P>
+This is a quick listing that shows which callsigns are connected and
+what sort of connection they have
+
+<sect1>wx
+
+<P>
+<tt>
+<bf>wx <text></bf> Send a weather message to local users<newline>
+<bf>wx full <text> </bf> Send a weather message to all cluster users
+</tt>
+
+<P>
+Weather messages can sometimes be useful if you are experiencing an extreme
+that may indicate enhanced conditions
+
+</article>
+ This line works fine for RedHat and SuSE distributions. The line
+ required for Slackware distributions is slightly different. My thanks
+ to Aurelio, PA3EZL for this information.
+
+
+
+ DX:23:respawn:/bin/su - sysop -c "/usr/bin/perl -w /spider/perl/cluster.pl" >/dev/tty7
+
+
+
+
+
This will automatically start DXSpider on tty7 (ALT-F7) on bootup and
restart it should it crash for any reason.
+ #
+ # hop table construction
+ #
+ package DXProt;
+ # default hopcount to use
+ $def_hopcount = 5;
+ # some variable hop counts based on message type
+ %hopcount =
+ (
+ 11 => 10,
+ 16 => 10,
+ 17 => 10,
+ 19 => 10,
+ 21 => 10,
+ );
-
- #
- # hop table construction
- #
-
- package DXProt;
-
- # default hopcount to use
- $def_hopcount = 5;
-
- # some variable hop counts based on message type
- %hopcount =
- (
- 11 => 10,
- 16 => 10,
- 17 => 10,
- 19 => 10,
- 21 => 10,
- );
-
-
- # the per node hop control thingy
+ # the per node hop control thingy
- %nodehops =
+ %nodehops =
- GB7ADX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
+ GB7ADX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
- GB7UDX => { 11 => 8,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- GB7BAA => {
- 11 => 5,
- 12 => 8,
- 16 => 8,
- 17 => 8,
- 19 => 8,
- 21 => 8,
- },
- };
+ GB7UDX => { 11 => 8,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ GB7BAA => {
+ 11 => 5,
+ 12 => 8,
+ 16 => 8,
+ 17 => 8,
+ 19 => 8,
+ 21 => 8,
+ },
+ };
will bring your changes into effect.
-
5\b5.\b.2\b2.\b. I\bIs\bso\bol\bla\bat\bti\bin\bng\bg n\bne\bet\btw\bwo\bor\brk\bks\bs
It is possible to isolate networks from each other on a "gateway" node
-
-
-
-
-
0 = frequency
1 = call
2 = date in unix format
--- /dev/null
+ The DXSpider User Manual
+ Ian Maude, G0VGS, (ianmaude@btinternet.com)
+ Version 1.0, March 2001
+
+ A complete reference for users of the DXSpider DXCluster program.
+ ______________________________________________________________________
+
+ Table of Contents
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 1. Introduction
+
+ 1.1 What is a DX Cluster?
+ 1.2 So what is DXSpider?
+
+ 2. Logins and logouts.
+
+ 2.1 AX25 logins.
+ 2.2 Netrom logins.
+ 2.3 Telnet logins.
+ 2.4 Logouts.
+
+ 3. Setting your personal details.
+
+ 4. Getting and posting DX.
+
+ 4.1 Receiving DX.
+ 4.2 Posting DX.
+
+ 5. Headings and propagation
+
+ 5.1 Sun
+ 5.2 Moon
+ 5.3 Heading
+
+ 6. Announcements.
+
+ 6.1 Making announcements.
+ 6.2 Listing announcements.
+
+ 7. Nodes and users.
+
+ 8. Talk mode.
+
+ 9. Mail.
+
+ 9.1 The "directory" command.
+ 9.2 Reading mail.
+ 9.3 Sending mail.
+ 9.4 Replying to mail.
+ 9.5 Deleting mail To delete a message, you use the
+
+ 10. Filtering (From version 1.45)
+
+ 10.1 General filter rules
+ 10.2 Types of filter
+ 10.3 Filter options
+ 10.4 Advanced filtering
+
+ 11. Hints, tips and common questions.
+
+ 12. The DXSpider command reference
+
+ 12.1 accept/announce
+ 12.2 accept/spots
+ 12.3 accept/wcy
+ 12.4 accept/wwv
+ 12.5 announce
+ 12.6 announce full
+ 12.7 apropos
+ 12.8 bye
+ 12.9 clear/spots
+ 12.10 dbavail
+ 12.11 dbshow
+ 12.12 directory
+ 12.13 dx
+ 12.14 help
+ 12.15 kill
+ 12.16 links
+ 12.17 read
+ 12.18 reject/announce
+ 12.19 reject/spots
+ 12.20 reject/wcy
+ 12.21 reject/wwv
+ 12.22 reply
+ 12.23 send
+ 12.24 set/address
+ 12.25 set/announce
+ 12.26 set/beep
+ 12.27 set/dx
+ 12.28 set/dxgrid
+ 12.29 set/echo
+ 12.30 set/here
+ 12.31 set/homenode
+ 12.32 set/language
+ 12.33 set/location
+ 12.34 set/logininfo
+ 12.35 set/name
+ 12.36 set/page
+ 12.37 set/qra
+ 12.38 set/qth
+ 12.39 set/talk
+ 12.40 set/wcy
+ 12.41 set/wwv
+ 12.42 set/wx
+ 12.43 show/date
+ 12.44 show/dx
+ 12.45 show/dxcc
+ 12.46 show/files
+ 12.47 show/filter
+ 12.48 show/moon
+ 12.49 show/muf
+ 12.50 show/prefix
+ 12.51 show/qra
+ 12.52 show/qrz
+ 12.53 show/route
+ 12.54 show/satellite
+ 12.55 show/sun
+ 12.56 show/time
+ 12.57 show/wcy
+ 12.58 show/wwv
+ 12.59 sysop
+ 12.60 talk
+ 12.61 type
+ 12.62 who
+ 12.63 wx
+
+
+ ______________________________________________________________________
+
+ 1\b1.\b. I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
+
+ 1\b1.\b.1\b1.\b. W\bWh\bha\bat\bt i\bis\bs a\ba D\bDX\bX C\bCl\blu\bus\bst\bte\ber\br?\b?
+
+ A DX Cluster is a packet node where DX chasers on any band or mode can
+ post rare or interesting stations that they have worked or heard. Of
+ course other people are doing the same thing too, so you can find new
+ DX as well as telling others about the stations you have worked.
+ Clusters tend to be linked to each other so that the amount of people
+ using them is increased, thereby increasing the amount of posted DX.
+ Other information can be found on clusters such as on-line call books,
+ mail etc. You can talk to other stations connected to the cluster
+ network too, in real time, whether at the node you are logged into or
+ on another node connected to the network. You can also use converse
+ mode, where several stations can talk to each other in the same way.
+ Of course, the DX is still posted to you all the while!
+
+
+ 1\b1.\b.2\b2.\b. S\bSo\bo w\bwh\bha\bat\bt i\bis\bs D\bDX\bXS\bSp\bpi\bid\bde\ber\br?\b?
+
+ PacketCluster nodes have been around since roughly 1985. The original
+ PacketCluster idea came from Dick Newell, AK1A, and ran under DOS. In
+ about 1992 Dick stopped the development of the PacketCluster software
+ for amateur radio. Many systems are still using this relatively old
+ DOS software today.
+
+ There are several new compatible cluster programs around now,
+ including DXSpider. DXSpider is a clone of PacketCluster software
+ that runs under the Linux operating system. Linux is fast becoming
+ the choice for amateur radio stations because of it's flexibility,
+ reliability and the lack of the memory limitations of DOS. Linux
+ supports multitasking and is also multiuser. It has support for AX25,
+ ROSE, NetROM and TCPIP built in, making it the ideal choice for
+ amateur radio. It is also totally free!
+
+ DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
+ exercise in perl programming. It has developed rapidly and today is a
+ very powerful cluster program. It was designed to be totally
+ compatible with the AK1A program, although several commands have been
+ extended to try and improve functionality.
+
+ This manual is designed to help you become familiar with the commands
+ that DXSpider supports and to help you get the best from the program
+ so you can enjoy working that rare DX! As DXSpider is being improved
+ all the time, commands will be added as time goes by, so make sure you
+ have the most upto date version of this manual. The latest version
+ will always be included with the cluster program so if you are unsure,
+ simply ask your sysop. The manual will also be available on the
+ wesite.
+
+
+
+ 2\b2.\b. L\bLo\bog\bgi\bin\bns\bs a\ban\bnd\bd l\blo\bog\bgo\bou\but\bts\bs.\b.
+
+ You might not think that there is a lot of point of including a
+ section on how to log in and out of DXSpider. However, you would be
+ suprised at the difficulties some people have in simply getting in and
+ out of the cluster!
+
+ There are several ways a login might be achieved, dependant on how the
+ sysop has DXSpider configured. It is impossible for me to cover all
+ variations but here are the basic ones.
+
+
+ 2\b2.\b.1\b1.\b. A\bAX\bX2\b25\b5 l\blo\bog\bgi\bin\bns\bs.\b.
+
+ Simplicity itself. The usual C\bCO\bON\bNN\bNE\bEC\bCT\bT command will log you straight
+ into the cluster and you will not have to do anything else.
+ Obviously, you will have to connect to the correct callsign. Some
+ nodes use an SSID with their call so you would have to add that.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ connect GB7MBC
+ connect GB7MBC-1
+
+ 2\b2.\b.2\b2.\b. N\bNe\bet\btr\bro\bom\bm l\blo\bog\bgi\bin\bns\bs.\b.
+
+ There are several possibilities here, dependant on how the sysop has
+ configured his system. If you are connecting via netrom then you are
+ most probably connecting from another station. Listing the nodes in
+ that station with the N\bNO\bOD\bDE\bES\bS command will tell you what callsign or
+ netrom alias to connect to. Then just issue the connect command from
+ there. It is possible that the netrom alias may connect you to a node
+ with an alias for the cluster, such as DXC. Just type this and you
+ will be connected.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+ connect MBCDX
+
+
+
+
+
+ 2\b2.\b.3\b3.\b. T\bTe\bel\bln\bne\bet\bt l\blo\bog\bgi\bin\bns\bs.\b.
+
+ Because DXSpider runs under the Linux operating system, it is possible
+ to make a direct telnet connection into the cluster. With telnet
+ connections, the source callsign is not seen by DXSpider, so you will
+ be asked to login with your callsign. To telnet to DXSpider, you
+ would connect to a specific port. There is no standard at the moment
+ for a cluster telnet port but ask the sysop if you are unsure.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ telnet gb7mbc 8000
+
+
+
+
+ All the above are possible ways of connecting to a DXSpider cluster.
+ You may have some or all of these available to you. There may be one
+ or two additional ways to connect dependant on the network local to
+ you. However I am sure you get the idea.
+
+
+ 2\b2.\b.4\b4.\b. L\bLo\bog\bgo\bou\but\bts\bs.\b.
+
+ Logging out can be done by simply issuing the standard B\bBY\bYE\bE command.
+
+ You could also send a disconnect if you are using AX25, or a C\bCL\bLO\bOS\bSE\bE
+ command if you are connected via telnet. If you do not log out
+ gracefully using one of the above commands, you may find you are
+ unable to get a full connect next time. This may also happen if a
+ NETRom connection drops. You may get connected, but nothing else will
+ happen because the program thinks you are still connected and will not
+ let you connect twice under the same call. However you could
+ reconnect by adding a number to the end of your call, for example
+ G0YLM2. This can be done by either altering your MYCALL setting in
+ the TNC or by altering your program configuration.
+
+
+
+ 3\b3.\b. S\bSe\bet\btt\bti\bin\bng\bg y\byo\bou\bur\br p\bpe\ber\brs\bso\bon\bna\bal\bl d\bde\bet\bta\bai\bil\bls\bs.\b.
+
+ Once logged in to the cluster, you should set your details so that
+ anybody who wishes to contact you can find out who and where you are.
+ There are four items to set, your name, qth, location and home node.
+ Setting these details also allows the use of the SHOW/HEADING and
+ SHOW/SUN commands from within the cluster. Unless you set your QTH
+ and location, these commands cannot function. Once you have set your
+ name, DXSpider will greet you with it next time you login. Your QTH
+ setting is where you live and it is a good idea to add your locator to
+ this as the location setting is converted to latitude and longitude
+ once inputted. You can actually set your location in
+ latitude/longitude or as a locator. Setting your home node will tell
+ the program where you wish mail to be sent to you.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ set/name Ian
+ set/qth Morecambe, Lancashire IO84NB
+ set/location 48 34 n 12 12 e
+ set/qra IO84NB
+ set/home gb7mbc
+
+
+
+
+
+ 4\b4.\b. G\bGe\bet\btt\bti\bin\bng\bg a\ban\bnd\bd p\bpo\bos\bst\bti\bin\bng\bg D\bDX\bX.\b.
+
+ When all is said and done, this is the main function of a DX cluster.
+ In its simplest form you can just connect to the node and you will
+ start to receive DX spots almost immediately! You can check on recent
+ postings in either a general manner or on a particular band or mode.
+ You can even check DX by callsign or a fragment of a callsign. Of
+ course, once you get the hang of things, it is expected that you start
+ posting some yourself! After all, there would be no clusters if
+ people did not post DX and you get the added thrill of the hunt!
+
+
+ 4\b4.\b.1\b1.\b. R\bRe\bec\bce\bei\biv\bvi\bin\bng\bg D\bDX\bX.\b.
+
+ As we have already said, it is possible just to connect to the cluster
+ and you will receive spots automatically. However, you may wish to
+ check on spots just posted. Maybe you wish to see if a particular
+ band is open or if a certain callsign is active, perhaps a DXpedition.
+ The command to do this is S\bSH\bHO\bOW\bW/\b/D\bDX\bX. Without any other arguments, this
+ command will output the last 10 spots posted. It is possible to look
+ at more than this, for example the last 20 or 50 spots, by adding the
+ number to the command. You can make it even more specific by adding a
+ band in either wavelength or frequency, and/or any additional
+ information such as QSL details.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ show/dx
+ show/dx 5
+ show/dx 20
+
+
+
+
+ will show the last 10, 5 and 20 spots received by the cluster
+ respectively.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs
+
+
+ show/dx on 20m
+ show/dx 10 on 20m
+ show/dx 20 on 20m
+
+
+
+
+ will show the last 5, 10 or 20 spots on 20 metres only.
+
+ It is also possible to check for certain callsigns, or fragments of
+ callsigns in the same way.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ show/dx g0vgs
+ show/dx 10 g0vgs
+
+
+
+
+ would show the last 5 or 10 dx spots containing the callsign g0vgs.
+
+
+ You can check for DX by offset and also by specifying a comment to
+ search for.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ show/dx 30-40
+ show/dx 14000-14033
+ show/dx iota
+
+
+
+
+ would show the spots that arrived between 30 and 40 spots ago and any
+ spots with the word _\bi_\bo_\bt_\ba in the comment field. The case of the
+ comment is not important.
+
+ Checking DX posted on a certain day is possible too. All you have to
+ do here is to specify how many days ago it was like this ...
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/dx day 30
+
+
+
+
+ It is of course possible to specify multiple arguments.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/dx 20 prefix 9a on vhf day 30
+
+
+
+
+ This would show the last 20 spots posted by or about calls with the
+ prefix 9a on vhf 30 days ago.
+
+ As you can see the S\bSH\bHO\bOW\bW/\b/D\bDX\bX command is very flexible, so if you are not
+ sure whether something will work or not, try it and see! More
+ information can be found in the Command Set section.
+
+
+ 4\b4.\b.2\b2.\b. P\bPo\bos\bst\bti\bin\bng\bg D\bDX\bX.\b.
+
+ To post DX you use the D\bDX\bX command. The syntax is shown below.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ dx (frequency) (callsign) (remarks)
+
+
+
+
+ Where frequency is in kilohertz and the callsign is the callsign of
+ the station you have worked or heard, (ie not your own callsign!).
+ The remarks section allows you to add information like the operators
+ name or perhaps a location. Actually DXSpider will allow the
+ frequency and callsign fields to be entered in any order.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ dx 14004 pa3ezl OP Aurelio 599
+
+
+
+
+ In fact, all the following will give the same result...
+
+
+
+ dx 14004 pa3ezl OP Aurelio 599
+ dx pa3ezl 14004 OP Aurelio 599
+ dx pa3ezl 14.004 OP Aurelio 599
+
+
+
+
+ This posting, or callout as it is known, will be forwarded to all
+ other connected stations both at the cluster you are connected to and
+ other active clusters in the network. The callout will also be sent
+ to you as proof of receipt.
+
+
+ 5\b5.\b. H\bHe\bea\bad\bdi\bin\bng\bgs\bs a\ban\bnd\bd p\bpr\bro\bop\bpa\bag\bga\bat\bti\bio\bon\bn
+
+ There are three commands in DXSpider to help you get the best DX
+ possible. These are S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN, S\bSH\bHO\bOW\bW/\b/M\bMO\bOO\bON\bN and S\bSH\bHO\bOW\bW/\b/H\bHE\bEA\bAD\bDI\bIN\bNG\bG. These
+ commands will only work for you if you have entered your personal
+ details. They use your entered location as a reference, so if you
+ have not entered it or have entered it incorrectly they will not
+ return the correct information.
+
+
+
+
+
+ 5\b5.\b.1\b1.\b. S\bSu\bun\bn
+
+ The S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN command can be used in three different ways. It can be
+ used to show sunrise and sunset times for your own station, a
+ particular callsign or a prefix.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/sun
+
+
+
+
+ The output from this would look something like this ..
+
+
+
+ sh/sun Location Rise Set Azim Elev
+ G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
+
+
+
+
+
+
+ sh/sun 5b4
+
+
+
+
+ would look like this ...
+
+
+
+ sh/sun 5b4 Location Rise Set Azim Elev 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
+
+
+
+
+ You can also specify multiple arguments like this ...
+
+
+
+ sh/sun gw4veq 5b4ab zs
+
+
+
+
+ and then the output would look like this ...
+
+
+
+ sh/sun gw4veq 5b4ab zs
+ Location Rise Set Azim Elev
+ GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9 5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
+ ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
+ ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
+ ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
+
+
+
+
+
+
+ 5\b5.\b.2\b2.\b. M\bMo\boo\bon\bn
+
+ The S\bSH\bHO\bOW\bW/\b/M\bMO\bOO\bON\bN command works in the same way as the S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN command.
+ This program however, calculates the rise and set times of the moon
+ for a prefix or callsign, together with the current azimuth and
+ elevation of the sun at these locations.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/moon ea
+
+
+
+
+ The output from this command would look like this ..
+
+
+
+ sh/moon ea
+ Location Rise Set Azim Elev RGain dB
+ EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
+
+
+
+
+ You can see that the output is similar to the S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN command, with
+ slightly different fields.
+
+
+ 5\b5.\b.3\b3.\b. H\bHe\bea\bad\bdi\bin\bng\bg
+
+ The S\bSH\bHO\bOW\bW/\b/H\bHE\bEA\bAD\bDI\bIN\bNG\bG command works in the same way as the S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN and
+ S\bSH\bHO\bOW\bW/\b/M\bMO\bOO\bON\bN commands but outputs beam headings for a specified callsign
+ or prefix. Reciprocal beam headings are also calculated.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be
+
+
+
+ show/heading zl
+
+
+
+
+ The output from this command would look like this ..
+
+
+
+ sh/heading zl
+ ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
+ ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
+ ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
+ ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
+
+
+
+
+
+ 6\b6.\b. A\bAn\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs.\b.
+
+ 6\b6.\b.1\b1.\b. M\bMa\bak\bki\bin\bng\bg a\ban\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs.\b.
+
+ Occasionally, you may wish to post something that does not fall into
+ the normal parameters for a DX callout. You may wish to tell
+ everybody connected that 10 FM is open for example, or ask if anyone
+ knows the QSL manager for a certain callsign etc. You can do this
+ using the A\bAN\bNN\bNO\bOU\bUN\bNC\bCE\bE command.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ announce 10 FM is open in IO84NB to europe.
+
+
+
+
+ That would let everyone know locally that this was the case, however
+ it would not be forwarded to other nodes connected. To send
+ announcements to other connected nodes as well, you would use the F\bFU\bUL\bLL\bL
+ extension.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ announce full Anyone seen EA7WA today?
+
+
+
+
+ Be cautious in your use of announce full. There are many other tools
+ available to get the information you require and the judicious use of
+ this command is frowned upon as it creates a great deal of traffic
+ across the network.
+
+
+ 6\b6.\b.2\b2.\b. L\bLi\bis\bst\bti\bin\bng\bg a\ban\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs.\b.
+
+ You can list previous announcements in the standard format with the
+ S\bSH\bHO\bOW\bW command. As before you can list just the last 5 or as many as
+ you wish.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/announcements
+ show/announcements 10
+
+
+
+
+
+ 7\b7.\b. N\bNo\bod\bde\bes\bs a\ban\bnd\bd u\bus\bse\ber\brs\bs.\b.
+
+ You can check which nodes are connected in the network, who is logged
+ on locally, who is logged on at all the nodes or even just one node in
+ particular. This is handy if you wish to see whether a friend is
+ connected at the node they use. To see who is connected to the nodes,
+ the S\bSH\bHO\bOW\bW/\b/C\bCO\bON\bNF\bFI\bIG\bGU\bUR\bRA\bAT\bTI\bIO\bON\bN command is used.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+
+
+
+
+ show/configuration
+ show/configuration/nodes
+ show/configuration (node_call)
+ show/configuration (prefix)
+
+
+
+
+ The first of our three examples would output something like this,
+
+
+ sh/c
+ Node Callsigns
+ EI5TCR (7 users)
+ GB7ADX
+ GB7BAA G4FPV G8TIC
+ GB7BIG (GD0TEP) GD3UMW
+ GB7BPQ (G0INA) G0RCI G3AKU G3OCA
+ (GB7CDX) G3JNB G4ALR
+ GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
+ G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
+ ON7WP
+ GB7DXA G0RDI G8SJP
+ GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
+ G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
+ GB7DXE G1NNB
+ (GB7DXG) GU6EFB GU7DHI
+ GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
+ G4XQY G7GAN
+ GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
+ M0BCT M1EMF
+
+
+
+ You will notice that EI5TCR is showing only that it has 7 users and
+ not giving the actual callsigns. This means that this node is on a
+ limited protocol of some kind, probably because of a contest situation
+ where slow radio links can block up and fail if too much information
+ is sent between nodes.
+
+ The second example would just show the nodes connected in the network,
+ like this,
+
+
+ sh/c/n
+ Node Callsigns
+ GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
+ GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
+ GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
+ GB7YDX KL7G N2TLY (ON0DXK)
+ GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
+ GB7MBC
+ PA4AB-14 PA4AB-14
+ PI4TUE-8 PI4TUE-8
+
+
+
+ If we insert the node_call pi4tue-8 into the third example, then this
+ would be the output,
+
+
+
+
+
+
+
+ Node Callsigns
+ PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
+ F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
+ ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
+ PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
+ YT1XX
+
+
+
+ As you can see, only the users of the requested node are shown.
+
+ You can also use a prefix to show only a group of nodes. For example
+ you may only wish to see who is connected to the nodes in the UK. To
+ do this simply use a prefix like this ...
+
+
+ show/configuration gb7
+
+
+
+ To show the locally connected users, the S\bSH\bHO\bOW\bW/\b/U\bUS\bSE\bER\bRS\bS command is used
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/users
+
+
+
+
+ The output of this command would look like this,
+
+
+ Callsigns connected to GB7MBC
+ G0JHC G0NEI G0VGS G0VGS-2 G0YLM
+ G3JAG G3OWO G3UEU
+
+
+
+
+ 8\b8.\b. T\bTa\bal\blk\bk m\bmo\bod\bde\be.\b.
+
+ You can send a single comment or start a dedicated talk session to
+ another user by using the T\bTA\bAL\bLK\bK command.
+
+
+ Talk mode is used to send a one line comment or greeting to a specific
+ user connected either at your node or another in the network. You can
+ also enter into a dedicated talk session with another user. Talks
+ will be automatically forwarded to other nodes if the station you are
+ talking to is not connected locally. You can find out who is
+ connected by using the S\bSH\bHO\bOW\bW/\b/C\bCO\bON\bNF\bFI\bIG\bGU\bUR\bRA\bAT\bTI\bIO\bON\bN command, (described
+ earlier).
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+
+ talk g0rdi Having a good day Iain?
+
+
+
+
+
+ This example would send the line "Having a good day Iain?" to the user
+ g0rdi but would leave you in normal mode.
+
+
+
+ talk g0rdi
+ Entering Talkmode, /EX to end, /<cmd> to run a command
+ Talk (G0RDI)>
+
+
+
+
+ As you can see, you can still run commands whilst in talk mode.
+ Simply prefix the command with a / like /sh/dx and you will get the
+ expected output. If the user is connected to another node, you may
+ have to use a slightly extended version of the T\bTA\bAL\bLK\bK command.
+
+
+
+ talk g0rdi > gb7djk
+
+
+
+
+ To exit talk mode, you issue the command /\b/e\bex\bx.
+
+ Whilst in talk mode you will still receive DX spots. This means that
+ you can chat to a friend whilst working DX.
+
+
+ 9\b9.\b. M\bMa\bai\bil\bl.\b.
+
+ You can send and receive both personal mail and bulletins with
+ DXSpider quite easily.
+
+
+ 9\b9.\b.1\b1.\b. T\bTh\bhe\be "\b"d\bdi\bir\bre\bec\bct\bto\bor\bry\by"\b" c\bco\bom\bmm\bma\ban\bnd\bd.\b.
+
+ To list mail you would use the D\bDI\bIR\bRE\bEC\bCT\bTO\bOR\bRY\bY command. On its own, this
+ command will output the last ten messages received by the node, either
+ to or from yourself or bulletins such as "DX" and "ALL". As with
+ other commands you can display more by specifying a number with the
+ command. You should be aware that Spider will accept these commands
+ by separating with either a slash or a space, so _\bd_\bi_\br _\bn_\be_\bw and _\bd_\bi_\br_\b/_\bn_\be_\bw
+ work in the same way.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ directory
+ directory/20
+ directory 20
+
+
+
+
+ Of course most of the time you will only want to list new mail sent to
+ you personally since your last login. However you might also like to
+ check for general mail received by the node. In fact if there is new
+ mail for you, the cluster will tell you when you login. You will also
+ be informed if new mail arrives for you during the time you are logged
+ in. Mail is not only sent to callsigns though. Mail can also be sent
+ to subjects like "all" or "local" or "dx" etc. You can treat these
+ bulletins in the same way as personal mail with the directory command.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ directory/new
+ directory/own
+ directory/own/10
+ directory/all
+ directory/from <call>
+
+
+
+
+
+ The last option will only show mail from a callsign if it was sent to
+ you personally or was sent as a bulletin. There are some additional
+ commands and these can be found in the DXSpider Command Reference
+ section.
+
+
+ 9\b9.\b.2\b2.\b. R\bRe\bea\bad\bdi\bin\bng\bg m\bma\bai\bil\bl.\b.
+
+ The output of the D\bDI\bIR\bRE\bEC\bCT\bTO\bOR\bRY\bY command could be something like this.
+
+
+ dir
+ 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
+ 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
+ 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
+ 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
+ 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
+ 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
+ 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
+ 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
+ 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
+ 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
+ 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
+
+
+
+ The first column is the actual message number. If the message is a
+ personal one to you, you will see a letter 'p' after this number. If
+ the message has been read, there will be a '-' between the message
+ number and the 'p'. This only works for personal messages. The next
+ column shows the file size of the message. The third column shows the
+ address the message was sent to and the next column shows who sent it.
+ The rest is fairly self-explanatory.
+
+ Reading a message is as simple as typing read, followed by the message
+ number that you wish to read.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ read 25
+
+
+
+
+ will read message number 25. However the mail will be displayed in
+ it's entirety unless you specify a page length. You can set your page
+ length to any number you like and when the message reaches that number
+ of lines you will get a prompt giving you options.
+
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ set/page 20
+
+
+
+
+
+
+ 9\b9.\b.3\b3.\b. S\bSe\ben\bnd\bdi\bin\bng\bg m\bma\bai\bil\bl.\b.
+
+ Sending mail is done in the time honoured way. First you specify a
+ recipient for the message, then you will be prompted for a subject.
+ Once you have done this you will be asked to type your message.
+ Please remember that there is no automatic word wrap, so unless you
+ are using a client that wraps lines automatically, remember to hit
+ return at the end of each line.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ send m0azm
+ Enter Subject (30 characters):
+ See you Thursday
+ Enter Message /EX to send or /ABORT to exit
+ Hi Ian,
+ Just a quick note to say that I can make Thursday after all. The
+ appointment I had has cancelled so we are go!
+ Cheers
+ Ian
+
+
+
+
+ At this point you can either hit return and enter /ex to send the
+ message or use /abort at any time to abort it. You can now display
+ the message in the normal way. There are several send options and
+ these are listed in the Command Set section. These include sending
+ mail to several recipients and asking for a return receipt.
+
+
+
+ 9\b9.\b.4\b4.\b. R\bRe\bep\bpl\bly\byi\bin\bng\bg t\bto\bo m\bma\bai\bil\bl.\b.
+
+ If mail is addressed to you or to a bulletin address, you can use the
+ R\bRE\bEP\bPL\bLY\bY command to reply to it. Using this command, the subject will be
+ automatically set for you as "Re: subject", whatever the subject was.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ reply 2500
+
+
+
+
+
+ 9\b9.\b.5\b5.\b. T\bTo\bo d\bde\bel\ble\bet\bte\be a\ba m\bme\bes\bss\bsa\bag\bge\be,\b, y\byo\bou\bu u\bus\bse\be t\bth\bhe\be d\bde\bel\ble\bet\bte\be c\bco\bom\bmm\bma\ban\bnd\bd.\b. Y\bYo\bou\bu c\bca\ban\bn o\bon\bnl\bly\by
+ d\bde\bel\ble\bet\bte\be m\bme\bes\bss\bsa\bag\bge\bes\bs s\bse\ben\bnt\bt t\bto\bo o\bor\br r\bre\bec\bce\bei\biv\bve\bed\bd b\bby\by y\byo\bou\bur\brs\bse\bel\blf\bf.\b. B\bBu\bul\bll\ble\bet\bti\bin\bns\bs a\bar\bre\be d\bde\bea\bal\blt\bt
+ w\bwi\bit\bth\bh a\bau\but\bto\bom\bma\bat\bti\bic\bca\bal\bll\bly\by o\bor\br b\bby\by t\bth\bhe\be s\bsy\bys\bso\bop\bp.\b. D\bDe\bel\ble\bet\bti\bin\bng\bg m\bma\bai\bil\bl
+
+
+ 1\b10\b0.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg (\b(F\bFr\bro\bom\bm v\bve\ber\brs\bsi\bio\bon\bn 1\b1.\b.4\b45\b5)\b)
+
+ 1\b10\b0.\b.1\b1.\b. G\bGe\ben\bne\ber\bra\bal\bl f\bfi\bil\blt\bte\ber\br r\bru\bul\ble\bes\bs
+
+ Upto v1.44 it was not possible for the user to set their own filters.
+ From v1.45 though that has all changed. It is now possible to set
+ filters for just about anything you wish. If you have just updated
+ from an older version of DXSpider you will need to update your new
+ filters. You do not need to do anything with your old filters, they
+ will be renamed as you update.
+
+
+ There are 3 basic commands involved in setting and manipulating
+ filters. These are _\ba_\bc_\bc_\be_\bp_\bt, _\br_\be_\bj_\be_\bc_\bt and _\bc_\bl_\be_\ba_\br. First we will look
+ generally at filtering. There are a number of things you can filter in
+ the DXSpider system. They all use the same general mechanism.
+
+
+ In general terms you can create a 'reject' or an 'accept' filter which
+ can have up to 10 lines in it. You do this using, for example ...
+
+
+
+
+ accept/spots .....
+ reject/spots .....
+
+
+
+
+ where ..... are the specific commands for that type of filter. There
+ are filters for spots, wwv, announce, wcy and (for sysops) connects.
+ See each different accept or reject command reference for more
+ details.
+
+ There is also a command to clear out one or more lines in a filter.
+ They are ...
+
+
+
+ clear/spots 1
+ clear/spots all
+
+
+
+
+ There is clear/xxxx command for each type of filter.
+
+
+ and you can check that your filters have worked by the command ...
+
+
+
+
+ show/filter
+
+
+
+
+
+ For now we are going to use spots for the examples, but you can apply
+ the same principles to all types of filter.
+
+
+
+
+ 1\b10\b0.\b.2\b2.\b. T\bTy\byp\bpe\bes\bs o\bof\bf f\bfi\bil\blt\bte\ber\br
+
+ There are two main types of filter, _\ba_\bc_\bc_\be_\bp_\bt or _\br_\be_\bj_\be_\bc_\bt. You can use
+ either to achieve the result you want dependent on your own preference
+ and which is more simple to do. It is pointless writing 8 lines of
+ reject filters when 1 accept filter would do the same thing! Each
+ filter has 10 lines (of any length) which are tried in order. If a
+ line matches then the action you have specified is taken (ie reject
+ means ignore it and accept means take it)
+
+
+ If you specify reject filters, then any lines that arrive that match
+ the filter will be dumped but all else will be accepted. If you use
+ an accept filter, then ONLY the lines in the filter will be accepted
+ and all else will be dumped. For example if you have a single line
+ _\ba_\bc_\bc_\be_\bp_\bt filter ...
+
+
+
+ accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+
+ then you will _\bO_\bN_\bL_\bY get VHF spots _\bf_\br_\bo_\bm or _\bt_\bo CQ zones 14, 15 and 16.
+
+
+ If you set a reject filter like this ...
+
+
+
+ reject/spots on hf/cw
+
+
+
+
+ Then you will get everything _\bE_\bX_\bC_\bE_\bP_\bT HF CW spots. You could make this
+ single filter even more flexible. For example, if you are interested
+ in IOTA and will work it even on CW even though normally you are not
+ interested in CW, then you could say ...
+
+
+
+ reject/spots on hf/cw and not info iota
+
+
+
+
+ But in that case you might only be interested in iota and say:-
+
+
+
+ accept/spots not on hf/cw or info iota
+
+
+
+
+ which achieves exactly the same thing. You should choose one or the
+ other until you are comfortable with the way it works. You can mix
+ them if you wish (actually you can have an accept AND a reject on the
+ same line) but don't attempt this until you are sure you know what you
+ are doing!
+
+
+ You can arrange your filter lines into logical units, either for your
+ own understanding or simply convenience. Here is an example ...
+ reject/spots 1 on hf/cw
+ reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+
+ What this does is to ignore all HF CW spots and also rejects any spots
+ on VHF which don't either originate or spot someone in Europe.
+
+
+ This is an example where you would use a line number (1 and 2 in this
+ case), if you leave the digit out, the system assumes '1'. Digits
+ '0'-'9' are available. This make it easier to see just what filters
+ you have set. It also makes it more simple to remove individual
+ filters, during a contest for example.
+
+
+ You will notice in the above example that the second line has
+ brackets. Look at the line logically. You can see there are 2
+ separate sections to it. We are saying reject spots that are VHF or
+ above _\bA_\bP_\bA_\bR_\bT from those in zones 14, 15 and 16 (either spotted there or
+ originated there). If you did not have the brackets to separate the 2
+ sections, then Spider would read it logically from the front and see a
+ different expression entirely ...
+
+
+
+ (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+
+
+
+
+ The simple way to remember this is, if you use OR - use brackets.
+ Whilst we are here CASE is not important. 'And BY_Zone' is just the
+ same as 'and by_zone'.
+
+ As mentioned earlier, setting several filters can be more flexible
+ than simply setting one complex one. Doing it in this way means that
+ if you want to alter your filter you can just redefine or remove one
+ or more lines of it or one line. For example ...
+
+
+
+ reject/spots 1 on hf/ssb
+
+
+
+
+ would redefine our earlier example, or
+
+
+
+ clear/spots 1
+
+
+
+
+ To remove all the filter lines in the spot filter ...
+
+
+
+ clear/spots all
+
+
+
+
+ 1\b10\b0.\b.3\b3.\b. F\bFi\bil\blt\bte\ber\br o\bop\bpt\bti\bio\bon\bns\bs
+
+ You can filter in several different ways. The options are listed in
+ the various helpfiles for accept, reject and filter.
+
+
+ 1\b10\b0.\b.4\b4.\b. A\bAd\bdv\bva\ban\bnc\bce\bed\bd f\bfi\bil\blt\bte\ber\bri\bin\bng\bg
+
+ Once you are happy with the results you get, you may like to
+ experiment.
+
+
+ The previous example that filters hf/cw spots and accepts vhf/uhf
+ spots from EU can be written with a mixed filter, for example ...
+
+
+
+ rej/spot on hf/cw
+ acc/spot on 0/30000
+ acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+
+ Note that the first filter has not been specified with a number. This
+ will automatically be assumed to be number 1. In this case, we have
+ said _\br_\be_\bj_\be_\bc_\bt _\ba_\bl_\bl _\bH_\bF _\bs_\bp_\bo_\bt_\bs _\bi_\bn _\bt_\bh_\be _\bC_\bW _\bs_\be_\bc_\bt_\bi_\bo_\bn _\bo_\bf _\bt_\bh_\be _\bb_\ba_\bn_\bd_\bs _\bb_\bu_\bt _\ba_\bc_\bc_\be_\bp_\bt _\ba_\bl_\bl
+ _\bo_\bt_\bh_\be_\br_\bs _\ba_\bt _\bH_\bF_\b. _\bA_\bl_\bs_\bo _\ba_\bc_\bc_\be_\bp_\bt _\ba_\bn_\by_\bt_\bh_\bi_\bn_\bg _\bi_\bn _\bV_\bH_\bF _\ba_\bn_\bd _\ba_\bb_\bo_\bv_\be _\bs_\bp_\bo_\bt_\bt_\be_\bd _\bi_\bn _\bo_\br _\bb_\by
+ _\bo_\bp_\be_\br_\ba_\bt_\bo_\br_\bs _\bi_\bn _\bt_\bh_\be _\bz_\bo_\bn_\be_\bs _\b1_\b4_\b, _\b1_\b5 _\ba_\bn_\bd _\b1_\b6. Each filter slot actually has a
+ 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
+ the accept slot.
+
+
+ It was mentioned earlier that after a reject test that doesn't match,
+ the default for following tests is 'accept', the reverse is true for
+ 'accept'. In the example what happens is that the reject is executed
+ first, any non hf/cw spot is passed to the accept line, which lets
+ through everything else on HF. The next filter line lets through just
+ VHF/UHF spots from EU.
+
+
+
+ 1\b11\b1.\b. H\bHi\bin\bnt\bts\bs,\b, t\bti\bip\bps\bs a\ban\bnd\bd c\bco\bom\bmm\bmo\bon\bn q\bqu\bue\bes\bst\bti\bio\bon\bns\bs.\b.
+
+ Q\bQ.\b.These commands seem very long! Can I shorten them?
+
+ A\bA.\b.Of course you can and the usual abbreviations work. If you are
+ unsure, try it.
+
+ Q\bQ.\b.I am not sure if this command is correct. Can I cause any harm if I
+ try it?
+
+ A\bA.\b.Do not be afraid to try a command to see if it will work, at the
+ worst you will get an error message. If you require any help on a
+ command, just type help followed by the command you want help on.
+ Look at the "DXSpider Command Reference" section to see what help can
+ be found.
+
+ Q\bQ.\b.How should I use the announce command?
+
+ A\bA.\b.With respect. Use the command by all means, but please only use the
+ "full" extension if absolutely necessary. It can create a LOT of
+ messages passing between clusters.
+
+ Q\bQ.\b.I like to be working in the shack while logged into the cluster but
+ I can't be looking at the screen all the time. How can I be alerted
+ when anything happens?
+
+ A\bA.\b.Use the S\bSE\bET\bT/\b/B\bBE\bEE\bEP\bP command. You can find information on this in the
+ "DXSpider Command Reference" section.
+
+ Q\bQ.\b.I keep getting disconnected from the cluster, what is happening and
+ how can I stop it?
+
+ Q\bQ.\b.I got disconnected from the cluster and now I can't log back in
+ again. What is wrong?
+
+ A\bA.\b.Probably the cluster thinks you are still logged on and will not let
+ you reconnect using the same call to prevent loops. Try logging on
+ again adding an ssid to your callsign as DXSpider treats G0YLM and
+ G0YLM-1 as different users.
+
+ Q\bQ.\b.I notice that all the commands are shown in lower case in the main
+ section of this manual, but in upper case in the "DXSpider Command
+ Reference" section. Why is that?
+
+ Q\bQ.\b.How do I know if I have got the latest version of this user manual?
+
+ A\bA.\b.The latest and greatest will always be on the Website. It will also
+ be included with every release of DXSpider. As always, if unsure, ask
+ your sysop what version number is the latest.
+
+
+ 1\b12\b2.\b. T\bTh\bhe\be D\bDX\bXS\bSp\bpi\bid\bde\ber\br c\bco\bom\bmm\bma\ban\bnd\bd r\bre\bef\bfe\ber\bre\ben\bnc\bce\be
+
+ Below is a complete list of commands available from the cluster
+ prompt. These are listed below in alphabetical order.
+
+
+ 1\b12\b2.\b.1\b1.\b. a\bac\bcc\bce\bep\bpt\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be
+
+ a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set an accept filter line for announce
+
+
+ Create an 'accept this announce' line for a filter.
+
+ An accept filter line means that if the announce matches this filter
+ it is passed onto the user. See HELP FILTERS for more info. Please
+ read this to understand how filters work - it will save a lot of grief
+ later on.
+
+ You can use any of the following things in this line:-
+
+
+
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+
+
+
+
+
+ some examples:-
+
+
+
+ acc/ann dest 6MUK
+ acc/ann 2 by_zone 14,15,16
+ (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+
+
+
+
+ or
+
+
+
+ acc/ann by G,M,2
+
+
+
+
+ This filter would only allow announces that were posted buy UK
+ stations. You can use the tag 'all' to accept everything eg:
+
+
+
+ acc/ann all
+
+
+
+
+ but this probably for advanced users...
+
+
+ 1\b12\b2.\b.2\b2.\b. a\bac\bcc\bce\bep\bpt\bt/\b/s\bsp\bpo\bot\bts\bs
+
+ a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set an accept filter line for spots
+
+
+ Create an 'accept this spot' line for a filter.
+
+
+ An accept filter line means that if the spot matches this filter it is
+ passed onto the user. See HELP FILTERS for more info. Please read this
+ to understand how filters work - it will save a lot of grief later on.
+
+ You can use any of the following things in this line:-
+
+
+
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+
+
+
+
+ For frequencies, you can use any of the band names defined in
+ SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+ thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+ this is more efficient than saying simply: freq HF (but don't get too
+ hung up about that)
+
+ some examples:-
+
+
+
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+
+ You can use the tag 'all' to accept everything, eg:
+
+
+
+ acc/spot 3 all
+
+
+
+
+ but this probably for advanced users...
+
+
+ 1\b12\b2.\b.3\b3.\b. a\bac\bcc\bce\bep\bpt\bt/\b/w\bwc\bcy\by
+
+ a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bwc
\bcy
\by [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> set an accept WCY filter
+
+
+ It is unlikely that you will want to do this, but if you do then you
+ can filter on the following fields:-
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+
+
+
+
+
+ There are no examples because WCY Broadcasts only come from one place
+ and you either want them or not (see UNSET/WCY if you don't want
+ them).
+
+ This command is really provided for future use.
+
+ See HELP FILTER for information.
+
+
+ 1\b12\b2.\b.4\b4.\b. a\bac\bcc\bce\bep\bpt\bt/\b/w\bww\bwv\bv
+
+ a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set an accept WWV filter
+
+
+ It is unlikely that you will want to do this, but if you do then you
+ can filter on the following fields:-
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+
+
+
+
+ for example
+
+
+
+ accept/wwv by_zone 4
+
+
+
+
+ is probably the only useful thing to do (which will only show WWV
+ broadcasts by stations in the US).
+
+ See HELP FILTER for information.
+
+
+ 1\b12\b2.\b.5\b5.\b. a\ban\bnn\bno\bou\bun\bnc\bce\be
+
+ a\ban\bnn\bno\bou\bun\bnc\bce\be <\b<t\bte\bex\bxt\bt>\b> Send an announcement to local users
+
+
+ Send an announcement to LOCAL users only, where <text> is the text of
+ the announcement you wish to broadcast
+
+
+ 1\b12\b2.\b.6\b6.\b. a\ban\bnn\bno\bou\bun\bnc\bce\be f\bfu\bul\bll\bl
+
+ a\ban\bnn\bno\bou\bun\bnc\bce\be f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b> Send an announcement cluster wide
+
+
+ This command will send your announcement across the whole cluster
+ network.
+
+
+ 1\b12\b2.\b.7\b7.\b. a\bap\bpr\bro\bop\bpo\bos\bs
+
+ a\bap\bpr\bro\bop\bpo\bos\bs <\b<s\bst\btr\bri\bin\bng\bg>\b> Search the help database
+
+
+ Search the help database for <string> (it isn't case sensitive), and
+ print the names of all the commands that may be relevant.
+
+
+ 1\b12\b2.\b.8\b8.\b. b\bby\bye\be
+
+ b\bby\bye\be Exit from the cluster
+
+
+
+ This will disconnect you from the cluster
+
+
+ 1\b12\b2.\b.9\b9.\b. c\bcl\ble\bea\bar\br/\b/s\bsp\bpo\bot\bts\bs
+
+ c\bcl\ble\bea\bar\br/\b/s\bsp\bpo\bot\bts\bs [\b[1\b1|\b|a\bal\bll\bl]\b] Clear a spot filter line
+
+
+ This command allows you to clear (remove) a line in a spot filter or
+ to remove the whole filter.
+
+ If you have a filter:-
+
+
+
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+
+ and you say:-
+
+
+
+ clear/spot 1
+
+
+
+
+ you will be left with:-
+
+
+
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+
+ If you do:
+
+
+
+ clear/spot all
+
+
+
+
+ the filter will be completely removed.
+
+
+ 1\b12\b2.\b.1\b10\b0.\b. d\bdb\bba\bav\bva\bai\bil\bl
+
+ d\bdb\bba\bav\bva\bai\bil\bl Show a list of all the databases in the system
+
+
+ The title says it all really, this command lists all the databases
+ defined in the system. It is also aliased to SHOW/COMMAND.
+
+
+ 1\b12\b2.\b.1\b11\b1.\b. d\bdb\bbs\bsh\bho\bow\bw
+
+ d\bdb\bbs\bsh\bho\bow\bw <\b<d\bdb\bbn\bna\bam\bme\be>\b> <\b<k\bke\bey\by>\b> Display an entry, if it exists, in a database
+
+
+
+ This is the generic user interface to the database to the database
+ system. It is expected that the sysop will add an entry to the local
+ Aliases file so that users can use the more familiar AK1A style of
+ enquiry such as:
+
+
+
+ SH/BUCK G1TLH
+
+
+
+
+ but if he hasn't and the database really does exist (use DBAVAIL or
+ SHOW/COMMAND to find out) you can do the same thing with:
+
+
+
+ DBSHOW buck G1TLH
+
+
+
+
+
+ 1\b12\b2.\b.1\b12\b2.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by
+
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by List messages
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by o\bow\bwn\bn List your own messages
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by n\bne\bew\bw List all new messages
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by t\bto\bo <\b<c\bca\bal\bll\bl>\b> List all messages to <call>
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by f\bfr\bro\bom\bm <\b<c\bca\bal\bll\bl>\b> List all messages from <call>
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by s\bsu\bub\bbj\bje\bec\bct\bt <\b<s\bst\btr\bri\bin\bng\bg>\b> List all messages with <string> in subject
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by <\b<n\bnn\bn>\b> List last <nn> messages
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by <\b<f\bfr\bro\bom\bm>\b>-\b-<\b<t\bto\bo>\b> List messages <from> message <to> message
+
+
+ List the messages in the messages directory.
+
+ If there is a 'p' one space after the message number then it is a
+ personal message. If there is a '-' between the message number and the
+
+ You can use shell escape characters such as '*' and '?' in the <call>
+ fields.
+
+ You can combine some of the various directory commands together eg:-
+
+
+
+ DIR TO G1TLH 5
+ or
+ DIR SUBJECT IOTA 200-250
+
+
+
+
+ You can abbreviate all the commands to one letter and use ak1a
+ syntax:-
+
+
+
+ DIR/T G1* 10
+ DIR/S QSL 10-100 5
+
+
+
+
+
+ 1\b12\b2.\b.1\b13\b3.\b. d\bdx\bx
+
+ d\bdx\bx [\b[b\bby\by <\b<c\bca\bal\bll\bl>\b>]\b] <\b<f\bfr\bre\beq\bq>\b> <\b<c\bca\bal\bll\bl>\b> <\b<r\bre\bem\bma\bar\brk\bks\bs>\b> Send a DX spot
+
+
+ This is how you send a DX Spot to other users. You can, in fact, now
+ enter the <freq> and the <call> either way round.
+
+
+
+ DX FR0G 144.600
+ DX 144.600 FR0G
+ DX 144600 FR0G
+
+
+
+
+ will all give the same result. You can add some remarks to the end of
+ the command and they will be added to the spot.
+
+
+
+ DX FR0G 144600 this is a test
+
+
+
+
+ You can credit someone else by saying:-
+
+
+
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
+
+
+
+
+ The <freq> is compared against the available bands set up in the
+ cluster. See SHOW/BANDS for more information.
+
+
+ 1\b12\b2.\b.1\b14\b4.\b. h\bhe\bel\blp\bp
+
+ h\bhe\bel\blp\bp <\b<c\bcm\bmd\bd>\b> Get help on a command
+
+
+ All commands can be abbreviated, so SHOW/DX can be abbreviated to
+ SH/DX, ANNOUNCE can be shortened to AN and so on.
+
+ Look at the APROPOS <string> command which will search the help
+ database for the <string> you specify and give you a list of likely
+ commands to look at with HELP.
+
+
+ 1\b12\b2.\b.1\b15\b5.\b. k\bki\bil\bll\bl
+
+ k\bki\bil\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b> .\b..\b.]\b] Delete a message from the local system
+
+
+ Delete a message from the local system. You will only be able to
+ delete messages that you have originated or been sent (unless you are
+ the sysop).
+
+
+
+
+
+ 1\b12\b2.\b.1\b16\b6.\b. l\bli\bin\bnk\bks\bs
+
+ l\bli\bin\bnk\bks\bs Show which nodes are physically connected
+
+
+ This is a quick listing that shows which links are connected and some
+ information about them. See WHO for a list of all connections.
+
+
+ 1\b12\b2.\b.1\b17\b7.\b. r\bre\bea\bad\bd
+
+ r\bre\bea\bad\bd Read the next unread personal message addressed to you
+ r\bre\bea\bad\bd <\b<m\bms\bsg\bgn\bno\bo>\b> Read the specified message
+
+
+ You can read any messages that are sent as 'non-personal' and also any
+ message either sent by or sent to your callsign.
+
+
+ 1\b12\b2.\b.1\b18\b8.\b. r\bre\bej\bje\bec\bct\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be
+
+ r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a reject filter for announce
+
+
+ Create an 'reject this announce' line for a filter.
+
+ An reject filter line means that if the announce matches this filter
+ it is passed onto the user. See HELP FILTERS for more info. Please
+ read this to understand how filters work - it will save a lot of grief
+ later on.
+
+ You can use any of the following things in this line:-
+
+
+
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+
+
+
+
+ some examples:-
+
+
+
+ rej/ann by_zone 14,15,16 and not by G,M,2
+
+
+
+
+ You can use the tag 'all' to reject everything eg:
+
+
+
+ rej/ann all
+
+ but this probably for advanced users...
+
+
+ 1\b12\b2.\b.1\b19\b9.\b. r\bre\bej\bje\bec\bct\bt/\b/s\bsp\bpo\bot\bts\bs
+
+ r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a reject filter line for spots
+
+
+ Create a 'reject this spot' line for a filter.
+
+ A reject filter line means that if the spot matches this filter it is
+ dumped (not passed on). See HELP FILTERS for more info. Please read
+ this to understand how filters work - it will save a lot of grief
+ later on.
+
+ You can use any of the following things in this line:-
+
+
+
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <numbers>
+ call_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ origin <prefixes>
+ channel <prefixes>
+
+
+
+
+ For frequencies, you can use any of the band names defined in
+ SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+ thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+ this is more efficient than saying simply: on HF (but don't get too
+ hung up about that)
+
+ some examples:-
+
+
+
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+
+ You can use the tag 'all' to reject everything eg:
+
+
+
+ rej/spot 3 all
+
+
+
+
+ but this probably for advanced users...
+
+
+
+
+ 1\b12\b2.\b.2\b20\b0.\b. r\bre\bej\bje\bec\bct\bt/\b/w\bwc\bcy\by
+
+ r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bwc
\bcy
\by [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a reject WCY filter
+
+
+ It is unlikely that you will want to do this, but if you do then you
+ can filter on the following fields:-
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+
+
+
+
+ There are no examples because WCY Broadcasts only come from one place
+ and you either want them or not (see UNSET/WCY if you don't want
+ them).
+
+ This command is really provided for future use.
+
+ See HELP FILTER for information.
+
+
+ 1\b12\b2.\b.2\b21\b1.\b. r\bre\bej\bje\bec\bct\bt/\b/w\bww\bwv\bv
+
+ r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bww
\bwv
\bv [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a reject WWV filter
+
+
+ It is unlikely that you will want to do this, but if you do then you
+ can filter on the following fields:-
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <numbers>
+ origin_zone <numbers>
+ by_dxcc <numbers>
+ by_itu <numbers>
+ by_zone <numbers>
+ channel <prefixes>
+
+
+
+
+ for example
+
+
+
+ reject/wwv by_zone 14,15,16
+
+
+
+
+ is probably the only useful thing to do (which will only show WWV
+ broadcasts by stations in the US).
+ See HELP FILTER for information.
+
+
+ 1\b12\b2.\b.2\b22\b2.\b. r\bre\bep\bpl\bly\by
+
+ r\bre\bep\bpl\bly\by Reply (privately) to the last message that you have read
+ r\bre\bep\bpl\bly\by <\b<m\bms\bsg\bgn\bno\bo>\b> Reply (privately) to the specified message
+ r\bre\bep\bpl\bly\by B\bB <\b<m\bms\bsg\bgn\bno\bo>\b> Reply as a Bulletin to the specified message
+ r\bre\bep\bpl\bly\by N\bNO\bOP\bPr\bri\biv\bva\bat\bte\be <\b<m\bms\bsg\bgn\bno\bo>\b> Reply as a Bulletin to the specified message
+ r\bre\bep\bpl\bly\by R\bRR\bR <\b<m\bms\bsg\bgn\bno\bo>\b> Reply to the specified message with read receipt
+
+
+ You can reply to a message and the subject will automatically have
+ "Re:" inserted in front of it, if it isn't already present.
+
+ You can also use all the extra qualifiers such as RR, PRIVATE,
+ NOPRIVATE, B that you can use with the SEND command (see SEND for
+ further details)
+
+
+ 1\b12\b2.\b.2\b23\b3.\b. s\bse\ben\bnd\bd
+
+ s\bse\ben\bnd\bd <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Send a message to one or more callsigns
+ s\bse\ben\bnd\bd R\bRR\bR <\b<c\bca\bal\bll\bl>\b> Send a message and ask for a read receipt
+ s\bse\ben\bnd\bd C\bCO\bOP\bPY\bY <\b<m\bms\bsg\bgn\bno\bo>\b> <\b<c\bca\bal\bll\bl>\b> Send a copy of a message to someone
+ s\bse\ben\bnd\bd P\bPR\bRI\bIV\bVA\bAT\bTE\bE <\b<c\bca\bal\bll\bl>\b> Send a personal message
+ s\bse\ben\bnd\bd N\bNO\bOP\bPR\bRI\bIV\bVA\bAT\bTE\bE <\b<c\bca\bal\bll\bl>\b> Send a message to all stations
+
+
+ All the SEND commands will create a message which will be sent either
+ to an individual callsign or to one of the 'bulletin' addresses.
+
+ SEND <call> on its own acts as though you had typed SEND PRIVATE, that
+ is it will mark the message as personal and send it to the cluster
+ node that that callsign is connected to.
+
+ You can have more than one callsign in all of the SEND commands.
+
+ You can have multiple qualifiers so that you can have for example:-
+
+
+
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
+
+
+
+
+ which should send a copy of message 123 to G1TLH and G0RDI and you
+ will receive a read receipt when they have read the message.
+
+ SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
+ is an alias for SEND PRIVATE
+
+
+ 1\b12\b2.\b.2\b24\b4.\b. s\bse\bet\bt/\b/a\bad\bdd\bdr\bre\bes\bss\bs
+
+ s\bse\bet\bt/\b/a\bad\bdd\bdr\bre\bes\bss\bs <\b<y\byo\bou\bur\br_\b_a\bad\bdd\bdr\bre\bes\bss\bs>\b> Record your postal address
+
+
+ Literally, record your address details on the cluster.
+
+
+ 1\b12\b2.\b.2\b25\b5.\b. s\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be
+
+ s\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be Allow announce messages
+
+ Allow announce messages to arrive at your terminal.
+
+
+ 1\b12\b2.\b.2\b26\b6.\b. s\bse\bet\bt/\b/b\bbe\bee\bep\bp
+
+ s\bse\bet\bt/\b/b\bbe\bee\bep\bp Add beeps to terminal messages
+
+
+ Add a beep to DX and other terminal messages.
+
+
+ 1\b12\b2.\b.2\b27\b7.\b. s\bse\bet\bt/\b/d\bdx\bx
+
+ s\bse\bet\bt/\b/d\bdx\bxAllow DX messages to arrive at your terminal
+
+
+ You can stop DX messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bd_\bx command
+
+
+ 1\b12\b2.\b.2\b28\b8.\b. s\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bd
+
+ s\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bdAllow grid squares on the end of DX messages
+
+
+ Some logging programs do not like the additional information at the
+ end of a DX spot. If this is the case, use the _\bu_\bn_\bs_\be_\bt_\b/_\bd_\bx_\bg_\br_\bi_\bd command
+ to remove the grid squares.
+
+
+ 1\b12\b2.\b.2\b29\b9.\b. s\bse\bet\bt/\b/e\bec\bch\bho\bo
+
+ s\bse\bet\bt/\b/e\bec\bch\bho\bo Make the cluster echo your input
+
+
+ If you are connected via a telnet session, different implimentations
+ of telnet handle echo differently depending on whether you are
+ connected via port 23 or some other port. You can use this command to
+ change the setting appropriately.
+
+ You can remove the echo with the _\bu_\bn_\bs_\be_\bt_\b/_\be_\bc_\bh_\bo command
+
+ The setting is stored in your user profile.
+
+ YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+
+
+ 1\b12\b2.\b.3\b30\b0.\b. s\bse\bet\bt/\b/h\bhe\ber\bre\be
+
+ s\bse\bet\bt/\b/h\bhe\ber\bre\be Set the here flag
+
+
+ Let others on the cluster know you are here by only displaying your
+ callsign. If you are away from your terminal you can use the
+ _\bu_\bn_\bs_\be_\bt_\b/_\bh_\be_\br_\be command to let people know you are away. This simply puts
+ brackets around your callsign to indicate you are not available.
+
+
+ 1\b12\b2.\b.3\b31\b1.\b. s\bse\bet\bt/\b/h\bho\bom\bme\ben\bno\bod\bde\be
+
+ s\bse\bet\bt/\b/h\bho\bom\bme\ben\bno\bod\bde\be <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> Set your home cluster
+
+
+ Tell the cluster system where you normally connect to. Any Messages
+ sent to you will normally find their way there should you not be
+ connected. eg:-
+
+ SET/HOMENODE gb7djk
+
+
+
+
+
+ 1\b12\b2.\b.3\b32\b2.\b. s\bse\bet\bt/\b/l\bla\ban\bng\bgu\bua\bag\bge\be
+
+ s\bse\bet\bt/\b/l\bla\ban\bng\bgu\bua\bag\bge\be <\b<l\bla\ban\bng\bgu\bua\bag\bge\be>\b> Set the language you wish to use
+
+
+ You can select the language that you want the cluster to use.
+ Currently the languages available are _\be_\bn (English) _\bs_\bp (Spanish) and _\bn_\bl
+ (Dutch).
+
+
+ 1\b12\b2.\b.3\b33\b3.\b. s\bse\bet\bt/\b/l\blo\boc\bca\bat\bti\bio\bon\bn
+
+ s\bse\bet\bt/\b/l\blo\boc\bca\bat\bti\bio\bon\bn <\b<l\bla\bat\bt a\ban\bnd\bd l\blo\bon\bng\bg>\b> Set your latitude and longitude
+
+
+ You can set your latitude and longitude manually or alternatively use
+ the _\bs_\be_\bt_\b/_\bq_\br_\ba command which will do the conversion for you.
+
+
+
+ set/location 54 04 N 2 02 E
+
+
+
+
+
+ 1\b12\b2.\b.3\b34\b4.\b. s\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo
+
+ s\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo Show logins and logouts of nodes and users
+
+
+ Show users and nodes when they log in and out of the local cluster.
+ You can stop these messages by using the _\bu_\bn_\bs_\be_\bt_\b/_\bl_\bo_\bg_\bi_\bn_\bi_\bn_\bf_\bo command.
+
+
+ 1\b12\b2.\b.3\b35\b5.\b. s\bse\bet\bt/\b/n\bna\bam\bme\be
+
+ s\bse\bet\bt/\b/n\bna\bam\bme\be <\b<y\byo\bou\bur\br_\b_n\bna\bam\bme\be>\b> Set your name
+
+
+ Tell the cluster what your name is, eg:-
+
+
+
+ set/name Dirk
+
+
+
+
+
+ 1\b12\b2.\b.3\b36\b6.\b. s\bse\bet\bt/\b/p\bpa\bag\bge\be
+
+ s\bse\bet\bt/\b/p\bpa\bag\bge\be <\b<n\bn>\b> Set the number of lines per page
+
+
+ Tell the system how many lines you wish on a page when the number of
+ lines of output from a command is more than this. The default is 20.
+ Setting it explicitly to 0 will disable paging.
+
+
+ SET/PAGE 30
+ SET/PAGE 0
+
+
+
+
+ The setting is stored in your user profile.
+
+
+ 1\b12\b2.\b.3\b37\b7.\b. s\bse\bet\bt/\b/q\bqr\bra\ba
+
+ s\bse\bet\bt/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> Set your QRA locator
+
+
+ Tell the system what your QRA (or Maidenhead) locator is. If you have
+ not done a SET/LOCATION then your latitude and longitude will be set
+ roughly correctly (assuming your locator is correct ;-). For example:-
+
+
+
+ SET/QRA JO02LQ
+
+
+
+
+
+ 1\b12\b2.\b.3\b38\b8.\b. s\bse\bet\bt/\b/q\bqt\bth\bh
+
+ s\bse\bet\bt/\b/q\bqt\bth\bh <\b<y\byo\bou\bur\br Q\bQT\bTH\bH>\b> Set your QTH
+
+
+ Tell the system where your are. For example:-
+
+
+
+ set/qth East Dereham, Norfolk
+
+
+
+
+
+ 1\b12\b2.\b.3\b39\b9.\b. s\bse\bet\bt/\b/t\bta\bal\blk\bk
+
+ s\bse\bet\bt/\b/t\bta\bal\blk\bk Allow talk messages to be seen at your console
+
+
+ Allow talk messages to arrive at your console. You can switch off
+ talks with the _\bu_\bn_\bs_\be_\bt_\b/_\bt_\ba_\bl_\bk command.
+
+
+ 1\b12\b2.\b.4\b40\b0.\b. s\bse\bet\bt/\b/w\bwc\bcy\by
+
+ s\bse\bet\bt/\b/w\bwc\bcy\by Allow WCY messages to be seen at your console
+
+
+ Allow WCY information to be seen at your console. You can switch off
+ WCY messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bw_\bc_\by command.
+
+
+ 1\b12\b2.\b.4\b41\b1.\b. s\bse\bet\bt/\b/w\bww\bwv\bv
+
+ s\bse\bet\bt/\b/w\bww\bwv\bv Allow WWV messages to be seen at your console
+
+
+ Allow WWV information to be seen at your console. You can switch off
+ WWV messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bw_\bw_\bv command.
+ 1\b12\b2.\b.4\b42\b2.\b. s\bse\bet\bt/\b/w\bwx\bx
+
+ s\bse\bet\bt/\b/w\bwx\bx Allow WX messages to be seen at your console
+
+
+ Allow WX information to be seen at your console. You can switch off
+ WX messages with the _\bu_\bn_\bs_\be_\bt_\b/_\bw_\bx command.
+
+
+ 1\b12\b2.\b.4\b43\b3.\b. s\bsh\bho\bow\bw/\b/d\bda\bat\bte\be
+
+ s
\bsh
\bho
\bow
\bw/
\b/d
\bda
\bat
\bte
\be [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show the local time
+
+
+ This is very nearly the same as SHOW/TIME, the only difference the
+ format of the date string if no arguments are given.
+
+ If no prefixes or callsigns are given then this command returns the
+ local time and UTC as the computer has it right now. If you give some
+ prefixes then it will show UTC and UTC + the local offset (not
+ including DST) at the prefixes or callsigns that you specify.
+
+
+ 1\b12\b2.\b.4\b44\b4.\b. s\bsh\bho\bow\bw/\b/d\bdx\bx
+
+ s\bsh\bho\bow\bw/\b/d\bdx\bx [\b[o\bop\bpt\bti\bio\bon\bns\bs]\b] interrogate the spot database
+
+
+ If you just type SHOW/DX you will get the last so many spots (sysop
+ configurable, but usually 10).
+
+ In addition you can add any number of these options in very nearly any
+ order to the basic SHOW/DX command, they are:-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ on <band> - eg 160m 20m 2m 23cm 6mm
+ on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+
+ <number> - the number of spots you want
+ <from>-<to> - <from> spot no <to> spot no in
+ the selected list
+
+ <prefix> - for a spotted callsign beginning with <prefix>
+ *<suffix> - for a spotted callsign ending in <suffix>
+ *<string>* - for a spotted callsign containing <string>
+
+ day <number> - starting <number> days ago
+ day <from>-<to> - <from> days <to> days ago
+
+ info <text> - any spots containing <text> in the info or remarks
+
+ by <call> - any spots spotted by <call> (spotter <call>
+ is the same).
+
+ qsl - this automatically looks for any qsl info on the call
+ held in the spot database.
+
+ iota [<iota>] - If the iota island number is missing it will
+ look for the string iota and anything which looks like
+ an iota island number. If you specify then it will look
+ for that island.
+
+ qra [<locator>] - this will look for the specific locator if
+ you specify one or else anything that looks like a locator.
+
+
+
+
+ e.g.
+
+
+
+
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
+
+
+
+
+
+ 1\b12\b2.\b.4\b45\b5.\b. s\bsh\bho\bow\bw/\b/d\bdx\bxc\bcc\bc
+
+ s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bxc
\bcc
\bc <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b> Interrogate the spot database by country
+
+
+ This command takes the <prefix> (which can be a full or partial
+ callsign if desired), looks up which internal country number it is and
+ then displays all the spots as per SH/DX for that country.
+
+ The options for SHOW/DX also apply to this command. e.g.
+
+
+
+
+
+
+ SH/DXCC G
+ SH/DXCC W on 20m info iota
+
+
+
+
+
+ 1\b12\b2.\b.4\b46\b6.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\ble\bes\bs
+
+ s\bsh\bho\bow\bw/\b/f\bfi\bil\ble\bes\bs [\b[<\b<f\bfi\bil\ble\bea\bar\bre\bea\ba>\b> [\b[<\b<s\bst\btr\bri\bin\bng\bg>\b>]\b]]\b] List the contents of a filearea
+
+
+ SHOW/FILES on its own will show you a list of the various fileareas
+ available on the system. To see the contents of a particular file area
+ type:-
+
+
+
+ SH/FILES <filearea>
+
+
+
+
+ where <filearea> is the name of the filearea you want to see the
+ contents of.
+
+ You can also use shell globbing characters like '*' and '?' in a
+ string to see a selection of files in a filearea eg:-
+
+
+
+ SH/FILES bulletins arld*
+
+
+
+
+ See also TYPE - to see the contents of a file.
+
+
+ 1\b12\b2.\b.4\b47\b7.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br
+
+ s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br Show the filters you have set
+
+
+ Show the contents of all the filters that are set by you. This command
+ displays all the filters set - for all the various categories.
+
+
+ 1\b12\b2.\b.4\b48\b8.\b. s\bsh\bho\bow\bw/\b/m\bmo\boo\bon\bn
+
+ s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show moon rise and set times
+
+
+ Show the Moon rise and set times for a (list of) prefixes or
+ callsigns, together with the azimuth and elevation of the sun
+ currently at those locations.
+
+ If you don't specify any prefixes or callsigns, it will show the times
+ for your QTH (assuming you have set it with either SET/LOCATION or
+ SET/QRA), together with the current azimuth and elevation.
+
+ In addition, it will show the gain or loss dB relative to the nominal
+ distance of 385,000Km due to the ellipsoidal nature of the orbit.
+
+ If all else fails it will show the Moonrise and set times for the node
+ that you are connected to.
+ For example:-
+
+
+
+ SH/MOON
+ SH/MOON G1TLH W5UN
+
+
+
+
+
+ 1\b12\b2.\b.4\b49\b9.\b. s\bsh\bho\bow\bw/\b/m\bmu\buf\bf
+
+ s
\bsh
\bho
\bow
\bw/
\b/m
\bmu
\buf
\bf <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b> [
\b[<
\b<h
\bho
\bou
\bur
\brs
\bs>
\b>]
\b][
\b[l
\blo
\bon
\bng
\bg]
\b] Show the likely propagation to
+ <prefix>
+
+
+ This command allow you to estimate the likelihood of you contacting a
+ station with the prefix you have specified. The output assumes a
+ modest power of 20dBW and receiver sensitivity of -123dBm (about
+ 0.15muV/10dB SINAD)
+
+ The result predicts the most likely operating frequencies and signal
+ levels for high frequency (shortwave) radio propagation paths on
+ specified days of the year and hours of the day. It is most useful for
+ paths between 250 km and 6000 km, but can be used with reduced
+ accuracy for paths shorter or longer than this.
+
+ The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
+ used to predict the MUF given the predicted flux, day of the year,
+ hour of the day and geographic coordinates of the transmitter and
+ receiver. This routine is reasonably accurate for the purposes here,
+ with a claimed RMS error of 3.8 MHz, but much smaller and less complex
+ than the programs used by major shortwave broadcasting organizations,
+ such as the Voice of America.
+
+ The command will display some header information detailing its
+ assumptions, together with the locations, latitude and longitudes and
+ bearings. It will then show UTC (UT), local time at the other end
+ (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
+ (Zen) and the likely signal strengths. Then for each frequency for
+ which the system thinks there is a likelihood of a circuit it prints a
+ value.
+
+ The value is currently a likely S meter reading based on the
+ conventional 6dB / S point scale. If the value has a '+' appended it
+ means that it is 1/2 an S point stronger. If the value is preceeded by
+ an 'm' it means that there is likely to be much fading and by an 's'
+ that the signal is likely to be noisy.
+
+ By default SHOW/MUF will show the next two hours worth of data. You
+ can specify anything up to 24 hours worth of data by appending the no
+ of hours required after the prefix. For example:-
+
+
+
+ SH/MUF W
+
+
+
+
+ produces:
+
+
+
+
+ RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
+ Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
+ Location Lat / Long Azim
+ East Dereham, Norfolk 52 41 N 0 57 E 47
+ United-States-W 43 0 N 87 54 W 299
+ UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
+ 18 23 11.5 -35 mS0+ mS2 S3
+ 19 0 11.2 -41 mS0+ mS2 S3
+
+
+
+
+ indicating that you will have weak, fading circuits on top band and
+ 80m but usable signals on 40m (about S3).
+
+ inputing:-
+
+
+
+ SH/MUF W 24
+
+
+
+
+ will get you the above display, but with the next 24 hours worth of
+ propagation data.
+
+
+
+ SH/MUF W L 24
+ SH/MUF W 24 Long
+
+
+
+
+ Gives you an estimate of the long path propagation characterics. It
+ should be noted that the figures will probably not be very useful, nor
+ terrible accurate, but it is included for completeness.
+
+
+ 1\b12\b2.\b.5\b50\b0.\b. s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx
+
+ s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Interrogate the prefix database
+
+
+ This command takes the <callsign> (which can be a full or partial
+ callsign or a prefix), looks up which internal country number it is
+ and then displays all the relevant prefixes for that country together
+ with the internal country no, the CQ and ITU regions.
+
+ See also SHOW/DXCC
+
+
+ 1\b12\b2.\b.5\b51\b1.\b. s\bsh\bho\bow\bw/\b/q\bqr\bra\ba
+
+ s\bsh\bho\bow\bw/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> [\b[<\b<l\blo\boc\bca\bat\bto\bor\br>\b>]\b] Show the distance between locators
+ s\bsh\bho\bow\bw/\b/q\bqr\bra\ba <\b<l\bla\bat\bt>\b> <\b<l\blo\bon\bng\bg>\b> Convert latitude and longitude to a locator
+
+
+ This is a multipurpose command that allows you either to calculate the
+ distance and bearing between two locators or (if only one locator is
+ given on the command line) the distance and beraing from your station
+ to the locator. For example:-
+
+
+
+ SH/QRA IO92QL
+ SH/QRA JN06 IN73
+
+
+
+
+ The first example will show the distance and bearing to the locator
+ from yourself, the second example will calculate the distance and
+ bearing from the first locator to the second. You can use 4 or 6
+ character locators.
+
+ It is also possible to convert a latitude and longitude to a locator
+ by using this command with a latitude and longitude as an argument,
+ for example:-
+
+
+
+ SH/QRA 52 41 N 0 58 E
+
+
+
+
+
+ 1\b12\b2.\b.5\b52\b2.\b. s\bsh\bho\bow\bw/\b/q\bqr\brz\bz
+
+ s\bsh\bho\bow\bw/\b/q\bqr\brz\bz <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show any callbook details on a callsign
+
+
+ This command queries the QRZ callbook server on the internet and
+ returns any information available for that callsign. This service is
+ provided for users of this software by http://www.qrz.com
+
+
+ 1\b12\b2.\b.5\b53\b3.\b. s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be
+
+ s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show the route to <callsign>
+
+
+ This command allows you to see to which node the callsigns specified
+ are connected. It is a sort of inverse sh/config.
+
+
+
+ sh/route n2tly
+
+
+
+
+
+ 1\b12\b2.\b.5\b54\b4.\b. s\bsh\bho\bow\bw/\b/s\bsa\bat\bte\bel\bll\bli\bit\bte\be
+
+ s\bsh\bho\bow\bw/\b/s\bsa\bat\bte\bel\bll\bli\bit\bte\be <\b<n\bna\bam\bme\be>\b> [\b[<\b<h\bho\bou\bur\brs\bs>\b> <\b<i\bin\bnt\bte\ber\brv\bva\bal\bl>\b>]\b] Show satellite tracking
+ data
+
+
+ Show the tracking data from your location to the satellite of your
+ choice from now on for the next few hours.
+
+ If you use this command without a satellite name it will display a
+ list of all the satellites known currently to the system.
+
+ If you give a name then you can obtain tracking data of all the passes
+ that start and finish 5 degrees below the horizon. As default it will
+ give information for the next three hours for every five minute
+ period.
+
+ You can alter the number of hours and the step size, within certain
+ limits.
+
+ Each pass in a period is separated with a row of '-----' characters
+
+ So for example:-
+
+
+
+ SH/SAT AO-10
+ SH/SAT FENGYUN1 12 2
+
+
+
+
+
+ 1\b12\b2.\b.5\b55\b5.\b. s\bsh\bho\bow\bw/\b/s\bsu\bun\bn
+
+ s
\bsh
\bho
\bow
\bw/
\b/s
\bsu
\bun
\bn [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show sun rise and set times
+
+
+ Show the sun rise and set times for a (list of) prefixes or callsigns,
+ together with the azimuth and elevation of the sun currently at those
+ locations.
+
+ If you don't specify any prefixes or callsigns, it will show the times
+ for your QTH (assuming you have set it with either SET/LOCATION or
+ SET/QRA), together with the current azimuth and elevation.
+
+ If all else fails it will show the sunrise and set times for the node
+ that you are connected to.
+
+ For example:-
+
+
+
+ SH/SUN
+ SH/SUN G1TLH K9CW ZS
+
+
+
+
+
+ 1\b12\b2.\b.5\b56\b6.\b. s\bsh\bho\bow\bw/\b/t\bti\bim\bme\be
+
+ s
\bsh
\bho
\bow
\bw/
\b/t
\bti
\bim
\bme
\be [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show the local time
+
+
+ If no prefixes or callsigns are given then this command returns the
+ local time and UTC as the computer has it right now. If you give some
+ prefixes then it will show UTC and UTC + the local offset (not
+ including DST) at the prefixes or callsigns that you specify.
+
+
+ 1\b12\b2.\b.5\b57\b7.\b. s\bsh\bho\bow\bw/\b/w\bwc\bcy\by
+
+ s\bsh\bho\bow\bw/\b/w\bwc\bcy\by Show the last 10 WCY broadcasts
+ s\bsh\bho\bow\bw/\b/w\bwc\bcy\by <\b<n\bn>\b> Show the last <n> WCY broadcasts
+
+
+ Display the most recent WCY information that has been received by the
+ system
+
+
+
+
+ 1\b12\b2.\b.5\b58\b8.\b. s\bsh\bho\bow\bw/\b/w\bww\bwv\bv
+
+ s\bsh\bho\bow\bw/\b/w\bww\bwv\bv Show the last 10 WWV broadcasts
+ s\bsh\bho\bow\bw/\b/w\bww\bwv\bv <\b<n\bn>\b> Show the last <n> WWV broadcasts
+
+
+ Display the most recent WWV information that has been received by the
+ system
+
+
+ 1\b12\b2.\b.5\b59\b9.\b. s\bsy\bys\bso\bop\bp
+
+ s\bsy\bys\bso\bop\bp Regain your privileges if you login remotely
+
+
+ The system automatically reduces your privilege level to that of a
+ normal user if you login in remotely. This command allows you to
+ regain your normal privilege level. It uses the normal system: five
+ numbers are returned that are indexes into the character array that is
+ your assigned password (see SET/PASSWORD). The indexes start from
+ zero.
+
+ You are expected to return a string which contains the characters
+ required in the correct order. You may intersperse those characters
+ with others to obscure your reply for any watchers. For example (and
+ these values are for explanation :-):
+
+
+
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
+
+
+
+
+ you type:-
+
+
+
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
+
+
+
+
+ They will all match. If there is no password you will still be offered
+ numbers but nothing will happen when you input a string. Any match is
+ case sensitive.
+
+
+ 1\b12\b2.\b.6\b60\b0.\b. t\bta\bal\blk\bk
+
+ t\bta\bal\blk\bk <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Enter talk mode with <callsign>
+ t\bta\bal\blk\bk <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> <\b<t\bte\bex\bxt\bt>\b> Send a text message to <callsign>
+ t\bta\bal\blk\bk <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> >\b> <\b<n\bno\bod\bde\be_\b_c\bca\bal\bll\bl>\b> [\b[<\b<t\bte\bex\bxt\bt>\b>]\b] Send a text message to
+ <callsign> via <node_call>
+
+
+ Send a short message to any other station that is visible on the
+ cluster system. You can send it to anyone you can see with a
+ SHOW/CONFIGURATION command, they don't have to be connected locally.
+
+ The second form of TALK is used when other cluster nodes are connected
+ with restricted information. This usually means that they don't send
+ the user information usually associated with logging on and off the
+ cluster.
+
+ If you know that G3JNB is likely to be present on GB7TLH, but you can
+ only see GB7TLH in the SH/C list but with no users, then you would use
+ the second form of the talk message.
+
+ If you want to have a ragchew with someone you can leave the text
+ message out and the system will go into 'Talk' mode. What this means
+ is that a short message is sent to the recipient telling them that you
+ are in a 'Talking' frame of mind and then you just type - everything
+ you send will go to the station that you asked for.
+
+ All the usual announcements, spots and so on will still come out on
+ your terminal.
+
+ If you want to do something (such as send a spot) you precede the
+ normal command with a '/' character, eg:-
+
+
+
+ /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
+ /HELP talk
+
+
+
+
+ To leave talk mode type:
+
+
+
+ /EX
+
+
+
+
+
+ 1\b12\b2.\b.6\b61\b1.\b. t\bty\byp\bpe\be
+
+ t\bty\byp\bpe\be <\b<f\bfi\bil\ble\bea\bar\bre\bea\ba>\b>/\b/<\b<n\bna\bam\bme\be>\b> Look at a file in one of the fileareas
+
+
+ Type out the contents of a file in a filearea. So, for example, in
+ filearea 'bulletins' you want to look at file 'arld051' you would
+ enter:-
+
+
+
+ TYPE bulletins/arld051
+
+
+
+
+ See also SHOW/FILES to see what fileareas are available and a list of
+ content.
+
+
+ 1\b12\b2.\b.6\b62\b2.\b. w\bwh\bho\bo
+
+ w\bwh\bho\bo Show who is physically connected locally
+
+
+ This is a quick listing that shows which callsigns are connected and
+ what sort of connection they have
+
+
+ 1\b12\b2.\b.6\b63\b3.\b. w\bwx\bx
+
+ w\bwx\bx <\b<t\bte\bex\bxt\bt>\b> Send a weather message to local users
+ w\bwx\bx f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b> Send a weather message to all cluster users
+
+
+ Weather messages can sometimes be useful if you are experiencing an
+ extreme that may indicate enhanced conditions
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
projects / spider.git / commitdiff