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 [<string>] [<nn>]^Print nn (default 1) blank lines (or strings)
211 In its basic form this command prints one or more blank lines. However if
212 you pass it a string it will replicate the string for the width of the
213 screen (default 80) and then print that one or more times, so:
217 prints two blank lines
221 prints a row of - characters once.
225 prints 'abcabcabcabcabcabc....'
227 This is really only of any use in a script file and you can print a maximum
230 === 0^BYE^Exit from the cluster
231 This will disconnect you from the cluster
233 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
234 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
235 When you send messages the fact that you have forwarded it to another node
236 is remembered so that it isn't sent again. When you have a new partner
237 node and you add their callsign to your /spider/msg/forward.pl file, all
238 outstanding non-private messages will be forwarded to them. This may well
239 be ALL the non-private messages. You can prevent this by using these
243 catchup GB7DJK 300 301 302 303 500-510
245 and to undo what you have just done:-
248 uncatchup GB7DJK 300 301 302 303 500-510
250 which will arrange for them to be forward candidates again.
252 Order is not important.
254 === 0^CLEAR/ANNOUNCE [1|all]^Clear a announce filter line
255 This command allows you to clear (remove) a line in a annouce filter or to
256 remove the whole filter.
258 see CLEAR/SPOTS for a more detailed explanation.
260 === 8^CLEAR/ANNOUNCE [input] <callsign> [0-9|all]^Clear a announce filter line
261 A sysop can clear an input or normal output filter for a user or the
262 node_default or user_default.
264 === 0^CLEAR/ROUTE [1|all]^Clear a route filter line
265 This command allows you to clear (remove) a line in a route filter or to
266 remove the whole filter.
268 see CLEAR/SPOTS for a more detailed explanation.
270 === 8^CLEAR/ROUTE [input] <callsign> [0-9|all]^Clear a route filter line
271 A sysop can clear an input or normal output filter for a user or the
272 node_default or user_default.
274 === 0^CLEAR/SPOTS [0-9|all]^Clear a spot filter line
275 This command allows you to clear (remove) a line in a spot filter or to
276 remove the whole filter.
278 If you have a filter:-
281 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
287 you will be left with:-
289 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
295 the filter will be completely removed.
297 === 8^CLEAR/SPOTS [input] <callsign> [0-9|all]^Clear a spot 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 === 0^CLEAR/WCY [1|all]^Clear a WCY filter line
302 This command allows you to clear (remove) a line in a WCY filter or to
303 remove the whole filter.
305 see CLEAR/SPOTS for a more detailed explanation.
307 === 8^CLEAR/WCY [input] <callsign> [0-9|all]^Clear a WCY filter line
308 A sysop can clear an input or normal output filter for a user or the
309 node_default or user_default.
311 === 0^CLEAR/WWV [1|all]^Clear a WWV filter line
312 This command allows you to clear (remove) a line in a WWV filter or to
313 remove the whole filter.
315 see CLEAR/SPOTS for a more detailed explanation.
317 === 8^CLEAR/WWV [input] <callsign> [0-9|all]^Clear a WWV filter line
318 A sysop can clear an input or normal output filter for a user or the
319 node_default or user_default.
321 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
322 Start a connection process that will culminate in a new connection to the
323 DX cluster <callsign>. This process creates a new 'client' process which will
324 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
325 necessary to traverse the network(s) to logon to the cluster <callsign>.
327 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
328 This command will completely remove a one or more users from the database.
330 There is NO SECOND CHANCE.
332 It goes without saying that you should use this command CAREFULLY!
334 === 0^DBAVAIL^Show a list of all the Databases in the system
335 Title says it all really, this command lists all the databases defined
336 in the system. It is also aliased to SHOW/COMMAND.
338 === 9^DBCREATE <name>^Create a database entry
339 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
340 === 9^DBCREATE <name> remote <node>^Create a remote database entry
341 DBCREATE allows you to define a database in the system. It doesn't actually
342 create anything, just defines it.
344 The databases that are created are simple DB_File hash databases, they are
345 therefore already 'indexed'.
347 You can define a local database with the first form of the command eg:
351 You can also chain databases with the addition of the 'chain' keyword.
352 This will search each database one after the other. A typical example
355 DBCREATE sdx_qsl chain sql_ad
357 No checking is done to see if the any of the chained databases exist, in
358 fact it is usually better to do the above staement first then do each of
359 the chained databases.
361 Databases can exist offsite. To define a database that lives on another
364 DBCREATE buckmaster remote gb7dxc
366 Remote databases cannot be chained; however, the last database in a
367 a chain can be a remote database eg:
369 DBCREATE qsl chain gb7dxc
371 To see what databases have been defined do:
373 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
375 It would be normal for you to add an entry into your local Aliases file
376 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
377 need to add a line like:-
382 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
391 to work as they may be used to.
393 See DBIMPORT for the importing of existing AK1A format data to databases.
394 See DBSHOW for generic database enquiry
396 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
397 If you want to import or update data in bulk to a database you can use
398 this command. It will either create or update entries into an existing
399 database. For example:-
401 DBIMPORT oblast /tmp/OBLAST.FUL
403 will import the standard OBLAST database that comes with AK1A into the
404 oblast database held locally.
406 === 9^DBREMOVE <dbname>^Delete a database
407 DBREMOVE will completely remove a database entry and also delete any data
408 file that is associated with it.
410 There is no warning, no comeback, no safety net.
416 will remove the oblast database from the system and it will also remove
417 the associated datafile.
421 There is no warning, no comeback, no safety net.
423 You have been warned.
425 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
426 This is the generic user interface to the database to the database system.
427 It is expected that the sysop will add an entry to the local Aliases file
428 so that users can use the more familiar AK1A style of enquiry such as:
432 but if he hasn't and the database really does exist (use DBAVAIL or
433 SHOW/COMMAND to find out) you can do the same thing with:
437 === 9^DEBUG^Set the cluster program into debug mode
438 Executing this command will only have an effect if you are running the cluster
443 It will interrupt the cluster just after the debug command has finished.
445 === 0^DIRECTORY^List messages
446 === 0^DIRECTORY ALL^List all messages
447 === 0^DIRECTORY OWN^List your own messages
448 === 0^DIRECTORY NEW^List all new messages
449 === 0^DIRECTORY TO <call>^List all messages to <call>
450 === 0^DIRECTORY FROM <call>^List all messages from <call>
451 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
452 === 0^DIRECTORY <nn>^List last <nn> messages
453 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
454 List the messages in the messages directory.
456 If there is a 'p' one space after the message number then it is a
457 personal message. If there is a '-' between the message number and the
458 'p' then this indicates that the message has been read.
460 You can use shell escape characters such as '*' and '?' in the <call>
463 You can combine some of the various directory commands together eg:-
467 DIR SUBJECT IOTA 200-250
469 You can abbreviate all the commands to one letter and use ak1a syntax:-
475 Sysops can see all users' messages.
477 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
478 Disconnect any <call> connected locally
480 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
481 This is how you send a DX Spot to other users. You can, in fact, now
482 enter the <freq> and the <call> either way round.
488 will all give the same result. You can add some remarks to the end
489 of the command and they will be added to the spot.
491 DX FR0G 144600 this is a test
493 You can credit someone else by saying:-
495 DX by G1TLH FR0G 144.600 he isn't on the cluster
497 The <freq> is compared against the available bands set up in the
498 cluster. See SHOW/BANDS for more information.
500 === 9^EXPORT <msgno> <filename>^Export a message to a file
501 Export a message to a file. This command can only be executed on a local
502 console with a fully privileged user. The file produced will be in a form
503 ready to be imported back into the cluster by placing it in the import
504 directory (/spider/msg/import).
506 This command cannot overwrite an existing file. This is to provide some
507 measure of security. Any files written will owned by the same user as the
508 main cluster, otherwise you can put the new files anywhere the cluster can
509 access. For example:-
513 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
514 Export the users database to a file in ascii format. If no filename
515 is given then it will export the file to /spider/data/user_asc.
517 If the file already exists it will be renamed to <filename>.o. In fact
518 up to 5 generations of the file can be kept each one with an extra 'o' on the
521 BE WARNED: this will write to any file you have write access to. No check is
522 made on the filename (if any) that you specify.
524 === 0^FILTERING...^Filtering things in DXSpider
525 There are a number of things you can filter in the DXSpider system. They
526 all use the same general mechanism.
528 In general terms you can create a 'reject' or an 'accept' filter which
529 can have up to 10 lines in it. You do this using, for example:-
534 where ..... are the specific commands for that type of filter. There
535 are filters for spots, wwv, announce, wcy and (for sysops)
536 connects. See each different accept or reject command reference for
539 There is also a command to clear out one or more lines in a filter and
540 one to show you what you have set. They are:-
549 There is clear/xxxx command for each type of filter.
551 For now we are going to use spots for the examples, but you can apply
552 the principles to all types of filter.
554 There are two main types of filter 'accept' or 'reject'; which you use
555 depends entirely on how you look at the world and what is least
556 writing to achieve what you want. Each filter has 10 lines (of any
557 length) which are tried in order. If a line matches then the action
558 you have specified is taken (ie reject means ignore it and accept
561 The important thing to remember is that if you specify a 'reject'
562 filter (all the lines in it say 'reject/spots' (for instance) then if
563 a spot comes in that doesn't match any of the lines then you will get
564 it BUT if you specify an 'accept' filter then any spots that don't
565 match are dumped. For example if I have a one line accept filter:-
567 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
569 then automatically you will ONLY get VHF spots from or to CQ zones 14
570 15 and 16. If you set a reject filter like:
572 reject/spots on hf/cw
574 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
575 and will work it even on CW then you could say:-
577 reject/spots on hf/cw and not info iota
579 But in that case you might only be interested in iota and say:-
581 accept/spots not on hf/cw or info iota
583 which is exactly the same. You should choose one or the other until
584 you are confortable with the way it works. Yes, you can mix them
585 (actually you can have an accept AND a reject on the same line) but
586 don't try this at home until you can analyse the results that you get
587 without ringing up the sysop for help.
589 You can arrange your filter lines into logical units, either for your
590 own understanding or simply convenience. I have one set frequently:-
592 reject/spots 1 on hf/cw
593 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
595 What this does is to ignore all HF CW spots (being a class B I can't
596 read any CW and couldn't possibly be interested in HF :-) and also
597 rejects any spots on VHF which don't either originate or spot someone
600 This is an exmaple where you would use the line number (1 and 2 in
601 this case), if you leave the digit out, the system assumes '1'. Digits
602 '0'-'9' are available.
604 You can leave the word 'and' out if you want, it is implied. You can
605 use any number of brackets to make the 'expression' as you want
606 it. There are things called precedence rules working here which mean
607 that you will NEED brackets in a situation like line 2 because,
608 without it, will assume:-
610 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
612 annoying, but that is the way it is. If you use OR - use
613 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
616 If you want to alter your filter you can just redefine one or more
617 lines of it or clear out one line. For example:-
619 reject/spots 1 on hf/ssb
625 To remove the filter in its entirty:-
629 There are similar CLEAR commands for the other filters:-
637 Once you are happy with the results you get, you may like to experiment.
639 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
640 can be written with a mixed filter, eg:
644 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
646 each filter slot actually has a 'reject' slot and an 'accept'
647 slot. The reject slot is executed BEFORE the accept slot.
649 It was mentioned earlier that after a reject test that doesn't match,
650 the default for following tests is 'accept', the reverse is true for
651 'accept'. In the example what happens is that the reject is executed
652 first, any non hf/cw spot is passed to the accept line, which lets
653 thru everything else on HF.
655 The next filter line lets through just VHF/UHF spots from EU.
657 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
658 This command sends all the latitude and longitude information that your
659 cluster is holding against callsigns. One advantage of recieving this
660 information is that more locator information is held by you. This
661 means that more locators are given on the DX line assuming you have
662 SET/DXGRID enabled. This could be a LOT of information though, so
663 it is not recommended on slow links.
665 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
666 This command sends out any information held in the user file which can
667 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
668 and Homenode. PC41s are only sent for the information that is available.
670 === 0^HELP^The HELP Command
671 HELP is available for a number of commands. The syntax is:-
675 Where <cmd> is the name of the command you want help on.
677 All commands can be abbreviated, so SHOW/DX can be abbreviated
678 to SH/DX, ANNOUNCE can be shortened to AN and so on.
680 Look at the APROPOS <string> command which will search the help database
681 for the <string> you specify and give you a list of likely commands
682 to look at with HELP.
684 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
685 This command attempts to re-initialise a link to a (usually) AK1A node
686 that has got confused, usually by a protocol loop of some kind. It may
687 work - but you usually will be better off simply disconnecting it (or
688 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
691 Best of luck - you will need it.
693 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
694 === 0^KILL <from msgno>-<to msgno>^Delete a range of messages
695 === 0^KILL from <regex>^Delete messages FROM a callsign or pattern
696 === 0^KILL to <regex>^Delete messages TO a callsign or pattern
697 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
698 Delete a message from the local system. You will only be able to
699 delete messages that you have originated or been sent (unless you are
704 Will delete all the messages that you own between msgnos 1234 and 1255.
708 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
712 will delete all messages to g1tlh.
716 will delete a message (usually a 'bulletin') from the whole cluster system.
718 This uses the subject field, so any messages that have exactly the
719 same subject will be deleted. Beware!
721 === 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
722 Deleting a message using the normal KILL commands only marks that message
723 for deletion. The actual deletion only happens later (usually two days later).
725 The KILL EXPUNGE command causes the message to be truly deleted more or less
728 It otherwise is used in the same way as the KILL command.
730 === 0^LINKS^Show which nodes is physically connected
731 This is a quick listing that shows which links are connected and
732 some information about them. See WHO for a list of all connections.
734 === 9^LOAD/ALIASES^Reload the command alias table
735 Reload the /spider/cmd/Aliases file after you have editted it. You
736 will need to do this if you change this file whilst the cluster is
737 running in order for the changes to take effect.
739 === 9^LOAD/BANDS^Reload the band limits table
740 Reload the /spider/data/bands.pl file if you have changed it manually whilst
741 the cluster is running.
743 === 9^LOAD/BADMSG^Reload the bad msg table
744 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
745 the cluster is running. This table contains a number of perl regular
746 expressions which are searched for in the fields targetted of each message.
747 If any of them match then that message is immediately deleted on receipt.
749 === 9^LOAD/BADWORDS^Reload the bad words table
750 Reload the /spider/data/badwords file if you have changed it manually whilst
751 the cluster is running. This file contains a list of words which, if found
752 on certain text portions of PC protocol, will cause those protocol frames
753 to be rejected. It will all put out a message if any of these words are
754 used on the announce, dx and talk commands. The words can be one or
755 more on a line, lines starting with '#' are ignored.
757 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
758 Normally, if you change a command file in the cmd or local_cmd tree it
759 will automatially be picked up by the cluster program. Sometimes it
760 can get confused if you are doing a lot of moving commands about or
761 delete a command in the local_cmd tree and want to use the normal one
762 again. Execute this command to reset everything back to the state it
763 was just after a cluster restart.
765 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
766 Reload the /spider/msg/forward.pl file if you have changed it
767 manually whilst the cluster is running.
769 === 9^LOAD/MESSAGES^Reload the system messages file
770 If you change the /spider/perl/Messages file (usually whilst
771 fiddling/writing new commands) you can have them take effect during a
772 cluster session by executing this command. You need to do this if get
775 unknown message 'xxxx' in lang 'en'
777 === 9^LOAD/PREFIXES^Reload the prefix table
778 Reload the /spider/data/prefix_data.pl file if you have changed it
779 manually whilst the cluster is running.
781 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
782 MERGE allows you to bring your spot and wwv database up to date. By default
783 it will request the last 10 spots and 5 WWVs from the node you select. The
784 node must be connected locally.
786 You can request any number of spots or wwv and although they will be appended
787 to your databases they will not duplicate any that have recently been added
788 (the last 2 days for spots and last month for WWV data).
790 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
791 Alter message parameters like To, From, Subject, whether private or bulletin
792 or return receipt (RR) is required or whether to keep this message from timing
795 MSG TO <msgno> <call> - change TO callsign to <call>
796 MSG FRom <msgno> <call> - change FROM callsign to <call>
797 MSG PRrivate <msgno> - set private flag
798 MSG NOPRrivate <msgno> - unset private flag
799 MSG RR <msgno> - set RR flag
800 MSG NORR <msgno> - unset RR flag
801 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
802 MSG NOKEep <msgno> - unset the keep flag
803 MSG SUbject <msgno> <new> - change the subject to <new>
804 MSG WAittime <msgno> - remove any waitting time for this message
805 MSG NOREad <msgno> - mark message as unread
806 MSG REad <msgno> - mark message as read
807 MSG QUeue - queue any outstanding bulletins
808 MSG QUeue 1 - queue any outstanding private messages
810 You can look at the status of a message by using:-
814 This will display more information on the message than DIR does.
816 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
817 Send some arbitrary text to a locally connected callsign. No
818 processing is done on the text. This command allows you to send PC
819 Protocol to unstick things if problems arise (messages get stuck
822 pc gb7djk PC33^GB7TLH^GB7DJK^400^
824 pc G1TLH Try doing that properly!!!
826 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
827 You can get rid of any message to or originating from your callsign using
828 this command. You can remove more than one message at a time.
830 === 5^KILL <from>-<to>^Remove a range of messages from the system
831 === 5^KILL FROM <call>^Remove all messages from a callsign
832 === 5^KILL TO <call>^Remove all messages to a callsign
833 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
834 Remove this message from the entire cluster system as well as your node.
837 As a sysop you can kill any message on the system.
839 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
840 Send any text you like to the callsign requested. This is used mainly to send
841 PC protocol to connected nodes either for testing or to unstick things.
843 You can also use in the same way as a talk command to a connected user but
844 without any processing, added of "from <blah> to <blah" or whatever.
846 === 1^PING <node call>^Check the link quality between nodes
847 This command allows you to send a frame to another cluster node on
848 the network and get a return frame. The time it takes to do this
849 is a good indication of the quality of the link. The actual time
850 it takes is output to the console in seconds.
851 Any visible cluster node can be PINGed.
853 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
854 This command allows you to send nearly any command to another DX Cluster
855 node that is connected to the system.
857 Whether you get any output is dependant on a) whether the other system knows
858 that the node callsign of this cluster is in fact a node b) whether the
859 other system is allowing RCMDs from this node and c) whether you have
860 permission to send this command at all.
862 === 0^READ^Read the next unread personal message addressed to you
863 === 0^READ <msgno>^Read the specified message
864 You can read any messages that are sent as 'non-personal' and also any
865 message either sent by or sent to your callsign.
868 As a sysop you may read any message on the system
870 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
871 Create an 'reject this announce' line for a filter.
873 A reject filter line means that if the announce matches this filter it is
874 passed onto the user. See HELP FILTERING for more info. Please read this
875 to understand how filters work - it will save a lot of grief later on.
877 You can use any of the following things in this line:-
879 info <string> eg: iota or qsl
880 by <prefixes> eg: G,M,2
882 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
883 origin_itu <prefixes or numbers> or: G,GM,GW
884 origin_zone <prefixes or numbers>
885 by_dxcc <prefixes or numbers>
886 by_itu <prefixes or numbers>
887 by_zone <prefixes or numbers>
889 wx 1 filter WX announces
890 dest <prefixes> eg: 6MUK,WDX (distros)
894 rej/ann by_zone 14,15,16 and not by G,M,2
896 You can use the tag 'all' to reject everything eg:
900 but this probably for advanced users...
902 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
903 This version allows a sysop to set a filter for a callsign as well as the
904 default for nodes and users eg:-
907 reject/ann input node_default by G,M,2
908 reject/ann user_default by G,M,2
910 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
911 Create a 'reject this spot' line for a filter.
913 A reject filter line means that if the spot matches this filter it is
914 dumped (not passed on). See HELP FILTERING for more info. Please read this
915 to understand how filters work - it will save a lot of grief later on.
917 You can use any of the following things in this line:-
919 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
920 on <range> same as 'freq'
921 call <prefixes> eg: G,PA,HB9
922 info <string> eg: iota or qsl
924 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
925 call_itu <prefixes or numbers> or: G,GM,GW
926 call_zone <prefixes or numbers>
927 by_dxcc <prefixes or numbers>
928 by_itu <prefixes or numbers>
929 by_zone <prefixes or numbers>
933 For frequencies, you can use any of the band names defined in
934 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
935 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
936 this is more efficient than saying simply: on HF (but don't get
937 too hung up about that)
942 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
944 You can use the tag 'all' to reject everything eg:
948 but this probably for advanced users...
950 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
951 Create an 'reject this routing PC Protocol' line for a filter.
953 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
954 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
955 read this to understand how filters work - it will save a lot of grief later on.
957 You can use any of the following things in this line:-
959 call <prefixes> the callsign of the thingy
960 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
961 call_itu <prefixes or numbers> or: G,GM,GW
962 call_zone <prefixes or numbers>
963 origin <prefixes> really the interface it came in on
964 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
965 origin_itu <prefixes or numbers> or: G,GM,GW
966 origin_zone <prefixes or numbers>
970 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
972 You can use the tag 'all' to reject everything eg:
974 rej/route all (equiv to [very] restricted mode)
976 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
977 This version allows a sysop to set a filter for a callsign as well as the
978 default for nodes and users eg:-
980 reject/spot db0sue-7 1 by_zone 14,15,16
981 reject/spot node_default all
982 set/hops node_default 10
984 reject/spot user_default by G,M,2
986 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
987 It is unlikely that you will want to do this, but if you do then you can
988 filter on the following fields:-
990 by <prefixes> eg: G,M,2
992 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
993 origin_itu <prefixes or numbers> or: G,GM,GW
994 origin_zone <prefixes or numbers>
995 by_dxcc <prefixes or numbers>
996 by_itu <prefixes or numbers>
997 by_zone <prefixes or numbers>
1000 There are no examples because WCY Broadcasts only come from one place and
1001 you either want them or not (see UNSET/WCY if you don't want them).
1003 This command is really provided for future use.
1005 See HELP FILTER for information.
1007 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
1008 This version allows a sysop to set a filter for a callsign as well as the
1009 default for nodes and users eg:-
1011 reject/wcy gb7djk all
1013 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
1014 It is unlikely that you will want to do this, but if you do then you can
1015 filter on the following fields:-
1017 by <prefixes> eg: G,M,2
1019 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1020 origin_itu <prefixes or numbers> or: G,GM,GW
1021 origin_zone <prefixes or numbers>
1022 by_dxcc <prefixes or numbers>
1023 by_itu <prefixes or numbers>
1024 by_zone <prefixes or numbers>
1029 reject/wwv by_zone 14,15,16
1031 is probably the only useful thing to do (which will only show WWV broadcasts
1032 by stations in the US).
1034 See HELP FILTER for information.
1036 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
1037 This version allows a sysop to set a filter for a callsign as well as the
1038 default for nodes and users eg:-
1040 reject/wwv db0sue-7 1 by_zone 4
1041 reject/wwv node_default all
1043 reject/wwv user_default by W
1045 === 0^REPLY^Reply (privately) to the last message that you have read
1046 === 0^REPLY <msgno>^Reply (privately) to the specified message
1047 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1048 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1049 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1050 You can reply to a message and the subject will automatically have
1051 "Re:" inserted in front of it, if it isn't already present.
1053 You can also use all the extra qualifiers such as RR, PRIVATE,
1054 NOPRIVATE, B that you can use with the SEND command (see SEND
1055 for further details)
1057 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1058 === 0^SEND RR <call>^Send a message and ask for a read receipt
1059 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1060 === 0^SEND PRIVATE <call>^Send a personal message
1061 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1062 All the SEND commands will create a message which will be sent either to
1063 an individual callsign or to one of the 'bulletin' addresses.
1065 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1066 it will mark the message as personal and send it to the cluster node that
1067 that callsign is connected to.
1069 You can have more than one callsign in all of the SEND commands.
1071 You can have multiple qualifiers so that you can have for example:-
1073 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1075 which should send a copy of message 123 to G1TLH and G0RDI and you will
1076 receive a read receipt when they have read the message.
1078 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1079 SP is an alias for SEND PRIVATE
1081 === 0^SET/ADDRESS <your address>^Record your postal address
1083 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1084 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1086 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1087 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1088 The announce system on legacy cluster nodes is used as a talk
1089 substitute because the network is so poorly connected. If you:
1093 you will suppress several of these announces, you may miss the odd
1094 useful one as well, but you would probably miss them anyway in the
1095 welter of useless ones.
1099 allows you to see them again. This is the default.
1101 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1103 === 8^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1104 === 8^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1105 Setting a word as 'baddx' will prevent spots with that word in the
1106 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1107 further. They will not be displayed and they will not be sent onto
1110 The word must be written in full, no wild cards are allowed eg:-
1112 set/baddx FORSALE VIDEO FR0G
1114 To allow a word again, use the following command ...
1118 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1119 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1120 Setting a callsign as a 'badnode' will prevent spots from that node
1121 going any further. They will not be displayed and they will not be
1122 sent onto other nodes.
1124 The call must be a full eg:-
1128 will stop anything from K1TTT. If you want SSIDs as well then you must
1129 enter them specifically.
1133 will allow spots from him again.
1135 Use with extreme care. This command may well be superceeded by FILTERing.
1137 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1138 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1139 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1140 going any further. They will not be displayed and they will not be
1141 sent onto other nodes.
1143 The call must be written in full, no wild cards are allowed eg:-
1145 set/badspotter VE2STN
1147 will stop anything from VE2STN. If you want SSIDs as well then you must
1148 enter them specifically.
1150 unset/badspotter VE2STN
1152 will allow spots from him again.
1154 Use with extreme care. This command may well be superceded by FILTERing.
1156 === 8^SET/BADWORD <word>..^Stop things with this word being propagated
1157 === 8^UNSET/BADWORD <word>..^Propagate things with this word again
1158 Setting a word as a 'badword' will prevent things like spots,
1159 announces or talks with this word in the the text part from going any
1160 further. They will not be displayed and they will not be sent onto
1163 The word must be written in full, no wild cards are allowed eg:-
1165 set/badword annihilate annihilated annihilation
1167 will stop anything with these words in the text.
1169 unset/badword annihilated
1171 will allow text with this word again.
1173 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1174 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1176 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1178 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1180 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1181 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1182 You can choose to log several different levels. The levels are
1190 You can show what levels you are logging with SHOW/DEBUG
1192 === 0^SET/DX^Allow DX messages to come out on your terminal
1193 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1195 === 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
1196 === 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
1197 A standard feature which is enabled in version 1.43 and above is
1198 that if the spotter's grid square is known it is output on the end
1199 of a DX announcement (there is just enough room). Some user programs
1200 cannot cope with this. You can use this command to reset (or set)
1203 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1205 === 0^SET/ECHO^Make the cluster echo your input
1206 === 0^UNSET/ECHO^Stop the cluster echoing your input
1207 If you are connected via a telnet session, different implimentations
1208 of telnet handle echo differently depending on whether you are
1209 connected via port 23 or some other port. You can use this command
1210 to change the setting appropriately.
1212 The setting is stored in your user profile.
1214 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1216 === 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
1217 === 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
1218 If any personal messages come in for your callsign then you can use
1219 these commands to control whether they are forwarded onto your email
1220 address. To enable the forwarding do something like:-
1222 SET/EMAIL mike.tubby@somewhere.com
1224 You can have more than one email address (each one separated by a space).
1225 Emails are forwarded to all the email addresses you specify.
1227 You can disable forwarding by:-
1231 === 0^SET/HERE^Tell the system you are present at your terminal
1232 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1234 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1235 Tell the cluster system where you normally connect to. Any Messages sent
1236 to you will normally find their way there should you not be connected.
1240 === 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
1241 === 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
1242 Set the hop count for a particular type of broadcast for a node.
1244 This command allows you to set up special hop counts for a node
1245 for currently: announce, spots, wwv and wcy broadcasts.
1248 set/hops gb7djk ann 10
1249 set/hops gb7mbc spots 20
1251 Set SHOW/HOPS for information on what is already set. This command
1252 creates a filter and works in conjunction with the filter system.
1254 You can unset the hops with command UNSET/HOPS. For example:-
1256 unset/hops gb7djk ann
1257 unset/hops gb7mbc spots
1260 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1261 Connect a node to your system in such a way that you are a full protocol
1262 member of its network and can see all spots on it, but nothing either leaks
1263 out from it nor goes back into from the rest of the nodes connected to you.
1265 You can potentially connect several nodes in this way.
1267 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1268 Remove isolation from a node - SET/ISOLATE
1270 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1271 You can select the language that you want the cluster to use. Currently
1272 the languages available are en (english) and nl (dutch).
1274 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1275 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1276 In order to get accurate headings and such like you must tell the system
1277 what your latitude and longitude is. If you have not yet done a SET/QRA
1278 then this command will set your QRA locator for you. For example:-
1279 SET/LOCATION 52 22 N 0 57 E
1281 === 0^SET/LOGININFO^Inform when a station logs in locally
1282 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1284 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1285 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1287 === 0^SET/NAME <your name>^Set your name
1288 Tell the system what your name is eg:-
1291 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1292 Tell the system that the call(s) are to be treated as AK1A cluster and
1293 fed PC Protocol rather normal user commands.
1295 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
1296 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1297 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1298 counter which is decremented on every outgoing ping and then reset to
1299 the 'obscount' value on every incoming ping. The default value of this
1302 What this means is that a neighbouring node will be pinged twice at
1303 (default) 300 second intervals and if no reply has been heard just before
1304 what would be the third attempt, that node is disconnected.
1306 If a ping is heard then the obscount is reset to the full value. Using
1307 default values, if a node has not responded to a ping within 15 minutes,
1310 You can set this parameter between 1 and 9.
1312 It is STRONGLY recommended that you don't change the default.
1314 === 0^SET/PAGE <lines per page>^Set the lines per page
1315 Tell the system how many lines you wish on a page when the number of line
1316 of output from a command is more than this. The default is 20. Setting it
1317 explicitly to 0 will disable paging.
1321 The setting is stored in your user profile.
1323 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1324 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1325 in order to determine the rolling quality of the link and, in future, to
1326 affect routing decisions. The default interval is 300 secs or 5 minutes.
1328 You can use this command to set a different interval. Please don't.
1330 But if you do the value you enter is treated as minutes up 30 and seconds
1331 for numbers greater than that.
1333 This is used also to help determine when a link is down at the far end
1334 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1335 for more information.
1337 If you must change it (and it may be useful for internet connected nodes
1338 on dynamic IP addresses that go away after a set time of usage) the time
1339 can be specified as:-
1341 5 which if less than 30 is converted to minutes otherwise is
1342 taken as the no of seconds between pings.
1347 Please be aware that this causes traffic to occur on the link, setting
1348 this value too low may annoy your neighbours beyond the point of
1351 You can switch this off by setting it to 0.
1353 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1354 Set the privilege level on a callsign. The privilege levels that pertain
1355 to commands are as default:-
1357 1 - allow remote nodes normal user RCMDs
1358 5 - various privileged commands (including shutdown, but not disc-
1359 connect), the normal level for another node.
1360 8 - more privileged commands (including disconnect)
1361 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1363 If you are a sysop and you come in as a normal user on a remote connection
1364 your privilege will automatically be set to 0.
1366 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1367 You can use this command to 'protect' this session from unauthorised
1368 use. If you want to get your normal privilege back you will need to
1369 either logout and login again (if you are on a console) or use the
1372 === 0^SET/PASSWORD^Set your own password
1373 This command only works for a 'telnet' user (currently). It will
1374 only work if you have a password already set. This initial password
1375 can only be set by the sysop.
1377 When you execute this command it will ask you for your old password,
1378 then ask you to type in your new password twice (to make sure you
1379 get it right). You may or may not see the data echoed on the screen
1380 as you type, depending on the type of telnet client you have.
1382 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1383 The password for a user can only be set by a full sysop. The string
1384 can contain any characters.
1386 The way this field is used depends on context. If it is being used in
1387 the SYSOP command context then you are offered 5 random numbers and you
1388 have to supply the corresponding letters. This is now mainly for ax25
1391 If it is being used on incoming telnet connections then, if a password
1394 set/var $main::passwdreq = 1
1396 command is executed in the startup script, then a password prompt is
1397 given after the normal 'login: ' prompt.
1399 === 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
1400 This command allows the sysop to completely delete and remove a
1401 password for a user.
1403 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1404 Tell the system that the call(s) are to be treated as DXSpider node and
1405 fed new style DX Protocol rather normal user commands.
1407 === 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
1408 === 0^SET/QRA <locator>^Set your QRA Grid locator
1409 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1410 done a SET/LOCATION then your latitude and longitude will be set roughly
1411 correctly (assuming your locator is correct ;-). For example:-
1414 === 0^SET/QTH <your qth>^Set your QTH
1415 Tell the system where you are. For example:-
1416 SET/QTH East Dereham, Norfolk
1418 === 9^SET/REGISTER <call> ...^Mark a user as registered
1419 === 9^UNSET/REGISTER <call> ...^Mark a user as not registered
1420 Registration is a concept that you can switch on by executing the
1422 set/var $main::regreq = 1
1424 command (usually in your startup file)
1426 If a user is NOT registered then, firstly, instead of the normal
1427 motd file (/spider/data/motd) being sent to the user at startup, the
1428 user is sent the motd_nor file instead. Secondly, the non registered
1429 user only has READ-ONLY access to the node. The non-registered user
1430 cannot use DX, ANN etc.
1432 The only exception to this is that a non-registered user can TALK or
1433 SEND messages to the sysop.
1435 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1436 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1438 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1439 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1441 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1442 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1444 === 0^SET/WX^Allow WX messages to come out on your terminal
1445 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1447 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1448 Display all the bad dx callsigns in the system, see SET/BADDX
1449 for more information.
1451 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1452 Display all the bad node callsigns in the system, see SET/BADNODE
1453 for more information.
1455 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1456 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1457 for more information.
1459 === 1^SHOW/BADWORD^Show all the bad words in the system
1460 Display all the bad words in the system, see SET/BADWORD
1461 for more information.
1463 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1464 This command allows you to see all the users that can be seen
1465 and the nodes to which they are connected.
1467 This command is normally abbreviated to: sh/c
1469 BE WARNED: the list that is returned can be VERY long
1471 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1472 Show all the nodes connected to this node.
1474 === 1^SHOW/CONNECT^Show all the active connections
1475 This command shows information on all the active connections known to
1476 the node. This command gives slightly more information than WHO.
1478 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1479 This is very nearly the same as SHOW/TIME, the only difference the format
1480 of the date string if no arguments are given.
1482 If no prefixes or callsigns are given then this command returns the local
1483 time and UTC as the computer has it right now. If you give some prefixes
1484 then it will show UTC and UTC + the local offset (not including DST) at
1485 the prefixes or callsigns that you specify.
1487 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1489 === 0^SHOW/DX^Interrogate the spot database
1490 If you just type SHOW/DX you will get the last so many spots
1491 (sysop configurable, but usually 10).
1493 In addition you can add any number of these commands in very nearly
1494 any order to the basic SHOW/DX command, they are:-
1496 on <band> - eg 160m 20m 2m 23cm 6mm
1497 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1499 <number> - the number of spots you want
1500 <from>-<to> - <from> spot no <to> spot no in the selected list
1502 <prefix> - for a spotted callsign beginning with <prefix>
1503 *<suffix> - for a spotted callsign ending in <suffix>
1504 *<string>* - for a spotted callsign containing <string>
1506 day <number> - starting <number> days ago
1507 day <from>-<to> - <from> days <to> days ago
1509 info <text> - any spots containing <text> in the info or remarks
1511 by <call> - any spots spotted by <call> (spotter <call> is the
1514 qsl - this automatically looks for any qsl info on the call
1515 held in the spot database.
1517 iota [<iota>] - If the iota island number is missing it will look for
1518 the string iota and anything which looks like an iota
1519 island number. If you specify then it will look for
1522 qra [<locator>] - this will look for the specific locator if you specify
1523 one or else anything that looks like a locator.
1528 SH/DX on 20m info iota
1529 SH/DX 9a on vhf day 30
1535 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1536 This command takes the <prefix> (which can be a full or partial
1537 callsign if desired), looks up which internal country number it is
1538 and then displays all the spots as per SH/DX for that country.
1540 The options for SHOW/DX also apply to this command.
1544 SH/DXCC W on 20m info iota
1546 === 0^SHOW/DXSTATS^Show the DX Statistics for last 31 days
1547 Show the total DX spots for the last 31 days
1549 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1550 SHOW/FILES on its own will show you a list of the various fileareas
1551 available on the system. To see the contents of a particular file
1554 where <filearea> is the name of the filearea you want to see the
1557 You can also use shell globbing characters like '*' and '?' in a
1558 string to see a selection of files in a filearea eg:-
1559 SH/FILES bulletins arld*
1561 See also TYPE - to see the contents of a file.
1563 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1564 Show the contents of all the filters that are set. This command displays
1565 all the filters set - for all the various categories.
1567 === 0^SHOW/HFSTATS^Show the HF DX Statistics for last 31 days
1568 Show the HF DX spots breakdown by band for the last 31 days
1570 === 0^SHOW/HFTABLE^Show the HF DX Spotter Table for your country
1571 Show the HF DX Spotter table for your country for the last 31 days
1573 === 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
1574 This command shows the hop counts set up for a node. You can specify
1575 which category you want to see. If you leave the category out then
1576 all the categories will be listed.
1578 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1580 === 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
1582 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
1583 This command outputs a short section of the system log. On its own
1584 it will output a general logfile. With the optional callsign it will
1585 show output from the log associated with that callsign.
1587 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
1588 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1589 together with the azimuth and elevation of the sun currently at those
1592 If you don't specify any prefixes or callsigns, it will show the times for
1593 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1594 together with the current azimuth and elevation.
1596 In addition, it will show the gain or loss dB relative to the nominal
1597 distance of 385,000Km due to the ellipsoidal nature of the orbit.
1599 If all else fails it will show the Moonrise and set times for the node
1600 that you are connected to.
1607 You can also use this command to see into the past or the future, so
1608 if you want to see yesterday's times then do:-
1612 or in three days time:-
1616 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1617 This command allow you to estimate the likelihood of you contacting
1618 a station with the prefix you have specified. The output assumes a modest
1619 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1621 The result predicts the most likely operating frequencies and signal
1622 levels for high frequency (shortwave) radio propagation paths on
1623 specified days of the year and hours of the day. It is most useful for
1624 paths between 250 km and 6000 km, but can be used with reduced accuracy
1625 for paths shorter or longer than this.
1627 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1628 used to predict the MUF given the predicted flux, day of the year,
1629 hour of the day and geographic coordinates of the transmitter and
1630 receiver. This routine is reasonably accurate for the purposes here,
1631 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1632 than the programs used by major shortwave broadcasting organizations,
1633 such as the Voice of America.
1635 The command will display some header information detailing its
1636 assumptions, together with the locations, latitude and longitudes and
1637 bearings. It will then show UTC (UT), local time at the other end
1638 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1639 (Zen) and the likely signal strengths. Then for each frequency for which
1640 the system thinks there is a likelihood of a circuit it prints a value.
1642 The value is currently a likely S meter reading based on the conventional
1643 6dB / S point scale. If the value has a '+' appended it means that it is
1644 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1645 there is likely to be much fading and by an 's' that the signal is likely
1648 By default SHOW/MUF will show the next two hours worth of data. You
1649 can specify anything up to 24 hours worth of data by appending the no of
1650 hours required after the prefix. For example:-
1656 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1657 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1658 Location Lat / Long Azim
1659 East Dereham, Norfolk 52 41 N 0 57 E 47
1660 United-States-W 43 0 N 87 54 W 299
1661 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1662 18 23 11.5 -35 mS0+ mS2 S3
1663 19 0 11.2 -41 mS0+ mS2 S3
1665 indicating that you will have weak, fading circuits on top band and
1666 80m but usable signals on 40m (about S3).
1672 will get you the above display, but with the next 24 hours worth of
1678 Gives you an estimate of the long path propagation characterics. It
1679 should be noted that the figures will probably not be very useful, nor
1680 terrible accurate, but it is included for completeness.
1682 === 0^SHOW/NEWCONFIGURATION [<node>]^Show all the nodes and users visible
1683 This command allows you to see all the users that can be seen
1684 and the nodes to which they are connected.
1686 This command produces essentially the same information as
1687 SHOW/CONFIGURATION except that it shows all the duplication of
1688 any routes that might be present It also uses a different format
1689 which may not take up quite as much space if you don't have any
1692 BE WARNED: the list that is returned can be VERY long
1694 === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
1695 Show all the nodes connected to this node in the new format.
1697 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1698 Show the type and version (if connected) of the nodes specified on the
1699 command line. If no callsigns are specified then a sorted list of all
1700 the non-user callsigns known to the system will be displayed.
1702 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1703 This command takes the <callsign> (which can be a full or partial
1704 callsign or a prefix), looks up which internal country number
1705 it is and then displays all the relevant prefixes for that country
1706 together with the internal country no, the CQ and ITU regions.
1710 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1711 Show the name and location where every program module was load from. This
1712 is useful for checking where you think you have loaded a .pm file from.
1714 === 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
1715 === 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
1716 This is a multipurpose command that allows you either to calculate the
1717 distance and bearing between two locators or (if only one locator is
1718 given on the command line) the distance and beraing from your station
1719 to the locator. For example:-
1724 The first example will show the distance and bearing to the locator from
1725 yourself, the second example will calculate the distance and bearing from
1726 the first locator to the second. You can use 4 or 6 character locators.
1728 It is also possible to convert a latitude and longitude to a locator by
1729 using this command with a latitude and longitude as an argument, for
1732 SH/QRA 52 41 N 0 58 E
1734 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
1735 This command queries the QRZ callbook server on the internet
1736 and returns any information available for that callsign. This service
1737 is provided for users of this software by http://www.qrz.com
1739 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
1741 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
1742 This command allows you to see to which node the callsigns specified are
1743 connected. It is a sort of inverse sh/config.
1747 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1748 Show the tracking data from your location to the satellite of your choice
1749 from now on for the next few hours.
1751 If you use this command without a satellite name it will display a list
1752 of all the satellites known currently to the system.
1754 If you give a name then you can obtain tracking data of all the passes
1755 that start and finish 5 degrees below the horizon. As default it will
1756 give information for the next three hours for every five minute period.
1758 You can alter the number of hours and the step size, within certain
1761 Each pass in a period is separated with a row of '-----' characters
1766 SH/SAT FENGYUN1 12 2
1768 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
1769 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
1770 Show the information known about a callsign and whether (and where)
1771 that callsign is connected to the cluster.
1775 If no callsign is given then show the information for yourself.
1777 === 0^SHOW/SUN [+/- days][<prefix>|<callsign>]^Show sun rise and set times
1778 Show the sun rise and set times for a (list of) prefixes or callsigns,
1779 together with the azimuth and elevation of the sun currently at those
1782 If you don't specify any prefixes or callsigns, it will show the times for
1783 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1784 together with the current azimuth and elevation.
1786 If all else fails it will show the sunrise and set times for the node
1787 that you are connected to.
1792 SH/SUN G1TLH K9CW ZS
1794 You can also use this command to see into the past or the future, so
1795 if you want to see yesterday's times then do:-
1799 or in three days time:-
1803 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
1804 If no prefixes or callsigns are given then this command returns the local
1805 time and UTC as the computer has it right now. If you give some prefixes
1806 then it will show UTC and UTC + the local offset (not including DST) at
1807 the prefixes or callsigns that you specify.
1809 === 0^SHOW/VHFSTATS^Show the VHF DX Statistics for last 31 days
1810 Show the VHF DX spots breakdown by band for the last 31 days
1812 === 0^SHOW/VHFTABLE^Show the VHF DX Spotter Table for your country
1813 Show the VHF DX Spotter table for your country for the last 31 days
1815 === 0^SHOW/WCY^Show last 10 WCY broadcasts
1816 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
1817 Display the most recent WCY information that has been received by the system
1819 === 0^SHOW/WWV^Show last 10 WWV broadcasts
1820 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
1821 Display the most recent WWV information that has been received by the system
1823 === 5^SHUTDOWN^Shutdown the cluster
1824 Shutdown the cluster and disconnect all the users
1826 === 9^SPOOF <call> <command>^Do a command as though you are another user
1827 This command is provided so that sysops can set a user's parameters without
1828 me having to write a special 'sysop' version for every user command. It
1829 allows you to pretend that you are doing the command as the user you specify.
1833 SPOOF G1TLH set/name Dirk
1834 SPOOF G1TLH set/qra JO02LQ
1836 === 5^STAT/DB <dbname>^Show the status of a database
1837 Show the internal status of a database descriptor.
1839 Depending on your privilege level you will see more or less information.
1840 This command is unlikely to be of much use to anyone other than a sysop.
1842 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
1843 Show the internal status of the channel object either for the channel that
1844 you are on or else for the callsign that you asked for.
1846 Only the fields that are defined (in perl term) will be displayed.
1848 === 1^STAT/MSG^Show the status of the message system
1849 === 1^STAT/MSG <msgno>^Show the status of a message
1850 This command shows the internal status of a message and includes information
1851 such as to whom it has been forwarded, its size, origin etc etc.
1853 If no message number is given then the status of the message system is
1856 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
1857 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
1859 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
1860 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
1862 === 5^STAT/USER [<callsign>]^Show the full status of a user
1863 Shows the full contents of a user record including all the secret flags
1866 Only the fields that are defined (in perl term) will be displayed.
1868 === 0^SYSOP^Regain your privileges if you login remotely
1869 The system automatically reduces your privilege level to that of a
1870 normal user if you login in remotely. This command allows you to
1871 regain your normal privilege level. It uses the normal system: five
1872 numbers are returned that are indexes into the character array that is
1873 your assigned password (see SET/PASSWORD). The indexes start from
1876 You are expected to return a string which contains the characters
1877 required in the correct order. You may intersperse those characters
1878 with others to obscure your reply for any watchers. For example (and
1879 these values are for explanation :-):
1881 password = 012345678901234567890123456789
1885 aa2bbbb0ccc5ddd7xxx3n
1889 They will all match. If there is no password you will still be offered
1890 numbers but nothing will happen when you input a string. Any match is
1893 === 0^TALK <call> [<text>]^Send a text message to another station
1894 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
1895 Send a short message to any other station that is visible on the cluster
1896 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
1897 command, they don't have to be connected locally.
1899 The second form of TALK is used when other cluster nodes are connected
1900 with restricted information. This usually means that they don't send
1901 the user information usually associated with logging on and off the cluster.
1903 If you know that G3JNB is likely to be present on GB7TLH, but you can only
1904 see GB7TLH in the SH/C list but with no users, then you would use the
1905 second form of the talk message.
1907 If you want to have a ragchew with someone you can leave the text message
1908 out and the system will go into 'Talk' mode. What this means is that a
1909 short message is sent to the recipient telling them that you are in a
1910 'Talking' frame of mind and then you just type - everything you send will
1911 go to the station that you asked for.
1913 All the usual announcements, spots and so on will still come out on your
1916 If you want to do something (such as send a spot) you preceed the normal
1917 command with a '/' character, eg:-
1919 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
1922 To leave talk mode type:
1926 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
1927 Type out the contents of a file in a filearea. So, for example, in
1928 filearea 'bulletins' you want to look at file 'arld051' you would
1930 TYPE bulletins/arld051
1932 See also SHOW/FILES to see what fileareas are available and a
1935 === 0^WHO^Show who is physically connected
1936 This is a quick listing that shows which callsigns are connected and
1937 what sort of connection they have
1939 === 0^WX <text>^Send a weather message to local users
1940 === 0^WX FULL <text>^Send a weather message to all cluster users
1941 === 5^WX SYSOP <text>^Send a weather message to other clusters only
1942 Weather messages can sometimes be useful if you are experiencing an extreme
1943 that may indicate enhanced conditions