X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fusermanual_en.sgml;h=4bd3cd930edc9b1abe560069b8d08ac2667d0719;hb=caf197683012300feef595d20d55aa46cf3de0f8;hp=bac44d2f1d530817168be209a1dc1337d8119e13;hpb=ded9826c433e14be019cb8713ebfb5a7ff65ea13;p=spider.git diff --git a/sgml/usermanual_en.sgml b/sgml/usermanual_en.sgml index bac44d2f..4bd3cd93 100644 --- a/sgml/usermanual_en.sgml +++ b/sgml/usermanual_en.sgml @@ -4,9 +4,9 @@ -
+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
+
This will disconnect you from the cluster
+
+
+
+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:-
+
+
@@ -1766,6 +1827,22 @@ 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.
+
+
+
+JOIN allows you to join a network wide conference group. To join a
+group (called FOC in this case) type:-
+
+
@@ -1808,6 +1885,22 @@ this command. You can remove more than one message at a time.
+
+
+
+LEAVE allows you to leave a network wide conference group. To leave a
+group (called FOC in this case) type:-
+
+
@@ -2213,6 +2306,14 @@ You can carry on with the message until you are ready to send it.
+
+
+
-
-
@@ -2278,8 +2379,8 @@ eg:-
You can select the language that you want the cluster to use. Currently
-the languages available are en (English), de (German), es (Spanish)
-and nl (Dutch).
+the languages available are en (English), de (German), es (Spanish),
+Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
@@ -2385,6 +2486,14 @@ Tell the system where you are. For example:-
+
+
+
+
+
+
+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.
@@ -2455,6 +2576,23 @@ that prefix.
Show all the nodes connected to this node.
+
+
+
+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:-
+
+
@@ -2558,7 +2696,50 @@ any order to the basic SHOW/DX command, they are:-
You can also use this with the 'by' keyword so
eg by W dxcc
-
+
+
+
+
+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:-
+
+
@@ -2614,6 +2829,20 @@ This can be done with the SHOW/DX command like this:-
Show the total DX spots for the last <days> no of days (default is 31),
starting from a <date> (default: today).
+
+
+
+Normally SHOW/DX outputs spot data in a different format to the
+realtime data. This is a deliberate policy (so you can tell the
+difference between the two). Some logging programs cannot handle
+this so SHOW/FDX outputs historical data in real time format.
+
+This is an alias for: SHOW/DX real
@@ -2834,6 +3063,25 @@ propagation data.
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.
+
+
+
+SHOW/DX potentially shows all the spots available in the system. Using
+SHOW/MYDX will, instead, filter the availble spots using any spot filter
+that you have set, first.
+
+This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
+you to customise the spots that you receive.
+
+So if you have said: ACC/SPOT on hf
+
+Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
+options on SH/DX can still be used.
@@ -3327,6 +3575,22 @@ allows you to see them again. This is the default.
+
+
+
+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.
@@ -3340,24 +3604,26 @@ that if the spotter's grid square is known it is output on the end
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.
-
-
-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.
@@ -3454,6 +3720,28 @@ normal.
+
+
+
+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.