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
14 # Comment lines are indented before printing
16 === 0^ACCEPT^Set a filter to accept something
17 Create a filter to accept something
19 There are 2 types of filter, accept and reject. See HELP FILTERING for more
22 === 0^ACCEPT/ANNOUNCE [0-9] <pattern>^Set an 'accept' filter line for announce
23 Create an 'accept this announce' line for a filter.
25 An accept filter line means that if the announce matches this filter it is
26 passed onto the user. See HELP FILTERING for more info. Please read this
27 to understand how filters work - it will save a lot of grief later on.
29 You can use any of the following things in this line:-
31 info <string> eg: iota or qsl
32 by <prefixes> eg: G,M,2
34 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
35 origin_itu <prefixes or numbers> or: G,GM,GW
36 origin_zone <prefixes or numbers>
37 origin_state <states> eg: VA,NH,RI,NH
38 by_dxcc <prefixes or numbers>
39 by_itu <prefixes or numbers>
40 by_zone <prefixes or numbers>
43 wx 1 filter WX announces
44 dest <prefixes> eg: 6MUK,WDX (distros)
49 acc/ann 2 by_zone 14,15,16
50 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
56 acc/ann by_state va,nh,ri,nh
58 You can use the tag 'all' to accept everything eg:
62 but this probably for advanced users...
64 === 8^ACCEPT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
65 This version allows a sysop to set a filter for a callsign as well as the
66 default for nodes and users eg:-
69 accept/ann input node_default by G,M,2
70 accept/ann user_default by G,M,2
72 === 8^ACCEPT/ROUTE <call> [0-9] <pattern>^Set an 'accept' filter line for routing
73 Create an 'accept this routing PC Protocol' line for a filter.
75 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
76 it is passed thru that interface. See HELP FILTERING for more info. Please read this
77 to understand how filters work - it will save a lot of grief later on.
79 You can use any of the following things in this line:-
81 call <prefixes> the callsign of the thingy
82 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
83 call_itu <prefixes or numbers> or: G,GM,GW
84 call_zone <prefixes or numbers>
85 call_state <states> eg: VA,NH,RI,NH
86 origin <prefixes> really the interface it came in on
87 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
88 origin_itu <prefixes or numbers> or: G,GM,GW
89 origin_zone <prefixes or numbers>
90 origin_state <states> eg: VA,NH,RI,NH
94 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
95 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
97 you can now use 'by' as a synonym for 'call' so:
104 You can use the tag 'all' to accept everything eg:
109 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
110 Create an 'accept this spot' line for a filter.
112 An accept filter line means that if the spot matches this filter it is
113 passed onto the user. See HELP FILTERING for more info. Please read this
114 to understand how filters work - it will save a lot of grief later on.
116 You can use any of the following things in this line:-
118 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
119 on <range> same as 'freq'
120 call <prefixes> eg: G,PA,HB9
121 info <string> eg: iota or qsl
123 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
124 call_itu <prefixes or numbers> or: G,GM,GW
125 call_zone <prefixes or numbers>
126 call_state <states> eg: VA,NH,RI,ME
127 by_dxcc <prefixes or numbers>
128 by_itu <prefixes or numbers>
129 by_zone <prefixes or numbers>
130 by_state <states> eg: VA,NH,RI,ME
134 'call' means the callsign that has spotted 'by' whoever.
136 For frequencies, you can use any of the band names defined in
137 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
138 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
139 this is more efficient than saying simply: freq HF (but don't get
140 too hung up about that)
145 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
147 You can use the tag 'all' to accept everything, eg:
153 acc/spots by_state VA,NH,RI,MA,ME
155 but this probably for advanced users...
158 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot 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/spot db0sue-7 1 by_zone 14,15,16
163 accept/spot node_default all
164 set/hops node_default 10
166 accept/spot user_default by G,M,2
168 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
169 It is unlikely that you will want to do this, but if you do then you can
170 filter on the following fields:-
172 by <prefixes> eg: G,M,2
174 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
175 origin_itu <prefixes or numbers> or: G,GM,GW
176 origin_zone <prefixes or numbers>
177 by_dxcc <prefixes or numbers>
178 by_itu <prefixes or numbers>
179 by_zone <prefixes or numbers>
182 There are no examples because WCY Broadcasts only come from one place and
183 you either want them or not (see UNSET/WCY if you don't want them).
185 This command is really provided for future use.
187 See HELP FILTER for information.
189 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
190 This version allows a sysop to set a filter for a callsign as well as the
191 default for nodes and users eg:-
193 accept/wcy node_default all
194 set/hops node_default 10
196 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
197 It is unlikely that you will want to do this, but if you do then you can
198 filter on the following fields:-
200 by <prefixes> eg: G,M,2
202 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
203 origin_itu <prefixes or numbers> or: G,GM,GW
204 origin_zone <prefixes or numbers>
205 by_dxcc <prefixes or numbers>
206 by_itu <prefixes or numbers>
207 by_zone <prefixes or numbers>
214 is probably the only useful thing to do (which will only show WWV broadcasts
215 by stations in the US).
217 See HELP FILTER for information.
219 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
220 This version allows a sysop to set a filter for a callsign as well as the
221 default for nodes and users eg:-
223 accept/wwv db0sue-7 1 by_zone 4
224 accept/wwv node_default all
225 set/hops node_default 10
227 accept/wwv user_default by W,K
229 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
230 <text> is the text of the announcement you wish to broadcast
232 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
233 This will send your announcement cluster wide
235 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
237 === 0^APROPOS <string>^Search help database for <string>
238 Search the help database for <string> (it isn't case sensitive), and print
239 the names of all the commands that may be relevant.
241 === 0^BLANK [<string>] [<nn>]^Print nn (default 1) blank lines (or strings)
242 In its basic form this command prints one or more blank lines. However if
243 you pass it a string it will replicate the string for the width of the
244 screen (default 80) and then print that one or more times, so:
248 prints two blank lines
252 prints a row of - characters once.
256 prints 'abcabcabcabcabcabc....'
258 This is really only of any use in a script file and you can print a maximum
261 === 0^BYE^Exit from the cluster
262 This will disconnect you from the cluster
264 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
265 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
266 When you send messages the fact that you have forwarded it to another node
267 is remembered so that it isn't sent again. When you have a new partner
268 node and you add their callsign to your /spider/msg/forward.pl file, all
269 outstanding non-private messages will be forwarded to them. This may well
270 be ALL the non-private messages. You can prevent this by using these
274 catchup GB7DJK 300 301 302 303 500-510
276 and to undo what you have just done:-
279 uncatchup GB7DJK 300 301 302 303 500-510
281 which will arrange for them to be forward candidates again.
283 Order is not important.
285 === 0^CHAT <group> <text>^Chat or Conference to a group
286 It is now possible to JOIN a group and have network wide conferencing to that
287 group. DXSpider does not (and probably will not) implement the AK1A
288 conference mode as this seems very limiting, is hardly used and doesn't seem
289 to work too well anyway.
291 This system uses the existing ANN system and is compatible with both other
292 DXSpider nodes and AK1A clusters (they use ANN/<group>).
294 You can be a member of as many "groups" as you want. To join a group type:-
296 JOIN FOC (where FOC is the group name)
298 To leave a group type:-
302 You can see which groups you are in by typing:-
306 and you can see whether your mate is in the group, if he connects to the
307 same node as you, by typing:-
311 To send a message to a group type:-
313 CHAT FOC hello everyone
317 CH #9000 hello I am back
319 See also JOIN, LEAVE, SHOW/CHAT
321 === 0^CLEAR/ANNOUNCE [1|all]^Clear a announce filter line
322 This command allows you to clear (remove) a line in a annouce filter or to
323 remove the whole filter.
325 see CLEAR/SPOTS for a more detailed explanation.
327 === 8^CLEAR/ANNOUNCE <callsign> [input] [0-9|all]^Clear a announce filter line
328 A sysop can clear an input or normal output filter for a user or the
329 node_default or user_default.
331 === 0^CLEAR/ROUTE [1|all]^Clear a route filter line
332 This command allows you to clear (remove) a line in a route filter or to
333 remove the whole filter.
335 see CLEAR/SPOTS for a more detailed explanation.
337 === 8^CLEAR/ROUTE <callsign> [input] [0-9|all]^Clear a route filter line
338 A sysop can clear an input or normal output filter for a user or the
339 node_default or user_default.
341 === 0^CLEAR/SPOTS [0-9|all]^Clear a spot filter line
342 This command allows you to clear (remove) a line in a spot filter or to
343 remove the whole filter.
345 If you have a filter:-
348 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
354 you will be left with:-
356 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
362 the filter will be completely removed.
364 === 8^CLEAR/SPOTS <callsign> [input] [0-9|all]^Clear a spot filter line
365 A sysop can clear an input or normal output filter for a user or the
366 node_default or user_default.
368 === 0^CLEAR/WCY [1|all]^Clear a WCY filter line
369 This command allows you to clear (remove) a line in a WCY filter or to
370 remove the whole filter.
372 see CLEAR/SPOTS for a more detailed explanation.
374 === 8^CLEAR/WCY <callsign> [input] [0-9|all]^Clear a WCY filter line
375 A sysop can clear an input or normal output filter for a user or the
376 node_default or user_default.
378 === 0^CLEAR/WWV [1|all]^Clear a WWV filter line
379 This command allows you to clear (remove) a line in a WWV filter or to
380 remove the whole filter.
382 see CLEAR/SPOTS for a more detailed explanation.
384 === 8^CLEAR/WWV <callsign> [input] [0-9|all]^Clear a WWV filter line
385 A sysop can clear an input or normal output filter for a user or the
386 node_default or user_default.
388 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
389 Start a connection process that will culminate in a new connection to the
390 DX cluster <callsign>. This process creates a new 'client' process which will
391 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
392 necessary to traverse the network(s) to logon to the cluster <callsign>.
394 === 9^DELETE/USDB <callsign> ...^Delete this user from the US State Database
395 This command will completely remove a one or more callsigns
396 from the US States database.
398 There is NO SECOND CHANCE.
400 It goes without saying that you should use this command CAREFULLY!
402 Note that these callsign may be re-instated by any weekly updates from
405 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
406 This command will completely remove a one or more users from the database.
408 There is NO SECOND CHANCE.
410 It goes without saying that you should use this command CAREFULLY!
412 === 0^DBAVAIL^Show a list of all the Databases in the system
413 Title says it all really, this command lists all the databases defined
414 in the system. It is also aliased to SHOW/COMMAND.
416 === 9^DBCREATE <name>^Create a database entry
417 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
418 === 9^DBCREATE <name> remote <node>^Create a remote database entry
419 === 9^DBCREATE <name> cmd <dxspider command>^make a local command available as a DB
420 DBCREATE allows you to define a database in the system. It doesn't actually
421 create anything, just defines it.
423 The databases that are created are simple DB_File hash databases, they are
424 therefore already 'indexed'.
426 You can define a local database with the first form of the command eg:
430 You can also chain databases with the addition of the 'chain' keyword.
431 This will search each database one after the other. A typical example
434 DBCREATE sdx_qsl chain sql_ad
436 No checking is done to see if the any of the chained databases exist, in
437 fact it is usually better to do the above staement first then do each of
438 the chained databases.
440 Databases can exist offsite. To define a database that lives on another
443 DBCREATE buckmaster remote gb7dxc
445 Remote databases cannot be chained; however, the last database in a
446 a chain can be a remote database eg:
448 DBCREATE qsl chain gb7dxc
450 To see what databases have been defined do:
452 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
454 It would be normal for you to add an entry into your local Aliases file
455 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
456 need to add a line like:-
461 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
470 to work as they may be used to.
472 You can also make local commands available as 'pseudo' databases. You
473 can therefore make spider special commands available as a database. I
474 imagine that this will be primarily useful for remote access from
475 legacy nodes. For example:-
477 DBCREATE dxqsl cmd show/dxqsl
479 You also use one of these databases in a chain. This may be useful
482 See DBIMPORT for the importing of existing AK1A format data to databases.
483 See DBSHOW for generic database enquiry
485 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
486 If you want to import or update data in bulk to a database you can use
487 this command. It will either create or update entries into an existing
488 database. For example:-
490 DBIMPORT oblast /tmp/OBLAST.FUL
492 will import the standard OBLAST database that comes with AK1A into the
493 oblast database held locally.
495 === 9^DBREMOVE <dbname>^Delete a database
496 DBREMOVE will completely remove a database entry and also delete any data
497 file that is associated with it.
499 There is no warning, no comeback, no safety net.
505 will remove the oblast database from the system and it will also remove
506 the associated datafile.
510 There is no warning, no comeback, no safety net.
512 You have been warned.
514 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
515 This is the generic user interface to the database to the database system.
516 It is expected that the sysop will add an entry to the local Aliases file
517 so that users can use the more familiar AK1A style of enquiry such as:
521 but if he hasn't and the database really does exist (use DBAVAIL or
522 SHOW/COMMAND to find out) you can do the same thing with:
526 === 9^DEBUG^Set the cluster program into debug mode
527 Executing this command will only have an effect if you are running the cluster
532 It will interrupt the cluster just after the debug command has finished.
534 === 0^DIRECTORY^List messages
535 === 0^DIRECTORY ALL^List all messages
536 === 0^DIRECTORY OWN^List your own messages
537 === 0^DIRECTORY NEW^List all new messages
538 === 0^DIRECTORY TO <call>^List all messages to <call>
539 === 0^DIRECTORY FROM <call>^List all messages from <call>
540 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
541 === 0^DIRECTORY <nn>^List last <nn> messages
542 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
543 List the messages in the messages directory.
545 If there is a 'p' one space after the message number then it is a
546 personal message. If there is a '-' between the message number and the
547 'p' then this indicates that the message has been read.
549 You can use shell escape characters such as '*' and '?' in the <call>
552 You can combine some of the various directory commands together eg:-
556 DIR SUBJECT IOTA 200-250
558 You can abbreviate all the commands to one letter and use ak1a syntax:-
564 Sysops can see all users' messages.
566 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
567 Disconnect any <call> connected locally
569 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
570 This is how you send a DX Spot to other users. You can, in fact, now
571 enter the <freq> and the <call> either way round.
577 will all give the same result. You can add some remarks to the end
578 of the command and they will be added to the spot.
580 DX FR0G 144600 this is a test
582 You can credit someone else by saying:-
584 DX by G1TLH FR0G 144.600 he isn't on the cluster
586 The <freq> is compared against the available bands set up in the
587 cluster. See SHOW/BANDS for more information.
589 === 0^ECHO <line>^Echo the line to the output
590 This command is useful in scripts and so forth for printing the
591 line that you give to the command to the output. You can use this
592 in user_default scripts and the SAVE command for titling and so forth
594 The script will interpret certain standard "escape" sequences as follows:-
596 \t - becomes a TAB character (0x09 in ascii)
597 \a - becomes a BEEP character (0x07 in ascii)
598 \n - prints a new line
600 So the following example:-
602 echo GB7DJK is a dxcluster
606 GB7DJK is a dxcluster
608 on the output. You don't need a \n on the end of the line you want to send.
610 A more complex example:-
612 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
622 === 9^EXPORT <msgno> <filename>^Export a message to a file
623 Export a message to a file. This command can only be executed on a local
624 console with a fully privileged user. The file produced will be in a form
625 ready to be imported back into the cluster by placing it in the import
626 directory (/spider/msg/import).
628 This command cannot overwrite an existing file. This is to provide some
629 measure of security. Any files written will owned by the same user as the
630 main cluster, otherwise you can put the new files anywhere the cluster can
631 access. For example:-
635 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
636 Export the users database to a file in ascii format. If no filename
637 is given then it will export the file to /spider/data/user_asc.
639 If the file already exists it will be renamed to <filename>.o. In fact
640 up to 5 generations of the file can be kept each one with an extra 'o' on the
643 BE WARNED: this will write to any file you have write access to. No check is
644 made on the filename (if any) that you specify.
646 === 0^FILTERING...^Filtering things in DXSpider
647 There are a number of things you can filter in the DXSpider system. They
648 all use the same general mechanism.
650 In general terms you can create a 'reject' or an 'accept' filter which
651 can have up to 10 lines in it. You do this using, for example:-
656 where ..... are the specific commands for that type of filter. There
657 are filters for spots, wwv, announce, wcy and (for sysops)
658 connects. See each different accept or reject command reference for
661 There is also a command to clear out one or more lines in a filter and
662 one to show you what you have set. They are:-
671 There is clear/xxxx command for each type of filter.
673 For now we are going to use spots for the examples, but you can apply
674 the principles to all types of filter.
676 There are two main types of filter 'accept' or 'reject'; which you use
677 depends entirely on how you look at the world and what is least
678 writing to achieve what you want. Each filter has 10 lines (of any
679 length) which are tried in order. If a line matches then the action
680 you have specified is taken (ie reject means ignore it and accept
683 The important thing to remember is that if you specify a 'reject'
684 filter (all the lines in it say 'reject/spots' (for instance)) then if
685 a spot comes in that doesn't match any of the lines then you will get
686 it BUT if you specify an 'accept' filter then any spots that don't
687 match are dumped. For example if I have a one line accept filter:-
689 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
691 then automatically you will ONLY get VHF spots from or to CQ zones 14
692 15 and 16. If you set a reject filter like:
694 reject/spots on hf/cw
696 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
697 and will work it even on CW then you could say:-
699 reject/spots on hf/cw and not info iota
701 But in that case you might only be interested in iota and say:-
703 accept/spots not on hf/cw or info iota
705 which is exactly the same. You should choose one or the other until
706 you are confortable with the way it works. Yes, you can mix them
707 (actually you can have an accept AND a reject on the same line) but
708 don't try this at home until you can analyse the results that you get
709 without ringing up the sysop for help.
711 Another useful addition now is filtering by US state
713 accept/spots by_state VA,NH,RI,ME
715 You can arrange your filter lines into logical units, either for your
716 own understanding or simply convenience. I have one set frequently:-
718 reject/spots 1 on hf/cw
719 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
721 What this does is to ignore all HF CW spots (being a class B I can't
722 read any CW and couldn't possibly be interested in HF :-) and also
723 rejects any spots on VHF which don't either originate or spot someone
726 This is an exmaple where you would use the line number (1 and 2 in
727 this case), if you leave the digit out, the system assumes '1'. Digits
728 '0'-'9' are available.
730 You can leave the word 'and' out if you want, it is implied. You can
731 use any number of brackets to make the 'expression' as you want
732 it. There are things called precedence rules working here which mean
733 that you will NEED brackets in a situation like line 2 because,
734 without it, will assume:-
736 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
738 annoying, but that is the way it is. If you use OR - use
739 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
742 If you want to alter your filter you can just redefine one or more
743 lines of it or clear out one line. For example:-
745 reject/spots 1 on hf/ssb
751 To remove the filter in its entirty:-
755 There are similar CLEAR commands for the other filters:-
763 Once you are happy with the results you get, you may like to experiment.
765 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
766 can be written with a mixed filter, eg:
770 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
772 each filter slot actually has a 'reject' slot and an 'accept'
773 slot. The reject slot is executed BEFORE the accept slot.
775 It was mentioned earlier that after a reject test that doesn't match,
776 the default for following tests is 'accept', the reverse is true for
777 'accept'. In the example what happens is that the reject is executed
778 first, any non hf/cw spot is passed to the accept line, which lets
779 thru everything else on HF.
781 The next filter line lets through just VHF/UHF spots from EU.
783 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
784 This command sends all the latitude and longitude information that your
785 cluster is holding against callsigns. One advantage of recieving this
786 information is that more locator information is held by you. This
787 means that more locators are given on the DX line assuming you have
788 SET/DXGRID enabled. This could be a LOT of information though, so
789 it is not recommended on slow links.
791 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
792 This command sends out any information held in the user file which can
793 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
794 and Homenode. PC41s are only sent for the information that is available.
796 === 0^HELP^The HELP Command
797 HELP is available for a number of commands. The syntax is:-
801 Where <cmd> is the name of the command you want help on.
803 All commands can be abbreviated, so SHOW/DX can be abbreviated
804 to SH/DX, ANNOUNCE can be shortened to AN and so on.
806 Look at the APROPOS <string> command which will search the help database
807 for the <string> you specify and give you a list of likely commands
808 to look at with HELP.
810 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
811 This command attempts to re-initialise a link to a (usually) AK1A node
812 that has got confused, usually by a protocol loop of some kind. It may
813 work - but you usually will be better off simply disconnecting it (or
814 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
817 Best of luck - you will need it.
819 === 9^DEMONSTRATE <call> <command>^Demonstrate a command to another user
820 This command is provided so that sysops can demonstrate commands to
821 other users. It runs a command as though that user had typed it in and
822 then sends the output to that user, together with the command that
825 DEMO g7brn sh/dx iota oc209
828 Note that this command is similar to SPOOF and will have the same side
829 effects. Commands are run at the privilege of the user which is being
832 === 0^JOIN <group>^Join a chat or conference group
833 JOIN allows you to join a network wide conference group. To join a
834 group (called FOC in this case) type:-
838 See also CHAT, LEAVE, SHOW/CHAT
840 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
841 === 0^KILL <from msgno>-<to msgno>^Delete a range of messages
842 === 0^KILL from <regex>^Delete messages FROM a callsign or pattern
843 === 0^KILL to <regex>^Delete messages TO a callsign or pattern
844 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
845 Delete a message from the local system. You will only be able to
846 delete messages that you have originated or been sent (unless you are
851 Will delete all the messages that you own between msgnos 1234 and 1255.
855 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
859 will delete all messages to g1tlh.
863 will delete a message (usually a 'bulletin') from the whole cluster system.
865 This uses the subject field, so any messages that have exactly the
866 same subject will be deleted. Beware!
868 === 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
869 Deleting a message using the normal KILL commands only marks that message
870 for deletion. The actual deletion only happens later (usually two days later).
872 The KILL EXPUNGE command causes the message to be truly deleted more or less
875 It otherwise is used in the same way as the KILL command.
877 === 0^LEAVE <group>^Leave a chat or conference group
878 LEAVE allows you to leave a network wide conference group. To leave a
879 group (called FOC in this case) type:-
883 See also CHAT, JOIN, SHOW/CHAT
885 === 0^LINKS^Show which nodes is physically connected
886 This is a quick listing that shows which links are connected and
887 some information about them. See WHO for a list of all connections.
889 === 9^LOAD/ALIASES^Reload the command alias table
890 Reload the /spider/cmd/Aliases file after you have editted it. You
891 will need to do this if you change this file whilst the cluster is
892 running in order for the changes to take effect.
894 === 9^LOAD/BANDS^Reload the band limits table
895 Reload the /spider/data/bands.pl file if you have changed it manually whilst
896 the cluster is running.
898 === 9^LOAD/BADMSG^Reload the bad msg table
899 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
900 the cluster is running. This table contains a number of perl regular
901 expressions which are searched for in the fields targetted of each message.
902 If any of them match then that message is immediately deleted on receipt.
904 === 9^LOAD/BADWORDS^Reload the bad words table
905 Reload the /spider/data/badwords file if you have changed it manually whilst
906 the cluster is running. This file contains a list of words which, if found
907 on certain text portions of PC protocol, will cause those protocol frames
908 to be rejected. It will all put out a message if any of these words are
909 used on the announce, dx and talk commands. The words can be one or
910 more on a line, lines starting with '#' are ignored.
912 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
913 Normally, if you change a command file in the cmd or local_cmd tree it
914 will automatially be picked up by the cluster program. Sometimes it
915 can get confused if you are doing a lot of moving commands about or
916 delete a command in the local_cmd tree and want to use the normal one
917 again. Execute this command to reset everything back to the state it
918 was just after a cluster restart. To see what is in the command cache
921 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
922 Reload the /spider/msg/forward.pl file if you have changed it
923 manually whilst the cluster is running.
925 === 5^LOAD/KEPS^Load new keps data
926 === 5^LOAD/KEPS [nn]^Load new keps data from message
927 If there is no message number then reload the current Keps data from
928 the Keps.pm data file. You create this file by running
930 /spider/perl/convkeps.pl <filename>
932 on a file containing NASA 2 line keps as a message issued by AMSAT.
934 If there is a message number, then it will take the message, run
935 convkeps.pl on it and then load the data, all in one step.
937 These messages are sent to ALL by GB7DJK (and others) from time to time.
939 === 9^LOAD/MESSAGES^Reload the system messages file
940 If you change the /spider/perl/Messages file (usually whilst
941 fiddling/writing new commands) you can have them take effect during a
942 cluster session by executing this command. You need to do this if get
945 unknown message 'xxxx' in lang 'en'
947 === 9^LOAD/PREFIXES^Reload the prefix table
948 Reload the /spider/data/prefix_data.pl file if you have changed it
949 manually whilst the cluster is running.
951 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
952 MERGE allows you to bring your spot and wwv database up to date. By default
953 it will request the last 10 spots and 5 WWVs from the node you select. The
954 node must be connected locally.
956 You can request any number of spots or wwv and although they will be appended
957 to your databases they will not duplicate any that have recently been added
958 (the last 2 days for spots and last month for WWV data).
960 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
961 Alter message parameters like To, From, Subject, whether private or bulletin
962 or return receipt (RR) is required or whether to keep this message from timing
965 MSG TO <msgno> <call> - change TO callsign to <call>
966 MSG FRom <msgno> <call> - change FROM callsign to <call>
967 MSG PRrivate <msgno> - set private flag
968 MSG NOPRrivate <msgno> - unset private flag
969 MSG RR <msgno> - set RR flag
970 MSG NORR <msgno> - unset RR flag
971 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
972 MSG NOKEep <msgno> - unset the keep flag
973 MSG SUbject <msgno> <new> - change the subject to <new>
974 MSG WAittime <msgno> - remove any waitting time for this message
975 MSG NOREad <msgno> - mark message as unread
976 MSG REad <msgno> - mark message as read
977 MSG QUeue - queue any outstanding bulletins
978 MSG QUeue 1 - queue any outstanding private messages
980 You can look at the status of a message by using:-
984 This will display more information on the message than DIR does.
986 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
987 Send some arbitrary text to a locally connected callsign. No
988 processing is done on the text. This command allows you to send PC
989 Protocol to unstick things if problems arise (messages get stuck
992 pc gb7djk PC33^GB7TLH^GB7DJK^400^
994 pc G1TLH Try doing that properly!!!
996 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
997 You can get rid of any message to or originating from your callsign using
998 this command. You can remove more than one message at a time.
1000 === 5^KILL <from>-<to>^Remove a range of messages from the system
1001 === 5^KILL FROM <call>^Remove all messages from a callsign
1002 === 5^KILL TO <call>^Remove all messages to a callsign
1003 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
1004 Remove this message from the entire cluster system as well as your node.
1007 As a sysop you can kill any message on the system.
1009 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
1010 Send any text you like to the callsign requested. This is used mainly to send
1011 PC protocol to connected nodes either for testing or to unstick things.
1013 You can also use in the same way as a talk command to a connected user but
1014 without any processing, added of "from <blah> to <blah" or whatever.
1016 === 1^PING <node call>^Check the link quality between nodes
1017 This command allows you to send a frame to another cluster node on
1018 the network and get a return frame. The time it takes to do this
1019 is a good indication of the quality of the link. The actual time
1020 it takes is output to the console in seconds.
1021 Any visible cluster node can be PINGed.
1023 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
1024 This command allows you to send nearly any command to another DX Cluster
1025 node that is connected to the system.
1027 Whether you get any output is dependant on a) whether the other system knows
1028 that the node callsign of this cluster is in fact a node b) whether the
1029 other system is allowing RCMDs from this node and c) whether you have
1030 permission to send this command at all.
1032 === 0^READ^Read the next unread personal message addressed to you
1033 === 0^READ <msgno>^Read the specified message
1034 You can read any messages that are sent as 'non-personal' and also any
1035 message either sent by or sent to your callsign.
1038 As a sysop you may read any message on the system
1040 === 0^REJECT^Set a filter to reject something
1041 Create a filter to reject something
1043 There are 2 types of filter, accept and reject. See HELP FILTERING for more
1046 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
1047 Create an 'reject this announce' line for a filter.
1049 A reject filter line means that if the announce matches this filter it is
1050 passed onto the user. See HELP FILTERING for more info. Please read this
1051 to understand how filters work - it will save a lot of grief later on.
1053 You can use any of the following things in this line:-
1055 info <string> eg: iota or qsl
1056 by <prefixes> eg: G,M,2
1058 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1059 origin_itu <prefixes or numbers> or: G,GM,GW
1060 origin_zone <prefixes or numbers>
1061 origin_state <states> eg: VA,NH,RI,ME
1062 by_dxcc <prefixes or numbers>
1063 by_itu <prefixes or numbers>
1064 by_zone <prefixes or numbers>
1065 by_state <states> eg: VA,NH,RI,ME
1067 wx 1 filter WX announces
1068 dest <prefixes> eg: 6MUK,WDX (distros)
1072 rej/ann by_zone 14,15,16 and not by G,M,2
1074 You can use the tag 'all' to reject everything eg:
1078 but this probably for advanced users...
1080 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
1081 This version allows a sysop to set a filter for a callsign as well as the
1082 default for nodes and users eg:-
1085 reject/ann input node_default by G,M,2
1086 reject/ann user_default by G,M,2
1088 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
1089 Create a 'reject this spot' line for a filter.
1091 A reject filter line means that if the spot matches this filter it is
1092 dumped (not passed on). See HELP FILTERING for more info. Please read this
1093 to understand how filters work - it will save a lot of grief later on.
1095 You can use any of the following things in this line:-
1097 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1098 on <range> same as 'freq'
1099 call <prefixes> eg: G,PA,HB9
1100 info <string> eg: iota or qsl
1102 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1103 call_itu <prefixes or numbers> or: G,GM,GW
1104 call_zone <prefixes or numbers>
1105 call_state <states> eg: VA,NH,RI,ME
1106 by_dxcc <prefixes or numbers>
1107 by_itu <prefixes or numbers>
1108 by_zone <prefixes or numbers>
1109 by_state <states> eg: VA,NH,RI,ME
1113 'call' means the callsign that has spotted 'by' whoever.
1115 For frequencies, you can use any of the band names defined in
1116 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1117 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1118 this is more efficient than saying simply: on HF (but don't get
1119 too hung up about that)
1124 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1126 You can use the tag 'all' to reject everything eg:
1130 but this probably for advanced users...
1132 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
1133 Create an 'reject this routing PC Protocol' line for a filter.
1135 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1136 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1137 read this to understand how filters work - it will save a lot of grief later on.
1139 You can use any of the following things in this line:-
1141 call <prefixes> the callsign of the thingy
1142 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1143 call_itu <prefixes or numbers> or: G,GM,GW
1144 call_zone <prefixes or numbers>
1145 call_state <states> eg: VA,NH,RI,ME
1146 origin <prefixes> really the interface it came in on
1147 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1148 origin_itu <prefixes or numbers> or: G,GM,GW
1149 origin_zone <prefixes or numbers>
1150 origin_state <states> eg: VA,NH,RI,ME
1154 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1156 You can use the tag 'all' to reject everything eg:
1158 rej/route all (equiv to [very] restricted mode)
1160 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
1162 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
1163 This version allows a sysop to set a filter for a callsign as well as the
1164 default for nodes and users eg:-
1166 reject/spot db0sue-7 1 by_zone 14,15,16
1167 reject/spot node_default all
1168 set/hops node_default 10
1170 reject/spot user_default by G,M,2
1172 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
1173 It is unlikely that you will want to do this, but if you do then you can
1174 filter on the following fields:-
1176 by <prefixes> eg: G,M,2
1178 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1179 origin_itu <prefixes or numbers> or: G,GM,GW
1180 origin_zone <prefixes or numbers>
1181 by_dxcc <prefixes or numbers>
1182 by_itu <prefixes or numbers>
1183 by_zone <prefixes or numbers>
1186 There are no examples because WCY Broadcasts only come from one place and
1187 you either want them or not (see UNSET/WCY if you don't want them).
1189 This command is really provided for future use.
1191 See HELP FILTER for information.
1193 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
1194 This version allows a sysop to set a filter for a callsign as well as the
1195 default for nodes and users eg:-
1197 reject/wcy gb7djk all
1199 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
1200 It is unlikely that you will want to do this, but if you do then you can
1201 filter on the following fields:-
1203 by <prefixes> eg: G,M,2
1205 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1206 origin_itu <prefixes or numbers> or: G,GM,GW
1207 origin_zone <prefixes or numbers>
1208 by_dxcc <prefixes or numbers>
1209 by_itu <prefixes or numbers>
1210 by_zone <prefixes or numbers>
1215 reject/wwv by_zone 14,15,16
1217 is probably the only useful thing to do (which will only show WWV broadcasts
1218 by stations in the US).
1220 See HELP FILTER for information.
1222 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
1223 This version allows a sysop to set a filter for a callsign as well as the
1224 default for nodes and users eg:-
1226 reject/wwv db0sue-7 1 by_zone 4
1227 reject/wwv node_default all
1229 reject/wwv user_default by W
1231 === 0^REPLY^Reply (privately) to the last message that you have read
1232 === 0^REPLY <msgno>^Reply (privately) to the specified message
1233 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1234 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1235 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1236 You can reply to a message and the subject will automatically have
1237 "Re:" inserted in front of it, if it isn't already present.
1239 You can also use all the extra qualifiers such as RR, PRIVATE,
1240 NOPRIVATE, B that you can use with the SEND command (see SEND
1241 for further details)
1243 === 9^SAVE [-d -t -a] <filename> "<cmd>" [...]^Save command output to a file
1244 This sysop only cammand allows you to save the output of one or more
1245 commands to a file. For example:-
1247 save /spider/packclus/dxstats show/dxstat
1249 will save the output of the normal command "show/dxstat" to the file
1250 "dxstats" in the files area.
1252 You can have some extra flags to the save which will either
1253 date stamp or time stamp or both the filename so:-
1255 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
1256 save -t /tmp/a <cmd> creates /tmp/a_2301Z
1257 save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
1259 The -a flag means append to the file instead of overwriting it.
1261 You can have more than one command on the line, to do this you MUST
1262 enclose each command in double quotes (") eg:-
1264 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
1268 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
1270 You can only write into places that the cluster has permission for (which
1271 is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
1272 need to create any directories you want to put stuff in beforehand as well.
1274 It is likely that you will want to run these commands in a crontab type
1275 situation. You would do that something like:-
1277 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
1279 Note that you still enclose each command with (") characters but you must
1280 enclose the entire save command in (') characters.
1282 Now in fact, this can be varied if you know what you are doing. See the
1283 admin manual for more details.
1285 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1286 === 0^SEND RR <call>^Send a message and ask for a read receipt
1287 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1288 === 0^SEND PRIVATE <call>^Send a personal message
1289 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1290 All the SEND commands will create a message which will be sent either to
1291 an individual callsign or to one of the 'bulletin' addresses.
1293 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1294 it will mark the message as personal and send it to the cluster node that
1295 that callsign is connected to. If the <call> you have specified is in fact
1296 a known bulletin category on your node (eg: ALL) then the message should
1297 automatically become a bulletin.
1299 You can have more than one callsign in all of the SEND commands.
1301 You can have multiple qualifiers so that you can have for example:-
1303 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1305 which should send a copy of message 123 to G1TLH and G0RDI and you will
1306 receive a read receipt when they have read the message.
1308 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1309 SP is an alias for SEND PRIVATE
1311 The system will ask you for a subject. Conventionally this should be
1312 no longer than 29 characters for compatibility. Most modern cluster
1313 software should accept more.
1315 You will now be prompted to start entering your text.
1317 You finish the message by entering '/EX' on a new line. For instance:
1324 If you have started a message and you don't want to keep it then you
1325 can abandon the message with '/ABORT' on a new line, like:-
1329 oh I just can't be bothered with this
1332 If you abort the message it will NOT be sent.
1334 When you are entering the text of your message, most normal output (such
1335 as DX announcements and so on are suppressed and stored for latter display
1336 (upto 20 such lines are stored, as new ones come along, so the oldest
1339 Also, you can enter normal commands commands (and get the output
1340 immediately) whilst in the middle of a message. You do this by typing
1341 the command preceeded by a '/' character on a new line, so:-
1343 /dx g1tlh 144010 strong signal
1345 Will issue a dx annoucement to the rest of the cluster.
1347 Also, you can add the output of a command to your message by preceeding
1348 the command with '//', thus :-
1352 This will show YOU the output from SH/VHFTABLE and also store it in the
1355 You can carry on with the message until you are ready to send it.
1356 === 0^SET/ADDRESS <your address>^Record your postal address
1358 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1359 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1361 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1362 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1363 The announce system on legacy cluster nodes is used as a talk
1364 substitute because the network is so poorly connected. If you:
1368 you will suppress several of these announces, you may miss the odd
1369 useful one as well, but you would probably miss them anyway in the
1370 welter of useless ones.
1374 allows you to see them again. This is the default.
1376 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1378 === 8^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1379 === 8^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1380 Setting a word as 'baddx' will prevent spots with that word in the
1381 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1382 further. They will not be displayed and they will not be sent onto
1385 The word must be written in full, no wild cards are allowed eg:-
1387 set/baddx FORSALE VIDEO FR0G
1389 To allow a word again, use the following command ...
1393 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1394 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1395 Setting a callsign as a 'badnode' will prevent spots from that node
1396 going any further. They will not be displayed and they will not be
1397 sent onto other nodes.
1399 The call must be a full eg:-
1403 will stop anything from K1TTT. If you want SSIDs as well then you must
1404 enter them specifically.
1408 will allow spots from him again.
1410 Use with extreme care. This command may well be superceeded by FILTERing.
1412 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1413 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1414 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1415 going any further. They will not be displayed and they will not be
1416 sent onto other nodes.
1418 The call must be written in full, no wild cards are allowed eg:-
1420 set/badspotter VE2STN
1422 will stop anything from VE2STN. This command will automatically
1423 stop spots from this user, regardless of whether or which SSID
1424 he uses. DO NOT USE SSIDs in the callsign, just use the callsign
1427 unset/badspotter VE2STN
1429 will allow spots from him again.
1431 Use with extreme care. This command may well be superceded by FILTERing.
1433 This command will also stop TALK and ANNOUNCE/FULL from any user marked
1436 === 8^SET/BADWORD <word>..^Stop things with this word being propagated
1437 === 8^UNSET/BADWORD <word>..^Propagate things with this word again
1438 Setting a word as a 'badword' will prevent things like spots,
1439 announces or talks with this word in the the text part from going any
1440 further. They will not be displayed and they will not be sent onto
1443 The word must be written in full, no wild cards are allowed eg:-
1445 set/badword annihilate annihilated annihilation
1447 will stop anything with these words in the text.
1449 unset/badword annihilated
1451 will allow text with this word again.
1453 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1454 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1456 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1458 === 0^SET/BUDDY <call> [<call>..]^Add this call to my buddy list
1459 === 0^UNSET/BUDDY <call> [<call>..]^Remove this call from my buddy list
1460 A notification message
1461 is sent to you automatically if anybody on your buddy list logs in or
1462 out of any node in this cluster.
1464 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1466 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1467 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1468 You can choose to log several different levels. The levels are
1476 You can show what levels you are logging with SHOW/DEBUG
1478 === 0^SET/DX^Allow DX messages to come out on your terminal
1479 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1481 === 0^SET/DXCQ^Show CQ Zones on the end of DX announcements
1482 === 0^UNSET/DXCQ^Stop CQ Zones on the end of DX announcements
1483 Display both the Spotter's and the Spotted's CQ Zone on the end
1484 of a DX announcement (there is just enough room). Some user programs
1485 cannot cope with this. The Spotter's CQ is on the RHS of the
1486 time, the Spotted's CQ is on the LHS.
1488 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
1490 Do a STAT/USER to see which flags you have set if you are confused.
1492 === 0^SET/DXITU^Show ITU Zones on the end of DX announcements
1493 === 0^UNSET/DXITU^Stop ITU Zones on the end of DX announcements
1494 Display both the Spotter's and the Spotted's ITU Zone on the end
1495 of a DX announcement (there is just enough room). Some user programs
1496 cannot cope with this. The Spotter's ITU is on the RHS of the
1497 time, the Spotted's ITU is on the LHS.
1499 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
1501 Do a STAT/USER to see which flags you have set if you are confused.
1503 === 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
1504 === 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
1505 A standard feature which is enabled in version 1.43 and above is
1506 that if the spotter's grid square is known it is output on the end
1507 of a DX announcement (there is just enough room). Some user programs
1508 cannot cope with this. You can use this command to reset (or set)
1511 Conflicts with: SET/DXCQ, SET/DXITU
1513 Do a STAT/USER to see which flags you have set if you are confused.
1515 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1517 === 0^SET/ECHO^Make the cluster echo your input
1518 === 0^UNSET/ECHO^Stop the cluster echoing your input
1519 If you are connected via a telnet session, different implimentations
1520 of telnet handle echo differently depending on whether you are
1521 connected via port 23 or some other port. You can use this command
1522 to change the setting appropriately.
1524 The setting is stored in your user profile.
1526 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1528 === 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
1529 === 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
1530 If any personal messages come in for your callsign then you can use
1531 these commands to control whether they are forwarded onto your email
1532 address. To enable the forwarding do something like:-
1534 SET/EMAIL mike.tubby@somewhere.com
1536 You can have more than one email address (each one separated by a space).
1537 Emails are forwarded to all the email addresses you specify.
1539 You can disable forwarding by:-
1543 === 0^SET/HERE^Tell the system you are present at your terminal
1544 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1546 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1547 Tell the cluster system where you normally connect to. Any Messages sent
1548 to you will normally find their way there should you not be connected.
1552 === 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
1553 === 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
1554 Set the hop count for a particular type of broadcast for a node.
1556 This command allows you to set up special hop counts for a node
1557 for currently: announce, spots, wwv and wcy broadcasts.
1560 set/hops gb7djk ann 10
1561 set/hops gb7mbc spots 20
1563 Set SHOW/HOPS for information on what is already set. This command
1564 creates a filter and works in conjunction with the filter system.
1566 You can unset the hops with command UNSET/HOPS. For example:-
1568 unset/hops gb7djk ann
1569 unset/hops gb7mbc spots
1572 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1573 Connect a node to your system in such a way that you are a full protocol
1574 member of its network and can see all spots on it, but nothing either leaks
1575 out from it nor goes back into from the rest of the nodes connected to you.
1577 You can potentially connect several nodes in this way.
1579 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1580 Remove isolation from a node - SET/ISOLATE
1582 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1583 You can select the language that you want the cluster to use. Currently
1584 the languages available are en (English), de (German), es (Spanish),
1585 Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
1587 === 5^SET/LOCAL_NODE^Add node to the local_node group
1588 === 5^UNSET/LOCAL_NODE^Remove node from the local_node group
1589 The 'local_node' group is a group of nodes that you want a user
1590 to perceive as effectively one big node. At the moment, this extends
1591 only to announcing whenever a user is logging in or out of one of
1592 the nodes in the group (if those users have SET/LOGININFO).
1594 The local node group is as setup on this node. If you want the other
1595 nodes to also include this node and all the other nodes specified, then
1596 you must get those nodes to also run this command (or rcmd them to do
1599 In principle, therefore, each node determines its own local node group
1600 and these can overlap with other nodes' views.
1602 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1603 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1604 In order to get accurate headings and such like you must tell the system
1605 what your latitude and longitude is. If you have not yet done a SET/QRA
1606 then this command will set your QRA locator for you. For example:-
1607 SET/LOCATION 52 22 N 0 57 E
1609 === 0^SET/LOGININFO^Inform when a station logs in/out locally
1610 === 0^UNSET/LOGININFO^No longer inform when a station logs in/out locally
1612 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1613 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1615 === 0^SET/NAME <your name>^Set your name
1616 Tell the system what your name is eg:-
1619 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1620 Tell the system that the call(s) are to be treated as AK1A cluster and
1621 fed PC Protocol rather normal user commands.
1623 === 8^SET/OBSCOUNT <count> <call>^Set the 'pump-up' obscelence PING counter
1624 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1625 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1626 counter which is decremented on every outgoing ping and then reset to
1627 the 'obscount' value on every incoming ping. The default value of this
1630 What this means is that a neighbouring node will be pinged twice at
1631 (default) 300 second intervals and if no reply has been heard just before
1632 what would be the third attempt, that node is disconnected.
1634 If a ping is heard then the obscount is reset to the full value. Using
1635 default values, if a node has not responded to a ping within 15 minutes,
1638 You can set this parameter between 1 and 9.
1640 It is STRONGLY recommended that you don't change the default.
1642 === 0^SET/PAGE <lines per page>^Set the lines per page
1643 Tell the system how many lines you wish on a page when the number of line
1644 of output from a command is more than this. The default is 20. Setting it
1645 explicitly to 0 will disable paging.
1649 The setting is stored in your user profile.
1651 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1652 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1653 in order to determine the rolling quality of the link and, in future, to
1654 affect routing decisions. The default interval is 300 secs or 5 minutes.
1656 You can use this command to set a different interval. Please don't.
1658 But if you do the value you enter is treated as minutes up 30 and seconds
1659 for numbers greater than that.
1661 This is used also to help determine when a link is down at the far end
1662 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1663 for more information.
1665 If you must change it (and it may be useful for internet connected nodes
1666 on dynamic IP addresses that go away after a set time of usage) the time
1667 can be specified as:-
1669 5 which if less than 30 is converted to minutes otherwise is
1670 taken as the no of seconds between pings.
1675 Please be aware that this causes traffic to occur on the link, setting
1676 this value too low may annoy your neighbours beyond the point of
1679 You can switch this off by setting it to 0.
1681 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1682 Set the privilege level on a callsign. The privilege levels that pertain
1683 to commands are as default:-
1685 1 - allow remote nodes normal user RCMDs
1686 5 - various privileged commands (including shutdown, but not disc-
1687 connect), the normal level for another node.
1688 8 - more privileged commands (including disconnect)
1689 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1691 If you are a sysop and you come in as a normal user on a remote connection
1692 your privilege will automatically be set to 0.
1694 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1695 You can use this command to 'protect' this session from unauthorised
1696 use. If you want to get your normal privilege back you will need to
1697 either logout and login again (if you are on a console) or use the
1700 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1701 The password for a user can only be set by a full sysop. The string
1702 can contain any characters.
1704 The way this field is used depends on context. If it is being used in
1705 the SYSOP command context then you are offered 5 random numbers and you
1706 have to supply the corresponding letters. This is now mainly for ax25
1709 If it is being used on incoming telnet connections then, if a password
1712 set/var $main::passwdreq = 1
1714 command is executed in the startup script, then a password prompt is
1715 given after the normal 'login: ' prompt.
1717 === 0^SET/PASSWORD^Set your own password
1718 This command only works for a 'telnet' user (currently). It will
1719 only work if you have a password already set. This initial password
1720 can only be set by the sysop.
1722 When you execute this command it will ask you for your old password,
1723 then ask you to type in your new password twice (to make sure you
1724 get it right). You may or may not see the data echoed on the screen
1725 as you type, depending on the type of telnet client you have.
1727 === 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
1728 This command allows the sysop to completely delete and remove a
1729 password for a user.
1731 === 0^SET/PROMPT <string>^Set your prompt to <string>
1732 === 0^UNSET/PROMPT^Set your prompt back to default
1733 This command will set your user prompt to the string that you
1734 say. The point of this command to enable a user to interface to programs
1735 that are looking for a specific prompt (or else you just want a different
1740 There are some substitutions that can be added to the prompt:
1742 %C - callsign [which will have ( and ) around it if not here]
1745 %M - cluster 'mycall'
1747 The standard prompt is defined as:
1749 SET/PROMPT %C de %M %D %T dxspider >
1751 UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to
1754 === 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
1755 === 0^SET/QRA <locator>^Set your QRA Grid locator
1756 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1757 done a SET/LOCATION then your latitude and longitude will be set roughly
1758 correctly (assuming your locator is correct ;-). For example:-
1761 === 0^SET/QTH <your qth>^Set your QTH
1762 Tell the system where you are. For example:-
1763 SET/QTH East Dereham, Norfolk
1765 === 9^SET/REGISTER <call> ...^Mark a user as registered
1766 === 9^UNSET/REGISTER <call> ...^Mark a user as not registered
1767 Registration is a concept that you can switch on by executing the
1769 set/var $main::regreq = 1
1771 command (usually in your startup file)
1773 If a user is NOT registered then, firstly, instead of the normal
1774 motd file (/spider/data/motd) being sent to the user at startup, the
1775 user is sent the motd_nor file instead. Secondly, the non registered
1776 user only has READ-ONLY access to the node. The non-registered user
1777 cannot use DX, ANN etc.
1779 The only exception to this is that a non-registered user can TALK or
1780 SEND messages to the sysop.
1782 === 6^SET/STARTUP <call>^Create a user startup script
1783 === 0^SET/STARTUP^Create your own startup script
1784 Create a startup script of DXSpider commands which will be executed
1785 everytime that you login into this node. You can only input the whole
1786 script afresh, it is not possible to 'edit' it. Inputting a new script is
1787 just like typing in a message using SEND. To finish inputting type: /EX
1788 on a newline, to abandon the script type: /ABORT.
1790 You may find the (curiously named) command BLANK useful to break
1791 up the output. If you simply want a blank line, it is easier to
1792 input one or more spaces and press the <return> key.
1794 See UNSET/STARTUP to remove a script.
1796 === 6^UNSET/STARTUP <call>^Remove a user startup script
1797 === 0^UNSET/STARTUP^Remove your own startup script
1798 You can remove your startup script with UNSET/STARTUP.
1800 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1801 Tell the system that the call(s) are to be treated as DXSpider node and
1802 fed new style DX Protocol rather normal user commands.
1804 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1805 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1807 === 9^SET/USDB <call> <state> <city>^add/update a US DB callsign
1808 This command allows you to add or alter a callsign in the US state
1809 database. Use with extreme caution. Anything you do here will be
1810 overwritten by any weekly updates that affect this callsign
1812 set/usdb g1tlh nh downtown rindge
1814 see also DELETE/USDB
1816 === 0^SET/USSTATE^Allow US State info on the end of DX announcements
1817 === 0^UNSET/USSTATE^Stop US State info on the end of DX announcements
1818 If the spotter's or spotted's US State is known it is output on the
1819 end of a DX announcement (there is just enough room).
1821 A spotter's state will appear on the RHS of the time (like
1822 SET/DXGRID) and the spotted's State will appear on the LHS of the
1823 time field. Any information found will override any locator
1824 information from SET/DXGRID.
1826 Some user programs cannot cope with this. You can use this command
1827 to reset (or set) this feature.
1829 Conflicts with: SET/DXCQ, SET/DXITU
1831 Do a STAT/USER to see which flags you have set if you are confused.
1833 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1834 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1836 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1837 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1839 === 0^SET/WX^Allow WX messages to come out on your terminal
1840 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1842 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1843 Display all the bad dx callsigns in the system, see SET/BADDX
1844 for more information.
1846 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1847 Display all the bad node callsigns in the system, see SET/BADNODE
1848 for more information.
1850 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1851 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1852 for more information.
1854 === 1^SHOW/BADWORD^Show all the bad words in the system
1855 Display all the bad words in the system, see SET/BADWORD
1856 for more information.
1858 === 0^SHOW/BUDDY^Show your list of buddies
1859 See SET/BUDDY for more information about buddies.
1861 === 0^SHOW/CHAT [<group>] [<lines>]^Show any chat or conferencing
1862 This command allows you to see any chat or conferencing that has
1863 occurred whilst you were away. SHOW/CHAT on its own will show data for
1864 all groups. If you use a group name then it will show only chat for
1867 === 9^SHOW/CMD_CACHE [pattern]^Show the real source path of commands
1868 It is possible in DXSpider to define local versions of commands.
1869 Sometimes one forgets that one has these. This command will show you
1870 the source path where the node is getting each one of its commands.
1872 If you find a local command that you don't want then then simply
1873 delete it, run LOAD/CMD_CACHE to clear out the command cache and
1874 try again. You will now be using the standard version.
1876 If you are looking for information on a specific command then
1877 just add a string, eg:
1884 set/dxgrid /spider/cmd/set/dxgrid.pl
1885 sh/dx /spider/cmd/show/dx.pl
1887 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1888 This command allows you to see all the users that can be seen
1889 and the nodes to which they are connected.
1891 This command is normally abbreviated to: sh/c
1893 Normally, the list returned will be just for the nodes from your
1894 country (because the list otherwise will be very long).
1898 will produce a complete list of all nodes.
1900 BE WARNED: the list that is returned can be VERY long
1902 It is possible to supply a node or part of a prefix and you will get
1903 a list of the users for that node or list of nodes starting with
1910 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1911 Show all the nodes connected to this node.
1913 === 1^SHOW/CONNECT^Show all the active connections
1914 This command shows information on all the active connections known to
1915 the node. This command gives slightly more information than WHO.
1917 === 0^SHOW/CONTEST <year and month>^Show all the contests for a month
1918 Show all known contests which are maintained at http://www.sk3bg.se/contest/
1919 for a particular month or year. The format is reasonably flexible.
1925 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1926 This is very nearly the same as SHOW/TIME, the only difference the format
1927 of the date string if no arguments are given.
1929 If no prefixes or callsigns are given then this command returns the local
1930 time and UTC as the computer has it right now. If you give some prefixes
1931 then it will show UTC and UTC + the local offset (not including DST) at
1932 the prefixes or callsigns that you specify.
1934 === 0^SHOW/DB0SDX <callsign>^Show QSL infomation from DB0SDX database
1935 This command queries the DB0SDX QSL server on the internet
1936 and returns any information available for that callsign. This service
1937 is provided for users of this software by http://www.qslinfo.de.
1939 See also SHOW/QRZ, SHOW/WM7D.
1941 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1943 === 0^SHOW/DX^Interrogate the spot database
1944 If you just type SHOW/DX you will get the last so many spots
1945 (sysop configurable, but usually 10).
1947 In addition you can add any number of these commands in very nearly
1948 any order to the basic SHOW/DX command, they are:-
1950 on <band> - eg 160m 20m 2m 23cm 6mm
1951 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1952 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
1955 <number> - the number of spots you want
1956 <from>-<to> - <from> spot no <to> spot no in the selected list
1959 <prefix> - for a spotted callsign beginning with <prefix>
1960 *<suffix> - for a spotted callsign ending in <suffix>
1961 *<string>* - for a spotted callsign containing <string>
1963 day <number> - starting <number> days ago
1964 day <from>-<to> - <from> days <to> days ago
1967 info <text> - any spots containing <text> in the info or remarks
1969 by <call> - any spots spotted by <call> (spotter <call> is the
1972 qsl - this automatically looks for any qsl info on the call
1973 held in the spot database.
1975 iota [<iota>] - If the iota island number is missing it will look for
1976 the string iota and anything which looks like an iota
1977 island number. If you specify then it will look for
1980 qra [<locator>] - this will look for the specific locator if you specify
1981 one or else anything that looks like a locator.
1983 dxcc - treat the prefix as a 'country' and look for spots
1984 from that country regardless of actual prefix.
1987 You can also use this with the 'by' keyword so
1990 real or rt - Format the output the same as for real time spots. The
1991 formats are deliberately different (so you can tell
1992 one sort from the other). This is useful for some
1993 logging programs that can't cope with normal sh/dx
1994 output. An alias of SHOW/FDX is available.
1996 filter - Filter the spots, before output, with the user's
1997 spot filter. An alias of SHOW/MYDX is available.
1999 zone <zones> - look for spots in the cq zone (or zones) specified.
2000 zones are numbers separated by commas.
2002 by_zone <zones> - look for spots spotted by people in the cq zone
2005 itu <itus> - look for spots in the itu zone (or zones) specified
2006 itu zones are numbers separated by commas.
2008 by_itu <itus> - look for spots spotted by people in the itu zone
2011 state <list> - look for spots in the US state (or states) specified
2012 The list is two letter state codes separated by commas.
2014 by_state <list> - look for spots spotted by people in the US state
2020 SH/DX on 20m info iota
2021 SH/DX 9a on vhf day 30
2027 SH/DX dxcc oq2 by w dxcc
2031 SH/DX by_state in,oh
2033 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
2034 This command takes the <prefix> (which can be a full or partial
2035 callsign if desired), looks up which internal country number it is
2036 and then displays all the spots as per SH/DX for that country.
2038 This is now an alias for 'SHOW/DX DXCC'
2040 The options for SHOW/DX also apply to this command.
2044 SH/DXCC W on 20m iota
2046 This can be done with the SHOW/DX command like this:-
2049 SH/DX dxcc w on 20m iota
2051 This is an alias for: SH/DX dxcc
2053 === 0^SHOW/FDX^Show the DX data in realtime format.
2054 Normally SHOW/DX outputs spot data in a different format to the
2055 realtime data. This is a deliberate policy (so you can tell the
2056 difference between the two). Some logging programs cannot handle
2057 this so SHOW/FDX outputs historical data in real time format.
2059 This is an alias for: SHOW/DX real
2061 === 0^SHOW/DXSTATS [days] [date]^Show the DX Statistics
2062 Show the total DX spots for the last <days> no of days (default is 31),
2063 starting from a <date> (default: today).
2065 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
2066 SHOW/FILES on its own will show you a list of the various fileareas
2067 available on the system. To see the contents of a particular file
2070 where <filearea> is the name of the filearea you want to see the
2073 You can also use shell globbing characters like '*' and '?' in a
2074 string to see a selection of files in a filearea eg:-
2075 SH/FILES bulletins arld*
2077 See also TYPE - to see the contents of a file.
2079 === 0^SHOW/FILTER^Show the contents of all the filters you have set
2080 Show the contents of all the filters that are set. This command displays
2081 all the filters set - for all the various categories.
2083 === 0^SHOW/GRAYLINE [ndays] [<prefix>|<callsign>]^Show Civil dawn/dusk times
2084 This command is very similar to SHOW/SUN except that it shows the
2085 start and end of "Official" or "Civil" Dawn and Dusk. This is defined
2086 as when the Sun is 6 degrees below the horizon.
2088 If you don't specify any prefixes or callsigns, it will show the
2089 times for your QTH (assuming you have set it with either SET/LOCATION
2090 or SET/QRA), together with the current azimuth and elevation.
2092 If all else fails it will show the civil dawn and dusk times for
2093 the node that you are connected to.
2098 SH/GRAYLINE G1TLH W5UN
2100 You can also use this command to see into the past or the future, so
2101 if you want to see yesterday's times then do:-
2105 or in three days time:-
2109 Upto 366 days can be checked both in the past and in the future.
2111 Please note that the times are given as the UT times of the requested
2114 === 0^SHOW/HFSTATS [days] [date]^Show the HF DX Statistics
2115 Show the HF DX spots breakdown by band for the last <days> no of days
2116 (default is 31), starting from a <date> (default: today).
2118 === 0^SHOW/HFTABLE [days] [date] [prefix ...]^Show the HF DX Spotter Table
2119 Show the HF DX Spotter table for the list of prefixes for the last
2120 <days> no of days (default is 31), starting from a <date> (default: today).
2122 If there are no prefixes then it will show the table for your country.
2124 Remember that some countries have more than one "DXCC country" in them
2125 (eg G :-), to show them (assuming you are not in G already which is
2126 specially treated in the code) you must list all the relevant prefixes
2128 sh/hftable g gm gd gi gj gw gu
2130 Note that the prefixes are converted into country codes so you don't have
2131 to list all possible prefixes for each country.
2133 If you want more or less days than the default simply include the
2134 number you require:-
2138 If you want to start at a different day, simply add the date in some
2141 sh/hftable 2 25nov02
2142 sh/hftable 2 25-nov-02
2144 sh/hftable 2 25/11/02
2146 This will show the stats for your DXCC for that CQWW contest weekend.
2148 You can specify either prefixes or full callsigns (so you can see how you
2149 did against all your mates). You can also say 'all' which will then print
2150 the worldwide statistics.
2154 === 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
2155 This command shows the hop counts set up for a node. You can specify
2156 which category you want to see. If you leave the category out then
2157 all the categories will be listed.
2159 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
2161 === 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
2163 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
2164 This command outputs a short section of the system log. On its own
2165 it will output a general logfile. With the optional callsign it will
2166 show output from the log associated with that callsign.
2168 === 0^SHOW/MOON [ndays] [<prefix>|<callsign>]^Show Moon rise and set times
2169 Show the Moon rise and set times for a (list of) prefixes or callsigns,
2170 together with the azimuth and elevation of the sun currently at those
2173 If you don't specify any prefixes or callsigns, it will show the times for
2174 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2175 together with the current azimuth and elevation.
2177 In addition, it will show the illuminated fraction of the moons disk.
2179 If all else fails it will show the Moonrise and set times for the node
2180 that you are connected to.
2187 You can also use this command to see into the past or the future, so
2188 if you want to see yesterday's times then do:-
2192 or in three days time:-
2196 Upto 366 days can be checked both in the past and in the future.
2198 Please note that the rise and set times are given as the UT times of rise and
2199 set on the requested UT day.
2201 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
2202 This command allow you to estimate the likelihood of you contacting
2203 a station with the prefix you have specified. The output assumes a modest
2204 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
2206 The result predicts the most likely operating frequencies and signal
2207 levels for high frequency (shortwave) radio propagation paths on
2208 specified days of the year and hours of the day. It is most useful for
2209 paths between 250 km and 6000 km, but can be used with reduced accuracy
2210 for paths shorter or longer than this.
2212 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2213 used to predict the MUF given the predicted flux, day of the year,
2214 hour of the day and geographic coordinates of the transmitter and
2215 receiver. This routine is reasonably accurate for the purposes here,
2216 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2217 than the programs used by major shortwave broadcasting organizations,
2218 such as the Voice of America.
2220 The command will display some header information detailing its
2221 assumptions, together with the locations, latitude and longitudes and
2222 bearings. It will then show UTC (UT), local time at the other end
2223 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2224 (Zen) and the likely signal strengths. Then for each frequency for which
2225 the system thinks there is a likelihood of a circuit it prints a value.
2227 The value is currently a likely S meter reading based on the conventional
2228 6dB / S point scale. If the value has a '+' appended it means that it is
2229 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
2230 there is likely to be much fading and by an 's' that the signal is likely
2233 By default SHOW/MUF will show the next two hours worth of data. You
2234 can specify anything up to 24 hours worth of data by appending the no of
2235 hours required after the prefix. For example:-
2241 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2242 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2243 Location Lat / Long Azim
2244 East Dereham, Norfolk 52 41 N 0 57 E 47
2245 United-States-W 43 0 N 87 54 W 299
2246 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2247 18 23 11.5 -35 mS0+ mS2 S3
2248 19 0 11.2 -41 mS0+ mS2 S3
2250 indicating that you will have weak, fading circuits on top band and
2251 80m but usable signals on 40m (about S3).
2257 will get you the above display, but with the next 24 hours worth of
2263 Gives you an estimate of the long path propagation characterics. It
2264 should be noted that the figures will probably not be very useful, nor
2265 terrible accurate, but it is included for completeness.
2267 === 0^SHOW/MYDX^Show the DX data filtered with your spot filter.
2268 SHOW/DX potentially shows all the spots available in the system. Using
2269 SHOW/MYDX will, instead, filter the availble spots using any spot filter
2270 that you have set, first.
2272 This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
2273 you to customise the spots that you receive.
2275 So if you have said: ACC/SPOT on hf
2277 Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
2278 options on SH/DX can still be used.
2280 === 0^SHOW/NEWCONFIGURATION [<node>]^Show all the nodes and users visible
2281 This command allows you to see all the users that can be seen
2282 and the nodes to which they are connected.
2284 This command produces essentially the same information as
2285 SHOW/CONFIGURATION except that it shows all the duplication of
2286 any routes that might be present It also uses a different format
2287 which may not take up quite as much space if you don't have any
2290 BE WARNED: the list that is returned can be VERY long
2292 === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
2293 Show all the nodes connected to this node in the new format.
2295 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
2296 Show the type and version (if connected) of the nodes specified on the
2297 command line. If no callsigns are specified then a sorted list of all
2298 the non-user callsigns known to the system will be displayed.
2300 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
2301 This command takes the <callsign> (which can be a full or partial
2302 callsign or a prefix), looks up which internal country number
2303 it is and then displays all the relevant prefixes for that country
2304 together with the internal country no, the CQ and ITU regions.
2308 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
2309 Show the name and location where every program module was load from. This
2310 is useful for checking where you think you have loaded a .pm file from.
2312 === 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
2313 === 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
2314 This is a multipurpose command that allows you either to calculate the
2315 distance and bearing between two locators or (if only one locator is
2316 given on the command line) the distance and beraing from your station
2317 to the locator. For example:-
2322 The first example will show the distance and bearing to the locator from
2323 yourself, the second example will calculate the distance and bearing from
2324 the first locator to the second. You can use 4 or 6 character locators.
2326 It is also possible to convert a latitude and longitude to a locator by
2327 using this command with a latitude and longitude as an argument, for
2330 SH/QRA 52 41 N 0 58 E
2332 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
2333 This command queries the QRZ callbook server on the internet
2334 and returns any information available for that callsign. This service
2335 is provided for users of this software by http://www.qrz.com
2337 See also SHOW/WM7D for an alternative.
2339 === 0^SHOW/DXQSL <callsign>^Show any QSL info gathered from spots
2340 The node collects information from the comment fields in spots (things
2341 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
2343 This command allows you to interrogate that database and if the callsign
2344 is found will display the manager(s) that people have spotted. This
2345 information is NOT reliable, but it is normally reasonably accurate if
2346 it is spotted enough times.
2352 You can check the raw input spots yourself with:-
2356 This gives you more background information.
2358 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
2360 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
2361 This command allows you to see to which node the callsigns specified are
2362 connected. It is a sort of inverse sh/config.
2366 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
2367 Show the tracking data from your location to the satellite of your choice
2368 from now on for the next few hours.
2370 If you use this command without a satellite name it will display a list
2371 of all the satellites known currently to the system.
2373 If you give a name then you can obtain tracking data of all the passes
2374 that start and finish 5 degrees below the horizon. As default it will
2375 give information for the next three hours for every five minute period.
2377 You can alter the number of hours and the step size, within certain
2380 Each pass in a period is separated with a row of '-----' characters
2385 SH/SAT FENGYUN1 12 2
2387 === 6^SHOW/STARTUP <call>^View a user startup script
2388 === 0^SHOW/STARTUP^View your own startup script
2389 View the contents of a startup script created with SET/STARTUP.
2391 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
2392 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
2393 Show the information known about a callsign and whether (and where)
2394 that callsign is connected to the cluster.
2398 If no callsign is given then show the information for yourself.
2400 === 0^SHOW/SUN [ndays] [<prefix>|<callsign>]^Show sun rise and set times
2401 Show the sun rise and set times for a (list of) prefixes or callsigns,
2402 together with the azimuth and elevation of the sun currently at those
2405 If you don't specify any prefixes or callsigns, it will show the times for
2406 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2407 together with the current azimuth and elevation.
2409 If all else fails it will show the sunrise and set times for the node
2410 that you are connected to.
2415 SH/SUN G1TLH K9CW ZS
2417 You can also use this command to see into the past or the future, so
2418 if you want to see yesterday's times then do:-
2422 or in three days time:-
2426 Upto 366 days can be checked both in the past and in the future.
2428 Please note that the rise and set times are given as the UT times of rise
2429 and set on the requested UT day.
2431 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
2432 If no prefixes or callsigns are given then this command returns the local
2433 time and UTC as the computer has it right now. If you give some prefixes
2434 then it will show UTC and UTC + the local offset (not including DST) at
2435 the prefixes or callsigns that you specify.
2437 === 0^SHOW/USDB [call ..]^Show information held on the FCC Call database
2438 Show the City and State of a Callsign held on the FCC database if
2439 his is being run on this system, eg:-
2443 === 0^SHOW/VHFSTATS [days] [date]^Show the VHF DX Statistics
2444 Show the VHF DX spots breakdown by band for the last
2445 <days> no of days (default is 31), starting from a date (default: today).
2447 === 0^SHOW/VHFTABLE [days] [date] [prefix ...]^Show the VHF DX Spotter Table
2448 Show the VHF DX Spotter table for the list of prefixes for the last
2449 <days> no of days (default is 31), starting from a date (default: today).
2451 If there are no prefixes then it will show the table for your country.
2453 Remember that some countries have more than one "DXCC country" in them
2454 (eg G :-), to show them (assuming you are not in G already which is
2455 specially treated in the code) you must list all the relevant prefixes
2457 sh/vhftable g gm gd gi gj gw gu
2459 Note that the prefixes are converted into country codes so you don't have
2460 to list all possible prefixes for each country.
2462 If you want more or less days than the default simply include the
2463 number you require:-
2467 If you want to start at a different day, simply add the date in some
2470 sh/vhftable 2 25nov02
2471 sh/vhftable 2 25-nov-02
2472 sh/vhftable 2 021125
2473 sh/vhftable 2 25/11/02
2475 This will show the stats for your DXCC for that CQWW contest weekend.
2477 You can specify either prefixes or full callsigns (so you can see how you
2478 did against all your mates). You can also say 'all' which will then print
2479 the worldwide statistics.
2483 === 0^SHOW/WCY^Show last 10 WCY broadcasts
2484 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
2485 Display the most recent WCY information that has been received by the system
2487 === 0^SHOW/WM7D <callsign>^Show callbook details on a US callsigns
2488 This command queries the WM7D callbook server on the internet
2489 and returns any information available for that US callsign. This service
2490 is provided for users of this software by http://www.wm7d.net.
2494 === 0^SHOW/WWV^Show last 10 WWV broadcasts
2495 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
2496 Display the most recent WWV information that has been received by the system
2498 === 5^SHUTDOWN^Shutdown the cluster
2499 Shutdown the cluster and disconnect all the users
2501 === 9^SPOOF <call> <command>^Do a command as though you are another user
2502 This command is provided so that sysops can set a user's parameters without
2503 me having to write a special 'sysop' version for every user command. It
2504 allows you to pretend that you are doing the command as the user you specify.
2508 SPOOF G1TLH set/name Dirk
2509 SPOOF G1TLH set/qra JO02LQ
2511 === 5^STAT/DB <dbname>^Show the status of a database
2512 Show the internal status of a database descriptor.
2514 Depending on your privilege level you will see more or less information.
2515 This command is unlikely to be of much use to anyone other than a sysop.
2517 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
2518 Show the internal status of the channel object either for the channel that
2519 you are on or else for the callsign that you asked for.
2521 Only the fields that are defined (in perl term) will be displayed.
2523 === 1^STAT/MSG^Show the status of the message system
2524 === 1^STAT/MSG <msgno>^Show the status of a message
2525 This command shows the internal status of a message and includes information
2526 such as to whom it has been forwarded, its size, origin etc etc.
2528 If no message number is given then the status of the message system is
2531 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
2532 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
2534 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
2535 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
2537 === 5^STAT/USER [<callsign>]^Show the full status of a user
2538 Shows the full contents of a user record including all the secret flags
2541 Only the fields that are defined (in perl term) will be displayed.
2543 === 0^SYSOP^Regain your privileges if you login remotely
2544 The system automatically reduces your privilege level to that of a
2545 normal user if you login in remotely. This command allows you to
2546 regain your normal privilege level. It uses the normal system: five
2547 numbers are returned that are indexes into the character array that is
2548 your assigned password (see SET/PASSWORD). The indexes start from
2551 You are expected to return a string which contains the characters
2552 required in the correct order. You may intersperse those characters
2553 with others to obscure your reply for any watchers. For example (and
2554 these values are for explanation :-):
2556 password = 012345678901234567890123456789
2560 aa2bbbb0ccc5ddd7xxx3n
2564 They will all match. If there is no password you will still be offered
2565 numbers but nothing will happen when you input a string. Any match is
2568 === 0^TALK <call> [<text>]^Send a text message to another station
2569 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
2570 Send a short message to any other station that is visible on the cluster
2571 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2572 command, they don't have to be connected locally.
2574 The second form of TALK is used when other cluster nodes are connected
2575 with restricted information. This usually means that they don't send
2576 the user information usually associated with logging on and off the cluster.
2578 If you know that G3JNB is likely to be present on GB7TLH, but you can only
2579 see GB7TLH in the SH/C list but with no users, then you would use the
2580 second form of the talk message.
2582 If you want to have a ragchew with someone you can leave the text message
2583 out and the system will go into 'Talk' mode. What this means is that a
2584 short message is sent to the recipient telling them that you are in a
2585 'Talking' frame of mind and then you just type - everything you send will
2586 go to the station that you asked for.
2588 All the usual announcements, spots and so on will still come out on your
2591 If you want to do something (such as send a spot) you preceed the normal
2592 command with a '/' character, eg:-
2594 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2597 To leave talk mode type:
2601 If you are in 'Talk' mode, there is an extention to the '/' command which
2602 allows you to send the output to all the people you are talking to. You do
2603 with the '//' command. For example:-
2607 will send the hftable as you have it to all the people you are currently
2610 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
2611 Type out the contents of a file in a filearea. So, for example, in
2612 filearea 'bulletins' you want to look at file 'arld051' you would
2614 TYPE bulletins/arld051
2616 See also SHOW/FILES to see what fileareas are available and a
2619 === 0^WHO^Show who is physically connected
2620 This is a quick listing that shows which callsigns are connected and
2621 what sort of connection they have
2623 === 0^WX <text>^Send a weather message to local users
2624 === 0^WX FULL <text>^Send a weather message to all cluster users
2625 === 5^WX SYSOP <text>^Send a weather message to other clusters only
2626 Weather messages can sometimes be useful if you are experiencing an extreme
2627 that may indicate enhanced conditions