1 <!doctype linuxdoc system>
5 <!-- Title information -->
7 <title>The DXSpider User Manual v1.50</title>
8 <author>Ian Maude, G0VGS, (g0vgs@gb7mbc.net)</author>
9 <date>March 2003 revision 0.3</date>
12 A complete reference for users of the DXSpider DXCluster program.
15 <!-- Table of contents -->
18 <!-- Begin the document -->
22 <sect1>What is a DX Cluster?
25 A DX Cluster is a packet node where DX chasers on any band or mode can
26 post rare or interesting stations that they have worked or heard. Of
27 course other people are doing the same thing too, so you can find new
28 DX as well as telling others about the stations you have worked.
29 Clusters tend to be linked to each other so that the amount of people
30 using them is increased, thereby increasing the amount of posted DX.
31 Other information can be found on clusters such as on-line call books,
32 mail etc. You can talk to other stations connected to the cluster
33 network too, in real time, whether at the node you are logged into or
34 on another node connected to the network. You can also use converse
35 mode, where several stations can talk to each other in the same way.
36 Of course, the DX is still posted to you all the while!
38 <sect1>So what is DXSpider?
41 PacketCluster nodes have been around since roughly 1985. The original
42 PacketCluster idea came from Dick Newell, AK1A, and ran under DOS.
43 In about 1992 Dick stopped the development of the PacketCluster
44 software for amateur radio. Many systems are still using this
45 relatively old DOS software today.
47 There are several new compatible cluster programs around now,
48 including DXSpider. DXSpider is a clone of PacketCluster software that runs
49 under several operating systems including Linux and Windows. Linux is fast
50 becoming the choice for amateur radio stations because of it's flexibility,
51 reliability and the lack of the memory limitations of DOS. Linux supports
52 multitasking and is also multiuser. It has support for AX25, ROSE,
53 NetROM and TCPIP built in, making it the ideal choice for amateur
54 radio. It is also totally free!
56 DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
57 exercise in perl programming. It has developed rapidly and today is a
58 very powerful cluster program. It was designed to be totally compatible
59 with the AK1A program, although several commands have been extended to
60 improve functionality.
62 This manual is designed to help you become familiar with the commands
63 that DXSpider supports and to help you get the best from the program so
64 you can enjoy working that rare DX! As DXSpider is being improved all the
65 time, commands will be added as time goes by, so make sure you have
66 the most upto date version of this manual. The latest version will
67 always be included with the cluster program so if you are unsure, simply
68 ask your sysop. The manual will also be available on the wesite.
71 <sect>Logins and logouts.
74 You might not think that there is a lot of point of including a
75 section on how to log in and out of DXSpider. However, you would be
76 suprised at the difficulties some people have in simply getting in
77 and out of the cluster!
79 There are several ways a login might be achieved, dependant on how
80 the sysop has DXSpider configured. It is impossible for me to cover all
81 variations but here are the basic ones.
86 Simplicity itself. The usual <bf>CONNECT</bf> command will log you straight
87 into the cluster and you will not have to do anything else.
88 Obviously, you will have to connect to the correct callsign. Some
89 nodes use an SSID with their call so you would have to add that.
101 There are several possibilities here, dependant on how the sysop has
102 configured his system. If you are connecting via netrom then you are
103 most probably connecting from another station. Listing the nodes in
104 that station with the <bf>NODES</bf> command will tell you what callsign
105 or netrom alias to connect to. Then just issue the connect command
106 from there. It is possible that the netrom alias may connect you to
107 a node with an alias for the cluster, such as DXC. Just type this
108 and you will be connected.
115 <sect1>Telnet logins.
118 With telnet connections, the source callsign is not seen by DXSpider, so
119 you will be asked to login with your callsign.
120 To telnet to DXSpider, you would connect to a specific port. There is no
121 standard at the moment for a cluster telnet port but ask the sysop if
130 All the above are possible ways of connecting to a DXSpider cluster. You
131 may have some or all of these available to you. There may be one or
132 two additional ways to connect dependant on the network local to you.
133 However I am sure you get the idea.
138 Logging out can be done by simply issuing the standard <bf>BYE</bf>
141 You could also send a disconnect if you are using AX25, or a <bf>CLOSE</bf>
142 command if you are connected via telnet.
143 If you do not log out gracefully using one of the above commands,
144 you may find you are unable to get a full connect next time. This
145 may also happen if a netrom connection drops. You may get connected,
146 but nothing else will happen because the program thinks you are still
147 connected and will not let you connect twice under the same call.
148 However you could reconnect by adding a number to the end of your call,
150 This can be done by either altering your MYCALL setting in the TNC or
151 by altering your program configuration.
154 <sect>Setting your personal details.
157 Once logged in to the cluster, you should set your details so that
158 anybody who wishes to contact you can find out who and where you are.
159 There are four items to set, your name, qth, location and home node.
160 Setting these details also allows the use of the SHOW/HEADING and
161 SHOW/SUN commands from within the cluster. Unless you set your QTH
162 and location, these commands cannot function.
163 Once you have set your name, DXSpider will greet you with it next time
164 you login. Your QTH setting is where you live and it is a good idea
165 to add your locator to this as the location setting is converted to
166 latitude and longitude once inputted. You can actually set your location
167 in latitude/longitude or as a locator. Setting your home node will
168 tell the program where you wish mail to be sent to you.
174 set/qth Morecambe, Lancashire IO84NB
175 set/location 48 34 n 12 12 e
180 <sect>Getting and posting DX.
183 When all is said and done, this is the main function of a DX cluster.
184 In its simplest form you can just connect to the node and you will
185 start to receive DX spots almost immediately! You can check on
186 recent postings in either a general manner or on a particular band or
187 mode. You can even check DX by callsign or a fragment of a callsign.
188 Of course, once you get the hang of things, it is expected that you
189 start posting some yourself! After all, there would be no clusters
190 if people did not post DX and you get the added thrill of the hunt!
195 As we have already said, it is possible just to connect to the
196 cluster and you will receive spots automatically. However, you may
197 wish to check on spots just posted. Maybe you wish to see if a
198 particular band is open or if a certain callsign is active, perhaps a
199 DXpedition. The command to do this is <bf>SHOW/DX</bf>. Without any
200 other arguments, this command will output the last 10 spots
201 posted. It is possible to look at more than this, for example the
202 last 20 or 50 spots, by adding the number to the command. You can
203 make it even more specific by adding a band in either wavelength or
204 frequency, and/or any additional information such as QSL details.
214 will show the last 10, 5 and 20 spots received by the cluster
225 will show the last 5, 10 or 20 spots on 20 metres only.
227 It is also possible to check for certain callsigns, or fragments of
228 callsigns in the same way.
237 would show the last 5 or 10 dx spots containing the callsign g0vgs.
240 You can check for DX by offset and also by specifying a comment to
251 would show the spots that arrived between 30 and 40 spots ago and any
252 spots with the word <em>iota</em> in the comment field. The case of
253 the comment is not important.
255 Checking DX posted on a certain day is possible too. All you have
256 to do here is to specify how many days ago it was like this ...
264 It is of course possible to specify multiple arguments.
269 show/dx 20 prefix 9a on vhf day 30
272 This would show the last 20 spots posted by or about calls with the prefix
273 9a on vhf 30 days ago.
275 As you can see the <bf>SHOW/DX</bf> command is very flexible, so if you are
276 not sure whether something will work or not, try it and see! More
277 information can be found in the Command Set section.
282 To post DX you use the <bf>DX</bf> command. The syntax is shown below.
287 dx (frequency) (callsign) (remarks)
290 Where frequency is in kilohertz and the callsign is the callsign of
291 the station you have worked or heard, (ie not your own callsign!).
292 The remarks section allows you to add information like the operators
293 name or perhaps a location. Actually DXSpider will allow the frequency
294 and callsign fields to be entered in any order.
299 dx 14004 pa3ezl OP Aurelio 599
302 In fact, all the following will give the same result...
305 dx 14004 pa3ezl OP Aurelio 599
306 dx pa3ezl 14004 OP Aurelio 599
307 dx pa3ezl 14.004 OP Aurelio 599
310 This posting, or callout as it is known, will be forwarded to all
311 other connected stations both at the cluster you are connected to and
312 other active clusters in the network. The callout will also be sent
313 to you as proof of receipt.
315 <sect>Headings and propagation
318 There are three commands in DXSpider to help you get the best DX possible.
319 These are <bf>SHOW/SUN</bf>, <bf>SHOW/MOON</bf> and
320 <bf>SHOW/HEADING</bf>. These commands will only work for you if you
321 have entered your personal details. They use your entered location as
322 a reference, so if you have not entered it or have entered it incorrectly
323 they will not return the correct information.
328 The <bf>SHOW/SUN</bf> command can be used in three different ways. It
329 can be used to show sunrise and sunset times for your own station, a
330 particular callsign or a prefix.
338 The output from this would look something like this ..
342 Location Rise Set Azim Elev
343 G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
350 would look like this ...
354 Location Rise Set Azim Elev
355 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
358 You can also specify multiple arguments like this ...
361 sh/sun gw4veq 5b4ab zs
364 and then the output would look like this ...
367 sh/sun gw4veq 5b4ab zs
368 Location Rise Set Azim Elev
369 GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9
370 5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
371 ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
372 ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
373 ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
379 The <bf>SHOW/MOON</bf> command works in the same way as the
380 <bf>SHOW/SUN</bf> command. This program however, calculates the
381 rise and set times of the moon for a prefix or callsign, together
382 with the current azimuth and elevation of the sun at these
391 The output from this command would look like this ..
395 Location Rise Set Azim Elev RGain dB
396 EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
399 You can see that the output is similar to the <bf>SHOW/SUN</bf>
400 command, with slightly different fields.
405 The <bf>SHOW/HEADING</bf> command works in the same way as the
406 <bf>SHOW/SUN</bf> and <bf>SHOW/MOON</bf> commands but outputs beam
407 headings for a specified callsign or prefix. Reciprocal beam headings
416 The output from this command would look like this ..
420 ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
421 ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
422 ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
423 ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
428 <sect1>Making announcements.
431 Occasionally, you may wish to post something that does not fall into
432 the normal parameters for a DX callout. You may wish to tell
433 everybody connected that 10 FM is open for example, or ask if anyone
434 knows the QSL manager for a certain callsign etc. You can do this
435 using the <bf>ANNOUNCE</bf> command.
440 announce 10 FM is open in IO84NB to europe.
443 That would let everyone know locally that this was the case, however
444 it would not be forwarded to other nodes connected. To send
445 announcements to other connected nodes as well, you would use the
446 <bf>FULL</bf> extension.
451 announce full Anyone seen EA7WA today?
454 Be cautious in your use of announce full. There are many other tools
455 available to get the information you require and the judicious use of
456 this command is frowned upon as it creates a great deal of traffic
459 <sect1>Listing announcements.
462 You can list previous announcements in the standard format with the
463 <bf>SHOW</bf> command. As before you can list just the last 5 or as
470 show/announcements 10
473 <sect>Nodes and users.
476 You can check which nodes are connected in the network, who is
477 logged on locally, who is logged on at all the nodes or even
478 just one node in particular. This is handy if you wish to see whether
479 a friend is connected at the node they use. To see who is connected
480 to the nodes, the <bf>SHOW/CONFIGURATION</bf> command is used.
486 show/configuration/nodes
487 show/configuration (node_call)
488 show/configuration (prefix)
491 The first of our three examples would output something like this,
499 GB7BIG (GD0TEP) GD3UMW
500 GB7BPQ (G0INA) G0RCI G3AKU G3OCA
502 GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
503 G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
506 GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
507 G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
509 (GB7DXG) GU6EFB GU7DHI
510 GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
512 GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
516 You will notice that EI5TCR is showing only that it has 7 users and not
517 giving the actual callsigns. This means that this node is on a limited
518 protocol of some kind, probably because of a contest situation where
519 slow radio links can block up and fail if too much information is sent
522 The second example would just show the nodes connected in the
528 GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
529 GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
530 GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
531 GB7YDX KL7G N2TLY (ON0DXK)
532 GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
538 If we insert the node_call pi4tue-8 into the third example, then
539 this would be the output,
543 PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
544 F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
545 ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
546 PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
550 As you can see, only the users of the requested node are shown.
552 You can also use a prefix to show only a group of nodes. For example
553 you may only wish to see who is connected to the nodes in the UK. To
554 do this simply use a prefix like this ...
557 show/configuration gb7
560 To show the locally connected users, the <bf>SHOW/USERS</bf> command is
569 The output of this command would look like this,
572 Callsigns connected to GB7MBC
573 G0JHC G0NEI G0VGS G0VGS-2 G0YLM
580 You can send a single comment or start a dedicated talk session to
581 another user by using the <bf>TALK</bf> command.
584 Talk mode is used to send a one line comment or greeting to a
585 specific user connected either at your node or another in the
586 network. You can also enter into a dedicated talk session with
587 another user. Talks will be automatically forwarded to other nodes
588 if the station you are talking to is not connected locally.
589 You can find out who is connected by using the
590 <bf>SHOW/CONFIGURATION</bf> command, (described earlier).
595 talk g0rdi Having a good day Iain?
598 This example would send the line "Having a good day Iain?" to the
599 user g0rdi but would leave you in normal mode.
603 Entering Talkmode, /EX to end, /<cmd> to run a command
607 As you can see, you can still run commands whilst in talk mode.
608 Simply prefix the command with a / like /sh/dx and you will get
610 If the user is connected to another node, you may have to use a
611 slightly extended version of the <bf>TALK</bf> command.
617 To exit talk mode, you issue the command <bf>/ex</bf>.
619 Whilst in talk mode you will still receive DX spots. This means that
620 you can chat to a friend whilst working DX.
625 You can send and receive both personal mail and bulletins with DXSpider
628 <sect1>The "directory" command.
631 To list mail you would use the <bf>DIRECTORY</bf> command. On its
632 own, this command will output the last ten messages received by the
633 node, either to or from yourself or bulletins such as "DX" and "ALL".
634 As with other commands you can display more by specifying a number
635 with the command. You should be aware that Spider will accept
636 these commands by separating with either a slash or a space, so
637 <em>dir new</em> and <em>dir/new</em> work in the same way.
647 Of course most of the time you will only want to list new mail sent
648 to you personally since your last login. However you might also like
649 to check for general mail received by the node. In fact if there is
650 new mail for you, the cluster will tell you when you login. You will
651 also be informed if new mail arrives for you during the time you are
653 Mail is not only sent to callsigns though. Mail can also be sent to
654 subjects like "all" or "local" or "dx" etc. You can treat these
655 bulletins in the same way as personal mail with the directory
665 directory/from <call>
668 The last option will only show mail from a callsign if it was sent to
669 you personally or was sent as a bulletin. There are some additional
670 commands and these can be found in the DXSpider Command Reference section.
675 The output of the <bf>DIRECTORY</bf> command could be something like
680 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
681 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
682 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
683 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
684 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
685 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
686 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
687 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
688 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
689 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
690 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
693 The first column is the actual message number. If the message is a
694 personal one to you, you will see a letter 'p' after this number. If
695 the message has been read, there will be a '-' between the message
696 number and the 'p'. This only works for personal messages. The next
697 column shows the file size of the message. The third column shows the
698 address the message was sent to and the next column shows who sent it.
699 The rest is fairly self-explanatory.
701 Reading a message is as simple as typing read, followed by the
702 message number that you wish to read.
710 will read message number 25. However the mail will be displayed in it's
711 entirety unless you specify a page length. You can set your page length
712 to any number you like and when the message reaches that number of lines
713 you will get a prompt giving you options.
725 Sending mail is done in the time honoured way. First you specify
726 a recipient for the message, then you will be prompted for a subject.
727 Once you have done this you will be asked to type your message.
728 Please remember that there is no automatic word wrap, so unless you
729 are using a client that wraps lines automatically, remember to hit
730 return at the end of each line.
736 Enter Subject (30 characters):
738 Enter Message /EX to send or /ABORT to exit
740 Just a quick note to say that I can make Thursday after all. The
741 appointment I had has cancelled so we are go!
746 At this point you can either hit return and enter /ex to send the
747 message or use /abort at any time to abort it. You can now display
748 the message in the normal way. There are several send options and
749 these are listed in the Command Set section. These include sending
750 mail to several recipients and asking for a return receipt.
753 <sect1>Replying to mail.
756 If mail is addressed to you or to a bulletin address, you can use the
757 <bf>REPLY</bf> command to reply to it. Using this command, the
758 subject will be automatically set for you as "Re: subject", whatever
770 To delete a message, you use the <em>delete</em> command.
771 You can only delete messages sent to or received by yourself.
772 Bulletins are dealt with automatically or by the sysop.
774 <sect>Filtering (From version 1.45)
776 <sect1>General filter rules
779 Upto v1.44 it was not possible for the user to set their own filters. From
780 v1.45 though that has all changed. It is now possible to set filters for just
781 about anything you wish. If you have just updated from an older version of
782 DXSpider you will need to update your new filters. You do not need to do
783 anything with your old filters, they will be renamed as you update.
786 There are 3 basic commands involved in setting and manipulating filters. These
787 are <em>accept</em>, <em>reject</em> and <em>clear</em>. First we will look
788 generally at filtering. There are a number of things you can filter in the
789 DXSpider system. They all use the same general mechanism.
792 In general terms you can create a 'reject' or an 'accept' filter which can have
793 up to 10 lines in it. You do this using, for example ...
800 where ..... are the specific commands for that type of filter. There are
801 filters for spots, wwv, announce, wcy and (for sysops) connects. See each
802 different accept or reject command reference for more details.
804 There is also a command to clear out one or more lines in a filter. They are ...
811 There is clear/xxxx command for each type of filter.
814 and you can check that your filters have worked by the command ...
821 For now we are going to use spots for the examples, but you can apply the same
822 principles to all types of filter.
824 <sect1>Types of filter
827 There are two main types of filter, <em>accept</em> or <em>reject</em>. You
828 can use either to achieve the result you want dependent on your own preference
829 and which is more simple to do. It is pointless writing 8 lines of reject
830 filters when 1 accept filter would do the same thing! Each filter has 10
831 lines (of any length) which are tried in order. If a line matches then the
832 action you have specified is taken (ie reject means ignore it and accept
836 If you specify reject filters, then any lines that arrive that match the filter
837 will be dumped but all else will be accepted. If you use an accept filter,
838 then ONLY the lines in the filter will be accepted and all else will be dumped.
839 For example if you have a single line <em>accept</em> filter ...
842 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
845 then you will <em>ONLY</em> get VHF spots <em>from</em> or <em>to</em> CQ zones
849 If you set a reject filter like this ...
852 reject/spots on hf/cw
855 Then you will get everything <em>EXCEPT</em> HF CW spots. You could make this
856 single filter even more flexible. For example, if you are interested in IOTA
857 and will work it even on CW even though normally you are not interested in
858 CW, then you could say ...
861 reject/spots on hf/cw and not info iota
864 But in that case you might only be interested in iota and say:-
867 accept/spots not on hf/cw or info iota
870 which achieves exactly the same thing. You should choose one or the other
871 until you are comfortable with the way it works. You can mix them if you
872 wish (actually you can have an accept AND a reject on the same line) but
873 don't attempt this until you are sure you know what you are doing!
876 You can arrange your filter lines into logical units, either for your own
877 understanding or simply convenience. Here is an example ...
880 reject/spots 1 on hf/cw
881 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
884 What this does is to ignore all HF CW spots and also rejects any spots on VHF
885 which don't either originate or spot someone in Europe.
888 This is an example where you would use a line number (1 and 2 in this case), if
889 you leave the digit out, the system assumes '1'. Digits '0'-'9' are available.
890 This make it easier to see just what filters you have set. It also makes it
891 more simple to remove individual filters, during a contest for example.
894 You will notice in the above example that the second line has brackets. Look
895 at the line logically. You can see there are 2 separate sections to it. We
896 are saying reject spots that are VHF or above <em>APART</em> from those in
897 zones 14, 15 and 16 (either spotted there or originated there). If you did
898 not have the brackets to separate the 2 sections, then Spider would read it
899 logically from the front and see a different expression entirely ...
902 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
905 The simple way to remember this is, if you use OR - use brackets. Whilst we are
906 here CASE is not important. 'And BY_Zone' is just the same as 'and by_zone'.
908 As mentioned earlier, setting several filters can be more flexible than
909 simply setting one complex one. Doing it in this way means that if you want
910 to alter your filter you can just redefine or remove one or more lines of it or
911 one line. For example ...
914 reject/spots 1 on hf/ssb
917 would redefine our earlier example, or
923 To remove all the filter lines in the spot filter ...
929 <sect1>Filter options
932 You can filter in several different ways. The options are listed in the
933 various helpfiles for accept, reject and filter.
935 <sect1>Advanced filtering
938 Once you are happy with the results you get, you may like to experiment.
941 The previous example that filters hf/cw spots and accepts vhf/uhf spots from EU
942 can be written with a mixed filter, for example ...
947 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
950 Note that the first filter has not been specified with a number. This
951 will automatically be assumed to be number 1. In this case, we have
952 said <em>reject all HF spots in the CW section of the bands but accept
953 all others at HF. Also accept anything in VHF and above spotted in or
954 by operators in the zones 14, 15 and 16</em>. Each filter slot actually
955 has a 'reject' slot and an 'accept' slot. The reject slot is executed
956 BEFORE the accept slot.
959 It was mentioned earlier that after a reject test that doesn't match, the
960 default for following tests is 'accept', the reverse is true for 'accept'.
961 In the example what happens is that the reject is executed first, any non
962 hf/cw spot is passed to the accept line, which lets through everything
963 else on HF. The next filter line lets through just VHF/UHF spots from EU.
966 <sect>Hints, tips and common questions.
969 <bf/Q./These commands seem very long! Can I shorten them?
971 <bf/A./Of course you can and the usual abbreviations work. If you
974 <bf/Q./I am not sure if this command is correct. Can I cause any
977 <bf/A./Do not be afraid to try a command to see if it will work,
978 at the worst you will get an error message. If you require any
979 help on a command, just type help followed by the command you
980 want help on. Look at the "DXSpider Command Reference" section to see
981 what help can be found.
983 <bf/Q./How should I use the announce command?
985 <bf/A./With respect. Use the command by all means, but please
986 only use the "full" extension if absolutely necessary. It can
987 create a LOT of messages passing between clusters.
989 <bf/Q./I like to be working in the shack while logged into the
990 cluster but I can't be looking at the screen all the time. How
991 can I be alerted when anything happens?
993 <bf/A./Use the <bf>SET/BEEP</bf> command. You can find information
994 on this in the "DXSpider Command Reference" section.
996 <bf/Q./I got disconnected from the cluster and now I can't log
997 back in again. What is wrong?
999 <bf/A./Probably the cluster thinks you are still logged on and
1000 will not let you reconnect using the same call to prevent loops.
1001 Try logging on again adding an ssid to your callsign as DXSpider
1002 treats G0YLM and G0YLM-1 as different users.
1004 <bf/Q./How do I know if I have got the latest version of this
1007 <bf/A./The latest and greatest will always be on the Website. It will
1008 also be included with every release of DXSpider. As always, if unsure,
1009 ask your sysop what version number is the latest.
1011 <sect>The DXSpider command reference
1017 <bf>accept</bf> Set a filter to accept something
1021 Create a filter to accept something
1023 There are 2 types of filter, accept and reject. See HELP FILTERING for more
1025 <sect1>accept/announce [0-9] <pattern>
1029 <bf>accept/announce [0-9] <pattern></bf> Set an 'accept' filter line for announce
1033 Create an 'accept this announce' line for a filter.
1035 An accept filter line means that if the announce matches this filter it is
1036 passed onto the user. See HELP FILTERING for more info. Please read this
1037 to understand how filters work - it will save a lot of grief later on.
1039 You can use any of the following things in this line:-
1042 info <string> eg: iota or qsl
1043 by <prefixes> eg: G,M,2
1044 origin <prefixes>
1045 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1046 origin_itu <prefixes or numbers> or: G,GM,GW
1047 origin_zone <prefixes or numbers>
1048 origin_state <states> eg: VA,NH,RI,NH
1049 by_dxcc <prefixes or numbers>
1050 by_itu <prefixes or numbers>
1051 by_zone <prefixes or numbers>
1052 by_state <states>
1053 channel <prefixes>
1054 wx 1 filter WX announces
1055 dest <prefixes> eg: 6MUK,WDX (distros)
1062 acc/ann 2 by_zone 14,15,16
1063 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1073 acc/ann by_state va,nh,ri,nh
1076 You can use the tag 'all' to accept everything eg:
1082 but this probably for advanced users...
1083 <sect1>accept/spots [0-9] <pattern>
1087 <bf>accept/spots [0-9] <pattern></bf> Set an 'accept' filter line for spots
1091 Create an 'accept this spot' line for a filter.
1093 An accept filter line means that if the spot matches this filter it is
1094 passed onto the user. See HELP FILTERING for more info. Please read this
1095 to understand how filters work - it will save a lot of grief later on.
1097 You can use any of the following things in this line:-
1100 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1101 on <range> same as 'freq'
1102 call <prefixes> eg: G,PA,HB9
1103 info <string> eg: iota or qsl
1105 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1106 call_itu <prefixes or numbers> or: G,GM,GW
1107 call_zone <prefixes or numbers>
1108 call_state <states> eg: VA,NH,RI,ME
1109 by_dxcc <prefixes or numbers>
1110 by_itu <prefixes or numbers>
1111 by_zone <prefixes or numbers>
1112 by_state <states> eg: VA,NH,RI,ME
1113 origin <prefixes>
1114 channel <prefixes>
1117 'call' means the callsign that has spotted 'by' whoever.
1119 For frequencies, you can use any of the band names defined in
1120 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1121 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1122 this is more efficient than saying simply: freq HF (but don't get
1123 too hung up about that)
1129 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1132 You can use the tag 'all' to accept everything, eg:
1141 acc/spots by_state VA,NH,RI,MA,ME
1144 but this probably for advanced users...
1145 <sect1>accept/wcy [0-9] <pattern>
1149 <bf>accept/wcy [0-9] <pattern></bf> set an 'accept' WCY filter
1153 It is unlikely that you will want to do this, but if you do then you can
1154 filter on the following fields:-
1157 by <prefixes> eg: G,M,2
1158 origin <prefixes>
1159 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1160 origin_itu <prefixes or numbers> or: G,GM,GW
1161 origin_zone <prefixes or numbers>
1162 by_dxcc <prefixes or numbers>
1163 by_itu <prefixes or numbers>
1164 by_zone <prefixes or numbers>
1165 channel <prefixes>
1168 There are no examples because WCY Broadcasts only come from one place and
1169 you either want them or not (see UNSET/WCY if you don't want them).
1171 This command is really provided for future use.
1173 See HELP FILTER for information.
1174 <sect1>accept/wwv [0-9] <pattern>
1178 <bf>accept/wwv [0-9] <pattern></bf> set an 'accept' WWV filter
1182 It is unlikely that you will want to do this, but if you do then you can
1183 filter on the following fields:-
1186 by <prefixes> eg: G,M,2
1187 origin <prefixes>
1188 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1189 origin_itu <prefixes or numbers> or: G,GM,GW
1190 origin_zone <prefixes or numbers>
1191 by_dxcc <prefixes or numbers>
1192 by_itu <prefixes or numbers>
1193 by_zone <prefixes or numbers>
1194 channel <prefixes>
1200 accept/wwv by_zone 4
1203 is probably the only useful thing to do (which will only show WWV broadcasts
1204 by stations in the US).
1206 See HELP FILTER for information.
1207 <sect1>announce <text>
1211 <bf>announce <text></bf> Send an announcement to LOCAL users only
1215 <text> is the text of the announcement you wish to broadcast
1216 <sect1>announce full <text>
1220 <bf>announce full <text></bf> Send an announcement cluster wide
1224 This will send your announcement cluster wide
1225 <sect1>apropos <string>
1229 <bf>apropos <string></bf> Search help database for <string>
1233 Search the help database for <string> (it isn't case sensitive), and print
1234 the names of all the commands that may be relevant.
1235 <sect1>blank [<string>] [<nn>]
1239 <bf>blank [<string>] [<nn>]</bf> Print nn (default 1) blank lines (or strings)
1243 In its basic form this command prints one or more blank lines. However if
1244 you pass it a string it will replicate the string for the width of the
1245 screen (default 80) and then print that one or more times, so:
1251 prints two blank lines
1257 prints a row of - characters once.
1263 prints 'abcabcabcabcabcabc....'
1265 This is really only of any use in a script file and you can print a maximum
1271 <bf>bye</bf> Exit from the cluster
1275 This will disconnect you from the cluster
1276 <sect1>clear/announce [1|all]
1280 <bf>clear/announce [1|all]</bf> Clear a announce filter line
1284 This command allows you to clear (remove) a line in a annouce filter or to
1285 remove the whole filter.
1287 see CLEAR/SPOTS for a more detailed explanation.
1288 <sect1>clear/route [1|all]
1292 <bf>clear/route [1|all]</bf> Clear a route filter line
1296 This command allows you to clear (remove) a line in a route filter or to
1297 remove the whole filter.
1299 see CLEAR/SPOTS for a more detailed explanation.
1300 <sect1>clear/spots [0-9|all]
1304 <bf>clear/spots [0-9|all]</bf> Clear a spot filter line
1308 This command allows you to clear (remove) a line in a spot filter or to
1309 remove the whole filter.
1311 If you have a filter:-
1315 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1324 you will be left with:-
1327 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1336 the filter will be completely removed.
1337 <sect1>clear/wcy [1|all]
1341 <bf>clear/wcy [1|all]</bf> Clear a WCY filter line
1345 This command allows you to clear (remove) a line in a WCY filter or to
1346 remove the whole filter.
1348 see CLEAR/SPOTS for a more detailed explanation.
1349 <sect1>clear/wwv [1|all]
1353 <bf>clear/wwv [1|all]</bf> Clear a WWV filter line
1357 This command allows you to clear (remove) a line in a WWV filter or to
1358 remove the whole filter.
1360 see CLEAR/SPOTS for a more detailed explanation.
1365 <bf>dbavail</bf> Show a list of all the Databases in the system
1369 Title says it all really, this command lists all the databases defined
1370 in the system. It is also aliased to SHOW/COMMAND.
1371 <sect1>dbshow <dbname> <key>
1375 <bf>dbshow <dbname> <key></bf> Display an entry, if it exists, in a database
1379 This is the generic user interface to the database to the database system.
1380 It is expected that the sysop will add an entry to the local Aliases file
1381 so that users can use the more familiar AK1A style of enquiry such as:
1387 but if he hasn't and the database really does exist (use DBAVAIL or
1388 SHOW/COMMAND to find out) you can do the same thing with:
1398 <bf>directory</bf> List messages
1402 <sect1>directory <from>-<to>
1406 <bf>directory <from>-<to></bf> List messages <from> message <to> message
1410 List the messages in the messages directory.
1412 If there is a 'p' one space after the message number then it is a
1413 personal message. If there is a '-' between the message number and the
1414 'p' then this indicates that the message has been read.
1416 You can use shell escape characters such as '*' and '?' in the <call>
1419 You can combine some of the various directory commands together eg:-
1426 DIR SUBJECT IOTA 200-250
1429 You can abbreviate all the commands to one letter and use ak1a syntax:-
1436 <sect1>directory <nn>
1440 <bf>directory <nn></bf> List last <nn> messages
1444 <sect1>directory all
1448 <bf>directory all</bf> List all messages
1452 <sect1>directory from <call>
1456 <bf>directory from <call></bf> List all messages from <call>
1460 <sect1>directory new
1464 <bf>directory new</bf> List all new messages
1468 <sect1>directory own
1472 <bf>directory own</bf> List your own messages
1476 <sect1>directory subject <string>
1480 <bf>directory subject <string></bf> List all messages with <string> in subject
1484 <sect1>directory to <call>
1488 <bf>directory to <call></bf> List all messages to <call>
1492 <sect1>dx [by <call>] <freq> <call> <remarks>
1496 <bf>dx [by <call>] <freq> <call> <remarks></bf> Send a DX spot
1500 This is how you send a DX Spot to other users. You can, in fact, now
1501 enter the <freq> and the <call> either way round.
1509 will all give the same result. You can add some remarks to the end
1510 of the command and they will be added to the spot.
1513 DX FR0G 144600 this is a test
1516 You can credit someone else by saying:-
1519 DX by G1TLH FR0G 144.600 he isn't on the cluster
1522 The <freq> is compared against the available bands set up in the
1523 cluster. See SHOW/BANDS for more information.
1524 <sect1>echo <line>
1528 <bf>echo <line></bf> Echo the line to the output
1532 This command is useful in scripts and so forth for printing the
1533 line that you give to the command to the output. You can use this
1534 in user_default scripts and the SAVE command for titling and so forth
1536 The script will interpret certain standard "escape" sequences as follows:-
1539 \t - becomes a TAB character (0x09 in ascii)
1540 \a - becomes a BEEP character (0x07 in ascii)
1541 \n - prints a new line
1544 So the following example:-
1547 echo GB7DJK is a dxcluster
1553 GB7DJK is a dxcluster
1556 on the output. You don't need a \n on the end of the line you want to send.
1558 A more complex example:-
1561 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
1578 <bf>filtering...</bf> Filtering things in DXSpider
1582 There are a number of things you can filter in the DXSpider system. They
1583 all use the same general mechanism.
1585 In general terms you can create a 'reject' or an 'accept' filter which
1586 can have up to 10 lines in it. You do this using, for example:-
1593 where ..... are the specific commands for that type of filter. There
1594 are filters for spots, wwv, announce, wcy and (for sysops)
1595 connects. See each different accept or reject command reference for
1598 There is also a command to clear out one or more lines in a filter and
1599 one to show you what you have set. They are:-
1612 There is clear/xxxx command for each type of filter.
1614 For now we are going to use spots for the examples, but you can apply
1615 the principles to all types of filter.
1617 There are two main types of filter 'accept' or 'reject'; which you use
1618 depends entirely on how you look at the world and what is least
1619 writing to achieve what you want. Each filter has 10 lines (of any
1620 length) which are tried in order. If a line matches then the action
1621 you have specified is taken (ie reject means ignore it and accept
1624 The important thing to remember is that if you specify a 'reject'
1625 filter (all the lines in it say 'reject/spots' (for instance)) then if
1626 a spot comes in that doesn't match any of the lines then you will get
1627 it BUT if you specify an 'accept' filter then any spots that don't
1628 match are dumped. For example if I have a one line accept filter:-
1631 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1634 then automatically you will ONLY get VHF spots from or to CQ zones 14
1635 15 and 16. If you set a reject filter like:
1638 reject/spots on hf/cw
1641 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
1642 and will work it even on CW then you could say:-
1645 reject/spots on hf/cw and not info iota
1648 But in that case you might only be interested in iota and say:-
1651 accept/spots not on hf/cw or info iota
1654 which is exactly the same. You should choose one or the other until
1655 you are confortable with the way it works. Yes, you can mix them
1656 (actually you can have an accept AND a reject on the same line) but
1657 don't try this at home until you can analyse the results that you get
1658 without ringing up the sysop for help.
1660 Another useful addition now is filtering by US state
1663 accept/spots by_state VA,NH,RI,ME
1666 You can arrange your filter lines into logical units, either for your
1667 own understanding or simply convenience. I have one set frequently:-
1670 reject/spots 1 on hf/cw
1671 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
1674 What this does is to ignore all HF CW spots (being a class B I can't
1675 read any CW and couldn't possibly be interested in HF :-) and also
1676 rejects any spots on VHF which don't either originate or spot someone
1679 This is an exmaple where you would use the line number (1 and 2 in
1680 this case), if you leave the digit out, the system assumes '1'. Digits
1681 '0'-'9' are available.
1683 You can leave the word 'and' out if you want, it is implied. You can
1684 use any number of brackets to make the 'expression' as you want
1685 it. There are things called precedence rules working here which mean
1686 that you will NEED brackets in a situation like line 2 because,
1687 without it, will assume:-
1690 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
1693 annoying, but that is the way it is. If you use OR - use
1694 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
1697 If you want to alter your filter you can just redefine one or more
1698 lines of it or clear out one line. For example:-
1701 reject/spots 1 on hf/ssb
1710 To remove the filter in its entirty:-
1716 There are similar CLEAR commands for the other filters:-
1726 Once you are happy with the results you get, you may like to experiment.
1728 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
1729 can be written with a mixed filter, eg:
1734 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
1737 each filter slot actually has a 'reject' slot and an 'accept'
1738 slot. The reject slot is executed BEFORE the accept slot.
1740 It was mentioned earlier that after a reject test that doesn't match,
1741 the default for following tests is 'accept', the reverse is true for
1742 'accept'. In the example what happens is that the reject is executed
1743 first, any non hf/cw spot is passed to the accept line, which lets
1744 thru everything else on HF.
1746 The next filter line lets through just VHF/UHF spots from EU.
1751 <bf>help</bf> The HELP Command
1755 HELP is available for a number of commands. The syntax is:-
1761 Where <cmd> is the name of the command you want help on.
1763 All commands can be abbreviated, so SHOW/DX can be abbreviated
1764 to SH/DX, ANNOUNCE can be shortened to AN and so on.
1766 Look at the APROPOS <string> command which will search the help database
1767 for the <string> you specify and give you a list of likely commands
1768 to look at with HELP.
1769 <sect1>kill <from msgno>-<to msgno>
1773 <bf>kill <from msgno>-<to msgno></bf> Delete a range of messages
1777 <sect1>kill <msgno> [<msgno..]
1781 <bf>kill <msgno> [<msgno..]</bf> Delete a message from the local system
1785 <sect1>kill <msgno> [<msgno> ...]
1789 <bf>kill <msgno> [<msgno> ...]</bf> Remove or erase a message from the system
1793 You can get rid of any message to or originating from your callsign using
1794 this command. You can remove more than one message at a time.
1795 <sect1>kill from <regex>
1799 <bf>kill from <regex></bf> Delete messages FROM a callsign or pattern
1803 <sect1>kill to <regex>
1807 <bf>kill to <regex></bf> Delete messages TO a callsign or pattern
1815 <bf>links</bf> Show which nodes is physically connected
1819 This is a quick listing that shows which links are connected and
1820 some information about them. See WHO for a list of all connections.
1825 <bf>read</bf> Read the next unread personal message addressed to you
1829 <sect1>read <msgno>
1833 <bf>read <msgno></bf> Read the specified message
1837 You can read any messages that are sent as 'non-personal' and also any
1838 message either sent by or sent to your callsign.
1843 <bf>reject</bf> Set a filter to reject something
1847 Create a filter to reject something
1849 There are 2 types of filter, accept and reject. See HELP FILTERING for more
1851 <sect1>reject/announce [0-9] <pattern>
1855 <bf>reject/announce [0-9] <pattern></bf> Set a 'reject' filter line for announce
1859 Create an 'reject this announce' line for a filter.
1861 A reject filter line means that if the announce matches this filter it is
1862 passed onto the user. See HELP FILTERING for more info. Please read this
1863 to understand how filters work - it will save a lot of grief later on.
1865 You can use any of the following things in this line:-
1868 info <string> eg: iota or qsl
1869 by <prefixes> eg: G,M,2
1870 origin <prefixes>
1871 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1872 origin_itu <prefixes or numbers> or: G,GM,GW
1873 origin_zone <prefixes or numbers>
1874 origin_state <states> eg: VA,NH,RI,ME
1875 by_dxcc <prefixes or numbers>
1876 by_itu <prefixes or numbers>
1877 by_zone <prefixes or numbers>
1878 by_state <states> eg: VA,NH,RI,ME
1879 channel <prefixes>
1880 wx 1 filter WX announces
1881 dest <prefixes> eg: 6MUK,WDX (distros)
1887 rej/ann by_zone 14,15,16 and not by G,M,2
1890 You can use the tag 'all' to reject everything eg:
1896 but this probably for advanced users...
1897 <sect1>reject/spots [0-9] <pattern>
1901 <bf>reject/spots [0-9] <pattern></bf> Set a 'reject' filter line for spots
1905 Create a 'reject this spot' line for a filter.
1907 A reject filter line means that if the spot matches this filter it is
1908 dumped (not passed on). See HELP FILTERING for more info. Please read this
1909 to understand how filters work - it will save a lot of grief later on.
1911 You can use any of the following things in this line:-
1914 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1915 on <range> same as 'freq'
1916 call <prefixes> eg: G,PA,HB9
1917 info <string> eg: iota or qsl
1919 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1920 call_itu <prefixes or numbers> or: G,GM,GW
1921 call_zone <prefixes or numbers>
1922 call_state <states> eg: VA,NH,RI,ME
1923 by_dxcc <prefixes or numbers>
1924 by_itu <prefixes or numbers>
1925 by_zone <prefixes or numbers>
1926 by_state <states> eg: VA,NH,RI,ME
1927 origin <prefixes>
1928 channel <prefixes>
1931 'call' means the callsign that has spotted 'by' whoever.
1933 For frequencies, you can use any of the band names defined in
1934 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1935 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1936 this is more efficient than saying simply: on HF (but don't get
1937 too hung up about that)
1943 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1946 You can use the tag 'all' to reject everything eg:
1952 but this probably for advanced users...
1953 <sect1>reject/wcy [0-9] <pattern>
1957 <bf>reject/wcy [0-9] <pattern></bf> set a 'reject' WCY filter
1961 It is unlikely that you will want to do this, but if you do then you can
1962 filter on the following fields:-
1965 by <prefixes> eg: G,M,2
1966 origin <prefixes>
1967 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1968 origin_itu <prefixes or numbers> or: G,GM,GW
1969 origin_zone <prefixes or numbers>
1970 by_dxcc <prefixes or numbers>
1971 by_itu <prefixes or numbers>
1972 by_zone <prefixes or numbers>
1973 channel <prefixes>
1976 There are no examples because WCY Broadcasts only come from one place and
1977 you either want them or not (see UNSET/WCY if you don't want them).
1979 This command is really provided for future use.
1981 See HELP FILTER for information.
1982 <sect1>reject/wwv [0-9] <pattern>
1986 <bf>reject/wwv [0-9] <pattern></bf> set a 'reject' WWV filter
1990 It is unlikely that you will want to do this, but if you do then you can
1991 filter on the following fields:-
1994 by <prefixes> eg: G,M,2
1995 origin <prefixes>
1996 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1997 origin_itu <prefixes or numbers> or: G,GM,GW
1998 origin_zone <prefixes or numbers>
1999 by_dxcc <prefixes or numbers>
2000 by_itu <prefixes or numbers>
2001 by_zone <prefixes or numbers>
2002 channel <prefixes>
2008 reject/wwv by_zone 14,15,16
2011 is probably the only useful thing to do (which will only show WWV broadcasts
2012 by stations in the US).
2014 See HELP FILTER for information.
2019 <bf>reply</bf> Reply (privately) to the last message that you have read
2023 <sect1>reply <msgno>
2027 <bf>reply <msgno></bf> Reply (privately) to the specified message
2031 <sect1>reply b <msgno>
2035 <bf>reply b <msgno></bf> Reply as a Bulletin to the specified message
2039 <sect1>reply noprivate <msgno>
2043 <bf>reply noprivate <msgno></bf> Reply as a Bulletin to the specified message
2047 <sect1>reply rr <msgno>
2051 <bf>reply rr <msgno></bf> Reply to the specified message with read receipt
2055 You can reply to a message and the subject will automatically have
2056 "Re:" inserted in front of it, if it isn't already present.
2058 You can also use all the extra qualifiers such as RR, PRIVATE,
2059 NOPRIVATE, B that you can use with the SEND command (see SEND
2060 for further details)
2061 <sect1>send <call> [<call> ...]
2065 <bf>send <call> [<call> ...]</bf> Send a message to one or more callsigns
2069 <sect1>send copy <msgno> <call>
2073 <bf>send copy <msgno> <call></bf> Send a copy of a message to someone
2077 <sect1>send noprivate <call>
2081 <bf>send noprivate <call></bf> Send a message to all stations
2085 All the SEND commands will create a message which will be sent either to
2086 an individual callsign or to one of the 'bulletin' addresses.
2088 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
2089 it will mark the message as personal and send it to the cluster node that
2090 that callsign is connected to. If the <call> you have specified is in fact
2091 a known bulletin category on your node (eg: ALL) then the message should
2092 automatically become a bulletin.
2094 You can have more than one callsign in all of the SEND commands.
2096 You can have multiple qualifiers so that you can have for example:-
2099 SEND RR COPY 123 PRIVATE G1TLH G0RDI
2102 which should send a copy of message 123 to G1TLH and G0RDI and you will
2103 receive a read receipt when they have read the message.
2105 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
2106 SP is an alias for SEND PRIVATE
2108 The system will ask you for a subject. Conventionally this should be
2109 no longer than 29 characters for compatibility. Most modern cluster
2110 software should accept more.
2112 You will now be prompted to start entering your text.
2114 You finish the message by entering '/EX' on a new line. For instance:
2123 If you have started a message and you don't want to keep it then you
2124 can abandon the message with '/ABORT' on a new line, like:-
2129 oh I just can't be bothered with this
2133 If you abort the message it will NOT be sent.
2135 When you are entering the text of your message, most normal output (such
2136 as DX announcements and so on are suppressed and stored for latter display
2137 (upto 20 such lines are stored, as new ones come along, so the oldest
2140 Also, you can enter normal commands commands (and get the output
2141 immediately) whilst in the middle of a message. You do this by typing
2142 the command preceeded by a '/' character on a new line, so:-
2145 /dx g1tlh 144010 strong signal
2148 Will issue a dx annoucement to the rest of the cluster.
2150 Also, you can add the output of a command to your message by preceeding
2151 the command with '//', thus :-
2157 This will show YOU the output from SH/VHFTABLE and also store it in the
2160 You can carry on with the message until you are ready to send it.
2161 <sect1>send private <call>
2165 <bf>send private <call></bf> Send a personal message
2169 <sect1>send rr <call>
2173 <bf>send rr <call></bf> Send a message and ask for a read receipt
2177 <sect1>set/address <your address>
2181 <bf>set/address <your address></bf> Record your postal address
2189 <bf>set/announce</bf> Allow announce messages to come out on your terminal
2197 <bf>set/anntalk</bf> Allow talk like announce messages on your terminal
2205 <bf>set/beep</bf> Add a beep to DX and other messages on your terminal
2213 <bf>set/dx</bf> Allow DX messages to come out on your terminal
2221 <bf>set/dxcq</bf> Show CQ Zones on the end of DX announcements
2229 <bf>set/dxgrid</bf> Allow QRA Grid Squares on the end of DX announcements
2237 <bf>set/dxitu</bf> Show ITU Zones on the end of DX announcements
2245 <bf>set/echo</bf> Make the cluster echo your input
2249 <sect1>set/email <email> ...
2253 <bf>set/email <email> ...</bf> Set email address(es) and forward your personals
2261 <bf>set/here</bf> Tell the system you are present at your terminal
2265 <sect1>set/homenode <node>
2269 <bf>set/homenode <node> </bf> Set your normal cluster callsign
2273 Tell the cluster system where you normally connect to. Any Messages sent
2274 to you will normally find their way there should you not be connected.
2280 <sect1>set/language <lang>
2284 <bf>set/language <lang></bf> Set the language you want to use
2288 You can select the language that you want the cluster to use. Currently
2289 the languages available are en (English), de (German), es (Spanish)
2291 <sect1>set/location <lat & long>
2295 <bf>set/location <lat & long></bf> Set your latitude and longitude
2299 <sect1>set/logininfo
2303 <bf>set/logininfo</bf> Inform when a station logs in locally
2307 <sect1>set/name <your name>
2311 <bf>set/name <your name></bf> Set your name
2315 Tell the system what your name is eg:-
2320 <sect1>set/page <lines per page>
2324 <bf>set/page <lines per page></bf> Set the lines per page
2328 Tell the system how many lines you wish on a page when the number of line
2329 of output from a command is more than this. The default is 20. Setting it
2330 explicitly to 0 will disable paging.
2336 The setting is stored in your user profile.
2341 <bf>set/password</bf> Set your own password
2345 This command only works for a 'telnet' user (currently). It will
2346 only work if you have a password already set. This initial password
2347 can only be set by the sysop.
2349 When you execute this command it will ask you for your old password,
2350 then ask you to type in your new password twice (to make sure you
2351 get it right). You may or may not see the data echoed on the screen
2352 as you type, depending on the type of telnet client you have.
2353 <sect1>set/prompt <string>
2357 <bf>set/prompt <string></bf> Set your prompt to <string>
2361 <sect1>set/qra <locator>
2365 <bf>set/qra <locator></bf> Set your QRA Grid locator
2369 Tell the system what your QRA (or Maidenhead) locator is. If you have not
2370 done a SET/LOCATION then your latitude and longitude will be set roughly
2371 correctly (assuming your locator is correct ;-). For example:-
2376 <sect1>set/qth <your qth>
2380 <bf>set/qth <your qth></bf> Set your QTH
2384 Tell the system where you are. For example:-
2386 SET/QTH East Dereham, Norfolk
2393 <bf>set/talk</bf> Allow TALK messages to come out on your terminal
2401 <bf>set/usstate</bf> Allow US State info on the end of DX announcements
2409 <bf>set/wcy</bf> Allow WCY messages to come out on your terminal
2417 <bf>set/wwv</bf> Allow WWV messages to come out on your terminal
2425 <bf>set/wx</bf> Allow WX messages to come out on your terminal
2429 <sect1>show/configuration [<node>]
2433 <bf>show/configuration [<node>]</bf> Show all the nodes and users visible
2437 This command allows you to see all the users that can be seen
2438 and the nodes to which they are connected.
2440 This command is normally abbreviated to: sh/c
2442 Normally, the list returned will be just for the nodes from your
2443 country (because the list otherwise will be very long).
2449 will produce a complete list of all nodes.
2451 BE WARNED: the list that is returned can be VERY long
2453 It is possible to supply a node or part of a prefix and you will get
2454 a list of the users for that node or list of nodes starting with
2465 <sect1>show/configuration/node
2469 <bf>show/configuration/node</bf> Show all the nodes connected locally
2473 Show all the nodes connected to this node.
2474 <sect1>show/contest <year and month>
2478 <bf>show/contest <year and month></bf> Show all the contests for a month
2482 Show all known contests which are maintained at http://www.sk3bg.se/contest/
2483 for a particular month or year. The format is reasonably flexible.
2491 <sect1>show/date [<prefix>|<callsign>]
2495 <bf>show/date [<prefix>|<callsign>]</bf> Show the local time
2499 This is very nearly the same as SHOW/TIME, the only difference the format
2500 of the date string if no arguments are given.
2502 If no prefixes or callsigns are given then this command returns the local
2503 time and UTC as the computer has it right now. If you give some prefixes
2504 then it will show UTC and UTC + the local offset (not including DST) at
2505 the prefixes or callsigns that you specify.
2506 <sect1>show/db0sdx <callsign>
2510 <bf>show/db0sdx <callsign></bf> Show QSL infomation from DB0SDX database
2514 This command queries the DB0SDX QSL server on the internet
2515 and returns any information available for that callsign. This service
2516 is provided for users of this software by http://www.qslinfo.de.
2518 See also SHOW/QRZ, SHOW/WM7D.
2523 <bf>show/dx</bf> Interrogate the spot database
2527 If you just type SHOW/DX you will get the last so many spots
2528 (sysop configurable, but usually 10).
2530 In addition you can add any number of these commands in very nearly
2531 any order to the basic SHOW/DX command, they are:-
2534 on <band> - eg 160m 20m 2m 23cm 6mm
2535 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2536 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
2537 <from>-<to>
2541 <number> - the number of spots you want
2542 <from>-<to> - <from> spot no <to> spot no in the selected list
2543 <from>/<to>
2547 <prefix> - for a spotted callsign beginning with <prefix>
2548 *<suffix> - for a spotted callsign ending in <suffix>
2549 *<string>* - for a spotted callsign containing <string>
2553 day <number> - starting <number> days ago
2554 day <from>-<to> - <from> days <to> days ago
2555 <from>/<to>
2559 info <text> - any spots containing <text> in the info or remarks
2563 by <call> - any spots spotted by <call> (spotter <call> is the
2568 qsl - this automatically looks for any qsl info on the call
2569 held in the spot database.
2573 iota [<iota>] - If the iota island number is missing it will look for
2574 the string iota and anything which looks like an iota
2575 island number. If you specify then it will look for
2580 qra [<locator>] - this will look for the specific locator if you specify
2581 one or else anything that looks like a locator.
2585 dxcc - treat the prefix as a 'country' and look for spots
2586 from that country regardless of actual prefix.
2591 You can also use this with the 'by' keyword so
2601 SH/DX on 20m info iota
2602 SH/DX 9a on vhf day 30
2608 SH/DX dxcc oq2 by w dxcc
2611 <sect1>show/dxcc <prefix>
2615 <bf>show/dxcc <prefix></bf> Interrogate the spot database by country
2619 This command takes the <prefix> (which can be a full or partial
2620 callsign if desired), looks up which internal country number it is
2621 and then displays all the spots as per SH/DX for that country.
2623 This is now an alias for 'SHOW/DX DXCC'
2625 The options for SHOW/DX also apply to this command.
2630 SH/DXCC W on 20m iota
2633 This can be done with the SHOW/DX command like this:-
2637 SH/DX dxcc w on 20m iota
2640 <sect1>show/dxqsl <callsign>
2644 <bf>show/dxqsl <callsign></bf> Show any QSL info gathered from spots
2648 The node collects information from the comment fields in spots (things
2649 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
2651 This command allows you to interrogate that database and if the callsign
2652 is found will display the manager(s) that people have spotted. This
2653 information is NOT reliable, but it is normally reasonably accurate if
2654 it is spotted enough times.
2662 You can check the raw input spots yourself with:-
2668 This gives you more background information.
2669 <sect1>show/dxstats [days] [date]
2673 <bf>show/dxstats [days] [date]</bf> Show the DX Statistics
2677 Show the total DX spots for the last <days> no of days (default is 31),
2678 starting from a <date> (default: today).
2679 <sect1>show/files [<filearea> [<string>]]
2683 <bf>show/files [<filearea> [<string>]]</bf> List the contents of a filearea
2687 SHOW/FILES on its own will show you a list of the various fileareas
2688 available on the system. To see the contents of a particular file
2691 SH/FILES <filearea>
2693 where <filearea> is the name of the filearea you want to see the
2696 You can also use shell globbing characters like '*' and '?' in a
2697 string to see a selection of files in a filearea eg:-
2699 SH/FILES bulletins arld*
2702 See also TYPE - to see the contents of a file.
2707 <bf>show/filter</bf> Show the contents of all the filters you have set
2711 Show the contents of all the filters that are set. This command displays
2712 all the filters set - for all the various categories.
2713 <sect1>show/hfstats [days] [date]
2717 <bf>show/hfstats [days] [date]</bf> Show the HF DX Statistics
2721 Show the HF DX spots breakdown by band for the last <days> no of days
2722 (default is 31), starting from a <date> (default: today).
2723 <sect1>show/hftable [days] [date] [prefix ...]
2727 <bf>show/hftable [days] [date] [prefix ...]</bf> Show the HF DX Spotter Table
2731 Show the HF DX Spotter table for the list of prefixes for the last
2732 <days> no of days (default is 31), starting from a <date> (default: today).
2734 If there are no prefixes then it will show the table for your country.
2736 Remember that some countries have more than one "DXCC country" in them
2737 (eg G :-), to show them (assuming you are not in G already which is
2738 specially treated in the code) you must list all the relevant prefixes
2741 sh/hftable g gm gd gi gj gw gu
2744 Note that the prefixes are converted into country codes so you don't have
2745 to list all possible prefixes for each country.
2747 If you want more or less days than the default simply include the
2748 number you require:-
2754 If you want to start at a different day, simply add the date in some
2758 sh/hftable 2 25nov02
2759 sh/hftable 2 25-nov-02
2761 sh/hftable 2 25/11/02
2764 This will show the stats for your DXCC for that CQWW contest weekend.
2766 You can specify either prefixes or full callsigns (so you can see how you
2767 did against all your mates). You can also say 'all' which will then print
2768 the worldwide statistics.
2774 <sect1>show/moon [ndays] [<prefix>|<callsign>]
2778 <bf>show/moon [ndays] [<prefix>|<callsign>]</bf> Show Moon rise and set times
2782 Show the Moon rise and set times for a (list of) prefixes or callsigns,
2783 together with the azimuth and elevation of the sun currently at those
2786 If you don't specify any prefixes or callsigns, it will show the times for
2787 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2788 together with the current azimuth and elevation.
2790 In addition, it will show the illuminated fraction of the moons disk.
2792 If all else fails it will show the Moonrise and set times for the node
2793 that you are connected to.
2802 You can also use this command to see into the past or the future, so
2803 if you want to see yesterday's times then do:-
2809 or in three days time:-
2815 Upto 366 days can be checked both in the past and in the future.
2817 Please note that the rise and set times are given as the UT times of rise and
2818 set on the requested UT day.
2819 <sect1>show/muf <prefix> [<hours>][long]
2823 <bf>show/muf <prefix> [<hours>][long]</bf> Show the likely propagation to a prefix
2827 This command allow you to estimate the likelihood of you contacting
2828 a station with the prefix you have specified. The output assumes a modest
2829 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
2831 The result predicts the most likely operating frequencies and signal
2832 levels for high frequency (shortwave) radio propagation paths on
2833 specified days of the year and hours of the day. It is most useful for
2834 paths between 250 km and 6000 km, but can be used with reduced accuracy
2835 for paths shorter or longer than this.
2837 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2838 used to predict the MUF given the predicted flux, day of the year,
2839 hour of the day and geographic coordinates of the transmitter and
2840 receiver. This routine is reasonably accurate for the purposes here,
2841 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2842 than the programs used by major shortwave broadcasting organizations,
2843 such as the Voice of America.
2845 The command will display some header information detailing its
2846 assumptions, together with the locations, latitude and longitudes and
2847 bearings. It will then show UTC (UT), local time at the other end
2848 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2849 (Zen) and the likely signal strengths. Then for each frequency for which
2850 the system thinks there is a likelihood of a circuit it prints a value.
2852 The value is currently a likely S meter reading based on the conventional
2853 6dB / S point scale. If the value has a '+' appended it means that it is
2854 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
2855 there is likely to be much fading and by an 's' that the signal is likely
2858 By default SHOW/MUF will show the next two hours worth of data. You
2859 can specify anything up to 24 hours worth of data by appending the no of
2860 hours required after the prefix. For example:-
2869 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2870 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2871 Location Lat / Long Azim
2872 East Dereham, Norfolk 52 41 N 0 57 E 47
2873 United-States-W 43 0 N 87 54 W 299
2874 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2875 18 23 11.5 -35 mS0+ mS2 S3
2876 19 0 11.2 -41 mS0+ mS2 S3
2879 indicating that you will have weak, fading circuits on top band and
2880 80m but usable signals on 40m (about S3).
2888 will get you the above display, but with the next 24 hours worth of
2896 Gives you an estimate of the long path propagation characterics. It
2897 should be noted that the figures will probably not be very useful, nor
2898 terrible accurate, but it is included for completeness.
2899 <sect1>show/newconfiguration [<node>]
2903 <bf>show/newconfiguration [<node>]</bf> Show all the nodes and users visible
2907 This command allows you to see all the users that can be seen
2908 and the nodes to which they are connected.
2910 This command produces essentially the same information as
2911 SHOW/CONFIGURATION except that it shows all the duplication of
2912 any routes that might be present It also uses a different format
2913 which may not take up quite as much space if you don't have any
2916 BE WARNED: the list that is returned can be VERY long
2917 <sect1>show/newconfiguration/node
2921 <bf>show/newconfiguration/node</bf> Show all the nodes connected locally
2925 Show all the nodes connected to this node in the new format.
2926 <sect1>show/prefix <callsign>
2930 <bf>show/prefix <callsign></bf> Interrogate the prefix database
2934 This command takes the <callsign> (which can be a full or partial
2935 callsign or a prefix), looks up which internal country number
2936 it is and then displays all the relevant prefixes for that country
2937 together with the internal country no, the CQ and ITU regions.
2940 <sect1>show/qra <lat> <long>
2944 <bf>show/qra <lat> <long></bf> Convert lat/long to a QRA Grid locator
2948 This is a multipurpose command that allows you either to calculate the
2949 distance and bearing between two locators or (if only one locator is
2950 given on the command line) the distance and beraing from your station
2951 to the locator. For example:-
2958 The first example will show the distance and bearing to the locator from
2959 yourself, the second example will calculate the distance and bearing from
2960 the first locator to the second. You can use 4 or 6 character locators.
2962 It is also possible to convert a latitude and longitude to a locator by
2963 using this command with a latitude and longitude as an argument, for
2967 SH/QRA 52 41 N 0 58 E
2970 <sect1>show/qra <locator> [<locator>]
2974 <bf>show/qra <locator> [<locator>]</bf> Show distance between QRA Grid locators
2978 <sect1>show/qrz <callsign>
2982 <bf>show/qrz <callsign></bf> Show any callbook details on a callsign
2986 This command queries the QRZ callbook server on the internet
2987 and returns any information available for that callsign. This service
2988 is provided for users of this software by http://www.qrz.com
2990 See also SHOW/WM7D for an alternative.
2991 <sect1>show/route <callsign> ...
2995 <bf>show/route <callsign> ...</bf> Show the route to the callsign
2999 This command allows you to see to which node the callsigns specified are
3000 connected. It is a sort of inverse sh/config.
3006 <sect1>show/satellite <name> [<hours> <interval>]
3010 <bf>show/satellite <name> [<hours> <interval>]</bf> Show tracking data
3014 Show the tracking data from your location to the satellite of your choice
3015 from now on for the next few hours.
3017 If you use this command without a satellite name it will display a list
3018 of all the satellites known currently to the system.
3020 If you give a name then you can obtain tracking data of all the passes
3021 that start and finish 5 degrees below the horizon. As default it will
3022 give information for the next three hours for every five minute period.
3024 You can alter the number of hours and the step size, within certain
3027 Each pass in a period is separated with a row of '-----' characters
3033 SH/SAT FENGYUN1 12 2
3036 <sect1>show/station [<callsign> ..]
3040 <bf>show/station [<callsign> ..]</bf> Show information about a callsign
3044 Show the information known about a callsign and whether (and where)
3045 that callsign is connected to the cluster.
3051 If no callsign is given then show the information for yourself.
3052 <sect1>show/sun [ndays] [<prefix>|<callsign>]
3056 <bf>show/sun [ndays] [<prefix>|<callsign>]</bf> Show sun rise and set times
3060 Show the sun rise and set times for a (list of) prefixes or callsigns,
3061 together with the azimuth and elevation of the sun currently at those
3064 If you don't specify any prefixes or callsigns, it will show the times for
3065 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
3066 together with the current azimuth and elevation.
3068 If all else fails it will show the sunrise and set times for the node
3069 that you are connected to.
3075 SH/SUN G1TLH K9CW ZS
3078 You can also use this command to see into the past or the future, so
3079 if you want to see yesterday's times then do:-
3085 or in three days time:-
3091 Upto 366 days can be checked both in the past and in the future.
3093 Please note that the rise and set times are given as the UT times of rise
3094 and set on the requested UT day.
3095 <sect1>show/time [<prefix>|<callsign>]
3099 <bf>show/time [<prefix>|<callsign>]</bf> Show the local time
3103 If no prefixes or callsigns are given then this command returns the local
3104 time and UTC as the computer has it right now. If you give some prefixes
3105 then it will show UTC and UTC + the local offset (not including DST) at
3106 the prefixes or callsigns that you specify.
3107 <sect1>show/usdb [call ..]
3111 <bf>show/usdb [call ..]</bf> Show information held on the FCC Call database
3115 Show the City and State of a Callsign held on the FCC database if
3116 his is being run on this system, eg:-
3122 <sect1>show/vhfstats [days] [date]
3126 <bf>show/vhfstats [days] [date]</bf> Show the VHF DX Statistics
3130 Show the VHF DX spots breakdown by band for the last
3131 <days> no of days (default is 31), starting from a date (default: today).
3132 <sect1>show/vhftable [days] [date] [prefix ...]
3136 <bf>show/vhftable [days] [date] [prefix ...]</bf> Show the VHF DX Spotter Table
3140 Show the VHF DX Spotter table for the list of prefixes for the last
3141 <days> no of days (default is 31), starting from a date (default: today).
3143 If there are no prefixes then it will show the table for your country.
3145 Remember that some countries have more than one "DXCC country" in them
3146 (eg G :-), to show them (assuming you are not in G already which is
3147 specially treated in the code) you must list all the relevant prefixes
3150 sh/vhftable g gm gd gi gj gw gu
3153 Note that the prefixes are converted into country codes so you don't have
3154 to list all possible prefixes for each country.
3156 If you want more or less days than the default simply include the
3157 number you require:-
3163 If you want to start at a different day, simply add the date in some
3167 sh/vhftable 2 25nov02
3168 sh/vhftable 2 25-nov-02
3169 sh/vhftable 2 021125
3170 sh/vhftable 2 25/11/02
3173 This will show the stats for your DXCC for that CQWW contest weekend.
3175 You can specify either prefixes or full callsigns (so you can see how you
3176 did against all your mates). You can also say 'all' which will then print
3177 the worldwide statistics.
3187 <bf>show/wcy</bf> Show last 10 WCY broadcasts
3191 <sect1>show/wcy <n>
3195 <bf>show/wcy <n></bf> Show last <n> WCY broadcasts
3199 Display the most recent WCY information that has been received by the system
3201 <sect1>show/wm7d <callsign>
3205 <bf>show/wm7d <callsign></bf> Show callbook details on a US callsigns
3209 This command queries the WM7D callbook server on the internet
3210 and returns any information available for that US callsign. This service
3211 is provided for users of this software by http://www.wm7d.net.
3218 <bf>show/wwv</bf> Show last 10 WWV broadcasts
3222 <sect1>show/wwv <n>
3226 <bf>show/wwv <n></bf> Show last <n> WWV broadcasts
3230 Display the most recent WWV information that has been received by the system
3235 <bf>sysop</bf> Regain your privileges if you login remotely
3239 The system automatically reduces your privilege level to that of a
3240 normal user if you login in remotely. This command allows you to
3241 regain your normal privilege level. It uses the normal system: five
3242 numbers are returned that are indexes into the character array that is
3243 your assigned password (see SET/PASSWORD). The indexes start from
3246 You are expected to return a string which contains the characters
3247 required in the correct order. You may intersperse those characters
3248 with others to obscure your reply for any watchers. For example (and
3249 these values are for explanation :-):
3252 password = 012345678901234567890123456789
3258 aa2bbbb0ccc5ddd7xxx3n
3263 They will all match. If there is no password you will still be offered
3264 numbers but nothing will happen when you input a string. Any match is
3266 <sect1>talk <call> > <node> [<text>]
3270 <bf>talk <call> > <node> [<text>]</bf> Send a text message to another station via a node
3274 Send a short message to any other station that is visible on the cluster
3275 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
3276 command, they don't have to be connected locally.
3278 The second form of TALK is used when other cluster nodes are connected
3279 with restricted information. This usually means that they don't send
3280 the user information usually associated with logging on and off the cluster.
3282 If you know that G3JNB is likely to be present on GB7TLH, but you can only
3283 see GB7TLH in the SH/C list but with no users, then you would use the
3284 second form of the talk message.
3286 If you want to have a ragchew with someone you can leave the text message
3287 out and the system will go into 'Talk' mode. What this means is that a
3288 short message is sent to the recipient telling them that you are in a
3289 'Talking' frame of mind and then you just type - everything you send will
3290 go to the station that you asked for.
3292 All the usual announcements, spots and so on will still come out on your
3295 If you want to do something (such as send a spot) you preceed the normal
3296 command with a '/' character, eg:-
3299 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
3303 To leave talk mode type:
3309 If you are in 'Talk' mode, there is an extention to the '/' command which
3310 allows you to send the output to all the people you are talking to. You do
3311 with the '//' command. For example:-
3317 will send the hftable as you have it to all the people you are currently
3319 <sect1>talk <call> [<text>]
3323 <bf>talk <call> [<text>]</bf> Send a text message to another station
3327 <sect1>type <filearea>/<name>
3331 <bf>type <filearea>/<name></bf> Look at the contents of a file in one of the fileareas
3335 Type out the contents of a file in a filearea. So, for example, in
3336 filearea 'bulletins' you want to look at file 'arld051' you would
3339 TYPE bulletins/arld051
3342 See also SHOW/FILES to see what fileareas are available and a
3344 <sect1>unset/announce
3348 <bf>unset/announce</bf> Stop announce messages coming out on your terminal
3352 <sect1>unset/anntalk
3356 <bf>unset/anntalk</bf> Stop talk like announce messages on your terminal
3360 The announce system on legacy cluster nodes is used as a talk
3361 substitute because the network is so poorly connected. If you:
3367 you will suppress several of these announces, you may miss the odd
3368 useful one as well, but you would probably miss them anyway in the
3369 welter of useless ones.
3375 allows you to see them again. This is the default.
3380 <bf>unset/beep</bf> Stop beeps for DX and other messages on your terminal
3388 <bf>unset/dx</bf> Stop DX messages coming out on your terminal
3396 <bf>unset/dxcq</bf> Stop CQ Zones on the end of DX announcements
3400 Display both the Spotter's and the Spotted's CQ Zone on the end
3401 of a DX announcement (there is just enough room). Some user programs
3402 cannot cope with this. The Spotter's CQ is on the RHS of the
3403 time, the Spotted's CQ is on the LHS.
3405 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
3407 Do a STAT/USER to see which flags you have set if you are confused.
3412 <bf>unset/dxgrid</bf> Stop QRA Grid Squares on the end of DX announcements
3416 A standard feature which is enabled in version 1.43 and above is
3417 that if the spotter's grid square is known it is output on the end
3418 of a DX announcement (there is just enough room). Some user programs
3419 cannot cope with this. You can use this command to reset (or set)
3422 Conflicts with: SET/DXCQ, SET/DXITU
3424 Do a STAT/USER to see which flags you have set if you are confused.
3429 <bf>unset/dxitu</bf> Stop ITU Zones on the end of DX announcements
3433 Display both the Spotter's and the Spotted's ITU Zone on the end
3434 of a DX announcement (there is just enough room). Some user programs
3435 cannot cope with this. The Spotter's ITU is on the RHS of the
3436 time, the Spotted's ITU is on the LHS.
3438 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
3440 Do a STAT/USER to see which flags you have set if you are confused.
3445 <bf>unset/echo</bf> Stop the cluster echoing your input
3449 If you are connected via a telnet session, different implimentations
3450 of telnet handle echo differently depending on whether you are
3451 connected via port 23 or some other port. You can use this command
3452 to change the setting appropriately.
3454 The setting is stored in your user profile.
3456 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
3461 <bf>unset/email</bf> Stop personal msgs being forwarded by email
3465 If any personal messages come in for your callsign then you can use
3466 these commands to control whether they are forwarded onto your email
3467 address. To enable the forwarding do something like:-
3470 SET/EMAIL mike.tubby@somewhere.com
3473 You can have more than one email address (each one separated by a space).
3474 Emails are forwarded to all the email addresses you specify.
3476 You can disable forwarding by:-
3486 <bf>unset/here</bf> Tell the system you are absent from your terminal
3490 <sect1>unset/logininfo
3494 <bf>unset/logininfo</bf> Inform when a station logs out locally
3498 <sect1>unset/privilege
3502 <bf>unset/privilege</bf> Remove any privilege for this session
3506 You can use this command to 'protect' this session from unauthorised
3507 use. If you want to get your normal privilege back you will need to
3508 either logout and login again (if you are on a console) or use the
3514 <bf>unset/prompt</bf> Set your prompt back to default
3518 This command will set your user prompt to exactly the string that you
3519 say. The point of this command to enable a user to interface to programs
3520 that are looking for a specific prompt (or else you just want a different
3527 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
3533 <bf>unset/talk</bf> Stop TALK messages coming out on your terminal
3537 <sect1>unset/usstate
3541 <bf>unset/usstate</bf> Stop US State info on the end of DX announcements
3545 If the spotter's or spotted's US State is known it is output on the
3546 end of a DX announcement (there is just enough room).
3548 A spotter's state will appear on the RHS of the time (like
3549 SET/DXGRID) and the spotted's State will appear on the LHS of the
3550 time field. Any information found will override any locator
3551 information from SET/DXGRID.
3553 Some user programs cannot cope with this. You can use this command
3554 to reset (or set) this feature.
3556 Conflicts with: SET/DXCQ, SET/DXITU
3558 Do a STAT/USER to see which flags you have set if you are confused.
3563 <bf>unset/wcy</bf> Stop WCY messages coming out on your terminal
3571 <bf>unset/wwv</bf> Stop WWV messages coming out on your terminal
3579 <bf>unset/wx</bf> Stop WX messages coming out on your terminal
3587 <bf>who</bf> Show who is physically connected
3591 This is a quick listing that shows which callsigns are connected and
3592 what sort of connection they have
3593 <sect1>wx <text>
3597 <bf>wx <text></bf> Send a weather message to local users
3601 <sect1>wx full <text>
3605 <bf>wx full <text></bf> Send a weather message to all cluster users
projects / spider.git / blob