2 # please put your help in in alphabetical order
4 # a string search is done in the command field (case is ignored)
5 # and all commands matching the asked for command are printed out
7 # the order of the fields in each header is
8 # privilege, command, Description
9 # if the command ends in a - then that line isn't printed, but any
10 # subsequent lines are
12 # Comment lines are indented before printing
14 === 0^ACCEPT/ANNOUNCE [0-9] <pattern>^Set an 'accept' filter line for announce
15 Create an 'accept this announce' line for a filter.
17 An accept filter line means that if the announce matches this filter it is
18 passed onto the user. See HELP FILTERING for more info. Please read this
19 to understand how filters work - it will save a lot of grief later on.
21 You can use any of the following things in this line:-
23 info <string> eg: iota or qsl
24 by <prefixes> eg: G,M,2
26 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
27 origin_itu <prefixes or numbers> or: G,GM,GW
28 origin_zone <prefixes or numbers>
29 by_dxcc <prefixes or numbers>
30 by_itu <prefixes or numbers>
31 by_zone <prefixes or numbers>
33 wx 1 filter WX announces
34 dest <prefixes> eg: 6MUK,WDX (distros)
39 acc/ann 2 by_zone 14,15,16
40 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
44 You can use the tag 'all' to accept everything eg:
48 but this probably for advanced users...
50 === 8^ACCEPT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
51 This version allows a sysop to set a filter for a callsign as well as the
52 default for nodes and users eg:-
55 accept/ann input node_default by G,M,2
56 accept/ann user_default by G,M,2
58 === 8^ACCEPT/ROUTE <call> [0-9] <pattern>^Set an 'accept' filter line for routing
59 Create an 'accept this routing PC Protocol' line for a filter.
61 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
62 it is passed thru that interface. See HELP FILTERING for more info. Please read this
63 to understand how filters work - it will save a lot of grief later on.
65 You can use any of the following things in this line:-
67 call <prefixes> the callsign of the thingy
68 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
69 call_itu <prefixes or numbers> or: G,GM,GW
70 call_zone <prefixes or numbers>
71 origin <prefixes> really the interface it came in on
72 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
73 origin_itu <prefixes or numbers> or: G,GM,GW
74 origin_zone <prefixes or numbers>
78 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
79 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
81 You can use the tag 'all' to accept everything eg:
86 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
87 Create an 'accept this spot' line for a filter.
89 An accept filter line means that if the spot matches this filter it is
90 passed onto the user. See HELP FILTERING for more info. Please read this
91 to understand how filters work - it will save a lot of grief later on.
93 You can use any of the following things in this line:-
95 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
96 on <range> same as 'freq'
97 call <prefixes> eg: G,PA,HB9
98 info <string> eg: iota or qsl
100 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
101 call_itu <prefixes or numbers> or: G,GM,GW
102 call_zone <prefixes or numbers>
103 by_dxcc <prefixes or numbers>
104 by_itu <prefixes or numbers>
105 by_zone <prefixes or numbers>
109 For frequencies, you can use any of the band names defined in
110 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
111 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
112 this is more efficient than saying simply: freq HF (but don't get
113 too hung up about that)
118 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
120 You can use the tag 'all' to accept everything, eg:
124 but this probably for advanced users...
127 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
128 This version allows a sysop to set a filter for a callsign as well as the
129 default for nodes and users eg:-
131 accept/spot db0sue-7 1 by_zone 14,15,16
132 accept/spot node_default all
133 set/hops node_default 10
135 accept/spot user_default by G,M,2
137 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
138 It is unlikely that you will want to do this, but if you do then you can
139 filter on the following fields:-
141 by <prefixes> eg: G,M,2
143 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
144 origin_itu <prefixes or numbers> or: G,GM,GW
145 origin_zone <prefixes or numbers>
146 by_dxcc <prefixes or numbers>
147 by_itu <prefixes or numbers>
148 by_zone <prefixes or numbers>
151 There are no examples because WCY Broadcasts only come from one place and
152 you either want them or not (see UNSET/WCY if you don't want them).
154 This command is really provided for future use.
156 See HELP FILTER for information.
158 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
159 This version allows a sysop to set a filter for a callsign as well as the
160 default for nodes and users eg:-
162 accept/wcy node_default all
163 set/hops node_default 10
165 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
166 It is unlikely that you will want to do this, but if you do then you can
167 filter on the following fields:-
169 by <prefixes> eg: G,M,2
171 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
172 origin_itu <prefixes or numbers> or: G,GM,GW
173 origin_zone <prefixes or numbers>
174 by_dxcc <prefixes or numbers>
175 by_itu <prefixes or numbers>
176 by_zone <prefixes or numbers>
183 is probably the only useful thing to do (which will only show WWV broadcasts
184 by stations in the US).
186 See HELP FILTER for information.
188 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
189 This version allows a sysop to set a filter for a callsign as well as the
190 default for nodes and users eg:-
192 accept/wwv db0sue-7 1 by_zone 4
193 accept/wwv node_default all
194 set/hops node_default 10
196 accept/wwv user_default by W,K
198 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
199 <text> is the text of the announcement you wish to broadcast
201 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
202 This will send your announcement cluster wide
204 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
206 === 0^APROPOS <string>^Search help database for <string>
207 Search the help database for <string> (it isn't case sensitive), and print
208 the names of all the commands that may be relevant.
210 === 0^BLANK <nn>^Print nn (default 1) blank lines
212 === 0^BYE^Exit from the cluster
213 This will disconnect you from the cluster
215 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
216 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
217 When you send messages the fact that you have forwarded it to another node
218 is remembered so that it isn't sent again. When you have a new partner
219 node and you add their callsign to your /spider/msg/forward.pl file, all
220 outstanding non-private messages will be forwarded to them. This may well
221 be ALL the non-private messages. You can prevent this by using these
225 catchup GB7DJK 300 301 302 303 500-510
227 and to undo what you have just done:-
230 uncatchup GB7DJK 300 301 302 303 500-510
232 which will arrange for them to be forward candidates again.
234 Order is not important.
236 === 0^CLEAR/ANNOUNCE [1|all]^Clear a announce filter line
237 This command allows you to clear (remove) a line in a annouce filter or to
238 remove the whole filter.
240 see CLEAR/SPOTS for a more detailed explanation.
242 === 8^CLEAR/ANNOUNCE [input] <callsign> [0-9|all]^Clear a announce filter line
243 A sysop can clear an input or normal output filter for a user or the
244 node_default or user_default.
246 === 0^CLEAR/ROUTE [1|all]^Clear a route filter line
247 This command allows you to clear (remove) a line in a route filter or to
248 remove the whole filter.
250 see CLEAR/SPOTS for a more detailed explanation.
252 === 8^CLEAR/ROUTE [input] <callsign> [0-9|all]^Clear a route filter line
253 A sysop can clear an input or normal output filter for a user or the
254 node_default or user_default.
256 === 0^CLEAR/SPOTS [0-9|all]^Clear a spot filter line
257 This command allows you to clear (remove) a line in a spot filter or to
258 remove the whole filter.
260 If you have a filter:-
263 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
269 you will be left with:-
271 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
277 the filter will be completely removed.
279 === 8^CLEAR/SPOTS [input] <callsign> [0-9|all]^Clear a spot filter line
280 A sysop can clear an input or normal output filter for a user or the
281 node_default or user_default.
283 === 0^CLEAR/WCY [1|all]^Clear a WCY filter line
284 This command allows you to clear (remove) a line in a WCY filter or to
285 remove the whole filter.
287 see CLEAR/SPOTS for a more detailed explanation.
289 === 8^CLEAR/WCY [input] <callsign> [0-9|all]^Clear a WCY filter line
290 A sysop can clear an input or normal output filter for a user or the
291 node_default or user_default.
293 === 0^CLEAR/WWV [1|all]^Clear a WWV filter line
294 This command allows you to clear (remove) a line in a WWV filter or to
295 remove the whole filter.
297 see CLEAR/SPOTS for a more detailed explanation.
299 === 8^CLEAR/WWV [input] <callsign> [0-9|all]^Clear a WWV filter line
300 A sysop can clear an input or normal output filter for a user or the
301 node_default or user_default.
303 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
304 Start a connection process that will culminate in a new connection to the
305 DX cluster <callsign>. This process creates a new 'client' process which will
306 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
307 necessary to traverse the network(s) to logon to the cluster <callsign>.
309 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
310 This command will completely remove a one or more users from the database.
312 There is NO SECOND CHANCE.
314 It goes without saying that you should use this command CAREFULLY!
316 === 0^DBAVAIL^Show a list of all the Databases in the system
317 Title says it all really, this command lists all the databases defined
318 in the system. It is also aliased to SHOW/COMMAND.
320 === 9^DBCREATE <name>^Create a database entry
321 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
322 === 9^DBCREATE <name> remote <node>^Create a remote database entry
323 DBCREATE allows you to define a database in the system. It doesn't actually
324 create anything, just defines it.
326 The databases that are created are simple DB_File hash databases, they are
327 therefore already 'indexed'.
329 You can define a local database with the first form of the command eg:
333 You can also chain databases with the addition of the 'chain' keyword.
334 This will search each database one after the other. A typical example
337 DBCREATE sdx_qsl chain sql_ad
339 No checking is done to see if the any of the chained databases exist, in
340 fact it is usually better to do the above staement first then do each of
341 the chained databases.
343 Databases can exist offsite. To define a database that lives on another
346 DBCREATE buckmaster remote gb7dxc
348 Remote databases cannot be chained; however, the last database in a
349 a chain can be a remote database eg:
351 DBCREATE qsl chain gb7dxc
353 To see what databases have been defined do:
355 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
357 It would be normal for you to add an entry into your local Aliases file
358 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
359 need to add a line like:-
364 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
373 to work as they may be used to.
375 See DBIMPORT for the importing of existing AK1A format data to databases.
376 See DBSHOW for generic database enquiry
378 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
379 If you want to import or update data in bulk to a database you can use
380 this command. It will either create or update entries into an existing
381 database. For example:-
383 DBIMPORT oblast /tmp/OBLAST.FUL
385 will import the standard OBLAST database that comes with AK1A into the
386 oblast database held locally.
388 === 9^DBREMOVE <dbname>^Delete a database
389 DBREMOVE will completely remove a database entry and also delete any data
390 file that is associated with it.
392 There is no warning, no comeback, no safety net.
398 will remove the oblast database from the system and it will also remove
399 the associated datafile.
403 There is no warning, no comeback, no safety net.
405 You have been warned.
407 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
408 This is the generic user interface to the database to the database system.
409 It is expected that the sysop will add an entry to the local Aliases file
410 so that users can use the more familiar AK1A style of enquiry such as:
414 but if he hasn't and the database really does exist (use DBAVAIL or
415 SHOW/COMMAND to find out) you can do the same thing with:
419 === 9^DEBUG^Set the cluster program into debug mode
420 Executing this command will only have an effect if you are running the cluster
425 It will interrupt the cluster just after the debug command has finished.
427 === 0^DIRECTORY^List messages
428 === 0^DIRECTORY ALL^List all messages
429 === 0^DIRECTORY OWN^List your own messages
430 === 0^DIRECTORY NEW^List all new messages
431 === 0^DIRECTORY TO <call>^List all messages to <call>
432 === 0^DIRECTORY FROM <call>^List all messages from <call>
433 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
434 === 0^DIRECTORY <nn>^List last <nn> messages
435 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
436 List the messages in the messages directory.
438 If there is a 'p' one space after the message number then it is a
439 personal message. If there is a '-' between the message number and the
440 'p' then this indicates that the message has been read.
442 You can use shell escape characters such as '*' and '?' in the <call>
445 You can combine some of the various directory commands together eg:-
449 DIR SUBJECT IOTA 200-250
451 You can abbreviate all the commands to one letter and use ak1a syntax:-
457 Sysops can see all users' messages.
459 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
460 Disconnect any <call> connected locally
462 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
463 This is how you send a DX Spot to other users. You can, in fact, now
464 enter the <freq> and the <call> either way round.
470 will all give the same result. You can add some remarks to the end
471 of the command and they will be added to the spot.
473 DX FR0G 144600 this is a test
475 You can credit someone else by saying:-
477 DX by G1TLH FR0G 144.600 he isn't on the cluster
479 The <freq> is compared against the available bands set up in the
480 cluster. See SHOW/BANDS for more information.
482 === 9^EXPORT <msgno> <filename>^Export a message to a file
483 Export a message to a file. This command can only be executed on a local
484 console with a fully privileged user. The file produced will be in a form
485 ready to be imported back into the cluster by placing it in the import
486 directory (/spider/msg/import).
488 This command cannot overwrite an existing file. This is to provide some
489 measure of security. Any files written will owned by the same user as the
490 main cluster, otherwise you can put the new files anywhere the cluster can
491 access. For example:-
495 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
496 Export the users database to a file in ascii format. If no filename
497 is given then it will export the file to /spider/data/user_asc.
499 If the file already exists it will be renamed to <filename>.o. In fact
500 up to 5 generations of the file can be kept each one with an extra 'o' on the
503 BE WARNED: this will write to any file you have write access to. No check is
504 made on the filename (if any) that you specify.
506 === 0^FILTERING...^Filtering things in DXSpider
507 There are a number of things you can filter in the DXSpider system. They
508 all use the same general mechanism.
510 In general terms you can create a 'reject' or an 'accept' filter which
511 can have up to 10 lines in it. You do this using, for example:-
516 where ..... are the specific commands for that type of filter. There
517 are filters for spots, wwv, announce, wcy and (for sysops)
518 connects. See each different accept or reject command reference for
521 There is also a command to clear out one or more lines in a filter and
522 one to show you what you have set. They are:-
531 There is clear/xxxx command for each type of filter.
533 For now we are going to use spots for the examples, but you can apply
534 the principles to all types of filter.
536 There are two main types of filter 'accept' or 'reject'; which you use
537 depends entirely on how you look at the world and what is least
538 writing to achieve what you want. Each filter has 10 lines (of any
539 length) which are tried in order. If a line matches then the action
540 you have specified is taken (ie reject means ignore it and accept
543 The important thing to remember is that if you specify a 'reject'
544 filter (all the lines in it say 'reject/spots' (for instance) then if
545 a spot comes in that doesn't match any of the lines then you will get
546 it BUT if you specify an 'accept' filter then any spots that don't
547 match are dumped. For example if I have a one line accept filter:-
549 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
551 then automatically you will ONLY get VHF spots from or to CQ zones 14
552 15 and 16. If you set a reject filter like:
554 reject/spots on hf/cw
556 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
557 and will work it even on CW then you could say:-
559 reject/spots on hf/cw and not info iota
561 But in that case you might only be interested in iota and say:-
563 accept/spots not on hf/cw or info iota
565 which is exactly the same. You should choose one or the other until
566 you are confortable with the way it works. Yes, you can mix them
567 (actually you can have an accept AND a reject on the same line) but
568 don't try this at home until you can analyse the results that you get
569 without ringing up the sysop for help.
571 You can arrange your filter lines into logical units, either for your
572 own understanding or simply convenience. I have one set frequently:-
574 reject/spots 1 on hf/cw
575 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
577 What this does is to ignore all HF CW spots (being a class B I can't
578 read any CW and couldn't possibly be interested in HF :-) and also
579 rejects any spots on VHF which don't either originate or spot someone
582 This is an exmaple where you would use the line number (1 and 2 in
583 this case), if you leave the digit out, the system assumes '1'. Digits
584 '0'-'9' are available.
586 You can leave the word 'and' out if you want, it is implied. You can
587 use any number of brackets to make the 'expression' as you want
588 it. There are things called precedence rules working here which mean
589 that you will NEED brackets in a situation like line 2 because,
590 without it, will assume:-
592 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
594 annoying, but that is the way it is. If you use OR - use
595 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
598 If you want to alter your filter you can just redefine one or more
599 lines of it or clear out one line. For example:-
601 reject/spots 1 on hf/ssb
607 To remove the filter in its entirty:-
611 There are similar CLEAR commands for the other filters:-
619 Once you are happy with the results you get, you may like to experiment.
621 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
622 can be written with a mixed filter, eg:
626 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
628 each filter slot actually has a 'reject' slot and an 'accept'
629 slot. The reject slot is executed BEFORE the accept slot.
631 It was mentioned earlier that after a reject test that doesn't match,
632 the default for following tests is 'accept', the reverse is true for
633 'accept'. In the example what happens is that the reject is executed
634 first, any non hf/cw spot is passed to the accept line, which lets
635 thru everything else on HF.
637 The next filter line lets through just VHF/UHF spots from EU.
639 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
640 This command sends all the latitude and longitude information that your
641 cluster is holding against callsigns. One advantage of recieving this
642 information is that more locator information is held by you. This
643 means that more locators are given on the DX line assuming you have
644 SET/DXGRID enabled. This could be a LOT of information though, so
645 it is not recommended on slow links.
647 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
648 This command sends out any information held in the user file which can
649 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
650 and Homenode. PC41s are only sent for the information that is available.
652 === 0^HELP^The HELP Command
653 HELP is available for a number of commands. The syntax is:-
657 Where <cmd> is the name of the command you want help on.
659 All commands can be abbreviated, so SHOW/DX can be abbreviated
660 to SH/DX, ANNOUNCE can be shortened to AN and so on.
662 Look at the APROPOS <string> command which will search the help database
663 for the <string> you specify and give you a list of likely commands
664 to look at with HELP.
666 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
667 This command attempts to re-initialise a link to a (usually) AK1A node
668 that has got confused, usually by a protocol loop of some kind. It may
669 work - but you usually will be better off simply disconnecting it (or
670 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
673 Best of luck - you will need it.
675 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
676 Delete a message from the local system. You will only be able to
677 delete messages that you have originated or been sent (unless you are
680 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
681 Delete a message (usually a 'bulletin') from the whole cluster system.
683 This uses the subject field, so any messages that have exactly the
684 same subject will be deleted. Beware!
686 === 0^LINKS^Show which nodes is physically connected
687 This is a quick listing that shows which links are connected and
688 some information about them. See WHO for a list of all connections.
690 === 9^LOAD/ALIASES^Reload the command alias table
691 Reload the /spider/cmd/Aliases file after you have editted it. You
692 will need to do this if you change this file whilst the cluster is
693 running in order for the changes to take effect.
695 === 9^LOAD/BANDS^Reload the band limits table
696 Reload the /spider/data/bands.pl file if you have changed it manually whilst
697 the cluster is running.
699 === 9^LOAD/BADMSG^Reload the bad msg table
700 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
701 the cluster is running. This table contains a number of perl regular
702 expressions which are searched for in the fields targetted of each message.
703 If any of them match then that message is immediately deleted on receipt.
705 === 9^LOAD/BADWORDS^Reload the bad words table
706 Reload the /spider/data/badwords file if you have changed it manually whilst
707 the cluster is running. This file contains a list of words which, if found
708 on certain text portions of PC protocol, will cause those protocol frames
709 to be rejected. It will all put out a message if any of these words are
710 used on the announce, dx and talk commands. The words can be one or
711 more on a line, lines starting with '#' are ignored.
713 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
714 Normally, if you change a command file in the cmd or local_cmd tree it
715 will automatially be picked up by the cluster program. Sometimes it
716 can get confused if you are doing a lot of moving commands about or
717 delete a command in the local_cmd tree and want to use the normal one
718 again. Execute this command to reset everything back to the state it
719 was just after a cluster restart.
721 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
722 Reload the /spider/msg/forward.pl file if you have changed it
723 manually whilst the cluster is running.
725 === 9^LOAD/MESSAGES^Reload the system messages file
726 If you change the /spider/perl/Messages file (usually whilst
727 fiddling/writing new commands) you can have them take effect during a
728 cluster session by executing this command. You need to do this if get
731 unknown message 'xxxx' in lang 'en'
733 === 9^LOAD/PREFIXES^Reload the prefix table
734 Reload the /spider/data/prefix_data.pl file if you have changed it
735 manually whilst the cluster is running.
737 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
738 MERGE allows you to bring your spot and wwv database up to date. By default
739 it will request the last 10 spots and 5 WWVs from the node you select. The
740 node must be connected locally.
742 You can request any number of spots or wwv and although they will be appended
743 to your databases they will not duplicate any that have recently been added
744 (the last 2 days for spots and last month for WWV data).
746 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
747 Alter message parameters like To, From, Subject, whether private or bulletin
748 or return receipt (RR) is required or whether to keep this message from timing
751 MSG TO <msgno> <call> - change TO callsign to <call>
752 MSG FRom <msgno> <call> - change FROM callsign to <call>
753 MSG PRrivate <msgno> - set private flag
754 MSG NOPRrivate <msgno> - unset private flag
755 MSG RR <msgno> - set RR flag
756 MSG NORR <msgno> - unset RR flag
757 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
758 MSG NOKEep <msgno> - unset the keep flag
759 MSG SUbject <msgno> <new> - change the subject to <new>
760 MSG WAittime <msgno> - remove any waitting time for this message
761 MSG NOREad <msgno> - mark message as unread
762 MSG REad <msgno> - mark message as read
763 MSG QUeue - queue any outstanding bulletins
764 MSG QUeue 1 - queue any outstanding private messages
766 You can look at the status of a message by using:-
770 This will display more information on the message than DIR does.
772 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
773 Send some arbitrary text to a locally connected callsign. No
774 processing is done on the text. This command allows you to send PC
775 Protocol to unstick things if problems arise (messages get stuck
778 pc gb7djk PC33^GB7TLH^GB7DJK^400^
780 pc G1TLH Try doing that properly!!!
782 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
783 You can get rid of any message to or originating from your callsign using
784 this command. You can remove more than one message at a time.
786 === 5^KILL <from>-<to>^Remove a range of messages from the system
787 === 5^KILL FROM <call>^Remove all messages from a callsign
788 === 5^KILL TO <call>^Remove all messages to a callsign
789 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
790 Remove this message from the entire cluster system as well as your node.
793 As a sysop you can kill any message on the system.
795 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
796 Send any text you like to the callsign requested. This is used mainly to send
797 PC protocol to connected nodes either for testing or to unstick things.
799 You can also use in the same way as a talk command to a connected user but
800 without any processing, added of "from <blah> to <blah" or whatever.
802 === 1^PING <node call>^Check the link quality between nodes
803 This command allows you to send a frame to another cluster node on
804 the network and get a return frame. The time it takes to do this
805 is a good indication of the quality of the link. The actual time
806 it takes is output to the console in seconds.
807 Any visible cluster node can be PINGed.
809 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
810 This command allows you to send nearly any command to another DX Cluster
811 node that is connected to the system.
813 Whether you get any output is dependant on a) whether the other system knows
814 that the node callsign of this cluster is in fact a node b) whether the
815 other system is allowing RCMDs from this node and c) whether you have
816 permission to send this command at all.
818 === 0^READ^Read the next unread personal message addressed to you
819 === 0^READ <msgno>^Read the specified message
820 You can read any messages that are sent as 'non-personal' and also any
821 message either sent by or sent to your callsign.
824 As a sysop you may read any message on the system
826 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
827 Create an 'reject this announce' line for a filter.
829 A reject filter line means that if the announce matches this filter it is
830 passed onto the user. See HELP FILTERING for more info. Please read this
831 to understand how filters work - it will save a lot of grief later on.
833 You can use any of the following things in this line:-
835 info <string> eg: iota or qsl
836 by <prefixes> eg: G,M,2
838 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
839 origin_itu <prefixes or numbers> or: G,GM,GW
840 origin_zone <prefixes or numbers>
841 by_dxcc <prefixes or numbers>
842 by_itu <prefixes or numbers>
843 by_zone <prefixes or numbers>
845 wx 1 filter WX announces
846 dest <prefixes> eg: 6MUK,WDX (distros)
850 rej/ann by_zone 14,15,16 and not by G,M,2
852 You can use the tag 'all' to reject everything eg:
856 but this probably for advanced users...
858 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
859 This version allows a sysop to set a filter for a callsign as well as the
860 default for nodes and users eg:-
863 reject/ann input node_default by G,M,2
864 reject/ann user_default by G,M,2
866 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
867 Create a 'reject this spot' line for a filter.
869 A reject filter line means that if the spot matches this filter it is
870 dumped (not passed on). See HELP FILTERING for more info. Please read this
871 to understand how filters work - it will save a lot of grief later on.
873 You can use any of the following things in this line:-
875 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
876 on <range> same as 'freq'
877 call <prefixes> eg: G,PA,HB9
878 info <string> eg: iota or qsl
880 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
881 call_itu <prefixes or numbers> or: G,GM,GW
882 call_zone <prefixes or numbers>
883 by_dxcc <prefixes or numbers>
884 by_itu <prefixes or numbers>
885 by_zone <prefixes or numbers>
889 For frequencies, you can use any of the band names defined in
890 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
891 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
892 this is more efficient than saying simply: on HF (but don't get
893 too hung up about that)
898 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
900 You can use the tag 'all' to reject everything eg:
904 but this probably for advanced users...
906 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
907 Create an 'reject this routing PC Protocol' line for a filter.
909 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
910 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
911 read this to understand how filters work - it will save a lot of grief later on.
913 You can use any of the following things in this line:-
915 call <prefixes> the callsign of the thingy
916 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
917 call_itu <prefixes or numbers> or: G,GM,GW
918 call_zone <prefixes or numbers>
919 origin <prefixes> really the interface it came in on
920 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
921 origin_itu <prefixes or numbers> or: G,GM,GW
922 origin_zone <prefixes or numbers>
926 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
928 You can use the tag 'all' to reject everything eg:
930 rej/route all (equiv to [very] restricted mode)
932 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
933 This version allows a sysop to set a filter for a callsign as well as the
934 default for nodes and users eg:-
936 reject/spot db0sue-7 1 by_zone 14,15,16
937 reject/spot node_default all
938 set/hops node_default 10
940 reject/spot user_default by G,M,2
942 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
943 It is unlikely that you will want to do this, but if you do then you can
944 filter on the following fields:-
946 by <prefixes> eg: G,M,2
948 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
949 origin_itu <prefixes or numbers> or: G,GM,GW
950 origin_zone <prefixes or numbers>
951 by_dxcc <prefixes or numbers>
952 by_itu <prefixes or numbers>
953 by_zone <prefixes or numbers>
956 There are no examples because WCY Broadcasts only come from one place and
957 you either want them or not (see UNSET/WCY if you don't want them).
959 This command is really provided for future use.
961 See HELP FILTER for information.
963 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
964 This version allows a sysop to set a filter for a callsign as well as the
965 default for nodes and users eg:-
967 reject/wcy gb7djk all
969 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
970 It is unlikely that you will want to do this, but if you do then you can
971 filter on the following fields:-
973 by <prefixes> eg: G,M,2
975 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
976 origin_itu <prefixes or numbers> or: G,GM,GW
977 origin_zone <prefixes or numbers>
978 by_dxcc <prefixes or numbers>
979 by_itu <prefixes or numbers>
980 by_zone <prefixes or numbers>
985 reject/wwv by_zone 14,15,16
987 is probably the only useful thing to do (which will only show WWV broadcasts
988 by stations in the US).
990 See HELP FILTER for information.
992 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
993 This version allows a sysop to set a filter for a callsign as well as the
994 default for nodes and users eg:-
996 reject/wwv db0sue-7 1 by_zone 4
997 reject/wwv node_default all
999 reject/wwv user_default by W
1001 === 0^REPLY^Reply (privately) to the last message that you have read
1002 === 0^REPLY <msgno>^Reply (privately) to the specified message
1003 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1004 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1005 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1006 You can reply to a message and the subject will automatically have
1007 "Re:" inserted in front of it, if it isn't already present.
1009 You can also use all the extra qualifiers such as RR, PRIVATE,
1010 NOPRIVATE, B that you can use with the SEND command (see SEND
1011 for further details)
1013 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1014 === 0^SEND RR <call>^Send a message and ask for a read receipt
1015 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1016 === 0^SEND PRIVATE <call>^Send a personal message
1017 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1018 All the SEND commands will create a message which will be sent either to
1019 an individual callsign or to one of the 'bulletin' addresses.
1021 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1022 it will mark the message as personal and send it to the cluster node that
1023 that callsign is connected to.
1025 You can have more than one callsign in all of the SEND commands.
1027 You can have multiple qualifiers so that you can have for example:-
1029 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1031 which should send a copy of message 123 to G1TLH and G0RDI and you will
1032 receive a read receipt when they have read the message.
1034 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1035 SP is an alias for SEND PRIVATE
1037 === 0^SET/ADDRESS <your address>^Record your postal address
1039 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1040 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1042 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1043 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1044 The announce system on legacy cluster nodes is used as a talk
1045 substitute because the network is so poorly connected. If you:
1049 you will suppress several of these announces, you may miss the odd
1050 useful one as well, but you would probably miss them anyway in the
1051 welter of useless ones.
1055 allows you to see them again. This is the default.
1057 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1059 === 8^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1060 === 8^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1061 Setting a word as 'baddx' will prevent spots with that word in the
1062 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1063 further. They will not be displayed and they will not be sent onto
1066 The word must be written in full, no wild cards are allowed eg:-
1068 set/baddx FORSALE VIDEO FR0G
1070 To allow a word again, use the following command ...
1074 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1075 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1076 Setting a callsign as a 'badnode' will prevent spots from that node
1077 going any further. They will not be displayed and they will not be
1078 sent onto other nodes.
1080 The call must be a full eg:-
1084 will stop anything from K1TTT. If you want SSIDs as well then you must
1085 enter them specifically.
1089 will allow spots from him again.
1091 Use with extreme care. This command may well be superceeded by FILTERing.
1093 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1094 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1095 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1096 going any further. They will not be displayed and they will not be
1097 sent onto other nodes.
1099 The call must be written in full, no wild cards are allowed eg:-
1101 set/badspotter VE2STN
1103 will stop anything from VE2STN. If you want SSIDs as well then you must
1104 enter them specifically.
1106 unset/badspotter VE2STN
1108 will allow spots from him again.
1110 Use with extreme care. This command may well be superceded by FILTERing.
1112 === 8^SET/BADWORD <word>..^Stop things with this word being propagated
1113 === 8^UNSET/BADWORD <word>..^Propagate things with this word again
1114 Setting a word as a 'badword' will prevent things like spots,
1115 announces or talks with this word in the the text part from going any
1116 further. They will not be displayed and they will not be sent onto
1119 The word must be written in full, no wild cards are allowed eg:-
1121 set/badword annihilate annihilated annihilation
1123 will stop anything with these words in the text.
1125 unset/badspotter annihilated
1127 will allow text with this word again.
1129 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1130 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1132 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1134 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1136 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1137 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1138 You can choose to log several different levels. The levels are
1146 You can show what levels you are logging with SHOW/DEBUG
1148 === 0^SET/DX^Allow DX messages to come out on your terminal
1149 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1151 === 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements
1152 === 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements
1153 A standard feature which is enabled in version 1.43 and above is
1154 that if the spotter's grid square is known it is output on the end
1155 of a DX announcement (there is just enough room). Some user programs
1156 cannot cope with this. You can use this command to reset (or set)
1159 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1161 === 0^SET/ECHO^Make the cluster echo your input
1162 === 0^UNSET/ECHO^Stop the cluster echoing your input
1163 If you are connected via a telnet session, different implimentations
1164 of telnet handle echo differently depending on whether you are
1165 connected via port 23 or some other port. You can use this command
1166 to change the setting appropriately.
1168 The setting is stored in your user profile.
1170 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1172 === 0^SET/HERE^Tell the system you are present at your terminal
1173 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1175 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1176 Tell the cluster system where you normally connect to. Any Messages sent
1177 to you will normally find their way there should you not be connected.
1181 === 8^SET/HOPS <call> ann|spots|wwv|wcy <n>^Set hop count
1182 Set the hop count for a particular type of broadcast for a node.
1184 This command allows you to set up special hop counts for a node
1185 for currently: announce, spots, wwv and wcy broadcasts.
1188 set/hops gb7djk ann 10
1189 set/hops gb7mbc spots 20
1191 Set SHOW/HOPS for information on what is already set. This command
1192 creates a filter and works in conjunction with the filter system.
1194 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1195 Connect a node to your system in such a way that you are a full protocol
1196 member of its network and can see all spots on it, but nothing either leaks
1197 out from it nor goes back into from the rest of the nodes connected to you.
1199 You can potentially connect several nodes in this way.
1201 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1202 Remove isolation from a node - SET/ISOLATE
1204 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1205 You can select the language that you want the cluster to use. Currently
1206 the languages available are en (english) and nl (dutch).
1208 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1209 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1210 In order to get accurate headings and such like you must tell the system
1211 what your latitude and longitude is. If you have not yet done a SET/QRA
1212 then this command will set your QRA locator for you. For example:-
1213 SET/LOCATION 52 22 N 0 57 E
1215 === 0^SET/LOGININFO^Inform when a station logs in locally
1216 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1218 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1219 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1221 === 0^SET/NAME <your name>^Set your name
1222 Tell the system what your name is eg:-
1225 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1226 Tell the system that the call(s) are to be treated as AK1A cluster and
1227 fed PC Protocol rather normal user commands.
1229 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
1230 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1231 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1232 counter which is decremented on every outgoing ping and then reset to
1233 the 'obscount' value on every incoming ping. The default value of this
1236 What this means is that a neighbouring node will be pinged twice at
1237 (default) 300 second intervals and if no reply has been heard just before
1238 what would be the third attempt, that node is disconnected.
1240 If a ping is heard then the obscount is reset to the full value. Using
1241 default values, if a node has not responded to a ping within 15 minutes,
1244 You can set this parameter between 1 and 9.
1246 It is STRONGLY recommended that you don't change the default.
1248 === 0^SET/PAGE <lines per page>^Set the lines per page
1249 Tell the system how many lines you wish on a page when the number of line
1250 of output from a command is more than this. The default is 20. Setting it
1251 explicitly to 0 will disable paging.
1255 The setting is stored in your user profile.
1257 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1258 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1259 in order to determine the rolling quality of the link and, in future, to
1260 affect routing decisions. The default interval is 300 secs or 5 minutes.
1262 You can use this command to set a different interval. Please don't.
1264 But if you do the value you enter is treated as minutes up 30 and seconds
1265 for numbers greater than that.
1267 This is used also to help determine when a link is down at the far end
1268 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1269 for more information.
1271 If you must change it (and it may be useful for internet connected nodes
1272 on dynamic IP addresses that go away after a set time of usage) the time
1273 can be specified as:-
1275 5 which if less than 30 is converted to minutes otherwise is
1276 taken as the no of seconds between pings.
1281 Please be aware that this causes traffic to occur on the link, setting
1282 this value too low may annoy your neighbours beyond the point of
1285 You can switch this off by setting it to 0.
1287 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1288 Set the privilege level on a callsign. The privilege levels that pertain
1289 to commands are as default:-
1291 1 - allow remote nodes normal user RCMDs
1292 5 - various privileged commands (including shutdown, but not disc-
1293 connect), the normal level for another node.
1294 8 - more privileged commands (including disconnect)
1295 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1297 If you are a sysop and you come in as a normal user on a remote connection
1298 your privilege will automatically be set to 0.
1300 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1301 You can use this command to 'protect' this session from unauthorised
1302 use. If you want to get your normal privilege back you will need to
1303 either logout and login again (if you are on a console) or use the
1306 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1307 The password for a user can only be set by a full sysop. The string
1308 can contain any characters but any spaces are removed (you can type in
1309 spaces - but they won't appear in the password). You can see the
1310 result with STAT/USER.
1312 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1313 Tell the system that the call(s) are to be treated as DXSpider node and
1314 fed new style DX Protocol rather normal user commands.
1316 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
1317 === 0^SET/QRA <locator>^Set your QRA locator
1318 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1319 done a SET/LOCATION then your latitude and longitude will be set roughly
1320 correctly (assuming your locator is correct ;-). For example:-
1323 === 0^SET/QTH <your qth>^Set your QTH
1324 Tell the system where you are. For example:-
1325 SET/QTH East Dereham, Norfolk
1327 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1328 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1330 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1331 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1333 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1334 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1336 === 0^SET/WX^Allow WX messages to come out on your terminal
1337 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1339 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1340 Display all the bad dx callsigns in the system, see SET/BADDX
1341 for more information.
1343 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1344 Display all the bad node callsigns in the system, see SET/BADNODE
1345 for more information.
1347 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1348 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1349 for more information.
1351 === 1^SHOW/BADWORD^Show all the bad words in the system
1352 Display all the bad words in the system, see SET/BADWORD
1353 for more information.
1355 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1356 This command allows you to see all the users that can be seen
1357 and the nodes to which they are connected.
1359 This command is normally abbreviated to: sh/c
1361 BE WARNED: the list that is returned can be VERY long
1363 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1364 Show all the nodes connected to this node.
1366 === 1^SHOW/CONNECT^Show all the active connections
1367 This command shows information on all the active connections known to
1368 the node. This command gives slightly more information than WHO.
1370 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1371 This is very nearly the same as SHOW/TIME, the only difference the format
1372 of the date string if no arguments are given.
1374 If no prefixes or callsigns are given then this command returns the local
1375 time and UTC as the computer has it right now. If you give some prefixes
1376 then it will show UTC and UTC + the local offset (not including DST) at
1377 the prefixes or callsigns that you specify.
1379 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1381 === 0^SHOW/DX^Interrogate the spot database
1382 If you just type SHOW/DX you will get the last so many spots
1383 (sysop configurable, but usually 10).
1385 In addition you can add any number of these commands in very nearly
1386 any order to the basic SHOW/DX command, they are:-
1388 on <band> - eg 160m 20m 2m 23cm 6mm
1389 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1391 <number> - the number of spots you want
1392 <from>-<to> - <from> spot no <to> spot no in the selected list
1394 <prefix> - for a spotted callsign beginning with <prefix>
1395 *<suffix> - for a spotted callsign ending in <suffix>
1396 *<string>* - for a spotted callsign containing <string>
1398 day <number> - starting <number> days ago
1399 day <from>-<to> - <from> days <to> days ago
1401 info <text> - any spots containing <text> in the info or remarks
1403 by <call> - any spots spotted by <call> (spotter <call> is the
1406 qsl - this automatically looks for any qsl info on the call
1407 held in the spot database.
1409 iota [<iota>] - If the iota island number is missing it will look for
1410 the string iota and anything which looks like an iota
1411 island number. If you specify then it will look for
1414 qra [<locator>] - this will look for the specific locator if you specify
1415 one or else anything that looks like a locator.
1420 SH/DX on 20m info iota
1421 SH/DX 9a on vhf day 30
1427 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1428 This command takes the <prefix> (which can be a full or partial
1429 callsign if desired), looks up which internal country number it is
1430 and then displays all the spots as per SH/DX for that country.
1432 The options for SHOW/DX also apply to this command.
1436 SH/DXCC W on 20m info iota
1438 === 0^SHOW/DXSTATS^Show the DX Statistics for last 31 days
1439 Show the total DX spots for the last 31 days
1441 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1442 SHOW/FILES on its own will show you a list of the various fileareas
1443 available on the system. To see the contents of a particular file
1446 where <filearea> is the name of the filearea you want to see the
1449 You can also use shell globbing characters like '*' and '?' in a
1450 string to see a selection of files in a filearea eg:-
1451 SH/FILES bulletins arld*
1453 See also TYPE - to see the contents of a file.
1455 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1456 Show the contents of all the filters that are set. This command displays
1457 all the filters set - for all the various categories.
1459 === 0^SHOW/HFSTATS^Show the HF DX Statistics for last 31 days
1460 Show the HF DX spots breakdown by band for the last 31 days
1462 === 0^SHOW/HFTABLE^Show the HF DX Spotter Table for your country
1463 Show the HF DX Spotter table for your country for the last 31 days
1465 === 8^SHOW/HOPS <call> [ann|spots|wcy|wwv]^Show the hop counts for a node
1466 This command shows the hop counts set up for a node. You can specify
1467 which category you want to see. If you leave the category out then
1468 all the categories will be listed.
1470 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1472 === 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
1474 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
1475 This command outputs a short section of the system log. On its own
1476 it will output a general logfile. With the optional callsign it will
1477 show output from the log associated with that callsign.
1479 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
1480 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1481 together with the azimuth and elevation of the sun currently at those
1484 If you don't specify any prefixes or callsigns, it will show the times for
1485 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1486 together with the current azimuth and elevation.
1488 In addition, it will show the gain or loss dB relative to the nominal
1489 distance of 385,000Km due to the ellipsoidal nature of the orbit.
1491 If all else fails it will show the Moonrise and set times for the node
1492 that you are connected to.
1499 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1500 This command allow you to estimate the likelihood of you contacting
1501 a station with the prefix you have specified. The output assumes a modest
1502 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1504 The result predicts the most likely operating frequencies and signal
1505 levels for high frequency (shortwave) radio propagation paths on
1506 specified days of the year and hours of the day. It is most useful for
1507 paths between 250 km and 6000 km, but can be used with reduced accuracy
1508 for paths shorter or longer than this.
1510 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1511 used to predict the MUF given the predicted flux, day of the year,
1512 hour of the day and geographic coordinates of the transmitter and
1513 receiver. This routine is reasonably accurate for the purposes here,
1514 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1515 than the programs used by major shortwave broadcasting organizations,
1516 such as the Voice of America.
1518 The command will display some header information detailing its
1519 assumptions, together with the locations, latitude and longitudes and
1520 bearings. It will then show UTC (UT), local time at the other end
1521 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1522 (Zen) and the likely signal strengths. Then for each frequency for which
1523 the system thinks there is a likelihood of a circuit it prints a value.
1525 The value is currently a likely S meter reading based on the conventional
1526 6dB / S point scale. If the value has a '+' appended it means that it is
1527 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1528 there is likely to be much fading and by an 's' that the signal is likely
1531 By default SHOW/MUF will show the next two hours worth of data. You
1532 can specify anything up to 24 hours worth of data by appending the no of
1533 hours required after the prefix. For example:-
1539 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1540 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1541 Location Lat / Long Azim
1542 East Dereham, Norfolk 52 41 N 0 57 E 47
1543 United-States-W 43 0 N 87 54 W 299
1544 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1545 18 23 11.5 -35 mS0+ mS2 S3
1546 19 0 11.2 -41 mS0+ mS2 S3
1548 indicating that you will have weak, fading circuits on top band and
1549 80m but usable signals on 40m (about S3).
1555 will get you the above display, but with the next 24 hours worth of
1561 Gives you an estimate of the long path propagation characterics. It
1562 should be noted that the figures will probably not be very useful, nor
1563 terrible accurate, but it is included for completeness.
1565 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1566 Show the type and version (if connected) of the nodes specified on the
1567 command line. If no callsigns are specified then a sorted list of all
1568 the non-user callsigns known to the system will be displayed.
1570 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1571 This command takes the <callsign> (which can be a full or partial
1572 callsign or a prefix), looks up which internal country number
1573 it is and then displays all the relevant prefixes for that country
1574 together with the internal country no, the CQ and ITU regions.
1578 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1579 Show the name and location where every program module was load from. This
1580 is useful for checking where you think you have loaded a .pm file from.
1582 === 0^SHOW/QRA <locator> [<locator>]^Show distance between locators
1583 === 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
1584 This is a multipurpose command that allows you either to calculate the
1585 distance and bearing between two locators or (if only one locator is
1586 given on the command line) the distance and beraing from your station
1587 to the locator. For example:-
1592 The first example will show the distance and bearing to the locator from
1593 yourself, the second example will calculate the distance and bearing from
1594 the first locator to the second. You can use 4 or 6 character locators.
1596 It is also possible to convert a latitude and longitude to a locator by
1597 using this command with a latitude and longitude as an argument, for
1600 SH/QRA 52 41 N 0 58 E
1602 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
1603 This command queries the QRZ callbook server on the internet
1604 and returns any information available for that callsign. This service
1605 is provided for users of this software by http://www.qrz.com
1607 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
1608 This command allows you to see to which node the callsigns specified are
1609 connected. It is a sort of inverse sh/config.
1613 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1614 Show the tracking data from your location to the satellite of your choice
1615 from now on for the next few hours.
1617 If you use this command without a satellite name it will display a list
1618 of all the satellites known currently to the system.
1620 If you give a name then you can obtain tracking data of all the passes
1621 that start and finish 5 degrees below the horizon. As default it will
1622 give information for the next three hours for every five minute period.
1624 You can alter the number of hours and the step size, within certain
1627 Each pass in a period is separated with a row of '-----' characters
1632 SH/SAT FENGYUN1 12 2
1634 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
1635 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
1636 Show the information known about a callsign and whether (and where)
1637 that callsign is connected to the cluster.
1641 If no callsign is given then show the information for yourself.
1643 === 0^SHOW/SUN [<prefix>|<callsign>]^Show sun rise and set times
1644 Show the sun rise and set times for a (list of) prefixes or callsigns,
1645 together with the azimuth and elevation of the sun currently at those
1648 If you don't specify any prefixes or callsigns, it will show the times for
1649 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1650 together with the current azimuth and elevation.
1652 If all else fails it will show the sunrise and set times for the node
1653 that you are connected to.
1658 SH/SUN G1TLH K9CW ZS
1660 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
1661 If no prefixes or callsigns are given then this command returns the local
1662 time and UTC as the computer has it right now. If you give some prefixes
1663 then it will show UTC and UTC + the local offset (not including DST) at
1664 the prefixes or callsigns that you specify.
1666 === 0^SHOW/VHFSTATS^Show the VHF DX Statistics for last 31 days
1667 Show the VHF DX spots breakdown by band for the last 31 days
1669 === 0^SHOW/VHFTABLE^Show the VHF DX Spotter Table for your country
1670 Show the VHF DX Spotter table for your country for the last 31 days
1672 === 0^SHOW/WCY^Show last 10 WCY broadcasts
1673 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
1674 Display the most recent WCY information that has been received by the system
1676 === 0^SHOW/WWV^Show last 10 WWV broadcasts
1677 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
1678 Display the most recent WWV information that has been received by the system
1680 === 5^SHUTDOWN^Shutdown the cluster
1681 Shutdown the cluster and disconnect all the users
1683 === 9^SPOOF <call> <command>^Do a command as though you are another user
1684 This command is provided so that sysops can set a user's parameters without
1685 me having to write a special 'sysop' version for every user command. It
1686 allows you to pretend that you are doing the command as the user you specify.
1690 SPOOF G1TLH set/name Dirk
1691 SPOOF G1TLH set/qra JO02LQ
1693 === 5^STAT/DB <dbname>^Show the status of a database
1694 Show the internal status of a database descriptor.
1696 Depending on your privilege level you will see more or less information.
1697 This command is unlikely to be of much use to anyone other than a sysop.
1699 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
1700 Show the internal status of the channel object either for the channel that
1701 you are on or else for the callsign that you asked for.
1703 Only the fields that are defined (in perl term) will be displayed.
1705 === 1^STAT/MSG^Show the status of the message system
1706 === 1^STAT/MSG <msgno>^Show the status of a message
1707 This command shows the internal status of a message and includes information
1708 such as to whom it has been forwarded, its size, origin etc etc.
1710 If no message number is given then the status of the message system is
1713 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
1714 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
1716 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
1717 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
1719 === 5^STAT/USER [<callsign>]^Show the full status of a user
1720 Shows the full contents of a user record including all the secret flags
1723 Only the fields that are defined (in perl term) will be displayed.
1725 === 0^SYSOP^Regain your privileges if you login remotely
1726 The system automatically reduces your privilege level to that of a
1727 normal user if you login in remotely. This command allows you to
1728 regain your normal privilege level. It uses the normal system: five
1729 numbers are returned that are indexes into the character array that is
1730 your assigned password (see SET/PASSWORD). The indexes start from
1733 You are expected to return a string which contains the characters
1734 required in the correct order. You may intersperse those characters
1735 with others to obscure your reply for any watchers. For example (and
1736 these values are for explanation :-):
1738 password = 012345678901234567890123456789
1742 aa2bbbb0ccc5ddd7xxx3n
1746 They will all match. If there is no password you will still be offered
1747 numbers but nothing will happen when you input a string. Any match is
1750 === 0^TALK <call> [<text>]^Send a text message to another station
1751 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
1752 Send a short message to any other station that is visible on the cluster
1753 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
1754 command, they don't have to be connected locally.
1756 The second form of TALK is used when other cluster nodes are connected
1757 with restricted information. This usually means that they don't send
1758 the user information usually associated with logging on and off the cluster.
1760 If you know that G3JNB is likely to be present on GB7TLH, but you can only
1761 see GB7TLH in the SH/C list but with no users, then you would use the
1762 second form of the talk message.
1764 If you want to have a ragchew with someone you can leave the text message
1765 out and the system will go into 'Talk' mode. What this means is that a
1766 short message is sent to the recipient telling them that you are in a
1767 'Talking' frame of mind and then you just type - everything you send will
1768 go to the station that you asked for.
1770 All the usual announcements, spots and so on will still come out on your
1773 If you want to do something (such as send a spot) you preceed the normal
1774 command with a '/' character, eg:-
1776 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
1779 To leave talk mode type:
1783 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
1784 Type out the contents of a file in a filearea. So, for example, in
1785 filearea 'bulletins' you want to look at file 'arld051' you would
1787 TYPE bulletins/arld051
1789 See also SHOW/FILES to see what fileareas are available and a
1792 === 0^WHO^Show who is physically connected
1793 This is a quick listing that shows which callsigns are connected and
1794 what sort of connection they have
1796 === 0^WX <text>^Send a weather message to local users
1797 === 0^WX FULL <text>^Send a weather message to all cluster users
1798 === 5^WX SYSOP <text>^Send a weather message to other clusters only
1799 Weather messages can sometimes be useful if you are experiencing an extreme
1800 that may indicate enhanced conditions