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 === 6^CLEAR/DUPEFILE^Clear out the dupefile completely
332 The system maintains a list of duplicate announces and spots (amongst many
333 other things). Sometimes this file gets corrupted during operation
334 (although not very often). This command will remove the file and start
337 Try this if you get several duplicate DX Spots, one after another.
339 Please ONLY use this command if you have a problem. And then only once.
340 If it does not cure your problem, then repeating the command won't help.
341 Get onto the dxspider-support list and let us try to help.
343 If you use this command frequently then you will cause other people, as
344 well as yourself, a lot of problems with duplicates.
346 === 0^CLEAR/ROUTE [1|all]^Clear a route filter line
347 This command allows you to clear (remove) a line in a route filter or to
348 remove the whole filter.
350 see CLEAR/SPOTS for a more detailed explanation.
352 === 8^CLEAR/ROUTE <callsign> [input] [0-9|all]^Clear a route filter line
353 A sysop can clear an input or normal output filter for a user or the
354 node_default or user_default.
356 === 0^CLEAR/SPOTS [0-9|all]^Clear a spot filter line
357 This command allows you to clear (remove) a line in a spot filter or to
358 remove the whole filter.
360 If you have a filter:-
363 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
369 you will be left with:-
371 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
377 the filter will be completely removed.
379 === 8^CLEAR/SPOTS <callsign> [input] [0-9|all]^Clear a spot filter line
380 A sysop can clear an input or normal output filter for a user or the
381 node_default or user_default.
383 === 0^CLEAR/WCY [1|all]^Clear a WCY filter line
384 This command allows you to clear (remove) a line in a WCY filter or to
385 remove the whole filter.
387 see CLEAR/SPOTS for a more detailed explanation.
389 === 8^CLEAR/WCY <callsign> [input] [0-9|all]^Clear a WCY filter line
390 A sysop can clear an input or normal output filter for a user or the
391 node_default or user_default.
393 === 0^CLEAR/WWV [1|all]^Clear a WWV filter line
394 This command allows you to clear (remove) a line in a WWV filter or to
395 remove the whole filter.
397 see CLEAR/SPOTS for a more detailed explanation.
399 === 8^CLEAR/WWV <callsign> [input] [0-9|all]^Clear a WWV filter line
400 A sysop can clear an input or normal output filter for a user or the
401 node_default or user_default.
403 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
404 Start a connection process that will culminate in a new connection to the
405 DX cluster <callsign>. This process creates a new 'client' process which will
406 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
407 necessary to traverse the network(s) to logon to the cluster <callsign>.
409 === 9^DELETE/USDB <callsign> ...^Delete this user from the US State Database
410 This command will completely remove a one or more callsigns
411 from the US States database.
413 There is NO SECOND CHANCE.
415 It goes without saying that you should use this command CAREFULLY!
417 Note that these callsign may be re-instated by any weekly updates from
420 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
421 This command will completely remove a one or more users from the database.
423 There is NO SECOND CHANCE.
425 It goes without saying that you should use this command CAREFULLY!
427 === 0^DBAVAIL^Show a list of all the Databases in the system
428 Title says it all really, this command lists all the databases defined
429 in the system. It is also aliased to SHOW/COMMAND.
431 === 9^DBCREATE <name>^Create a database entry
432 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
433 === 9^DBCREATE <name> remote <node>^Create a remote database entry
434 === 9^DBCREATE <name> cmd <dxspider command>^make a local command available as a DB
435 DBCREATE allows you to define a database in the system. It doesn't actually
436 create anything, just defines it.
438 The databases that are created are simple DB_File hash databases, they are
439 therefore already 'indexed'.
441 You can define a local database with the first form of the command eg:
445 You can also chain databases with the addition of the 'chain' keyword.
446 This will search each database one after the other. A typical example
449 DBCREATE sdx_qsl chain sql_ad
451 No checking is done to see if the any of the chained databases exist, in
452 fact it is usually better to do the above staement first then do each of
453 the chained databases.
455 Databases can exist offsite. To define a database that lives on another
458 DBCREATE buckmaster remote gb7dxc
460 Remote databases cannot be chained; however, the last database in a
461 a chain can be a remote database eg:
463 DBCREATE qsl chain gb7dxc
465 To see what databases have been defined do:
467 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
469 It would be normal for you to add an entry into your local Aliases file
470 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
471 need to add a line like:-
476 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
485 to work as they may be used to.
487 You can also make local commands available as 'pseudo' databases. You
488 can therefore make spider special commands available as a database. I
489 imagine that this will be primarily useful for remote access from
490 legacy nodes. For example:-
492 DBCREATE dxqsl cmd show/dxqsl
494 You also use one of these databases in a chain. This may be useful
497 See DBIMPORT for the importing of existing AK1A format data to databases.
498 See DBSHOW for generic database enquiry
500 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
501 If you want to import or update data in bulk to a database you can use
502 this command. It will either create or update entries into an existing
503 database. For example:-
505 DBIMPORT oblast /tmp/OBLAST.FUL
507 will import the standard OBLAST database that comes with AK1A into the
508 oblast database held locally.
510 === 9^DBREMOVE <dbname>^Delete a database
511 DBREMOVE will completely remove a database entry and also delete any data
512 file that is associated with it.
514 There is no warning, no comeback, no safety net.
520 will remove the oblast database from the system and it will also remove
521 the associated datafile.
525 There is no warning, no comeback, no safety net.
527 You have been warned.
529 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
530 This is the generic user interface to the database to the database system.
531 It is expected that the sysop will add an entry to the local Aliases file
532 so that users can use the more familiar AK1A style of enquiry such as:
536 but if he hasn't and the database really does exist (use DBAVAIL or
537 SHOW/COMMAND to find out) you can do the same thing with:
541 === 9^DEBUG^Set the cluster program into debug mode
542 Executing this command will only have an effect if you are running the cluster
547 It will interrupt the cluster just after the debug command has finished.
549 === 0^DIRECTORY^List messages
550 === 0^DIRECTORY ALL^List all messages
551 === 0^DIRECTORY OWN^List your own messages
552 === 0^DIRECTORY NEW^List all new messages
553 === 0^DIRECTORY TO <call>^List all messages to <call>
554 === 0^DIRECTORY FROM <call>^List all messages from <call>
555 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
556 === 0^DIRECTORY <nn>^List last <nn> messages
557 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
558 List the messages in the messages directory.
560 If there is a 'p' one space after the message number then it is a
561 personal message. If there is a '-' between the message number and the
562 'p' then this indicates that the message has been read.
564 You can use shell escape characters such as '*' and '?' in the <call>
567 You can combine some of the various directory commands together eg:-
571 DIR SUBJECT IOTA 200-250
573 You can abbreviate all the commands to one letter and use ak1a syntax:-
579 Sysops can see all users' messages.
581 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
582 Disconnect any <call> connected locally
584 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
585 This is how you send a DX Spot to other users. You can, in fact, now
586 enter the <freq> and the <call> either way round.
592 will all give the same result. You can add some remarks to the end
593 of the command and they will be added to the spot.
595 DX FR0G 144600 this is a test
597 You can credit someone else by saying:-
599 DX by G1TLH FR0G 144.600 he isn't on the cluster
601 The <freq> is compared against the available bands set up in the
602 cluster. See SHOW/BANDS for more information.
604 === 0^ECHO <line>^Echo the line to the output
605 This command is useful in scripts and so forth for printing the
606 line that you give to the command to the output. You can use this
607 in user_default scripts and the SAVE command for titling and so forth
609 The script will interpret certain standard "escape" sequences as follows:-
611 \t - becomes a TAB character (0x09 in ascii)
612 \a - becomes a BEEP character (0x07 in ascii)
613 \n - prints a new line
615 So the following example:-
617 echo GB7DJK is a dxcluster
621 GB7DJK is a dxcluster
623 on the output. You don't need a \n on the end of the line you want to send.
625 A more complex example:-
627 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
637 === 9^EXPORT <msgno> <filename>^Export a message to a file
638 Export a message to a file. This command can only be executed on a local
639 console with a fully privileged user. The file produced will be in a form
640 ready to be imported back into the cluster by placing it in the import
641 directory (/spider/msg/import).
643 This command cannot overwrite an existing file. This is to provide some
644 measure of security. Any files written will owned by the same user as the
645 main cluster, otherwise you can put the new files anywhere the cluster can
646 access. For example:-
650 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
651 Export the users database to a file in ascii format. If no filename
652 is given then it will export the file to /spider/data/user_asc.
654 If the file already exists it will be renamed to <filename>.o. In fact
655 up to 5 generations of the file can be kept each one with an extra 'o' on the
658 BE WARNED: this will write to any file you have write access to. No check is
659 made on the filename (if any) that you specify.
661 === 0^FILTERING...^Filtering things in DXSpider
662 There are a number of things you can filter in the DXSpider system. They
663 all use the same general mechanism.
665 In general terms you can create a 'reject' or an 'accept' filter which
666 can have up to 10 lines in it. You do this using, for example:-
671 where ..... are the specific commands for that type of filter. There
672 are filters for spots, wwv, announce, wcy and (for sysops)
673 connects. See each different accept or reject command reference for
676 There is also a command to clear out one or more lines in a filter and
677 one to show you what you have set. They are:-
686 There is clear/xxxx command for each type of filter.
688 For now we are going to use spots for the examples, but you can apply
689 the principles to all types of filter.
691 There are two main types of filter 'accept' or 'reject'; which you use
692 depends entirely on how you look at the world and what is least
693 writing to achieve what you want. Each filter has 10 lines (of any
694 length) which are tried in order. If a line matches then the action
695 you have specified is taken (ie reject means ignore it and accept
698 The important thing to remember is that if you specify a 'reject'
699 filter (all the lines in it say 'reject/spots' (for instance)) then if
700 a spot comes in that doesn't match any of the lines then you will get
701 it BUT if you specify an 'accept' filter then any spots that don't
702 match are dumped. For example if I have a one line accept filter:-
704 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
706 then automatically you will ONLY get VHF spots from or to CQ zones 14
707 15 and 16. If you set a reject filter like:
709 reject/spots on hf/cw
711 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
712 and will work it even on CW then you could say:-
714 reject/spots on hf/cw and not info iota
716 But in that case you might only be interested in iota and say:-
718 accept/spots not on hf/cw or info iota
720 which is exactly the same. You should choose one or the other until
721 you are confortable with the way it works. Yes, you can mix them
722 (actually you can have an accept AND a reject on the same line) but
723 don't try this at home until you can analyse the results that you get
724 without ringing up the sysop for help.
726 Another useful addition now is filtering by US state
728 accept/spots by_state VA,NH,RI,ME
730 You can arrange your filter lines into logical units, either for your
731 own understanding or simply convenience. I have one set frequently:-
733 reject/spots 1 on hf/cw
734 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
736 What this does is to ignore all HF CW spots (being a class B I can't
737 read any CW and couldn't possibly be interested in HF :-) and also
738 rejects any spots on VHF which don't either originate or spot someone
741 This is an exmaple where you would use the line number (1 and 2 in
742 this case), if you leave the digit out, the system assumes '1'. Digits
743 '0'-'9' are available.
745 You can leave the word 'and' out if you want, it is implied. You can
746 use any number of brackets to make the 'expression' as you want
747 it. There are things called precedence rules working here which mean
748 that you will NEED brackets in a situation like line 2 because,
749 without it, will assume:-
751 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
753 annoying, but that is the way it is. If you use OR - use
754 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
757 If you want to alter your filter you can just redefine one or more
758 lines of it or clear out one line. For example:-
760 reject/spots 1 on hf/ssb
766 To remove the filter in its entirty:-
770 There are similar CLEAR commands for the other filters:-
778 Once you are happy with the results you get, you may like to experiment.
780 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
781 can be written with a mixed filter, eg:
785 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
787 each filter slot actually has a 'reject' slot and an 'accept'
788 slot. The reject slot is executed BEFORE the accept slot.
790 It was mentioned earlier that after a reject test that doesn't match,
791 the default for following tests is 'accept', the reverse is true for
792 'accept'. In the example what happens is that the reject is executed
793 first, any non hf/cw spot is passed to the accept line, which lets
794 thru everything else on HF.
796 The next filter line lets through just VHF/UHF spots from EU.
798 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
799 This command sends all the latitude and longitude information that your
800 cluster is holding against callsigns. One advantage of recieving this
801 information is that more locator information is held by you. This
802 means that more locators are given on the DX line assuming you have
803 SET/DXGRID enabled. This could be a LOT of information though, so
804 it is not recommended on slow links.
806 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
807 This command sends out any information held in the user file which can
808 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
809 and Homenode. PC41s are only sent for the information that is available.
811 === 0^HELP^The HELP Command
812 HELP is available for a number of commands. The syntax is:-
816 Where <cmd> is the name of the command you want help on.
818 All commands can be abbreviated, so SHOW/DX can be abbreviated
819 to SH/DX, ANNOUNCE can be shortened to AN and so on.
821 Look at the APROPOS <string> command which will search the help database
822 for the <string> you specify and give you a list of likely commands
823 to look at with HELP.
825 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
826 This command attempts to re-initialise a link to a (usually) AK1A node
827 that has got confused, usually by a protocol loop of some kind. It may
828 work - but you usually will be better off simply disconnecting it (or
829 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
832 Best of luck - you will need it.
834 === 9^DEMONSTRATE <call> <command>^Demonstrate a command to another user
835 This command is provided so that sysops can demonstrate commands to
836 other users. It runs a command as though that user had typed it in and
837 then sends the output to that user, together with the command that
840 DEMO g7brn sh/dx iota oc209
843 Note that this command is similar to SPOOF and will have the same side
844 effects. Commands are run at the privilege of the user which is being
847 === 0^JOIN <group>^Join a chat or conference group
848 JOIN allows you to join a network wide conference group. To join a
849 group (called FOC in this case) type:-
853 See also CHAT, LEAVE, SHOW/CHAT
855 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
856 === 0^KILL <from msgno>-<to msgno>^Delete a range of messages
857 === 0^KILL from <regex>^Delete messages FROM a callsign or pattern
858 === 0^KILL to <regex>^Delete messages TO a callsign or pattern
859 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
860 Delete a message from the local system. You will only be able to
861 delete messages that you have originated or been sent (unless you are
866 Will delete all the messages that you own between msgnos 1234 and 1255.
870 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
874 will delete all messages to g1tlh.
878 will delete a message (usually a 'bulletin') from the whole cluster system.
880 This uses the subject field, so any messages that have exactly the
881 same subject will be deleted. Beware!
883 === 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
884 Deleting a message using the normal KILL commands only marks that message
885 for deletion. The actual deletion only happens later (usually two days later).
887 The KILL EXPUNGE command causes the message to be truly deleted more or less
890 It otherwise is used in the same way as the KILL command.
892 === 0^LEAVE <group>^Leave a chat or conference group
893 LEAVE allows you to leave a network wide conference group. To leave a
894 group (called FOC in this case) type:-
898 See also CHAT, JOIN, SHOW/CHAT
900 === 0^LINKS^Show which nodes is physically connected
901 This is a quick listing that shows which links are connected and
902 some information about them. See WHO for a list of all connections.
904 === 9^LOAD/ALIASES^Reload the command alias table
905 Reload the /spider/cmd/Aliases file after you have editted it. You
906 will need to do this if you change this file whilst the cluster is
907 running in order for the changes to take effect.
909 === 9^LOAD/BANDS^Reload the band limits table
910 Reload the /spider/data/bands.pl file if you have changed it manually whilst
911 the cluster is running.
913 === 9^LOAD/BADMSG^Reload the bad msg table
914 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
915 the cluster is running. This table contains a number of perl regular
916 expressions which are searched for in the fields targetted of each message.
917 If any of them match then that message is immediately deleted on receipt.
919 === 9^LOAD/BADWORDS^Reload the bad words table
920 Reload the /spider/data/badwords file if you have changed it manually whilst
921 the cluster is running. This file contains a list of words which, if found
922 on certain text portions of PC protocol, will cause those protocol frames
923 to be rejected. It will all put out a message if any of these words are
924 used on the announce, dx and talk commands. The words can be one or
925 more on a line, lines starting with '#' are ignored.
927 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
928 Normally, if you change a command file in the cmd or local_cmd tree it
929 will automatially be picked up by the cluster program. Sometimes it
930 can get confused if you are doing a lot of moving commands about or
931 delete a command in the local_cmd tree and want to use the normal one
932 again. Execute this command to reset everything back to the state it
933 was just after a cluster restart. To see what is in the command cache
936 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
937 Reload the /spider/msg/forward.pl file if you have changed it
938 manually whilst the cluster is running.
940 === 5^LOAD/KEPS^Load new keps data
941 === 5^LOAD/KEPS [nn]^Load new keps data from message
942 If there is no message number then reload the current Keps data from
943 the Keps.pm data file. You create this file by running
945 /spider/perl/convkeps.pl <filename>
947 on a file containing NASA 2 line keps as a message issued by AMSAT.
949 If there is a message number, then it will take the message, run
950 convkeps.pl on it and then load the data, all in one step.
952 These messages are sent to ALL by GB7DJK (and others) from time to time.
954 === 9^LOAD/MESSAGES^Reload the system messages file
955 If you change the /spider/perl/Messages file (usually whilst
956 fiddling/writing new commands) you can have them take effect during a
957 cluster session by executing this command. You need to do this if get
960 unknown message 'xxxx' in lang 'en'
962 === 9^LOAD/PREFIXES^Reload the prefix table
963 Reload the /spider/data/prefix_data.pl file if you have changed it
964 manually whilst the cluster is running.
966 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
967 MERGE allows you to bring your spot and wwv database up to date. By default
968 it will request the last 10 spots and 5 WWVs from the node you select. The
969 node must be connected locally.
971 You can request any number of spots or wwv and although they will be appended
972 to your databases they will not duplicate any that have recently been added
973 (the last 2 days for spots and last month for WWV data).
975 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
976 Alter message parameters like To, From, Subject, whether private or bulletin
977 or return receipt (RR) is required or whether to keep this message from timing
980 MSG TO <msgno> <call> - change TO callsign to <call>
981 MSG FRom <msgno> <call> - change FROM callsign to <call>
982 MSG PRrivate <msgno> - set private flag
983 MSG NOPRrivate <msgno> - unset private flag
984 MSG RR <msgno> - set RR flag
985 MSG NORR <msgno> - unset RR flag
986 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
987 MSG NOKEep <msgno> - unset the keep flag
988 MSG SUbject <msgno> <new> - change the subject to <new>
989 MSG WAittime <msgno> - remove any waitting time for this message
990 MSG NOREad <msgno> - mark message as unread
991 MSG REad <msgno> - mark message as read
992 MSG QUeue - queue any outstanding bulletins
993 MSG QUeue 1 - queue any outstanding private messages
995 You can look at the status of a message by using:-
999 This will display more information on the message than DIR does.
1001 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
1002 Send some arbitrary text to a locally connected callsign. No
1003 processing is done on the text. This command allows you to send PC
1004 Protocol to unstick things if problems arise (messages get stuck
1007 pc gb7djk PC33^GB7TLH^GB7DJK^400^
1009 pc G1TLH Try doing that properly!!!
1011 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
1012 You can get rid of any message to or originating from your callsign using
1013 this command. You can remove more than one message at a time.
1015 === 5^KILL <from>-<to>^Remove a range of messages from the system
1016 === 5^KILL FROM <call>^Remove all messages from a callsign
1017 === 5^KILL TO <call>^Remove all messages to a callsign
1018 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
1019 Remove this message from the entire cluster system as well as your node.
1022 As a sysop you can kill any message on the system.
1024 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
1025 Send any text you like to the callsign requested. This is used mainly to send
1026 PC protocol to connected nodes either for testing or to unstick things.
1028 You can also use in the same way as a talk command to a connected user but
1029 without any processing, added of "from <blah> to <blah" or whatever.
1031 === 1^PING <node call>^Check the link quality between nodes
1032 This command allows you to send a frame to another cluster node on
1033 the network and get a return frame. The time it takes to do this
1034 is a good indication of the quality of the link. The actual time
1035 it takes is output to the console in seconds.
1036 Any visible cluster node can be PINGed.
1038 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
1039 This command allows you to send nearly any command to another DX Cluster
1040 node that is connected to the system.
1042 Whether you get any output is dependant on a) whether the other system knows
1043 that the node callsign of this cluster is in fact a node b) whether the
1044 other system is allowing RCMDs from this node and c) whether you have
1045 permission to send this command at all.
1047 === 0^READ^Read the next unread personal message addressed to you
1048 === 0^READ <msgno>^Read the specified message
1049 You can read any messages that are sent as 'non-personal' and also any
1050 message either sent by or sent to your callsign.
1053 As a sysop you may read any message on the system
1055 === 0^REJECT^Set a filter to reject something
1056 Create a filter to reject something
1058 There are 2 types of filter, accept and reject. See HELP FILTERING for more
1061 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
1062 Create an 'reject this announce' line for a filter.
1064 A reject filter line means that if the announce matches this filter it is
1065 passed onto the user. See HELP FILTERING for more info. Please read this
1066 to understand how filters work - it will save a lot of grief later on.
1068 You can use any of the following things in this line:-
1070 info <string> eg: iota or qsl
1071 by <prefixes> eg: G,M,2
1073 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1074 origin_itu <prefixes or numbers> or: G,GM,GW
1075 origin_zone <prefixes or numbers>
1076 origin_state <states> eg: VA,NH,RI,ME
1077 by_dxcc <prefixes or numbers>
1078 by_itu <prefixes or numbers>
1079 by_zone <prefixes or numbers>
1080 by_state <states> eg: VA,NH,RI,ME
1082 wx 1 filter WX announces
1083 dest <prefixes> eg: 6MUK,WDX (distros)
1087 rej/ann by_zone 14,15,16 and not by G,M,2
1089 You can use the tag 'all' to reject everything eg:
1093 but this probably for advanced users...
1095 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
1096 This version allows a sysop to set a filter for a callsign as well as the
1097 default for nodes and users eg:-
1100 reject/ann input node_default by G,M,2
1101 reject/ann user_default by G,M,2
1103 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
1104 Create a 'reject this spot' line for a filter.
1106 A reject filter line means that if the spot matches this filter it is
1107 dumped (not passed on). See HELP FILTERING for more info. Please read this
1108 to understand how filters work - it will save a lot of grief later on.
1110 You can use any of the following things in this line:-
1112 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1113 on <range> same as 'freq'
1114 call <prefixes> eg: G,PA,HB9
1115 info <string> eg: iota or qsl
1117 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1118 call_itu <prefixes or numbers> or: G,GM,GW
1119 call_zone <prefixes or numbers>
1120 call_state <states> eg: VA,NH,RI,ME
1121 by_dxcc <prefixes or numbers>
1122 by_itu <prefixes or numbers>
1123 by_zone <prefixes or numbers>
1124 by_state <states> eg: VA,NH,RI,ME
1128 'call' means the callsign that has spotted 'by' whoever.
1130 For frequencies, you can use any of the band names defined in
1131 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1132 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1133 this is more efficient than saying simply: on HF (but don't get
1134 too hung up about that)
1139 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1141 You can use the tag 'all' to reject everything eg:
1145 but this probably for advanced users...
1147 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
1148 Create an 'reject this routing PC Protocol' line for a filter.
1150 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1151 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1152 read this to understand how filters work - it will save a lot of grief later on.
1154 You can use any of the following things in this line:-
1156 call <prefixes> the callsign of the thingy
1157 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1158 call_itu <prefixes or numbers> or: G,GM,GW
1159 call_zone <prefixes or numbers>
1160 call_state <states> eg: VA,NH,RI,ME
1161 origin <prefixes> really the interface it came in on
1162 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1163 origin_itu <prefixes or numbers> or: G,GM,GW
1164 origin_zone <prefixes or numbers>
1165 origin_state <states> eg: VA,NH,RI,ME
1169 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1171 You can use the tag 'all' to reject everything eg:
1173 rej/route all (equiv to [very] restricted mode)
1175 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
1177 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
1178 This version allows a sysop to set a filter for a callsign as well as the
1179 default for nodes and users eg:-
1181 reject/spot db0sue-7 1 by_zone 14,15,16
1182 reject/spot node_default all
1183 set/hops node_default 10
1185 reject/spot user_default by G,M,2
1187 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
1188 It is unlikely that you will want to do this, but if you do then you can
1189 filter on the following fields:-
1191 by <prefixes> eg: G,M,2
1193 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1194 origin_itu <prefixes or numbers> or: G,GM,GW
1195 origin_zone <prefixes or numbers>
1196 by_dxcc <prefixes or numbers>
1197 by_itu <prefixes or numbers>
1198 by_zone <prefixes or numbers>
1201 There are no examples because WCY Broadcasts only come from one place and
1202 you either want them or not (see UNSET/WCY if you don't want them).
1204 This command is really provided for future use.
1206 See HELP FILTER for information.
1208 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
1209 This version allows a sysop to set a filter for a callsign as well as the
1210 default for nodes and users eg:-
1212 reject/wcy gb7djk all
1214 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
1215 It is unlikely that you will want to do this, but if you do then you can
1216 filter on the following fields:-
1218 by <prefixes> eg: G,M,2
1220 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1221 origin_itu <prefixes or numbers> or: G,GM,GW
1222 origin_zone <prefixes or numbers>
1223 by_dxcc <prefixes or numbers>
1224 by_itu <prefixes or numbers>
1225 by_zone <prefixes or numbers>
1230 reject/wwv by_zone 14,15,16
1232 is probably the only useful thing to do (which will only show WWV broadcasts
1233 by stations in the US).
1235 See HELP FILTER for information.
1237 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
1238 This version allows a sysop to set a filter for a callsign as well as the
1239 default for nodes and users eg:-
1241 reject/wwv db0sue-7 1 by_zone 4
1242 reject/wwv node_default all
1244 reject/wwv user_default by W
1246 === 0^REPLY^Reply (privately) to the last message that you have read
1247 === 0^REPLY <msgno>^Reply (privately) to the specified message
1248 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1249 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1250 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1251 You can reply to a message and the subject will automatically have
1252 "Re:" inserted in front of it, if it isn't already present.
1254 You can also use all the extra qualifiers such as RR, PRIVATE,
1255 NOPRIVATE, B that you can use with the SEND command (see SEND
1256 for further details)
1258 === 9^SAVE [-d -t -a] <filename> "<cmd>" [...]^Save command output to a file
1259 This sysop only cammand allows you to save the output of one or more
1260 commands to a file. For example:-
1262 save /spider/packclus/dxstats show/dxstat
1264 will save the output of the normal command "show/dxstat" to the file
1265 "dxstats" in the files area.
1267 You can have some extra flags to the save which will either
1268 date stamp or time stamp or both the filename so:-
1270 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
1271 save -t /tmp/a <cmd> creates /tmp/a_2301Z
1272 save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
1274 The -a flag means append to the file instead of overwriting it.
1276 You can have more than one command on the line, to do this you MUST
1277 enclose each command in double quotes (") eg:-
1279 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
1283 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
1285 You can only write into places that the cluster has permission for (which
1286 is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
1287 need to create any directories you want to put stuff in beforehand as well.
1289 It is likely that you will want to run these commands in a crontab type
1290 situation. You would do that something like:-
1292 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
1294 Note that you still enclose each command with (") characters but you must
1295 enclose the entire save command in (') characters.
1297 Now in fact, this can be varied if you know what you are doing. See the
1298 admin manual for more details.
1300 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1301 === 0^SEND RR <call>^Send a message and ask for a read receipt
1302 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1303 === 0^SEND PRIVATE <call>^Send a personal message
1304 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1305 All the SEND commands will create a message which will be sent either to
1306 an individual callsign or to one of the 'bulletin' addresses.
1308 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1309 it will mark the message as personal and send it to the cluster node that
1310 that callsign is connected to. If the <call> you have specified is in fact
1311 a known bulletin category on your node (eg: ALL) then the message should
1312 automatically become a bulletin.
1314 You can have more than one callsign in all of the SEND commands.
1316 You can have multiple qualifiers so that you can have for example:-
1318 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1320 which should send a copy of message 123 to G1TLH and G0RDI and you will
1321 receive a read receipt when they have read the message.
1323 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1324 SP is an alias for SEND PRIVATE
1326 The system will ask you for a subject. Conventionally this should be
1327 no longer than 29 characters for compatibility. Most modern cluster
1328 software should accept more.
1330 You will now be prompted to start entering your text.
1332 You finish the message by entering '/EX' on a new line. For instance:
1339 If you have started a message and you don't want to keep it then you
1340 can abandon the message with '/ABORT' on a new line, like:-
1344 oh I just can't be bothered with this
1347 If you abort the message it will NOT be sent.
1349 When you are entering the text of your message, most normal output (such
1350 as DX announcements and so on are suppressed and stored for latter display
1351 (upto 20 such lines are stored, as new ones come along, so the oldest
1354 Also, you can enter normal commands commands (and get the output
1355 immediately) whilst in the middle of a message. You do this by typing
1356 the command preceeded by a '/' character on a new line, so:-
1358 /dx g1tlh 144010 strong signal
1360 Will issue a dx annoucement to the rest of the cluster.
1362 Also, you can add the output of a command to your message by preceeding
1363 the command with '//', thus :-
1367 This will show YOU the output from SH/VHFTABLE and also store it in the
1370 You can carry on with the message until you are ready to send it.
1371 === 0^SET/ADDRESS <your address>^Record your postal address
1373 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1374 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1376 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1377 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1378 The announce system on legacy cluster nodes is used as a talk
1379 substitute because the network is so poorly connected. If you:
1383 you will suppress several of these announces, you may miss the odd
1384 useful one as well, but you would probably miss them anyway in the
1385 welter of useless ones.
1389 allows you to see them again. This is the default.
1391 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1393 === 8^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1394 === 8^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1395 Setting a word as 'baddx' will prevent spots with that word in the
1396 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1397 further. They will not be displayed and they will not be sent onto
1400 The word must be written in full, no wild cards are allowed eg:-
1402 set/baddx FORSALE VIDEO FR0G
1404 To allow a word again, use the following command ...
1408 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1409 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1410 Setting a callsign as a 'badnode' will prevent spots from that node
1411 going any further. They will not be displayed and they will not be
1412 sent onto other nodes.
1414 The call must be a full eg:-
1418 will stop anything from K1TTT. If you want SSIDs as well then you must
1419 enter them specifically.
1423 will allow spots from him again.
1425 Use with extreme care. This command may well be superceeded by FILTERing.
1427 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1428 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1429 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1430 going any further. They will not be displayed and they will not be
1431 sent onto other nodes.
1433 The call must be written in full, no wild cards are allowed eg:-
1435 set/badspotter VE2STN
1437 will stop anything from VE2STN. This command will automatically
1438 stop spots from this user, regardless of whether or which SSID
1439 he uses. DO NOT USE SSIDs in the callsign, just use the callsign
1442 unset/badspotter VE2STN
1444 will allow spots from him again.
1446 Use with extreme care. This command may well be superceded by FILTERing.
1448 This command will also stop TALK and ANNOUNCE/FULL from any user marked
1451 === 8^SET/BADWORD <word>..^Stop things with this word being propagated
1452 === 8^UNSET/BADWORD <word>..^Propagate things with this word again
1453 Setting a word as a 'badword' will prevent things like spots,
1454 announces or talks with this word in the the text part from going any
1455 further. They will not be displayed and they will not be sent onto
1458 The word must be written in full, no wild cards are allowed eg:-
1460 set/badword annihilate annihilated annihilation
1462 will stop anything with these words in the text.
1464 unset/badword annihilated
1466 will allow text with this word again.
1468 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1469 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1471 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1473 === 0^SET/BUDDY <call> [<call>..]^Add this call to my buddy list
1474 === 0^UNSET/BUDDY <call> [<call>..]^Remove this call from my buddy list
1475 A notification message
1476 is sent to you automatically if anybody on your buddy list logs in or
1477 out of any node in this cluster.
1479 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1481 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1482 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1483 You can choose to log several different levels. The levels are
1491 You can show what levels you are logging with SHOW/DEBUG
1493 === 0^SET/DX^Allow DX messages to come out on your terminal
1494 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1496 === 0^SET/DXCQ^Show CQ Zones on the end of DX announcements
1497 === 0^UNSET/DXCQ^Stop CQ Zones on the end of DX announcements
1498 Display both the Spotter's and the Spotted's CQ Zone on the end
1499 of a DX announcement (there is just enough room). Some user programs
1500 cannot cope with this. The Spotter's CQ is on the RHS of the
1501 time, the Spotted's CQ is on the LHS.
1503 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
1505 Do a STAT/USER to see which flags you have set if you are confused.
1507 === 0^SET/DXITU^Show ITU Zones on the end of DX announcements
1508 === 0^UNSET/DXITU^Stop ITU Zones on the end of DX announcements
1509 Display both the Spotter's and the Spotted's ITU Zone on the end
1510 of a DX announcement (there is just enough room). Some user programs
1511 cannot cope with this. The Spotter's ITU is on the RHS of the
1512 time, the Spotted's ITU is on the LHS.
1514 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
1516 Do a STAT/USER to see which flags you have set if you are confused.
1518 === 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
1519 === 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
1520 A standard feature which is enabled in version 1.43 and above is
1521 that if the spotter's grid square is known it is output on the end
1522 of a DX announcement (there is just enough room). Some user programs
1523 cannot cope with this. You can use this command to reset (or set)
1526 Conflicts with: SET/DXCQ, SET/DXITU
1528 Do a STAT/USER to see which flags you have set if you are confused.
1530 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1532 === 0^SET/ECHO^Make the cluster echo your input
1533 === 0^UNSET/ECHO^Stop the cluster echoing your input
1534 If you are connected via a telnet session, different implimentations
1535 of telnet handle echo differently depending on whether you are
1536 connected via port 23 or some other port. You can use this command
1537 to change the setting appropriately.
1539 The setting is stored in your user profile.
1541 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1543 === 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
1544 === 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
1545 If any personal messages come in for your callsign then you can use
1546 these commands to control whether they are forwarded onto your email
1547 address. To enable the forwarding do something like:-
1549 SET/EMAIL mike.tubby@somewhere.com
1551 You can have more than one email address (each one separated by a space).
1552 Emails are forwarded to all the email addresses you specify.
1554 You can disable forwarding by:-
1558 === 0^SET/HERE^Tell the system you are present at your terminal
1559 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1561 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1562 Tell the cluster system where you normally connect to. Any Messages sent
1563 to you will normally find their way there should you not be connected.
1567 === 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
1568 === 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
1569 Set the hop count for a particular type of broadcast for a node.
1571 This command allows you to set up special hop counts for a node
1572 for currently: announce, spots, wwv and wcy broadcasts.
1575 set/hops gb7djk ann 10
1576 set/hops gb7mbc spots 20
1578 Set SHOW/HOPS for information on what is already set. This command
1579 creates a filter and works in conjunction with the filter system.
1581 You can unset the hops with command UNSET/HOPS. For example:-
1583 unset/hops gb7djk ann
1584 unset/hops gb7mbc spots
1587 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1588 Connect a node to your system in such a way that you are a full protocol
1589 member of its network and can see all spots on it, but nothing either leaks
1590 out from it nor goes back into from the rest of the nodes connected to you.
1592 You can potentially connect several nodes in this way.
1594 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1595 Remove isolation from a node - SET/ISOLATE
1597 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1598 You can select the language that you want the cluster to use. Currently
1599 the languages available are en (English), de (German), es (Spanish),
1600 Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
1602 === 5^SET/LOCAL_NODE^Add node to the local_node group
1603 === 5^UNSET/LOCAL_NODE^Remove node from the local_node group
1604 The 'local_node' group is a group of nodes that you want a user
1605 to perceive as effectively one big node. At the moment, this extends
1606 only to announcing whenever a user is logging in or out of one of
1607 the nodes in the group (if those users have SET/LOGININFO).
1609 The local node group is as setup on this node. If you want the other
1610 nodes to also include this node and all the other nodes specified, then
1611 you must get those nodes to also run this command (or rcmd them to do
1614 In principle, therefore, each node determines its own local node group
1615 and these can overlap with other nodes' views.
1617 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1618 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1619 In order to get accurate headings and such like you must tell the system
1620 what your latitude and longitude is. If you have not yet done a SET/QRA
1621 then this command will set your QRA locator for you. For example:-
1622 SET/LOCATION 52 22 N 0 57 E
1624 === 0^SET/LOGININFO^Inform when a station logs in/out locally
1625 === 0^UNSET/LOGININFO^No longer inform when a station logs in/out locally
1627 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1628 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1630 === 0^SET/NAME <your name>^Set your name
1631 Tell the system what your name is eg:-
1634 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1635 Tell the system that the call(s) are to be treated as AK1A cluster and
1636 fed PC Protocol rather normal user commands.
1638 === 8^SET/OBSCOUNT <count> <call>^Set the 'pump-up' obscelence PING counter
1639 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1640 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1641 counter which is decremented on every outgoing ping and then reset to
1642 the 'obscount' value on every incoming ping. The default value of this
1645 What this means is that a neighbouring node will be pinged twice at
1646 (default) 300 second intervals and if no reply has been heard just before
1647 what would be the third attempt, that node is disconnected.
1649 If a ping is heard then the obscount is reset to the full value. Using
1650 default values, if a node has not responded to a ping within 15 minutes,
1653 You can set this parameter between 1 and 9.
1655 It is STRONGLY recommended that you don't change the default.
1657 === 0^SET/PAGE <lines per page>^Set the lines per page
1658 Tell the system how many lines you wish on a page when the number of line
1659 of output from a command is more than this. The default is 20. Setting it
1660 explicitly to 0 will disable paging.
1664 The setting is stored in your user profile.
1666 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1667 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1668 in order to determine the rolling quality of the link and, in future, to
1669 affect routing decisions. The default interval is 300 secs or 5 minutes.
1671 You can use this command to set a different interval. Please don't.
1673 But if you do the value you enter is treated as minutes up 30 and seconds
1674 for numbers greater than that.
1676 This is used also to help determine when a link is down at the far end
1677 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1678 for more information.
1680 If you must change it (and it may be useful for internet connected nodes
1681 on dynamic IP addresses that go away after a set time of usage) the time
1682 can be specified as:-
1684 5 which if less than 30 is converted to minutes otherwise is
1685 taken as the no of seconds between pings.
1690 Please be aware that this causes traffic to occur on the link, setting
1691 this value too low may annoy your neighbours beyond the point of
1694 You can switch this off by setting it to 0.
1696 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1697 Set the privilege level on a callsign. The privilege levels that pertain
1698 to commands are as default:-
1700 1 - allow remote nodes normal user RCMDs
1701 5 - various privileged commands (including shutdown, but not disc-
1702 connect), the normal level for another node.
1703 8 - more privileged commands (including disconnect)
1704 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1706 If you are a sysop and you come in as a normal user on a remote connection
1707 your privilege will automatically be set to 0.
1709 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1710 You can use this command to 'protect' this session from unauthorised
1711 use. If you want to get your normal privilege back you will need to
1712 either logout and login again (if you are on a console) or use the
1715 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1716 The password for a user can only be set by a full sysop. The string
1717 can contain any characters.
1719 The way this field is used depends on context. If it is being used in
1720 the SYSOP command context then you are offered 5 random numbers and you
1721 have to supply the corresponding letters. This is now mainly for ax25
1724 If it is being used on incoming telnet connections then, if a password
1727 set/var $main::passwdreq = 1
1729 command is executed in the startup script, then a password prompt is
1730 given after the normal 'login: ' prompt.
1732 === 0^SET/PASSWORD^Set your own password
1733 This command only works for a 'telnet' user (currently). It will
1734 only work if you have a password already set. This initial password
1735 can only be set by the sysop.
1737 When you execute this command it will ask you for your old password,
1738 then ask you to type in your new password twice (to make sure you
1739 get it right). You may or may not see the data echoed on the screen
1740 as you type, depending on the type of telnet client you have.
1742 === 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
1743 This command allows the sysop to completely delete and remove a
1744 password for a user.
1746 === 0^SET/PROMPT <string>^Set your prompt to <string>
1747 === 0^UNSET/PROMPT^Set your prompt back to default
1748 This command will set your user prompt to the string that you
1749 say. The point of this command to enable a user to interface to programs
1750 that are looking for a specific prompt (or else you just want a different
1755 There are some substitutions that can be added to the prompt:
1757 %C - callsign [which will have ( and ) around it if not here]
1760 %M - cluster 'mycall'
1762 The standard prompt is defined as:
1764 SET/PROMPT %C de %M %D %T dxspider >
1766 UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to
1769 === 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
1770 === 0^SET/QRA <locator>^Set your QRA Grid locator
1771 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1772 done a SET/LOCATION then your latitude and longitude will be set roughly
1773 correctly (assuming your locator is correct ;-). For example:-
1776 === 0^SET/QTH <your qth>^Set your QTH
1777 Tell the system where you are. For example:-
1778 SET/QTH East Dereham, Norfolk
1780 === 9^SET/REGISTER <call> ...^Mark a user as registered
1781 === 9^UNSET/REGISTER <call> ...^Mark a user as not registered
1782 Registration is a concept that you can switch on by executing the
1784 set/var $main::regreq = 1
1786 command (usually in your startup file)
1788 If a user is NOT registered then, firstly, instead of the normal
1789 motd file (/spider/data/motd) being sent to the user at startup, the
1790 user is sent the motd_nor file instead. Secondly, the non registered
1791 user only has READ-ONLY access to the node. The non-registered user
1792 cannot use DX, ANN etc.
1794 The only exception to this is that a non-registered user can TALK or
1795 SEND messages to the sysop.
1797 === 6^SET/STARTUP <call>^Create a user startup script
1798 === 0^SET/STARTUP^Create your own startup script
1799 Create a startup script of DXSpider commands which will be executed
1800 everytime that you login into this node. You can only input the whole
1801 script afresh, it is not possible to 'edit' it. Inputting a new script is
1802 just like typing in a message using SEND. To finish inputting type: /EX
1803 on a newline, to abandon the script type: /ABORT.
1805 You may find the (curiously named) command BLANK useful to break
1806 up the output. If you simply want a blank line, it is easier to
1807 input one or more spaces and press the <return> key.
1809 See UNSET/STARTUP to remove a script.
1811 === 6^UNSET/STARTUP <call>^Remove a user startup script
1812 === 0^UNSET/STARTUP^Remove your own startup script
1813 You can remove your startup script with UNSET/STARTUP.
1815 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1816 Tell the system that the call(s) are to be treated as DXSpider node and
1817 fed new style DX Protocol rather normal user commands.
1819 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1820 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1822 === 9^SET/USDB <call> <state> <city>^add/update a US DB callsign
1823 This command allows you to add or alter a callsign in the US state
1824 database. Use with extreme caution. Anything you do here will be
1825 overwritten by any weekly updates that affect this callsign
1827 set/usdb g1tlh nh downtown rindge
1829 see also DELETE/USDB
1831 === 0^SET/USSTATE^Allow US State info on the end of DX announcements
1832 === 0^UNSET/USSTATE^Stop US State info on the end of DX announcements
1833 If the spotter's or spotted's US State is known it is output on the
1834 end of a DX announcement (there is just enough room).
1836 A spotter's state will appear on the RHS of the time (like
1837 SET/DXGRID) and the spotted's State will appear on the LHS of the
1838 time field. Any information found will override any locator
1839 information from SET/DXGRID.
1841 Some user programs cannot cope with this. You can use this command
1842 to reset (or set) this feature.
1844 Conflicts with: SET/DXCQ, SET/DXITU
1846 Do a STAT/USER to see which flags you have set if you are confused.
1848 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1849 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1851 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1852 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1854 === 0^SET/WX^Allow WX messages to come out on your terminal
1855 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1857 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1858 Display all the bad dx callsigns in the system, see SET/BADDX
1859 for more information.
1861 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1862 Display all the bad node callsigns in the system, see SET/BADNODE
1863 for more information.
1865 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1866 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1867 for more information.
1869 === 1^SHOW/BADWORD^Show all the bad words in the system
1870 Display all the bad words in the system, see SET/BADWORD
1871 for more information.
1873 === 0^SHOW/BANDS [band|region names]^Show the list of bands and regions
1874 Display the bands and regions (collections of bands) known to
1875 the system. If you supply band or region names to SHOW/BANDS,
1876 the command will display just those bands or regions, e.g.:
1881 === 0^SHOW/BUDDY^Show your list of buddies
1882 See SET/BUDDY for more information about buddies.
1884 === 0^SHOW/CHAT [<group>] [<lines>]^Show any chat or conferencing
1885 This command allows you to see any chat or conferencing that has
1886 occurred whilst you were away. SHOW/CHAT on its own will show data for
1887 all groups. If you use a group name then it will show only chat for
1890 === 9^SHOW/CMD_CACHE [pattern]^Show the real source path of commands
1891 It is possible in DXSpider to define local versions of commands.
1892 Sometimes one forgets that one has these. This command will show you
1893 the source path where the node is getting each one of its commands.
1895 If you find a local command that you don't want then then simply
1896 delete it, run LOAD/CMD_CACHE to clear out the command cache and
1897 try again. You will now be using the standard version.
1899 If you are looking for information on a specific command then
1900 just add a string, eg:
1907 set/dxgrid /spider/cmd/set/dxgrid.pl
1908 sh/dx /spider/cmd/show/dx.pl
1910 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1911 This command allows you to see all the users that can be seen
1912 and the nodes to which they are connected.
1914 This command is normally abbreviated to: sh/c
1916 Normally, the list returned will be just for the nodes from your
1917 country (because the list otherwise will be very long).
1921 will produce a complete list of all nodes.
1923 BE WARNED: the list that is returned can be VERY long
1925 It is possible to supply a node or part of a prefix and you will get
1926 a list of the users for that node or list of nodes starting with
1933 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1934 Show all the nodes connected to this node.
1936 === 1^SHOW/CONNECT^Show all the active connections
1937 This command shows information on all the active connections known to
1938 the node. This command gives slightly more information than WHO.
1940 === 0^SHOW/CONTEST <year and month>^Show all the contests for a month
1941 Show all known contests which are maintained at http://www.sk3bg.se/contest/
1942 for a particular month or year. The format is reasonably flexible.
1948 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1949 This is very nearly the same as SHOW/TIME, the only difference the format
1950 of the date string if no arguments are given.
1952 If no prefixes or callsigns are given then this command returns the local
1953 time and UTC as the computer has it right now. If you give some prefixes
1954 then it will show UTC and UTC + the local offset (not including DST) at
1955 the prefixes or callsigns that you specify.
1957 === 0^SHOW/DB0SDX <callsign>^Show QSL infomation from DB0SDX database
1958 This command queries the DB0SDX QSL server on the internet
1959 and returns any information available for that callsign. This service
1960 is provided for users of this software by http://www.qslinfo.de.
1962 See also SHOW/QRZ, SHOW/WM7D.
1964 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1966 === 0^SHOW/DX^Interrogate the spot database
1967 If you just type SHOW/DX you will get the last so many spots
1968 (sysop configurable, but usually 10).
1970 In addition you can add any number of these commands in very nearly
1971 any order to the basic SHOW/DX command, they are:-
1973 on <band> - eg 160m 20m 2m 23cm 6mm
1974 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1975 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
1978 <number> - the number of spots you want
1979 <from>-<to> - <from> spot no <to> spot no in the selected list
1982 <prefix> - for a spotted callsign beginning with <prefix>
1983 *<suffix> - for a spotted callsign ending in <suffix>
1984 *<string>* - for a spotted callsign containing <string>
1986 day <number> - starting <number> days ago
1987 day <from>-<to> - <from> days <to> days ago
1990 info <text> - any spots containing <text> in the info or remarks
1992 by <call> - any spots spotted by <call> (spotter <call> is the
1995 qsl - this automatically looks for any qsl info on the call
1996 held in the spot database.
1998 iota [<iota>] - If the iota island number is missing it will look for
1999 the string iota and anything which looks like an iota
2000 island number. If you specify then it will look for
2003 qra [<locator>] - this will look for the specific locator if you specify
2004 one or else anything that looks like a locator.
2006 dxcc - treat the prefix as a 'country' and look for spots
2007 from that country regardless of actual prefix.
2010 You can also use this with the 'by' keyword so
2013 real or rt - Format the output the same as for real time spots. The
2014 formats are deliberately different (so you can tell
2015 one sort from the other). This is useful for some
2016 logging programs that can't cope with normal sh/dx
2017 output. An alias of SHOW/FDX is available.
2019 filter - Filter the spots, before output, with the user's
2020 spot filter. An alias of SHOW/MYDX is available.
2022 zone <zones> - look for spots in the cq zone (or zones) specified.
2023 zones are numbers separated by commas.
2025 by_zone <zones> - look for spots spotted by people in the cq zone
2028 itu <itus> - look for spots in the itu zone (or zones) specified
2029 itu zones are numbers separated by commas.
2031 by_itu <itus> - look for spots spotted by people in the itu zone
2034 state <list> - look for spots in the US state (or states) specified
2035 The list is two letter state codes separated by commas.
2037 by_state <list> - look for spots spotted by people in the US state
2043 SH/DX on 20m info iota
2044 SH/DX 9a on vhf day 30
2050 SH/DX dxcc oq2 by w dxcc
2054 SH/DX by_state in,oh
2056 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
2057 This command takes the <prefix> (which can be a full or partial
2058 callsign if desired), looks up which internal country number it is
2059 and then displays all the spots as per SH/DX for that country.
2061 This is now an alias for 'SHOW/DX DXCC'
2063 The options for SHOW/DX also apply to this command.
2067 SH/DXCC W on 20m iota
2069 This can be done with the SHOW/DX command like this:-
2072 SH/DX dxcc w on 20m iota
2074 This is an alias for: SH/DX dxcc
2076 === 0^SHOW/FDX^Show the DX data in realtime format.
2077 Normally SHOW/DX outputs spot data in a different format to the
2078 realtime data. This is a deliberate policy (so you can tell the
2079 difference between the two). Some logging programs cannot handle
2080 this so SHOW/FDX outputs historical data in real time format.
2082 This is an alias for: SHOW/DX real
2084 === 0^SHOW/DXSTATS [days] [date]^Show the DX Statistics
2085 Show the total DX spots for the last <days> no of days (default is 31),
2086 starting from a <date> (default: today).
2088 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
2089 SHOW/FILES on its own will show you a list of the various fileareas
2090 available on the system. To see the contents of a particular file
2093 where <filearea> is the name of the filearea you want to see the
2096 You can also use shell globbing characters like '*' and '?' in a
2097 string to see a selection of files in a filearea eg:-
2098 SH/FILES bulletins arld*
2100 See also TYPE - to see the contents of a file.
2102 === 0^SHOW/FILTER^Show the contents of all the filters you have set
2103 Show the contents of all the filters that are set. This command displays
2104 all the filters set - for all the various categories.
2106 === 0^SHOW/GRAYLINE [ndays] [<prefix>|<callsign>]^Show Civil dawn/dusk times
2107 This command is very similar to SHOW/SUN except that it shows the
2108 start and end of "Official" or "Civil" Dawn and Dusk. This is defined
2109 as when the Sun is 6 degrees below the horizon.
2111 If you don't specify any prefixes or callsigns, it will show the
2112 times for your QTH (assuming you have set it with either SET/LOCATION
2113 or SET/QRA), together with the current azimuth and elevation.
2115 If all else fails it will show the civil dawn and dusk times for
2116 the node that you are connected to.
2121 SH/GRAYLINE G1TLH W5UN
2123 You can also use this command to see into the past or the future, so
2124 if you want to see yesterday's times then do:-
2128 or in three days time:-
2132 Upto 366 days can be checked both in the past and in the future.
2134 Please note that the times are given as the UT times of the requested
2137 === 0^SHOW/HFSTATS [days] [date]^Show the HF DX Statistics
2138 Show the HF DX spots breakdown by band for the last <days> no of days
2139 (default is 31), starting from a <date> (default: today).
2141 === 0^SHOW/HFTABLE [days] [date] [prefix ...]^Show the HF DX Spotter Table
2142 Show the HF DX Spotter table for the list of prefixes for the last
2143 <days> no of days (default is 31), starting from a <date> (default: today).
2145 If there are no prefixes then it will show the table for your country.
2147 Remember that some countries have more than one "DXCC country" in them
2148 (eg G :-), to show them (assuming you are not in G already which is
2149 specially treated in the code) you must list all the relevant prefixes
2151 sh/hftable g gm gd gi gj gw gu
2153 Note that the prefixes are converted into country codes so you don't have
2154 to list all possible prefixes for each country.
2156 If you want more or less days than the default simply include the
2157 number you require:-
2161 If you want to start at a different day, simply add the date in some
2164 sh/hftable 2 25nov02
2165 sh/hftable 2 25-nov-02
2167 sh/hftable 2 25/11/02
2169 This will show the stats for your DXCC for that CQWW contest weekend.
2171 You can specify either prefixes or full callsigns (so you can see how you
2172 did against all your mates). You can also say 'all' which will then print
2173 the worldwide statistics.
2177 === 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
2178 This command shows the hop counts set up for a node. You can specify
2179 which category you want to see. If you leave the category out then
2180 all the categories will be listed.
2182 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
2184 === 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
2186 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
2187 This command outputs a short section of the system log. On its own
2188 it will output a general logfile. With the optional callsign it will
2189 show output from the log associated with that callsign.
2191 === 0^SHOW/MOON [ndays] [<prefix>|<callsign>]^Show Moon rise and set times
2192 Show the Moon rise and set times for a (list of) prefixes or callsigns,
2193 together with the azimuth and elevation of the sun currently at those
2196 If you don't specify any prefixes or callsigns, it will show the times for
2197 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2198 together with the current azimuth and elevation.
2200 In addition, it will show the illuminated fraction of the moons disk.
2202 If all else fails it will show the Moonrise and set times for the node
2203 that you are connected to.
2210 You can also use this command to see into the past or the future, so
2211 if you want to see yesterday's times then do:-
2215 or in three days time:-
2219 Upto 366 days can be checked both in the past and in the future.
2221 Please note that the rise and set times are given as the UT times of rise and
2222 set on the requested UT day.
2224 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
2225 This command allow you to estimate the likelihood of you contacting
2226 a station with the prefix you have specified. The output assumes a modest
2227 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
2229 The result predicts the most likely operating frequencies and signal
2230 levels for high frequency (shortwave) radio propagation paths on
2231 specified days of the year and hours of the day. It is most useful for
2232 paths between 250 km and 6000 km, but can be used with reduced accuracy
2233 for paths shorter or longer than this.
2235 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2236 used to predict the MUF given the predicted flux, day of the year,
2237 hour of the day and geographic coordinates of the transmitter and
2238 receiver. This routine is reasonably accurate for the purposes here,
2239 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2240 than the programs used by major shortwave broadcasting organizations,
2241 such as the Voice of America.
2243 The command will display some header information detailing its
2244 assumptions, together with the locations, latitude and longitudes and
2245 bearings. It will then show UTC (UT), local time at the other end
2246 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2247 (Zen) and the likely signal strengths. Then for each frequency for which
2248 the system thinks there is a likelihood of a circuit it prints a value.
2250 The value is currently a likely S meter reading based on the conventional
2251 6dB / S point scale. If the value has a '+' appended it means that it is
2252 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
2253 there is likely to be much fading and by an 's' that the signal is likely
2256 By default SHOW/MUF will show the next two hours worth of data. You
2257 can specify anything up to 24 hours worth of data by appending the no of
2258 hours required after the prefix. For example:-
2264 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2265 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2266 Location Lat / Long Azim
2267 East Dereham, Norfolk 52 41 N 0 57 E 47
2268 United-States-W 43 0 N 87 54 W 299
2269 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2270 18 23 11.5 -35 mS0+ mS2 S3
2271 19 0 11.2 -41 mS0+ mS2 S3
2273 indicating that you will have weak, fading circuits on top band and
2274 80m but usable signals on 40m (about S3).
2280 will get you the above display, but with the next 24 hours worth of
2286 Gives you an estimate of the long path propagation characterics. It
2287 should be noted that the figures will probably not be very useful, nor
2288 terrible accurate, but it is included for completeness.
2290 === 0^SHOW/MYDX^Show the DX data filtered with your spot filter.
2291 SHOW/DX potentially shows all the spots available in the system. Using
2292 SHOW/MYDX will, instead, filter the availble spots using any spot filter
2293 that you have set, first.
2295 This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
2296 you to customise the spots that you receive.
2298 So if you have said: ACC/SPOT on hf
2300 Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
2301 options on SH/DX can still be used.
2303 === 0^SHOW/NEWCONFIGURATION [<node>]^Show all the nodes and users visible
2304 This command allows you to see all the users that can be seen
2305 and the nodes to which they are connected.
2307 This command produces essentially the same information as
2308 SHOW/CONFIGURATION except that it shows all the duplication of
2309 any routes that might be present It also uses a different format
2310 which may not take up quite as much space if you don't have any
2313 BE WARNED: the list that is returned can be VERY long
2315 === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
2316 Show all the nodes connected to this node in the new format.
2318 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
2319 Show the type and version (if connected) of the nodes specified on the
2320 command line. If no callsigns are specified then a sorted list of all
2321 the non-user callsigns known to the system will be displayed.
2323 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
2324 This command takes the <callsign> (which can be a full or partial
2325 callsign or a prefix), looks up which internal country number
2326 it is and then displays all the relevant prefixes for that country
2327 together with the internal country no, the CQ and ITU regions.
2331 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
2332 Show the name and location where every program module was load from. This
2333 is useful for checking where you think you have loaded a .pm file from.
2335 === 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
2336 === 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
2337 This is a multipurpose command that allows you either to calculate the
2338 distance and bearing between two locators or (if only one locator is
2339 given on the command line) the distance and beraing from your station
2340 to the locator. For example:-
2345 The first example will show the distance and bearing to the locator from
2346 yourself, the second example will calculate the distance and bearing from
2347 the first locator to the second. You can use 4 or 6 character locators.
2349 It is also possible to convert a latitude and longitude to a locator by
2350 using this command with a latitude and longitude as an argument, for
2353 SH/QRA 52 41 N 0 58 E
2355 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
2356 This command queries the QRZ callbook server on the internet
2357 and returns any information available for that callsign. This service
2358 is provided for users of this software by http://www.qrz.com
2360 See also SHOW/WM7D for an alternative.
2362 === 0^SHOW/DXQSL <callsign>^Show any QSL info gathered from spots
2363 The node collects information from the comment fields in spots (things
2364 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
2366 This command allows you to interrogate that database and if the callsign
2367 is found will display the manager(s) that people have spotted. This
2368 information is NOT reliable, but it is normally reasonably accurate if
2369 it is spotted enough times.
2375 You can check the raw input spots yourself with:-
2379 This gives you more background information.
2381 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
2383 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
2384 This command allows you to see to which node the callsigns specified are
2385 connected. It is a sort of inverse sh/config.
2389 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
2390 Show the tracking data from your location to the satellite of your choice
2391 from now on for the next few hours.
2393 If you use this command without a satellite name it will display a list
2394 of all the satellites known currently to the system.
2396 If you give a name then you can obtain tracking data of all the passes
2397 that start and finish 5 degrees below the horizon. As default it will
2398 give information for the next three hours for every five minute period.
2400 You can alter the number of hours and the step size, within certain
2403 Each pass in a period is separated with a row of '-----' characters
2408 SH/SAT FENGYUN1 12 2
2410 === 6^SHOW/STARTUP <call>^View a user startup script
2411 === 0^SHOW/STARTUP^View your own startup script
2412 View the contents of a startup script created with SET/STARTUP.
2414 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
2415 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
2416 Show the information known about a callsign and whether (and where)
2417 that callsign is connected to the cluster.
2421 If no callsign is given then show the information for yourself.
2423 === 0^SHOW/SUN [ndays] [<prefix>|<callsign>]^Show sun rise and set times
2424 Show the sun rise and set times for a (list of) prefixes or callsigns,
2425 together with the azimuth and elevation of the sun currently at those
2428 If you don't specify any prefixes or callsigns, it will show the times for
2429 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2430 together with the current azimuth and elevation.
2432 If all else fails it will show the sunrise and set times for the node
2433 that you are connected to.
2438 SH/SUN G1TLH K9CW ZS
2440 You can also use this command to see into the past or the future, so
2441 if you want to see yesterday's times then do:-
2445 or in three days time:-
2449 Upto 366 days can be checked both in the past and in the future.
2451 Please note that the rise and set times are given as the UT times of rise
2452 and set on the requested UT day.
2454 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
2455 If no prefixes or callsigns are given then this command returns the local
2456 time and UTC as the computer has it right now. If you give some prefixes
2457 then it will show UTC and UTC + the local offset (not including DST) at
2458 the prefixes or callsigns that you specify.
2460 === 0^SHOW/USDB [call ..]^Show information held on the FCC Call database
2461 Show the City and State of a Callsign held on the FCC database if
2462 his is being run on this system, eg:-
2466 === 0^SHOW/VHFSTATS [days] [date]^Show the VHF DX Statistics
2467 Show the VHF DX spots breakdown by band for the last
2468 <days> no of days (default is 31), starting from a date (default: today).
2470 === 0^SHOW/VHFTABLE [days] [date] [prefix ...]^Show the VHF DX Spotter Table
2471 Show the VHF DX Spotter table for the list of prefixes for the last
2472 <days> no of days (default is 31), starting from a date (default: today).
2474 If there are no prefixes then it will show the table for your country.
2476 Remember that some countries have more than one "DXCC country" in them
2477 (eg G :-), to show them (assuming you are not in G already which is
2478 specially treated in the code) you must list all the relevant prefixes
2480 sh/vhftable g gm gd gi gj gw gu
2482 Note that the prefixes are converted into country codes so you don't have
2483 to list all possible prefixes for each country.
2485 If you want more or less days than the default simply include the
2486 number you require:-
2490 If you want to start at a different day, simply add the date in some
2493 sh/vhftable 2 25nov02
2494 sh/vhftable 2 25-nov-02
2495 sh/vhftable 2 021125
2496 sh/vhftable 2 25/11/02
2498 This will show the stats for your DXCC for that CQWW contest weekend.
2500 You can specify either prefixes or full callsigns (so you can see how you
2501 did against all your mates). You can also say 'all' which will then print
2502 the worldwide statistics.
2506 === 0^SHOW/WCY^Show last 10 WCY broadcasts
2507 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
2508 Display the most recent WCY information that has been received by the system
2510 === 0^SHOW/WM7D <callsign>^Show callbook details on a US callsigns
2511 This command queries the WM7D callbook server on the internet
2512 and returns any information available for that US callsign. This service
2513 is provided for users of this software by http://www.wm7d.net.
2517 === 0^SHOW/WWV^Show last 10 WWV broadcasts
2518 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
2519 Display the most recent WWV information that has been received by the system
2521 === 5^SHUTDOWN^Shutdown the cluster
2522 Shutdown the cluster and disconnect all the users
2524 === 9^SPOOF <call> <command>^Do a command as though you are another user
2525 This command is provided so that sysops can set a user's parameters without
2526 me having to write a special 'sysop' version for every user command. It
2527 allows you to pretend that you are doing the command as the user you specify.
2531 SPOOF G1TLH set/name Dirk
2532 SPOOF G1TLH set/qra JO02LQ
2534 === 5^STAT/DB <dbname>^Show the status of a database
2535 Show the internal status of a database descriptor.
2537 Depending on your privilege level you will see more or less information.
2538 This command is unlikely to be of much use to anyone other than a sysop.
2540 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
2541 Show the internal status of the channel object either for the channel that
2542 you are on or else for the callsign that you asked for.
2544 Only the fields that are defined (in perl term) will be displayed.
2546 === 1^STAT/MSG^Show the status of the message system
2547 === 1^STAT/MSG <msgno>^Show the status of a message
2548 This command shows the internal status of a message and includes information
2549 such as to whom it has been forwarded, its size, origin etc etc.
2551 If no message number is given then the status of the message system is
2554 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
2555 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
2557 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
2558 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
2560 === 5^STAT/USER [<callsign>]^Show the full status of a user
2561 Shows the full contents of a user record including all the secret flags
2564 Only the fields that are defined (in perl term) will be displayed.
2566 === 0^SYSOP^Regain your privileges if you login remotely
2567 The system automatically reduces your privilege level to that of a
2568 normal user if you login in remotely. This command allows you to
2569 regain your normal privilege level. It uses the normal system: five
2570 numbers are returned that are indexes into the character array that is
2571 your assigned password (see SET/PASSWORD). The indexes start from
2574 You are expected to return a string which contains the characters
2575 required in the correct order. You may intersperse those characters
2576 with others to obscure your reply for any watchers. For example (and
2577 these values are for explanation :-):
2579 password = 012345678901234567890123456789
2583 aa2bbbb0ccc5ddd7xxx3n
2587 They will all match. If there is no password you will still be offered
2588 numbers but nothing will happen when you input a string. Any match is
2591 === 0^TALK <call> [<text>]^Send a text message to another station
2592 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
2593 Send a short message to any other station that is visible on the cluster
2594 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2595 command, they don't have to be connected locally.
2597 The second form of TALK is used when other cluster nodes are connected
2598 with restricted information. This usually means that they don't send
2599 the user information usually associated with logging on and off the cluster.
2601 If you know that G3JNB is likely to be present on GB7TLH, but you can only
2602 see GB7TLH in the SH/C list but with no users, then you would use the
2603 second form of the talk message.
2605 If you want to have a ragchew with someone you can leave the text message
2606 out and the system will go into 'Talk' mode. What this means is that a
2607 short message is sent to the recipient telling them that you are in a
2608 'Talking' frame of mind and then you just type - everything you send will
2609 go to the station that you asked for.
2611 All the usual announcements, spots and so on will still come out on your
2614 If you want to do something (such as send a spot) you preceed the normal
2615 command with a '/' character, eg:-
2617 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2620 To leave talk mode type:
2624 If you are in 'Talk' mode, there is an extention to the '/' command which
2625 allows you to send the output to all the people you are talking to. You do
2626 with the '//' command. For example:-
2630 will send the hftable as you have it to all the people you are currently
2633 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
2634 Type out the contents of a file in a filearea. So, for example, in
2635 filearea 'bulletins' you want to look at file 'arld051' you would
2637 TYPE bulletins/arld051
2639 See also SHOW/FILES to see what fileareas are available and a
2642 === 0^WHO^Show who is physically connected
2643 This is a quick listing that shows which callsigns are connected and
2644 what sort of connection they have
2646 === 0^WX <text>^Send a weather message to local users
2647 === 0^WX FULL <text>^Send a weather message to all cluster users
2648 === 5^WX SYSOP <text>^Send a weather message to other clusters only
2649 Weather messages can sometimes be useful if you are experiencing an extreme
2650 that may indicate enhanced conditions