1 The DXSpider User Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
3 April 2003 revision 0.5
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.
53 12. The DXSpider Command Reference
55 12.2 accept/announce [0-9] <pattern>
56 12.3 accept/spots [0-9] <pattern>
57 12.4 accept/wcy [0-9] <pattern>
58 12.5 accept/wwv [0-9] <pattern>
60 12.7 announce full <text>
62 12.9 blank [<string>] [<nn>]
64 12.11 chat <group> <text>
65 12.12 clear/announce [1|all]
66 12.13 clear/route [1|all]
67 12.14 clear/spots [0-9|all]
68 12.15 clear/wcy [1|all]
69 12.16 clear/wwv [1|all]
71 12.18 dbshow <dbname> <key>
73 12.20 directory <from>-<to>
76 12.23 directory from <call>
79 12.26 directory subject <string>
80 12.27 directory to <call>
81 12.28 dx [by <call>] <freq> <call> <remarks>
86 12.33 kill <from msgno>-<to msgno>
87 12.34 kill <msgno> [<msgno..]
88 12.35 kill <msgno> [<msgno> ...]
89 12.36 kill from <regex>
96 12.43 reject/announce [0-9] <pattern>
97 12.44 reject/spots [0-9] <pattern>
98 12.45 reject/wcy [0-9] <pattern>
99 12.46 reject/wwv [0-9] <pattern>
102 12.49 reply b <msgno>
103 12.50 reply noprivate <msgno>
104 12.51 reply rr <msgno>
105 12.52 send <call> [<call> ...]
106 12.53 send copy <msgno> <call>
107 12.54 send noprivate <call>
108 12.55 send private <call>
110 12.57 set/address <your address>
119 12.66 set/email <email> ...
121 12.68 set/homenode <node>
122 12.69 set/language <lang>
123 12.70 set/location <lat & long>
125 12.72 set/name <your name>
126 12.73 set/page <lines per page>
128 12.75 set/prompt <string>
129 12.76 set/qra <locator>
130 12.77 set/qth <your qth>
136 12.83 show/chat [<group>] [<lines>]
137 12.84 show/configuration [<node>]
138 12.85 show/configuration/node
139 12.86 show/contest <year and month>
140 12.87 show/date [<prefix>|<callsign>]
141 12.88 show/db0sdx <callsign>
143 12.90 show/dxcc <prefix>
144 12.91 show/dxqsl <callsign>
145 12.92 show/dxstats [days] [date]
146 12.93 show/files [<filearea> [<string>]]
148 12.95 show/hfstats [days] [date]
149 12.96 show/hftable [days] [date] [prefix ...]
150 12.97 show/moon [ndays] [<prefix>|<callsign>]
151 12.98 show/muf <prefix> [<hours>][long]
152 12.99 show/newconfiguration [<node>]
153 12.100 show/newconfiguration/node
154 12.101 show/prefix <callsign>
155 12.102 show/qra <lat> <long>
156 12.103 show/qra <locator> [<locator>]
157 12.104 show/qrz <callsign>
158 12.105 show/route <callsign> ...
159 12.106 show/satellite <name> [<hours> <interval>]
160 12.107 show/station [<callsign> ..]
161 12.108 show/sun [ndays] [<prefix>|<callsign>]
162 12.109 show/time [<prefix>|<callsign>]
163 12.110 show/usdb [call ..]
164 12.111 show/vhfstats [days] [date]
165 12.112 show/vhftable [days] [date] [prefix ...]
168 12.115 show/wm7d <callsign>
172 12.119 talk <call> > <node> [<text>]
173 12.120 talk <call> [<text>]
174 12.121 type <filearea>/<name>
175 12.122 unset/announce
185 12.132 unset/logininfo
186 12.133 unset/privilege
195 12.142 wx full <text>
198 ______________________________________________________________________
202 1.1. What is a DX Cluster?
204 A DX Cluster is a packet node where DX chasers on any band or mode can
205 post rare or interesting stations that they have worked or heard. Of
206 course other people are doing the same thing too, so you can find new
207 DX as well as telling others about the stations you have worked.
208 Clusters tend to be linked to each other so that the amount of people
209 using them is increased, thereby increasing the amount of posted DX.
210 Other information can be found on clusters such as on-line call books,
211 mail etc. You can talk to other stations connected to the cluster
212 network too, in real time, whether at the node you are logged into or
213 on another node connected to the network. You can also use converse
214 mode, where several stations can talk to each other in the same way.
215 Of course, the DX is still posted to you all the while!
218 1.2. So what is DXSpider?
220 PacketCluster nodes have been around since roughly 1985. The original
221 PacketCluster idea came from Dick Newell, AK1A, and ran under DOS. In
222 about 1992 Dick stopped the development of the PacketCluster software
223 for amateur radio. Many systems are still using this relatively old
226 There are several new compatible cluster programs around now,
227 including DXSpider. DXSpider is a clone of PacketCluster software
228 that runs under several operating systems including Linux and Windows.
229 Linux is fast becoming the choice for amateur radio stations because
230 of it's flexibility, reliability and the lack of the memory
231 limitations of DOS. Linux supports multitasking and is also
232 multiuser. It has support for AX25, ROSE, NetROM and TCPIP built in,
233 making it the ideal choice for amateur radio. It is also totally
236 DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
237 exercise in perl programming. It has developed rapidly and today is a
238 very powerful cluster program. It was designed to be totally
239 compatible with the AK1A program, although several commands have been
240 extended to improve functionality.
242 This manual is designed to help you become familiar with the commands
243 that DXSpider supports and to help you get the best from the program
244 so you can enjoy working that rare DX! As DXSpider is being improved
245 all the time, commands will be added as time goes by, so make sure you
246 have the most upto date version of this manual. The latest version
247 will always be included with the cluster program so if you are unsure,
248 simply ask your sysop. The manual will also be available on the
253 2. Logins and logouts.
255 You might not think that there is a lot of point of including a
256 section on how to log in and out of DXSpider. However, you would be
257 suprised at the difficulties some people have in simply getting in and
260 There are several ways a login might be achieved, dependant on how the
261 sysop has DXSpider configured. It is impossible for me to cover all
262 variations but here are the basic ones.
267 Simplicity itself. The usual CONNECT command will log you straight
268 into the cluster and you will not have to do anything else.
269 Obviously, you will have to connect to the correct callsign. Some
270 nodes use an SSID with their call so you would have to add that.
283 There are several possibilities here, dependant on how the sysop has
284 configured his system. If you are connecting via netrom then you are
285 most probably connecting from another station. Listing the nodes in
286 that station with the NODES command will tell you what callsign or
287 netrom alias to connect to. Then just issue the connect command from
288 there. It is possible that the netrom alias may connect you to a node
289 with an alias for the cluster, such as DXC. Just type this and you
301 With telnet connections, the source callsign is not seen by DXSpider,
302 so you will be asked to login with your callsign. To telnet to
303 DXSpider, you would connect to a specific port. There is no standard
304 at the moment for a cluster telnet port but ask the sysop if you are
315 All the above are possible ways of connecting to a DXSpider cluster.
316 You may have some or all of these available to you. There may be one
317 or two additional ways to connect dependant on the network local to
318 you. However I am sure you get the idea.
323 Logging out can be done by simply issuing the standard BYE command.
325 You could also send a disconnect if you are using AX25, or a CLOSE
326 command if you are connected via telnet. If you do not log out
327 gracefully using one of the above commands, you may find you are
328 unable to get a full connect next time. This may also happen if a
329 netrom connection drops. You may get connected, but nothing else will
330 happen because the program thinks you are still connected and will not
331 let you connect twice under the same call. However you could
332 reconnect by adding a number to the end of your call, for example
333 G0YLM-2. This can be done by either altering your MYCALL setting in
334 the TNC or by altering your program configuration.
337 3. Setting your personal details.
339 Once logged in to the cluster, you should set your details so that
340 anybody who wishes to contact you can find out who and where you are.
341 There are four items to set, your name, qth, location and home node.
342 Setting these details also allows the use of the SHOW/HEADING and
343 SHOW/SUN commands from within the cluster. Unless you set your QTH
344 and location, these commands cannot function. Once you have set your
345 name, DXSpider will greet you with it next time you login. Your QTH
346 setting is where you live and it is a good idea to add your locator to
347 this as the location setting is converted to latitude and longitude
348 once inputted. You can actually set your location in
349 latitude/longitude or as a locator. Setting your home node will tell
350 the program where you wish mail to be sent to you.
357 set/qth Morecambe, Lancashire IO84NB
358 set/location 48 34 n 12 12 e
364 4. Getting and posting DX.
366 When all is said and done, this is the main function of a DX cluster.
367 In its simplest form you can just connect to the node and you will
368 start to receive DX spots almost immediately! You can check on recent
369 postings in either a general manner or on a particular band or mode.
370 You can even check DX by callsign or a fragment of a callsign. Of
371 course, once you get the hang of things, it is expected that you start
372 posting some yourself! After all, there would be no clusters if
373 people did not post DX and you get the added thrill of the hunt!
378 As we have already said, it is possible just to connect to the cluster
379 and you will receive spots automatically. However, you may wish to
380 check on spots just posted. Maybe you wish to see if a particular
381 band is open or if a certain callsign is active, perhaps a DXpedition.
382 The command to do this is SHOW/DX. Without any other arguments, this
383 command will output the last 10 spots posted. It is possible to look
384 at more than this, for example the last 20 or 50 spots, by adding the
385 number to the command. You can make it even more specific by adding a
386 band in either wavelength or frequency, and/or any additional
387 information such as QSL details.
399 will show the last 10, 5 and 20 spots received by the cluster
412 will show the last 5, 10 or 20 spots on 20 metres only.
414 It is also possible to check for certain callsigns, or fragments of
415 callsigns in the same way.
426 would show the last 5 or 10 dx spots containing the callsign g0vgs.
429 You can check for DX by offset and also by specifying a comment to
442 would show the spots that arrived between 30 and 40 spots ago and any
443 spots with the word iota in the comment field. The case of the
444 comment is not important.
446 Checking DX posted on a certain day is possible too. All you have to
447 do here is to specify how many days ago it was like this ...
457 It is of course possible to specify multiple arguments.
461 show/dx 20 prefix 9a on vhf day 30
465 This would show the last 20 spots posted by or about calls with the
466 prefix 9a on vhf 30 days ago.
468 As you can see the SHOW/DX command is very flexible, so if you are not
469 sure whether something will work or not, try it and see! More
470 information can be found in the Command Set section.
475 To post DX you use the DX command. The syntax is shown below.
481 dx (frequency) (callsign) (remarks)
485 Where frequency is in kilohertz and the callsign is the callsign of
486 the station you have worked or heard, (ie not your own callsign!).
487 The remarks section allows you to add information like the operators
488 name or perhaps a location. Actually DXSpider will allow the
489 frequency and callsign fields to be entered in any order.
495 dx 14004 pa3ezl OP Aurelio 599
499 In fact, all the following will give the same result...
503 dx 14004 pa3ezl OP Aurelio 599
504 dx pa3ezl 14004 OP Aurelio 599
505 dx pa3ezl 14.004 OP Aurelio 599
509 This posting, or callout as it is known, will be forwarded to all
510 other connected stations both at the cluster you are connected to and
511 other active clusters in the network. The callout will also be sent
512 to you as proof of receipt.
515 5. Headings and propagation
517 There are three commands in DXSpider to help you get the best DX
518 possible. These are SHOW/SUN, SHOW/MOON and SHOW/HEADING. These
519 commands will only work for you if you have entered your personal
520 details. They use your entered location as a reference, so if you
521 have not entered it or have entered it incorrectly they will not
522 return the correct information.
525 The SHOW/SUN command can be used in three different ways. It can be
526 used to show sunrise and sunset times for your own station, a
527 particular callsign or a prefix.
537 The output from this would look something like this ..
542 Location Rise Set Azim Elev
543 G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
551 would look like this ...
556 Location Rise Set Azim Elev
557 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
561 You can also specify multiple arguments like this ...
565 sh/sun gw4veq 5b4ab zs
569 and then the output would look like this ...
573 sh/sun gw4veq 5b4ab zs
574 Location Rise Set Azim Elev
575 GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9
576 5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
577 ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
578 ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
579 ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
584 The SHOW/MOON command works in the same way as the SHOW/SUN command.
585 This program however, calculates the rise and set times of the moon
586 for a prefix or callsign, together with the current azimuth and
587 elevation of the sun at these locations.
597 The output from this command would look like this ..
602 Location Rise Set Azim Elev RGain dB
603 EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
607 You can see that the output is similar to the SHOW/SUN command, with
608 slightly different fields.
613 The SHOW/HEADING command works in the same way as the SHOW/SUN and
614 SHOW/MOON commands but outputs beam headings for a specified callsign
615 or prefix. Reciprocal beam headings are also calculated.
625 The output from this command would look like this ..
630 ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
631 ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
632 ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
633 ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
639 6.1. Making announcements.
641 Occasionally, you may wish to post something that does not fall into
642 the normal parameters for a DX callout. You may wish to tell
643 everybody connected that 10 FM is open for example, or ask if anyone
644 knows the QSL manager for a certain callsign etc. You can do this
645 using the ANNOUNCE command.
651 announce 10 FM is open in IO84NB to europe.
655 That would let everyone know locally that this was the case, however
656 it would not be forwarded to other nodes connected. To send
657 announcements to other connected nodes as well, you would use the FULL
664 announce full Anyone seen EA7WA today?
668 Be cautious in your use of announce full. There are many other tools
669 available to get the information you require and the judicious use of
670 this command is frowned upon as it creates a great deal of traffic
674 6.2. Listing announcements.
676 You can list previous announcements in the standard format with the
677 SHOW command. As before you can list just the last 5 or as many as
685 show/announcements 10
691 You can check which nodes are connected in the network, who is logged
692 on locally, who is logged on at all the nodes or even just one node in
693 particular. This is handy if you wish to see whether a friend is
694 connected at the node they use. To see who is connected to the nodes,
695 the SHOW/CONFIGURATION command is used.
702 show/configuration/nodes
703 show/configuration (node_call)
704 show/configuration (prefix)
708 The first of our three examples would output something like this,
717 GB7BIG (GD0TEP) GD3UMW
718 GB7BPQ (G0INA) G0RCI G3AKU G3OCA
720 GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
721 G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
724 GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
725 G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
727 (GB7DXG) GU6EFB GU7DHI
728 GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
730 GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
735 You will notice that EI5TCR is showing only that it has 7 users and
736 not giving the actual callsigns. This means that this node is on a
737 limited protocol of some kind, probably because of a contest situation
738 where slow radio links can block up and fail if too much information
739 is sent between nodes.
741 The second example would just show the nodes connected in the network,
748 GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
749 GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
750 GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
751 GB7YDX KL7G N2TLY (ON0DXK)
752 GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
759 If we insert the node_call pi4tue-8 into the third example, then this
765 PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
766 F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
767 ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
768 PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
773 As you can see, only the users of the requested node are shown.
775 You can also use a prefix to show only a group of nodes. For example
776 you may only wish to see who is connected to the nodes in the UK. To
777 do this simply use a prefix like this ...
780 show/configuration gb7
784 To show the locally connected users, the SHOW/USERS command is used
794 The output of this command would look like this,
798 Callsigns connected to GB7MBC
799 G0JHC G0NEI G0VGS G0VGS-2 G0YLM
806 You can send a single comment or start a dedicated talk session to
807 another user by using the TALK command.
810 Talk mode is used to send a one line comment or greeting to a specific
811 user connected either at your node or another in the network. You can
812 also enter into a dedicated talk session with another user. Talks
813 will be automatically forwarded to other nodes if the station you are
814 talking to is not connected locally. You can find out who is
815 connected by using the SHOW/CONFIGURATION command, (described
822 talk g0rdi Having a good day Iain?
825 This example would send the line "Having a good day Iain?" to the user
826 g0rdi but would leave you in normal mode.
831 Entering Talkmode, /EX to end, /<cmd> to run a command
836 As you can see, you can still run commands whilst in talk mode.
837 Simply prefix the command with a / like /sh/dx and you will get the
838 expected output. If the user is connected to another node, you may
839 have to use a slightly extended version of the TALK command.
847 To exit talk mode, you issue the command /ex.
849 Whilst in talk mode you will still receive DX spots. This means that
850 you can chat to a friend whilst working DX.
855 You can send and receive both personal mail and bulletins with
856 DXSpider quite easily.
859 9.1. The "directory" command.
861 To list mail you would use the DIRECTORY command. On its own, this
862 command will output the last ten messages received by the node, either
863 to or from yourself or bulletins such as "DX" and "ALL". As with
864 other commands you can display more by specifying a number with the
865 command. You should be aware that Spider will accept these commands
866 by separating with either a slash or a space, so dir new and dir/new
867 work in the same way.
879 Of course most of the time you will only want to list new mail sent to
880 you personally since your last login. However you might also like to
881 check for general mail received by the node. In fact if there is new
882 mail for you, the cluster will tell you when you login. You will also
883 be informed if new mail arrives for you during the time you are logged
884 in. Mail is not only sent to callsigns though. Mail can also be sent
885 to subjects like "all" or "local" or "dx" etc. You can treat these
886 bulletins in the same way as personal mail with the directory command.
896 directory/from <call>
900 The last option will only show mail from a callsign if it was sent to
901 you personally or was sent as a bulletin. There are some additional
902 commands and these can be found in the DXSpider Command Reference
908 The output of the DIRECTORY command could be something like this.
913 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
914 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
915 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
916 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
917 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
918 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
919 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
920 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
921 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
922 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
923 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
927 The first column is the actual message number. If the message is a
928 personal one to you, you will see a letter 'p' after this number. If
929 the message has been read, there will be a '-' between the message
930 number and the 'p'. This only works for personal messages. The next
931 column shows the file size of the message. The third column shows the
932 address the message was sent to and the next column shows who sent it.
933 The rest is fairly self-explanatory.
935 Reading a message is as simple as typing read, followed by the message
936 number that you wish to read.
946 will read message number 25. However the mail will be displayed in
947 it's entirety unless you specify a page length. You can set your page
948 length to any number you like and when the message reaches that number
949 of lines you will get a prompt giving you options.
960 Sending mail is done in the time honoured way. First you specify a
961 recipient for the message, then you will be prompted for a subject.
962 Once you have done this you will be asked to type your message.
963 Please remember that there is no automatic word wrap, so unless you
964 are using a client that wraps lines automatically, remember to hit
965 return at the end of each line.
972 Enter Subject (30 characters):
974 Enter Message /EX to send or /ABORT to exit
976 Just a quick note to say that I can make Thursday after all. The
977 appointment I had has cancelled so we are go!
983 At this point you can either hit return and enter /ex to send the
984 message or use /abort at any time to abort it. You can now display
985 the message in the normal way. There are several send options and
986 these are listed in the Command Set section. These include sending
987 mail to several recipients and asking for a return receipt.
991 9.4. Replying to mail.
993 If mail is addressed to you or to a bulletin address, you can use the
994 REPLY command to reply to it. Using this command, the subject will be
995 automatically set for you as "Re: subject", whatever the subject was.
1007 To delete a message, you use the delete command. You can only delete
1008 messages sent to or received by yourself. Bulletins are dealt with
1009 automatically or by the sysop.
1010 10. Filtering (From version 1.45)
1012 10.1. General filter rules
1014 Upto v1.44 it was not possible for the user to set their own filters.
1015 From v1.45 though that has all changed. It is now possible to set
1016 filters for just about anything you wish. If you have just updated
1017 from an older version of DXSpider you will need to update your new
1018 filters. You do not need to do anything with your old filters, they
1019 will be renamed as you update.
1022 There are 3 basic commands involved in setting and manipulating
1023 filters. These are accept, reject and clear. First we will look
1024 generally at filtering. There are a number of things you can filter in
1025 the DXSpider system. They all use the same general mechanism.
1028 In general terms you can create a 'reject' or an 'accept' filter which
1029 can have up to 10 lines in it. You do this using, for example ...
1038 where ..... are the specific commands for that type of filter. There
1039 are filters for spots, wwv, announce, wcy and (for sysops) connects.
1040 See each different accept or reject command reference for more
1043 There is also a command to clear out one or more lines in a filter.
1053 There is clear/xxxx command for each type of filter.
1056 and you can check that your filters have worked by the command ...
1064 For now we are going to use spots for the examples, but you can apply
1065 the same principles to all types of filter.
1069 10.2. Types of filter
1071 There are two main types of filter, accept or reject. You can use
1072 either to achieve the result you want dependent on your own preference
1073 and which is more simple to do. It is pointless writing 8 lines of
1074 reject filters when 1 accept filter would do the same thing! Each
1075 filter has 10 lines (of any length) which are tried in order. If a
1076 line matches then the action you have specified is taken (ie reject
1077 means ignore it and accept means take it)
1080 If you specify reject filters, then any lines that arrive that match
1081 the filter will be dumped but all else will be accepted. If you use
1082 an accept filter, then ONLY the lines in the filter will be accepted
1083 and all else will be dumped. For example if you have a single line
1088 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1092 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
1095 If you set a reject filter like this ...
1099 reject/spots on hf/cw
1103 Then you will get everything EXCEPT HF CW spots. You could make this
1104 single filter even more flexible. For example, if you are interested
1105 in IOTA and will work it even on CW even though normally you are not
1106 interested in CW, then you could say ...
1110 reject/spots on hf/cw and not info iota
1114 But in that case you might only be interested in iota and say:-
1118 accept/spots not on hf/cw or info iota
1122 which achieves exactly the same thing. You should choose one or the
1123 other until you are comfortable with the way it works. You can mix
1124 them if you wish (actually you can have an accept AND a reject on the
1125 same line) but don't attempt this until you are sure you know what you
1129 You can arrange your filter lines into logical units, either for your
1130 own understanding or simply convenience. Here is an example ...
1131 reject/spots 1 on hf/cw
1132 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
1136 What this does is to ignore all HF CW spots and also rejects any spots
1137 on VHF which don't either originate or spot someone in Europe.
1140 This is an example where you would use a line number (1 and 2 in this
1141 case), if you leave the digit out, the system assumes '1'. Digits
1142 '0'-'9' are available. This make it easier to see just what filters
1143 you have set. It also makes it more simple to remove individual
1144 filters, during a contest for example.
1147 You will notice in the above example that the second line has
1148 brackets. Look at the line logically. You can see there are 2
1149 separate sections to it. We are saying reject spots that are VHF or
1150 above APART from those in zones 14, 15 and 16 (either spotted there or
1151 originated there). If you did not have the brackets to separate the 2
1152 sections, then Spider would read it logically from the front and see a
1153 different expression entirely ...
1157 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
1161 The simple way to remember this is, if you use OR - use brackets.
1162 Whilst we are here CASE is not important. 'And BY_Zone' is just the
1163 same as 'and by_zone'.
1165 As mentioned earlier, setting several filters can be more flexible
1166 than simply setting one complex one. Doing it in this way means that
1167 if you want to alter your filter you can just redefine or remove one
1168 or more lines of it or one line. For example ...
1172 reject/spots 1 on hf/ssb
1176 would redefine our earlier example, or
1184 To remove all the filter lines in the spot filter ...
1192 10.3. Filter options
1194 You can filter in several different ways. The options are listed in
1195 the various helpfiles for accept, reject and filter.
1198 10.4. Advanced filtering
1200 Once you are happy with the results you get, you may like to
1204 The previous example that filters hf/cw spots and accepts vhf/uhf
1205 spots from EU can be written with a mixed filter, for example ...
1211 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
1215 Note that the first filter has not been specified with a number. This
1216 will automatically be assumed to be number 1. In this case, we have
1217 said reject all HF spots in the CW section of the bands but accept all
1218 others at HF. Also accept anything in VHF and above spotted in or by
1219 operators in the zones 14, 15 and 16. Each filter slot actually has a
1220 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
1224 It was mentioned earlier that after a reject test that doesn't match,
1225 the default for following tests is 'accept', the reverse is true for
1226 'accept'. In the example what happens is that the reject is executed
1227 first, any non hf/cw spot is passed to the accept line, which lets
1228 through everything else on HF. The next filter line lets through just
1229 VHF/UHF spots from EU.
1232 10.5. A Filtering Tutorial
1234 There is now an excellent primer/tutorial on filtering written by Jim
1235 Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly
1236 suggest you read. You can read it here The DXSpider User Filtering
1240 11. Hints, tips and common questions.
1242 Q.These commands seem very long! Can I shorten them?
1244 A.Of course you can and the usual abbreviations work. If you are
1247 Q.I am not sure if this command is correct. Can I cause any harm if I
1250 A.Do not be afraid to try a command to see if it will work, at the
1251 worst you will get an error message. If you require any help on a
1252 command, just type help followed by the command you want help on.
1253 Look at the "DXSpider Command Reference" section to see what help can
1257 Q.How should I use the announce command?
1259 A.With respect. Use the command by all means, but please only use the
1260 "full" extension if absolutely necessary. It can create a LOT of
1261 messages passing between clusters.
1263 Q.I like to be working in the shack while logged into the cluster but
1264 I can't be looking at the screen all the time. How can I be alerted
1265 when anything happens?
1267 A.Use the SET/BEEP command. You can find information on this in the
1268 "DXSpider Command Reference" section.
1270 Q.I got disconnected from the cluster and now I can't log back in
1271 again. What is wrong?
1273 A.Probably the cluster thinks you are still logged on and will not let
1274 you reconnect using the same call to prevent loops. Try logging on
1275 again adding an ssid to your callsign as DXSpider treats G0YLM and
1276 G0YLM-1 as different users.
1278 Q.How do I know if I have got the latest version of this user manual?
1280 A.The latest and greatest will always be on the Website. It will also
1281 be included with every release of DXSpider. As always, if unsure, ask
1282 your sysop what version number is the latest.
1285 12. The DXSpider Command Reference
1289 accept Set a filter to accept something
1292 Create a filter to accept something
1294 There are 2 types of filter, accept and reject. See HELP FILTERING
1297 12.2. accept/announce [0-9] <pattern>
1299 accept/announce [0-9] <pattern> Set an 'accept' filter line for
1303 Create an 'accept this announce' line for a filter.
1305 An accept filter line means that if the announce matches this filter
1306 it is passed onto the user. See HELP FILTERING for more info. Please
1307 read this to understand how filters work - it will save a lot of grief
1310 You can use any of the following things in this line:-
1314 info <string> eg: iota or qsl
1315 by <prefixes> eg: G,M,2
1317 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1318 origin_itu <prefixes or numbers> or: G,GM,GW
1319 origin_zone <prefixes or numbers>
1320 origin_state <states> eg: VA,NH,RI,NH
1321 by_dxcc <prefixes or numbers>
1322 by_itu <prefixes or numbers>
1323 by_zone <prefixes or numbers>
1326 wx 1 filter WX announces
1327 dest <prefixes> eg: 6MUK,WDX (distros)
1336 acc/ann 2 by_zone 14,15,16
1337 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1352 acc/ann by_state va,nh,ri,nh
1356 You can use the tag 'all' to accept everything eg:
1364 but this probably for advanced users...
1366 12.3. accept/spots [0-9] <pattern>
1368 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
1371 Create an 'accept this spot' line for a filter.
1373 An accept filter line means that if the spot matches this filter it is
1374 passed onto the user. See HELP FILTERING for more info. Please read
1375 this to understand how filters work - it will save a lot of grief
1378 You can use any of the following things in this line:-
1382 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1383 on <range> same as 'freq'
1384 call <prefixes> eg: G,PA,HB9
1385 info <string> eg: iota or qsl
1387 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1388 call_itu <prefixes or numbers> or: G,GM,GW
1389 call_zone <prefixes or numbers>
1390 call_state <states> eg: VA,NH,RI,ME
1391 by_dxcc <prefixes or numbers>
1392 by_itu <prefixes or numbers>
1393 by_zone <prefixes or numbers>
1394 by_state <states> eg: VA,NH,RI,ME
1400 For frequencies, you can use any of the band names defined in
1401 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1402 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1403 this is more efficient than saying simply: freq HF (but don't get too
1411 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1415 You can use the tag 'all' to accept everything, eg:
1427 acc/spots by_state VA,NH,RI,MA,ME
1431 but this probably for advanced users...
1435 12.4. accept/wcy [0-9] <pattern>
1437 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
1440 It is unlikely that you will want to do this, but if you do then you
1441 can filter on the following fields:-
1445 by <prefixes> eg: G,M,2
1447 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1448 origin_itu <prefixes or numbers> or: G,GM,GW
1449 origin_zone <prefixes or numbers>
1450 by_dxcc <prefixes or numbers>
1451 by_itu <prefixes or numbers>
1452 by_zone <prefixes or numbers>
1457 There are no examples because WCY Broadcasts only come from one place
1458 and you either want them or not (see UNSET/WCY if you don't want
1461 This command is really provided for future use.
1463 See HELP FILTER for information.
1465 12.5. accept/wwv [0-9] <pattern>
1467 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
1470 It is unlikely that you will want to do this, but if you do then you
1471 can filter on the following fields:-
1475 by <prefixes> eg: G,M,2
1477 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1478 origin_itu <prefixes or numbers> or: G,GM,GW
1479 origin_zone <prefixes or numbers>
1480 by_dxcc <prefixes or numbers>
1481 by_itu <prefixes or numbers>
1482 by_zone <prefixes or numbers>
1491 accept/wwv by_zone 4
1495 is probably the only useful thing to do (which will only show WWV
1496 broadcasts by stations in the US).
1498 See HELP FILTER for information.
1500 12.6. announce <text>
1502 announce <text> Send an announcement to LOCAL users only
1505 <text> is the text of the announcement you wish to broadcast
1507 12.7. announce full <text>
1509 announce full <text> Send an announcement cluster wide
1512 This will send your announcement cluster wide
1514 12.8. apropos <string>
1516 apropos <string> Search help database for <string>
1519 Search the help database for <string> (it isn't case sensitive), and
1520 print the names of all the commands that may be relevant.
1522 12.9. blank [<string>] [<nn>]
1524 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
1527 In its basic form this command prints one or more blank lines. However
1528 if you pass it a string it will replicate the string for the width of
1529 the screen (default 80) and then print that one or more times, so:
1537 prints two blank lines
1545 prints a row of - characters once.
1553 prints 'abcabcabcabcabcabc....'
1555 This is really only of any use in a script file and you can print a
1562 bye Exit from the cluster
1565 This will disconnect you from the cluster
1567 12.11. chat <group> <text>
1569 chat <group> <text> Chat or Conference to a group
1572 It is now possible to JOIN a group and have network wide conferencing
1573 to that group. DXSpider does not (and probably will not) implement the
1574 AK1A conference mode as this seems very limiting, is hardly used and
1575 doesn't seem to work too well anyway.
1577 This system uses the existing ANN system and is compatible with both
1578 other DXSpider nodes and AK1A clusters (they use ANN/<group>).
1580 You can be a member of as many "groups" as you want. To join a group
1585 JOIN FOC (where FOC is the group name)
1589 To leave a group type:-
1597 You can see which groups you are in by typing:-
1605 and you can see whether your mate is in the group, if he connects to
1606 the same node as you, by typing:-
1614 To send a message to a group type:-
1618 CHAT FOC hello everyone
1626 CH #9000 hello I am back
1630 See also JOIN, LEAVE, SHOW/CHAT
1632 12.12. clear/announce [1|all]
1634 clear/announce [1|all] Clear a announce filter line
1637 This command allows you to clear (remove) a line in a annouce filter
1638 or to remove the whole filter.
1640 see CLEAR/SPOTS for a more detailed explanation.
1642 12.13. clear/route [1|all]
1644 clear/route [1|all] Clear a route filter line
1647 This command allows you to clear (remove) a line in a route filter or
1648 to remove the whole filter.
1650 see CLEAR/SPOTS for a more detailed explanation.
1652 12.14. clear/spots [0-9|all]
1654 clear/spots [0-9|all] Clear a spot filter line
1657 This command allows you to clear (remove) a line in a spot filter or
1658 to remove the whole filter.
1660 If you have a filter:-
1665 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1677 you will be left with:-
1681 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1693 the filter will be completely removed.
1695 12.15. clear/wcy [1|all]
1697 clear/wcy [1|all] Clear a WCY filter line
1700 This command allows you to clear (remove) a line in a WCY filter or to
1701 remove the whole filter.
1703 see CLEAR/SPOTS for a more detailed explanation.
1705 12.16. clear/wwv [1|all]
1707 clear/wwv [1|all] Clear a WWV filter line
1710 This command allows you to clear (remove) a line in a WWV filter or to
1711 remove the whole filter.
1713 see CLEAR/SPOTS for a more detailed explanation.
1717 dbavail Show a list of all the Databases in the system
1720 Title says it all really, this command lists all the databases defined
1721 in the system. It is also aliased to SHOW/COMMAND.
1723 12.18. dbshow <dbname> <key>
1725 dbshow <dbname> <key> Display an entry, if it exists, in a database
1728 This is the generic user interface to the database to the database
1729 system. It is expected that the sysop will add an entry to the local
1730 Aliases file so that users can use the more familiar AK1A style of
1739 but if he hasn't and the database really does exist (use DBAVAIL or
1740 SHOW/COMMAND to find out) you can do the same thing with:
1750 directory List messages
1754 12.20. directory <from>-<to>
1756 directory <from>-<to> List messages <from> message <to> message
1759 List the messages in the messages directory.
1761 If there is a 'p' one space after the message number then it is a
1762 personal message. If there is a '-' between the message number and the
1764 You can use shell escape characters such as '*' and '?' in the <call>
1767 You can combine some of the various directory commands together eg:-
1778 DIR SUBJECT IOTA 200-250
1782 You can abbreviate all the commands to one letter and use ak1a
1792 12.21. directory <nn>
1794 directory <nn> List last <nn> messages
1798 12.22. directory all
1800 directory all List all messages
1804 12.23. directory from <call>
1806 directory from <call> List all messages from <call>
1810 12.24. directory new
1812 directory new List all new messages
1816 12.25. directory own
1818 directory own List your own messages
1822 12.26. directory subject <string>
1824 directory subject <string> List all messages with <string> in subject
1828 12.27. directory to <call>
1830 directory to <call> List all messages to <call>
1834 12.28. dx [by <call>] <freq> <call> <remarks>
1836 dx [by <call>] <freq> <call> <remarks> Send a DX spot
1839 This is how you send a DX Spot to other users. You can, in fact, now
1840 enter the <freq> and the <call> either way round.
1850 will all give the same result. You can add some remarks to the end of
1851 the command and they will be added to the spot.
1855 DX FR0G 144600 this is a test
1859 You can credit someone else by saying:-
1863 DX by G1TLH FR0G 144.600 he isn't on the cluster
1867 The <freq> is compared against the available bands set up in the
1868 cluster. See SHOW/BANDS for more information.
1874 echo <line> Echo the line to the output
1877 This command is useful in scripts and so forth for printing the line
1878 that you give to the command to the output. You can use this in
1879 user_default scripts and the SAVE command for titling and so forth
1881 The script will interpret certain standard "escape" sequences as
1886 \t - becomes a TAB character (0x09 in ascii)
1887 \a - becomes a BEEP character (0x07 in ascii)
1888 \n - prints a new line
1892 So the following example:-
1896 echo GB7DJK is a dxcluster
1904 GB7DJK is a dxcluster
1908 on the output. You don't need a \n on the end of the line you want to
1911 A more complex example:-
1915 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
1935 filtering... Filtering things in DXSpider
1938 There are a number of things you can filter in the DXSpider system.
1939 They all use the same general mechanism.
1941 In general terms you can create a 'reject' or an 'accept' filter which
1942 can have up to 10 lines in it. You do this using, for example:-
1951 where ..... are the specific commands for that type of filter. There
1952 are filters for spots, wwv, announce, wcy and (for sysops) connects.
1953 See each different accept or reject command reference for more
1956 There is also a command to clear out one or more lines in a filter and
1957 one to show you what you have set. They are:-
1974 There is clear/xxxx command for each type of filter.
1976 For now we are going to use spots for the examples, but you can apply
1977 the principles to all types of filter.
1979 There are two main types of filter 'accept' or 'reject'; which you use
1980 depends entirely on how you look at the world and what is least
1981 writing to achieve what you want. Each filter has 10 lines (of any
1982 length) which are tried in order. If a line matches then the action
1983 you have specified is taken (ie reject means ignore it and accept
1986 The important thing to remember is that if you specify a 'reject'
1987 filter (all the lines in it say 'reject/spots' (for instance)) then if
1988 a spot comes in that doesn't match any of the lines then you will get
1989 it BUT if you specify an 'accept' filter then any spots that don't
1990 match are dumped. For example if I have a one line accept filter:-
1994 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1996 then automatically you will ONLY get VHF spots from or to CQ zones 14
1997 15 and 16. If you set a reject filter like:
2001 reject/spots on hf/cw
2005 Then you will get everything EXCEPT HF CW spots, If you am interested
2006 in IOTA and will work it even on CW then you could say:-
2010 reject/spots on hf/cw and not info iota
2014 But in that case you might only be interested in iota and say:-
2018 accept/spots not on hf/cw or info iota
2022 which is exactly the same. You should choose one or the other until
2023 you are confortable with the way it works. Yes, you can mix them
2024 (actually you can have an accept AND a reject on the same line) but
2025 don't try this at home until you can analyse the results that you get
2026 without ringing up the sysop for help.
2028 Another useful addition now is filtering by US state
2032 accept/spots by_state VA,NH,RI,ME
2036 You can arrange your filter lines into logical units, either for your
2037 own understanding or simply convenience. I have one set frequently:-
2041 reject/spots 1 on hf/cw
2042 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
2046 What this does is to ignore all HF CW spots (being a class B I can't
2047 read any CW and couldn't possibly be interested in HF :-) and also
2048 rejects any spots on VHF which don't either originate or spot someone
2051 This is an exmaple where you would use the line number (1 and 2 in
2052 this case), if you leave the digit out, the system assumes '1'. Digits
2054 You can leave the word 'and' out if you want, it is implied. You can
2055 use any number of brackets to make the 'expression' as you want it.
2056 There are things called precedence rules working here which mean that
2057 you will NEED brackets in a situation like line 2 because, without it,
2062 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
2066 annoying, but that is the way it is. If you use OR - use brackets.
2067 Whilst we are here CASE is not important. 'And BY_Zone' is just 'and
2070 If you want to alter your filter you can just redefine one or more
2071 lines of it or clear out one line. For example:-
2075 reject/spots 1 on hf/ssb
2087 To remove the filter in its entirty:-
2095 There are similar CLEAR commands for the other filters:-
2107 Once you are happy with the results you get, you may like to
2110 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
2111 can be written with a mixed filter, eg:
2117 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
2121 each filter slot actually has a 'reject' slot and an 'accept' slot.
2122 The reject slot is executed BEFORE the accept slot.
2124 It was mentioned earlier that after a reject test that doesn't match,
2125 the default for following tests is 'accept', the reverse is true for
2126 first, any non hf/cw spot is passed to the accept line, which lets
2127 thru everything else on HF.
2129 The next filter line lets through just VHF/UHF spots from EU.
2133 help The HELP Command
2136 HELP is available for a number of commands. The syntax is:-
2144 Where <cmd> is the name of the command you want help on.
2146 All commands can be abbreviated, so SHOW/DX can be abbreviated to
2147 SH/DX, ANNOUNCE can be shortened to AN and so on.
2149 Look at the APROPOS <string> command which will search the help
2150 database for the <string> you specify and give you a list of likely
2151 commands to look at with HELP.
2155 join <group> Join a chat or conference group
2158 JOIN allows you to join a network wide conference group. To join a
2159 group (called FOC in this case) type:-
2167 See also CHAT, LEAVE, SHOW/CHAT
2169 12.33. kill <from msgno>-<to msgno>
2171 kill <from msgno>-<to msgno> Delete a range of messages
2175 12.34. kill <msgno> [<msgno..]
2177 kill <msgno> [<msgno..] Delete a message from the local system
2181 12.35. kill <msgno> [<msgno> ...]
2183 kill <msgno> [<msgno> ...] Remove or erase a message from the system
2186 You can get rid of any message to or originating from your callsign
2187 using this command. You can remove more than one message at a time.
2189 12.36. kill from <regex>
2191 kill from <regex> Delete messages FROM a callsign or pattern
2195 12.37. kill to <regex>
2197 kill to <regex> Delete messages TO a callsign or pattern
2201 12.38. leave <group>
2203 leave <group> Leave a chat or conference group
2206 LEAVE allows you to leave a network wide conference group. To leave a
2207 group (called FOC in this case) type:-
2215 See also CHAT, JOIN, SHOW/CHAT
2219 links Show which nodes is physically connected
2222 This is a quick listing that shows which links are connected and some
2223 information about them. See WHO for a list of all connections.
2227 read Read the next unread personal message addressed to you
2233 read <msgno> Read the specified message
2236 You can read any messages that are sent as 'non-personal' and also any
2237 message either sent by or sent to your callsign.
2242 reject Set a filter to reject something
2245 Create a filter to reject something
2247 There are 2 types of filter, accept and reject. See HELP FILTERING
2250 12.43. reject/announce [0-9] <pattern>
2252 reject/announce [0-9] <pattern> Set a 'reject' filter line for
2256 Create an 'reject this announce' line for a filter.
2258 A reject filter line means that if the announce matches this filter it
2259 is passed onto the user. See HELP FILTERING for more info. Please read
2260 this to understand how filters work - it will save a lot of grief
2263 You can use any of the following things in this line:-
2267 info <string> eg: iota or qsl
2268 by <prefixes> eg: G,M,2
2270 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2271 origin_itu <prefixes or numbers> or: G,GM,GW
2272 origin_zone <prefixes or numbers>
2273 origin_state <states> eg: VA,NH,RI,ME
2274 by_dxcc <prefixes or numbers>
2275 by_itu <prefixes or numbers>
2276 by_zone <prefixes or numbers>
2277 by_state <states> eg: VA,NH,RI,ME
2279 wx 1 filter WX announces
2280 dest <prefixes> eg: 6MUK,WDX (distros)
2288 rej/ann by_zone 14,15,16 and not by G,M,2
2292 You can use the tag 'all' to reject everything eg:
2300 but this probably for advanced users...
2303 12.44. reject/spots [0-9] <pattern>
2305 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
2308 Create a 'reject this spot' line for a filter.
2310 A reject filter line means that if the spot matches this filter it is
2311 dumped (not passed on). See HELP FILTERING for more info. Please read
2312 this to understand how filters work - it will save a lot of grief
2315 You can use any of the following things in this line:-
2319 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
2320 on <range> same as 'freq'
2321 call <prefixes> eg: G,PA,HB9
2322 info <string> eg: iota or qsl
2324 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2325 call_itu <prefixes or numbers> or: G,GM,GW
2326 call_zone <prefixes or numbers>
2327 call_state <states> eg: VA,NH,RI,ME
2328 by_dxcc <prefixes or numbers>
2329 by_itu <prefixes or numbers>
2330 by_zone <prefixes or numbers>
2331 by_state <states> eg: VA,NH,RI,ME
2337 For frequencies, you can use any of the band names defined in
2338 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
2339 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
2340 this is more efficient than saying simply: on HF (but don't get too
2348 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
2352 You can use the tag 'all' to reject everything eg:
2360 but this probably for advanced users...
2364 12.45. reject/wcy [0-9] <pattern>
2366 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
2369 It is unlikely that you will want to do this, but if you do then you
2370 can filter on the following fields:-
2374 by <prefixes> eg: G,M,2
2376 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2377 origin_itu <prefixes or numbers> or: G,GM,GW
2378 origin_zone <prefixes or numbers>
2379 by_dxcc <prefixes or numbers>
2380 by_itu <prefixes or numbers>
2381 by_zone <prefixes or numbers>
2386 There are no examples because WCY Broadcasts only come from one place
2387 and you either want them or not (see UNSET/WCY if you don't want
2390 This command is really provided for future use.
2392 See HELP FILTER for information.
2394 12.46. reject/wwv [0-9] <pattern>
2396 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
2399 It is unlikely that you will want to do this, but if you do then you
2400 can filter on the following fields:-
2404 by <prefixes> eg: G,M,2
2406 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2407 origin_itu <prefixes or numbers> or: G,GM,GW
2408 origin_zone <prefixes or numbers>
2409 by_dxcc <prefixes or numbers>
2410 by_itu <prefixes or numbers>
2411 by_zone <prefixes or numbers>
2420 reject/wwv by_zone 14,15,16
2424 is probably the only useful thing to do (which will only show WWV
2425 broadcasts by stations in the US).
2427 See HELP FILTER for information.
2431 reply Reply (privately) to the last message that you have read
2435 12.48. reply <msgno>
2437 reply <msgno> Reply (privately) to the specified message
2441 12.49. reply b <msgno>
2443 reply b <msgno> Reply as a Bulletin to the specified message
2447 12.50. reply noprivate <msgno>
2449 reply noprivate <msgno> Reply as a Bulletin to the specified message
2453 12.51. reply rr <msgno>
2455 reply rr <msgno> Reply to the specified message with read receipt
2458 You can reply to a message and the subject will automatically have
2459 "Re:" inserted in front of it, if it isn't already present.
2461 You can also use all the extra qualifiers such as RR, PRIVATE,
2462 NOPRIVATE, B that you can use with the SEND command (see SEND for
2465 12.52. send <call> [<call> ...]
2467 send <call> [<call> ...] Send a message to one or more callsigns
2471 12.53. send copy <msgno> <call>
2473 send copy <msgno> <call> Send a copy of a message to someone
2477 12.54. send noprivate <call>
2479 send noprivate <call> Send a message to all stations
2482 All the SEND commands will create a message which will be sent either
2483 to an individual callsign or to one of the 'bulletin' addresses.
2485 SEND <call> on its own acts as though you had typed SEND PRIVATE, that
2486 is it will mark the message as personal and send it to the cluster
2487 node that that callsign is connected to. If the <call> you have
2488 specified is in fact a known bulletin category on your node (eg: ALL)
2489 then the message should automatically become a bulletin.
2491 You can have more than one callsign in all of the SEND commands.
2493 You can have multiple qualifiers so that you can have for example:-
2497 SEND RR COPY 123 PRIVATE G1TLH G0RDI
2501 which should send a copy of message 123 to G1TLH and G0RDI and you
2502 will receive a read receipt when they have read the message.
2504 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
2505 is an alias for SEND PRIVATE
2507 The system will ask you for a subject. Conventionally this should be
2508 no longer than 29 characters for compatibility. Most modern cluster
2509 software should accept more.
2511 You will now be prompted to start entering your text.
2513 You finish the message by entering '/EX' on a new line. For instance:
2524 If you have started a message and you don't want to keep it then you
2525 can abandon the message with '/ABORT' on a new line, like:-
2531 oh I just can't be bothered with this
2536 If you abort the message it will NOT be sent.
2538 When you are entering the text of your message, most normal output
2539 (such as DX announcements and so on are suppressed and stored for
2540 latter display (upto 20 such lines are stored, as new ones come along,
2541 so the oldest lines are dropped).
2543 Also, you can enter normal commands commands (and get the output
2544 immediately) whilst in the middle of a message. You do this by typing
2545 the command preceeded by a '/' character on a new line, so:-
2549 /dx g1tlh 144010 strong signal
2553 Will issue a dx annoucement to the rest of the cluster.
2555 Also, you can add the output of a command to your message by
2556 preceeding the command with '//', thus :-
2564 This will show YOU the output from SH/VHFTABLE and also store it in
2567 You can carry on with the message until you are ready to send it.
2569 12.55. send private <call>
2571 send private <call> Send a personal message
2575 12.56. send rr <call>
2577 send rr <call> Send a message and ask for a read receipt
2581 12.57. set/address <your address>
2583 set/address <your address> Record your postal address
2589 set/announce Allow announce messages to come out on your terminal
2595 set/anntalk Allow talk like announce messages on your terminal
2601 set/beep Add a beep to DX and other messages on your terminal
2607 set/dx Allow DX messages to come out on your terminal
2613 set/dxcq Show CQ Zones on the end of DX announcements
2619 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
2625 set/dxitu Show ITU Zones on the end of DX announcements
2631 set/echo Make the cluster echo your input
2635 12.66. set/email <email> ...
2637 set/email <email> ... Set email address(es) and forward your personals
2643 set/here Tell the system you are present at your terminal
2647 12.68. set/homenode <node>
2649 set/homenode <node> Set your normal cluster callsign
2652 Tell the cluster system where you normally connect to. Any Messages
2653 sent to you will normally find their way there should you not be
2661 12.69. set/language <lang>
2663 set/language <lang> Set the language you want to use
2666 You can select the language that you want the cluster to use.
2667 Currently the languages available are en (English), de (German), es
2668 (Spanish) and nl (Dutch).
2670 12.70. set/location <lat & long>
2672 set/location <lat & long> Set your latitude and longitude
2676 12.71. set/logininfo
2678 set/logininfo Inform when a station logs in locally
2681 12.72. set/name <your name>
2683 set/name <your name> Set your name
2686 Tell the system what your name is eg:-
2693 12.73. set/page <lines per page>
2695 set/page <lines per page> Set the lines per page
2698 Tell the system how many lines you wish on a page when the number of
2699 line of output from a command is more than this. The default is 20.
2700 Setting it explicitly to 0 will disable paging.
2708 The setting is stored in your user profile.
2712 set/password Set your own password
2715 This command only works for a 'telnet' user (currently). It will only
2716 work if you have a password already set. This initial password can
2717 only be set by the sysop.
2719 When you execute this command it will ask you for your old password,
2720 then ask you to type in your new password twice (to make sure you get
2721 it right). You may or may not see the data echoed on the screen as you
2722 type, depending on the type of telnet client you have.
2724 12.75. set/prompt <string>
2726 set/prompt <string> Set your prompt to <string>
2730 12.76. set/qra <locator>
2732 set/qra <locator> Set your QRA Grid locator
2735 Tell the system what your QRA (or Maidenhead) locator is. If you have
2736 not done a SET/LOCATION then your latitude and longitude will be set
2737 roughly correctly (assuming your locator is correct ;-). For example:-
2744 12.77. set/qth <your qth>
2746 set/qth <your qth> Set your QTH
2749 Tell the system where you are. For example:-
2752 SET/QTH East Dereham, Norfolk
2758 set/talk Allow TALK messages to come out on your terminal
2764 set/usstate Allow US State info on the end of DX announcements
2770 set/wcy Allow WCY messages to come out on your terminal
2776 set/wwv Allow WWV messages to come out on your terminal
2782 set/wx Allow WX messages to come out on your terminal
2786 12.83. show/chat [<group>] [<lines>]
2788 show/chat [<group>] [<lines>] Show any chat or conferencing
2791 This command allows you to see any chat or conferencing that has
2792 occurred whilst you were away. SHOW/CHAT on its own will show data for
2793 all groups. If you use a group name then it will show only chat for
2796 12.84. show/configuration [<node>]
2798 show/configuration [<node>] Show all the nodes and users visible
2801 This command allows you to see all the users that can be seen and the
2802 nodes to which they are connected.
2804 This command is normally abbreviated to: sh/c
2806 Normally, the list returned will be just for the nodes from your
2807 country (because the list otherwise will be very long).
2812 will produce a complete list of all nodes.
2814 BE WARNED: the list that is returned can be VERY long
2816 It is possible to supply a node or part of a prefix and you will get a
2817 list of the users for that node or list of nodes starting with that
2830 12.85. show/configuration/node
2832 show/configuration/node Show all the nodes connected locally
2835 Show all the nodes connected to this node.
2837 12.86. show/contest <year and month>
2839 show/contest <year and month> Show all the contests for a month
2842 Show all known contests which are maintained at
2843 http://www.sk3bg.se/contest/ for a particular month or year. The
2844 format is reasonably flexible. For example:-
2853 12.87. show/date [<prefix>|<callsign>]
2855 show/date [<prefix>|<callsign>] Show the local time
2858 This is very nearly the same as SHOW/TIME, the only difference the
2859 format of the date string if no arguments are given.
2861 If no prefixes or callsigns are given then this command returns the
2862 local time and UTC as the computer has it right now. If you give some
2863 prefixes then it will show UTC and UTC + the local offset (not
2864 including DST) at the prefixes or callsigns that you specify.
2866 12.88. show/db0sdx <callsign>
2868 show/db0sdx <callsign> Show QSL infomation from DB0SDX database
2871 This command queries the DB0SDX QSL server on the internet and returns
2872 any information available for that callsign. This service is provided
2873 for users of this software by http://www.qslinfo.de.
2875 See also SHOW/QRZ, SHOW/WM7D.
2879 show/dx Interrogate the spot database
2882 If you just type SHOW/DX you will get the last so many spots (sysop
2883 configurable, but usually 10).
2885 In addition you can add any number of these commands in very nearly
2886 any order to the basic SHOW/DX command, they are:-
2890 on <band> - eg 160m 20m 2m 23cm 6mm
2891 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2892 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
2897 <number> - the number of spots you want
2898 <from>-<to> - <from> spot no <to> spot no in the selected list
2903 <prefix> - for a spotted callsign beginning with <prefix>
2904 *<suffix> - for a spotted callsign ending in <suffix>
2905 *<string>* - for a spotted callsign containing <string>
2909 day <number> - starting <number> days ago
2910 day <from>-<to> - <from> days <to> days ago
2915 info <text> - any spots containing <text> in the info or remarks
2919 by <call> - any spots spotted by <call> (spotter <call> is the
2924 qsl - this automatically looks for any qsl info on the call
2925 held in the spot database.
2929 iota [<iota>] - If the iota island number is missing it will look for
2930 the string iota and anything which looks like an iota
2931 island number. If you specify then it will look for
2936 qra [<locator>] - this will look for the specific locator if you specify
2937 one or else anything that looks like a locator.
2941 dxcc - treat the prefix as a 'country' and look for spots
2942 from that country regardless of actual prefix.
2947 You can also use this with the 'by' keyword so
2957 SH/DX on 20m info iota
2958 SH/DX 9a on vhf day 30
2964 SH/DX dxcc oq2 by w dxcc
2968 12.90. show/dxcc <prefix>
2970 show/dxcc <prefix> Interrogate the spot database by country
2973 This command takes the <prefix> (which can be a full or partial
2974 callsign if desired), looks up which internal country number it is and
2975 then displays all the spots as per SH/DX for that country.
2977 This is now an alias for 'SHOW/DX DXCC'
2979 The options for SHOW/DX also apply to this command. e.g.
2984 SH/DXCC W on 20m iota
2988 This can be done with the SHOW/DX command like this:-
2993 SH/DX dxcc w on 20m iota
2997 12.91. show/dxqsl <callsign>
2999 show/dxqsl <callsign> Show any QSL info gathered from spots
3002 The node collects information from the comment fields in spots (things
3003 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
3005 This command allows you to interrogate that database and if the
3006 callsign is found will display the manager(s) that people have
3007 spotted. This information is NOT reliable, but it is normally
3008 reasonably accurate if it is spotted enough times.
3017 You can check the raw input spots yourself with:-
3025 This gives you more background information.
3027 12.92. show/dxstats [days] [date]
3029 show/dxstats [days] [date] Show the DX Statistics
3032 Show the total DX spots for the last <days> no of days (default is
3033 31), starting from a <date> (default: today).
3035 12.93. show/files [<filearea> [<string>]]
3037 show/files [<filearea> [<string>]] List the contents of a filearea
3040 SHOW/FILES on its own will show you a list of the various fileareas
3041 available on the system. To see the contents of a particular file area
3049 where <filearea> is the name of the filearea you want to see the con-
3052 You can also use shell globbing characters like '*' and '?' in a
3053 string to see a selection of files in a filearea eg:-
3056 SH/FILES bulletins arld*
3060 See also TYPE - to see the contents of a file.
3064 show/filter Show the contents of all the filters you have set
3067 Show the contents of all the filters that are set. This command
3068 displays all the filters set - for all the various categories.
3070 12.95. show/hfstats [days] [date]
3072 show/hfstats [days] [date] Show the HF DX Statistics
3075 Show the HF DX spots breakdown by band for the last <days> no of days
3076 (default is 31), starting from a <date> (default: today).
3080 12.96. show/hftable [days] [date] [prefix ...]
3082 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
3085 Show the HF DX Spotter table for the list of prefixes for the last
3086 <days> no of days (default is 31), starting from a <date> (default:
3089 If there are no prefixes then it will show the table for your country.
3091 Remember that some countries have more than one "DXCC country" in them
3092 (eg G :-), to show them (assuming you are not in G already which is
3093 specially treated in the code) you must list all the relevant prefixes
3097 sh/hftable g gm gd gi gj gw gu
3101 Note that the prefixes are converted into country codes so you don't
3102 have to list all possible prefixes for each country.
3104 If you want more or less days than the default simply include the
3105 number you require:-
3113 If you want to start at a different day, simply add the date in some
3118 sh/hftable 2 25nov02
3119 sh/hftable 2 25-nov-02
3121 sh/hftable 2 25/11/02
3125 This will show the stats for your DXCC for that CQWW contest weekend.
3127 You can specify either prefixes or full callsigns (so you can see how
3128 you did against all your mates). You can also say 'all' which will
3129 then print the worldwide statistics.
3137 12.97. show/moon [ndays] [<prefix>|<callsign>]
3139 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
3141 Show the Moon rise and set times for a (list of) prefixes or
3142 callsigns, together with the azimuth and elevation of the sun
3143 currently at those locations.
3145 If you don't specify any prefixes or callsigns, it will show the times
3146 for your QTH (assuming you have set it with either SET/LOCATION or
3147 SET/QRA), together with the current azimuth and elevation.
3149 In addition, it will show the illuminated fraction of the moons disk.
3151 If all else fails it will show the Moonrise and set times for the node
3152 that you are connected to.
3163 You can also use this command to see into the past or the future, so
3164 if you want to see yesterday's times then do:-
3172 or in three days time:-
3180 Upto 366 days can be checked both in the past and in the future.
3182 Please note that the rise and set times are given as the UT times of
3183 rise and set on the requested UT day.
3185 12.98. show/muf <prefix> [<hours>][long]
3187 show/muf <prefix> [<hours>][long] Show the likely propagation to a
3191 This command allow you to estimate the likelihood of you contacting a
3192 station with the prefix you have specified. The output assumes a
3193 modest power of 20dBW and receiver sensitivity of -123dBm (about
3196 The result predicts the most likely operating frequencies and signal
3197 levels for high frequency (shortwave) radio propagation paths on
3198 specified days of the year and hours of the day. It is most useful for
3199 paths between 250 km and 6000 km, but can be used with reduced
3200 accuracy for paths shorter or longer than this.
3202 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
3203 used to predict the MUF given the predicted flux, day of the year,
3204 hour of the day and geographic coordinates of the transmitter and
3205 receiver. This routine is reasonably accurate for the purposes here,
3206 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
3207 than the programs used by major shortwave broadcasting organizations,
3208 such as the Voice of America.
3210 The command will display some header information detailing its
3211 assumptions, together with the locations, latitude and longitudes and
3212 bearings. It will then show UTC (UT), local time at the other end
3213 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
3214 (Zen) and the likely signal strengths. Then for each frequency for
3215 which the system thinks there is a likelihood of a circuit it prints a
3218 The value is currently a likely S meter reading based on the
3219 conventional 6dB / S point scale. If the value has a '+' appended it
3220 means that it is 1/2 an S point stronger. If the value is preceeded by
3221 an 'm' it means that there is likely to be much fading and by an 's'
3222 that the signal is likely to be noisy.
3224 By default SHOW/MUF will show the next two hours worth of data. You
3225 can specify anything up to 24 hours worth of data by appending the no
3226 of hours required after the prefix. For example:-
3238 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
3239 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
3240 Location Lat / Long Azim
3241 East Dereham, Norfolk 52 41 N 0 57 E 47
3242 United-States-W 43 0 N 87 54 W 299
3243 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
3244 18 23 11.5 -35 mS0+ mS2 S3
3245 19 0 11.2 -41 mS0+ mS2 S3
3249 indicating that you will have weak, fading circuits on top band and
3250 80m but usable signals on 40m (about S3).
3260 will get you the above display, but with the next 24 hours worth of
3270 Gives you an estimate of the long path propagation characterics. It
3271 should be noted that the figures will probably not be very useful, nor
3272 terrible accurate, but it is included for completeness.
3274 12.99. show/newconfiguration [<node>]
3276 show/newconfiguration [<node>] Show all the nodes and users visible
3279 This command allows you to see all the users that can be seen and the
3280 nodes to which they are connected.
3282 This command produces essentially the same information as
3283 SHOW/CONFIGURATION except that it shows all the duplication of any
3284 routes that might be present It also uses a different format which may
3285 not take up quite as much space if you don't have any loops.
3287 BE WARNED: the list that is returned can be VERY long
3289 12.100. show/newconfiguration/node
3291 show/newconfiguration/node Show all the nodes connected locally
3294 Show all the nodes connected to this node in the new format.
3296 12.101. show/prefix <callsign>
3298 show/prefix <callsign> Interrogate the prefix database
3301 This command takes the <callsign> (which can be a full or partial
3302 callsign or a prefix), looks up which internal country number it is
3303 and then displays all the relevant prefixes for that country together
3304 with the internal country no, the CQ and ITU regions.
3308 12.102. show/qra <lat> <long>
3310 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
3313 This is a multipurpose command that allows you either to calculate the
3314 distance and bearing between two locators or (if only one locator is
3315 given on the command line) the distance and beraing from your station
3316 to the locator. For example:-
3325 The first example will show the distance and bearing to the locator
3326 from yourself, the second example will calculate the distance and
3327 bearing from the first locator to the second. You can use 4 or 6
3329 It is also possible to convert a latitude and longitude to a locator
3330 by using this command with a latitude and longitude as an argument,
3335 SH/QRA 52 41 N 0 58 E
3339 12.103. show/qra <locator> [<locator>]
3341 show/qra <locator> [<locator>] Show distance between QRA Grid locators
3345 12.104. show/qrz <callsign>
3347 show/qrz <callsign> Show any callbook details on a callsign
3350 This command queries the QRZ callbook server on the internet and
3351 returns any information available for that callsign. This service is
3352 provided for users of this software by http://www.qrz.com
3354 See also SHOW/WM7D for an alternative.
3356 12.105. show/route <callsign> ...
3358 show/route <callsign> ... Show the route to the callsign
3361 This command allows you to see to which node the callsigns specified
3362 are connected. It is a sort of inverse sh/config.
3370 12.106. show/satellite <name> [<hours> <interval>]
3372 show/satellite <name> [<hours> <interval>] Show tracking data
3375 Show the tracking data from your location to the satellite of your
3376 choice from now on for the next few hours.
3378 If you use this command without a satellite name it will display a
3379 list of all the satellites known currently to the system.
3381 If you give a name then you can obtain tracking data of all the passes
3382 that start and finish 5 degrees below the horizon. As default it will
3383 give information for the next three hours for every five minute
3386 You can alter the number of hours and the step size, within certain
3389 Each pass in a period is separated with a row of '-----' characters
3396 SH/SAT FENGYUN1 12 2
3400 12.107. show/station [<callsign> ..]
3402 show/station [<callsign> ..] Show information about a callsign
3405 Show the information known about a callsign and whether (and where)
3406 that callsign is connected to the cluster.
3414 If no callsign is given then show the information for yourself.
3416 12.108. show/sun [ndays] [<prefix>|<callsign>]
3418 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
3421 Show the sun rise and set times for a (list of) prefixes or callsigns,
3422 together with the azimuth and elevation of the sun currently at those
3425 If you don't specify any prefixes or callsigns, it will show the times
3426 for your QTH (assuming you have set it with either SET/LOCATION or
3427 SET/QRA), together with the current azimuth and elevation.
3429 If all else fails it will show the sunrise and set times for the node
3430 that you are connected to.
3437 SH/SUN G1TLH K9CW ZS
3441 You can also use this command to see into the past or the future, so
3442 if you want to see yesterday's times then do:-
3450 or in three days time:-
3456 Upto 366 days can be checked both in the past and in the future.
3458 Please note that the rise and set times are given as the UT times of
3459 rise and set on the requested UT day.
3461 12.109. show/time [<prefix>|<callsign>]
3463 show/time [<prefix>|<callsign>] Show the local time
3466 If no prefixes or callsigns are given then this command returns the
3467 local time and UTC as the computer has it right now. If you give some
3468 prefixes then it will show UTC and UTC + the local offset (not
3469 including DST) at the prefixes or callsigns that you specify.
3471 12.110. show/usdb [call ..]
3473 show/usdb [call ..] Show information held on the FCC Call database
3476 Show the City and State of a Callsign held on the FCC database if his
3477 is being run on this system, eg:-
3485 12.111. show/vhfstats [days] [date]
3487 show/vhfstats [days] [date] Show the VHF DX Statistics
3490 Show the VHF DX spots breakdown by band for the last <days> no of days
3491 (default is 31), starting from a date (default: today).
3493 12.112. show/vhftable [days] [date] [prefix ...]
3495 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
3498 Show the VHF DX Spotter table for the list of prefixes for the last
3499 <days> no of days (default is 31), starting from a date (default:
3502 If there are no prefixes then it will show the table for your country.
3504 Remember that some countries have more than one "DXCC country" in them
3505 (eg G :-), to show them (assuming you are not in G already which is
3506 specially treated in the code) you must list all the relevant prefixes
3510 sh/vhftable g gm gd gi gj gw gu
3514 Note that the prefixes are converted into country codes so you don't
3515 have to list all possible prefixes for each country.
3517 If you want more or less days than the default simply include the
3518 number you require:-
3526 If you want to start at a different day, simply add the date in some
3531 sh/vhftable 2 25nov02
3532 sh/vhftable 2 25-nov-02
3533 sh/vhftable 2 021125
3534 sh/vhftable 2 25/11/02
3538 This will show the stats for your DXCC for that CQWW contest weekend.
3540 You can specify either prefixes or full callsigns (so you can see how
3541 you did against all your mates). You can also say 'all' which will
3542 then print the worldwide statistics.
3552 show/wcy Show last 10 WCY broadcasts
3556 12.114. show/wcy <n>
3558 show/wcy <n> Show last <n> WCY broadcasts
3561 Display the most recent WCY information that has been received by the
3565 12.115. show/wm7d <callsign>
3567 show/wm7d <callsign> Show callbook details on a US callsigns
3570 This command queries the WM7D callbook server on the internet and
3571 returns any information available for that US callsign. This service
3572 is provided for users of this software by http://www.wm7d.net.
3578 show/wwv Show last 10 WWV broadcasts
3582 12.117. show/wwv <n>
3584 show/wwv <n> Show last <n> WWV broadcasts
3587 Display the most recent WWV information that has been received by the
3592 sysop Regain your privileges if you login remotely
3595 The system automatically reduces your privilege level to that of a
3596 normal user if you login in remotely. This command allows you to
3597 regain your normal privilege level. It uses the normal system: five
3598 numbers are returned that are indexes into the character array that is
3599 your assigned password (see SET/PASSWORD). The indexes start from
3602 You are expected to return a string which contains the characters
3603 required in the correct order. You may intersperse those characters
3604 with others to obscure your reply for any watchers. For example (and
3605 these values are for explanation :-):
3609 password = 012345678901234567890123456789
3618 aa2bbbb0ccc5ddd7xxx3n
3624 They will all match. If there is no password you will still be offered
3625 numbers but nothing will happen when you input a string. Any match is
3628 12.119. talk <call> > <node> [<text>]
3630 talk <call> > <node> [<text>] Send a text message to another station
3634 Send a short message to any other station that is visible on the
3635 cluster system. You can send it to anyone you can see with a
3636 SHOW/CONFIGURATION command, they don't have to be connected locally.
3638 The second form of TALK is used when other cluster nodes are connected
3639 with restricted information. This usually means that they don't send
3640 the user information usually associated with logging on and off the
3643 If you know that G3JNB is likely to be present on GB7TLH, but you can
3644 only see GB7TLH in the SH/C list but with no users, then you would use
3645 the second form of the talk message.
3647 If you want to have a ragchew with someone you can leave the text
3648 message out and the system will go into 'Talk' mode. What this means
3649 is that a short message is sent to the recipient telling them that you
3650 are in a go to the station that you asked for.
3652 All the usual announcements, spots and so on will still come out on
3655 If you want to do something (such as send a spot) you preceed the
3656 normal command with a '/' character, eg:-
3660 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
3665 To leave talk mode type:
3673 If you are in 'Talk' mode, there is an extention to the '/' command
3674 which allows you to send the output to all the people you are talking
3675 to. You do with the '//' command. For example:-
3683 will send the hftable as you have it to all the people you are
3684 currently talking to.
3686 12.120. talk <call> [<text>]
3688 talk <call> [<text>] Send a text message to another station
3692 12.121. type <filearea>/<name>
3694 type <filearea>/<name> Look at the contents of a file in one of the
3698 Type out the contents of a file in a filearea. So, for example, in
3699 filearea 'bulletins' you want to look at file 'arld051' you would
3703 TYPE bulletins/arld051
3707 See also SHOW/FILES to see what fileareas are available and a list of
3710 12.122. unset/announce
3712 unset/announce Stop announce messages coming out on your terminal
3716 12.123. unset/anntalk
3718 unset/anntalk Stop talk like announce messages on your terminal
3721 The announce system on legacy cluster nodes is used as a talk
3722 substitute because the network is so poorly connected. If you:
3730 you will suppress several of these announces, you may miss the odd
3731 useful one as well, but you would probably miss them anyway in the
3732 welter of useless ones.
3740 allows you to see them again. This is the default.
3744 unset/beep Stop beeps for DX and other messages on your terminal
3750 unset/dx Stop DX messages coming out on your terminal
3756 unset/dxcq Stop CQ Zones on the end of DX announcements
3759 Display both the Spotter's and the Spotted's CQ Zone on the end of a
3760 DX announcement (there is just enough room). Some user programs cannot
3761 cope with this. The Spotter's CQ is on the RHS of the time, the
3762 Spotted's CQ is on the LHS.
3764 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
3766 Do a STAT/USER to see which flags you have set if you are confused.
3768 12.127. unset/dxgrid
3770 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
3773 A standard feature which is enabled in version 1.43 and above is that
3774 if the spotter's grid square is known it is output on the end of a DX
3775 announcement (there is just enough room). Some user programs cannot
3776 cope with this. You can use this command to reset (or set) this
3779 Conflicts with: SET/DXCQ, SET/DXITU
3781 Do a STAT/USER to see which flags you have set if you are confused.
3785 unset/dxitu Stop ITU Zones on the end of DX announcements
3788 Display both the Spotter's and the Spotted's ITU Zone on the end of a
3789 DX announcement (there is just enough room). Some user programs cannot
3790 cope with this. The Spotter's ITU is on the RHS of the time, the
3791 Spotted's ITU is on the LHS.
3793 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
3795 Do a STAT/USER to see which flags you have set if you are confused.
3799 unset/echo Stop the cluster echoing your input
3802 If you are connected via a telnet session, different implimentations
3803 of telnet handle echo differently depending on whether you are
3804 connected via port 23 or some other port. You can use this command to
3805 change the setting appropriately.
3807 The setting is stored in your user profile.
3809 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
3813 unset/email Stop personal msgs being forwarded by email
3816 If any personal messages come in for your callsign then you can use
3817 these commands to control whether they are forwarded onto your email
3818 address. To enable the forwarding do something like:-
3822 SET/EMAIL mike.tubby@somewhere.com
3826 You can have more than one email address (each one separated by a
3827 space). Emails are forwarded to all the email addresses you specify.
3829 You can disable forwarding by:-
3837 unset/here Tell the system you are absent from your terminal
3841 12.132. unset/logininfo
3843 unset/logininfo Inform when a station logs out locally
3847 12.133. unset/privilege
3849 unset/privilege Remove any privilege for this session
3852 You can use this command to 'protect' this session from unauthorised
3853 use. If you want to get your normal privilege back you will need to
3854 either logout and login again (if you are on a console) or use the
3857 12.134. unset/prompt
3859 unset/prompt Set your prompt back to default
3862 This command will set your user prompt to exactly the string that you
3863 say. The point of this command to enable a user to interface to
3864 programs that are looking for a specific prompt (or else you just want
3865 a different fixed prompt).
3873 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
3878 unset/talk Stop TALK messages coming out on your terminal
3882 12.136. unset/usstate
3884 unset/usstate Stop US State info on the end of DX announcements
3887 If the spotter's or spotted's US State is known it is output on the
3888 end of a DX announcement (there is just enough room).
3890 A spotter's state will appear on the RHS of the time (like SET/DXGRID)
3891 and the spotted's State will appear on the LHS of the time field. Any
3892 information found will override any locator information from
3894 Some user programs cannot cope with this. You can use this command to
3895 reset (or set) this feature.
3897 Conflicts with: SET/DXCQ, SET/DXITU
3899 Do a STAT/USER to see which flags you have set if you are confused.
3903 unset/wcy Stop WCY messages coming out on your terminal
3909 unset/wwv Stop WWV messages coming out on your terminal
3915 unset/wx Stop WX messages coming out on your terminal
3921 who Show who is physically connected
3924 This is a quick listing that shows which callsigns are connected and
3925 what sort of connection they have
3929 wx <text> Send a weather message to local users
3933 12.142. wx full <text>
3935 wx full <text> Send a weather message to all cluster users
projects / spider.git / blob