X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fusermanual_en.sgml;h=09c7a26ee321b042e04e39ba1ea1118aa9ceb7c9;hb=782ad549b29a1efec023ebcde840073a4676d8e8;hp=a5383cdbd7b25d72dfd2b0db017048d6dc8dee6a;hpb=7c3d8bfac8fa88490ef5473116ef73656934c4bf;p=spider.git diff --git a/sgml/usermanual_en.sgml b/sgml/usermanual_en.sgml index a5383cdb..09c7a26e 100644 --- a/sgml/usermanual_en.sgml +++ b/sgml/usermanual_en.sgml @@ -6,7 +6,7 @@ The DXSpider User Manual v1.50 Ian Maude, G0VGS, (g0vgs@gb7mbc.net) -February 2003 revision 0.2 +April 2003 revision 0.5 A complete reference for users of the DXSpider DXCluster program. @@ -962,6 +962,13 @@ 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. +A Filtering Tutorial + +

+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 + Hints, tips and common questions. @@ -1008,7 +1015,7 @@ user manual? also be included with every release of DXSpider. As always, if unsure, ask your sysop what version number is the latest. -The DXSpider command reference +The DXSpider Command Reference accept @@ -1273,6 +1280,60 @@ of 9 lines.

This will disconnect you from the cluster +chat <group> <text> + +

+ +chat <group> <text> Chat or Conference to a group + + +

+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:- + + + JOIN FOC (where FOC is the group name) + + +To leave a group type:- + + + LEAVE FOC + + +You can see which groups you are in by typing:- + + + STAT/USER + + +and you can see whether your mate is in the group, if he connects to the +same node as you, by typing:- + + + STAT/USER g1tlh + + +To send a message to a group type:- + + + CHAT FOC hello everyone + + +or + + + CH #9000 hello I am back + + +See also JOIN, LEAVE, SHOW/CHAT clear/announce [1|all]

@@ -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 <group> + +

+ +join <group> Join a chat or conference group + + +

+JOIN allows you to join a network wide conference group. To join a +group (called FOC in this case) type:- + + + JOIN FOC + + +See also CHAT, LEAVE, SHOW/CHAT kill <from msgno>-<to msgno>

@@ -1808,6 +1885,22 @@ this command. You can remove more than one message at a time.

+leave <group> + +

+ +leave <group> Leave a chat or conference group + + +

+LEAVE allows you to leave a network wide conference group. To leave a +group (called FOC in this case) type:- + + + LEAVE FOC + + +See also CHAT, JOIN, SHOW/CHAT links

@@ -2213,6 +2306,14 @@ You can carry on with the message until you are ready to send it. set/dx Allow DX messages to come out on your terminal +

+set/dxcq + +

+ +set/dxcq Show CQ Zones on the end of DX announcements + +

set/dxgrid @@ -2222,11 +2323,11 @@ You can carry on with the message until you are ready to send it.

-set/dxstate +set/dxitu

-set/dxstate Allow US State info on the end of DX announcements +set/dxitu Show ITU Zones on the end of DX announcements

@@ -2385,6 +2486,14 @@ Tell the system where you are. For example:- set/talk Allow TALK messages to come out on your terminal +

+set/usstate + +

+ +set/usstate Allow US State info on the end of DX announcements + +

set/wcy @@ -2410,6 +2519,18 @@ Tell the system where you are. For example:-

+show/chat [<group>] [<lines>] + +

+ +show/chat [<group>] [<lines>] Show any chat or conferencing + + +

+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. show/configuration [<node>]

@@ -2455,6 +2576,23 @@ that prefix.

Show all the nodes connected to this node. +show/contest <year and month> + +

+ +show/contest <year and month> Show all the contests for a month + + +

+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:- + + + SH/CONTEST sep2003 + SH/CONTEST 03 march + + show/date [<prefix>|<callsign>]

@@ -2604,6 +2742,35 @@ This can be done with the SHOW/DX command like this:- SH/DX dxcc w on 20m iota +show/dxqsl <callsign> + +

+ +show/dxqsl <callsign> Show any QSL info gathered from spots + + +

+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:- + + + sh/dxqsl 4k9w + + +You can check the raw input spots yourself with:- + + + sh/dx 4k9w qsl + + +This gives you more background information. show/dxstats [days] [date]

@@ -3327,6 +3494,22 @@ allows you to see them again. This is the default.

+unset/dxcq + +

+ +unset/dxcq Stop CQ Zones on the end of DX announcements + + +

+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. unset/dxgrid

@@ -3340,24 +3523,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. -unset/dxstate + +Conflicts with: SET/DXCQ, SET/DXITU + +Do a STAT/USER to see which flags you have set if you are confused. +unset/dxitu

-unset/dxstate Stop US State info on the end of DX announcements +unset/dxitu Stop ITU Zones on the end of DX announcements

-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. unset/echo

@@ -3454,6 +3639,28 @@ normal.

+unset/usstate + +

+ +unset/usstate Stop US State info on the end of DX announcements + + +

+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. unset/wcy