1 The DXSpider User Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
3 March 2003 revision 0.4
5 A complete reference for users of the DXSpider DXCluster program.
6 ______________________________________________________________________
13 1.1 What is a DX Cluster?
14 1.2 So what is DXSpider?
16 2. Logins and logouts.
22 3. Setting your personal details.
23 4. Getting and posting DX.
27 5. Headings and propagation
33 6.1 Making announcements.
34 6.2 Listing announcements.
39 9.1 The "directory" command.
45 10. Filtering (From version 1.45)
46 10.1 General filter rules
49 10.4 Advanced filtering
50 10.5 A Filtering Tutorial
52 11. Hints, tips and common questions.
54 11.2 accept/announce [0-9] <pattern>
55 11.3 accept/spots [0-9] <pattern>
56 11.4 accept/wcy [0-9] <pattern>
57 11.5 accept/wwv [0-9] <pattern>
59 11.7 announce full <text>
61 11.9 blank [<string>] [<nn>]
63 11.11 chat <group> <text>
64 11.12 clear/announce [1|all]
65 11.13 clear/route [1|all]
66 11.14 clear/spots [0-9|all]
67 11.15 clear/wcy [1|all]
68 11.16 clear/wwv [1|all]
70 11.18 dbshow <dbname> <key>
72 11.20 directory <from>-<to>
75 11.23 directory from <call>
78 11.26 directory subject <string>
79 11.27 directory to <call>
80 11.28 dx [by <call>] <freq> <call> <remarks>
85 11.33 kill <from msgno>-<to msgno>
86 11.34 kill <msgno> [<msgno..]
87 11.35 kill <msgno> [<msgno> ...]
88 11.36 kill from <regex>
95 11.43 reject/announce [0-9] <pattern>
96 11.44 reject/spots [0-9] <pattern>
97 11.45 reject/wcy [0-9] <pattern>
98 11.46 reject/wwv [0-9] <pattern>
101 11.49 reply b <msgno>
102 11.50 reply noprivate <msgno>
103 11.51 reply rr <msgno>
104 11.52 send <call> [<call> ...]
105 11.53 send copy <msgno> <call>
106 11.54 send noprivate <call>
107 11.55 send private <call>
109 11.57 set/address <your address>
118 11.66 set/email <email> ...
120 11.68 set/homenode <node>
121 11.69 set/language <lang>
122 11.70 set/location <lat & long>
124 11.72 set/name <your name>
125 11.73 set/page <lines per page>
127 11.75 set/prompt <string>
128 11.76 set/qra <locator>
129 11.77 set/qth <your qth>
135 11.83 show/chat [<group>] [<lines>]
136 11.84 show/configuration [<node>]
137 11.85 show/configuration/node
138 11.86 show/contest <year and month>
139 11.87 show/date [<prefix>|<callsign>]
140 11.88 show/db0sdx <callsign>
142 11.90 show/dxcc <prefix>
143 11.91 show/dxqsl <callsign>
144 11.92 show/dxstats [days] [date]
145 11.93 show/files [<filearea> [<string>]]
147 11.95 show/hfstats [days] [date]
148 11.96 show/hftable [days] [date] [prefix ...]
149 11.97 show/moon [ndays] [<prefix>|<callsign>]
150 11.98 show/muf <prefix> [<hours>][long]
151 11.99 show/newconfiguration [<node>]
152 11.100 show/newconfiguration/node
153 11.101 show/prefix <callsign>
154 11.102 show/qra <lat> <long>
155 11.103 show/qra <locator> [<locator>]
156 11.104 show/qrz <callsign>
157 11.105 show/route <callsign> ...
158 11.106 show/satellite <name> [<hours> <interval>]
159 11.107 show/station [<callsign> ..]
160 11.108 show/sun [ndays] [<prefix>|<callsign>]
161 11.109 show/time [<prefix>|<callsign>]
162 11.110 show/usdb [call ..]
163 11.111 show/vhfstats [days] [date]
164 11.112 show/vhftable [days] [date] [prefix ...]
167 11.115 show/wm7d <callsign>
171 11.119 talk <call> > <node> [<text>]
172 11.120 talk <call> [<text>]
173 11.121 type <filearea>/<name>
174 11.122 unset/announce
184 11.132 unset/logininfo
185 11.133 unset/privilege
194 11.142 wx full <text>
197 ______________________________________________________________________
201 1.1. What is a DX Cluster?
203 A DX Cluster is a packet node where DX chasers on any band or mode can
204 post rare or interesting stations that they have worked or heard. Of
205 course other people are doing the same thing too, so you can find new
206 DX as well as telling others about the stations you have worked.
207 Clusters tend to be linked to each other so that the amount of people
208 using them is increased, thereby increasing the amount of posted DX.
209 Other information can be found on clusters such as on-line call books,
210 mail etc. You can talk to other stations connected to the cluster
211 network too, in real time, whether at the node you are logged into or
212 on another node connected to the network. You can also use converse
213 mode, where several stations can talk to each other in the same way.
214 Of course, the DX is still posted to you all the while!
217 1.2. So what is DXSpider?
219 PacketCluster nodes have been around since roughly 1985. The original
220 PacketCluster idea came from Dick Newell, AK1A, and ran under DOS. In
221 about 1992 Dick stopped the development of the PacketCluster software
222 for amateur radio. Many systems are still using this relatively old
225 There are several new compatible cluster programs around now,
226 including DXSpider. DXSpider is a clone of PacketCluster software
227 that runs under several operating systems including Linux and Windows.
228 Linux is fast becoming the choice for amateur radio stations because
229 of it's flexibility, reliability and the lack of the memory
230 limitations of DOS. Linux supports multitasking and is also
231 multiuser. It has support for AX25, ROSE, NetROM and TCPIP built in,
232 making it the ideal choice for amateur radio. It is also totally
235 DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
236 exercise in perl programming. It has developed rapidly and today is a
237 very powerful cluster program. It was designed to be totally
238 compatible with the AK1A program, although several commands have been
239 extended to improve functionality.
241 This manual is designed to help you become familiar with the commands
242 that DXSpider supports and to help you get the best from the program
243 so you can enjoy working that rare DX! As DXSpider is being improved
244 all the time, commands will be added as time goes by, so make sure you
245 have the most upto date version of this manual. The latest version
246 will always be included with the cluster program so if you are unsure,
247 simply ask your sysop. The manual will also be available on the
252 2. Logins and logouts.
254 You might not think that there is a lot of point of including a
255 section on how to log in and out of DXSpider. However, you would be
256 suprised at the difficulties some people have in simply getting in and
259 There are several ways a login might be achieved, dependant on how the
260 sysop has DXSpider configured. It is impossible for me to cover all
261 variations but here are the basic ones.
266 Simplicity itself. The usual CONNECT command will log you straight
267 into the cluster and you will not have to do anything else.
268 Obviously, you will have to connect to the correct callsign. Some
269 nodes use an SSID with their call so you would have to add that.
282 There are several possibilities here, dependant on how the sysop has
283 configured his system. If you are connecting via netrom then you are
284 most probably connecting from another station. Listing the nodes in
285 that station with the NODES command will tell you what callsign or
286 netrom alias to connect to. Then just issue the connect command from
287 there. It is possible that the netrom alias may connect you to a node
288 with an alias for the cluster, such as DXC. Just type this and you
300 With telnet connections, the source callsign is not seen by DXSpider,
301 so you will be asked to login with your callsign. To telnet to
302 DXSpider, you would connect to a specific port. There is no standard
303 at the moment for a cluster telnet port but ask the sysop if you are
314 All the above are possible ways of connecting to a DXSpider cluster.
315 You may have some or all of these available to you. There may be one
316 or two additional ways to connect dependant on the network local to
317 you. However I am sure you get the idea.
322 Logging out can be done by simply issuing the standard BYE command.
324 You could also send a disconnect if you are using AX25, or a CLOSE
325 command if you are connected via telnet. If you do not log out
326 gracefully using one of the above commands, you may find you are
327 unable to get a full connect next time. This may also happen if a
328 netrom connection drops. You may get connected, but nothing else will
329 happen because the program thinks you are still connected and will not
330 let you connect twice under the same call. However you could
331 reconnect by adding a number to the end of your call, for example
332 G0YLM-2. This can be done by either altering your MYCALL setting in
333 the TNC or by altering your program configuration.
336 3. Setting your personal details.
338 Once logged in to the cluster, you should set your details so that
339 anybody who wishes to contact you can find out who and where you are.
340 There are four items to set, your name, qth, location and home node.
341 Setting these details also allows the use of the SHOW/HEADING and
342 SHOW/SUN commands from within the cluster. Unless you set your QTH
343 and location, these commands cannot function. Once you have set your
344 name, DXSpider will greet you with it next time you login. Your QTH
345 setting is where you live and it is a good idea to add your locator to
346 this as the location setting is converted to latitude and longitude
347 once inputted. You can actually set your location in
348 latitude/longitude or as a locator. Setting your home node will tell
349 the program where you wish mail to be sent to you.
356 set/qth Morecambe, Lancashire IO84NB
357 set/location 48 34 n 12 12 e
363 4. Getting and posting DX.
365 When all is said and done, this is the main function of a DX cluster.
366 In its simplest form you can just connect to the node and you will
367 start to receive DX spots almost immediately! You can check on recent
368 postings in either a general manner or on a particular band or mode.
369 You can even check DX by callsign or a fragment of a callsign. Of
370 course, once you get the hang of things, it is expected that you start
371 posting some yourself! After all, there would be no clusters if
372 people did not post DX and you get the added thrill of the hunt!
377 As we have already said, it is possible just to connect to the cluster
378 and you will receive spots automatically. However, you may wish to
379 check on spots just posted. Maybe you wish to see if a particular
380 band is open or if a certain callsign is active, perhaps a DXpedition.
381 The command to do this is SHOW/DX. Without any other arguments, this
382 command will output the last 10 spots posted. It is possible to look
383 at more than this, for example the last 20 or 50 spots, by adding the
384 number to the command. You can make it even more specific by adding a
385 band in either wavelength or frequency, and/or any additional
386 information such as QSL details.
398 will show the last 10, 5 and 20 spots received by the cluster
411 will show the last 5, 10 or 20 spots on 20 metres only.
413 It is also possible to check for certain callsigns, or fragments of
414 callsigns in the same way.
425 would show the last 5 or 10 dx spots containing the callsign g0vgs.
428 You can check for DX by offset and also by specifying a comment to
441 would show the spots that arrived between 30 and 40 spots ago and any
442 spots with the word iota in the comment field. The case of the
443 comment is not important.
445 Checking DX posted on a certain day is possible too. All you have to
446 do here is to specify how many days ago it was like this ...
456 It is of course possible to specify multiple arguments.
460 show/dx 20 prefix 9a on vhf day 30
464 This would show the last 20 spots posted by or about calls with the
465 prefix 9a on vhf 30 days ago.
467 As you can see the SHOW/DX command is very flexible, so if you are not
468 sure whether something will work or not, try it and see! More
469 information can be found in the Command Set section.
474 To post DX you use the DX command. The syntax is shown below.
480 dx (frequency) (callsign) (remarks)
484 Where frequency is in kilohertz and the callsign is the callsign of
485 the station you have worked or heard, (ie not your own callsign!).
486 The remarks section allows you to add information like the operators
487 name or perhaps a location. Actually DXSpider will allow the
488 frequency and callsign fields to be entered in any order.
494 dx 14004 pa3ezl OP Aurelio 599
498 In fact, all the following will give the same result...
502 dx 14004 pa3ezl OP Aurelio 599
503 dx pa3ezl 14004 OP Aurelio 599
504 dx pa3ezl 14.004 OP Aurelio 599
508 This posting, or callout as it is known, will be forwarded to all
509 other connected stations both at the cluster you are connected to and
510 other active clusters in the network. The callout will also be sent
511 to you as proof of receipt.
514 5. Headings and propagation
516 There are three commands in DXSpider to help you get the best DX
517 possible. These are SHOW/SUN, SHOW/MOON and SHOW/HEADING. These
518 commands will only work for you if you have entered your personal
519 details. They use your entered location as a reference, so if you
520 have not entered it or have entered it incorrectly they will not
521 return the correct information.
524 The SHOW/SUN command can be used in three different ways. It can be
525 used to show sunrise and sunset times for your own station, a
526 particular callsign or a prefix.
536 The output from this would look something like this ..
541 Location Rise Set Azim Elev
542 G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
550 would look like this ...
555 Location Rise Set Azim Elev
556 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
560 You can also specify multiple arguments like this ...
564 sh/sun gw4veq 5b4ab zs
568 and then the output would look like this ...
572 sh/sun gw4veq 5b4ab zs
573 Location Rise Set Azim Elev
574 GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9
575 5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
576 ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
577 ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
578 ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
583 The SHOW/MOON command works in the same way as the SHOW/SUN command.
584 This program however, calculates the rise and set times of the moon
585 for a prefix or callsign, together with the current azimuth and
586 elevation of the sun at these locations.
596 The output from this command would look like this ..
601 Location Rise Set Azim Elev RGain dB
602 EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
606 You can see that the output is similar to the SHOW/SUN command, with
607 slightly different fields.
612 The SHOW/HEADING command works in the same way as the SHOW/SUN and
613 SHOW/MOON commands but outputs beam headings for a specified callsign
614 or prefix. Reciprocal beam headings are also calculated.
624 The output from this command would look like this ..
629 ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
630 ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
631 ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
632 ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
638 6.1. Making announcements.
640 Occasionally, you may wish to post something that does not fall into
641 the normal parameters for a DX callout. You may wish to tell
642 everybody connected that 10 FM is open for example, or ask if anyone
643 knows the QSL manager for a certain callsign etc. You can do this
644 using the ANNOUNCE command.
650 announce 10 FM is open in IO84NB to europe.
654 That would let everyone know locally that this was the case, however
655 it would not be forwarded to other nodes connected. To send
656 announcements to other connected nodes as well, you would use the FULL
663 announce full Anyone seen EA7WA today?
667 Be cautious in your use of announce full. There are many other tools
668 available to get the information you require and the judicious use of
669 this command is frowned upon as it creates a great deal of traffic
673 6.2. Listing announcements.
675 You can list previous announcements in the standard format with the
676 SHOW command. As before you can list just the last 5 or as many as
684 show/announcements 10
690 You can check which nodes are connected in the network, who is logged
691 on locally, who is logged on at all the nodes or even just one node in
692 particular. This is handy if you wish to see whether a friend is
693 connected at the node they use. To see who is connected to the nodes,
694 the SHOW/CONFIGURATION command is used.
701 show/configuration/nodes
702 show/configuration (node_call)
703 show/configuration (prefix)
707 The first of our three examples would output something like this,
716 GB7BIG (GD0TEP) GD3UMW
717 GB7BPQ (G0INA) G0RCI G3AKU G3OCA
719 GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
720 G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
723 GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
724 G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
726 (GB7DXG) GU6EFB GU7DHI
727 GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
729 GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
734 You will notice that EI5TCR is showing only that it has 7 users and
735 not giving the actual callsigns. This means that this node is on a
736 limited protocol of some kind, probably because of a contest situation
737 where slow radio links can block up and fail if too much information
738 is sent between nodes.
740 The second example would just show the nodes connected in the network,
747 GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
748 GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
749 GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
750 GB7YDX KL7G N2TLY (ON0DXK)
751 GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
758 If we insert the node_call pi4tue-8 into the third example, then this
764 PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
765 F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
766 ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
767 PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
772 As you can see, only the users of the requested node are shown.
774 You can also use a prefix to show only a group of nodes. For example
775 you may only wish to see who is connected to the nodes in the UK. To
776 do this simply use a prefix like this ...
779 show/configuration gb7
783 To show the locally connected users, the SHOW/USERS command is used
793 The output of this command would look like this,
797 Callsigns connected to GB7MBC
798 G0JHC G0NEI G0VGS G0VGS-2 G0YLM
805 You can send a single comment or start a dedicated talk session to
806 another user by using the TALK command.
809 Talk mode is used to send a one line comment or greeting to a specific
810 user connected either at your node or another in the network. You can
811 also enter into a dedicated talk session with another user. Talks
812 will be automatically forwarded to other nodes if the station you are
813 talking to is not connected locally. You can find out who is
814 connected by using the SHOW/CONFIGURATION command, (described
821 talk g0rdi Having a good day Iain?
824 This example would send the line "Having a good day Iain?" to the user
825 g0rdi but would leave you in normal mode.
830 Entering Talkmode, /EX to end, /<cmd> to run a command
835 As you can see, you can still run commands whilst in talk mode.
836 Simply prefix the command with a / like /sh/dx and you will get the
837 expected output. If the user is connected to another node, you may
838 have to use a slightly extended version of the TALK command.
846 To exit talk mode, you issue the command /ex.
848 Whilst in talk mode you will still receive DX spots. This means that
849 you can chat to a friend whilst working DX.
854 You can send and receive both personal mail and bulletins with
855 DXSpider quite easily.
858 9.1. The "directory" command.
860 To list mail you would use the DIRECTORY command. On its own, this
861 command will output the last ten messages received by the node, either
862 to or from yourself or bulletins such as "DX" and "ALL". As with
863 other commands you can display more by specifying a number with the
864 command. You should be aware that Spider will accept these commands
865 by separating with either a slash or a space, so dir new and dir/new
866 work in the same way.
878 Of course most of the time you will only want to list new mail sent to
879 you personally since your last login. However you might also like to
880 check for general mail received by the node. In fact if there is new
881 mail for you, the cluster will tell you when you login. You will also
882 be informed if new mail arrives for you during the time you are logged
883 in. Mail is not only sent to callsigns though. Mail can also be sent
884 to subjects like "all" or "local" or "dx" etc. You can treat these
885 bulletins in the same way as personal mail with the directory command.
895 directory/from <call>
899 The last option will only show mail from a callsign if it was sent to
900 you personally or was sent as a bulletin. There are some additional
901 commands and these can be found in the DXSpider Command Reference
907 The output of the DIRECTORY command could be something like this.
912 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
913 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
914 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
915 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
916 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
917 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
918 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
919 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
920 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
921 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
922 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
926 The first column is the actual message number. If the message is a
927 personal one to you, you will see a letter 'p' after this number. If
928 the message has been read, there will be a '-' between the message
929 number and the 'p'. This only works for personal messages. The next
930 column shows the file size of the message. The third column shows the
931 address the message was sent to and the next column shows who sent it.
932 The rest is fairly self-explanatory.
934 Reading a message is as simple as typing read, followed by the message
935 number that you wish to read.
945 will read message number 25. However the mail will be displayed in
946 it's entirety unless you specify a page length. You can set your page
947 length to any number you like and when the message reaches that number
948 of lines you will get a prompt giving you options.
959 Sending mail is done in the time honoured way. First you specify a
960 recipient for the message, then you will be prompted for a subject.
961 Once you have done this you will be asked to type your message.
962 Please remember that there is no automatic word wrap, so unless you
963 are using a client that wraps lines automatically, remember to hit
964 return at the end of each line.
971 Enter Subject (30 characters):
973 Enter Message /EX to send or /ABORT to exit
975 Just a quick note to say that I can make Thursday after all. The
976 appointment I had has cancelled so we are go!
982 At this point you can either hit return and enter /ex to send the
983 message or use /abort at any time to abort it. You can now display
984 the message in the normal way. There are several send options and
985 these are listed in the Command Set section. These include sending
986 mail to several recipients and asking for a return receipt.
990 9.4. Replying to mail.
992 If mail is addressed to you or to a bulletin address, you can use the
993 REPLY command to reply to it. Using this command, the subject will be
994 automatically set for you as "Re: subject", whatever the subject was.
1006 To delete a message, you use the delete command. You can only delete
1007 messages sent to or received by yourself. Bulletins are dealt with
1008 automatically or by the sysop.
1009 10. Filtering (From version 1.45)
1011 10.1. General filter rules
1013 Upto v1.44 it was not possible for the user to set their own filters.
1014 From v1.45 though that has all changed. It is now possible to set
1015 filters for just about anything you wish. If you have just updated
1016 from an older version of DXSpider you will need to update your new
1017 filters. You do not need to do anything with your old filters, they
1018 will be renamed as you update.
1021 There are 3 basic commands involved in setting and manipulating
1022 filters. These are accept, reject and clear. First we will look
1023 generally at filtering. There are a number of things you can filter in
1024 the DXSpider system. They all use the same general mechanism.
1027 In general terms you can create a 'reject' or an 'accept' filter which
1028 can have up to 10 lines in it. You do this using, for example ...
1037 where ..... are the specific commands for that type of filter. There
1038 are filters for spots, wwv, announce, wcy and (for sysops) connects.
1039 See each different accept or reject command reference for more
1042 There is also a command to clear out one or more lines in a filter.
1052 There is clear/xxxx command for each type of filter.
1055 and you can check that your filters have worked by the command ...
1063 For now we are going to use spots for the examples, but you can apply
1064 the same principles to all types of filter.
1068 10.2. Types of filter
1070 There are two main types of filter, accept or reject. You can use
1071 either to achieve the result you want dependent on your own preference
1072 and which is more simple to do. It is pointless writing 8 lines of
1073 reject filters when 1 accept filter would do the same thing! Each
1074 filter has 10 lines (of any length) which are tried in order. If a
1075 line matches then the action you have specified is taken (ie reject
1076 means ignore it and accept means take it)
1079 If you specify reject filters, then any lines that arrive that match
1080 the filter will be dumped but all else will be accepted. If you use
1081 an accept filter, then ONLY the lines in the filter will be accepted
1082 and all else will be dumped. For example if you have a single line
1087 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1091 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
1094 If you set a reject filter like this ...
1098 reject/spots on hf/cw
1102 Then you will get everything EXCEPT HF CW spots. You could make this
1103 single filter even more flexible. For example, if you are interested
1104 in IOTA and will work it even on CW even though normally you are not
1105 interested in CW, then you could say ...
1109 reject/spots on hf/cw and not info iota
1113 But in that case you might only be interested in iota and say:-
1117 accept/spots not on hf/cw or info iota
1121 which achieves exactly the same thing. You should choose one or the
1122 other until you are comfortable with the way it works. You can mix
1123 them if you wish (actually you can have an accept AND a reject on the
1124 same line) but don't attempt this until you are sure you know what you
1128 You can arrange your filter lines into logical units, either for your
1129 own understanding or simply convenience. Here is an example ...
1130 reject/spots 1 on hf/cw
1131 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
1135 What this does is to ignore all HF CW spots and also rejects any spots
1136 on VHF which don't either originate or spot someone in Europe.
1139 This is an example where you would use a line number (1 and 2 in this
1140 case), if you leave the digit out, the system assumes '1'. Digits
1141 '0'-'9' are available. This make it easier to see just what filters
1142 you have set. It also makes it more simple to remove individual
1143 filters, during a contest for example.
1146 You will notice in the above example that the second line has
1147 brackets. Look at the line logically. You can see there are 2
1148 separate sections to it. We are saying reject spots that are VHF or
1149 above APART from those in zones 14, 15 and 16 (either spotted there or
1150 originated there). If you did not have the brackets to separate the 2
1151 sections, then Spider would read it logically from the front and see a
1152 different expression entirely ...
1156 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
1160 The simple way to remember this is, if you use OR - use brackets.
1161 Whilst we are here CASE is not important. 'And BY_Zone' is just the
1162 same as 'and by_zone'.
1164 As mentioned earlier, setting several filters can be more flexible
1165 than simply setting one complex one. Doing it in this way means that
1166 if you want to alter your filter you can just redefine or remove one
1167 or more lines of it or one line. For example ...
1171 reject/spots 1 on hf/ssb
1175 would redefine our earlier example, or
1183 To remove all the filter lines in the spot filter ...
1191 10.3. Filter options
1193 You can filter in several different ways. The options are listed in
1194 the various helpfiles for accept, reject and filter.
1197 10.4. Advanced filtering
1199 Once you are happy with the results you get, you may like to
1203 The previous example that filters hf/cw spots and accepts vhf/uhf
1204 spots from EU can be written with a mixed filter, for example ...
1210 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
1214 Note that the first filter has not been specified with a number. This
1215 will automatically be assumed to be number 1. In this case, we have
1216 said reject all HF spots in the CW section of the bands but accept all
1217 others at HF. Also accept anything in VHF and above spotted in or by
1218 operators in the zones 14, 15 and 16. Each filter slot actually has a
1219 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
1223 It was mentioned earlier that after a reject test that doesn't match,
1224 the default for following tests is 'accept', the reverse is true for
1225 'accept'. In the example what happens is that the reject is executed
1226 first, any non hf/cw spot is passed to the accept line, which lets
1227 through everything else on HF. The next filter line lets through just
1228 VHF/UHF spots from EU.
1231 10.5. A Filtering Tutorial
1233 There is now an excellent primer/tutorial on filtering written by Jim
1234 Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly
1235 suggest you read. You can read it here The DXSpider User Filtering
1239 11. Hints, tips and common questions.
1241 Q.These commands seem very long! Can I shorten them?
1243 A.Of course you can and the usual abbreviations work. If you are
1246 Q.I am not sure if this command is correct. Can I cause any harm if I
1249 A.Do not be afraid to try a command to see if it will work, at the
1250 worst you will get an error message. If you require any help on a
1251 command, just type help followed by the command you want help on.
1252 Look at the "DXSpider Command Reference" section to see what help can
1256 Q.How should I use the announce command?
1258 A.With respect. Use the command by all means, but please only use the
1259 "full" extension if absolutely necessary. It can create a LOT of
1260 messages passing between clusters.
1262 Q.I like to be working in the shack while logged into the cluster but
1263 I can't be looking at the screen all the time. How can I be alerted
1264 when anything happens?
1266 A.Use the SET/BEEP command. You can find information on this in the
1267 "DXSpider Command Reference" section.
1269 Q.I got disconnected from the cluster and now I can't log back in
1270 again. What is wrong?
1272 A.Probably the cluster thinks you are still logged on and will not let
1273 you reconnect using the same call to prevent loops. Try logging on
1274 again adding an ssid to your callsign as DXSpider treats G0YLM and
1275 G0YLM-1 as different users.
1277 Q.How do I know if I have got the latest version of this user manual?
1279 A.The latest and greatest will always be on the Website. It will also
1280 be included with every release of DXSpider. As always, if unsure, ask
1281 your sysop what version number is the latest.
1287 accept Set a filter to accept something
1290 Create a filter to accept something
1292 There are 2 types of filter, accept and reject. See HELP FILTERING
1295 11.2. accept/announce [0-9] <pattern>
1297 accept/announce [0-9] <pattern> Set an 'accept' filter line for
1301 Create an 'accept this announce' line for a filter.
1303 An accept filter line means that if the announce matches this filter
1304 it is passed onto the user. See HELP FILTERING for more info. Please
1305 read this to understand how filters work - it will save a lot of grief
1308 You can use any of the following things in this line:-
1312 info <string> eg: iota or qsl
1313 by <prefixes> eg: G,M,2
1315 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1316 origin_itu <prefixes or numbers> or: G,GM,GW
1317 origin_zone <prefixes or numbers>
1318 origin_state <states> eg: VA,NH,RI,NH
1319 by_dxcc <prefixes or numbers>
1320 by_itu <prefixes or numbers>
1321 by_zone <prefixes or numbers>
1324 wx 1 filter WX announces
1325 dest <prefixes> eg: 6MUK,WDX (distros)
1334 acc/ann 2 by_zone 14,15,16
1335 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1350 acc/ann by_state va,nh,ri,nh
1354 You can use the tag 'all' to accept everything eg:
1362 but this probably for advanced users...
1364 11.3. accept/spots [0-9] <pattern>
1366 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
1369 Create an 'accept this spot' line for a filter.
1371 An accept filter line means that if the spot matches this filter it is
1372 passed onto the user. See HELP FILTERING for more info. Please read
1373 this to understand how filters work - it will save a lot of grief
1376 You can use any of the following things in this line:-
1380 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1381 on <range> same as 'freq'
1382 call <prefixes> eg: G,PA,HB9
1383 info <string> eg: iota or qsl
1385 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1386 call_itu <prefixes or numbers> or: G,GM,GW
1387 call_zone <prefixes or numbers>
1388 call_state <states> eg: VA,NH,RI,ME
1389 by_dxcc <prefixes or numbers>
1390 by_itu <prefixes or numbers>
1391 by_zone <prefixes or numbers>
1392 by_state <states> eg: VA,NH,RI,ME
1398 For frequencies, you can use any of the band names defined in
1399 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1400 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1401 this is more efficient than saying simply: freq HF (but don't get too
1409 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1413 You can use the tag 'all' to accept everything, eg:
1425 acc/spots by_state VA,NH,RI,MA,ME
1429 but this probably for advanced users...
1433 11.4. accept/wcy [0-9] <pattern>
1435 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
1438 It is unlikely that you will want to do this, but if you do then you
1439 can filter on the following fields:-
1443 by <prefixes> eg: G,M,2
1445 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1446 origin_itu <prefixes or numbers> or: G,GM,GW
1447 origin_zone <prefixes or numbers>
1448 by_dxcc <prefixes or numbers>
1449 by_itu <prefixes or numbers>
1450 by_zone <prefixes or numbers>
1455 There are no examples because WCY Broadcasts only come from one place
1456 and you either want them or not (see UNSET/WCY if you don't want
1459 This command is really provided for future use.
1461 See HELP FILTER for information.
1463 11.5. accept/wwv [0-9] <pattern>
1465 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
1468 It is unlikely that you will want to do this, but if you do then you
1469 can filter on the following fields:-
1473 by <prefixes> eg: G,M,2
1475 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1476 origin_itu <prefixes or numbers> or: G,GM,GW
1477 origin_zone <prefixes or numbers>
1478 by_dxcc <prefixes or numbers>
1479 by_itu <prefixes or numbers>
1480 by_zone <prefixes or numbers>
1489 accept/wwv by_zone 4
1493 is probably the only useful thing to do (which will only show WWV
1494 broadcasts by stations in the US).
1496 See HELP FILTER for information.
1498 11.6. announce <text>
1500 announce <text> Send an announcement to LOCAL users only
1503 <text> is the text of the announcement you wish to broadcast
1505 11.7. announce full <text>
1507 announce full <text> Send an announcement cluster wide
1510 This will send your announcement cluster wide
1512 11.8. apropos <string>
1514 apropos <string> Search help database for <string>
1517 Search the help database for <string> (it isn't case sensitive), and
1518 print the names of all the commands that may be relevant.
1520 11.9. blank [<string>] [<nn>]
1522 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
1525 In its basic form this command prints one or more blank lines. However
1526 if you pass it a string it will replicate the string for the width of
1527 the screen (default 80) and then print that one or more times, so:
1535 prints two blank lines
1543 prints a row of - characters once.
1551 prints 'abcabcabcabcabcabc....'
1553 This is really only of any use in a script file and you can print a
1560 bye Exit from the cluster
1563 This will disconnect you from the cluster
1565 11.11. chat <group> <text>
1567 chat <group> <text> Chat or Conference to a group
1570 It is now possible to JOIN a group and have network wide conferencing
1571 to that group. DXSpider does not (and probably will not) implement the
1572 AK1A conference mode as this seems very limiting, is hardly used and
1573 doesn't seem to work too well anyway.
1575 This system uses the existing ANN system and is compatible with both
1576 other DXSpider nodes and AK1A clusters (they use ANN/<group>).
1578 You can be a member of as many "groups" as you want. To join a group
1583 JOIN FOC (where FOC is the group name)
1587 To leave a group type:-
1595 You can see which groups you are in by typing:-
1603 and you can see whether your mate is in the group, if he connects to
1604 the same node as you, by typing:-
1612 To send a message to a group type:-
1616 CHAT FOC hello everyone
1624 CH #9000 hello I am back
1628 See also JOIN, LEAVE, SHOW/CHAT
1630 11.12. clear/announce [1|all]
1632 clear/announce [1|all] Clear a announce filter line
1635 This command allows you to clear (remove) a line in a annouce filter
1636 or to remove the whole filter.
1638 see CLEAR/SPOTS for a more detailed explanation.
1640 11.13. clear/route [1|all]
1642 clear/route [1|all] Clear a route filter line
1645 This command allows you to clear (remove) a line in a route filter or
1646 to remove the whole filter.
1648 see CLEAR/SPOTS for a more detailed explanation.
1650 11.14. clear/spots [0-9|all]
1652 clear/spots [0-9|all] Clear a spot filter line
1655 This command allows you to clear (remove) a line in a spot filter or
1656 to remove the whole filter.
1658 If you have a filter:-
1663 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1675 you will be left with:-
1679 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1691 the filter will be completely removed.
1693 11.15. clear/wcy [1|all]
1695 clear/wcy [1|all] Clear a WCY filter line
1698 This command allows you to clear (remove) a line in a WCY filter or to
1699 remove the whole filter.
1701 see CLEAR/SPOTS for a more detailed explanation.
1703 11.16. clear/wwv [1|all]
1705 clear/wwv [1|all] Clear a WWV filter line
1708 This command allows you to clear (remove) a line in a WWV filter or to
1709 remove the whole filter.
1711 see CLEAR/SPOTS for a more detailed explanation.
1715 dbavail Show a list of all the Databases in the system
1718 Title says it all really, this command lists all the databases defined
1719 in the system. It is also aliased to SHOW/COMMAND.
1721 11.18. dbshow <dbname> <key>
1723 dbshow <dbname> <key> Display an entry, if it exists, in a database
1726 This is the generic user interface to the database to the database
1727 system. It is expected that the sysop will add an entry to the local
1728 Aliases file so that users can use the more familiar AK1A style of
1737 but if he hasn't and the database really does exist (use DBAVAIL or
1738 SHOW/COMMAND to find out) you can do the same thing with:
1748 directory List messages
1752 11.20. directory <from>-<to>
1754 directory <from>-<to> List messages <from> message <to> message
1757 List the messages in the messages directory.
1759 If there is a 'p' one space after the message number then it is a
1760 personal message. If there is a '-' between the message number and the
1762 You can use shell escape characters such as '*' and '?' in the <call>
1765 You can combine some of the various directory commands together eg:-
1776 DIR SUBJECT IOTA 200-250
1780 You can abbreviate all the commands to one letter and use ak1a
1790 11.21. directory <nn>
1792 directory <nn> List last <nn> messages
1796 11.22. directory all
1798 directory all List all messages
1802 11.23. directory from <call>
1804 directory from <call> List all messages from <call>
1808 11.24. directory new
1810 directory new List all new messages
1814 11.25. directory own
1816 directory own List your own messages
1820 11.26. directory subject <string>
1822 directory subject <string> List all messages with <string> in subject
1826 11.27. directory to <call>
1828 directory to <call> List all messages to <call>
1832 11.28. dx [by <call>] <freq> <call> <remarks>
1834 dx [by <call>] <freq> <call> <remarks> Send a DX spot
1837 This is how you send a DX Spot to other users. You can, in fact, now
1838 enter the <freq> and the <call> either way round.
1848 will all give the same result. You can add some remarks to the end of
1849 the command and they will be added to the spot.
1853 DX FR0G 144600 this is a test
1857 You can credit someone else by saying:-
1861 DX by G1TLH FR0G 144.600 he isn't on the cluster
1865 The <freq> is compared against the available bands set up in the
1866 cluster. See SHOW/BANDS for more information.
1872 echo <line> Echo the line to the output
1875 This command is useful in scripts and so forth for printing the line
1876 that you give to the command to the output. You can use this in
1877 user_default scripts and the SAVE command for titling and so forth
1879 The script will interpret certain standard "escape" sequences as
1884 \t - becomes a TAB character (0x09 in ascii)
1885 \a - becomes a BEEP character (0x07 in ascii)
1886 \n - prints a new line
1890 So the following example:-
1894 echo GB7DJK is a dxcluster
1902 GB7DJK is a dxcluster
1906 on the output. You don't need a \n on the end of the line you want to
1909 A more complex example:-
1913 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
1933 filtering... Filtering things in DXSpider
1936 There are a number of things you can filter in the DXSpider system.
1937 They all use the same general mechanism.
1939 In general terms you can create a 'reject' or an 'accept' filter which
1940 can have up to 10 lines in it. You do this using, for example:-
1949 where ..... are the specific commands for that type of filter. There
1950 are filters for spots, wwv, announce, wcy and (for sysops) connects.
1951 See each different accept or reject command reference for more
1954 There is also a command to clear out one or more lines in a filter and
1955 one to show you what you have set. They are:-
1972 There is clear/xxxx command for each type of filter.
1974 For now we are going to use spots for the examples, but you can apply
1975 the principles to all types of filter.
1977 There are two main types of filter 'accept' or 'reject'; which you use
1978 depends entirely on how you look at the world and what is least
1979 writing to achieve what you want. Each filter has 10 lines (of any
1980 length) which are tried in order. If a line matches then the action
1981 you have specified is taken (ie reject means ignore it and accept
1984 The important thing to remember is that if you specify a 'reject'
1985 filter (all the lines in it say 'reject/spots' (for instance)) then if
1986 a spot comes in that doesn't match any of the lines then you will get
1987 it BUT if you specify an 'accept' filter then any spots that don't
1988 match are dumped. For example if I have a one line accept filter:-
1992 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1994 then automatically you will ONLY get VHF spots from or to CQ zones 14
1995 15 and 16. If you set a reject filter like:
1999 reject/spots on hf/cw
2003 Then you will get everything EXCEPT HF CW spots, If you am interested
2004 in IOTA and will work it even on CW then you could say:-
2008 reject/spots on hf/cw and not info iota
2012 But in that case you might only be interested in iota and say:-
2016 accept/spots not on hf/cw or info iota
2020 which is exactly the same. You should choose one or the other until
2021 you are confortable with the way it works. Yes, you can mix them
2022 (actually you can have an accept AND a reject on the same line) but
2023 don't try this at home until you can analyse the results that you get
2024 without ringing up the sysop for help.
2026 Another useful addition now is filtering by US state
2030 accept/spots by_state VA,NH,RI,ME
2034 You can arrange your filter lines into logical units, either for your
2035 own understanding or simply convenience. I have one set frequently:-
2039 reject/spots 1 on hf/cw
2040 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
2044 What this does is to ignore all HF CW spots (being a class B I can't
2045 read any CW and couldn't possibly be interested in HF :-) and also
2046 rejects any spots on VHF which don't either originate or spot someone
2049 This is an exmaple where you would use the line number (1 and 2 in
2050 this case), if you leave the digit out, the system assumes '1'. Digits
2052 You can leave the word 'and' out if you want, it is implied. You can
2053 use any number of brackets to make the 'expression' as you want it.
2054 There are things called precedence rules working here which mean that
2055 you will NEED brackets in a situation like line 2 because, without it,
2060 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
2064 annoying, but that is the way it is. If you use OR - use brackets.
2065 Whilst we are here CASE is not important. 'And BY_Zone' is just 'and
2068 If you want to alter your filter you can just redefine one or more
2069 lines of it or clear out one line. For example:-
2073 reject/spots 1 on hf/ssb
2085 To remove the filter in its entirty:-
2093 There are similar CLEAR commands for the other filters:-
2105 Once you are happy with the results you get, you may like to
2108 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
2109 can be written with a mixed filter, eg:
2115 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
2119 each filter slot actually has a 'reject' slot and an 'accept' slot.
2120 The reject slot is executed BEFORE the accept slot.
2122 It was mentioned earlier that after a reject test that doesn't match,
2123 the default for following tests is 'accept', the reverse is true for
2124 first, any non hf/cw spot is passed to the accept line, which lets
2125 thru everything else on HF.
2127 The next filter line lets through just VHF/UHF spots from EU.
2131 help The HELP Command
2134 HELP is available for a number of commands. The syntax is:-
2142 Where <cmd> is the name of the command you want help on.
2144 All commands can be abbreviated, so SHOW/DX can be abbreviated to
2145 SH/DX, ANNOUNCE can be shortened to AN and so on.
2147 Look at the APROPOS <string> command which will search the help
2148 database for the <string> you specify and give you a list of likely
2149 commands to look at with HELP.
2153 join <group> Join a chat or conference group
2156 JOIN allows you to join a network wide conference group. To join a
2157 group (called FOC in this case) type:-
2165 See also CHAT, LEAVE, SHOW/CHAT
2167 11.33. kill <from msgno>-<to msgno>
2169 kill <from msgno>-<to msgno> Delete a range of messages
2173 11.34. kill <msgno> [<msgno..]
2175 kill <msgno> [<msgno..] Delete a message from the local system
2179 11.35. kill <msgno> [<msgno> ...]
2181 kill <msgno> [<msgno> ...] Remove or erase a message from the system
2184 You can get rid of any message to or originating from your callsign
2185 using this command. You can remove more than one message at a time.
2187 11.36. kill from <regex>
2189 kill from <regex> Delete messages FROM a callsign or pattern
2193 11.37. kill to <regex>
2195 kill to <regex> Delete messages TO a callsign or pattern
2199 11.38. leave <group>
2201 leave <group> Leave a chat or conference group
2204 LEAVE allows you to leave a network wide conference group. To leave a
2205 group (called FOC in this case) type:-
2213 See also CHAT, JOIN, SHOW/CHAT
2217 links Show which nodes is physically connected
2220 This is a quick listing that shows which links are connected and some
2221 information about them. See WHO for a list of all connections.
2225 read Read the next unread personal message addressed to you
2231 read <msgno> Read the specified message
2234 You can read any messages that are sent as 'non-personal' and also any
2235 message either sent by or sent to your callsign.
2240 reject Set a filter to reject something
2243 Create a filter to reject something
2245 There are 2 types of filter, accept and reject. See HELP FILTERING
2248 11.43. reject/announce [0-9] <pattern>
2250 reject/announce [0-9] <pattern> Set a 'reject' filter line for
2254 Create an 'reject this announce' line for a filter.
2256 A reject filter line means that if the announce matches this filter it
2257 is passed onto the user. See HELP FILTERING for more info. Please read
2258 this to understand how filters work - it will save a lot of grief
2261 You can use any of the following things in this line:-
2265 info <string> eg: iota or qsl
2266 by <prefixes> eg: G,M,2
2268 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2269 origin_itu <prefixes or numbers> or: G,GM,GW
2270 origin_zone <prefixes or numbers>
2271 origin_state <states> eg: VA,NH,RI,ME
2272 by_dxcc <prefixes or numbers>
2273 by_itu <prefixes or numbers>
2274 by_zone <prefixes or numbers>
2275 by_state <states> eg: VA,NH,RI,ME
2277 wx 1 filter WX announces
2278 dest <prefixes> eg: 6MUK,WDX (distros)
2286 rej/ann by_zone 14,15,16 and not by G,M,2
2290 You can use the tag 'all' to reject everything eg:
2298 but this probably for advanced users...
2301 11.44. reject/spots [0-9] <pattern>
2303 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
2306 Create a 'reject this spot' line for a filter.
2308 A reject filter line means that if the spot matches this filter it is
2309 dumped (not passed on). See HELP FILTERING for more info. Please read
2310 this to understand how filters work - it will save a lot of grief
2313 You can use any of the following things in this line:-
2317 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
2318 on <range> same as 'freq'
2319 call <prefixes> eg: G,PA,HB9
2320 info <string> eg: iota or qsl
2322 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2323 call_itu <prefixes or numbers> or: G,GM,GW
2324 call_zone <prefixes or numbers>
2325 call_state <states> eg: VA,NH,RI,ME
2326 by_dxcc <prefixes or numbers>
2327 by_itu <prefixes or numbers>
2328 by_zone <prefixes or numbers>
2329 by_state <states> eg: VA,NH,RI,ME
2335 For frequencies, you can use any of the band names defined in
2336 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
2337 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
2338 this is more efficient than saying simply: on HF (but don't get too
2346 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
2350 You can use the tag 'all' to reject everything eg:
2358 but this probably for advanced users...
2362 11.45. reject/wcy [0-9] <pattern>
2364 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
2367 It is unlikely that you will want to do this, but if you do then you
2368 can filter on the following fields:-
2372 by <prefixes> eg: G,M,2
2374 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2375 origin_itu <prefixes or numbers> or: G,GM,GW
2376 origin_zone <prefixes or numbers>
2377 by_dxcc <prefixes or numbers>
2378 by_itu <prefixes or numbers>
2379 by_zone <prefixes or numbers>
2384 There are no examples because WCY Broadcasts only come from one place
2385 and you either want them or not (see UNSET/WCY if you don't want
2388 This command is really provided for future use.
2390 See HELP FILTER for information.
2392 11.46. reject/wwv [0-9] <pattern>
2394 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
2397 It is unlikely that you will want to do this, but if you do then you
2398 can filter on the following fields:-
2402 by <prefixes> eg: G,M,2
2404 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2405 origin_itu <prefixes or numbers> or: G,GM,GW
2406 origin_zone <prefixes or numbers>
2407 by_dxcc <prefixes or numbers>
2408 by_itu <prefixes or numbers>
2409 by_zone <prefixes or numbers>
2418 reject/wwv by_zone 14,15,16
2422 is probably the only useful thing to do (which will only show WWV
2423 broadcasts by stations in the US).
2425 See HELP FILTER for information.
2429 reply Reply (privately) to the last message that you have read
2433 11.48. reply <msgno>
2435 reply <msgno> Reply (privately) to the specified message
2439 11.49. reply b <msgno>
2441 reply b <msgno> Reply as a Bulletin to the specified message
2445 11.50. reply noprivate <msgno>
2447 reply noprivate <msgno> Reply as a Bulletin to the specified message
2451 11.51. reply rr <msgno>
2453 reply rr <msgno> Reply to the specified message with read receipt
2456 You can reply to a message and the subject will automatically have
2457 "Re:" inserted in front of it, if it isn't already present.
2459 You can also use all the extra qualifiers such as RR, PRIVATE,
2460 NOPRIVATE, B that you can use with the SEND command (see SEND for
2463 11.52. send <call> [<call> ...]
2465 send <call> [<call> ...] Send a message to one or more callsigns
2469 11.53. send copy <msgno> <call>
2471 send copy <msgno> <call> Send a copy of a message to someone
2475 11.54. send noprivate <call>
2477 send noprivate <call> Send a message to all stations
2480 All the SEND commands will create a message which will be sent either
2481 to an individual callsign or to one of the 'bulletin' addresses.
2483 SEND <call> on its own acts as though you had typed SEND PRIVATE, that
2484 is it will mark the message as personal and send it to the cluster
2485 node that that callsign is connected to. If the <call> you have
2486 specified is in fact a known bulletin category on your node (eg: ALL)
2487 then the message should automatically become a bulletin.
2489 You can have more than one callsign in all of the SEND commands.
2491 You can have multiple qualifiers so that you can have for example:-
2495 SEND RR COPY 123 PRIVATE G1TLH G0RDI
2499 which should send a copy of message 123 to G1TLH and G0RDI and you
2500 will receive a read receipt when they have read the message.
2502 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
2503 is an alias for SEND PRIVATE
2505 The system will ask you for a subject. Conventionally this should be
2506 no longer than 29 characters for compatibility. Most modern cluster
2507 software should accept more.
2509 You will now be prompted to start entering your text.
2511 You finish the message by entering '/EX' on a new line. For instance:
2522 If you have started a message and you don't want to keep it then you
2523 can abandon the message with '/ABORT' on a new line, like:-
2529 oh I just can't be bothered with this
2534 If you abort the message it will NOT be sent.
2536 When you are entering the text of your message, most normal output
2537 (such as DX announcements and so on are suppressed and stored for
2538 latter display (upto 20 such lines are stored, as new ones come along,
2539 so the oldest lines are dropped).
2541 Also, you can enter normal commands commands (and get the output
2542 immediately) whilst in the middle of a message. You do this by typing
2543 the command preceeded by a '/' character on a new line, so:-
2547 /dx g1tlh 144010 strong signal
2551 Will issue a dx annoucement to the rest of the cluster.
2553 Also, you can add the output of a command to your message by
2554 preceeding the command with '//', thus :-
2562 This will show YOU the output from SH/VHFTABLE and also store it in
2565 You can carry on with the message until you are ready to send it.
2567 11.55. send private <call>
2569 send private <call> Send a personal message
2573 11.56. send rr <call>
2575 send rr <call> Send a message and ask for a read receipt
2579 11.57. set/address <your address>
2581 set/address <your address> Record your postal address
2587 set/announce Allow announce messages to come out on your terminal
2593 set/anntalk Allow talk like announce messages on your terminal
2599 set/beep Add a beep to DX and other messages on your terminal
2605 set/dx Allow DX messages to come out on your terminal
2611 set/dxcq Show CQ Zones on the end of DX announcements
2617 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
2623 set/dxitu Show ITU Zones on the end of DX announcements
2629 set/echo Make the cluster echo your input
2633 11.66. set/email <email> ...
2635 set/email <email> ... Set email address(es) and forward your personals
2641 set/here Tell the system you are present at your terminal
2645 11.68. set/homenode <node>
2647 set/homenode <node> Set your normal cluster callsign
2650 Tell the cluster system where you normally connect to. Any Messages
2651 sent to you will normally find their way there should you not be
2659 11.69. set/language <lang>
2661 set/language <lang> Set the language you want to use
2664 You can select the language that you want the cluster to use.
2665 Currently the languages available are en (English), de (German), es
2666 (Spanish) and nl (Dutch).
2668 11.70. set/location <lat & long>
2670 set/location <lat & long> Set your latitude and longitude
2674 11.71. set/logininfo
2676 set/logininfo Inform when a station logs in locally
2679 11.72. set/name <your name>
2681 set/name <your name> Set your name
2684 Tell the system what your name is eg:-
2691 11.73. set/page <lines per page>
2693 set/page <lines per page> Set the lines per page
2696 Tell the system how many lines you wish on a page when the number of
2697 line of output from a command is more than this. The default is 20.
2698 Setting it explicitly to 0 will disable paging.
2706 The setting is stored in your user profile.
2710 set/password Set your own password
2713 This command only works for a 'telnet' user (currently). It will only
2714 work if you have a password already set. This initial password can
2715 only be set by the sysop.
2717 When you execute this command it will ask you for your old password,
2718 then ask you to type in your new password twice (to make sure you get
2719 it right). You may or may not see the data echoed on the screen as you
2720 type, depending on the type of telnet client you have.
2722 11.75. set/prompt <string>
2724 set/prompt <string> Set your prompt to <string>
2728 11.76. set/qra <locator>
2730 set/qra <locator> Set your QRA Grid locator
2733 Tell the system what your QRA (or Maidenhead) locator is. If you have
2734 not done a SET/LOCATION then your latitude and longitude will be set
2735 roughly correctly (assuming your locator is correct ;-). For example:-
2742 11.77. set/qth <your qth>
2744 set/qth <your qth> Set your QTH
2747 Tell the system where you are. For example:-
2750 SET/QTH East Dereham, Norfolk
2756 set/talk Allow TALK messages to come out on your terminal
2762 set/usstate Allow US State info on the end of DX announcements
2768 set/wcy Allow WCY messages to come out on your terminal
2774 set/wwv Allow WWV messages to come out on your terminal
2780 set/wx Allow WX messages to come out on your terminal
2784 11.83. show/chat [<group>] [<lines>]
2786 show/chat [<group>] [<lines>] Show any chat or conferencing
2789 This command allows you to see any chat or conferencing that has
2790 occurred whilst you were away. SHOW/CHAT on its own will show data for
2791 all groups. If you use a group name then it will show only chat for
2794 11.84. show/configuration [<node>]
2796 show/configuration [<node>] Show all the nodes and users visible
2799 This command allows you to see all the users that can be seen and the
2800 nodes to which they are connected.
2802 This command is normally abbreviated to: sh/c
2804 Normally, the list returned will be just for the nodes from your
2805 country (because the list otherwise will be very long).
2810 will produce a complete list of all nodes.
2812 BE WARNED: the list that is returned can be VERY long
2814 It is possible to supply a node or part of a prefix and you will get a
2815 list of the users for that node or list of nodes starting with that
2828 11.85. show/configuration/node
2830 show/configuration/node Show all the nodes connected locally
2833 Show all the nodes connected to this node.
2835 11.86. show/contest <year and month>
2837 show/contest <year and month> Show all the contests for a month
2840 Show all known contests which are maintained at
2841 http://www.sk3bg.se/contest/ for a particular month or year. The
2842 format is reasonably flexible. For example:-
2851 11.87. show/date [<prefix>|<callsign>]
2853 show/date [<prefix>|<callsign>] Show the local time
2856 This is very nearly the same as SHOW/TIME, the only difference the
2857 format of the date string if no arguments are given.
2859 If no prefixes or callsigns are given then this command returns the
2860 local time and UTC as the computer has it right now. If you give some
2861 prefixes then it will show UTC and UTC + the local offset (not
2862 including DST) at the prefixes or callsigns that you specify.
2864 11.88. show/db0sdx <callsign>
2866 show/db0sdx <callsign> Show QSL infomation from DB0SDX database
2869 This command queries the DB0SDX QSL server on the internet and returns
2870 any information available for that callsign. This service is provided
2871 for users of this software by http://www.qslinfo.de.
2873 See also SHOW/QRZ, SHOW/WM7D.
2877 show/dx Interrogate the spot database
2880 If you just type SHOW/DX you will get the last so many spots (sysop
2881 configurable, but usually 10).
2883 In addition you can add any number of these commands in very nearly
2884 any order to the basic SHOW/DX command, they are:-
2888 on <band> - eg 160m 20m 2m 23cm 6mm
2889 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2890 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
2895 <number> - the number of spots you want
2896 <from>-<to> - <from> spot no <to> spot no in the selected list
2901 <prefix> - for a spotted callsign beginning with <prefix>
2902 *<suffix> - for a spotted callsign ending in <suffix>
2903 *<string>* - for a spotted callsign containing <string>
2907 day <number> - starting <number> days ago
2908 day <from>-<to> - <from> days <to> days ago
2913 info <text> - any spots containing <text> in the info or remarks
2917 by <call> - any spots spotted by <call> (spotter <call> is the
2922 qsl - this automatically looks for any qsl info on the call
2923 held in the spot database.
2927 iota [<iota>] - If the iota island number is missing it will look for
2928 the string iota and anything which looks like an iota
2929 island number. If you specify then it will look for
2934 qra [<locator>] - this will look for the specific locator if you specify
2935 one or else anything that looks like a locator.
2939 dxcc - treat the prefix as a 'country' and look for spots
2940 from that country regardless of actual prefix.
2945 You can also use this with the 'by' keyword so
2955 SH/DX on 20m info iota
2956 SH/DX 9a on vhf day 30
2962 SH/DX dxcc oq2 by w dxcc
2966 11.90. show/dxcc <prefix>
2968 show/dxcc <prefix> Interrogate the spot database by country
2971 This command takes the <prefix> (which can be a full or partial
2972 callsign if desired), looks up which internal country number it is and
2973 then displays all the spots as per SH/DX for that country.
2975 This is now an alias for 'SHOW/DX DXCC'
2977 The options for SHOW/DX also apply to this command. e.g.
2982 SH/DXCC W on 20m iota
2986 This can be done with the SHOW/DX command like this:-
2991 SH/DX dxcc w on 20m iota
2995 11.91. show/dxqsl <callsign>
2997 show/dxqsl <callsign> Show any QSL info gathered from spots
3000 The node collects information from the comment fields in spots (things
3001 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
3003 This command allows you to interrogate that database and if the
3004 callsign is found will display the manager(s) that people have
3005 spotted. This information is NOT reliable, but it is normally
3006 reasonably accurate if it is spotted enough times.
3015 You can check the raw input spots yourself with:-
3023 This gives you more background information.
3025 11.92. show/dxstats [days] [date]
3027 show/dxstats [days] [date] Show the DX Statistics
3030 Show the total DX spots for the last <days> no of days (default is
3031 31), starting from a <date> (default: today).
3033 11.93. show/files [<filearea> [<string>]]
3035 show/files [<filearea> [<string>]] List the contents of a filearea
3038 SHOW/FILES on its own will show you a list of the various fileareas
3039 available on the system. To see the contents of a particular file area
3047 where <filearea> is the name of the filearea you want to see the con-
3050 You can also use shell globbing characters like '*' and '?' in a
3051 string to see a selection of files in a filearea eg:-
3054 SH/FILES bulletins arld*
3058 See also TYPE - to see the contents of a file.
3062 show/filter Show the contents of all the filters you have set
3065 Show the contents of all the filters that are set. This command
3066 displays all the filters set - for all the various categories.
3068 11.95. show/hfstats [days] [date]
3070 show/hfstats [days] [date] Show the HF DX Statistics
3073 Show the HF DX spots breakdown by band for the last <days> no of days
3074 (default is 31), starting from a <date> (default: today).
3078 11.96. show/hftable [days] [date] [prefix ...]
3080 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
3083 Show the HF DX Spotter table for the list of prefixes for the last
3084 <days> no of days (default is 31), starting from a <date> (default:
3087 If there are no prefixes then it will show the table for your country.
3089 Remember that some countries have more than one "DXCC country" in them
3090 (eg G :-), to show them (assuming you are not in G already which is
3091 specially treated in the code) you must list all the relevant prefixes
3095 sh/hftable g gm gd gi gj gw gu
3099 Note that the prefixes are converted into country codes so you don't
3100 have to list all possible prefixes for each country.
3102 If you want more or less days than the default simply include the
3103 number you require:-
3111 If you want to start at a different day, simply add the date in some
3116 sh/hftable 2 25nov02
3117 sh/hftable 2 25-nov-02
3119 sh/hftable 2 25/11/02
3123 This will show the stats for your DXCC for that CQWW contest weekend.
3125 You can specify either prefixes or full callsigns (so you can see how
3126 you did against all your mates). You can also say 'all' which will
3127 then print the worldwide statistics.
3135 11.97. show/moon [ndays] [<prefix>|<callsign>]
3137 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
3139 Show the Moon rise and set times for a (list of) prefixes or
3140 callsigns, together with the azimuth and elevation of the sun
3141 currently at those locations.
3143 If you don't specify any prefixes or callsigns, it will show the times
3144 for your QTH (assuming you have set it with either SET/LOCATION or
3145 SET/QRA), together with the current azimuth and elevation.
3147 In addition, it will show the illuminated fraction of the moons disk.
3149 If all else fails it will show the Moonrise and set times for the node
3150 that you are connected to.
3161 You can also use this command to see into the past or the future, so
3162 if you want to see yesterday's times then do:-
3170 or in three days time:-
3178 Upto 366 days can be checked both in the past and in the future.
3180 Please note that the rise and set times are given as the UT times of
3181 rise and set on the requested UT day.
3183 11.98. show/muf <prefix> [<hours>][long]
3185 show/muf <prefix> [<hours>][long] Show the likely propagation to a
3189 This command allow you to estimate the likelihood of you contacting a
3190 station with the prefix you have specified. The output assumes a
3191 modest power of 20dBW and receiver sensitivity of -123dBm (about
3194 The result predicts the most likely operating frequencies and signal
3195 levels for high frequency (shortwave) radio propagation paths on
3196 specified days of the year and hours of the day. It is most useful for
3197 paths between 250 km and 6000 km, but can be used with reduced
3198 accuracy for paths shorter or longer than this.
3200 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
3201 used to predict the MUF given the predicted flux, day of the year,
3202 hour of the day and geographic coordinates of the transmitter and
3203 receiver. This routine is reasonably accurate for the purposes here,
3204 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
3205 than the programs used by major shortwave broadcasting organizations,
3206 such as the Voice of America.
3208 The command will display some header information detailing its
3209 assumptions, together with the locations, latitude and longitudes and
3210 bearings. It will then show UTC (UT), local time at the other end
3211 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
3212 (Zen) and the likely signal strengths. Then for each frequency for
3213 which the system thinks there is a likelihood of a circuit it prints a
3216 The value is currently a likely S meter reading based on the
3217 conventional 6dB / S point scale. If the value has a '+' appended it
3218 means that it is 1/2 an S point stronger. If the value is preceeded by
3219 an 'm' it means that there is likely to be much fading and by an 's'
3220 that the signal is likely to be noisy.
3222 By default SHOW/MUF will show the next two hours worth of data. You
3223 can specify anything up to 24 hours worth of data by appending the no
3224 of hours required after the prefix. For example:-
3236 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
3237 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
3238 Location Lat / Long Azim
3239 East Dereham, Norfolk 52 41 N 0 57 E 47
3240 United-States-W 43 0 N 87 54 W 299
3241 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
3242 18 23 11.5 -35 mS0+ mS2 S3
3243 19 0 11.2 -41 mS0+ mS2 S3
3247 indicating that you will have weak, fading circuits on top band and
3248 80m but usable signals on 40m (about S3).
3258 will get you the above display, but with the next 24 hours worth of
3268 Gives you an estimate of the long path propagation characterics. It
3269 should be noted that the figures will probably not be very useful, nor
3270 terrible accurate, but it is included for completeness.
3272 11.99. show/newconfiguration [<node>]
3274 show/newconfiguration [<node>] Show all the nodes and users visible
3277 This command allows you to see all the users that can be seen and the
3278 nodes to which they are connected.
3280 This command produces essentially the same information as
3281 SHOW/CONFIGURATION except that it shows all the duplication of any
3282 routes that might be present It also uses a different format which may
3283 not take up quite as much space if you don't have any loops.
3285 BE WARNED: the list that is returned can be VERY long
3287 11.100. show/newconfiguration/node
3289 show/newconfiguration/node Show all the nodes connected locally
3292 Show all the nodes connected to this node in the new format.
3294 11.101. show/prefix <callsign>
3296 show/prefix <callsign> Interrogate the prefix database
3299 This command takes the <callsign> (which can be a full or partial
3300 callsign or a prefix), looks up which internal country number it is
3301 and then displays all the relevant prefixes for that country together
3302 with the internal country no, the CQ and ITU regions.
3306 11.102. show/qra <lat> <long>
3308 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
3311 This is a multipurpose command that allows you either to calculate the
3312 distance and bearing between two locators or (if only one locator is
3313 given on the command line) the distance and beraing from your station
3314 to the locator. For example:-
3323 The first example will show the distance and bearing to the locator
3324 from yourself, the second example will calculate the distance and
3325 bearing from the first locator to the second. You can use 4 or 6
3327 It is also possible to convert a latitude and longitude to a locator
3328 by using this command with a latitude and longitude as an argument,
3333 SH/QRA 52 41 N 0 58 E
3337 11.103. show/qra <locator> [<locator>]
3339 show/qra <locator> [<locator>] Show distance between QRA Grid locators
3343 11.104. show/qrz <callsign>
3345 show/qrz <callsign> Show any callbook details on a callsign
3348 This command queries the QRZ callbook server on the internet and
3349 returns any information available for that callsign. This service is
3350 provided for users of this software by http://www.qrz.com
3352 See also SHOW/WM7D for an alternative.
3354 11.105. show/route <callsign> ...
3356 show/route <callsign> ... Show the route to the callsign
3359 This command allows you to see to which node the callsigns specified
3360 are connected. It is a sort of inverse sh/config.
3368 11.106. show/satellite <name> [<hours> <interval>]
3370 show/satellite <name> [<hours> <interval>] Show tracking data
3373 Show the tracking data from your location to the satellite of your
3374 choice from now on for the next few hours.
3376 If you use this command without a satellite name it will display a
3377 list of all the satellites known currently to the system.
3379 If you give a name then you can obtain tracking data of all the passes
3380 that start and finish 5 degrees below the horizon. As default it will
3381 give information for the next three hours for every five minute
3384 You can alter the number of hours and the step size, within certain
3387 Each pass in a period is separated with a row of '-----' characters
3394 SH/SAT FENGYUN1 12 2
3398 11.107. show/station [<callsign> ..]
3400 show/station [<callsign> ..] Show information about a callsign
3403 Show the information known about a callsign and whether (and where)
3404 that callsign is connected to the cluster.
3412 If no callsign is given then show the information for yourself.
3414 11.108. show/sun [ndays] [<prefix>|<callsign>]
3416 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
3419 Show the sun rise and set times for a (list of) prefixes or callsigns,
3420 together with the azimuth and elevation of the sun currently at those
3423 If you don't specify any prefixes or callsigns, it will show the times
3424 for your QTH (assuming you have set it with either SET/LOCATION or
3425 SET/QRA), together with the current azimuth and elevation.
3427 If all else fails it will show the sunrise and set times for the node
3428 that you are connected to.
3435 SH/SUN G1TLH K9CW ZS
3439 You can also use this command to see into the past or the future, so
3440 if you want to see yesterday's times then do:-
3448 or in three days time:-
3454 Upto 366 days can be checked both in the past and in the future.
3456 Please note that the rise and set times are given as the UT times of
3457 rise and set on the requested UT day.
3459 11.109. show/time [<prefix>|<callsign>]
3461 show/time [<prefix>|<callsign>] Show the local time
3464 If no prefixes or callsigns are given then this command returns the
3465 local time and UTC as the computer has it right now. If you give some
3466 prefixes then it will show UTC and UTC + the local offset (not
3467 including DST) at the prefixes or callsigns that you specify.
3469 11.110. show/usdb [call ..]
3471 show/usdb [call ..] Show information held on the FCC Call database
3474 Show the City and State of a Callsign held on the FCC database if his
3475 is being run on this system, eg:-
3483 11.111. show/vhfstats [days] [date]
3485 show/vhfstats [days] [date] Show the VHF DX Statistics
3488 Show the VHF DX spots breakdown by band for the last <days> no of days
3489 (default is 31), starting from a date (default: today).
3491 11.112. show/vhftable [days] [date] [prefix ...]
3493 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
3496 Show the VHF DX Spotter table for the list of prefixes for the last
3497 <days> no of days (default is 31), starting from a date (default:
3500 If there are no prefixes then it will show the table for your country.
3502 Remember that some countries have more than one "DXCC country" in them
3503 (eg G :-), to show them (assuming you are not in G already which is
3504 specially treated in the code) you must list all the relevant prefixes
3508 sh/vhftable g gm gd gi gj gw gu
3512 Note that the prefixes are converted into country codes so you don't
3513 have to list all possible prefixes for each country.
3515 If you want more or less days than the default simply include the
3516 number you require:-
3524 If you want to start at a different day, simply add the date in some
3529 sh/vhftable 2 25nov02
3530 sh/vhftable 2 25-nov-02
3531 sh/vhftable 2 021125
3532 sh/vhftable 2 25/11/02
3536 This will show the stats for your DXCC for that CQWW contest weekend.
3538 You can specify either prefixes or full callsigns (so you can see how
3539 you did against all your mates). You can also say 'all' which will
3540 then print the worldwide statistics.
3550 show/wcy Show last 10 WCY broadcasts
3554 11.114. show/wcy <n>
3556 show/wcy <n> Show last <n> WCY broadcasts
3559 Display the most recent WCY information that has been received by the
3563 11.115. show/wm7d <callsign>
3565 show/wm7d <callsign> Show callbook details on a US callsigns
3568 This command queries the WM7D callbook server on the internet and
3569 returns any information available for that US callsign. This service
3570 is provided for users of this software by http://www.wm7d.net.
3576 show/wwv Show last 10 WWV broadcasts
3580 11.117. show/wwv <n>
3582 show/wwv <n> Show last <n> WWV broadcasts
3585 Display the most recent WWV information that has been received by the
3590 sysop Regain your privileges if you login remotely
3593 The system automatically reduces your privilege level to that of a
3594 normal user if you login in remotely. This command allows you to
3595 regain your normal privilege level. It uses the normal system: five
3596 numbers are returned that are indexes into the character array that is
3597 your assigned password (see SET/PASSWORD). The indexes start from
3600 You are expected to return a string which contains the characters
3601 required in the correct order. You may intersperse those characters
3602 with others to obscure your reply for any watchers. For example (and
3603 these values are for explanation :-):
3607 password = 012345678901234567890123456789
3616 aa2bbbb0ccc5ddd7xxx3n
3622 They will all match. If there is no password you will still be offered
3623 numbers but nothing will happen when you input a string. Any match is
3626 11.119. talk <call> > <node> [<text>]
3628 talk <call> > <node> [<text>] Send a text message to another station
3632 Send a short message to any other station that is visible on the
3633 cluster system. You can send it to anyone you can see with a
3634 SHOW/CONFIGURATION command, they don't have to be connected locally.
3636 The second form of TALK is used when other cluster nodes are connected
3637 with restricted information. This usually means that they don't send
3638 the user information usually associated with logging on and off the
3641 If you know that G3JNB is likely to be present on GB7TLH, but you can
3642 only see GB7TLH in the SH/C list but with no users, then you would use
3643 the second form of the talk message.
3645 If you want to have a ragchew with someone you can leave the text
3646 message out and the system will go into 'Talk' mode. What this means
3647 is that a short message is sent to the recipient telling them that you
3648 are in a go to the station that you asked for.
3650 All the usual announcements, spots and so on will still come out on
3653 If you want to do something (such as send a spot) you preceed the
3654 normal command with a '/' character, eg:-
3658 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
3663 To leave talk mode type:
3671 If you are in 'Talk' mode, there is an extention to the '/' command
3672 which allows you to send the output to all the people you are talking
3673 to. You do with the '//' command. For example:-
3681 will send the hftable as you have it to all the people you are
3682 currently talking to.
3684 11.120. talk <call> [<text>]
3686 talk <call> [<text>] Send a text message to another station
3690 11.121. type <filearea>/<name>
3692 type <filearea>/<name> Look at the contents of a file in one of the
3696 Type out the contents of a file in a filearea. So, for example, in
3697 filearea 'bulletins' you want to look at file 'arld051' you would
3701 TYPE bulletins/arld051
3705 See also SHOW/FILES to see what fileareas are available and a list of
3708 11.122. unset/announce
3710 unset/announce Stop announce messages coming out on your terminal
3714 11.123. unset/anntalk
3716 unset/anntalk Stop talk like announce messages on your terminal
3719 The announce system on legacy cluster nodes is used as a talk
3720 substitute because the network is so poorly connected. If you:
3728 you will suppress several of these announces, you may miss the odd
3729 useful one as well, but you would probably miss them anyway in the
3730 welter of useless ones.
3738 allows you to see them again. This is the default.
3742 unset/beep Stop beeps for DX and other messages on your terminal
3748 unset/dx Stop DX messages coming out on your terminal
3754 unset/dxcq Stop CQ Zones on the end of DX announcements
3757 Display both the Spotter's and the Spotted's CQ Zone on the end of a
3758 DX announcement (there is just enough room). Some user programs cannot
3759 cope with this. The Spotter's CQ is on the RHS of the time, the
3760 Spotted's CQ is on the LHS.
3762 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
3764 Do a STAT/USER to see which flags you have set if you are confused.
3766 11.127. unset/dxgrid
3768 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
3771 A standard feature which is enabled in version 1.43 and above is that
3772 if the spotter's grid square is known it is output on the end of a DX
3773 announcement (there is just enough room). Some user programs cannot
3774 cope with this. You can use this command to reset (or set) this
3777 Conflicts with: SET/DXCQ, SET/DXITU
3779 Do a STAT/USER to see which flags you have set if you are confused.
3783 unset/dxitu Stop ITU Zones on the end of DX announcements
3786 Display both the Spotter's and the Spotted's ITU Zone on the end of a
3787 DX announcement (there is just enough room). Some user programs cannot
3788 cope with this. The Spotter's ITU is on the RHS of the time, the
3789 Spotted's ITU is on the LHS.
3791 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
3793 Do a STAT/USER to see which flags you have set if you are confused.
3797 unset/echo Stop the cluster echoing your input
3800 If you are connected via a telnet session, different implimentations
3801 of telnet handle echo differently depending on whether you are
3802 connected via port 23 or some other port. You can use this command to
3803 change the setting appropriately.
3805 The setting is stored in your user profile.
3807 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
3811 unset/email Stop personal msgs being forwarded by email
3814 If any personal messages come in for your callsign then you can use
3815 these commands to control whether they are forwarded onto your email
3816 address. To enable the forwarding do something like:-
3820 SET/EMAIL mike.tubby@somewhere.com
3824 You can have more than one email address (each one separated by a
3825 space). Emails are forwarded to all the email addresses you specify.
3827 You can disable forwarding by:-
3835 unset/here Tell the system you are absent from your terminal
3839 11.132. unset/logininfo
3841 unset/logininfo Inform when a station logs out locally
3845 11.133. unset/privilege
3847 unset/privilege Remove any privilege for this session
3850 You can use this command to 'protect' this session from unauthorised
3851 use. If you want to get your normal privilege back you will need to
3852 either logout and login again (if you are on a console) or use the
3855 11.134. unset/prompt
3857 unset/prompt Set your prompt back to default
3860 This command will set your user prompt to exactly the string that you
3861 say. The point of this command to enable a user to interface to
3862 programs that are looking for a specific prompt (or else you just want
3863 a different fixed prompt).
3871 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
3876 unset/talk Stop TALK messages coming out on your terminal
3880 11.136. unset/usstate
3882 unset/usstate Stop US State info on the end of DX announcements
3885 If the spotter's or spotted's US State is known it is output on the
3886 end of a DX announcement (there is just enough room).
3888 A spotter's state will appear on the RHS of the time (like SET/DXGRID)
3889 and the spotted's State will appear on the LHS of the time field. Any
3890 information found will override any locator information from
3892 Some user programs cannot cope with this. You can use this command to
3893 reset (or set) this feature.
3895 Conflicts with: SET/DXCQ, SET/DXITU
3897 Do a STAT/USER to see which flags you have set if you are confused.
3901 unset/wcy Stop WCY messages coming out on your terminal
3907 unset/wwv Stop WWV messages coming out on your terminal
3913 unset/wx Stop WX messages coming out on your terminal
3919 who Show who is physically connected
3922 This is a quick listing that shows which callsigns are connected and
3923 what sort of connection they have
3927 wx <text> Send a weather message to local users
3931 11.142. wx full <text>
3933 wx full <text> Send a weather message to all cluster users