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 === 5^CREATE/USER <callsign> ...^Create this user from the User Database
410 This command will create one or more new users. None of the fields
411 like name, qth etc will be filled in. It is just a new entry in the user
412 database to which one can add more stuff like SET/PASSWORD or by SPOOF.
414 === 9^DELETE/USDB <callsign> ...^Delete this user from the US State Database
415 This command will completely remove a one or more callsigns
416 from the US States database.
418 There is NO SECOND CHANCE.
420 It goes without saying that you should use this command CAREFULLY!
422 Note that these callsign may be re-instated by any weekly updates from
425 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
426 This command will completely remove a one or more users from the database.
428 There is NO SECOND CHANCE.
430 It goes without saying that you should use this command CAREFULLY!
432 === 0^DBAVAIL^Show a list of all the Databases in the system
433 Title says it all really, this command lists all the databases defined
434 in the system. It is also aliased to SHOW/COMMAND.
436 === 9^DBCREATE <name>^Create a database entry
437 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
438 === 9^DBCREATE <name> remote <node>^Create a remote database entry
439 === 9^DBCREATE <name> cmd <dxspider command>^make a local command available as a DB
440 DBCREATE allows you to define a database in the system. It doesn't actually
441 create anything, just defines it.
443 The databases that are created are simple DB_File hash databases, they are
444 therefore already 'indexed'.
446 You can define a local database with the first form of the command eg:
450 You can also chain databases with the addition of the 'chain' keyword.
451 This will search each database one after the other. A typical example
454 DBCREATE sdx_qsl chain sql_ad
456 No checking is done to see if the any of the chained databases exist, in
457 fact it is usually better to do the above staement first then do each of
458 the chained databases.
460 Databases can exist offsite. To define a database that lives on another
463 DBCREATE buckmaster remote gb7dxc
465 Remote databases cannot be chained; however, the last database in a
466 a chain can be a remote database eg:
468 DBCREATE qsl chain gb7dxc
470 To see what databases have been defined do:
472 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
474 It would be normal for you to add an entry into your local Aliases file
475 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
476 need to add a line like:-
481 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
490 to work as they may be used to.
492 You can also make local commands available as 'pseudo' databases. You
493 can therefore make spider special commands available as a database. I
494 imagine that this will be primarily useful for remote access from
495 legacy nodes. For example:-
497 DBCREATE dxqsl cmd show/dxqsl
499 You also use one of these databases in a chain. This may be useful
502 See DBIMPORT for the importing of existing AK1A format data to databases.
503 See DXEXPORT for how to export an AK1A data in a form able to be imported.
504 See DBSHOW for generic database enquiry
507 === 9^DBEXPORT <dbname> <filename>^Export an AK1A data to a file
508 Sometimes one needs to export the data from an existing database file,
509 maybe for a backup or to send to another node.
511 DBEXPORT oblast /tmp/OBLAST.FUL
513 will export the OBLAST database to /tmp/OBLAST.FUL
515 There is no protection, it is up to you not to overwrite a file that
518 See DBIMPORT for the importing of existing AK1A format data to databases.
520 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
521 If you want to import or update data in bulk to a database you can use
522 this command. It will either create or update entries into an existing
523 database. For example:-
525 DBIMPORT oblast /tmp/OBLAST.FUL
527 will import the standard OBLAST database that comes with AK1A into the
528 oblast database held locally.
530 See DBEXPORT for how to export an AK1A database
532 === 9^DBREMOVE <dbname>^Delete a database
533 DBREMOVE will completely remove a database entry and also delete any data
534 file that is associated with it.
536 There is no warning, no comeback, no safety net.
542 will remove the oblast database from the system and it will also remove
543 the associated datafile.
547 There is no warning, no comeback, no safety net.
549 You have been warned.
551 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
552 This is the generic user interface to the database to the database system.
553 It is expected that the sysop will add an entry to the local Aliases file
554 so that users can use the more familiar AK1A style of enquiry such as:
558 but if he hasn't and the database really does exist (use DBAVAIL or
559 SHOW/COMMAND to find out) you can do the same thing with:
563 === 9^DEBUG^Set the cluster program into debug mode
564 Executing this command will only have an effect if you are running the cluster
569 It will interrupt the cluster just after the debug command has finished.
571 === 0^DIRECTORY^List messages
572 === 0^DIRECTORY ALL^List all messages
573 === 0^DIRECTORY OWN^List your own messages
574 === 0^DIRECTORY NEW^List all new messages
575 === 0^DIRECTORY TO <call>^List all messages to <call>
576 === 0^DIRECTORY FROM <call>^List all messages from <call>
577 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
578 === 0^DIRECTORY <nn>^List last <nn> messages
579 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
580 List the messages in the messages directory.
582 If there is a 'p' one space after the message number then it is a
583 personal message. If there is a '-' between the message number and the
584 'p' then this indicates that the message has been read.
586 You can use shell escape characters such as '*' and '?' in the <call>
589 You can combine some of the various directory commands together eg:-
593 DIR SUBJECT IOTA 200-250
595 You can abbreviate all the commands to one letter and use ak1a syntax:-
601 Sysops can see all users' messages.
603 === 8^DISCONNECT <call> [<call> ...]^Disconnect user(s) or node(s)
604 Disconnect any <call> connected locally.
606 In addition you can disconnect all users (except yourself) with
614 or everything (except yourself) with
618 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
619 This is how you send a DX Spot to other users. You can, in fact, now
620 enter the <freq> and the <call> either way round.
626 will all give the same result. You can add some remarks to the end
627 of the command and they will be added to the spot.
629 DX FR0G 144600 this is a test
631 You can credit someone else by saying:-
633 DX by G1TLH FR0G 144.600 he isn't on the cluster
635 The <freq> is compared against the available bands set up in the
636 cluster. See SHOW/BANDS for more information.
638 === 9^DXQSL_EXPORT <filename>^Export SH/DXSQL information to a file
639 The SHOW/DXQSL command shows any QSL managers that have been extracted
640 from comments on a DX spot.
642 Use this command to export the current state of the information to
643 a CSV style text file. For example:
645 DXQSL_EXPORT /tmp/qsl.csv
647 NOTE: this command will overwrite any file that you have write
650 See also DXQSL_IMPORT to import one of these files.
652 === 9^DXQSL_IMPORT <filename>^Import SH/DXSQL information from a file
653 The SHOW/DXQSL command shows any QSL managers that have been extracted
654 from comments on a DX spot.
656 Use this command to restore a file created by the DXSQL_EXPORT command.
659 DXQSL_IMPORT /tmp/qsl.csv
661 The data in this file will UPDATE any information that may already be
662 present. This may not be what you want. To make the data the same as
663 the import file then you must:
666 * remove /spider/data/qsl.v1
671 Preferably before too many DX spots with qsl manager info come in.
673 === 0^ECHO <line>^Echo the line to the output
674 This command is useful in scripts and so forth for printing the
675 line that you give to the command to the output. You can use this
676 in user_default scripts and the SAVE command for titling and so forth
678 The script will interpret certain standard "escape" sequences as follows:-
680 \t - becomes a TAB character (0x09 in ascii)
681 \a - becomes a BEEP character (0x07 in ascii)
682 \n - prints a new line
684 So the following example:-
686 echo GB7DJK is a dxcluster
690 GB7DJK is a dxcluster
692 on the output. You don't need a \n on the end of the line you want to send.
694 A more complex example:-
696 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
706 === 9^EXPORT <msgno> <filename>^Export a message to a file
707 Export a message to a file. This command can only be executed on a local
708 console with a fully privileged user. The file produced will be in a form
709 ready to be imported back into the cluster by placing it in the import
710 directory (/spider/msg/import).
712 This command cannot overwrite an existing file. This is to provide some
713 measure of security. Any files written will owned by the same user as the
714 main cluster, otherwise you can put the new files anywhere the cluster can
715 access. For example:-
719 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
720 Export the users database to a file in ascii format. If no filename
721 is given then it will export the file to /spider/data/user_asc.
723 If the file already exists it will be renamed to <filename>.o. In fact
724 up to 5 generations of the file can be kept each one with an extra 'o' on the
727 BE WARNED: this will write to any file you have write access to. No check is
728 made on the filename (if any) that you specify.
730 === 0^FILTERING...^Filtering things in DXSpider
731 There are a number of things you can filter in the DXSpider system. They
732 all use the same general mechanism.
734 In general terms you can create a 'reject' or an 'accept' filter which
735 can have up to 10 lines in it. You do this using, for example:-
740 where ..... are the specific commands for that type of filter. There
741 are filters for spots, wwv, announce, wcy and (for sysops)
742 connects. See each different accept or reject command reference for
745 There is also a command to clear out one or more lines in a filter and
746 one to show you what you have set. They are:-
755 There is clear/xxxx command for each type of filter.
757 For now we are going to use spots for the examples, but you can apply
758 the principles to all types of filter.
760 There are two main types of filter 'accept' or 'reject'; which you use
761 depends entirely on how you look at the world and what is least
762 writing to achieve what you want. Each filter has 10 lines (of any
763 length) which are tried in order. If a line matches then the action
764 you have specified is taken (ie reject means ignore it and accept
767 The important thing to remember is that if you specify a 'reject'
768 filter (all the lines in it say 'reject/spots' (for instance)) then if
769 a spot comes in that doesn't match any of the lines then you will get
770 it BUT if you specify an 'accept' filter then any spots that don't
771 match are dumped. For example if I have a one line accept filter:-
773 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
775 then automatically you will ONLY get VHF spots from or to CQ zones 14
776 15 and 16. If you set a reject filter like:
778 reject/spots on hf/cw
780 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
781 and will work it even on CW then you could say:-
783 reject/spots on hf/cw and not info iota
785 But in that case you might only be interested in iota and say:-
787 accept/spots not on hf/cw or info iota
789 which is exactly the same. You should choose one or the other until
790 you are confortable with the way it works. Yes, you can mix them
791 (actually you can have an accept AND a reject on the same line) but
792 don't try this at home until you can analyse the results that you get
793 without ringing up the sysop for help.
795 Another useful addition now is filtering by US state
797 accept/spots by_state VA,NH,RI,ME
799 You can arrange your filter lines into logical units, either for your
800 own understanding or simply convenience. I have one set frequently:-
802 reject/spots 1 on hf/cw
803 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
805 What this does is to ignore all HF CW spots (being a class B I can't
806 read any CW and couldn't possibly be interested in HF :-) and also
807 rejects any spots on VHF which don't either originate or spot someone
810 This is an exmaple where you would use the line number (1 and 2 in
811 this case), if you leave the digit out, the system assumes '1'. Digits
812 '0'-'9' are available.
814 You can leave the word 'and' out if you want, it is implied. You can
815 use any number of brackets to make the 'expression' as you want
816 it. There are things called precedence rules working here which mean
817 that you will NEED brackets in a situation like line 2 because,
818 without it, will assume:-
820 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
822 annoying, but that is the way it is. If you use OR - use
823 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
826 If you want to alter your filter you can just redefine one or more
827 lines of it or clear out one line. For example:-
829 reject/spots 1 on hf/ssb
835 To remove the filter in its entirty:-
839 There are similar CLEAR commands for the other filters:-
847 Once you are happy with the results you get, you may like to experiment.
849 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
850 can be written with a mixed filter, eg:
854 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
856 each filter slot actually has a 'reject' slot and an 'accept'
857 slot. The reject slot is executed BEFORE the accept slot.
859 It was mentioned earlier that after a reject test that doesn't match,
860 the default for following tests is 'accept', the reverse is true for
861 'accept'. In the example what happens is that the reject is executed
862 first, any non hf/cw spot is passed to the accept line, which lets
863 thru everything else on HF.
865 The next filter line lets through just VHF/UHF spots from EU.
867 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
868 This command sends all the latitude and longitude information that your
869 cluster is holding against callsigns. One advantage of recieving this
870 information is that more locator information is held by you. This
871 means that more locators are given on the DX line assuming you have
872 SET/DXGRID enabled. This could be a LOT of information though, so
873 it is not recommended on slow links.
875 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
876 This command sends out any information held in the user file which can
877 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
878 and Homenode. PC41s are only sent for the information that is available.
880 === 0^HELP^The HELP Command
881 HELP is available for a number of commands. The syntax is:-
885 Where <cmd> is the name of the command you want help on.
887 All commands can be abbreviated, so SHOW/DX can be abbreviated
888 to SH/DX, ANNOUNCE can be shortened to AN and so on.
890 Look at the APROPOS <string> command which will search the help database
891 for the <string> you specify and give you a list of likely commands
892 to look at with HELP.
894 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
895 This command attempts to re-initialise a link to a (usually) AK1A node
896 that has got confused, usually by a protocol loop of some kind. It may
897 work - but you usually will be better off simply disconnecting it (or
898 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
901 Best of luck - you will need it.
903 === 9^DEMONSTRATE <call> <command>^Demonstrate a command to another user
904 This command is provided so that sysops can demonstrate commands to
905 other users. It runs a command as though that user had typed it in and
906 then sends the output to that user, together with the command that
909 DEMO g7brn sh/dx iota oc209
912 Note that this command is similar to SPOOF and will have the same side
913 effects. Commands are run at the privilege of the user which is being
916 === 0^JOIN <group>^Join a chat or conference group
917 JOIN allows you to join a network wide conference group. To join a
918 group (called FOC in this case) type:-
922 See also CHAT, LEAVE, SHOW/CHAT
924 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
925 === 0^KILL <from msgno>-<to msgno>^Delete a range of messages
926 === 0^KILL from <regex>^Delete messages FROM a callsign or pattern
927 === 0^KILL to <regex>^Delete messages TO a callsign or pattern
928 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
929 Delete a message from the local system. You will only be able to
930 delete messages that you have originated or been sent (unless you are
935 Will delete all the messages that you own between msgnos 1234 and 1255.
939 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
943 will delete all messages to g1tlh.
947 will delete a message (usually a 'bulletin') from the whole cluster system.
949 This uses the subject field, so any messages that have exactly the
950 same subject will be deleted. Beware!
952 === 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
953 Deleting a message using the normal KILL commands only marks that message
954 for deletion. The actual deletion only happens later (usually two days later).
956 The KILL EXPUNGE command causes the message to be truly deleted more or less
959 It otherwise is used in the same way as the KILL command.
961 === 0^LEAVE <group>^Leave a chat or conference group
962 LEAVE allows you to leave a network wide conference group. To leave a
963 group (called FOC in this case) type:-
967 See also CHAT, JOIN, SHOW/CHAT
969 === 0^LINKS^Show which nodes is physically connected
970 This is a quick listing that shows which links are connected and
971 some information about them. See WHO for a list of all connections.
973 === 9^LOAD/ALIASES^Reload the command alias table
974 Reload the /spider/cmd/Aliases file after you have editted it. You
975 will need to do this if you change this file whilst the cluster is
976 running in order for the changes to take effect.
978 === 9^LOAD/BANDS^Reload the band limits table
979 Reload the /spider/data/bands.pl file if you have changed it manually whilst
980 the cluster is running.
982 === 9^LOAD/BADMSG^Reload the bad msg table
983 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
984 the cluster is running. This table contains a number of perl regular
985 expressions which are searched for in the fields targetted of each message.
986 If any of them match then that message is immediately deleted on receipt.
988 === 9^LOAD/BADWORDS^Reload the bad words table
989 Reload the /spider/data/badwords file if you have changed it manually whilst
990 the cluster is running. This file contains a list of words which, if found
991 on certain text portions of PC protocol, will cause those protocol frames
992 to be rejected. It will all put out a message if any of these words are
993 used on the announce, dx and talk commands. The words can be one or
994 more on a line, lines starting with '#' are ignored.
996 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
997 Normally, if you change a command file in the cmd or local_cmd tree it
998 will automatially be picked up by the cluster program. Sometimes it
999 can get confused if you are doing a lot of moving commands about or
1000 delete a command in the local_cmd tree and want to use the normal one
1001 again. Execute this command to reset everything back to the state it
1002 was just after a cluster restart. To see what is in the command cache
1005 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
1006 Reload the /spider/msg/forward.pl file if you have changed it
1007 manually whilst the cluster is running.
1009 === 5^LOAD/KEPS^Load new keps data
1010 === 5^LOAD/KEPS [nn]^Load new keps data from message
1011 If there is no message number then reload the current Keps data from
1012 the Keps.pm data file. You create this file by running
1014 /spider/perl/convkeps.pl <filename>
1016 on a file containing NASA 2 line keps as a message issued by AMSAT.
1018 If there is a message number, then it will take the message, run
1019 convkeps.pl on it and then load the data, all in one step.
1021 These messages are sent to ALL by GB7DJK (and others) from time to time.
1023 === 9^LOAD/MESSAGES^Reload the system messages file
1024 If you change the /spider/perl/Messages file (usually whilst
1025 fiddling/writing new commands) you can have them take effect during a
1026 cluster session by executing this command. You need to do this if get
1029 unknown message 'xxxx' in lang 'en'
1031 === 9^LOAD/PREFIXES^Reload the prefix table
1032 Reload the /spider/data/prefix_data.pl file if you have changed it
1033 manually whilst the cluster is running.
1035 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
1036 MERGE allows you to bring your spot and wwv database up to date. By default
1037 it will request the last 10 spots and 5 WWVs from the node you select. The
1038 node must be connected locally.
1040 You can request any number of spots or wwv and although they will be appended
1041 to your databases they will not duplicate any that have recently been added
1042 (the last 2 days for spots and last month for WWV data).
1044 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
1045 Alter message parameters like To, From, Subject, whether private or bulletin
1046 or return receipt (RR) is required or whether to keep this message from timing
1049 MSG TO <msgno> <call> - change TO callsign to <call>
1050 MSG FRom <msgno> <call> - change FROM callsign to <call>
1051 MSG PRrivate <msgno> - set private flag
1052 MSG NOPRrivate <msgno> - unset private flag
1053 MSG RR <msgno> - set RR flag
1054 MSG NORR <msgno> - unset RR flag
1055 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1056 MSG NOKEep <msgno> - unset the keep flag
1057 MSG SUbject <msgno> <new> - change the subject to <new>
1058 MSG WAittime <msgno> - remove any waitting time for this message
1059 MSG NOREad <msgno> - mark message as unread
1060 MSG REad <msgno> - mark message as read
1061 MSG QUeue - queue any outstanding bulletins
1062 MSG QUeue 1 - queue any outstanding private messages
1064 You can look at the status of a message by using:-
1068 This will display more information on the message than DIR does.
1070 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
1071 Send some arbitrary text to a locally connected callsign. No
1072 processing is done on the text. This command allows you to send PC
1073 Protocol to unstick things if problems arise (messages get stuck
1076 pc gb7djk PC33^GB7TLH^GB7DJK^400^
1078 pc G1TLH Try doing that properly!!!
1080 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
1081 You can get rid of any message to or originating from your callsign using
1082 this command. You can remove more than one message at a time.
1084 === 5^KILL <from>-<to>^Remove a range of messages from the system
1085 === 5^KILL FROM <call>^Remove all messages from a callsign
1086 === 5^KILL TO <call>^Remove all messages to a callsign
1087 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
1088 Remove this message from the entire cluster system as well as your node.
1091 As a sysop you can kill any message on the system.
1093 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
1094 Send any text you like to the callsign requested. This is used mainly to send
1095 PC protocol to connected nodes either for testing or to unstick things.
1097 You can also use in the same way as a talk command to a connected user but
1098 without any processing, added of "from <blah> to <blah" or whatever.
1100 === 1^PING <node call>^Check the link quality between nodes
1101 This command allows you to send a frame to another cluster node on
1102 the network and get a return frame. The time it takes to do this
1103 is a good indication of the quality of the link. The actual time
1104 it takes is output to the console in seconds.
1105 Any visible cluster node can be PINGed.
1107 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
1108 This command allows you to send nearly any command to another DX Cluster
1109 node that is connected to the system.
1111 Whether you get any output is dependant on a) whether the other system knows
1112 that the node callsign of this cluster is in fact a node b) whether the
1113 other system is allowing RCMDs from this node and c) whether you have
1114 permission to send this command at all.
1116 === 0^READ^Read the next unread personal message addressed to you
1117 === 0^READ <msgno>^Read the specified message
1118 You can read any messages that are sent as 'non-personal' and also any
1119 message either sent by or sent to your callsign.
1122 As a sysop you may read any message on the system
1124 === 0^REJECT^Set a filter to reject something
1125 Create a filter to reject something
1127 There are 2 types of filter, accept and reject. See HELP FILTERING for more
1130 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
1131 Create an 'reject this announce' line for a filter.
1133 A reject filter line means that if the announce matches this filter it is
1134 passed onto the user. See HELP FILTERING for more info. Please read this
1135 to understand how filters work - it will save a lot of grief later on.
1137 You can use any of the following things in this line:-
1139 info <string> eg: iota or qsl
1140 by <prefixes> eg: G,M,2
1142 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1143 origin_itu <prefixes or numbers> or: G,GM,GW
1144 origin_zone <prefixes or numbers>
1145 origin_state <states> eg: VA,NH,RI,ME
1146 by_dxcc <prefixes or numbers>
1147 by_itu <prefixes or numbers>
1148 by_zone <prefixes or numbers>
1149 by_state <states> eg: VA,NH,RI,ME
1151 wx 1 filter WX announces
1152 dest <prefixes> eg: 6MUK,WDX (distros)
1156 rej/ann by_zone 14,15,16 and not by G,M,2
1158 You can use the tag 'all' to reject everything eg:
1162 but this probably for advanced users...
1164 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
1165 This version allows a sysop to set a filter for a callsign as well as the
1166 default for nodes and users eg:-
1169 reject/ann input node_default by G,M,2
1170 reject/ann user_default by G,M,2
1172 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
1173 Create a 'reject this spot' line for a filter.
1175 A reject filter line means that if the spot matches this filter it is
1176 dumped (not passed on). See HELP FILTERING for more info. Please read this
1177 to understand how filters work - it will save a lot of grief later on.
1179 You can use any of the following things in this line:-
1181 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1182 on <range> same as 'freq'
1183 call <prefixes> eg: G,PA,HB9
1184 info <string> eg: iota or qsl
1186 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1187 call_itu <prefixes or numbers> or: G,GM,GW
1188 call_zone <prefixes or numbers>
1189 call_state <states> eg: VA,NH,RI,ME
1190 by_dxcc <prefixes or numbers>
1191 by_itu <prefixes or numbers>
1192 by_zone <prefixes or numbers>
1193 by_state <states> eg: VA,NH,RI,ME
1197 'call' means the callsign that has spotted 'by' whoever.
1199 For frequencies, you can use any of the band names defined in
1200 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1201 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1202 this is more efficient than saying simply: on HF (but don't get
1203 too hung up about that)
1208 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1210 You can use the tag 'all' to reject everything eg:
1214 but this probably for advanced users...
1216 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
1217 Create an 'reject this routing PC Protocol' line for a filter.
1219 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1220 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1221 read this to understand how filters work - it will save a lot of grief later on.
1223 You can use any of the following things in this line:-
1225 call <prefixes> the callsign of the thingy
1226 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1227 call_itu <prefixes or numbers> or: G,GM,GW
1228 call_zone <prefixes or numbers>
1229 call_state <states> eg: VA,NH,RI,ME
1230 origin <prefixes> really the interface it came in on
1231 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1232 origin_itu <prefixes or numbers> or: G,GM,GW
1233 origin_zone <prefixes or numbers>
1234 origin_state <states> eg: VA,NH,RI,ME
1238 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1240 You can use the tag 'all' to reject everything eg:
1242 rej/route all (equiv to [very] restricted mode)
1244 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
1246 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
1247 This version allows a sysop to set a filter for a callsign as well as the
1248 default for nodes and users eg:-
1250 reject/spot db0sue-7 1 by_zone 14,15,16
1251 reject/spot node_default all
1252 set/hops node_default 10
1254 reject/spot user_default by G,M,2
1256 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
1257 It is unlikely that you will want to do this, but if you do then you can
1258 filter on the following fields:-
1260 by <prefixes> eg: G,M,2
1262 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1263 origin_itu <prefixes or numbers> or: G,GM,GW
1264 origin_zone <prefixes or numbers>
1265 by_dxcc <prefixes or numbers>
1266 by_itu <prefixes or numbers>
1267 by_zone <prefixes or numbers>
1270 There are no examples because WCY Broadcasts only come from one place and
1271 you either want them or not (see UNSET/WCY if you don't want them).
1273 This command is really provided for future use.
1275 See HELP FILTER for information.
1277 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
1278 This version allows a sysop to set a filter for a callsign as well as the
1279 default for nodes and users eg:-
1281 reject/wcy gb7djk all
1283 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
1284 It is unlikely that you will want to do this, but if you do then you can
1285 filter on the following fields:-
1287 by <prefixes> eg: G,M,2
1289 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1290 origin_itu <prefixes or numbers> or: G,GM,GW
1291 origin_zone <prefixes or numbers>
1292 by_dxcc <prefixes or numbers>
1293 by_itu <prefixes or numbers>
1294 by_zone <prefixes or numbers>
1299 reject/wwv by_zone 14,15,16
1301 is probably the only useful thing to do (which will only show WWV broadcasts
1302 by stations in the US).
1304 See HELP FILTER for information.
1306 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
1307 This version allows a sysop to set a filter for a callsign as well as the
1308 default for nodes and users eg:-
1310 reject/wwv db0sue-7 1 by_zone 4
1311 reject/wwv node_default all
1313 reject/wwv user_default by W
1315 === 0^REPLY^Reply (privately) to the last message that you have read
1316 === 0^REPLY <msgno>^Reply (privately) to the specified message
1317 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1318 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1319 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1320 You can reply to a message and the subject will automatically have
1321 "Re:" inserted in front of it, if it isn't already present.
1323 You can also use all the extra qualifiers such as RR, PRIVATE,
1324 NOPRIVATE, B that you can use with the SEND command (see SEND
1325 for further details)
1327 === 9^SAVE [-d -t -a] <filename> "<cmd>" [...]^Save command output to a file
1328 This sysop only cammand allows you to save the output of one or more
1329 commands to a file. For example:-
1331 save /spider/packclus/dxstats show/dxstat
1333 will save the output of the normal command "show/dxstat" to the file
1334 "dxstats" in the files area.
1336 You can have some extra flags to the save which will either
1337 date stamp or time stamp or both the filename so:-
1339 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
1340 save -t /tmp/a <cmd> creates /tmp/a_2301Z
1341 save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
1343 The -a flag means append to the file instead of overwriting it.
1345 You can have more than one command on the line, to do this you MUST
1346 enclose each command in double quotes (") eg:-
1348 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
1352 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
1354 You can only write into places that the cluster has permission for (which
1355 is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
1356 need to create any directories you want to put stuff in beforehand as well.
1358 It is likely that you will want to run these commands in a crontab type
1359 situation. You would do that something like:-
1361 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
1363 Note that you still enclose each command with (") characters but you must
1364 enclose the entire save command in (') characters.
1366 Now in fact, this can be varied if you know what you are doing. See the
1367 admin manual for more details.
1369 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1370 === 0^SEND RR <call>^Send a message and ask for a read receipt
1371 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1372 === 0^SEND PRIVATE <call>^Send a personal message
1373 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1374 All the SEND commands will create a message which will be sent either to
1375 an individual callsign or to one of the 'bulletin' addresses.
1377 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1378 it will mark the message as personal and send it to the cluster node that
1379 that callsign is connected to. If the <call> you have specified is in fact
1380 a known bulletin category on your node (eg: ALL) then the message should
1381 automatically become a bulletin.
1383 You can have more than one callsign in all of the SEND commands.
1385 You can have multiple qualifiers so that you can have for example:-
1387 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1389 which should send a copy of message 123 to G1TLH and G0RDI and you will
1390 receive a read receipt when they have read the message.
1392 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1393 SP is an alias for SEND PRIVATE
1395 The system will ask you for a subject. Conventionally this should be
1396 no longer than 29 characters for compatibility. Most modern cluster
1397 software should accept more.
1399 You will now be prompted to start entering your text.
1401 You finish the message by entering '/EX' on a new line. For instance:
1408 If you have started a message and you don't want to keep it then you
1409 can abandon the message with '/ABORT' on a new line, like:-
1413 oh I just can't be bothered with this
1416 If you abort the message it will NOT be sent.
1418 When you are entering the text of your message, most normal output (such
1419 as DX announcements and so on are suppressed and stored for latter display
1420 (upto 20 such lines are stored, as new ones come along, so the oldest
1423 Also, you can enter normal commands commands (and get the output
1424 immediately) whilst in the middle of a message. You do this by typing
1425 the command preceeded by a '/' character on a new line, so:-
1427 /dx g1tlh 144010 strong signal
1429 Will issue a dx annoucement to the rest of the cluster.
1431 Also, you can add the output of a command to your message by preceeding
1432 the command with '//', thus :-
1436 This will show YOU the output from SH/VHFTABLE and also store it in the
1439 You can carry on with the message until you are ready to send it.
1441 === 6^SEND_CONFIG^Broadcast PC92 C records
1442 This is the PC92 equivalent of INIT. In that it will send out a new
1443 PC92 C record to all interfaces. This can be used to bring other nodes
1444 up to date quicker after a restart.
1446 === 0^SET/ADDRESS <your address>^Record your postal address
1448 === 9^SET/AGWENGINE^Enable the AGW Engine
1449 === 9^UNSET/AGWENGINE^Disable the AGW Engine
1450 These commands assume that /spider/local/AGWConnect.pm has been setup
1451 correctly and you wish to do some testing or otherwise want to alter
1452 the default state of your connection to the AGW Engine.
1454 === 9^SET/AGWMONITOR^Enable Monitoring on the AGW Engine
1455 === 9^UNSET/AGWMONITOR^Disable Monitoring on the AGW Engine
1457 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1458 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1460 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1461 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1462 The announce system on legacy cluster nodes is used as a talk
1463 substitute because the network is so poorly connected. If you:
1467 you will suppress several of these announces, you may miss the odd
1468 useful one as well, but you would probably miss them anyway in the
1469 welter of useless ones.
1473 allows you to see them again. This is the default.
1475 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1477 === 6^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1478 === 6^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1479 Setting a word as 'baddx' will prevent spots with that word in the
1480 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1481 further. They will not be displayed and they will not be sent onto
1484 The word must be written in full, no wild cards are allowed eg:-
1486 set/baddx FORSALE VIDEO FR0G
1488 To allow a word again, use the following command ...
1492 === 6^SET/BADNODE <call>..^Stop spots from this node being propagated
1493 === 6^UNSET/BADNODE <call>..^Allow spots from this node again
1494 Setting a callsign as a 'badnode' will prevent spots from that node
1495 going any further. They will not be displayed and they will not be
1496 sent onto other nodes.
1498 The call must be a full eg:-
1502 will stop anything from K1TTT. If you want SSIDs as well then you must
1503 enter them specifically.
1507 will allow spots from him again.
1509 Use with extreme care. This command may well be superceeded by FILTERing.
1511 === 6^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1512 === 6^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1513 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1514 going any further. They will not be displayed and they will not be
1515 sent onto other nodes.
1517 The call must be written in full, no wild cards are allowed eg:-
1519 set/badspotter VE2STN
1521 will stop anything from VE2STN. This command will automatically
1522 stop spots from this user, regardless of whether or which SSID
1523 he uses. DO NOT USE SSIDs in the callsign, just use the callsign
1526 unset/badspotter VE2STN
1528 will allow spots from him again.
1530 Use with extreme care. This command may well be superceded by FILTERing.
1532 This command will also stop TALK and ANNOUNCE/FULL from any user marked
1535 === 6^SET/BADWORD <word>..^Stop things with this word being propagated
1536 === 6^UNSET/BADWORD <word>..^Propagate things with this word again
1537 Setting a word as a 'badword' will prevent things like spots,
1538 announces or talks with this word in the the text part from going any
1539 further. They will not be displayed and they will not be sent onto
1542 The word must be written in full, no wild cards are allowed eg:-
1544 set/badword annihilate annihilated annihilation
1546 will stop anything with these words in the text.
1548 unset/badword annihilated
1550 will allow text with this word again.
1552 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1553 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1555 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1557 === 0^SET/BUDDY <call> [<call>..]^Add this call to my buddy list
1558 === 0^UNSET/BUDDY <call> [<call>..]^Remove this call from my buddy list
1559 A notification message
1560 is sent to you automatically if anybody on your buddy list logs in or
1561 out of any node in this cluster.
1563 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1565 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1566 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1567 You can choose to log several different levels. The levels are
1575 You can show what levels you are logging with SHOW/DEBUG
1577 === 0^SET/DX^Allow DX messages to come out on your terminal
1578 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1580 === 0^SET/DXCQ^Show CQ Zones on the end of DX announcements
1581 === 0^UNSET/DXCQ^Stop CQ Zones on the end of DX announcements
1582 Display both the Spotter's and the Spotted's CQ Zone on the end
1583 of a DX announcement (there is just enough room). Some user programs
1584 cannot cope with this. The Spotter's CQ is on the RHS of the
1585 time, the Spotted's CQ is on the LHS.
1587 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
1589 Do a STAT/USER to see which flags you have set if you are confused.
1591 === 0^SET/DXITU^Show ITU Zones on the end of DX announcements
1592 === 0^UNSET/DXITU^Stop ITU Zones on the end of DX announcements
1593 Display both the Spotter's and the Spotted's ITU Zone on the end
1594 of a DX announcement (there is just enough room). Some user programs
1595 cannot cope with this. The Spotter's ITU is on the RHS of the
1596 time, the Spotted's ITU is on the LHS.
1598 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
1600 Do a STAT/USER to see which flags you have set if you are confused.
1602 === 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
1603 === 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
1604 A standard feature which is enabled in version 1.43 and above is
1605 that if the spotter's grid square is known it is output on the end
1606 of a DX announcement (there is just enough room). Some user programs
1607 cannot cope with this. You can use this command to reset (or set)
1610 Conflicts with: SET/DXCQ, SET/DXITU
1612 Do a STAT/USER to see which flags you have set if you are confused.
1614 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1616 === 0^SET/ECHO^Make the cluster echo your input
1617 === 0^UNSET/ECHO^Stop the cluster echoing your input
1618 If you are connected via a telnet session, different implimentations
1619 of telnet handle echo differently depending on whether you are
1620 connected via port 23 or some other port. You can use this command
1621 to change the setting appropriately.
1623 The setting is stored in your user profile.
1625 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1627 === 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
1628 === 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
1629 If any personal messages come in for your callsign then you can use
1630 these commands to control whether they are forwarded onto your email
1631 address. To enable the forwarding do something like:-
1633 SET/EMAIL mike.tubby@somewhere.com
1635 You can have more than one email address (each one separated by a space).
1636 Emails are forwarded to all the email addresses you specify.
1638 You can disable forwarding by:-
1642 === 0^SET/HERE^Tell the system you are present at your terminal
1643 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1645 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1646 Tell the cluster system where you normally connect to. Any Messages sent
1647 to you will normally find their way there should you not be connected.
1651 === 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
1652 === 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
1653 Set the hop count for a particular type of broadcast for a node.
1655 This command allows you to set up special hop counts for a node
1656 for currently: announce, spots, wwv and wcy broadcasts.
1659 set/hops gb7djk ann 10
1660 set/hops gb7mbc spots 20
1662 Set SHOW/HOPS for information on what is already set. This command
1663 creates a filter and works in conjunction with the filter system.
1665 You can unset the hops with command UNSET/HOPS. For example:-
1667 unset/hops gb7djk ann
1668 unset/hops gb7mbc spots
1671 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1672 Connect a node to your system in such a way that you are a full protocol
1673 member of its network and can see all spots on it, but nothing either leaks
1674 out from it nor goes back into from the rest of the nodes connected to you.
1676 You can potentially connect several nodes in this way.
1678 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1679 Remove isolation from a node - SET/ISOLATE
1681 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1682 You can select the language that you want the cluster to use. Currently
1683 the languages available are en (English), de (German), es (Spanish),
1684 Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
1686 === 5^SET/LOCAL_NODE^Add node to the local_node group
1687 === 5^UNSET/LOCAL_NODE^Remove node from the local_node group
1688 The 'local_node' group is a group of nodes that you want a user
1689 to perceive as effectively one big node. At the moment, this extends
1690 only to announcing whenever a user is logging in or out of one of
1691 the nodes in the group (if those users have SET/LOGININFO).
1693 The local node group is as setup on this node. If you want the other
1694 nodes to also include this node and all the other nodes specified, then
1695 you must get those nodes to also run this command (or rcmd them to do
1698 In principle, therefore, each node determines its own local node group
1699 and these can overlap with other nodes' views.
1701 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1702 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1703 In order to get accurate headings and such like you must tell the system
1704 what your latitude and longitude is. If you have not yet done a SET/QRA
1705 then this command will set your QRA locator for you. For example:-
1706 SET/LOCATION 52 22 N 0 57 E
1708 === 0^SET/LOGININFO^Inform when a station logs in/out locally
1709 === 0^UNSET/LOGININFO^No longer inform when a station logs in/out locally
1711 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1712 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1714 === 8^SET/MAXCONNECT <value> [<call> ..]^Set max incoming connections for user/node
1715 Set the maximum no of connections (parents) an incoming user or node is
1716 allowed to have. If this incoming connection takes it over the separate
1717 limits for users and nodes (defaults: 3 and 8 respectively), then the
1718 connection is refused (with a polite message).
1720 The idea behind this to limit the number of copies of messages that
1721 are sent to users (and nodes). Nodes really don't need to have more than
1722 5 or 6 partners and users don't need more than two connections into the
1725 This check is only for INCOMING connections, no check is performed for
1726 outgoing connections.
1728 === 0^SET/NAME <your name>^Set your name
1729 Tell the system what your name is eg:-
1732 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1733 Tell the system that the call(s) are to be treated as AK1A cluster and
1734 fed PC Protocol rather normal user commands.
1736 === 8^SET/OBSCOUNT <count> <call>^Set the 'pump-up' obscelence PING counter
1737 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1738 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1739 counter which is decremented on every outgoing ping and then reset to
1740 the 'obscount' value on every incoming ping. The default value of this
1743 What this means is that a neighbouring node will be pinged twice at
1744 (default) 300 second intervals and if no reply has been heard just before
1745 what would be the third attempt, that node is disconnected.
1747 If a ping is heard then the obscount is reset to the full value. Using
1748 default values, if a node has not responded to a ping within 15 minutes,
1751 You can set this parameter between 1 and 9.
1753 It is STRONGLY recommended that you don't change the default.
1755 === 0^SET/PAGE <lines per page>^Set the lines per page
1756 Tell the system how many lines you wish on a page when the number of line
1757 of output from a command is more than this. The default is 20. Setting it
1758 explicitly to 0 will disable paging.
1762 The setting is stored in your user profile.
1764 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1765 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1766 in order to determine the rolling quality of the link and, in future, to
1767 affect routing decisions. The default interval is 300 secs or 5 minutes.
1769 You can use this command to set a different interval. Please don't.
1771 But if you do the value you enter is treated as minutes up 30 and seconds
1772 for numbers greater than that.
1774 This is used also to help determine when a link is down at the far end
1775 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1776 for more information.
1778 If you must change it (and it may be useful for internet connected nodes
1779 on dynamic IP addresses that go away after a set time of usage) the time
1780 can be specified as:-
1782 5 which if less than 30 is converted to minutes otherwise is
1783 taken as the no of seconds between pings.
1788 Please be aware that this causes traffic to occur on the link, setting
1789 this value too low may annoy your neighbours beyond the point of
1792 You can switch this off by setting it to 0.
1794 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1795 Set the privilege level on a callsign. The privilege levels that pertain
1796 to commands are as default:-
1798 1 - allow remote nodes normal user RCMDs
1799 5 - various privileged commands (including shutdown, but not disc-
1800 connect), the normal level for another node.
1801 8 - more privileged commands (including disconnect)
1802 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1804 If you are a sysop and you come in as a normal user on a remote connection
1805 your privilege will automatically be set to 0.
1807 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1808 You can use this command to 'protect' this session from unauthorised
1809 use. If you want to get your normal privilege back you will need to
1810 either logout and login again (if you are on a console) or use the
1813 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1814 The password for a user can only be set by a full sysop. The string
1815 can contain any characters.
1817 The way this field is used depends on context. If it is being used in
1818 the SYSOP command context then you are offered 5 random numbers and you
1819 have to supply the corresponding letters. This is now mainly for ax25
1822 If it is being used on incoming telnet connections then, if a password
1825 set/var $main::passwdreq = 1
1827 command is executed in the startup script, then a password prompt is
1828 given after the normal 'login: ' prompt.
1830 === 0^SET/PASSWORD^Set your own password
1831 This command only works for a 'telnet' user (currently). It will
1832 only work if you have a password already set. This initial password
1833 can only be set by the sysop.
1835 When you execute this command it will ask you for your old password,
1836 then ask you to type in your new password twice (to make sure you
1837 get it right). You may or may not see the data echoed on the screen
1838 as you type, depending on the type of telnet client you have.
1840 === 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
1841 This command allows the sysop to completely delete and remove a
1842 password for a user.
1844 === 0^SET/PROMPT <string>^Set your prompt to <string>
1845 === 0^UNSET/PROMPT^Set your prompt back to default
1846 This command will set your user prompt to the string that you
1847 say. The point of this command to enable a user to interface to programs
1848 that are looking for a specific prompt (or else you just want a different
1853 There are some substitutions that can be added to the prompt:
1855 %C - callsign [which will have ( and ) around it if not here]
1858 %M - cluster 'mycall'
1860 The standard prompt is defined as:
1862 SET/PROMPT %C de %M %D %T dxspider >
1864 UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to
1867 === 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
1868 === 0^SET/QRA <locator>^Set your QRA Grid locator
1869 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1870 done a SET/LOCATION then your latitude and longitude will be set roughly
1871 correctly (assuming your locator is correct ;-). For example:-
1874 === 0^SET/QTH <your qth>^Set your QTH
1875 Tell the system where you are. For example:-
1876 SET/QTH East Dereham, Norfolk
1878 === 9^SET/REGISTER <call> ...^Mark a user as registered
1879 === 9^UNSET/REGISTER <call> ...^Mark a user as not registered
1880 Registration is a concept that you can switch on by executing the
1882 set/var $main::regreq = 1
1884 command (usually in your startup file)
1886 If a user is NOT registered then, firstly, instead of the normal
1887 motd file (/spider/data/motd) being sent to the user at startup, the
1888 user is sent the motd_nor file instead. Secondly, the non registered
1889 user only has READ-ONLY access to the node. The non-registered user
1890 cannot use DX, ANN etc.
1892 The only exception to this is that a non-registered user can TALK or
1893 SEND messages to the sysop.
1895 === 6^SET/STARTUP <call>^Create a user startup script
1896 === 0^SET/STARTUP^Create your own startup script
1897 Create a startup script of DXSpider commands which will be executed
1898 everytime that you login into this node. You can only input the whole
1899 script afresh, it is not possible to 'edit' it. Inputting a new script is
1900 just like typing in a message using SEND. To finish inputting type: /EX
1901 on a newline, to abandon the script type: /ABORT.
1903 You may find the (curiously named) command BLANK useful to break
1904 up the output. If you simply want a blank line, it is easier to
1905 input one or more spaces and press the <return> key.
1907 See UNSET/STARTUP to remove a script.
1909 === 6^UNSET/STARTUP <call>^Remove a user startup script
1910 === 0^UNSET/STARTUP^Remove your own startup script
1911 You can remove your startup script with UNSET/STARTUP.
1913 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1914 Tell the system that the call(s) are to be treated as DXSpider node and
1915 fed new style DX Protocol rather normal user commands.
1917 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1918 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1920 === 9^SET/USDB <call> <state> <city>^add/update a US DB callsign
1921 This command allows you to add or alter a callsign in the US state
1922 database. Use with extreme caution. Anything you do here will be
1923 overwritten by any weekly updates that affect this callsign
1925 set/usdb g1tlh nh downtown rindge
1927 see also DELETE/USDB
1929 === 0^SET/USSTATE^Allow US State info on the end of DX announcements
1930 === 0^UNSET/USSTATE^Stop US State info on the end of DX announcements
1931 If the spotter's or spotted's US State is known it is output on the
1932 end of a DX announcement (there is just enough room).
1934 A spotter's state will appear on the RHS of the time (like
1935 SET/DXGRID) and the spotted's State will appear on the LHS of the
1936 time field. Any information found will override any locator
1937 information from SET/DXGRID.
1939 Some user programs cannot cope with this. You can use this command
1940 to reset (or set) this feature.
1942 Conflicts with: SET/DXCQ, SET/DXITU
1944 Do a STAT/USER to see which flags you have set if you are confused.
1946 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1947 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1949 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1950 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1952 === 0^SET/WX^Allow WX messages to come out on your terminal
1953 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1955 === 0^SHOW/ANNOUNCE [<n>][<from>-<to>][<call>] ...^Show log of announces
1956 Show announcements that have come in.
1958 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1959 Display all the bad dx callsigns in the system, see SET/BADDX
1960 for more information.
1962 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1963 Display all the bad node callsigns in the system, see SET/BADNODE
1964 for more information.
1966 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1967 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1968 for more information.
1970 === 1^SHOW/BADWORD^Show all the bad words in the system
1971 Display all the bad words in the system, see SET/BADWORD
1972 for more information.
1974 === 0^SHOW/BANDS [band|region names]^Show the list of bands and regions
1975 Display the bands and regions (collections of bands) known to
1976 the system. If you supply band or region names to SHOW/BANDS,
1977 the command will display just those bands or regions, e.g.:
1982 === 0^SHOW/BUDDY^Show your list of buddies
1983 See SET/BUDDY for more information about buddies.
1985 === 0^SHOW/CHAT [<group>] [<lines>]^Show any chat or conferencing
1986 This command allows you to see any chat or conferencing that has
1987 occurred whilst you were away. SHOW/CHAT on its own will show data for
1988 all groups. If you use a group name then it will show only chat for
1991 === 9^SHOW/CMD_CACHE [pattern]^Show the real source path of commands
1992 It is possible in DXSpider to define local versions of commands.
1993 Sometimes one forgets that one has these. This command will show you
1994 the source path where the node is getting each one of its commands.
1996 If you find a local command that you don't want then then simply
1997 delete it, run LOAD/CMD_CACHE to clear out the command cache and
1998 try again. You will now be using the standard version.
2000 If you are looking for information on a specific command then
2001 just add a string, eg:
2008 set/dxgrid /spider/cmd/set/dxgrid.pl
2009 sh/dx /spider/cmd/show/dx.pl
2011 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
2012 This command allows you to see all the users that can be seen
2013 and the nodes to which they are connected.
2015 This command is normally abbreviated to: sh/c
2017 Normally, the list returned will be just for the nodes from your
2018 country (because the list otherwise will be very long).
2022 will produce a complete list of all nodes.
2024 BE WARNED: the list that is returned can be VERY long
2026 It is possible to supply a node or part of a prefix and you will get
2027 a list of the users for that node or list of nodes starting with
2034 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
2035 Show all the nodes connected to this node.
2037 === 1^SHOW/CONNECT^Show all the active connections
2038 This command shows information on all the active connections known to
2039 the node. This command gives slightly more information than WHO.
2041 === 0^SHOW/CONTEST <year and month>^Show all the contests for a month
2042 Show all known contests which are maintained at http://www.sk3bg.se/contest/
2043 for a particular month or year. The format is reasonably flexible.
2049 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
2050 This is very nearly the same as SHOW/TIME, the only difference the format
2051 of the date string if no arguments are given.
2053 If no prefixes or callsigns are given then this command returns the local
2054 time and UTC as the computer has it right now. If you give some prefixes
2055 then it will show UTC and UTC + the local offset (not including DST) at
2056 the prefixes or callsigns that you specify.
2058 === 0^SHOW/DB0SDX <callsign>^Show QSL infomation from DB0SDX database
2059 This command queries the DB0SDX QSL server on the internet
2060 and returns any information available for that callsign. This service
2061 is provided for users of this software by http://www.qslinfo.de.
2063 See also SHOW/QRZ, SHOW/WM7D.
2065 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
2067 === 0^SHOW/DX^Interrogate the spot database
2068 If you just type SHOW/DX you will get the last so many spots
2069 (sysop configurable, but usually 10).
2071 In addition you can add any number of these commands in very nearly
2072 any order to the basic SHOW/DX command, they are:-
2074 on <band> - eg 160m 20m 2m 23cm 6mm
2075 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2076 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
2079 <number> - the number of spots you want
2080 <from>-<to> - <from> spot no <to> spot no in the selected list
2083 <prefix> - for a spotted callsign beginning with <prefix>
2084 *<suffix> - for a spotted callsign ending in <suffix>
2085 *<string>* - for a spotted callsign containing <string>
2086 <call> exact - for a spotted callsign *exactly* as typed.
2088 day <number> - starting <number> days ago
2089 day <from>-<to> - <from> days <to> days ago
2092 info <text> - any spots containing <text> in the info or remarks
2094 by <call> - any spots spotted by <call> (spotter <call> is the
2097 qsl - this automatically looks for any qsl info on the call
2098 held in the spot database.
2100 iota [<iota>] - If the iota island number is missing it will look for
2101 the string iota and anything which looks like an iota
2102 island number. If you specify then it will look for
2105 qra [<locator>] - this will look for the specific locator if you specify
2106 one or else anything that looks like a locator.
2108 dxcc - treat the prefix as a 'country' and look for spots
2109 from that country regardless of actual prefix.
2112 You can also use this with the 'by' keyword so
2115 real or rt - Format the output the same as for real time spots. The
2116 formats are deliberately different (so you can tell
2117 one sort from the other). This is useful for some
2118 logging programs that can't cope with normal sh/dx
2119 output. An alias of SHOW/FDX is available.
2121 filter - Filter the spots, before output, with the user's
2122 spot filter. An alias of SHOW/MYDX is available.
2124 zone <zones> - look for spots in the cq zone (or zones) specified.
2125 zones are numbers separated by commas.
2127 by_zone <zones> - look for spots spotted by people in the cq zone
2130 itu <itus> - look for spots in the itu zone (or zones) specified
2131 itu zones are numbers separated by commas.
2133 by_itu <itus> - look for spots spotted by people in the itu zone
2136 state <list> - look for spots in the US state (or states) specified
2137 The list is two letter state codes separated by commas.
2139 by_state <list> - look for spots spotted by people in the US state
2145 SH/DX on 20m info iota
2146 SH/DX 9a on vhf day 30
2152 SH/DX dxcc oq2 by w dxcc
2156 SH/DX by_state in,oh
2159 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
2160 This command takes the <prefix> (which can be a full or partial
2161 callsign if desired), looks up which internal country number it is
2162 and then displays all the spots as per SH/DX for that country.
2164 This is now an alias for 'SHOW/DX DXCC'
2166 The options for SHOW/DX also apply to this command.
2170 SH/DXCC W on 20m iota
2172 This can be done with the SHOW/DX command like this:-
2175 SH/DX dxcc w on 20m iota
2177 This is an alias for: SH/DX dxcc
2179 === 0^SHOW/FDX^Show the DX data in realtime format.
2180 Normally SHOW/DX outputs spot data in a different format to the
2181 realtime data. This is a deliberate policy (so you can tell the
2182 difference between the two). Some logging programs cannot handle
2183 this so SHOW/FDX outputs historical data in real time format.
2185 This is an alias for: SHOW/DX real
2187 === 0^SHOW/DXSTATS [days] [date]^Show the DX Statistics
2188 Show the total DX spots for the last <days> no of days (default is 31),
2189 starting from a <date> (default: today).
2191 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
2192 SHOW/FILES on its own will show you a list of the various fileareas
2193 available on the system. To see the contents of a particular file
2196 where <filearea> is the name of the filearea you want to see the
2199 You can also use shell globbing characters like '*' and '?' in a
2200 string to see a selection of files in a filearea eg:-
2201 SH/FILES bulletins arld*
2203 See also TYPE - to see the contents of a file.
2205 === 0^SHOW/FILTER^Show the contents of all the filters you have set
2206 Show the contents of all the filters that are set. This command displays
2207 all the filters set - for all the various categories.
2209 === 0^SHOW/GRAYLINE [ndays] [<prefix>|<callsign>]^Show Civil dawn/dusk times
2210 This command is very similar to SHOW/SUN except that it shows the
2211 start and end of "Official" or "Civil" Dawn and Dusk. This is defined
2212 as when the Sun is 6 degrees below the horizon.
2214 If you don't specify any prefixes or callsigns, it will show the
2215 times for your QTH (assuming you have set it with either SET/LOCATION
2216 or SET/QRA), together with the current azimuth and elevation.
2218 If all else fails it will show the civil dawn and dusk times for
2219 the node that you are connected to.
2224 SH/GRAYLINE G1TLH W5UN
2226 You can also use this command to see into the past or the future, so
2227 if you want to see yesterday's times then do:-
2231 or in three days time:-
2235 Upto 366 days can be checked both in the past and in the future.
2237 Please note that the times are given as the UT times of the requested
2240 === 0^SHOW/HFSTATS [days] [date]^Show the HF DX Statistics
2241 Show the HF DX spots breakdown by band for the last <days> no of days
2242 (default is 31), starting from a <date> (default: today).
2244 === 0^SHOW/HFTABLE [days] [date] [prefix ...]^Show the HF DX Spotter Table
2245 Show the HF DX Spotter table for the list of prefixes for the last
2246 <days> no of days (default is 31), starting from a <date> (default: today).
2248 If there are no prefixes then it will show the table for your country.
2250 Remember that some countries have more than one "DXCC country" in them
2251 (eg G :-), to show them (assuming you are not in G already which is
2252 specially treated in the code) you must list all the relevant prefixes
2254 sh/hftable g gm gd gi gj gw gu
2256 Note that the prefixes are converted into country codes so you don't have
2257 to list all possible prefixes for each country.
2259 If you want more or less days than the default simply include the
2260 number you require:-
2264 If you want to start at a different day, simply add the date in some
2267 sh/hftable 2 25nov02
2268 sh/hftable 2 25-nov-02
2270 sh/hftable 2 25/11/02
2272 This will show the stats for your DXCC for that CQWW contest weekend.
2274 You can specify either prefixes or full callsigns (so you can see how you
2275 did against all your mates). You can also say 'all' which will then print
2276 the worldwide statistics.
2280 === 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
2281 This command shows the hop counts set up for a node. You can specify
2282 which category you want to see. If you leave the category out then
2283 all the categories will be listed.
2285 === 0^SHOW/IK3QAR <callsign>^Obtain QSL info from IK3QAR database
2286 Get QSL information from the online dabase run by IK3QAR.
2288 Your sysop needs to set up this command by obtaining a password from IK3QAR.
2289 Instructions are available in local/Internet.pm
2291 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
2293 === 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
2295 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
2296 This command outputs a short section of the system log. On its own
2297 it will output a general logfile. With the optional callsign it will
2298 show output from the log associated with that callsign.
2300 === 0^SHOW/MOON [ndays] [<prefix>|<callsign>]^Show Moon rise and set times
2301 Show the Moon rise and set times for a (list of) prefixes or callsigns,
2302 together with the azimuth and elevation of the sun currently at those
2305 If you don't specify any prefixes or callsigns, it will show the times for
2306 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2307 together with the current azimuth and elevation.
2309 In addition, it will show the illuminated fraction of the moons disk.
2311 If all else fails it will show the Moonrise and set times for the node
2312 that you are connected to.
2319 You can also use this command to see into the past or the future, so
2320 if you want to see yesterday's times then do:-
2324 or in three days time:-
2328 Upto 366 days can be checked both in the past and in the future.
2330 Please note that the rise and set times are given as the UT times of rise and
2331 set on the requested UT day.
2333 === 0^SHOW/MOTD^Show your MOTD (the Message of the Day)
2334 The Message of the Day is normally printed whenever one logs on. However
2335 many people now login using logging programs or something other than plain
2336 telnet or ax25 connections. This command allows the user (or the program)
2337 to see what is in the MOTD.
2339 The actual MOTD that you are shown depends on what carrier you are logged
2340 on via, whether you are registered and some other factors that your sysop
2343 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
2344 This command allow you to estimate the likelihood of you contacting
2345 a station with the prefix you have specified. The output assumes a modest
2346 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
2348 The result predicts the most likely operating frequencies and signal
2349 levels for high frequency (shortwave) radio propagation paths on
2350 specified days of the year and hours of the day. It is most useful for
2351 paths between 250 km and 6000 km, but can be used with reduced accuracy
2352 for paths shorter or longer than this.
2354 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2355 used to predict the MUF given the predicted flux, day of the year,
2356 hour of the day and geographic coordinates of the transmitter and
2357 receiver. This routine is reasonably accurate for the purposes here,
2358 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2359 than the programs used by major shortwave broadcasting organizations,
2360 such as the Voice of America.
2362 The command will display some header information detailing its
2363 assumptions, together with the locations, latitude and longitudes and
2364 bearings. It will then show UTC (UT), local time at the other end
2365 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2366 (Zen) and the likely signal strengths. Then for each frequency for which
2367 the system thinks there is a likelihood of a circuit it prints a value.
2369 The value is currently a likely S meter reading based on the conventional
2370 6dB / S point scale. If the value has a '+' appended it means that it is
2371 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
2372 there is likely to be much fading and by an 's' that the signal is likely
2375 By default SHOW/MUF will show the next two hours worth of data. You
2376 can specify anything up to 24 hours worth of data by appending the no of
2377 hours required after the prefix. For example:-
2383 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2384 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2385 Location Lat / Long Azim
2386 East Dereham, Norfolk 52 41 N 0 57 E 47
2387 United-States-W 43 0 N 87 54 W 299
2388 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2389 18 23 11.5 -35 mS0+ mS2 S3
2390 19 0 11.2 -41 mS0+ mS2 S3
2392 indicating that you will have weak, fading circuits on top band and
2393 80m but usable signals on 40m (about S3).
2399 will get you the above display, but with the next 24 hours worth of
2405 Gives you an estimate of the long path propagation characterics. It
2406 should be noted that the figures will probably not be very useful, nor
2407 terrible accurate, but it is included for completeness.
2409 === 0^SHOW/MYDX^Show the DX data filtered with your spot filter.
2410 SHOW/DX potentially shows all the spots available in the system. Using
2411 SHOW/MYDX will, instead, filter the availble spots using any spot filter
2412 that you have set, first.
2414 This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
2415 you to customise the spots that you receive.
2417 So if you have said: ACC/SPOT on hf
2419 Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
2420 options on SH/DX can still be used.
2422 === 0^SHOW/NEWCONFIGURATION [USERS|<node call>]^Show the cluster map
2423 Show the map of the whole cluster.
2425 This shows the structure of the cluster that you are connected to. By
2426 default it will only show the nodes that are known. By adding the keyword
2427 USER to the command it will show all the users as well.
2429 As there will be loops, you will see '...', this means that the information
2430 is as printed earlier and that is a looped connection from here on.
2432 BE WARNED: the list that is returned can be VERY long (particularly
2433 with the USER keyword)
2435 === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
2436 Show all the nodes connected to this node in the new format.
2438 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
2439 Show the type and version (if connected) of the nodes specified on the
2440 command line. If no callsigns are specified then a sorted list of all
2441 the non-user callsigns known to the system will be displayed.
2443 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
2444 This command takes the <callsign> (which can be a full or partial
2445 callsign or a prefix), looks up which internal country number
2446 it is and then displays all the relevant prefixes for that country
2447 together with the internal country no, the CQ and ITU regions.
2451 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
2452 Show the name and location where every program module was load from. This
2453 is useful for checking where you think you have loaded a .pm file from.
2455 === 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
2456 === 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
2457 This is a multipurpose command that allows you either to calculate the
2458 distance and bearing between two locators or (if only one locator is
2459 given on the command line) the distance and beraing from your station
2460 to the locator. For example:-
2465 The first example will show the distance and bearing to the locator from
2466 yourself, the second example will calculate the distance and bearing from
2467 the first locator to the second. You can use 4 or 6 character locators.
2469 It is also possible to convert a latitude and longitude to a locator by
2470 using this command with a latitude and longitude as an argument, for
2473 SH/QRA 52 41 N 0 58 E
2475 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
2476 This command queries the QRZ callbook server on the internet
2477 and returns any information available for that callsign. This service
2478 is provided for users of this software by http://www.qrz.com
2480 See also SHOW/WM7D for an alternative.
2482 === 0^SHOW/DXQSL <callsign>^Show any QSL info gathered from spots
2483 The node collects information from the comment fields in spots (things
2484 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
2486 This command allows you to interrogate that database and if the callsign
2487 is found will display the manager(s) that people have spotted. This
2488 information is NOT reliable, but it is normally reasonably accurate if
2489 it is spotted enough times.
2495 You can check the raw input spots yourself with:-
2499 This gives you more background information.
2501 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
2503 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
2504 This command allows you to see to which node the callsigns specified are
2505 connected. It is a sort of inverse sh/config.
2509 === 9^SHOW/RCMD [<n>][<from>-<to>][<call>] ...^Show log of rcmds
2510 Show the rcmds that have come in and their replies.
2512 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
2513 Show the tracking data from your location to the satellite of your choice
2514 from now on for the next few hours.
2516 If you use this command without a satellite name it will display a list
2517 of all the satellites known currently to the system.
2519 If you give a name then you can obtain tracking data of all the passes
2520 that start and finish 5 degrees below the horizon. As default it will
2521 give information for the next three hours for every five minute period.
2523 You can alter the number of hours and the step size, within certain
2526 Each pass in a period is separated with a row of '-----' characters
2531 SH/SAT FENGYUN1 12 2
2533 === 6^SHOW/STARTUP <call>^View a user startup script
2534 === 0^SHOW/STARTUP^View your own startup script
2535 View the contents of a startup script created with SET/STARTUP.
2537 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
2538 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
2539 Show the information known about a callsign and whether (and where)
2540 that callsign is connected to the cluster.
2544 If no callsign is given then show the information for yourself.
2546 === 0^SHOW/SUN [ndays] [<prefix>|<callsign>]^Show sun rise and set times
2547 Show the sun rise and set times for a (list of) prefixes or callsigns,
2548 together with the azimuth and elevation of the sun currently at those
2551 If you don't specify any prefixes or callsigns, it will show the times for
2552 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2553 together with the current azimuth and elevation.
2555 If all else fails it will show the sunrise and set times for the node
2556 that you are connected to.
2561 SH/SUN G1TLH K9CW ZS
2563 You can also use this command to see into the past or the future, so
2564 if you want to see yesterday's times then do:-
2568 or in three days time:-
2572 Upto 366 days can be checked both in the past and in the future.
2574 Please note that the rise and set times are given as the UT times of rise
2575 and set on the requested UT day.
2577 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
2578 If no prefixes or callsigns are given then this command returns the local
2579 time and UTC as the computer has it right now. If you give some prefixes
2580 then it will show UTC and UTC + the local offset (not including DST) at
2581 the prefixes or callsigns that you specify.
2583 === 0^SHOW/USDB [call ..]^Show information held on the FCC Call database
2584 Show the City and State of a Callsign held on the FCC database if
2585 his is being run on this system, eg:-
2589 === 0^SHOW/VHFSTATS [days] [date]^Show the VHF DX Statistics
2590 Show the VHF DX spots breakdown by band for the last
2591 <days> no of days (default is 31), starting from a date (default: today).
2593 === 0^SHOW/VHFTABLE [days] [date] [prefix ...]^Show the VHF DX Spotter Table
2594 Show the VHF DX Spotter table for the list of prefixes for the last
2595 <days> no of days (default is 31), starting from a date (default: today).
2597 If there are no prefixes then it will show the table for your country.
2599 Remember that some countries have more than one "DXCC country" in them
2600 (eg G :-), to show them (assuming you are not in G already which is
2601 specially treated in the code) you must list all the relevant prefixes
2603 sh/vhftable g gm gd gi gj gw gu
2605 Note that the prefixes are converted into country codes so you don't have
2606 to list all possible prefixes for each country.
2608 If you want more or less days than the default simply include the
2609 number you require:-
2613 If you want to start at a different day, simply add the date in some
2616 sh/vhftable 2 25nov02
2617 sh/vhftable 2 25-nov-02
2618 sh/vhftable 2 021125
2619 sh/vhftable 2 25/11/02
2621 This will show the stats for your DXCC for that CQWW contest weekend.
2623 You can specify either prefixes or full callsigns (so you can see how you
2624 did against all your mates). You can also say 'all' which will then print
2625 the worldwide statistics.
2629 === 0^SHOW/WCY^Show last 10 WCY broadcasts
2630 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
2631 Display the most recent WCY information that has been received by the system
2633 === 0^SHOW/WM7D <callsign>^Show callbook details on a US callsigns
2634 This command queries the WM7D callbook server on the internet
2635 and returns any information available for that US callsign. This service
2636 is provided for users of this software by http://www.wm7d.net.
2640 === 0^SHOW/WWV^Show last 10 WWV broadcasts
2641 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
2642 Display the most recent WWV information that has been received by the system
2644 === 5^SHUTDOWN^Shutdown the cluster
2645 Shutdown the cluster and disconnect all the users
2647 === 9^SPOOF <call> <command>^Do a command as though you are another user
2648 This command is provided so that sysops can set a user's parameters without
2649 me having to write a special 'sysop' version for every user command. It
2650 allows you to pretend that you are doing the command as the user you specify.
2654 SPOOF G1TLH set/name Dirk
2655 SPOOF G1TLH set/qra JO02LQ
2657 === 5^STAT/DB <dbname>^Show the status of a database
2658 Show the internal status of a database descriptor.
2660 Depending on your privilege level you will see more or less information.
2661 This command is unlikely to be of much use to anyone other than a sysop.
2663 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
2664 Show the internal status of the channel object either for the channel that
2665 you are on or else for the callsign that you asked for.
2667 Only the fields that are defined (in perl term) will be displayed.
2669 === 1^STAT/MSG^Show the status of the message system
2670 === 1^STAT/MSG <msgno>^Show the status of a message
2671 This command shows the internal status of a message and includes information
2672 such as to whom it has been forwarded, its size, origin etc etc.
2674 If no message number is given then the status of the message system is
2677 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
2678 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
2680 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
2681 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
2683 === 5^STAT/USER [<callsign>]^Show the full status of a user
2684 Shows the full contents of a user record including all the secret flags
2687 Only the fields that are defined (in perl term) will be displayed.
2689 === 0^SYSOP^Regain your privileges if you login remotely
2690 The system automatically reduces your privilege level to that of a
2691 normal user if you login in remotely. This command allows you to
2692 regain your normal privilege level. It uses the normal system: five
2693 numbers are returned that are indexes into the character array that is
2694 your assigned password (see SET/PASSWORD). The indexes start from
2697 You are expected to return a string which contains the characters
2698 required in the correct order. You may intersperse those characters
2699 with others to obscure your reply for any watchers. For example (and
2700 these values are for explanation :-):
2702 password = 012345678901234567890123456789
2706 aa2bbbb0ccc5ddd7xxx3n
2710 They will all match. If there is no password you will still be offered
2711 numbers but nothing will happen when you input a string. Any match is
2714 === 0^TALK <call> [<text>]^Send a text message to another station
2715 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
2716 Send a short message to any other station that is visible on the cluster
2717 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2718 command, they don't have to be connected locally.
2720 The second form of TALK is used when other cluster nodes are connected
2721 with restricted information. This usually means that they don't send
2722 the user information usually associated with logging on and off the cluster.
2724 If you know that G3JNB is likely to be present on GB7TLH, but you can only
2725 see GB7TLH in the SH/C list but with no users, then you would use the
2726 second form of the talk message.
2728 If you want to have a ragchew with someone you can leave the text message
2729 out and the system will go into 'Talk' mode. What this means is that a
2730 short message is sent to the recipient telling them that you are in a
2731 'Talking' frame of mind and then you just type - everything you send will
2732 go to the station that you asked for.
2734 All the usual announcements, spots and so on will still come out on your
2737 If you want to do something (such as send a spot) you preceed the normal
2738 command with a '/' character, eg:-
2740 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2743 To leave talk mode type:
2747 If you are in 'Talk' mode, there is an extention to the '/' command which
2748 allows you to send the output to all the people you are talking to. You do
2749 with the '//' command. For example:-
2753 will send the hftable as you have it to all the people you are currently
2756 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
2757 Type out the contents of a file in a filearea. So, for example, in
2758 filearea 'bulletins' you want to look at file 'arld051' you would
2760 TYPE bulletins/arld051
2762 See also SHOW/FILES to see what fileareas are available and a
2765 === 0^WHO^Show who is physically connected
2766 This is a quick listing that shows which callsigns are connected and
2767 what sort of connection they have
2769 === 0^WX <text>^Send a weather message to local users
2770 === 0^WX FULL <text>^Send a weather message to all cluster users
2771 === 5^WX SYSOP <text>^Send a weather message to other clusters only
2772 Weather messages can sometimes be useful if you are experiencing an extreme
2773 that may indicate enhanced conditions