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^BYE^Exit from the cluster
211 This will disconnect you from the cluster
213 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
214 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
215 When you send messages the fact that you have forwarded it to another node
216 is remembered so that it isn't sent again. When you have a new partner
217 node and you add their callsign to your /spider/msg/forward.pl file, all
218 outstanding non-private messages will be forwarded to them. This may well
219 be ALL the non-private messages. You can prevent this by using these
223 catchup GB7DJK 300 301 302 303 500-510
225 and to undo what you have just done:-
228 uncatchup GB7DJK 300 301 302 303 500-510
230 which will arrange for them to be forward candidates again.
232 Order is not important.
234 === 0^CLEAR/ANNOUNCE [1|all]^Clear a announce filter line
235 This command allows you to clear (remove) a line in a annouce filter or to
236 remove the whole filter.
238 see CLEAR/SPOTS for a more detailed explanation.
240 === 8^CLEAR/ANNOUNCE [input] <callsign> [0-9|all]^Clear a announce filter line
241 A sysop can clear an input or normal output filter for a user or the
242 node_default or user_default.
244 === 0^CLEAR/ROUTE [1|all]^Clear a route filter line
245 This command allows you to clear (remove) a line in a route filter or to
246 remove the whole filter.
248 see CLEAR/SPOTS for a more detailed explanation.
250 === 8^CLEAR/ROUTE [input] <callsign> [0-9|all]^Clear a route filter line
251 A sysop can clear an input or normal output filter for a user or the
252 node_default or user_default.
254 === 0^CLEAR/SPOTS [0-9|all]^Clear a spot filter line
255 This command allows you to clear (remove) a line in a spot filter or to
256 remove the whole filter.
258 If you have a filter:-
261 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
267 you will be left with:-
269 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
275 the filter will be completely removed.
277 === 8^CLEAR/SPOTS [input] <callsign> [0-9|all]^Clear a spot filter line
278 A sysop can clear an input or normal output filter for a user or the
279 node_default or user_default.
281 === 0^CLEAR/WCY [1|all]^Clear a WCY filter line
282 This command allows you to clear (remove) a line in a WCY filter or to
283 remove the whole filter.
285 see CLEAR/SPOTS for a more detailed explanation.
287 === 8^CLEAR/WCY [input] <callsign> [0-9|all]^Clear a WCY filter line
288 A sysop can clear an input or normal output filter for a user or the
289 node_default or user_default.
291 === 0^CLEAR/WWV [1|all]^Clear a WWV filter line
292 This command allows you to clear (remove) a line in a WWV filter or to
293 remove the whole filter.
295 see CLEAR/SPOTS for a more detailed explanation.
297 === 8^CLEAR/WWV [input] <callsign> [0-9|all]^Clear a WWV filter line
298 A sysop can clear an input or normal output filter for a user or the
299 node_default or user_default.
301 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
302 Start a connection process that will culminate in a new connection to the
303 DX cluster <callsign>. This process creates a new 'client' process which will
304 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
305 necessary to traverse the network(s) to logon to the cluster <callsign>.
307 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
308 This command will completely remove a one or more users from the database.
310 There is NO SECOND CHANCE.
312 It goes without saying that you should use this command CAREFULLY!
314 === 0^DBAVAIL^Show a list of all the Databases in the system
315 Title says it all really, this command lists all the databases defined
316 in the system. It is also aliased to SHOW/COMMAND.
318 === 9^DBCREATE <name>^Create a database entry
319 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
320 === 9^DBCREATE <name> remote <node>^Create a remote database entry
321 DBCREATE allows you to define a database in the system. It doesn't actually
322 create anything, just defines it.
324 The databases that are created are simple DB_File hash databases, they are
325 therefore already 'indexed'.
327 You can define a local database with the first form of the command eg:
331 You can also chain databases with the addition of the 'chain' keyword.
332 This will search each database one after the other. A typical example
335 DBCREATE sdx_qsl chain sql_ad
337 No checking is done to see if the any of the chained databases exist, in
338 fact it is usually better to do the above staement first then do each of
339 the chained databases.
341 Databases can exist offsite. To define a database that lives on another
344 DBCREATE buckmaster remote gb7dxc
346 Remote databases cannot be chained; however, the last database in a
347 a chain can be a remote database eg:
349 DBCREATE qsl chain gb7dxc
351 To see what databases have been defined do:
353 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
355 It would be normal for you to add an entry into your local Aliases file
356 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
357 need to add a line like:-
362 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
371 to work as they may be used to.
373 See DBIMPORT for the importing of existing AK1A format data to databases.
374 See DBSHOW for generic database enquiry
376 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
377 If you want to import or update data in bulk to a database you can use
378 this command. It will either create or update entries into an existing
379 database. For example:-
381 DBIMPORT oblast /tmp/OBLAST.FUL
383 will import the standard OBLAST database that comes with AK1A into the
384 oblast database held locally.
386 === 9^DBREMOVE <dbname>^Delete a database
387 DBREMOVE will completely remove a database entry and also delete any data
388 file that is associated with it.
390 There is no warning, no comeback, no safety net.
396 will remove the oblast database from the system and it will also remove
397 the associated datafile.
401 There is no warning, no comeback, no safety net.
403 You have been warned.
405 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
406 This is the generic user interface to the database to the database system.
407 It is expected that the sysop will add an entry to the local Aliases file
408 so that users can use the more familiar AK1A style of enquiry such as:
412 but if he hasn't and the database really does exist (use DBAVAIL or
413 SHOW/COMMAND to find out) you can do the same thing with:
417 === 9^DEBUG^Set the cluster program into debug mode
418 Executing this command will only have an effect if you are running the cluster
423 It will interrupt the cluster just after the debug command has finished.
425 === 0^DIRECTORY^List messages
426 === 0^DIRECTORY ALL^List all messages
427 === 0^DIRECTORY OWN^List your own messages
428 === 0^DIRECTORY NEW^List all new messages
429 === 0^DIRECTORY TO <call>^List all messages to <call>
430 === 0^DIRECTORY FROM <call>^List all messages from <call>
431 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
432 === 0^DIRECTORY <nn>^List last <nn> messages
433 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
434 List the messages in the messages directory.
436 If there is a 'p' one space after the message number then it is a
437 personal message. If there is a '-' between the message number and the
438 'p' then this indicates that the message has been read.
440 You can use shell escape characters such as '*' and '?' in the <call>
443 You can combine some of the various directory commands together eg:-
447 DIR SUBJECT IOTA 200-250
449 You can abbreviate all the commands to one letter and use ak1a syntax:-
455 Sysops can see all users' messages.
457 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
458 Disconnect any <call> connected locally
460 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
461 This is how you send a DX Spot to other users. You can, in fact, now
462 enter the <freq> and the <call> either way round.
468 will all give the same result. You can add some remarks to the end
469 of the command and they will be added to the spot.
471 DX FR0G 144600 this is a test
473 You can credit someone else by saying:-
475 DX by G1TLH FR0G 144.600 he isn't on the cluster
477 The <freq> is compared against the available bands set up in the
478 cluster. See SHOW/BANDS for more information.
480 === 9^EXPORT <msgno> <filename>^Export a message to a file
481 Export a message to a file. This command can only be executed on a local
482 console with a fully privileged user. The file produced will be in a form
483 ready to be imported back into the cluster by placing it in the import
484 directory (/spider/msg/import).
486 This command cannot overwrite an existing file. This is to provide some
487 measure of security. Any files written will owned by the same user as the
488 main cluster, otherwise you can put the new files anywhere the cluster can
489 access. For example:-
493 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
494 Export the users database to a file in ascii format. If no filename
495 is given then it will export the file to /spider/data/user_asc.
497 If the file already exists it will be renamed to <filename>.o. In fact
498 up to 5 generations of the file can be kept each one with an extra 'o' on the
501 BE WARNED: this will write to any file you have write access to. No check is
502 made on the filename (if any) that you specify.
504 === 0^FILTERING...^Filtering things in DXSpider
505 There are a number of things you can filter in the DXSpider system. They
506 all use the same general mechanism.
508 In general terms you can create a 'reject' or an 'accept' filter which
509 can have up to 10 lines in it. You do this using, for example:-
514 where ..... are the specific commands for that type of filter. There
515 are filters for spots, wwv, announce, wcy and (for sysops)
516 connects. See each different accept or reject command reference for
519 There is also a command to clear out one or more lines in a filter and
520 one to show you what you have set. They are:-
529 There is clear/xxxx command for each type of filter.
531 For now we are going to use spots for the examples, but you can apply
532 the principles to all types of filter.
534 There are two main types of filter 'accept' or 'reject'; which you use
535 depends entirely on how you look at the world and what is least
536 writing to achieve what you want. Each filter has 10 lines (of any
537 length) which are tried in order. If a line matches then the action
538 you have specified is taken (ie reject means ignore it and accept
541 The important thing to remember is that if you specify a 'reject'
542 filter (all the lines in it say 'reject/spots' (for instance) then if
543 a spot comes in that doesn't match any of the lines then you will get
544 it BUT if you specify an 'accept' filter then any spots that don't
545 match are dumped. For example if I have a one line accept filter:-
547 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
549 then automatically you will ONLY get VHF spots from or to CQ zones 14
550 15 and 16. If you set a reject filter like:
552 reject/spots on hf/cw
554 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
555 and will work it even on CW then you could say:-
557 reject/spots on hf/cw and not info iota
559 But in that case you might only be interested in iota and say:-
561 accept/spots not on hf/cw or info iota
563 which is exactly the same. You should choose one or the other until
564 you are confortable with the way it works. Yes, you can mix them
565 (actually you can have an accept AND a reject on the same line) but
566 don't try this at home until you can analyse the results that you get
567 without ringing up the sysop for help.
569 You can arrange your filter lines into logical units, either for your
570 own understanding or simply convenience. I have one set frequently:-
572 reject/spots 1 on hf/cw
573 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
575 What this does is to ignore all HF CW spots (being a class B I can't
576 read any CW and couldn't possibly be interested in HF :-) and also
577 rejects any spots on VHF which don't either originate or spot someone
580 This is an exmaple where you would use the line number (1 and 2 in
581 this case), if you leave the digit out, the system assumes '1'. Digits
582 '0'-'9' are available.
584 You can leave the word 'and' out if you want, it is implied. You can
585 use any number of brackets to make the 'expression' as you want
586 it. There are things called precedence rules working here which mean
587 that you will NEED brackets in a situation like line 2 because,
588 without it, will assume:-
590 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
592 annoying, but that is the way it is. If you use OR - use
593 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
596 If you want to alter your filter you can just redefine one or more
597 lines of it or clear out one line. For example:-
599 reject/spots 1 on hf/ssb
605 To remove the filter in its entirty:-
609 There are similar CLEAR commands for the other filters:-
617 Once you are happy with the results you get, you may like to experiment.
619 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
620 can be written with a mixed filter, eg:
624 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
626 each filter slot actually has a 'reject' slot and an 'accept'
627 slot. The reject slot is executed BEFORE the accept slot.
629 It was mentioned earlier that after a reject test that doesn't match,
630 the default for following tests is 'accept', the reverse is true for
631 'accept'. In the example what happens is that the reject is executed
632 first, any non hf/cw spot is passed to the accept line, which lets
633 thru everything else on HF.
635 The next filter line lets through just VHF/UHF spots from EU.
637 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
638 This command sends all the latitude and longitude information that your
639 cluster is holding against callsigns. One advantage of recieving this
640 information is that more locator information is held by you. This
641 means that more locators are given on the DX line assuming you have
642 SET/DXGRID enabled. This could be a LOT of information though, so
643 it is not recommended on slow links.
645 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
646 This command sends out any information held in the user file which can
647 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
648 and Homenode. PC41s are only sent for the information that is available.
650 === 0^HELP^The HELP Command
651 HELP is available for a number of commands. The syntax is:-
655 Where <cmd> is the name of the command you want help on.
657 All commands can be abbreviated, so SHOW/DX can be abbreviated
658 to SH/DX, ANNOUNCE can be shortened to AN and so on.
660 Look at the APROPOS <string> command which will search the help database
661 for the <string> you specify and give you a list of likely commands
662 to look at with HELP.
664 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
665 This command attempts to re-initialise a link to a (usually) AK1A node
666 that has got confused, usually by a protocol loop of some kind. It may
667 work - but you usually will be better off simply disconnecting it (or
668 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
671 Best of luck - you will need it.
673 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
674 Delete a message from the local system. You will only be able to
675 delete messages that you have originated or been sent (unless you are
678 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
679 Delete a message (usually a 'bulletin') from the whole cluster system.
681 This uses the subject field, so any messages that have exactly the
682 same subject will be deleted. Beware!
684 === 0^LINKS^Show which nodes is physically connected
685 This is a quick listing that shows which links are connected and
686 some information about them. See WHO for a list of all connections.
688 === 9^LOAD/ALIASES^Reload the command alias table
689 Reload the /spider/cmd/Aliases file after you have editted it. You
690 will need to do this if you change this file whilst the cluster is
691 running in order for the changes to take effect.
693 === 9^LOAD/BANDS^Reload the band limits table
694 Reload the /spider/data/bands.pl file if you have changed it manually whilst
695 the cluster is running.
697 === 9^LOAD/BADMSG^Reload the bad msg table
698 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
699 the cluster is running. This table contains a number of perl regular
700 expressions which are searched for in the fields targetted of each message.
701 If any of them match then that message is immediately deleted on receipt.
703 === 9^LOAD/BADWORDS^Reload the bad words table
704 Reload the /spider/data/badwords file if you have changed it manually whilst
705 the cluster is running. This file contains a list of words which, if found
706 on certain text portions of PC protocol, will cause those protocol frames
707 to be rejected. It will all put out a message if any of these words are
708 used on the announce, dx and talk commands. The words can be one or
709 more on a line, lines starting with '#' are ignored.
711 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
712 Normally, if you change a command file in the cmd or local_cmd tree it
713 will automatially be picked up by the cluster program. Sometimes it
714 can get confused if you are doing a lot of moving commands about or
715 delete a command in the local_cmd tree and want to use the normal one
716 again. Execute this command to reset everything back to the state it
717 was just after a cluster restart.
719 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
720 Reload the /spider/msg/forward.pl file if you have changed it
721 manually whilst the cluster is running.
723 === 9^LOAD/MESSAGES^Reload the system messages file
724 If you change the /spider/perl/Messages file (usually whilst
725 fiddling/writing new commands) you can have them take effect during a
726 cluster session by executing this command. You need to do this if get
729 unknown message 'xxxx' in lang 'en'
731 === 9^LOAD/PREFIXES^Reload the prefix table
732 Reload the /spider/data/prefix_data.pl file if you have changed it
733 manually whilst the cluster is running.
735 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
736 MERGE allows you to bring your spot and wwv database up to date. By default
737 it will request the last 10 spots and 5 WWVs from the node you select. The
738 node must be connected locally.
740 You can request any number of spots or wwv and although they will be appended
741 to your databases they will not duplicate any that have recently been added
742 (the last 2 days for spots and last month for WWV data).
744 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
745 Alter message parameters like To, From, Subject, whether private or bulletin
746 or return receipt (RR) is required or whether to keep this message from timing
749 MSG TO <msgno> <call> - change TO callsign to <call>
750 MSG FRom <msgno> <call> - change FROM callsign to <call>
751 MSG PRrivate <msgno> - set private flag
752 MSG NOPRrivate <msgno> - unset private flag
753 MSG RR <msgno> - set RR flag
754 MSG NORR <msgno> - unset RR flag
755 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
756 MSG NOKEep <msgno> - unset the keep flag
757 MSG SUbject <msgno> <new> - change the subject to <new>
758 MSG WAittime <msgno> - remove any waitting time for this message
759 MSG NOREad <msgno> - mark message as unread
760 MSG REad <msgno> - mark message as read
761 MSG QUeue - queue any outstanding bulletins
762 MSG QUeue 1 - queue any outstanding private messages
764 You can look at the status of a message by using:-
768 This will display more information on the message than DIR does.
770 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
771 Send some arbitrary text to a locally connected callsign. No
772 processing is done on the text. This command allows you to send PC
773 Protocol to unstick things if problems arise (messages get stuck
776 pc gb7djk PC33^GB7TLH^GB7DJK^400^
778 pc G1TLH Try doing that properly!!!
780 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
781 You can get rid of any message to or originating from your callsign using
782 this command. You can remove more than one message at a time.
784 === 5^KILL <from>-<to>^Remove a range of messages from the system
785 === 5^KILL FROM <call>^Remove all messages from a callsign
786 === 5^KILL TO <call>^Remove all messages to a callsign
787 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
788 Remove this message from the entire cluster system as well as your node.
791 As a sysop you can kill any message on the system.
793 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
794 Send any text you like to the callsign requested. This is used mainly to send
795 PC protocol to connected nodes either for testing or to unstick things.
797 You can also use in the same way as a talk command to a connected user but
798 without any processing, added of "from <blah> to <blah" or whatever.
800 === 1^PING <node call>^Check the link quality between nodes
801 This command allows you to send a frame to another cluster node on
802 the network and get a return frame. The time it takes to do this
803 is a good indication of the quality of the link. The actual time
804 it takes is output to the console in seconds.
805 Any visible cluster node can be PINGed.
807 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
808 This command allows you to send nearly any command to another DX Cluster
809 node that is connected to the system.
811 Whether you get any output is dependant on a) whether the other system knows
812 that the node callsign of this cluster is in fact a node b) whether the
813 other system is allowing RCMDs from this node and c) whether you have
814 permission to send this command at all.
816 === 0^READ^Read the next unread personal message addressed to you
817 === 0^READ <msgno>^Read the specified message
818 You can read any messages that are sent as 'non-personal' and also any
819 message either sent by or sent to your callsign.
822 As a sysop you may read any message on the system
824 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
825 Create an 'reject this announce' line for a filter.
827 A reject filter line means that if the announce matches this filter it is
828 passed onto the user. See HELP FILTERING for more info. Please read this
829 to understand how filters work - it will save a lot of grief later on.
831 You can use any of the following things in this line:-
833 info <string> eg: iota or qsl
834 by <prefixes> eg: G,M,2
836 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
837 origin_itu <prefixes or numbers> or: G,GM,GW
838 origin_zone <prefixes or numbers>
839 by_dxcc <prefixes or numbers>
840 by_itu <prefixes or numbers>
841 by_zone <prefixes or numbers>
843 wx 1 filter WX announces
844 dest <prefixes> eg: 6MUK,WDX (distros)
848 rej/ann by_zone 14,15,16 and not by G,M,2
850 You can use the tag 'all' to reject everything eg:
854 but this probably for advanced users...
856 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
857 This version allows a sysop to set a filter for a callsign as well as the
858 default for nodes and users eg:-
861 reject/ann input node_default by G,M,2
862 reject/ann user_default by G,M,2
864 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
865 Create a 'reject this spot' line for a filter.
867 A reject filter line means that if the spot matches this filter it is
868 dumped (not passed on). See HELP FILTERING for more info. Please read this
869 to understand how filters work - it will save a lot of grief later on.
871 You can use any of the following things in this line:-
873 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
874 on <range> same as 'freq'
875 call <prefixes> eg: G,PA,HB9
876 info <string> eg: iota or qsl
878 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
879 call_itu <prefixes or numbers> or: G,GM,GW
880 call_zone <prefixes or numbers>
881 by_dxcc <prefixes or numbers>
882 by_itu <prefixes or numbers>
883 by_zone <prefixes or numbers>
887 For frequencies, you can use any of the band names defined in
888 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
889 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
890 this is more efficient than saying simply: on HF (but don't get
891 too hung up about that)
896 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
898 You can use the tag 'all' to reject everything eg:
902 but this probably for advanced users...
904 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
905 Create an 'reject this routing PC Protocol' line for a filter.
907 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
908 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
909 read this to understand how filters work - it will save a lot of grief later on.
911 You can use any of the following things in this line:-
913 call <prefixes> the callsign of the thingy
914 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
915 call_itu <prefixes or numbers> or: G,GM,GW
916 call_zone <prefixes or numbers>
917 origin <prefixes> really the interface it came in on
918 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
919 origin_itu <prefixes or numbers> or: G,GM,GW
920 origin_zone <prefixes or numbers>
924 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
926 You can use the tag 'all' to reject everything eg:
928 rej/route all (equiv to [very] restricted mode)
930 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
931 This version allows a sysop to set a filter for a callsign as well as the
932 default for nodes and users eg:-
934 reject/spot db0sue-7 1 by_zone 14,15,16
935 reject/spot node_default all
936 set/hops node_default 10
938 reject/spot user_default by G,M,2
940 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
941 It is unlikely that you will want to do this, but if you do then you can
942 filter on the following fields:-
944 by <prefixes> eg: G,M,2
946 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
947 origin_itu <prefixes or numbers> or: G,GM,GW
948 origin_zone <prefixes or numbers>
949 by_dxcc <prefixes or numbers>
950 by_itu <prefixes or numbers>
951 by_zone <prefixes or numbers>
954 There are no examples because WCY Broadcasts only come from one place and
955 you either want them or not (see UNSET/WCY if you don't want them).
957 This command is really provided for future use.
959 See HELP FILTER for information.
961 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
962 This version allows a sysop to set a filter for a callsign as well as the
963 default for nodes and users eg:-
965 reject/wcy gb7djk all
967 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
968 It is unlikely that you will want to do this, but if you do then you can
969 filter on the following fields:-
971 by <prefixes> eg: G,M,2
973 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
974 origin_itu <prefixes or numbers> or: G,GM,GW
975 origin_zone <prefixes or numbers>
976 by_dxcc <prefixes or numbers>
977 by_itu <prefixes or numbers>
978 by_zone <prefixes or numbers>
983 reject/wwv by_zone 14,15,16
985 is probably the only useful thing to do (which will only show WWV broadcasts
986 by stations in the US).
988 See HELP FILTER for information.
990 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
991 This version allows a sysop to set a filter for a callsign as well as the
992 default for nodes and users eg:-
994 reject/wwv db0sue-7 1 by_zone 4
995 reject/wwv node_default all
997 reject/wwv user_default by W
999 === 0^REPLY^Reply (privately) to the last message that you have read
1000 === 0^REPLY <msgno>^Reply (privately) to the specified message
1001 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1002 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1003 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1004 You can reply to a message and the subject will automatically have
1005 "Re:" inserted in front of it, if it isn't already present.
1007 You can also use all the extra qualifiers such as RR, PRIVATE,
1008 NOPRIVATE, B that you can use with the SEND command (see SEND
1009 for further details)
1011 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1012 === 0^SEND RR <call>^Send a message and ask for a read receipt
1013 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1014 === 0^SEND PRIVATE <call>^Send a personal message
1015 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1016 All the SEND commands will create a message which will be sent either to
1017 an individual callsign or to one of the 'bulletin' addresses.
1019 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1020 it will mark the message as personal and send it to the cluster node that
1021 that callsign is connected to.
1023 You can have more than one callsign in all of the SEND commands.
1025 You can have multiple qualifiers so that you can have for example:-
1027 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1029 which should send a copy of message 123 to G1TLH and G0RDI and you will
1030 receive a read receipt when they have read the message.
1032 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1033 SP is an alias for SEND PRIVATE
1035 === 0^SET/ADDRESS <your address>^Record your postal address
1037 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1038 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1040 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1042 === 8^SET/BADDX <call>..^Stop words we do not wish to see in the callsign field
1043 of a dx spot being propagated
1044 === 8^UNSET/BADDX <call>..^Allow a word to be seen again in a DX spot
1045 Setting a word as 'baddx' will prevent spots with that word in the
1046 callsign field of a DX spot from going any further. They will not be
1047 displayed and they will not be sent onto other nodes.
1049 The word must be wriiten in full, no wild cards are allowed eg:-
1051 set/baddx FORSALE VIDEO FR0G
1053 To allow a word again, use the following command ...
1057 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1058 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1059 Setting a callsign as a 'badnode' will prevent spots from that node
1060 going any further. They will not be displayed and they will not be
1061 sent onto other nodes.
1063 The call must be a full eg:-
1067 will stop anything from K1TTT. If you want SSIDs as well then you must
1068 enter them specifically.
1072 will allow spots from him again.
1074 Use with extreme care. This command may well be superceeded by FILTERing.
1076 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1077 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1078 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1079 going any further. They will not be displayed and they will not be
1080 sent onto other nodes.
1082 The call must be written in full, no wild cards are allowed eg:-
1084 set/badspotter VE2STN
1086 will stop anything from VE2STN. If you want SSIDs as well then you must
1087 enter them specifically.
1089 unset/badspotter VE2STN
1091 will allow spots from him again.
1093 Use with extreme care. This command may well be superceded by FILTERing.
1095 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1096 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1098 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1100 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1102 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1103 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1104 You can choose to log several different levels. The levels are
1112 You can show what levels you are logging with SHOW/DEBUG
1114 === 0^SET/DX^Allow DX messages to come out on your terminal
1115 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1117 === 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements
1118 === 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements
1119 A standard feature which is enabled in version 1.43 and above is
1120 that if the spotter's grid square is known it is output on the end
1121 of a DX announcement (there is just enough room). Some user programs
1122 cannot cope with this. You can use this command to reset (or set)
1125 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1127 === 0^SET/ECHO^Make the cluster echo your input
1128 === 0^UNSET/ECHO^Stop the cluster echoing your input
1129 If you are connected via a telnet session, different implimentations
1130 of telnet handle echo differently depending on whether you are
1131 connected via port 23 or some other port. You can use this command
1132 to change the setting appropriately.
1134 The setting is stored in your user profile.
1136 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1138 === 0^SET/HERE^Tell the system you are present at your terminal
1139 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1141 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1142 Tell the cluster system where you normally connect to. Any Messages sent
1143 to you will normally find their way there should you not be connected.
1147 === 8^SET/HOPS <call> ann|spots|wwv|wcy <n>^Set hop count
1148 Set the hop count for a particular type of broadcast for a node.
1150 This command allows you to set up special hop counts for a node
1151 for currently: announce, spots, wwv and wcy broadcasts.
1154 set/hops gb7djk ann 10
1155 set/hops gb7mbc spots 20
1157 Set SHOW/HOPS for information on what is already set. This command
1158 creates a filter and works in conjunction with the filter system.
1160 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1161 Connect a node to your system in such a way that you are a full protocol
1162 member of its network and can see all spots on it, but nothing either leaks
1163 out from it nor goes back into from the rest of the nodes connected to you.
1165 You can potentially connect several nodes in this way.
1167 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1168 Remove isolation from a node - SET/ISOLATE
1170 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1171 You can select the language that you want the cluster to use. Currently
1172 the languages available are en (english) and nl (dutch).
1174 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1175 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1176 In order to get accurate headings and such like you must tell the system
1177 what your latitude and longitude is. If you have not yet done a SET/QRA
1178 then this command will set your QRA locator for you. For example:-
1179 SET/LOCATION 52 22 N 0 57 E
1181 === 0^SET/LOGININFO^Inform when a station logs in locally
1182 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1184 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1185 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1187 === 0^SET/NAME <your name>^Set your name
1188 Tell the system what your name is eg:-
1191 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1192 Tell the system that the call(s) are to be treated as AK1A cluster and
1193 fed PC Protocol rather normal user commands.
1195 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
1196 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1197 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1198 counter which is decremented on every outgoing ping and then reset to
1199 the 'obscount' value on every incoming ping. The default value of this
1202 What this means is that a neighbouring node will be pinged twice at
1203 (default) 300 second intervals and if no reply has been heard just before
1204 what would be the third attempt, that node is disconnected.
1206 If a ping is heard then the obscount is reset to the full value. Using
1207 default values, if a node has not responded to a ping within 15 minutes,
1210 You can set this parameter between 1 and 9.
1212 It is STRONGLY recommended that you don't change the default.
1214 === 0^SET/PAGE <lines per page>^Set the lines per page
1215 Tell the system how many lines you wish on a page when the number of line
1216 of output from a command is more than this. The default is 20. Setting it
1217 explicitly to 0 will disable paging.
1221 The setting is stored in your user profile.
1223 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1224 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1225 in order to determine the rolling quality of the link and, in future, to
1226 affect routing decisions. The default interval is 300 secs or 5 minutes.
1228 You can use this command to set a different interval. Please don't.
1230 But if you do the value you enter is treated as minutes up 30 and seconds
1231 for numbers greater than that.
1233 This is used also to help determine when a link is down at the far end
1234 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1235 for more information.
1237 If you must change it (and it may be useful for internet connected nodes
1238 on dynamic IP addresses that go away after a set time of usage) the time
1239 can be specified as:-
1241 5 which if less than 30 is converted to minutes otherwise is
1242 taken as the no of seconds between pings.
1247 Please be aware that this causes traffic to occur on the link, setting
1248 this value too low may annoy your neighbours beyond the point of
1251 You can switch this off by setting it to 0.
1253 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1254 Set the privilege level on a callsign. The privilege levels that pertain
1255 to commands are as default:-
1257 1 - allow remote nodes normal user RCMDs
1258 5 - various privileged commands (including shutdown, but not disc-
1259 connect), the normal level for another node.
1260 8 - more privileged commands (including disconnect)
1261 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1263 If you are a sysop and you come in as a normal user on a remote connection
1264 your privilege will automatically be set to 0.
1266 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1267 You can use this command to 'protect' this session from unauthorised
1268 use. If you want to get your normal privilege back you will need to
1269 either logout and login again (if you are on a console) or use the
1272 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1273 The password for a user can only be set by a full sysop. The string
1274 can contain any characters but any spaces are removed (you can type in
1275 spaces - but they won't appear in the password). You can see the
1276 result with STAT/USER.
1278 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1279 Tell the system that the call(s) are to be treated as DXSpider node and
1280 fed new style DX Protocol rather normal user commands.
1282 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
1283 === 0^SET/QRA <locator>^Set your QRA locator
1284 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1285 done a SET/LOCATION then your latitude and longitude will be set roughly
1286 correctly (assuming your locator is correct ;-). For example:-
1289 === 0^SET/QTH <your qth>^Set your QTH
1290 Tell the system where you are. For example:-
1291 SET/QTH East Dereham, Norfolk
1293 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1294 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1296 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1297 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1299 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1300 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1302 === 0^SET/WX^Allow WX messages to come out on your terminal
1303 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1305 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1306 Display all the bad dx callsigns in the system, see SET/BADDX
1307 for more information.
1309 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1310 Display all the bad node callsigns in the system, see SET/BADNODE
1311 for more information.
1313 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1314 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1315 for more information.
1317 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1318 This command allows you to see all the users that can be seen
1319 and the nodes to which they are connected.
1321 This command is normally abbreviated to: sh/c
1323 BE WARNED: the list that is returned can be VERY long
1325 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1326 Show all the nodes connected to this node.
1328 === 1^SHOW/CONNECT^Show all the active connections
1329 This command shows information on all the active connections known to
1330 the node. This command gives slightly more information than WHO.
1332 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1333 This is very nearly the same as SHOW/TIME, the only difference the format
1334 of the date string if no arguments are given.
1336 If no prefixes or callsigns are given then this command returns the local
1337 time and UTC as the computer has it right now. If you give some prefixes
1338 then it will show UTC and UTC + the local offset (not including DST) at
1339 the prefixes or callsigns that you specify.
1341 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1343 === 0^SHOW/DX^Interrogate the spot database
1344 If you just type SHOW/DX you will get the last so many spots
1345 (sysop configurable, but usually 10).
1347 In addition you can add any number of these commands in very nearly
1348 any order to the basic SHOW/DX command, they are:-
1350 on <band> - eg 160m 20m 2m 23cm 6mm
1351 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1353 <number> - the number of spots you want
1354 <from>-<to> - <from> spot no <to> spot no in the selected list
1356 <prefix> - for a spotted callsign beginning with <prefix>
1357 *<suffix> - for a spotted callsign ending in <suffix>
1358 *<string>* - for a spotted callsign containing <string>
1360 day <number> - starting <number> days ago
1361 day <from>-<to> - <from> days <to> days ago
1363 info <text> - any spots containing <text> in the info or remarks
1365 by <call> - any spots spotted by <call> (spotter <call> is the
1368 qsl - this automatically looks for any qsl info on the call
1369 held in the spot database.
1371 iota [<iota>] - If the iota island number is missing it will look for
1372 the string iota and anything which looks like an iota
1373 island number. If you specify then it will look for
1376 qra [<locator>] - this will look for the specific locator if you specify
1377 one or else anything that looks like a locator.
1382 SH/DX on 20m info iota
1383 SH/DX 9a on vhf day 30
1389 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1390 This command takes the <prefix> (which can be a full or partial
1391 callsign if desired), looks up which internal country number it is
1392 and then displays all the spots as per SH/DX for that country.
1394 The options for SHOW/DX also apply to this command.
1398 SH/DXCC W on 20m info iota
1400 === 0^SHOW/DXSTATS^Show the DX Statistics for last 31 days
1401 Show the total DX spots for the last 31 days
1403 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1404 SHOW/FILES on its own will show you a list of the various fileareas
1405 available on the system. To see the contents of a particular file
1408 where <filearea> is the name of the filearea you want to see the
1411 You can also use shell globbing characters like '*' and '?' in a
1412 string to see a selection of files in a filearea eg:-
1413 SH/FILES bulletins arld*
1415 See also TYPE - to see the contents of a file.
1417 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1418 Show the contents of all the filters that are set. This command displays
1419 all the filters set - for all the various categories.
1421 === 0^SHOW/HFSTATS^Show the HF DX Statistics for last 31 days
1422 Show the HF DX spots breakdown by band for the last 31 days
1424 === 0^SHOW/HFTABLE^Show the HF DX Spotter Table for your country
1425 Show the HF DX Spotter table for your country for the last 31 days
1427 === 8^SHOW/HOPS <call> [ann|spots|wcy|wwv]^Show the hop counts for a node
1428 This command shows the hop counts set up for a node. You can specify
1429 which category you want to see. If you leave the category out then
1430 all the categories will be listed.
1432 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1434 === 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
1436 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
1437 This command outputs a short section of the system log. On its own
1438 it will output a general logfile. With the optional callsign it will
1439 show output from the log associated with that callsign.
1441 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
1442 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1443 together with the azimuth and elevation of the sun currently at those
1446 If you don't specify any prefixes or callsigns, it will show the times for
1447 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1448 together with the current azimuth and elevation.
1450 In addition, it will show the gain or loss dB relative to the nominal
1451 distance of 385,000Km due to the ellipsoidal nature of the orbit.
1453 If all else fails it will show the Moonrise and set times for the node
1454 that you are connected to.
1461 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1462 This command allow you to estimate the likelihood of you contacting
1463 a station with the prefix you have specified. The output assumes a modest
1464 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1466 The result predicts the most likely operating frequencies and signal
1467 levels for high frequency (shortwave) radio propagation paths on
1468 specified days of the year and hours of the day. It is most useful for
1469 paths between 250 km and 6000 km, but can be used with reduced accuracy
1470 for paths shorter or longer than this.
1472 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1473 used to predict the MUF given the predicted flux, day of the year,
1474 hour of the day and geographic coordinates of the transmitter and
1475 receiver. This routine is reasonably accurate for the purposes here,
1476 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1477 than the programs used by major shortwave broadcasting organizations,
1478 such as the Voice of America.
1480 The command will display some header information detailing its
1481 assumptions, together with the locations, latitude and longitudes and
1482 bearings. It will then show UTC (UT), local time at the other end
1483 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1484 (Zen) and the likely signal strengths. Then for each frequency for which
1485 the system thinks there is a likelihood of a circuit it prints a value.
1487 The value is currently a likely S meter reading based on the conventional
1488 6dB / S point scale. If the value has a '+' appended it means that it is
1489 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1490 there is likely to be much fading and by an 's' that the signal is likely
1493 By default SHOW/MUF will show the next two hours worth of data. You
1494 can specify anything up to 24 hours worth of data by appending the no of
1495 hours required after the prefix. For example:-
1501 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1502 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1503 Location Lat / Long Azim
1504 East Dereham, Norfolk 52 41 N 0 57 E 47
1505 United-States-W 43 0 N 87 54 W 299
1506 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1507 18 23 11.5 -35 mS0+ mS2 S3
1508 19 0 11.2 -41 mS0+ mS2 S3
1510 indicating that you will have weak, fading circuits on top band and
1511 80m but usable signals on 40m (about S3).
1517 will get you the above display, but with the next 24 hours worth of
1523 Gives you an estimate of the long path propagation characterics. It
1524 should be noted that the figures will probably not be very useful, nor
1525 terrible accurate, but it is included for completeness.
1527 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1528 Show the type and version (if connected) of the nodes specified on the
1529 command line. If no callsigns are specified then a sorted list of all
1530 the non-user callsigns known to the system will be displayed.
1532 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1533 This command takes the <callsign> (which can be a full or partial
1534 callsign or a prefix), looks up which internal country number
1535 it is and then displays all the relevant prefixes for that country
1536 together with the internal country no, the CQ and ITU regions.
1540 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1541 Show the name and location where every program module was load from. This
1542 is useful for checking where you think you have loaded a .pm file from.
1544 === 0^SHOW/QRA <locator> [<locator>]^Show distance between locators
1545 === 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
1546 This is a multipurpose command that allows you either to calculate the
1547 distance and bearing between two locators or (if only one locator is
1548 given on the command line) the distance and beraing from your station
1549 to the locator. For example:-
1554 The first example will show the distance and bearing to the locator from
1555 yourself, the second example will calculate the distance and bearing from
1556 the first locator to the second. You can use 4 or 6 character locators.
1558 It is also possible to convert a latitude and longitude to a locator by
1559 using this command with a latitude and longitude as an argument, for
1562 SH/QRA 52 41 N 0 58 E
1564 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
1565 This command queries the QRZ callbook server on the internet
1566 and returns any information available for that callsign. This service
1567 is provided for users of this software by http://www.qrz.com
1569 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
1570 This command allows you to see to which node the callsigns specified are
1571 connected. It is a sort of inverse sh/config.
1575 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1576 Show the tracking data from your location to the satellite of your choice
1577 from now on for the next few hours.
1579 If you use this command without a satellite name it will display a list
1580 of all the satellites known currently to the system.
1582 If you give a name then you can obtain tracking data of all the passes
1583 that start and finish 5 degrees below the horizon. As default it will
1584 give information for the next three hours for every five minute period.
1586 You can alter the number of hours and the step size, within certain
1589 Each pass in a period is separated with a row of '-----' characters
1594 SH/SAT FENGYUN1 12 2
1596 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
1597 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
1598 Show the information known about a callsign and whether (and where)
1599 that callsign is connected to the cluster.
1603 If no callsign is given then show the information for yourself.
1605 === 0^SHOW/SUN [<prefix>|<callsign>]^Show sun rise and set times
1606 Show the sun rise and set times for a (list of) prefixes or callsigns,
1607 together with the azimuth and elevation of the sun currently at those
1610 If you don't specify any prefixes or callsigns, it will show the times for
1611 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1612 together with the current azimuth and elevation.
1614 If all else fails it will show the sunrise and set times for the node
1615 that you are connected to.
1620 SH/SUN G1TLH K9CW ZS
1622 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
1623 If no prefixes or callsigns are given then this command returns the local
1624 time and UTC as the computer has it right now. If you give some prefixes
1625 then it will show UTC and UTC + the local offset (not including DST) at
1626 the prefixes or callsigns that you specify.
1628 === 0^SHOW/VHFSTATS^Show the VHF DX Statistics for last 31 days
1629 Show the VHF DX spots breakdown by band for the last 31 days
1631 === 0^SHOW/VHFTABLE^Show the VHF DX Spotter Table for your country
1632 Show the VHF DX Spotter table for your country for the last 31 days
1634 === 0^SHOW/WCY^Show last 10 WCY broadcasts
1635 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
1636 Display the most recent WCY information that has been received by the system
1638 === 0^SHOW/WWV^Show last 10 WWV broadcasts
1639 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
1640 Display the most recent WWV information that has been received by the system
1642 === 5^SHUTDOWN^Shutdown the cluster
1643 Shutdown the cluster and disconnect all the users
1645 === 9^SPOOF <call> <command>^Do a command as though you are another user
1646 This command is provided so that sysops can set a user's parameters without
1647 me having to write a special 'sysop' version for every user command. It
1648 allows you to pretend that you are doing the command as the user you specify.
1652 SPOOF G1TLH set/name Dirk
1653 SPOOF G1TLH set/qra JO02LQ
1655 === 5^STAT/DB <dbname>^Show the status of a database
1656 Show the internal status of a database descriptor.
1658 Depending on your privilege level you will see more or less information.
1659 This command is unlikely to be of much use to anyone other than a sysop.
1661 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
1662 Show the internal status of the channel object either for the channel that
1663 you are on or else for the callsign that you asked for.
1665 Only the fields that are defined (in perl term) will be displayed.
1667 === 1^STAT/MSG^Show the status of the message system
1668 === 1^STAT/MSG <msgno>^Show the status of a message
1669 This command shows the internal status of a message and includes information
1670 such as to whom it has been forwarded, its size, origin etc etc.
1672 If no message number is given then the status of the message system is
1675 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
1676 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
1678 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
1679 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
1681 === 5^STAT/USER [<callsign>]^Show the full status of a user
1682 Shows the full contents of a user record including all the secret flags
1685 Only the fields that are defined (in perl term) will be displayed.
1687 === 0^SYSOP^Regain your privileges if you login remotely
1688 The system automatically reduces your privilege level to that of a
1689 normal user if you login in remotely. This command allows you to
1690 regain your normal privilege level. It uses the normal system: five
1691 numbers are returned that are indexes into the character array that is
1692 your assigned password (see SET/PASSWORD). The indexes start from
1695 You are expected to return a string which contains the characters
1696 required in the correct order. You may intersperse those characters
1697 with others to obscure your reply for any watchers. For example (and
1698 these values are for explanation :-):
1700 password = 012345678901234567890123456789
1704 aa2bbbb0ccc5ddd7xxx3n
1708 They will all match. If there is no password you will still be offered
1709 numbers but nothing will happen when you input a string. Any match is
1712 === 0^TALK <call> [<text>]^Send a text message to another station
1713 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
1714 Send a short message to any other station that is visible on the cluster
1715 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
1716 command, they don't have to be connected locally.
1718 The second form of TALK is used when other cluster nodes are connected
1719 with restricted information. This usually means that they don't send
1720 the user information usually associated with logging on and off the cluster.
1722 If you know that G3JNB is likely to be present on GB7TLH, but you can only
1723 see GB7TLH in the SH/C list but with no users, then you would use the
1724 second form of the talk message.
1726 If you want to have a ragchew with someone you can leave the text message
1727 out and the system will go into 'Talk' mode. What this means is that a
1728 short message is sent to the recipient telling them that you are in a
1729 'Talking' frame of mind and then you just type - everything you send will
1730 go to the station that you asked for.
1732 All the usual announcements, spots and so on will still come out on your
1735 If you want to do something (such as send a spot) you preceed the normal
1736 command with a '/' character, eg:-
1738 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
1741 To leave talk mode type:
1745 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
1746 Type out the contents of a file in a filearea. So, for example, in
1747 filearea 'bulletins' you want to look at file 'arld051' you would
1749 TYPE bulletins/arld051
1751 See also SHOW/FILES to see what fileareas are available and a
1754 === 0^WHO^Show who is physically connected
1755 This is a quick listing that shows which callsigns are connected and
1756 what sort of connection they have
1758 === 0^WX <text>^Send a weather message to local users
1759 === 0^WX FULL <text>^Send a weather message to all cluster users
1760 === 5^WX SYSOP <text>^Send a weather message to other clusters only
1761 Weather messages can sometimes be useful if you are experiencing an extreme
1762 that may indicate enhanced conditions