<title>The DXSpider User Manual v1.50</title>
<author>Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</author>
-<date>September 2002 revision 0.1</date>
+<date>March 2003 revision 0.4</date>
<abstract>
A complete reference for users of the DXSpider DXCluster program.
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.
+<sect1>A Filtering Tutorial
+
+<P>
+There is now an excellent primer/tutorial on filtering written by Jim
+Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly
+suggest you read. You can read it here
+<htmlurl url="filtering_en.html" name="The DXSpider User Filtering Primer">
<sect>Hints, tips and common questions.
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
<sect1>accept
<P>
This will disconnect you from the cluster
+<sect1>chat <group> <text>
+
+<P>
+<tt>
+<bf>chat <group> <text></bf> Chat or Conference to a group
+</tt>
+
+<P>
+It is now possible to JOIN a group and have network wide conferencing to that
+group. DXSpider does not (and probably will not) implement the AK1A
+conference mode as this seems very limiting, is hardly used and doesn't seem
+to work too well anyway.
+
+This system uses the existing ANN system and is compatible with both other
+DXSpider nodes and AK1A clusters (they use ANN/<group>).
+
+You can be a member of as many "groups" as you want. To join a group type:-
+
+<tscreen><verb>
+ JOIN FOC (where FOC is the group name)
+</verb></tscreen>
+
+To leave a group type:-
+
+<tscreen><verb>
+ LEAVE FOC
+</verb></tscreen>
+
+You can see which groups you are in by typing:-
+
+<tscreen><verb>
+ STAT/USER
+</verb></tscreen>
+
+and you can see whether your mate is in the group, if he connects to the
+same node as you, by typing:-
+
+<tscreen><verb>
+ STAT/USER g1tlh
+</verb></tscreen>
+
+To send a message to a group type:-
+
+<tscreen><verb>
+ CHAT FOC hello everyone
+</verb></tscreen>
+
+or
+
+<tscreen><verb>
+ CH #9000 hello I am back
+</verb></tscreen>
+
+See also JOIN, LEAVE, SHOW/CHAT
<sect1>clear/announce [1|all]
<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.
+<sect1>join <group>
+
+<P>
+<tt>
+<bf>join <group></bf> Join a chat or conference group
+</tt>
+
+<P>
+JOIN allows you to join a network wide conference group. To join a
+group (called FOC in this case) type:-
+
+<tscreen><verb>
+ JOIN FOC
+</verb></tscreen>
+
+See also CHAT, LEAVE, SHOW/CHAT
<sect1>kill <from msgno>-<to msgno>
<P>
</tt>
<P>
+<sect1>leave <group>
+
+<P>
+<tt>
+<bf>leave <group></bf> Leave a chat or conference group
+</tt>
+
+<P>
+LEAVE allows you to leave a network wide conference group. To leave a
+group (called FOC in this case) type:-
+
+<tscreen><verb>
+ LEAVE FOC
+</verb></tscreen>
+
+See also CHAT, JOIN, SHOW/CHAT
<sect1>links
<P>
<bf>set/dx</bf> Allow DX messages to come out on your terminal
</tt>
+<P>
+<sect1>set/dxcq
+
+<P>
+<tt>
+<bf>set/dxcq</bf> Show CQ Zones on the end of DX announcements
+</tt>
+
<P>
<sect1>set/dxgrid
</tt>
<P>
-<sect1>set/dxstate
+<sect1>set/dxitu
<P>
<tt>
-<bf>set/dxstate</bf> Allow US State info on the end of DX announcements
+<bf>set/dxitu</bf> Show ITU Zones on the end of DX announcements
</tt>
<P>
<bf>set/talk</bf> Allow TALK messages to come out on your terminal
</tt>
+<P>
+<sect1>set/usstate
+
+<P>
+<tt>
+<bf>set/usstate</bf> Allow US State info on the end of DX announcements
+</tt>
+
<P>
<sect1>set/wcy
</tt>
<P>
+<sect1>show/chat [<group>] [<lines>]
+
+<P>
+<tt>
+<bf>show/chat [<group>] [<lines>]</bf> Show any chat or conferencing
+</tt>
+
+<P>
+This command allows you to see any chat or conferencing that has
+occurred whilst you were away. SHOW/CHAT on its own will show data for
+all groups. If you use a group name then it will show only chat for
+that group.
<sect1>show/configuration [<node>]
<P>
<P>
Show all the nodes connected to this node.
+<sect1>show/contest <year and month>
+
+<P>
+<tt>
+<bf>show/contest <year and month></bf> Show all the contests for a month
+</tt>
+
+<P>
+Show all known contests which are maintained at http://www.sk3bg.se/contest/
+for a particular month or year. The format is reasonably flexible.
+For example:-
+
+<tscreen><verb>
+ SH/CONTEST sep2003
+ SH/CONTEST 03 march
+</verb></tscreen>
+
<sect1>show/date [<prefix>|<callsign>]
<P>
SH/DX dxcc w on 20m iota
</verb></tscreen>
+<sect1>show/dxqsl <callsign>
+
+<P>
+<tt>
+<bf>show/dxqsl <callsign></bf> Show any QSL info gathered from spots
+</tt>
+
+<P>
+The node collects information from the comment fields in spots (things
+like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
+
+This command allows you to interrogate that database and if the callsign
+is found will display the manager(s) that people have spotted. This
+information is NOT reliable, but it is normally reasonably accurate if
+it is spotted enough times.
+
+For example:-
+
+<tscreen><verb>
+ sh/dxqsl 4k9w
+</verb></tscreen>
+
+You can check the raw input spots yourself with:-
+
+<tscreen><verb>
+ sh/dx 4k9w qsl
+</verb></tscreen>
+
+This gives you more background information.
<sect1>show/dxstats [days] [date]
<P>
</tt>
<P>
+<sect1>unset/dxcq
+
+<P>
+<tt>
+<bf>unset/dxcq</bf> Stop CQ Zones on the end of DX announcements
+</tt>
+
+<P>
+Display both the Spotter's and the Spotted's CQ Zone on the end
+of a DX announcement (there is just enough room). Some user programs
+cannot cope with this. The Spotter's CQ is on the RHS of the
+time, the Spotted's CQ is on the LHS.
+
+Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
+
+Do a STAT/USER to see which flags you have set if you are confused.
<sect1>unset/dxgrid
<P>
of a DX announcement (there is just enough room). Some user programs
cannot cope with this. You can use this command to reset (or set)
this feature.
-<sect1>unset/dxstate
+
+Conflicts with: SET/DXCQ, SET/DXITU
+
+Do a STAT/USER to see which flags you have set if you are confused.
+<sect1>unset/dxitu
<P>
<tt>
-<bf>unset/dxstate</bf> Stop US State info on the end of DX announcements
+<bf>unset/dxitu</bf> Stop ITU Zones on the end of DX announcements
</tt>
<P>
-If the spotter's or spotted's US State is known it is output on the
-end of a DX announcement (there is just enough room).
+Display both the Spotter's and the Spotted's ITU Zone on the end
+of a DX announcement (there is just enough room). Some user programs
+cannot cope with this. The Spotter's ITU is on the RHS of the
+time, the Spotted's ITU is on the LHS.
-A spotter's state will appear on the RHS of the time (like
-SET/DXGRID) and the spotted's State will appear on the LHS of the
-time field. Any information found will override any locator
-information from SET/DXGRID.
+Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
-Some user programs cannot cope with this. You can use this command
-to reset (or set) this feature.
+Do a STAT/USER to see which flags you have set if you are confused.
<sect1>unset/echo
<P>
</tt>
<P>
+<sect1>unset/usstate
+
+<P>
+<tt>
+<bf>unset/usstate</bf> Stop US State info on the end of DX announcements
+</tt>
+
+<P>
+If the spotter's or spotted's US State is known it is output on the
+end of a DX announcement (there is just enough room).
+
+A spotter's state will appear on the RHS of the time (like
+SET/DXGRID) and the spotted's State will appear on the LHS of the
+time field. Any information found will override any locator
+information from SET/DXGRID.
+
+Some user programs cannot cope with this. You can use this command
+to reset (or set) this feature.
+
+Conflicts with: SET/DXCQ, SET/DXITU
+
+Do a STAT/USER to see which flags you have set if you are confused.
<sect1>unset/wcy
<P>
projects / spider.git / blobdiff