1 The DXSpider User Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
3 March 2003 revision 0.3
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
51 11. Hints, tips and common questions.
53 11.2 accept/announce [0-9] <pattern>
54 11.3 accept/spots [0-9] <pattern>
55 11.4 accept/wcy [0-9] <pattern>
56 11.5 accept/wwv [0-9] <pattern>
58 11.7 announce full <text>
60 11.9 blank [<string>] [<nn>]
62 11.11 chat <group> <text>
63 11.12 clear/announce [1|all]
64 11.13 clear/route [1|all]
65 11.14 clear/spots [0-9|all]
66 11.15 clear/wcy [1|all]
67 11.16 clear/wwv [1|all]
69 11.18 dbshow <dbname> <key>
71 11.20 directory <from>-<to>
74 11.23 directory from <call>
77 11.26 directory subject <string>
78 11.27 directory to <call>
79 11.28 dx [by <call>] <freq> <call> <remarks>
84 11.33 kill <from msgno>-<to msgno>
85 11.34 kill <msgno> [<msgno..]
86 11.35 kill <msgno> [<msgno> ...]
87 11.36 kill from <regex>
94 11.43 reject/announce [0-9] <pattern>
95 11.44 reject/spots [0-9] <pattern>
96 11.45 reject/wcy [0-9] <pattern>
97 11.46 reject/wwv [0-9] <pattern>
100 11.49 reply b <msgno>
101 11.50 reply noprivate <msgno>
102 11.51 reply rr <msgno>
103 11.52 send <call> [<call> ...]
104 11.53 send copy <msgno> <call>
105 11.54 send noprivate <call>
106 11.55 send private <call>
108 11.57 set/address <your address>
117 11.66 set/email <email> ...
119 11.68 set/homenode <node>
120 11.69 set/language <lang>
121 11.70 set/location <lat & long>
123 11.72 set/name <your name>
124 11.73 set/page <lines per page>
126 11.75 set/prompt <string>
127 11.76 set/qra <locator>
128 11.77 set/qth <your qth>
134 11.83 show/chat [<group>] [<lines>]
135 11.84 show/configuration [<node>]
136 11.85 show/configuration/node
137 11.86 show/contest <year and month>
138 11.87 show/date [<prefix>|<callsign>]
139 11.88 show/db0sdx <callsign>
141 11.90 show/dxcc <prefix>
142 11.91 show/dxqsl <callsign>
143 11.92 show/dxstats [days] [date]
144 11.93 show/files [<filearea> [<string>]]
146 11.95 show/hfstats [days] [date]
147 11.96 show/hftable [days] [date] [prefix ...]
148 11.97 show/moon [ndays] [<prefix>|<callsign>]
149 11.98 show/muf <prefix> [<hours>][long]
150 11.99 show/newconfiguration [<node>]
151 11.100 show/newconfiguration/node
152 11.101 show/prefix <callsign>
153 11.102 show/qra <lat> <long>
154 11.103 show/qra <locator> [<locator>]
155 11.104 show/qrz <callsign>
156 11.105 show/route <callsign> ...
157 11.106 show/satellite <name> [<hours> <interval>]
158 11.107 show/station [<callsign> ..]
159 11.108 show/sun [ndays] [<prefix>|<callsign>]
160 11.109 show/time [<prefix>|<callsign>]
161 11.110 show/usdb [call ..]
162 11.111 show/vhfstats [days] [date]
163 11.112 show/vhftable [days] [date] [prefix ...]
166 11.115 show/wm7d <callsign>
170 11.119 talk <call> > <node> [<text>]
171 11.120 talk <call> [<text>]
172 11.121 type <filearea>/<name>
173 11.122 unset/announce
183 11.132 unset/logininfo
184 11.133 unset/privilege
193 11.142 wx full <text>
196 ______________________________________________________________________
200 1.1. What is a DX Cluster?
202 A DX Cluster is a packet node where DX chasers on any band or mode can
203 post rare or interesting stations that they have worked or heard. Of
204 course other people are doing the same thing too, so you can find new
205 DX as well as telling others about the stations you have worked.
206 Clusters tend to be linked to each other so that the amount of people
207 using them is increased, thereby increasing the amount of posted DX.
208 Other information can be found on clusters such as on-line call books,
209 mail etc. You can talk to other stations connected to the cluster
210 network too, in real time, whether at the node you are logged into or
211 on another node connected to the network. You can also use converse
212 mode, where several stations can talk to each other in the same way.
213 Of course, the DX is still posted to you all the while!
216 1.2. So what is DXSpider?
218 PacketCluster nodes have been around since roughly 1985. The original
219 PacketCluster idea came from Dick Newell, AK1A, and ran under DOS. In
220 about 1992 Dick stopped the development of the PacketCluster software
221 for amateur radio. Many systems are still using this relatively old
224 There are several new compatible cluster programs around now,
225 including DXSpider. DXSpider is a clone of PacketCluster software
226 that runs under several operating systems including Linux and Windows.
227 Linux is fast becoming the choice for amateur radio stations because
228 of it's flexibility, reliability and the lack of the memory
229 limitations of DOS. Linux supports multitasking and is also
230 multiuser. It has support for AX25, ROSE, NetROM and TCPIP built in,
231 making it the ideal choice for amateur radio. It is also totally
234 DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
235 exercise in perl programming. It has developed rapidly and today is a
236 very powerful cluster program. It was designed to be totally
237 compatible with the AK1A program, although several commands have been
238 extended to improve functionality.
240 This manual is designed to help you become familiar with the commands
241 that DXSpider supports and to help you get the best from the program
242 so you can enjoy working that rare DX! As DXSpider is being improved
243 all the time, commands will be added as time goes by, so make sure you
244 have the most upto date version of this manual. The latest version
245 will always be included with the cluster program so if you are unsure,
246 simply ask your sysop. The manual will also be available on the
251 2. Logins and logouts.
253 You might not think that there is a lot of point of including a
254 section on how to log in and out of DXSpider. However, you would be
255 suprised at the difficulties some people have in simply getting in and
258 There are several ways a login might be achieved, dependant on how the
259 sysop has DXSpider configured. It is impossible for me to cover all
260 variations but here are the basic ones.
265 Simplicity itself. The usual CONNECT command will log you straight
266 into the cluster and you will not have to do anything else.
267 Obviously, you will have to connect to the correct callsign. Some
268 nodes use an SSID with their call so you would have to add that.
281 There are several possibilities here, dependant on how the sysop has
282 configured his system. If you are connecting via netrom then you are
283 most probably connecting from another station. Listing the nodes in
284 that station with the NODES command will tell you what callsign or
285 netrom alias to connect to. Then just issue the connect command from
286 there. It is possible that the netrom alias may connect you to a node
287 with an alias for the cluster, such as DXC. Just type this and you
299 With telnet connections, the source callsign is not seen by DXSpider,
300 so you will be asked to login with your callsign. To telnet to
301 DXSpider, you would connect to a specific port. There is no standard
302 at the moment for a cluster telnet port but ask the sysop if you are
313 All the above are possible ways of connecting to a DXSpider cluster.
314 You may have some or all of these available to you. There may be one
315 or two additional ways to connect dependant on the network local to
316 you. However I am sure you get the idea.
321 Logging out can be done by simply issuing the standard BYE command.
323 You could also send a disconnect if you are using AX25, or a CLOSE
324 command if you are connected via telnet. If you do not log out
325 gracefully using one of the above commands, you may find you are
326 unable to get a full connect next time. This may also happen if a
327 netrom connection drops. You may get connected, but nothing else will
328 happen because the program thinks you are still connected and will not
329 let you connect twice under the same call. However you could
330 reconnect by adding a number to the end of your call, for example
331 G0YLM-2. This can be done by either altering your MYCALL setting in
332 the TNC or by altering your program configuration.
335 3. Setting your personal details.
337 Once logged in to the cluster, you should set your details so that
338 anybody who wishes to contact you can find out who and where you are.
339 There are four items to set, your name, qth, location and home node.
340 Setting these details also allows the use of the SHOW/HEADING and
341 SHOW/SUN commands from within the cluster. Unless you set your QTH
342 and location, these commands cannot function. Once you have set your
343 name, DXSpider will greet you with it next time you login. Your QTH
344 setting is where you live and it is a good idea to add your locator to
345 this as the location setting is converted to latitude and longitude
346 once inputted. You can actually set your location in
347 latitude/longitude or as a locator. Setting your home node will tell
348 the program where you wish mail to be sent to you.
355 set/qth Morecambe, Lancashire IO84NB
356 set/location 48 34 n 12 12 e
362 4. Getting and posting DX.
364 When all is said and done, this is the main function of a DX cluster.
365 In its simplest form you can just connect to the node and you will
366 start to receive DX spots almost immediately! You can check on recent
367 postings in either a general manner or on a particular band or mode.
368 You can even check DX by callsign or a fragment of a callsign. Of
369 course, once you get the hang of things, it is expected that you start
370 posting some yourself! After all, there would be no clusters if
371 people did not post DX and you get the added thrill of the hunt!
376 As we have already said, it is possible just to connect to the cluster
377 and you will receive spots automatically. However, you may wish to
378 check on spots just posted. Maybe you wish to see if a particular
379 band is open or if a certain callsign is active, perhaps a DXpedition.
380 The command to do this is SHOW/DX. Without any other arguments, this
381 command will output the last 10 spots posted. It is possible to look
382 at more than this, for example the last 20 or 50 spots, by adding the
383 number to the command. You can make it even more specific by adding a
384 band in either wavelength or frequency, and/or any additional
385 information such as QSL details.
397 will show the last 10, 5 and 20 spots received by the cluster
410 will show the last 5, 10 or 20 spots on 20 metres only.
412 It is also possible to check for certain callsigns, or fragments of
413 callsigns in the same way.
424 would show the last 5 or 10 dx spots containing the callsign g0vgs.
427 You can check for DX by offset and also by specifying a comment to
440 would show the spots that arrived between 30 and 40 spots ago and any
441 spots with the word iota in the comment field. The case of the
442 comment is not important.
444 Checking DX posted on a certain day is possible too. All you have to
445 do here is to specify how many days ago it was like this ...
455 It is of course possible to specify multiple arguments.
459 show/dx 20 prefix 9a on vhf day 30
463 This would show the last 20 spots posted by or about calls with the
464 prefix 9a on vhf 30 days ago.
466 As you can see the SHOW/DX command is very flexible, so if you are not
467 sure whether something will work or not, try it and see! More
468 information can be found in the Command Set section.
473 To post DX you use the DX command. The syntax is shown below.
479 dx (frequency) (callsign) (remarks)
483 Where frequency is in kilohertz and the callsign is the callsign of
484 the station you have worked or heard, (ie not your own callsign!).
485 The remarks section allows you to add information like the operators
486 name or perhaps a location. Actually DXSpider will allow the
487 frequency and callsign fields to be entered in any order.
493 dx 14004 pa3ezl OP Aurelio 599
497 In fact, all the following will give the same result...
501 dx 14004 pa3ezl OP Aurelio 599
502 dx pa3ezl 14004 OP Aurelio 599
503 dx pa3ezl 14.004 OP Aurelio 599
507 This posting, or callout as it is known, will be forwarded to all
508 other connected stations both at the cluster you are connected to and
509 other active clusters in the network. The callout will also be sent
510 to you as proof of receipt.
513 5. Headings and propagation
515 There are three commands in DXSpider to help you get the best DX
516 possible. These are SHOW/SUN, SHOW/MOON and SHOW/HEADING. These
517 commands will only work for you if you have entered your personal
518 details. They use your entered location as a reference, so if you
519 have not entered it or have entered it incorrectly they will not
520 return the correct information.
523 The SHOW/SUN command can be used in three different ways. It can be
524 used to show sunrise and sunset times for your own station, a
525 particular callsign or a prefix.
535 The output from this would look something like this ..
540 Location Rise Set Azim Elev
541 G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
549 would look like this ...
554 Location Rise Set Azim Elev
555 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
559 You can also specify multiple arguments like this ...
563 sh/sun gw4veq 5b4ab zs
567 and then the output would look like this ...
571 sh/sun gw4veq 5b4ab zs
572 Location Rise Set Azim Elev
573 GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9
574 5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
575 ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
576 ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
577 ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
582 The SHOW/MOON command works in the same way as the SHOW/SUN command.
583 This program however, calculates the rise and set times of the moon
584 for a prefix or callsign, together with the current azimuth and
585 elevation of the sun at these locations.
595 The output from this command would look like this ..
600 Location Rise Set Azim Elev RGain dB
601 EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
605 You can see that the output is similar to the SHOW/SUN command, with
606 slightly different fields.
611 The SHOW/HEADING command works in the same way as the SHOW/SUN and
612 SHOW/MOON commands but outputs beam headings for a specified callsign
613 or prefix. Reciprocal beam headings are also calculated.
623 The output from this command would look like this ..
628 ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
629 ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
630 ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
631 ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
637 6.1. Making announcements.
639 Occasionally, you may wish to post something that does not fall into
640 the normal parameters for a DX callout. You may wish to tell
641 everybody connected that 10 FM is open for example, or ask if anyone
642 knows the QSL manager for a certain callsign etc. You can do this
643 using the ANNOUNCE command.
649 announce 10 FM is open in IO84NB to europe.
653 That would let everyone know locally that this was the case, however
654 it would not be forwarded to other nodes connected. To send
655 announcements to other connected nodes as well, you would use the FULL
662 announce full Anyone seen EA7WA today?
666 Be cautious in your use of announce full. There are many other tools
667 available to get the information you require and the judicious use of
668 this command is frowned upon as it creates a great deal of traffic
672 6.2. Listing announcements.
674 You can list previous announcements in the standard format with the
675 SHOW command. As before you can list just the last 5 or as many as
683 show/announcements 10
689 You can check which nodes are connected in the network, who is logged
690 on locally, who is logged on at all the nodes or even just one node in
691 particular. This is handy if you wish to see whether a friend is
692 connected at the node they use. To see who is connected to the nodes,
693 the SHOW/CONFIGURATION command is used.
700 show/configuration/nodes
701 show/configuration (node_call)
702 show/configuration (prefix)
706 The first of our three examples would output something like this,
715 GB7BIG (GD0TEP) GD3UMW
716 GB7BPQ (G0INA) G0RCI G3AKU G3OCA
718 GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
719 G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
722 GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
723 G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
725 (GB7DXG) GU6EFB GU7DHI
726 GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
728 GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
733 You will notice that EI5TCR is showing only that it has 7 users and
734 not giving the actual callsigns. This means that this node is on a
735 limited protocol of some kind, probably because of a contest situation
736 where slow radio links can block up and fail if too much information
737 is sent between nodes.
739 The second example would just show the nodes connected in the network,
746 GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
747 GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
748 GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
749 GB7YDX KL7G N2TLY (ON0DXK)
750 GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
757 If we insert the node_call pi4tue-8 into the third example, then this
763 PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
764 F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
765 ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
766 PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
771 As you can see, only the users of the requested node are shown.
773 You can also use a prefix to show only a group of nodes. For example
774 you may only wish to see who is connected to the nodes in the UK. To
775 do this simply use a prefix like this ...
778 show/configuration gb7
782 To show the locally connected users, the SHOW/USERS command is used
792 The output of this command would look like this,
796 Callsigns connected to GB7MBC
797 G0JHC G0NEI G0VGS G0VGS-2 G0YLM
804 You can send a single comment or start a dedicated talk session to
805 another user by using the TALK command.
808 Talk mode is used to send a one line comment or greeting to a specific
809 user connected either at your node or another in the network. You can
810 also enter into a dedicated talk session with another user. Talks
811 will be automatically forwarded to other nodes if the station you are
812 talking to is not connected locally. You can find out who is
813 connected by using the SHOW/CONFIGURATION command, (described
820 talk g0rdi Having a good day Iain?
823 This example would send the line "Having a good day Iain?" to the user
824 g0rdi but would leave you in normal mode.
829 Entering Talkmode, /EX to end, /<cmd> to run a command
834 As you can see, you can still run commands whilst in talk mode.
835 Simply prefix the command with a / like /sh/dx and you will get the
836 expected output. If the user is connected to another node, you may
837 have to use a slightly extended version of the TALK command.
845 To exit talk mode, you issue the command /ex.
847 Whilst in talk mode you will still receive DX spots. This means that
848 you can chat to a friend whilst working DX.
853 You can send and receive both personal mail and bulletins with
854 DXSpider quite easily.
857 9.1. The "directory" command.
859 To list mail you would use the DIRECTORY command. On its own, this
860 command will output the last ten messages received by the node, either
861 to or from yourself or bulletins such as "DX" and "ALL". As with
862 other commands you can display more by specifying a number with the
863 command. You should be aware that Spider will accept these commands
864 by separating with either a slash or a space, so dir new and dir/new
865 work in the same way.
877 Of course most of the time you will only want to list new mail sent to
878 you personally since your last login. However you might also like to
879 check for general mail received by the node. In fact if there is new
880 mail for you, the cluster will tell you when you login. You will also
881 be informed if new mail arrives for you during the time you are logged
882 in. Mail is not only sent to callsigns though. Mail can also be sent
883 to subjects like "all" or "local" or "dx" etc. You can treat these
884 bulletins in the same way as personal mail with the directory command.
894 directory/from <call>
898 The last option will only show mail from a callsign if it was sent to
899 you personally or was sent as a bulletin. There are some additional
900 commands and these can be found in the DXSpider Command Reference
906 The output of the DIRECTORY command could be something like this.
911 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
912 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
913 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
914 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
915 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
916 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
917 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
918 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
919 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
920 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
921 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
925 The first column is the actual message number. If the message is a
926 personal one to you, you will see a letter 'p' after this number. If
927 the message has been read, there will be a '-' between the message
928 number and the 'p'. This only works for personal messages. The next
929 column shows the file size of the message. The third column shows the
930 address the message was sent to and the next column shows who sent it.
931 The rest is fairly self-explanatory.
933 Reading a message is as simple as typing read, followed by the message
934 number that you wish to read.
944 will read message number 25. However the mail will be displayed in
945 it's entirety unless you specify a page length. You can set your page
946 length to any number you like and when the message reaches that number
947 of lines you will get a prompt giving you options.
958 Sending mail is done in the time honoured way. First you specify a
959 recipient for the message, then you will be prompted for a subject.
960 Once you have done this you will be asked to type your message.
961 Please remember that there is no automatic word wrap, so unless you
962 are using a client that wraps lines automatically, remember to hit
963 return at the end of each line.
970 Enter Subject (30 characters):
972 Enter Message /EX to send or /ABORT to exit
974 Just a quick note to say that I can make Thursday after all. The
975 appointment I had has cancelled so we are go!
981 At this point you can either hit return and enter /ex to send the
982 message or use /abort at any time to abort it. You can now display
983 the message in the normal way. There are several send options and
984 these are listed in the Command Set section. These include sending
985 mail to several recipients and asking for a return receipt.
989 9.4. Replying to mail.
991 If mail is addressed to you or to a bulletin address, you can use the
992 REPLY command to reply to it. Using this command, the subject will be
993 automatically set for you as "Re: subject", whatever the subject was.
1005 To delete a message, you use the delete command. You can only delete
1006 messages sent to or received by yourself. Bulletins are dealt with
1007 automatically or by the sysop.
1008 10. Filtering (From version 1.45)
1010 10.1. General filter rules
1012 Upto v1.44 it was not possible for the user to set their own filters.
1013 From v1.45 though that has all changed. It is now possible to set
1014 filters for just about anything you wish. If you have just updated
1015 from an older version of DXSpider you will need to update your new
1016 filters. You do not need to do anything with your old filters, they
1017 will be renamed as you update.
1020 There are 3 basic commands involved in setting and manipulating
1021 filters. These are accept, reject and clear. First we will look
1022 generally at filtering. There are a number of things you can filter in
1023 the DXSpider system. They all use the same general mechanism.
1026 In general terms you can create a 'reject' or an 'accept' filter which
1027 can have up to 10 lines in it. You do this using, for example ...
1036 where ..... are the specific commands for that type of filter. There
1037 are filters for spots, wwv, announce, wcy and (for sysops) connects.
1038 See each different accept or reject command reference for more
1041 There is also a command to clear out one or more lines in a filter.
1051 There is clear/xxxx command for each type of filter.
1054 and you can check that your filters have worked by the command ...
1062 For now we are going to use spots for the examples, but you can apply
1063 the same principles to all types of filter.
1067 10.2. Types of filter
1069 There are two main types of filter, accept or reject. You can use
1070 either to achieve the result you want dependent on your own preference
1071 and which is more simple to do. It is pointless writing 8 lines of
1072 reject filters when 1 accept filter would do the same thing! Each
1073 filter has 10 lines (of any length) which are tried in order. If a
1074 line matches then the action you have specified is taken (ie reject
1075 means ignore it and accept means take it)
1078 If you specify reject filters, then any lines that arrive that match
1079 the filter will be dumped but all else will be accepted. If you use
1080 an accept filter, then ONLY the lines in the filter will be accepted
1081 and all else will be dumped. For example if you have a single line
1086 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1090 then you will ONLY get VHF spots from or to CQ zones 14, 15 and 16.
1093 If you set a reject filter like this ...
1097 reject/spots on hf/cw
1101 Then you will get everything EXCEPT HF CW spots. You could make this
1102 single filter even more flexible. For example, if you are interested
1103 in IOTA and will work it even on CW even though normally you are not
1104 interested in CW, then you could say ...
1108 reject/spots on hf/cw and not info iota
1112 But in that case you might only be interested in iota and say:-
1116 accept/spots not on hf/cw or info iota
1120 which achieves exactly the same thing. You should choose one or the
1121 other until you are comfortable with the way it works. You can mix
1122 them if you wish (actually you can have an accept AND a reject on the
1123 same line) but don't attempt this until you are sure you know what you
1127 You can arrange your filter lines into logical units, either for your
1128 own understanding or simply convenience. Here is an example ...
1129 reject/spots 1 on hf/cw
1130 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
1134 What this does is to ignore all HF CW spots and also rejects any spots
1135 on VHF which don't either originate or spot someone in Europe.
1138 This is an example where you would use a line number (1 and 2 in this
1139 case), if you leave the digit out, the system assumes '1'. Digits
1140 '0'-'9' are available. This make it easier to see just what filters
1141 you have set. It also makes it more simple to remove individual
1142 filters, during a contest for example.
1145 You will notice in the above example that the second line has
1146 brackets. Look at the line logically. You can see there are 2
1147 separate sections to it. We are saying reject spots that are VHF or
1148 above APART from those in zones 14, 15 and 16 (either spotted there or
1149 originated there). If you did not have the brackets to separate the 2
1150 sections, then Spider would read it logically from the front and see a
1151 different expression entirely ...
1155 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
1159 The simple way to remember this is, if you use OR - use brackets.
1160 Whilst we are here CASE is not important. 'And BY_Zone' is just the
1161 same as 'and by_zone'.
1163 As mentioned earlier, setting several filters can be more flexible
1164 than simply setting one complex one. Doing it in this way means that
1165 if you want to alter your filter you can just redefine or remove one
1166 or more lines of it or one line. For example ...
1170 reject/spots 1 on hf/ssb
1174 would redefine our earlier example, or
1182 To remove all the filter lines in the spot filter ...
1190 10.3. Filter options
1192 You can filter in several different ways. The options are listed in
1193 the various helpfiles for accept, reject and filter.
1196 10.4. Advanced filtering
1198 Once you are happy with the results you get, you may like to
1202 The previous example that filters hf/cw spots and accepts vhf/uhf
1203 spots from EU can be written with a mixed filter, for example ...
1209 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
1213 Note that the first filter has not been specified with a number. This
1214 will automatically be assumed to be number 1. In this case, we have
1215 said reject all HF spots in the CW section of the bands but accept all
1216 others at HF. Also accept anything in VHF and above spotted in or by
1217 operators in the zones 14, 15 and 16. Each filter slot actually has a
1218 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
1222 It was mentioned earlier that after a reject test that doesn't match,
1223 the default for following tests is 'accept', the reverse is true for
1224 'accept'. In the example what happens is that the reject is executed
1225 first, any non hf/cw spot is passed to the accept line, which lets
1226 through everything else on HF. The next filter line lets through just
1227 VHF/UHF spots from EU.
1231 11. Hints, tips and common questions.
1233 Q.These commands seem very long! Can I shorten them?
1235 A.Of course you can and the usual abbreviations work. If you are
1238 Q.I am not sure if this command is correct. Can I cause any harm if I
1241 A.Do not be afraid to try a command to see if it will work, at the
1242 worst you will get an error message. If you require any help on a
1243 command, just type help followed by the command you want help on.
1244 Look at the "DXSpider Command Reference" section to see what help can
1247 Q.How should I use the announce command?
1249 A.With respect. Use the command by all means, but please only use the
1250 "full" extension if absolutely necessary. It can create a LOT of
1251 messages passing between clusters.
1253 Q.I like to be working in the shack while logged into the cluster but
1254 I can't be looking at the screen all the time. How can I be alerted
1255 when anything happens?
1257 A.Use the SET/BEEP command. You can find information on this in the
1258 "DXSpider Command Reference" section.
1260 Q.I got disconnected from the cluster and now I can't log back in
1261 again. What is wrong?
1263 A.Probably the cluster thinks you are still logged on and will not let
1264 you reconnect using the same call to prevent loops. Try logging on
1265 again adding an ssid to your callsign as DXSpider treats G0YLM and
1266 G0YLM-1 as different users.
1268 Q.How do I know if I have got the latest version of this user manual?
1270 A.The latest and greatest will always be on the Website. It will also
1271 be included with every release of DXSpider. As always, if unsure, ask
1272 your sysop what version number is the latest.
1278 accept Set a filter to accept something
1281 Create a filter to accept something
1283 There are 2 types of filter, accept and reject. See HELP FILTERING
1286 11.2. accept/announce [0-9] <pattern>
1288 accept/announce [0-9] <pattern> Set an 'accept' filter line for
1292 Create an 'accept this announce' line for a filter.
1294 An accept filter line means that if the announce matches this filter
1295 it is passed onto the user. See HELP FILTERING for more info. Please
1296 read this to understand how filters work - it will save a lot of grief
1299 You can use any of the following things in this line:-
1303 info <string> eg: iota or qsl
1304 by <prefixes> eg: G,M,2
1306 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1307 origin_itu <prefixes or numbers> or: G,GM,GW
1308 origin_zone <prefixes or numbers>
1309 origin_state <states> eg: VA,NH,RI,NH
1310 by_dxcc <prefixes or numbers>
1311 by_itu <prefixes or numbers>
1312 by_zone <prefixes or numbers>
1315 wx 1 filter WX announces
1316 dest <prefixes> eg: 6MUK,WDX (distros)
1325 acc/ann 2 by_zone 14,15,16
1326 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1341 acc/ann by_state va,nh,ri,nh
1345 You can use the tag 'all' to accept everything eg:
1353 but this probably for advanced users...
1355 11.3. accept/spots [0-9] <pattern>
1357 accept/spots [0-9] <pattern> Set an 'accept' filter line for spots
1360 Create an 'accept this spot' line for a filter.
1362 An accept filter line means that if the spot matches this filter it is
1363 passed onto the user. See HELP FILTERING for more info. Please read
1364 this to understand how filters work - it will save a lot of grief
1367 You can use any of the following things in this line:-
1371 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1372 on <range> same as 'freq'
1373 call <prefixes> eg: G,PA,HB9
1374 info <string> eg: iota or qsl
1376 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1377 call_itu <prefixes or numbers> or: G,GM,GW
1378 call_zone <prefixes or numbers>
1379 call_state <states> eg: VA,NH,RI,ME
1380 by_dxcc <prefixes or numbers>
1381 by_itu <prefixes or numbers>
1382 by_zone <prefixes or numbers>
1383 by_state <states> eg: VA,NH,RI,ME
1389 For frequencies, you can use any of the band names defined in
1390 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1391 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1392 this is more efficient than saying simply: freq HF (but don't get too
1400 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1404 You can use the tag 'all' to accept everything, eg:
1416 acc/spots by_state VA,NH,RI,MA,ME
1420 but this probably for advanced users...
1422 11.4. accept/wcy [0-9] <pattern>
1424 accept/wcy [0-9] <pattern> set an 'accept' WCY filter
1427 It is unlikely that you will want to do this, but if you do then you
1428 can filter on the following fields:-
1432 by <prefixes> eg: G,M,2
1434 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1435 origin_itu <prefixes or numbers> or: G,GM,GW
1436 origin_zone <prefixes or numbers>
1437 by_dxcc <prefixes or numbers>
1438 by_itu <prefixes or numbers>
1439 by_zone <prefixes or numbers>
1444 There are no examples because WCY Broadcasts only come from one place
1445 and you either want them or not (see UNSET/WCY if you don't want
1448 This command is really provided for future use.
1450 See HELP FILTER for information.
1452 11.5. accept/wwv [0-9] <pattern>
1454 accept/wwv [0-9] <pattern> set an 'accept' WWV filter
1457 It is unlikely that you will want to do this, but if you do then you
1458 can filter on the following fields:-
1462 by <prefixes> eg: G,M,2
1464 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1465 origin_itu <prefixes or numbers> or: G,GM,GW
1466 origin_zone <prefixes or numbers>
1467 by_dxcc <prefixes or numbers>
1468 by_itu <prefixes or numbers>
1469 by_zone <prefixes or numbers>
1478 accept/wwv by_zone 4
1482 is probably the only useful thing to do (which will only show WWV
1483 broadcasts by stations in the US).
1485 See HELP FILTER for information.
1487 11.6. announce <text>
1489 announce <text> Send an announcement to LOCAL users only
1492 <text> is the text of the announcement you wish to broadcast
1495 11.7. announce full <text>
1497 announce full <text> Send an announcement cluster wide
1500 This will send your announcement cluster wide
1502 11.8. apropos <string>
1504 apropos <string> Search help database for <string>
1507 Search the help database for <string> (it isn't case sensitive), and
1508 print the names of all the commands that may be relevant.
1510 11.9. blank [<string>] [<nn>]
1512 blank [<string>] [<nn>] Print nn (default 1) blank lines (or strings)
1515 In its basic form this command prints one or more blank lines. However
1516 if you pass it a string it will replicate the string for the width of
1517 the screen (default 80) and then print that one or more times, so:
1525 prints two blank lines
1533 prints a row of - characters once.
1541 prints 'abcabcabcabcabcabc....'
1543 This is really only of any use in a script file and you can print a
1548 bye Exit from the cluster
1551 This will disconnect you from the cluster
1553 11.11. chat <group> <text>
1555 chat <group> <text> Chat or Conference to a group
1558 It is now possible to JOIN a group and have network wide conferencing
1559 to that group. DXSpider does not (and probably will not) implement the
1560 AK1A conference mode as this seems very limiting, is hardly used and
1561 doesn't seem to work too well anyway.
1563 This system uses the existing ANN system and is compatible with both
1564 other DXSpider nodes and AK1A clusters (they use ANN/<group>).
1566 You can be a member of as many "groups" as you want. To join a group
1571 JOIN FOC (where FOC is the group name)
1575 To leave a group type:-
1583 You can see which groups you are in by typing:-
1591 and you can see whether your mate is in the group, if he connects to
1592 the same node as you, by typing:-
1600 To send a message to a group type:-
1604 CHAT FOC hello everyone
1612 CH #9000 hello I am back
1616 See also JOIN, LEAVE, SHOW/CHAT
1618 11.12. clear/announce [1|all]
1620 clear/announce [1|all] Clear a announce filter line
1623 This command allows you to clear (remove) a line in a annouce filter
1624 or to remove the whole filter.
1626 see CLEAR/SPOTS for a more detailed explanation.
1628 11.13. clear/route [1|all]
1630 clear/route [1|all] Clear a route filter line
1633 This command allows you to clear (remove) a line in a route filter or
1634 to remove the whole filter.
1636 see CLEAR/SPOTS for a more detailed explanation.
1638 11.14. clear/spots [0-9|all]
1640 clear/spots [0-9|all] Clear a spot filter line
1643 This command allows you to clear (remove) a line in a spot filter or
1644 to remove the whole filter.
1646 If you have a filter:-
1651 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1663 you will be left with:-
1667 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1679 the filter will be completely removed.
1681 11.15. clear/wcy [1|all]
1683 clear/wcy [1|all] Clear a WCY filter line
1686 This command allows you to clear (remove) a line in a WCY filter or to
1687 remove the whole filter.
1689 see CLEAR/SPOTS for a more detailed explanation.
1691 11.16. clear/wwv [1|all]
1693 clear/wwv [1|all] Clear a WWV filter line
1696 This command allows you to clear (remove) a line in a WWV filter or to
1697 remove the whole filter.
1699 see CLEAR/SPOTS for a more detailed explanation.
1703 dbavail Show a list of all the Databases in the system
1706 Title says it all really, this command lists all the databases defined
1707 in the system. It is also aliased to SHOW/COMMAND.
1709 11.18. dbshow <dbname> <key>
1711 dbshow <dbname> <key> Display an entry, if it exists, in a database
1714 This is the generic user interface to the database to the database
1715 system. It is expected that the sysop will add an entry to the local
1716 Aliases file so that users can use the more familiar AK1A style of
1725 but if he hasn't and the database really does exist (use DBAVAIL or
1726 SHOW/COMMAND to find out) you can do the same thing with:
1736 directory List messages
1740 11.20. directory <from>-<to>
1742 directory <from>-<to> List messages <from> message <to> message
1745 List the messages in the messages directory.
1747 If there is a 'p' one space after the message number then it is a
1748 personal message. If there is a '-' between the message number and the
1750 You can use shell escape characters such as '*' and '?' in the <call>
1753 You can combine some of the various directory commands together eg:-
1764 DIR SUBJECT IOTA 200-250
1768 You can abbreviate all the commands to one letter and use ak1a
1778 11.21. directory <nn>
1780 directory <nn> List last <nn> messages
1784 11.22. directory all
1786 directory all List all messages
1790 11.23. directory from <call>
1792 directory from <call> List all messages from <call>
1796 11.24. directory new
1798 directory new List all new messages
1802 11.25. directory own
1804 directory own List your own messages
1808 11.26. directory subject <string>
1810 directory subject <string> List all messages with <string> in subject
1814 11.27. directory to <call>
1816 directory to <call> List all messages to <call>
1820 11.28. dx [by <call>] <freq> <call> <remarks>
1822 dx [by <call>] <freq> <call> <remarks> Send a DX spot
1825 This is how you send a DX Spot to other users. You can, in fact, now
1826 enter the <freq> and the <call> either way round.
1836 will all give the same result. You can add some remarks to the end of
1837 the command and they will be added to the spot.
1841 DX FR0G 144600 this is a test
1845 You can credit someone else by saying:-
1849 DX by G1TLH FR0G 144.600 he isn't on the cluster
1853 The <freq> is compared against the available bands set up in the
1854 cluster. See SHOW/BANDS for more information.
1858 echo <line> Echo the line to the output
1861 This command is useful in scripts and so forth for printing the line
1862 that you give to the command to the output. You can use this in
1863 user_default scripts and the SAVE command for titling and so forth
1865 The script will interpret certain standard "escape" sequences as
1870 \t - becomes a TAB character (0x09 in ascii)
1871 \a - becomes a BEEP character (0x07 in ascii)
1872 \n - prints a new line
1876 So the following example:-
1880 echo GB7DJK is a dxcluster
1888 GB7DJK is a dxcluster
1892 on the output. You don't need a \n on the end of the line you want to
1895 A more complex example:-
1899 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
1918 filtering... Filtering things in DXSpider
1921 There are a number of things you can filter in the DXSpider system.
1922 They all use the same general mechanism.
1924 In general terms you can create a 'reject' or an 'accept' filter which
1925 can have up to 10 lines in it. You do this using, for example:-
1931 where ..... are the specific commands for that type of filter. There
1932 are filters for spots, wwv, announce, wcy and (for sysops) connects.
1933 See each different accept or reject command reference for more
1936 There is also a command to clear out one or more lines in a filter and
1937 one to show you what you have set. They are:-
1954 There is clear/xxxx command for each type of filter.
1956 For now we are going to use spots for the examples, but you can apply
1957 the principles to all types of filter.
1959 There are two main types of filter 'accept' or 'reject'; which you use
1960 depends entirely on how you look at the world and what is least
1961 writing to achieve what you want. Each filter has 10 lines (of any
1962 length) which are tried in order. If a line matches then the action
1963 you have specified is taken (ie reject means ignore it and accept
1966 The important thing to remember is that if you specify a 'reject'
1967 filter (all the lines in it say 'reject/spots' (for instance)) then if
1968 a spot comes in that doesn't match any of the lines then you will get
1969 it BUT if you specify an 'accept' filter then any spots that don't
1970 match are dumped. For example if I have a one line accept filter:-
1974 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1978 then automatically you will ONLY get VHF spots from or to CQ zones 14
1979 15 and 16. If you set a reject filter like:
1983 reject/spots on hf/cw
1987 Then you will get everything EXCEPT HF CW spots, If you am interested
1988 in IOTA and will work it even on CW then you could say:-
1992 reject/spots on hf/cw and not info iota
1996 But in that case you might only be interested in iota and say:-
2000 accept/spots not on hf/cw or info iota
2004 which is exactly the same. You should choose one or the other until
2005 you are confortable with the way it works. Yes, you can mix them
2006 (actually you can have an accept AND a reject on the same line) but
2007 don't try this at home until you can analyse the results that you get
2008 without ringing up the sysop for help.
2010 Another useful addition now is filtering by US state
2014 accept/spots by_state VA,NH,RI,ME
2018 You can arrange your filter lines into logical units, either for your
2019 own understanding or simply convenience. I have one set frequently:-
2023 reject/spots 1 on hf/cw
2024 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
2028 What this does is to ignore all HF CW spots (being a class B I can't
2029 read any CW and couldn't possibly be interested in HF :-) and also
2030 rejects any spots on VHF which don't either originate or spot someone
2033 This is an exmaple where you would use the line number (1 and 2 in
2034 this case), if you leave the digit out, the system assumes '1'. Digits
2036 You can leave the word 'and' out if you want, it is implied. You can
2037 use any number of brackets to make the 'expression' as you want it.
2038 There are things called precedence rules working here which mean that
2039 you will NEED brackets in a situation like line 2 because, without it,
2044 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
2048 annoying, but that is the way it is. If you use OR - use brackets.
2049 Whilst we are here CASE is not important. 'And BY_Zone' is just 'and
2052 If you want to alter your filter you can just redefine one or more
2053 lines of it or clear out one line. For example:-
2057 reject/spots 1 on hf/ssb
2069 To remove the filter in its entirty:-
2077 There are similar CLEAR commands for the other filters:-
2089 Once you are happy with the results you get, you may like to
2092 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
2093 can be written with a mixed filter, eg:
2099 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
2103 each filter slot actually has a 'reject' slot and an 'accept' slot.
2104 The reject slot is executed BEFORE the accept slot.
2106 It was mentioned earlier that after a reject test that doesn't match,
2107 the default for following tests is 'accept', the reverse is true for
2108 first, any non hf/cw spot is passed to the accept line, which lets
2109 thru everything else on HF.
2111 The next filter line lets through just VHF/UHF spots from EU.
2115 help The HELP Command
2118 HELP is available for a number of commands. The syntax is:-
2126 Where <cmd> is the name of the command you want help on.
2128 All commands can be abbreviated, so SHOW/DX can be abbreviated to
2129 SH/DX, ANNOUNCE can be shortened to AN and so on.
2131 Look at the APROPOS <string> command which will search the help
2132 database for the <string> you specify and give you a list of likely
2133 commands to look at with HELP.
2137 join <group> Join a chat or conference group
2140 JOIN allows you to join a network wide conference group. To join a
2141 group (called FOC in this case) type:-
2149 See also CHAT, LEAVE, SHOW/CHAT
2151 11.33. kill <from msgno>-<to msgno>
2153 kill <from msgno>-<to msgno> Delete a range of messages
2157 11.34. kill <msgno> [<msgno..]
2159 kill <msgno> [<msgno..] Delete a message from the local system
2163 11.35. kill <msgno> [<msgno> ...]
2165 kill <msgno> [<msgno> ...] Remove or erase a message from the system
2168 You can get rid of any message to or originating from your callsign
2169 using this command. You can remove more than one message at a time.
2173 11.36. kill from <regex>
2175 kill from <regex> Delete messages FROM a callsign or pattern
2179 11.37. kill to <regex>
2181 kill to <regex> Delete messages TO a callsign or pattern
2185 11.38. leave <group>
2187 leave <group> Leave a chat or conference group
2190 LEAVE allows you to leave a network wide conference group. To leave a
2191 group (called FOC in this case) type:-
2199 See also CHAT, JOIN, SHOW/CHAT
2203 links Show which nodes is physically connected
2206 This is a quick listing that shows which links are connected and some
2207 information about them. See WHO for a list of all connections.
2211 read Read the next unread personal message addressed to you
2217 read <msgno> Read the specified message
2220 You can read any messages that are sent as 'non-personal' and also any
2221 message either sent by or sent to your callsign.
2225 reject Set a filter to reject something
2228 Create a filter to reject something
2230 There are 2 types of filter, accept and reject. See HELP FILTERING
2233 11.43. reject/announce [0-9] <pattern>
2235 reject/announce [0-9] <pattern> Set a 'reject' filter line for
2238 Create an 'reject this announce' line for a filter.
2240 A reject filter line means that if the announce matches this filter it
2241 is passed onto the user. See HELP FILTERING for more info. Please read
2242 this to understand how filters work - it will save a lot of grief
2245 You can use any of the following things in this line:-
2249 info <string> eg: iota or qsl
2250 by <prefixes> eg: G,M,2
2252 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2253 origin_itu <prefixes or numbers> or: G,GM,GW
2254 origin_zone <prefixes or numbers>
2255 origin_state <states> eg: VA,NH,RI,ME
2256 by_dxcc <prefixes or numbers>
2257 by_itu <prefixes or numbers>
2258 by_zone <prefixes or numbers>
2259 by_state <states> eg: VA,NH,RI,ME
2261 wx 1 filter WX announces
2262 dest <prefixes> eg: 6MUK,WDX (distros)
2270 rej/ann by_zone 14,15,16 and not by G,M,2
2274 You can use the tag 'all' to reject everything eg:
2282 but this probably for advanced users...
2284 11.44. reject/spots [0-9] <pattern>
2286 reject/spots [0-9] <pattern> Set a 'reject' filter line for spots
2289 Create a 'reject this spot' line for a filter.
2291 A reject filter line means that if the spot matches this filter it is
2292 dumped (not passed on). See HELP FILTERING for more info. Please read
2293 this to understand how filters work - it will save a lot of grief
2296 You can use any of the following things in this line:-
2300 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
2301 on <range> same as 'freq'
2302 call <prefixes> eg: G,PA,HB9
2303 info <string> eg: iota or qsl
2305 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2306 call_itu <prefixes or numbers> or: G,GM,GW
2307 call_zone <prefixes or numbers>
2308 call_state <states> eg: VA,NH,RI,ME
2309 by_dxcc <prefixes or numbers>
2310 by_itu <prefixes or numbers>
2311 by_zone <prefixes or numbers>
2312 by_state <states> eg: VA,NH,RI,ME
2318 For frequencies, you can use any of the band names defined in
2319 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
2320 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
2321 this is more efficient than saying simply: on HF (but don't get too
2329 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
2333 You can use the tag 'all' to reject everything eg:
2341 but this probably for advanced users...
2343 11.45. reject/wcy [0-9] <pattern>
2345 reject/wcy [0-9] <pattern> set a 'reject' WCY filter
2348 It is unlikely that you will want to do this, but if you do then you
2349 can filter on the following fields:-
2353 by <prefixes> eg: G,M,2
2355 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2356 origin_itu <prefixes or numbers> or: G,GM,GW
2357 origin_zone <prefixes or numbers>
2358 by_dxcc <prefixes or numbers>
2359 by_itu <prefixes or numbers>
2360 by_zone <prefixes or numbers>
2365 There are no examples because WCY Broadcasts only come from one place
2366 and you either want them or not (see UNSET/WCY if you don't want
2369 This command is really provided for future use.
2371 See HELP FILTER for information.
2373 11.46. reject/wwv [0-9] <pattern>
2375 reject/wwv [0-9] <pattern> set a 'reject' WWV filter
2378 It is unlikely that you will want to do this, but if you do then you
2379 can filter on the following fields:-
2383 by <prefixes> eg: G,M,2
2385 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
2386 origin_itu <prefixes or numbers> or: G,GM,GW
2387 origin_zone <prefixes or numbers>
2388 by_dxcc <prefixes or numbers>
2389 by_itu <prefixes or numbers>
2390 by_zone <prefixes or numbers>
2399 reject/wwv by_zone 14,15,16
2403 is probably the only useful thing to do (which will only show WWV
2404 broadcasts by stations in the US).
2406 See HELP FILTER for information.
2410 reply Reply (privately) to the last message that you have read
2414 11.48. reply <msgno>
2416 reply <msgno> Reply (privately) to the specified message
2420 11.49. reply b <msgno>
2422 reply b <msgno> Reply as a Bulletin to the specified message
2426 11.50. reply noprivate <msgno>
2428 reply noprivate <msgno> Reply as a Bulletin to the specified message
2432 11.51. reply rr <msgno>
2434 reply rr <msgno> Reply to the specified message with read receipt
2437 You can reply to a message and the subject will automatically have
2438 "Re:" inserted in front of it, if it isn't already present.
2440 You can also use all the extra qualifiers such as RR, PRIVATE,
2441 NOPRIVATE, B that you can use with the SEND command (see SEND for
2444 11.52. send <call> [<call> ...]
2446 send <call> [<call> ...] Send a message to one or more callsigns
2450 11.53. send copy <msgno> <call>
2452 send copy <msgno> <call> Send a copy of a message to someone
2456 11.54. send noprivate <call>
2458 send noprivate <call> Send a message to all stations
2461 All the SEND commands will create a message which will be sent either
2462 to an individual callsign or to one of the 'bulletin' addresses.
2464 SEND <call> on its own acts as though you had typed SEND PRIVATE, that
2465 is it will mark the message as personal and send it to the cluster
2466 node that that callsign is connected to. If the <call> you have
2467 specified is in fact a known bulletin category on your node (eg: ALL)
2468 then the message should automatically become a bulletin.
2470 You can have more than one callsign in all of the SEND commands.
2472 You can have multiple qualifiers so that you can have for example:-
2476 SEND RR COPY 123 PRIVATE G1TLH G0RDI
2480 which should send a copy of message 123 to G1TLH and G0RDI and you
2481 will receive a read receipt when they have read the message.
2483 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
2484 is an alias for SEND PRIVATE
2486 The system will ask you for a subject. Conventionally this should be
2487 no longer than 29 characters for compatibility. Most modern cluster
2488 software should accept more.
2490 You will now be prompted to start entering your text.
2492 You finish the message by entering '/EX' on a new line. For instance:
2503 If you have started a message and you don't want to keep it then you
2504 can abandon the message with '/ABORT' on a new line, like:-
2510 oh I just can't be bothered with this
2515 If you abort the message it will NOT be sent.
2517 When you are entering the text of your message, most normal output
2518 (such as DX announcements and so on are suppressed and stored for
2519 latter display (upto 20 such lines are stored, as new ones come along,
2520 so the oldest lines are dropped).
2522 Also, you can enter normal commands commands (and get the output
2523 immediately) whilst in the middle of a message. You do this by typing
2524 the command preceeded by a '/' character on a new line, so:-
2528 /dx g1tlh 144010 strong signal
2532 Will issue a dx annoucement to the rest of the cluster.
2534 Also, you can add the output of a command to your message by
2535 preceeding the command with '//', thus :-
2543 This will show YOU the output from SH/VHFTABLE and also store it in
2546 You can carry on with the message until you are ready to send it.
2548 11.55. send private <call>
2550 send private <call> Send a personal message
2554 11.56. send rr <call>
2556 send rr <call> Send a message and ask for a read receipt
2560 11.57. set/address <your address>
2562 set/address <your address> Record your postal address
2568 set/announce Allow announce messages to come out on your terminal
2574 set/anntalk Allow talk like announce messages on your terminal
2580 set/beep Add a beep to DX and other messages on your terminal
2586 set/dx Allow DX messages to come out on your terminal
2592 set/dxcq Show CQ Zones on the end of DX announcements
2598 set/dxgrid Allow QRA Grid Squares on the end of DX announcements
2604 set/dxitu Show ITU Zones on the end of DX announcements
2610 set/echo Make the cluster echo your input
2614 11.66. set/email <email> ...
2616 set/email <email> ... Set email address(es) and forward your personals
2622 set/here Tell the system you are present at your terminal
2626 11.68. set/homenode <node>
2628 set/homenode <node> Set your normal cluster callsign
2631 Tell the cluster system where you normally connect to. Any Messages
2632 sent to you will normally find their way there should you not be
2640 11.69. set/language <lang>
2642 set/language <lang> Set the language you want to use
2645 You can select the language that you want the cluster to use.
2646 Currently the languages available are en (English), de (German), es
2647 (Spanish) and nl (Dutch).
2649 11.70. set/location <lat & long>
2651 set/location <lat & long> Set your latitude and longitude
2655 11.71. set/logininfo
2657 set/logininfo Inform when a station logs in locally
2661 11.72. set/name <your name>
2663 set/name <your name> Set your name
2666 Tell the system what your name is eg:-
2672 11.73. set/page <lines per page>
2674 set/page <lines per page> Set the lines per page
2677 Tell the system how many lines you wish on a page when the number of
2678 line of output from a command is more than this. The default is 20.
2679 Setting it explicitly to 0 will disable paging.
2687 The setting is stored in your user profile.
2691 set/password Set your own password
2694 This command only works for a 'telnet' user (currently). It will only
2695 work if you have a password already set. This initial password can
2696 only be set by the sysop.
2698 When you execute this command it will ask you for your old password,
2699 then ask you to type in your new password twice (to make sure you get
2700 it right). You may or may not see the data echoed on the screen as you
2701 type, depending on the type of telnet client you have.
2703 11.75. set/prompt <string>
2705 set/prompt <string> Set your prompt to <string>
2709 11.76. set/qra <locator>
2711 set/qra <locator> Set your QRA Grid locator
2714 Tell the system what your QRA (or Maidenhead) locator is. If you have
2715 not done a SET/LOCATION then your latitude and longitude will be set
2716 roughly correctly (assuming your locator is correct ;-). For example:-
2723 11.77. set/qth <your qth>
2725 set/qth <your qth> Set your QTH
2728 Tell the system where you are. For example:-
2731 SET/QTH East Dereham, Norfolk
2737 set/talk Allow TALK messages to come out on your terminal
2743 set/usstate Allow US State info on the end of DX announcements
2749 set/wcy Allow WCY messages to come out on your terminal
2755 set/wwv Allow WWV messages to come out on your terminal
2761 set/wx Allow WX messages to come out on your terminal
2765 11.83. show/chat [<group>] [<lines>]
2767 show/chat [<group>] [<lines>] Show any chat or conferencing
2770 This command allows you to see any chat or conferencing that has
2771 occurred whilst you were away. SHOW/CHAT on its own will show data for
2772 all groups. If you use a group name then it will show only chat for
2775 11.84. show/configuration [<node>]
2777 show/configuration [<node>] Show all the nodes and users visible
2780 This command allows you to see all the users that can be seen and the
2781 nodes to which they are connected.
2783 This command is normally abbreviated to: sh/c
2785 Normally, the list returned will be just for the nodes from your
2786 country (because the list otherwise will be very long).
2794 will produce a complete list of all nodes.
2796 BE WARNED: the list that is returned can be VERY long
2798 It is possible to supply a node or part of a prefix and you will get a
2799 list of the users for that node or list of nodes starting with that
2812 11.85. show/configuration/node
2814 show/configuration/node Show all the nodes connected locally
2817 Show all the nodes connected to this node.
2819 11.86. show/contest <year and month>
2821 show/contest <year and month> Show all the contests for a month
2824 Show all known contests which are maintained at
2825 http://www.sk3bg.se/contest/ for a particular month or year. The
2826 format is reasonably flexible. For example:-
2835 11.87. show/date [<prefix>|<callsign>]
2837 show/date [<prefix>|<callsign>] Show the local time
2840 This is very nearly the same as SHOW/TIME, the only difference the
2841 format of the date string if no arguments are given.
2843 If no prefixes or callsigns are given then this command returns the
2844 local time and UTC as the computer has it right now. If you give some
2845 prefixes then it will show UTC and UTC + the local offset (not
2846 including DST) at the prefixes or callsigns that you specify.
2848 11.88. show/db0sdx <callsign>
2850 show/db0sdx <callsign> Show QSL infomation from DB0SDX database
2853 This command queries the DB0SDX QSL server on the internet and returns
2854 any information available for that callsign. This service is provided
2855 for users of this software by http://www.qslinfo.de.
2857 See also SHOW/QRZ, SHOW/WM7D.
2861 show/dx Interrogate the spot database
2864 If you just type SHOW/DX you will get the last so many spots (sysop
2865 configurable, but usually 10).
2867 In addition you can add any number of these commands in very nearly
2868 any order to the basic SHOW/DX command, they are:-
2872 on <band> - eg 160m 20m 2m 23cm 6mm
2873 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2874 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
2879 <number> - the number of spots you want
2880 <from>-<to> - <from> spot no <to> spot no in the selected list
2885 <prefix> - for a spotted callsign beginning with <prefix>
2886 *<suffix> - for a spotted callsign ending in <suffix>
2887 *<string>* - for a spotted callsign containing <string>
2891 day <number> - starting <number> days ago
2892 day <from>-<to> - <from> days <to> days ago
2897 info <text> - any spots containing <text> in the info or remarks
2901 by <call> - any spots spotted by <call> (spotter <call> is the
2906 qsl - this automatically looks for any qsl info on the call
2907 held in the spot database.
2911 iota [<iota>] - If the iota island number is missing it will look for
2912 the string iota and anything which looks like an iota
2913 island number. If you specify then it will look for
2918 qra [<locator>] - this will look for the specific locator if you specify
2919 one or else anything that looks like a locator.
2923 dxcc - treat the prefix as a 'country' and look for spots
2924 from that country regardless of actual prefix.
2929 You can also use this with the 'by' keyword so
2939 SH/DX on 20m info iota
2940 SH/DX 9a on vhf day 30
2946 SH/DX dxcc oq2 by w dxcc
2950 11.90. show/dxcc <prefix>
2952 show/dxcc <prefix> Interrogate the spot database by country
2955 This command takes the <prefix> (which can be a full or partial
2956 callsign if desired), looks up which internal country number it is and
2957 then displays all the spots as per SH/DX for that country.
2959 This is now an alias for 'SHOW/DX DXCC'
2961 The options for SHOW/DX also apply to this command. e.g.
2966 SH/DXCC W on 20m iota
2970 This can be done with the SHOW/DX command like this:-
2975 SH/DX dxcc w on 20m iota
2979 11.91. show/dxqsl <callsign>
2981 show/dxqsl <callsign> Show any QSL info gathered from spots
2984 The node collects information from the comment fields in spots (things
2985 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
2987 This command allows you to interrogate that database and if the
2988 callsign is found will display the manager(s) that people have
2989 spotted. This information is NOT reliable, but it is normally
2990 reasonably accurate if it is spotted enough times.
3000 You can check the raw input spots yourself with:-
3008 This gives you more background information.
3011 11.92. show/dxstats [days] [date]
3013 show/dxstats [days] [date] Show the DX Statistics
3016 Show the total DX spots for the last <days> no of days (default is
3017 31), starting from a <date> (default: today).
3019 11.93. show/files [<filearea> [<string>]]
3021 show/files [<filearea> [<string>]] List the contents of a filearea
3024 SHOW/FILES on its own will show you a list of the various fileareas
3025 available on the system. To see the contents of a particular file area
3033 where <filearea> is the name of the filearea you want to see the con-
3036 You can also use shell globbing characters like '*' and '?' in a
3037 string to see a selection of files in a filearea eg:-
3040 SH/FILES bulletins arld*
3044 See also TYPE - to see the contents of a file.
3048 show/filter Show the contents of all the filters you have set
3051 Show the contents of all the filters that are set. This command
3052 displays all the filters set - for all the various categories.
3054 11.95. show/hfstats [days] [date]
3056 show/hfstats [days] [date] Show the HF DX Statistics
3059 Show the HF DX spots breakdown by band for the last <days> no of days
3060 (default is 31), starting from a <date> (default: today).
3062 11.96. show/hftable [days] [date] [prefix ...]
3064 show/hftable [days] [date] [prefix ...] Show the HF DX Spotter Table
3067 Show the HF DX Spotter table for the list of prefixes for the last
3068 <days> no of days (default is 31), starting from a <date> (default:
3071 If there are no prefixes then it will show the table for your country.
3073 Remember that some countries have more than one "DXCC country" in them
3074 (eg G :-), to show them (assuming you are not in G already which is
3075 specially treated in the code) you must list all the relevant prefixes
3079 sh/hftable g gm gd gi gj gw gu
3083 Note that the prefixes are converted into country codes so you don't
3084 have to list all possible prefixes for each country.
3086 If you want more or less days than the default simply include the
3087 number you require:-
3095 If you want to start at a different day, simply add the date in some
3100 sh/hftable 2 25nov02
3101 sh/hftable 2 25-nov-02
3103 sh/hftable 2 25/11/02
3107 This will show the stats for your DXCC for that CQWW contest weekend.
3109 You can specify either prefixes or full callsigns (so you can see how
3110 you did against all your mates). You can also say 'all' which will
3111 then print the worldwide statistics.
3119 11.97. show/moon [ndays] [<prefix>|<callsign>]
3121 show/moon [ndays] [<prefix>|<callsign>] Show Moon rise and set times
3124 Show the Moon rise and set times for a (list of) prefixes or
3125 callsigns, together with the azimuth and elevation of the sun
3126 currently at those locations.
3128 If you don't specify any prefixes or callsigns, it will show the times
3129 for your QTH (assuming you have set it with either SET/LOCATION or
3130 SET/QRA), together with the current azimuth and elevation.
3132 In addition, it will show the illuminated fraction of the moons disk.
3134 If all else fails it will show the Moonrise and set times for the node
3135 that you are connected to.
3145 You can also use this command to see into the past or the future, so
3146 if you want to see yesterday's times then do:-
3154 or in three days time:-
3162 Upto 366 days can be checked both in the past and in the future.
3164 Please note that the rise and set times are given as the UT times of
3165 rise and set on the requested UT day.
3167 11.98. show/muf <prefix> [<hours>][long]
3169 show/muf <prefix> [<hours>][long] Show the likely propagation to a
3173 This command allow you to estimate the likelihood of you contacting a
3174 station with the prefix you have specified. The output assumes a
3175 modest power of 20dBW and receiver sensitivity of -123dBm (about
3178 The result predicts the most likely operating frequencies and signal
3179 levels for high frequency (shortwave) radio propagation paths on
3180 specified days of the year and hours of the day. It is most useful for
3181 paths between 250 km and 6000 km, but can be used with reduced
3182 accuracy for paths shorter or longer than this.
3184 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
3185 used to predict the MUF given the predicted flux, day of the year,
3186 hour of the day and geographic coordinates of the transmitter and
3187 receiver. This routine is reasonably accurate for the purposes here,
3188 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
3189 than the programs used by major shortwave broadcasting organizations,
3190 such as the Voice of America.
3192 The command will display some header information detailing its
3193 assumptions, together with the locations, latitude and longitudes and
3194 bearings. It will then show UTC (UT), local time at the other end
3195 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
3196 (Zen) and the likely signal strengths. Then for each frequency for
3197 which the system thinks there is a likelihood of a circuit it prints a
3199 The value is currently a likely S meter reading based on the
3200 conventional 6dB / S point scale. If the value has a '+' appended it
3201 means that it is 1/2 an S point stronger. If the value is preceeded by
3202 an 'm' it means that there is likely to be much fading and by an 's'
3203 that the signal is likely to be noisy.
3205 By default SHOW/MUF will show the next two hours worth of data. You
3206 can specify anything up to 24 hours worth of data by appending the no
3207 of hours required after the prefix. For example:-
3219 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
3220 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
3221 Location Lat / Long Azim
3222 East Dereham, Norfolk 52 41 N 0 57 E 47
3223 United-States-W 43 0 N 87 54 W 299
3224 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
3225 18 23 11.5 -35 mS0+ mS2 S3
3226 19 0 11.2 -41 mS0+ mS2 S3
3230 indicating that you will have weak, fading circuits on top band and
3231 80m but usable signals on 40m (about S3).
3241 will get you the above display, but with the next 24 hours worth of
3251 Gives you an estimate of the long path propagation characterics. It
3252 should be noted that the figures will probably not be very useful, nor
3253 terrible accurate, but it is included for completeness.
3255 11.99. show/newconfiguration [<node>]
3257 show/newconfiguration [<node>] Show all the nodes and users visible
3261 This command allows you to see all the users that can be seen and the
3262 nodes to which they are connected.
3264 This command produces essentially the same information as
3265 SHOW/CONFIGURATION except that it shows all the duplication of any
3266 routes that might be present It also uses a different format which may
3267 not take up quite as much space if you don't have any loops.
3269 BE WARNED: the list that is returned can be VERY long
3271 11.100. show/newconfiguration/node
3273 show/newconfiguration/node Show all the nodes connected locally
3276 Show all the nodes connected to this node in the new format.
3278 11.101. show/prefix <callsign>
3280 show/prefix <callsign> Interrogate the prefix database
3283 This command takes the <callsign> (which can be a full or partial
3284 callsign or a prefix), looks up which internal country number it is
3285 and then displays all the relevant prefixes for that country together
3286 with the internal country no, the CQ and ITU regions.
3290 11.102. show/qra <lat> <long>
3292 show/qra <lat> <long> Convert lat/long to a QRA Grid locator
3295 This is a multipurpose command that allows you either to calculate the
3296 distance and bearing between two locators or (if only one locator is
3297 given on the command line) the distance and beraing from your station
3298 to the locator. For example:-
3307 The first example will show the distance and bearing to the locator
3308 from yourself, the second example will calculate the distance and
3309 bearing from the first locator to the second. You can use 4 or 6
3312 It is also possible to convert a latitude and longitude to a locator
3313 by using this command with a latitude and longitude as an argument,
3318 SH/QRA 52 41 N 0 58 E
3322 11.103. show/qra <locator> [<locator>]
3324 show/qra <locator> [<locator>] Show distance between QRA Grid locators
3328 11.104. show/qrz <callsign>
3330 show/qrz <callsign> Show any callbook details on a callsign
3333 This command queries the QRZ callbook server on the internet and
3334 returns any information available for that callsign. This service is
3335 provided for users of this software by http://www.qrz.com
3337 See also SHOW/WM7D for an alternative.
3339 11.105. show/route <callsign> ...
3341 show/route <callsign> ... Show the route to the callsign
3344 This command allows you to see to which node the callsigns specified
3345 are connected. It is a sort of inverse sh/config.
3353 11.106. show/satellite <name> [<hours> <interval>]
3355 show/satellite <name> [<hours> <interval>] Show tracking data
3358 Show the tracking data from your location to the satellite of your
3359 choice from now on for the next few hours.
3361 If you use this command without a satellite name it will display a
3362 list of all the satellites known currently to the system.
3364 If you give a name then you can obtain tracking data of all the passes
3365 that start and finish 5 degrees below the horizon. As default it will
3366 give information for the next three hours for every five minute
3369 You can alter the number of hours and the step size, within certain
3372 Each pass in a period is separated with a row of '-----' characters
3379 SH/SAT FENGYUN1 12 2
3383 11.107. show/station [<callsign> ..]
3385 show/station [<callsign> ..] Show information about a callsign
3388 Show the information known about a callsign and whether (and where)
3389 that callsign is connected to the cluster.
3397 If no callsign is given then show the information for yourself.
3399 11.108. show/sun [ndays] [<prefix>|<callsign>]
3401 show/sun [ndays] [<prefix>|<callsign>] Show sun rise and set times
3404 Show the sun rise and set times for a (list of) prefixes or callsigns,
3405 together with the azimuth and elevation of the sun currently at those
3408 If you don't specify any prefixes or callsigns, it will show the times
3409 for your QTH (assuming you have set it with either SET/LOCATION or
3410 SET/QRA), together with the current azimuth and elevation.
3412 If all else fails it will show the sunrise and set times for the node
3413 that you are connected to.
3420 SH/SUN G1TLH K9CW ZS
3424 You can also use this command to see into the past or the future, so
3425 if you want to see yesterday's times then do:-
3433 or in three days time:-
3441 Upto 366 days can be checked both in the past and in the future.
3443 Please note that the rise and set times are given as the UT times of
3444 rise and set on the requested UT day.
3445 11.109. show/time [<prefix>|<callsign>]
3447 show/time [<prefix>|<callsign>] Show the local time
3450 If no prefixes or callsigns are given then this command returns the
3451 local time and UTC as the computer has it right now. If you give some
3452 prefixes then it will show UTC and UTC + the local offset (not
3453 including DST) at the prefixes or callsigns that you specify.
3455 11.110. show/usdb [call ..]
3457 show/usdb [call ..] Show information held on the FCC Call database
3460 Show the City and State of a Callsign held on the FCC database if his
3461 is being run on this system, eg:-
3469 11.111. show/vhfstats [days] [date]
3471 show/vhfstats [days] [date] Show the VHF DX Statistics
3474 Show the VHF DX spots breakdown by band for the last <days> no of days
3475 (default is 31), starting from a date (default: today).
3477 11.112. show/vhftable [days] [date] [prefix ...]
3479 show/vhftable [days] [date] [prefix ...] Show the VHF DX Spotter Table
3482 Show the VHF DX Spotter table for the list of prefixes for the last
3483 <days> no of days (default is 31), starting from a date (default:
3486 If there are no prefixes then it will show the table for your country.
3488 Remember that some countries have more than one "DXCC country" in them
3489 (eg G :-), to show them (assuming you are not in G already which is
3490 specially treated in the code) you must list all the relevant prefixes
3494 sh/vhftable g gm gd gi gj gw gu
3498 Note that the prefixes are converted into country codes so you don't
3499 have to list all possible prefixes for each country.
3501 If you want more or less days than the default simply include the
3502 number you require:-
3508 If you want to start at a different day, simply add the date in some
3513 sh/vhftable 2 25nov02
3514 sh/vhftable 2 25-nov-02
3515 sh/vhftable 2 021125
3516 sh/vhftable 2 25/11/02
3520 This will show the stats for your DXCC for that CQWW contest weekend.
3522 You can specify either prefixes or full callsigns (so you can see how
3523 you did against all your mates). You can also say 'all' which will
3524 then print the worldwide statistics.
3534 show/wcy Show last 10 WCY broadcasts
3538 11.114. show/wcy <n>
3540 show/wcy <n> Show last <n> WCY broadcasts
3543 Display the most recent WCY information that has been received by the
3547 11.115. show/wm7d <callsign>
3549 show/wm7d <callsign> Show callbook details on a US callsigns
3552 This command queries the WM7D callbook server on the internet and
3553 returns any information available for that US callsign. This service
3554 is provided for users of this software by http://www.wm7d.net.
3560 show/wwv Show last 10 WWV broadcasts
3564 11.117. show/wwv <n>
3566 show/wwv <n> Show last <n> WWV broadcasts
3569 Display the most recent WWV information that has been received by the
3573 sysop Regain your privileges if you login remotely
3576 The system automatically reduces your privilege level to that of a
3577 normal user if you login in remotely. This command allows you to
3578 regain your normal privilege level. It uses the normal system: five
3579 numbers are returned that are indexes into the character array that is
3580 your assigned password (see SET/PASSWORD). The indexes start from
3583 You are expected to return a string which contains the characters
3584 required in the correct order. You may intersperse those characters
3585 with others to obscure your reply for any watchers. For example (and
3586 these values are for explanation :-):
3590 password = 012345678901234567890123456789
3599 aa2bbbb0ccc5ddd7xxx3n
3605 They will all match. If there is no password you will still be offered
3606 numbers but nothing will happen when you input a string. Any match is
3609 11.119. talk <call> > <node> [<text>]
3611 talk <call> > <node> [<text>] Send a text message to another station
3615 Send a short message to any other station that is visible on the
3616 cluster system. You can send it to anyone you can see with a
3617 SHOW/CONFIGURATION command, they don't have to be connected locally.
3619 The second form of TALK is used when other cluster nodes are connected
3620 with restricted information. This usually means that they don't send
3621 the user information usually associated with logging on and off the
3624 If you know that G3JNB is likely to be present on GB7TLH, but you can
3625 only see GB7TLH in the SH/C list but with no users, then you would use
3626 the second form of the talk message.
3628 If you want to have a ragchew with someone you can leave the text
3629 message out and the system will go into 'Talk' mode. What this means
3630 is that a short message is sent to the recipient telling them that you
3631 are in a go to the station that you asked for.
3633 All the usual announcements, spots and so on will still come out on
3635 If you want to do something (such as send a spot) you preceed the
3636 normal command with a '/' character, eg:-
3640 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
3645 To leave talk mode type:
3653 If you are in 'Talk' mode, there is an extention to the '/' command
3654 which allows you to send the output to all the people you are talking
3655 to. You do with the '//' command. For example:-
3663 will send the hftable as you have it to all the people you are
3664 currently talking to.
3666 11.120. talk <call> [<text>]
3668 talk <call> [<text>] Send a text message to another station
3672 11.121. type <filearea>/<name>
3674 type <filearea>/<name> Look at the contents of a file in one of the
3678 Type out the contents of a file in a filearea. So, for example, in
3679 filearea 'bulletins' you want to look at file 'arld051' you would
3683 TYPE bulletins/arld051
3687 See also SHOW/FILES to see what fileareas are available and a list of
3690 11.122. unset/announce
3692 unset/announce Stop announce messages coming out on your terminal
3696 11.123. unset/anntalk
3698 unset/anntalk Stop talk like announce messages on your terminal
3701 The announce system on legacy cluster nodes is used as a talk
3702 substitute because the network is so poorly connected. If you:
3710 you will suppress several of these announces, you may miss the odd
3711 useful one as well, but you would probably miss them anyway in the
3712 welter of useless ones.
3720 allows you to see them again. This is the default.
3724 unset/beep Stop beeps for DX and other messages on your terminal
3730 unset/dx Stop DX messages coming out on your terminal
3736 unset/dxcq Stop CQ Zones on the end of DX announcements
3739 Display both the Spotter's and the Spotted's CQ Zone on the end of a
3740 DX announcement (there is just enough room). Some user programs cannot
3741 cope with this. The Spotter's CQ is on the RHS of the time, the
3742 Spotted's CQ is on the LHS.
3744 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
3746 Do a STAT/USER to see which flags you have set if you are confused.
3748 11.127. unset/dxgrid
3750 unset/dxgrid Stop QRA Grid Squares on the end of DX announcements
3753 A standard feature which is enabled in version 1.43 and above is that
3754 if the spotter's grid square is known it is output on the end of a DX
3755 announcement (there is just enough room). Some user programs cannot
3756 cope with this. You can use this command to reset (or set) this
3760 Conflicts with: SET/DXCQ, SET/DXITU
3762 Do a STAT/USER to see which flags you have set if you are confused.
3766 unset/dxitu Stop ITU Zones on the end of DX announcements
3769 Display both the Spotter's and the Spotted's ITU Zone on the end of a
3770 DX announcement (there is just enough room). Some user programs cannot
3771 cope with this. The Spotter's ITU is on the RHS of the time, the
3772 Spotted's ITU is on the LHS.
3774 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
3776 Do a STAT/USER to see which flags you have set if you are confused.
3780 unset/echo Stop the cluster echoing your input
3783 If you are connected via a telnet session, different implimentations
3784 of telnet handle echo differently depending on whether you are
3785 connected via port 23 or some other port. You can use this command to
3786 change the setting appropriately.
3788 The setting is stored in your user profile.
3790 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
3794 unset/email Stop personal msgs being forwarded by email
3797 If any personal messages come in for your callsign then you can use
3798 these commands to control whether they are forwarded onto your email
3799 address. To enable the forwarding do something like:-
3803 SET/EMAIL mike.tubby@somewhere.com
3807 You can have more than one email address (each one separated by a
3808 space). Emails are forwarded to all the email addresses you specify.
3810 You can disable forwarding by:-
3820 unset/here Tell the system you are absent from your terminal
3823 11.132. unset/logininfo
3825 unset/logininfo Inform when a station logs out locally
3829 11.133. unset/privilege
3831 unset/privilege Remove any privilege for this session
3834 You can use this command to 'protect' this session from unauthorised
3835 use. If you want to get your normal privilege back you will need to
3836 either logout and login again (if you are on a console) or use the
3839 11.134. unset/prompt
3841 unset/prompt Set your prompt back to default
3844 This command will set your user prompt to exactly the string that you
3845 say. The point of this command to enable a user to interface to
3846 programs that are looking for a specific prompt (or else you just want
3847 a different fixed prompt).
3855 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
3860 unset/talk Stop TALK messages coming out on your terminal
3864 11.136. unset/usstate
3866 unset/usstate Stop US State info on the end of DX announcements
3869 If the spotter's or spotted's US State is known it is output on the
3870 end of a DX announcement (there is just enough room).
3872 A spotter's state will appear on the RHS of the time (like SET/DXGRID)
3873 and the spotted's State will appear on the LHS of the time field. Any
3874 information found will override any locator information from
3877 Some user programs cannot cope with this. You can use this command to
3878 reset (or set) this feature.
3880 Conflicts with: SET/DXCQ, SET/DXITU
3882 Do a STAT/USER to see which flags you have set if you are confused.
3886 unset/wcy Stop WCY messages coming out on your terminal
3890 unset/wwv Stop WWV messages coming out on your terminal
3896 unset/wx Stop WX messages coming out on your terminal
3902 who Show who is physically connected
3905 This is a quick listing that shows which callsigns are connected and
3906 what sort of connection they have
3910 wx <text> Send a weather message to local users
3914 11.142. wx full <text>
3916 wx full <text> Send a weather message to all cluster users