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 === 0^ACCEPT/RBN [0-9] <pattern>^Set an 'accept' filter line for RBN spots
111 Create an 'accept this spot' line for a filter.
113 An accept filter line means that if the spot matches this filter it is
114 passed onto the user. See HELP FILTERING for more info. Please read this
115 to understand how filters work - it will save a lot of grief later on.
117 You can use any of the following things in this line:-
119 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
120 on <range> same as 'freq'
121 call <prefixes> eg: G,PA,HB9
122 info <string> eg: iota or qsl
124 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
125 call_itu <prefixes or numbers> or: G,GM,GW
126 call_zone <prefixes or numbers>
127 call_state <states> eg: VA,NH,RI,ME
128 by_dxcc <prefixes or numbers>
129 by_itu <prefixes or numbers>
130 by_zone <prefixes or numbers>
131 by_state <states> eg: VA,NH,RI,ME
135 'call' means the callsign that has spotted 'by' whoever.
137 For frequencies, you can use any of the band names defined in
138 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
139 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
140 this is more efficient than saying simply: freq HF (but don't get
141 too hung up about that)
146 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
148 You can use the tag 'all' to accept everything, eg:
154 acc/spots by_state VA,NH,RI,MA,ME
156 but this probably for advanced users...
159 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
160 This version allows a sysop to set a filter for a callsign as well as the
161 default for nodes and users eg:-
163 accept/spot db0sue-7 1 by_zone 14,15,16
164 accept/spot node_default all
165 set/hops node_default 10
167 accept/spot user_default by G,M,2
169 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
170 It is unlikely that you will want to do this, but if you do then you can
171 filter on the following fields:-
173 by <prefixes> eg: G,M,2
175 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
176 origin_itu <prefixes or numbers> or: G,GM,GW
177 origin_zone <prefixes or numbers>
178 by_dxcc <prefixes or numbers>
179 by_itu <prefixes or numbers>
180 by_zone <prefixes or numbers>
183 There are no examples because WCY Broadcasts only come from one place and
184 you either want them or not (see UNSET/WCY if you don't want them).
186 This command is really provided for future use.
188 See HELP FILTER for information.
190 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
191 This version allows a sysop to set a filter for a callsign as well as the
192 default for nodes and users eg:-
194 accept/wcy node_default all
195 set/hops node_default 10
197 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
198 It is unlikely that you will want to do this, but if you do then you can
199 filter on the following fields:-
201 by <prefixes> eg: G,M,2
203 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
204 origin_itu <prefixes or numbers> or: G,GM,GW
205 origin_zone <prefixes or numbers>
206 by_dxcc <prefixes or numbers>
207 by_itu <prefixes or numbers>
208 by_zone <prefixes or numbers>
215 is probably the only useful thing to do (which will only show WWV broadcasts
216 by stations in the US).
218 See HELP FILTER for information.
220 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
221 This version allows a sysop to set a filter for a callsign as well as the
222 default for nodes and users eg:-
224 accept/wwv db0sue-7 1 by_zone 4
225 accept/wwv node_default all
226 set/hops node_default 10
228 accept/wwv user_default by W,K
230 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
231 <text> is the text of the announcement you wish to broadcast
233 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
234 This will send your announcement cluster wide
236 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
238 === 0^APROPOS <string>^Search help database for <string>
239 Search the help database for <string> (it isn't case sensitive), and print
240 the names of all the commands that may be relevant.
242 === 0^BLANK [<string>] [<nn>]^Print nn (default 1) blank lines (or strings)
243 In its basic form this command prints one or more blank lines. However if
244 you pass it a string it will replicate the string for the width of the
245 screen (default 80) and then print that one or more times, so:
249 prints two blank lines
253 prints a row of - characters once.
257 prints 'abcabcabcabcabcabc....'
259 This is really only of any use in a script file and you can print a maximum
262 === 0^BYE^Exit from the cluster
263 This will disconnect you from the cluster
265 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
266 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
267 When you send messages the fact that you have forwarded it to another node
268 is remembered so that it isn't sent again. When you have a new partner
269 node and you add their callsign to your /spider/msg/forward.pl file, all
270 outstanding non-private messages will be forwarded to them. This may well
271 be ALL the non-private messages. You can prevent this by using these
275 catchup GB7DJK 300 301 302 303 500-510
277 and to undo what you have just done:-
280 uncatchup GB7DJK 300 301 302 303 500-510
282 which will arrange for them to be forward candidates again.
284 Order is not important.
286 === 0^CHAT <group> <text>^Chat or Conference to a group
287 It is now possible to JOIN a group and have network wide conferencing to that
288 group. DXSpider does not (and probably will not) implement the AK1A
289 conference mode as this seems very limiting, is hardly used and doesn't seem
290 to work too well anyway.
292 This system uses the existing ANN system and is compatible with both other
293 DXSpider nodes and AK1A clusters (they use ANN/<group>).
295 You can be a member of as many "groups" as you want. To join a group type:-
297 JOIN FOC (where FOC is the group name)
299 To leave a group type:-
303 You can see which groups you are in by typing:-
307 and you can see whether your mate is in the group, if he connects to the
308 same node as you, by typing:-
312 To send a message to a group type:-
314 CHAT FOC hello everyone
318 CH #9000 hello I am back
320 See also JOIN, LEAVE, SHOW/CHAT
322 === 0^CLEAR/ANNOUNCE [1|all]^Clear a announce filter line
323 This command allows you to clear (remove) a line in a annouce filter or to
324 remove the whole filter.
326 see CLEAR/SPOTS for a more detailed explanation.
328 === 8^CLEAR/ANNOUNCE <callsign> [input] [0-9|all]^Clear a announce filter line
329 A sysop can clear an input or normal output filter for a user or the
330 node_default or user_default.
332 === 6^CLEAR/DUPEFILE^Clear out the dupefile completely
333 The system maintains a list of duplicate announces and spots (amongst many
334 other things). Sometimes this file gets corrupted during operation
335 (although not very often). This command will remove the file and start
338 Try this if you get several duplicate DX Spots, one after another.
340 Please ONLY use this command if you have a problem. And then only once.
341 If it does not cure your problem, then repeating the command won't help.
342 Get onto the dxspider-support list and let us try to help.
344 If you use this command frequently then you will cause other people, as
345 well as yourself, a lot of problems with duplicates.
347 === 0^CLEAR/ROUTE [1|all]^Clear a route filter line
348 This command allows you to clear (remove) a line in a route filter or to
349 remove the whole filter.
351 see CLEAR/SPOTS for a more detailed explanation.
353 === 8^CLEAR/ROUTE <callsign> [input] [0-9|all]^Clear a route filter line
354 A sysop can clear an input or normal output filter for a user or the
355 node_default or user_default.
357 === 0^CLEAR/SPOTS [0-9|all]^Clear a spot filter line
358 This command allows you to clear (remove) a line in a spot filter or to
359 remove the whole filter.
361 If you have a filter:-
364 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
370 you will be left with:-
372 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
378 the filter will be completely removed.
380 === 8^CLEAR/SPOTS <callsign> [input] [0-9|all]^Clear a spot filter line
381 A sysop can clear an input or normal output filter for a user or the
382 node_default or user_default.
384 === 0^CLEAR/WCY [1|all]^Clear a WCY filter line
385 This command allows you to clear (remove) a line in a WCY filter or to
386 remove the whole filter.
388 see CLEAR/SPOTS for a more detailed explanation.
390 === 8^CLEAR/WCY <callsign> [input] [0-9|all]^Clear a WCY filter line
391 A sysop can clear an input or normal output filter for a user or the
392 node_default or user_default.
394 === 0^CLEAR/WWV [1|all]^Clear a WWV filter line
395 This command allows you to clear (remove) a line in a WWV filter or to
396 remove the whole filter.
398 see CLEAR/SPOTS for a more detailed explanation.
400 === 8^CLEAR/WWV <callsign> [input] [0-9|all]^Clear a WWV filter line
401 A sysop can clear an input or normal output filter for a user or the
402 node_default or user_default.
404 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
405 Start a connection process that will culminate in a new connection to the
406 DX cluster <callsign>. This process creates a new 'client' process which will
407 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
408 necessary to traverse the network(s) to logon to the cluster <callsign>.
410 === 5^CREATE/USER <callsign> ...^Create this user from the User Database
411 This command will create one or more new users. None of the fields
412 like name, qth etc will be filled in. It is just a new entry in the user
413 database to which one can add more stuff like SET/PASSWORD or by SPOOF.
415 === 9^DELETE/USDB <callsign> ...^Delete this user from the US State Database
416 This command will completely remove a one or more callsigns
417 from the US States database.
419 There is NO SECOND CHANCE.
421 It goes without saying that you should use this command CAREFULLY!
423 Note that these callsign may be re-instated by any weekly updates from
426 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
427 This command will completely remove a one or more users from the database.
429 There is NO SECOND CHANCE.
431 It goes without saying that you should use this command CAREFULLY!
433 === 0^DBAVAIL^Show a list of all the Databases in the system
434 Title says it all really, this command lists all the databases defined
435 in the system. It is also aliased to SHOW/COMMAND.
437 === 9^DBCREATE <name>^Create a database entry
438 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
439 === 9^DBCREATE <name> remote <node>^Create a remote database entry
440 === 9^DBCREATE <name> cmd <dxspider command>^make a local command available as a DB
441 DBCREATE allows you to define a database in the system. It doesn't actually
442 create anything, just defines it.
444 The databases that are created are simple DB_File hash databases, they are
445 therefore already 'indexed'.
447 You can define a local database with the first form of the command eg:
451 You can also chain databases with the addition of the 'chain' keyword.
452 This will search each database one after the other. A typical example
455 DBCREATE sdx_qsl chain sql_ad
457 No checking is done to see if the any of the chained databases exist, in
458 fact it is usually better to do the above staement first then do each of
459 the chained databases.
461 Databases can exist offsite. To define a database that lives on another
464 DBCREATE buckmaster remote gb7dxc
466 Remote databases cannot be chained; however, the last database in a
467 a chain can be a remote database eg:
469 DBCREATE qsl chain gb7dxc
471 To see what databases have been defined do:
473 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
475 It would be normal for you to add an entry into your local Aliases file
476 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
477 need to add a line like:-
482 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
491 to work as they may be used to.
493 You can also make local commands available as 'pseudo' databases. You
494 can therefore make spider special commands available as a database. I
495 imagine that this will be primarily useful for remote access from
496 legacy nodes. For example:-
498 DBCREATE dxqsl cmd show/dxqsl
500 You also use one of these databases in a chain. This may be useful
503 See DBIMPORT for the importing of existing AK1A format data to databases.
504 See DXEXPORT for how to export an AK1A data in a form able to be imported.
505 See DBSHOW for generic database enquiry
508 === 9^DBEXPORT <dbname> <filename>^Export an AK1A data to a file
509 Sometimes one needs to export the data from an existing database file,
510 maybe for a backup or to send to another node.
512 DBEXPORT oblast /tmp/OBLAST.FUL
514 will export the OBLAST database to /tmp/OBLAST.FUL
516 There is no protection, it is up to you not to overwrite a file that
519 See DBIMPORT for the importing of existing AK1A format data to databases.
521 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
522 If you want to import or update data in bulk to a database you can use
523 this command. It will either create or update entries into an existing
524 database. For example:-
526 DBIMPORT oblast /tmp/OBLAST.FUL
528 will import the standard OBLAST database that comes with AK1A into the
529 oblast database held locally.
531 See DBEXPORT for how to export an AK1A database
533 === 9^DBREMOVE <dbname>^Delete a database
534 DBREMOVE will completely remove a database entry and also delete any data
535 file that is associated with it.
537 There is no warning, no comeback, no safety net.
543 will remove the oblast database from the system and it will also remove
544 the associated datafile.
548 There is no warning, no comeback, no safety net.
550 You have been warned.
552 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
553 This is the generic user interface to the database to the database system.
554 It is expected that the sysop will add an entry to the local Aliases file
555 so that users can use the more familiar AK1A style of enquiry such as:
559 but if he hasn't and the database really does exist (use DBAVAIL or
560 SHOW/COMMAND to find out) you can do the same thing with:
564 === 9^DEBUG^Set the cluster program into debug mode
565 Executing this command will only have an effect if you are running the cluster
570 It will interrupt the cluster just after the debug command has finished.
572 === 0^DIRECTORY^List messages
573 === 0^DIRECTORY ALL^List all messages
574 === 0^DIRECTORY OWN^List your own messages
575 === 0^DIRECTORY NEW^List all new messages
576 === 0^DIRECTORY TO <call>^List all messages to <call>
577 === 0^DIRECTORY FROM <call>^List all messages from <call>
578 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
579 === 0^DIRECTORY <nn>^List last <nn> messages
580 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
581 List the messages in the messages directory.
583 If there is a 'p' one space after the message number then it is a
584 personal message. If there is a '-' between the message number and the
585 'p' then this indicates that the message has been read.
587 You can use shell escape characters such as '*' and '?' in the <call>
590 You can combine some of the various directory commands together eg:-
594 DIR SUBJECT IOTA 200-250
596 You can abbreviate all the commands to one letter and use ak1a syntax:-
602 Sysops can see all users' messages.
604 === 8^DISCONNECT <call> [<call> ...]^Disconnect user(s) or node(s)
605 Disconnect any <call> connected locally.
607 In addition you can disconnect all users (except yourself) with
615 or everything (except yourself) with
619 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
620 This is how you send a DX Spot to other users. You can, in fact, now
621 enter the <freq> and the <call> either way round.
627 will all give the same result. You can add some remarks to the end
628 of the command and they will be added to the spot.
630 DX FR0G 144600 this is a test
632 You can credit someone else by saying:-
634 DX by G1TLH FR0G 144.600 he isn't on the cluster
636 The <freq> is compared against the available bands set up in the
637 cluster. See SHOW/BANDS for more information.
639 === 9^DXQSL_EXPORT <filename>^Export SH/DXSQL information to a file
640 The SHOW/DXQSL command shows any QSL managers that have been extracted
641 from comments on a DX spot.
643 Use this command to export the current state of the information to
644 a CSV style text file. For example:
646 DXQSL_EXPORT /tmp/qsl.csv
648 NOTE: this command will overwrite any file that you have write
651 See also DXQSL_IMPORT to import one of these files.
653 === 9^DXQSL_IMPORT <filename>^Import SH/DXSQL information from a file
654 The SHOW/DXQSL command shows any QSL managers that have been extracted
655 from comments on a DX spot.
657 Use this command to restore a file created by the DXSQL_EXPORT command.
660 DXQSL_IMPORT /tmp/qsl.csv
662 The data in this file will UPDATE any information that may already be
663 present. This may not be what you want. To make the data the same as
664 the import file then you must:
667 * remove /spider/data/qsl.v1
672 Preferably before too many DX spots with qsl manager info come in.
674 === 0^ECHO <line>^Echo the line to the output
675 This command is useful in scripts and so forth for printing the
676 line that you give to the command to the output. You can use this
677 in user_default scripts and the SAVE command for titling and so forth
679 The script will interpret certain standard "escape" sequences as follows:-
681 \t - becomes a TAB character (0x09 in ascii)
682 \a - becomes a BEEP character (0x07 in ascii)
683 \n - prints a new line
685 So the following example:-
687 echo GB7DJK is a dxcluster
691 GB7DJK is a dxcluster
693 on the output. You don't need a \n on the end of the line you want to send.
695 A more complex example:-
697 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
707 === 9^EXPORT <msgno> <filename>^Export a message to a file
708 Export a message to a file. This command can only be executed on a local
709 console with a fully privileged user. The file produced will be in a form
710 ready to be imported back into the cluster by placing it in the import
711 directory (/spider/msg/import).
713 This command cannot overwrite an existing file. This is to provide some
714 measure of security. Any files written will owned by the same user as the
715 main cluster, otherwise you can put the new files anywhere the cluster can
716 access. For example:-
720 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
721 Export the users database to a file in ascii format. If no filename
722 is given then it will export the file to /spider/data/user_asc.
724 If the file already exists it will be renamed to <filename>.o. In fact
725 up to 5 generations of the file can be kept each one with an extra 'o' on the
728 BE WARNED: this will write to any file you have write access to. No check is
729 made on the filename (if any) that you specify.
731 === 0^FILTERING...^Filtering things in DXSpider
732 There are a number of things you can filter in the DXSpider system. They
733 all use the same general mechanism.
735 In general terms you can create a 'reject' or an 'accept' filter which
736 can have up to 10 lines in it. You do this using, for example:-
741 where ..... are the specific commands for that type of filter. There
742 are filters for spots, wwv, announce, wcy and (for sysops)
743 connects. See each different accept or reject command reference for
746 There is also a command to clear out one or more lines in a filter and
747 one to show you what you have set. They are:-
756 There is clear/xxxx command for each type of filter.
758 For now we are going to use spots for the examples, but you can apply
759 the principles to all types of filter.
761 There are two main types of filter 'accept' or 'reject'; which you use
762 depends entirely on how you look at the world and what is least
763 writing to achieve what you want. Each filter has 10 lines (of any
764 length) which are tried in order. If a line matches then the action
765 you have specified is taken (ie reject means ignore it and accept
768 The important thing to remember is that if you specify a 'reject'
769 filter (all the lines in it say 'reject/spots' (for instance)) then if
770 a spot comes in that doesn't match any of the lines then you will get
771 it BUT if you specify an 'accept' filter then any spots that don't
772 match are dumped. For example if I have a one line accept filter:-
774 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
776 then automatically you will ONLY get VHF spots from or to CQ zones 14
777 15 and 16. If you set a reject filter like:
779 reject/spots on hf/cw
781 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
782 and will work it even on CW then you could say:-
784 reject/spots on hf/cw and not info iota
786 But in that case you might only be interested in iota and say:-
788 accept/spots not on hf/cw or info iota
790 which is exactly the same. You should choose one or the other until
791 you are confortable with the way it works. Yes, you can mix them
792 (actually you can have an accept AND a reject on the same line) but
793 don't try this at home until you can analyse the results that you get
794 without ringing up the sysop for help.
796 Another useful addition now is filtering by US state
798 accept/spots by_state VA,NH,RI,ME
800 You can arrange your filter lines into logical units, either for your
801 own understanding or simply convenience. I have one set frequently:-
803 reject/spots 1 on hf/cw
804 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
806 What this does is to ignore all HF CW spots (being a class B I can't
807 read any CW and couldn't possibly be interested in HF :-) and also
808 rejects any spots on VHF which don't either originate or spot someone
811 This is an exmaple where you would use the line number (1 and 2 in
812 this case), if you leave the digit out, the system assumes '1'. Digits
813 '0'-'9' are available.
815 You can leave the word 'and' out if you want, it is implied. You can
816 use any number of brackets to make the 'expression' as you want
817 it. There are things called precedence rules working here which mean
818 that you will NEED brackets in a situation like line 2 because,
819 without it, will assume:-
821 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
823 annoying, but that is the way it is. If you use OR - use
824 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
827 If you want to alter your filter you can just redefine one or more
828 lines of it or clear out one line. For example:-
830 reject/spots 1 on hf/ssb
836 To remove the filter in its entirty:-
840 There are similar CLEAR commands for the other filters:-
848 Once you are happy with the results you get, you may like to experiment.
850 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
851 can be written with a mixed filter, eg:
855 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
857 each filter slot actually has a 'reject' slot and an 'accept'
858 slot. The reject slot is executed BEFORE the accept slot.
860 It was mentioned earlier that after a reject test that doesn't match,
861 the default for following tests is 'accept', the reverse is true for
862 'accept'. In the example what happens is that the reject is executed
863 first, any non hf/cw spot is passed to the accept line, which lets
864 thru everything else on HF.
866 The next filter line lets through just VHF/UHF spots from EU.
868 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
869 This command sends all the latitude and longitude information that your
870 cluster is holding against callsigns. One advantage of recieving this
871 information is that more locator information is held by you. This
872 means that more locators are given on the DX line assuming you have
873 SET/DXGRID enabled. This could be a LOT of information though, so
874 it is not recommended on slow links.
876 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
877 This command sends out any information held in the user file which can
878 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
879 and Homenode. PC41s are only sent for the information that is available.
881 === 8^GET/KEPS^Obtain the latest AMSAT Keplarian Elements from the web
882 There are various ways that one can obtain the AMSAT keps. Traditionally the
883 regular method was to get on the mailing list and then arrange for the email
884 to be piped into convkeps.pl and arrange from the crontab to run LOAD/KEPS.
885 For various reasons, it was quite easy for one to be silently dropped
886 from this mailing list.
888 With the advent of asynchronous (web) connections in DXSpider it is now
889 possible to use this command to get the latest keps direct from the
890 AMSAT web site. One can do this from the command line or one can add a line
891 in the local DXSpider crontab file to do periodically (say once a week).
893 This command will clear out the existing keps and then run LOAD/KEPS
894 for you (but only) after a successful download from the AMSAT website.
896 === 0^HELP^The HELP Command
897 HELP is available for a number of commands. The syntax is:-
901 Where <cmd> is the name of the command you want help on.
903 All commands can be abbreviated, so SHOW/DX can be abbreviated
904 to SH/DX, ANNOUNCE can be shortened to AN and so on.
906 Look at the APROPOS <string> command which will search the help database
907 for the <string> you specify and give you a list of likely commands
908 to look at with HELP.
910 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
911 This command attempts to re-initialise a link to a (usually) AK1A node
912 that has got confused, usually by a protocol loop of some kind. It may
913 work - but you usually will be better off simply disconnecting it (or
914 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
917 Best of luck - you will need it.
919 === 9^DEMONSTRATE <call> <command>^Demonstrate a command to another user
920 This command is provided so that sysops can demonstrate commands to
921 other users. It runs a command as though that user had typed it in and
922 then sends the output to that user, together with the command that
925 DEMO g7brn sh/dx iota oc209
928 Note that this command is similar to SPOOF and will have the same side
929 effects. Commands are run at the privilege of the user which is being
932 === 0^JOIN <group>^Join a chat or conference group
933 JOIN allows you to join a network wide conference group. To join a
934 group (called FOC in this case) type:-
938 See also CHAT, LEAVE, SHOW/CHAT
940 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
941 === 0^KILL <from msgno>-<to msgno>^Delete a range of messages
942 === 0^KILL from <regex>^Delete messages FROM a callsign or pattern
943 === 0^KILL to <regex>^Delete messages TO a callsign or pattern
944 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
945 Delete a message from the local system. You will only be able to
946 delete messages that you have originated or been sent (unless you are
951 Will delete all the messages that you own between msgnos 1234 and 1255.
955 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
959 will delete all messages to g1tlh.
963 will delete a message (usually a 'bulletin') from the whole cluster system.
965 This uses the subject field, so any messages that have exactly the
966 same subject will be deleted. Beware!
968 === 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
969 Deleting a message using the normal KILL commands only marks that message
970 for deletion. The actual deletion only happens later (usually two days later).
972 The KILL EXPUNGE command causes the message to be truly deleted more or less
975 It otherwise is used in the same way as the KILL command.
977 === 0^LEAVE <group>^Leave a chat or conference group
978 LEAVE allows you to leave a network wide conference group. To leave a
979 group (called FOC in this case) type:-
983 See also CHAT, JOIN, SHOW/CHAT
985 === 0^LINKS^Show which nodes is physically connected
986 This is a quick listing that shows which links are connected and
987 some information about them. See WHO for a list of all connections.
989 === 9^LOAD/ALIASES^Reload the command alias table
990 Reload the /spider/cmd/Aliases file after you have editted it. You
991 will need to do this if you change this file whilst the cluster is
992 running in order for the changes to take effect.
994 === 9^LOAD/BANDS^Reload the band limits table
995 Reload the /spider/data/bands.pl file if you have changed it manually whilst
996 the cluster is running.
998 === 9^LOAD/BADMSG^Reload the bad msg table
999 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
1000 the cluster is running. This table contains a number of perl regular
1001 expressions which are searched for in the fields targetted of each message.
1002 If any of them match then that message is immediately deleted on receipt.
1004 === 9^LOAD/BADWORDS^Reload the bad words table
1005 Reload the /spider/data/badwords file if you have changed it manually whilst
1006 the cluster is running. This file contains a list of words which, if found
1007 on certain text portions of PC protocol, will cause those protocol frames
1008 to be rejected. It will all put out a message if any of these words are
1009 used on the announce, dx and talk commands. The words can be one or
1010 more on a line, lines starting with '#' are ignored.
1012 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
1013 Normally, if you change a command file in the cmd or local_cmd tree it
1014 will automatially be picked up by the cluster program. Sometimes it
1015 can get confused if you are doing a lot of moving commands about or
1016 delete a command in the local_cmd tree and want to use the normal one
1017 again. Execute this command to reset everything back to the state it
1018 was just after a cluster restart. To see what is in the command cache
1021 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
1022 Reload the /spider/msg/forward.pl file if you have changed it
1023 manually whilst the cluster is running.
1025 === 5^LOAD/KEPS^Load new keps data
1026 === 5^LOAD/KEPS [nn]^Load new keps data from message
1027 If there is no message number then reload the current Keps data from
1028 the Keps.pm data file. You create this file by running
1030 /spider/perl/convkeps.pl <filename>
1032 on a file containing NASA 2 line keps as a message issued by AMSAT.
1034 If there is a message number, then it will take the message, run
1035 convkeps.pl on it and then load the data, all in one step.
1037 These messages are sent to ALL by GB7DJK (and others) from time to time.
1039 === 9^LOAD/MESSAGES^Reload the system messages file
1040 If you change the /spider/perl/Messages file (usually whilst
1041 fiddling/writing new commands) you can have them take effect during a
1042 cluster session by executing this command. You need to do this if get
1045 unknown message 'xxxx' in lang 'en'
1047 === 9^LOAD/PREFIXES^Reload the prefix table
1048 Reload the /spider/data/prefix_data.pl file if you have changed it
1049 manually whilst the cluster is running.
1051 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
1052 MERGE allows you to bring your spot and wwv database up to date. By default
1053 it will request the last 10 spots and 5 WWVs from the node you select. The
1054 node must be connected locally.
1056 You can request any number of spots or wwv and although they will be appended
1057 to your databases they will not duplicate any that have recently been added
1058 (the last 2 days for spots and last month for WWV data).
1060 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
1061 Alter message parameters like To, From, Subject, whether private or bulletin
1062 or return receipt (RR) is required or whether to keep this message from timing
1065 MSG TO <msgno> <call> - change TO callsign to <call>
1066 MSG FRom <msgno> <call> - change FROM callsign to <call>
1067 MSG PRrivate <msgno> - set private flag
1068 MSG NOPRrivate <msgno> - unset private flag
1069 MSG RR <msgno> - set RR flag
1070 MSG NORR <msgno> - unset RR flag
1071 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1072 MSG NOKEep <msgno> - unset the keep flag
1073 MSG SUbject <msgno> <new> - change the subject to <new>
1074 MSG WAittime <msgno> - remove any waitting time for this message
1075 MSG NOREad <msgno> - mark message as unread
1076 MSG REad <msgno> - mark message as read
1077 MSG QUeue - queue any outstanding bulletins
1078 MSG QUeue 1 - queue any outstanding private messages
1080 You can look at the status of a message by using:-
1084 This will display more information on the message than DIR does.
1086 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
1087 Send some arbitrary text to a locally connected callsign. No
1088 processing is done on the text. This command allows you to send PC
1089 Protocol to unstick things if problems arise (messages get stuck
1092 pc gb7djk PC33^GB7TLH^GB7DJK^400^
1094 pc G1TLH Try doing that properly!!!
1096 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
1097 You can get rid of any message to or originating from your callsign using
1098 this command. You can remove more than one message at a time.
1100 === 5^KILL <from>-<to>^Remove a range of messages from the system
1101 === 5^KILL FROM <call>^Remove all messages from a callsign
1102 === 5^KILL TO <call>^Remove all messages to a callsign
1103 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
1104 Remove this message from the entire cluster system as well as your node.
1107 As a sysop you can kill any message on the system.
1109 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
1110 Send any text you like to the callsign requested. This is used mainly to send
1111 PC protocol to connected nodes either for testing or to unstick things.
1113 You can also use in the same way as a talk command to a connected user but
1114 without any processing, added of "from <blah> to <blah" or whatever.
1116 === 1^PING <node call>^Check the link quality between nodes
1117 This command allows you to send a frame to another cluster node on
1118 the network and get a return frame. The time it takes to do this
1119 is a good indication of the quality of the link. The actual time
1120 it takes is output to the console in seconds.
1121 Any visible cluster node can be PINGed.
1123 === 0^RBN^The Reverse Beacon or Skimmer System
1124 DXSpider now has the ability to show spots from the Reverse Beacon Network
1125 or "Skimmers", if your sysop has enabled the feed(s) (and has the bandwidth
1126 to both receive the feeds and also to pass them on to you.
1128 Currently there are two RBN/Skimmer feeds available which, at busy
1129 times can send up to 50,000 spots/hour EACH. Somewhere in the low
1130 1000s is more normal. Clearly this is not much use to the average user
1131 and so DXSpider "curates" them by removing duplicates and checking for
1132 invalid callsigns or prefixes, as well as using some algorithms to fix
1133 the rather variable frequencies that some skimmers produce
1134 (particularly for CW spots).
1136 This means that the format of the spot that you see is completely
1137 different to the spots that the RBN feeds supply and, as a result of
1138 the "curation" reduces the volume of spots to you by between 8 and 11
1141 See SET/SKIMMER (or SET/WANTRBN) for more information on enabling
1142 RBN/Skimmer spots and also on selecting particular categories (e.g CW
1143 or FT8/FT4) - which has the side benefit of reducing the volume of
1144 spots that you receive even more!
1146 Here are some examples of the output:
1148 DX de LZ4UX-#: 14015.5 ON7TQ CW 6dB Q:9 Z:5,14,15,40 14 0646Z 20
1149 DX de VE7CC-#: 3573.0 N8ADO FT8 -14dB Q:4 Z:4,5 4 0647Z 3
1150 DX de DM7EE-#: 14027.5 R1AC CW 9dB Q:9* Z:5,15,17,20 16 0643Z 14
1151 DX de WE9V-#: 7074.0 EA7ALL FT8 -9dB Q:2+ Z:5 14 0641Z 4
1153 Note that UNSET/DXGRID, UNSET/DXITU and SET/DXCQ are in operation in
1154 these examples. This is completely optional.
1156 The comment field has been completely changed in order provide as much
1157 information, in as smaller space, as possible. All the irrelevant
1158 information has been removed.
1160 You can use the Category (CW and FT8 in these examples) to with
1161 SET/SKIMMER (or SET/WANTRBN) to, rather coarsely, select which spots
1162 you require. You can refine this further by the use of Filtering. See
1163 SET/SKIMMER or SET/WANTRBN for more information. But the short answer
1164 is that these are spots and are filtered like any other spot, unless
1165 you want to filter these spots differently, in which case you can use
1166 REJECT/RBN and ACCEPT/RBN in exactly the same way as ACCEPT/SPOT and
1167 REJECT/SPOT. If you don't use RBN filters then these spots will be
1168 filter by any spot filters that you may have.
1170 The next field (6dB, -14dB etc) is the LOWEST reported signal that was
1173 The Q: field is the number of skimmers that heard this spot (up to 9
1174 shown, but it could easily be many more). If Q: is > 1 (especially on
1175 CW) then you can be reasonably certain that the callsign is accurate,
1176 especially on CW. 'Q' stands for "Qualitee" :-)
1178 If there is a '*', it means that there was a disagreement about
1179 frequency. In fact, particularly for CW spots, I have see
1180 disagreements of 600Hz. Which is a worry. The frequency that is shown
1181 is the majority view of all the skimmers spotting this call. You may
1182 have to fossick about the airwaves to find the actual frequency :-)
1184 There are stations that are permanently on, like Beacons, and also
1185 others that have long sessions on the same frequency and do a lot of
1186 CQing. If they have been on for a certain length of time and they
1187 reappear before their cache entry expires (about 2 hours), then they
1188 are respotted. This is indicated by the '+'. NOTE - if they change
1189 frequency, this will generate new spots. Each callsign/frequency pair
1190 could respotted separately for as long as any individual
1191 callsign/frequency pair remain in the cache.
1193 The Z: field is present then that indicates the other CQ zones that
1194 heard this spot - not including the skimmer that is shown. I show as
1195 many as there are in whatever space is left in the comment
1196 field. Note: if you have any of the optional flags around the time
1197 then they may overwrite part of this field.
1199 If there is NO filter in operation, then the skimmer spot with the
1200 LOWEST signal strength will be shown. This implies that if any extra
1201 Z: zones are shown, then the signal will be higher in those zones.
1203 If you have a filter (for instance: ACCEPT/SPOT by_zone 14 and not
1204 zone 14 or zone 14 and not by_zone 14) where '14' is your QTH CQ
1205 zone. You will, instead be served with the lowest signal strength spot
1206 that satisfies that filter. Incidentally, this particular style of
1207 filter is quite useful for RBN spots, as it reduces the volume and is
1208 likely to be more relevant for casual use. If this filter is too broad
1209 (or narrow) for your normal spotting requirements, then you can use
1210 ACCEPT/RBN with the same filter specification and it will only apply
1211 to RBN spots. You can also replace '14' with a list like '14,15' if
1212 you want to broaden it out. You will still get the same Z: list (if
1213 any) whether you filter or not.
1215 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
1216 This command allows you to send nearly any command to another DX Cluster
1217 node that is connected to the system.
1219 Whether you get any output is dependant on a) whether the other system knows
1220 that the node callsign of this cluster is in fact a node b) whether the
1221 other system is allowing RCMDs from this node and c) whether you have
1222 permission to send this command at all.
1224 === 0^READ^Read the next unread personal message addressed to you
1225 === 0^READ <msgno>^Read the specified message
1226 You can read any messages that are sent as 'non-personal' and also any
1227 message either sent by or sent to your callsign.
1230 As a sysop you may read any message on the system
1232 === 0^REJECT^Set a filter to reject something
1233 Create a filter to reject something
1235 There are 2 types of filter, accept and reject. See HELP FILTERING for more
1238 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
1239 Create an 'reject this announce' line for a filter.
1241 A reject filter line means that if the announce matches this filter it is
1242 passed onto the user. See HELP FILTERING for more info. Please read this
1243 to understand how filters work - it will save a lot of grief later on.
1245 You can use any of the following things in this line:-
1247 info <string> eg: iota or qsl
1248 by <prefixes> eg: G,M,2
1250 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1251 origin_itu <prefixes or numbers> or: G,GM,GW
1252 origin_zone <prefixes or numbers>
1253 origin_state <states> eg: VA,NH,RI,ME
1254 by_dxcc <prefixes or numbers>
1255 by_itu <prefixes or numbers>
1256 by_zone <prefixes or numbers>
1257 by_state <states> eg: VA,NH,RI,ME
1259 wx 1 filter WX announces
1260 dest <prefixes> eg: 6MUK,WDX (distros)
1264 rej/ann by_zone 14,15,16 and not by G,M,2
1266 You can use the tag 'all' to reject everything eg:
1270 but this probably for advanced users...
1272 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
1273 This version allows a sysop to set a filter for a callsign as well as the
1274 default for nodes and users eg:-
1277 reject/ann input node_default by G,M,2
1278 reject/ann user_default by G,M,2
1280 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
1281 === 0^REJECT/RBN [0-9] <pattern>^Set a 'reject' filter line for RBN spots
1282 Create a 'reject this spot' line for a filter.
1284 A reject filter line means that if the spot matches this filter it is
1285 dumped (not passed on). See HELP FILTERING for more info. Please read this
1286 to understand how filters work - it will save a lot of grief later on.
1288 You can use any of the following things in this line:-
1290 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1291 on <range> same as 'freq'
1292 call <prefixes> eg: G,PA,HB9
1293 info <string> eg: iota or qsl
1295 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1296 call_itu <prefixes or numbers> or: G,GM,GW
1297 call_zone <prefixes or numbers>
1298 call_state <states> eg: VA,NH,RI,ME
1299 by_dxcc <prefixes or numbers>
1300 by_itu <prefixes or numbers>
1301 by_zone <prefixes or numbers>
1302 by_state <states> eg: VA,NH,RI,ME
1306 'call' means the callsign that has spotted 'by' whoever.
1308 For frequencies, you can use any of the band names defined in
1309 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1310 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1311 this is more efficient than saying simply: on HF (but don't get
1312 too hung up about that)
1317 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1319 You can use the tag 'all' to reject everything eg:
1323 but this probably for advanced users...
1325 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
1326 Create an 'reject this routing PC Protocol' line for a filter.
1328 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1329 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1330 read this to understand how filters work - it will save a lot of grief later on.
1332 You can use any of the following things in this line:-
1334 call <prefixes> the callsign of the thingy
1335 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1336 call_itu <prefixes or numbers> or: G,GM,GW
1337 call_zone <prefixes or numbers>
1338 call_state <states> eg: VA,NH,RI,ME
1339 origin <prefixes> really the interface it came in on
1340 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1341 origin_itu <prefixes or numbers> or: G,GM,GW
1342 origin_zone <prefixes or numbers>
1343 origin_state <states> eg: VA,NH,RI,ME
1347 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1349 You can use the tag 'all' to reject everything eg:
1351 rej/route all (equiv to [very] restricted mode)
1353 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
1355 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
1356 This version allows a sysop to set a filter for a callsign as well as the
1357 default for nodes and users eg:-
1359 reject/spot db0sue-7 1 by_zone 14,15,16
1360 reject/spot node_default all
1361 set/hops node_default 10
1363 reject/spot user_default by G,M,2
1365 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
1366 It is unlikely that you will want to do this, but if you do then you can
1367 filter on the following fields:-
1369 by <prefixes> eg: G,M,2
1371 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1372 origin_itu <prefixes or numbers> or: G,GM,GW
1373 origin_zone <prefixes or numbers>
1374 by_dxcc <prefixes or numbers>
1375 by_itu <prefixes or numbers>
1376 by_zone <prefixes or numbers>
1379 There are no examples because WCY Broadcasts only come from one place and
1380 you either want them or not (see UNSET/WCY if you don't want them).
1382 This command is really provided for future use.
1384 See HELP FILTER for information.
1386 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
1387 This version allows a sysop to set a filter for a callsign as well as the
1388 default for nodes and users eg:-
1390 reject/wcy gb7djk all
1392 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
1393 It is unlikely that you will want to do this, but if you do then you can
1394 filter on the following fields:-
1396 by <prefixes> eg: G,M,2
1398 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1399 origin_itu <prefixes or numbers> or: G,GM,GW
1400 origin_zone <prefixes or numbers>
1401 by_dxcc <prefixes or numbers>
1402 by_itu <prefixes or numbers>
1403 by_zone <prefixes or numbers>
1408 reject/wwv by_zone 14,15,16
1410 is probably the only useful thing to do (which will only show WWV broadcasts
1411 by stations in the US).
1413 See HELP FILTER for information.
1415 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
1416 This version allows a sysop to set a filter for a callsign as well as the
1417 default for nodes and users eg:-
1419 reject/wwv db0sue-7 1 by_zone 4
1420 reject/wwv node_default all
1422 reject/wwv user_default by W
1424 === 0^REPLY^Reply (privately) to the last message that you have read
1425 === 0^REPLY <msgno>^Reply (privately) to the specified message
1426 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1427 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1428 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1429 You can reply to a message and the subject will automatically have
1430 "Re:" inserted in front of it, if it isn't already present.
1432 You can also use all the extra qualifiers such as RR, PRIVATE,
1433 NOPRIVATE, B that you can use with the SEND command (see SEND
1434 for further details)
1436 === 9^SAVE [-d -t -a] <filename> "<cmd>" [...]^Save command output to a file
1437 This sysop only cammand allows you to save the output of one or more
1438 commands to a file. For example:-
1440 save /spider/packclus/dxstats show/dxstat
1442 will save the output of the normal command "show/dxstat" to the file
1443 "dxstats" in the files area.
1445 You can have some extra flags to the save which will either
1446 date stamp or time stamp or both the filename so:-
1448 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
1449 save -t /tmp/a <cmd> creates /tmp/a_2301Z
1450 save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
1452 The -a flag means append to the file instead of overwriting it.
1454 You can have more than one command on the line, to do this you MUST
1455 enclose each command in double quotes (") eg:-
1457 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
1461 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
1463 You can only write into places that the cluster has permission for (which
1464 is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
1465 need to create any directories you want to put stuff in beforehand as well.
1467 It is likely that you will want to run these commands in a crontab type
1468 situation. You would do that something like:-
1470 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
1472 Note that you still enclose each command with (") characters but you must
1473 enclose the entire save command in (') characters.
1475 Now in fact, this can be varied if you know what you are doing. See the
1476 admin manual for more details.
1478 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1479 === 0^SEND RR <call>^Send a message and ask for a read receipt
1480 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1481 === 0^SEND PRIVATE <call>^Send a personal message
1482 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1483 All the SEND commands will create a message which will be sent either to
1484 an individual callsign or to one of the 'bulletin' addresses.
1486 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1487 it will mark the message as personal and send it to the cluster node that
1488 that callsign is connected to. If the <call> you have specified is in fact
1489 a known bulletin category on your node (eg: ALL) then the message should
1490 automatically become a bulletin.
1492 You can have more than one callsign in all of the SEND commands.
1494 You can have multiple qualifiers so that you can have for example:-
1496 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1498 which should send a copy of message 123 to G1TLH and G0RDI and you will
1499 receive a read receipt when they have read the message.
1501 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1502 SP is an alias for SEND PRIVATE
1504 The system will ask you for a subject. Conventionally this should be
1505 no longer than 29 characters for compatibility. Most modern cluster
1506 software should accept more.
1508 You will now be prompted to start entering your text.
1510 You finish the message by entering '/EX' on a new line. For instance:
1517 If you have started a message and you don't want to keep it then you
1518 can abandon the message with '/ABORT' on a new line, like:-
1522 oh I just can't be bothered with this
1525 If you abort the message it will NOT be sent.
1527 When you are entering the text of your message, most normal output (such
1528 as DX announcements and so on are suppressed and stored for latter display
1529 (upto 20 such lines are stored, as new ones come along, so the oldest
1532 Also, you can enter normal commands commands (and get the output
1533 immediately) whilst in the middle of a message. You do this by typing
1534 the command preceeded by a '/' character on a new line, so:-
1536 /dx g1tlh 144010 strong signal
1538 Will issue a dx annoucement to the rest of the cluster.
1540 Also, you can add the output of a command to your message by preceeding
1541 the command with '//', thus :-
1545 This will show YOU the output from SH/VHFTABLE and also store it in the
1548 You can carry on with the message until you are ready to send it.
1550 === 6^SEND_CONFIG^Broadcast PC92 C records
1551 This is the PC92 equivalent of INIT. In that it will send out a new
1552 PC92 C record to all interfaces. This can be used to bring other nodes
1553 up to date quicker after a restart.
1555 === 0^SET/ADDRESS <your address>^Record your postal address
1557 === 9^SET/AGWENGINE^Enable the AGW Engine
1558 === 9^UNSET/AGWENGINE^Disable the AGW Engine
1559 These commands assume that /spider/local/AGWConnect.pm has been setup
1560 correctly and you wish to do some testing or otherwise want to alter
1561 the default state of your connection to the AGW Engine.
1563 === 9^SET/AGWMONITOR^Enable Monitoring on the AGW Engine
1564 === 9^UNSET/AGWMONITOR^Disable Monitoring on the AGW Engine
1566 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1567 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1569 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1570 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1571 The announce system on legacy cluster nodes is used as a talk
1572 substitute because the network is so poorly connected. If you:
1576 you will suppress several of these announces, you may miss the odd
1577 useful one as well, but you would probably miss them anyway in the
1578 welter of useless ones.
1582 allows you to see them again. This is the default.
1584 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1586 === 6^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1587 === 6^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1588 Setting a word as 'baddx' will prevent spots with that word in the
1589 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1590 further. They will not be displayed and they will not be sent onto
1593 The word must be written in full, no wild cards are allowed eg:-
1595 set/baddx FORSALE VIDEO FR0G
1597 To allow a word again, use the following command ...
1601 === 6^SET/BADNODE <call>..^Stop spots from this node being propagated
1602 === 6^UNSET/BADNODE <call>..^Allow spots from this node again
1603 Setting a callsign as a 'badnode' will prevent spots from that node
1604 going any further. They will not be displayed and they will not be
1605 sent onto other nodes.
1607 The call must be a full eg:-
1611 will stop anything from K1TTT. If you want SSIDs as well then you must
1612 enter them specifically.
1616 will allow spots from him again.
1618 Use with extreme care. This command may well be superceeded by FILTERing.
1620 === 6^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1621 === 6^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1622 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1623 going any further. They will not be displayed and they will not be
1624 sent onto other nodes.
1626 The call must be written in full, no wild cards are allowed eg:-
1628 set/badspotter VE2STN
1630 will stop anything from VE2STN. This command will automatically
1631 stop spots from this user, regardless of whether or which SSID
1632 he uses. DO NOT USE SSIDs in the callsign, just use the callsign
1635 unset/badspotter VE2STN
1637 will allow spots from him again.
1639 Use with extreme care. This command may well be superceded by FILTERing.
1641 This command will also stop TALK and ANNOUNCE/FULL from any user marked
1644 === 6^SET/BADWORD <word>..^Stop things like this word being propagated
1645 Setting a word as a 'badword' will prevent things like spots,
1646 announces or talks with this word in the the text part from going any
1647 further. They will not be displayed and they will not be sent onto
1650 This has changed its meaning from the master release. All words entered
1651 are reduced to the minimum regex that will match words starting like
1654 set/badword annihilate
1656 will stop anything that starts with these words in the text
1659 annihilate annihilated
1661 but it will also stop things like this:
1663 anihilate annni11ihhh ii lllattt eee ddd
1665 A few common 'leet' substitutions are automatically matched:
1667 b0ll0cks bo0lll0ccckks fr1iig
1671 === 6^UNSET/BADWORD <word>..^Propagate things like this word again
1672 This is the opposite of set/badword <word>
1676 will allow text with this word again (if it has been set as a bad word.
1678 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1679 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1681 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1683 === 0^SET/BUDDY <call> [<call>..]^Add this call to my buddy list
1684 === 0^UNSET/BUDDY <call> [<call>..]^Remove this call from my buddy list
1685 A notification message
1686 is sent to you automatically if anybody on your buddy list logs in or
1687 out of any node in this cluster.
1689 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1691 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1692 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1693 You can choose to log several different levels. The levels are
1701 You can show what levels you are logging with SHOW/DEBUG
1703 === 0^SET/DX^Allow DX messages to come out on your terminal
1704 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1706 === 0^SET/DXCQ^Show CQ Zones on the end of DX announcements
1707 === 0^UNSET/DXCQ^Stop CQ Zones on the end of DX announcements
1708 Display both the Spotter's and the Spotted's CQ Zone on the end
1709 of a DX announcement (there is just enough room). Some user programs
1710 cannot cope with this. The Spotter's CQ is on the RHS of the
1711 time, the Spotted's CQ is on the LHS.
1713 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
1715 Do a STAT/USER to see which flags you have set if you are confused.
1717 === 0^SET/DXITU^Show ITU Zones on the end of DX announcements
1718 === 0^UNSET/DXITU^Stop ITU Zones on the end of DX announcements
1719 Display both the Spotter's and the Spotted's ITU Zone on the end
1720 of a DX announcement (there is just enough room). Some user programs
1721 cannot cope with this. The Spotter's ITU is on the RHS of the
1722 time, the Spotted's ITU is on the LHS.
1724 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
1726 Do a STAT/USER to see which flags you have set if you are confused.
1728 === 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
1729 === 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
1730 A standard feature which is enabled in version 1.43 and above is
1731 that if the spotter's grid square is known it is output on the end
1732 of a DX announcement (there is just enough room). Some user programs
1733 cannot cope with this. You can use this command to reset (or set)
1736 Conflicts with: SET/DXCQ, SET/DXITU
1738 Do a STAT/USER to see which flags you have set if you are confused.
1740 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1742 === 0^SET/ECHO^Make the cluster echo your input
1743 === 0^UNSET/ECHO^Stop the cluster echoing your input
1744 If you are connected via a telnet session, different implimentations
1745 of telnet handle echo differently depending on whether you are
1746 connected via port 23 or some other port. You can use this command
1747 to change the setting appropriately.
1749 The setting is stored in your user profile.
1751 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1753 === 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
1754 === 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
1755 If any personal messages come in for your callsign then you can use
1756 these commands to control whether they are forwarded onto your email
1757 address. To enable the forwarding do something like:-
1759 SET/EMAIL mike.tubby@somewhere.com
1761 You can have more than one email address (each one separated by a space).
1762 Emails are forwarded to all the email addresses you specify.
1764 You can disable forwarding by:-
1768 === 0^SET/HERE^Tell the system you are present at your terminal
1769 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1771 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1772 Tell the cluster system where you normally connect to. Any Messages sent
1773 to you will normally find their way there should you not be connected.
1777 === 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
1778 === 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
1779 Set the hop count for a particular type of broadcast for a node.
1781 This command allows you to set up special hop counts for a node
1782 for currently: announce, spots, wwv and wcy broadcasts.
1785 set/hops gb7djk ann 10
1786 set/hops gb7mbc spots 20
1788 Set SHOW/HOPS for information on what is already set. This command
1789 creates a filter and works in conjunction with the filter system.
1791 You can unset the hops with command UNSET/HOPS. For example:-
1793 unset/hops gb7djk ann
1794 unset/hops gb7mbc spots
1797 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1798 Connect a node to your system in such a way that you are a full protocol
1799 member of its network and can see all spots on it, but nothing either leaks
1800 out from it nor goes back into from the rest of the nodes connected to you.
1802 You can potentially connect several nodes in this way.
1804 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1805 Remove isolation from a node - SET/ISOLATE
1807 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1808 You can select the language that you want the cluster to use. Currently
1809 the languages available are en (English), de (German), es (Spanish),
1810 Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
1812 === 5^SET/LOCAL_NODE^Add node to the local_node group
1813 === 5^UNSET/LOCAL_NODE^Remove node from the local_node group
1814 The 'local_node' group is a group of nodes that you want a user
1815 to perceive as effectively one big node. At the moment, this extends
1816 only to announcing whenever a user is logging in or out of one of
1817 the nodes in the group (if those users have SET/LOGININFO).
1819 The local node group is as setup on this node. If you want the other
1820 nodes to also include this node and all the other nodes specified, then
1821 you must get those nodes to also run this command (or rcmd them to do
1824 In principle, therefore, each node determines its own local node group
1825 and these can overlap with other nodes' views.
1827 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1828 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1829 In order to get accurate headings and such like you must tell the system
1830 what your latitude and longitude is. If you have not yet done a SET/QRA
1831 then this command will set your QRA locator for you. For example:-
1832 SET/LOCATION 52 22 N 0 57 E
1834 === 0^SET/LOGININFO^Inform when a station logs in/out locally
1835 === 0^UNSET/LOGININFO^No longer inform when a station logs in/out locally
1837 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1838 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1840 === 8^SET/MAXCONNECT <value> [<call> ..]^Set max incoming connections for user/node
1841 Set the maximum no of connections (parents) an incoming user or node is
1842 allowed to have. If this incoming connection takes it over the separate
1843 limits for users and nodes (defaults: 3 and 8 respectively), then the
1844 connection is refused (with a polite message).
1846 The idea behind this to limit the number of copies of messages that
1847 are sent to users (and nodes). Nodes really don't need to have more than
1848 5 or 6 partners and users don't need more than two connections into the
1851 This check is only for INCOMING connections, no check is performed for
1852 outgoing connections.
1854 === 0^SET/NAME <your name>^Set your name
1855 Tell the system what your name is eg:-
1858 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1859 Tell the system that the call(s) are to be treated as AK1A cluster and
1860 fed PC Protocol rather normal user commands.
1862 === 8^SET/OBSCOUNT <count> <call>^Set the 'pump-up' obscelence PING counter
1863 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1864 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1865 counter which is decremented on every outgoing ping and then reset to
1866 the 'obscount' value on every incoming ping. The default value of this
1869 What this means is that a neighbouring node will be pinged twice at
1870 (default) 300 second intervals and if no reply has been heard just before
1871 what would be the third attempt, that node is disconnected.
1873 If a ping is heard then the obscount is reset to the full value. Using
1874 default values, if a node has not responded to a ping within 15 minutes,
1877 You can set this parameter between 1 and 9.
1879 It is STRONGLY recommended that you don't change the default.
1881 === 0^SET/PAGE <lines per page>^Set the lines per page
1882 Tell the system how many lines you wish on a page when the number of line
1883 of output from a command is more than this. The default is 20. Setting it
1884 explicitly to 0 will disable paging.
1888 The setting is stored in your user profile.
1890 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1891 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1892 in order to determine the rolling quality of the link and, in future, to
1893 affect routing decisions. The default interval is 300 secs or 5 minutes.
1895 You can use this command to set a different interval. Please don't.
1897 But if you do the value you enter is treated as minutes up 30 and seconds
1898 for numbers greater than that.
1900 This is used also to help determine when a link is down at the far end
1901 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1902 for more information.
1904 If you must change it (and it may be useful for internet connected nodes
1905 on dynamic IP addresses that go away after a set time of usage) the time
1906 can be specified as:-
1908 5 which if less than 30 is converted to minutes otherwise is
1909 taken as the no of seconds between pings.
1914 Please be aware that this causes traffic to occur on the link, setting
1915 this value too low may annoy your neighbours beyond the point of
1918 You can switch this off by setting it to 0.
1920 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1921 Set the privilege level on a callsign. The privilege levels that pertain
1922 to commands are as default:-
1924 1 - allow remote nodes normal user RCMDs
1925 5 - various privileged commands (including shutdown, but not disc-
1926 connect), the normal level for another node.
1927 8 - more privileged commands (including disconnect)
1928 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1930 If you are a sysop and you come in as a normal user on a remote connection
1931 your privilege will automatically be set to 0.
1933 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1934 You can use this command to 'protect' this session from unauthorised
1935 use. If you want to get your normal privilege back you will need to
1936 either logout and login again (if you are on a console) or use the
1939 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1940 The password for a user can only be set by a full sysop. The string
1941 can contain any characters.
1943 The way this field is used depends on context. If it is being used in
1944 the SYSOP command context then you are offered 5 random numbers and you
1945 have to supply the corresponding letters. This is now mainly for ax25
1948 If it is being used on incoming telnet connections then, if a password
1951 set/var $main::passwdreq = 1
1953 command is executed in the startup script, then a password prompt is
1954 given after the normal 'login: ' prompt.
1956 === 0^SET/PASSWORD^Set your own password
1957 This command only works for a 'telnet' user (currently). It will
1958 only work if you have a password already set. This initial password
1959 can only be set by the sysop.
1961 When you execute this command it will ask you for your old password,
1962 then ask you to type in your new password twice (to make sure you
1963 get it right). You may or may not see the data echoed on the screen
1964 as you type, depending on the type of telnet client you have.
1966 === 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
1967 This command allows the sysop to completely delete and remove a
1968 password for a user.
1970 === 0^SET/PROMPT <string>^Set your prompt to <string>
1971 === 0^UNSET/PROMPT^Set your prompt back to default
1972 This command will set your user prompt to the string that you
1973 say. The point of this command to enable a user to interface to programs
1974 that are looking for a specific prompt (or else you just want a different
1979 There are some substitutions that can be added to the prompt:
1981 %C - callsign [which will have ( and ) around it if not here]
1984 %M - cluster 'mycall'
1986 The standard prompt is defined as:
1988 SET/PROMPT %C de %M %D %T dxspider >
1990 UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to
1993 === 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
1994 === 0^SET/QRA <locator>^Set your QRA Grid locator
1995 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1996 done a SET/LOCATION then your latitude and longitude will be set roughly
1997 correctly (assuming your locator is correct ;-). For example:-
2000 === 0^SET/QTH <your qth>^Set your QTH
2001 Tell the system where you are. For example:-
2002 SET/QTH East Dereham, Norfolk
2004 === 9^SET/RBN <call> ...^Mark this call as an RBN node
2005 This will mark this callsign as a Reverse Beacon
2006 Network client. It's not a node in the normal sense of that word
2007 in DXSpider. But it will generate spots from the RBN/Skimmers and
2008 will act like a specialised node just for RBN spots.
2010 You will need to use this command to create your skimmer node
2011 connections. Normally one per RBN port (7000, 7001) but, in principle
2012 you could connect to any skimmer that uses the same spot format.
2014 === 9^SET/REGISTER <call> ...^Mark a user as registered
2015 === 9^UNSET/REGISTER <call> ...^Mark a user as not registered
2016 Registration is a concept that you can switch on by executing the
2018 set/var $main::regreq = 1
2020 command (usually in your startup file)
2022 If a user is NOT registered then, firstly, instead of the normal
2023 motd file (/spider/data/motd) being sent to the user at startup, the
2024 user is sent the motd_nor file instead. Secondly, the non registered
2025 user only has READ-ONLY access to the node. The non-registered user
2026 cannot use DX, ANN etc.
2028 The only exception to this is that a non-registered user can TALK or
2029 SEND messages to the sysop.
2031 === 6^SET/STARTUP <call>^Create a user startup script
2032 === 0^SET/STARTUP^Create your own startup script
2033 Create a startup script of DXSpider commands which will be executed
2034 everytime that you login into this node. You can only input the whole
2035 script afresh, it is not possible to 'edit' it. Inputting a new script is
2036 just like typing in a message using SEND. To finish inputting type: /EX
2037 on a newline, to abandon the script type: /ABORT.
2039 You may find the (curiously named) command BLANK useful to break
2040 up the output. If you simply want a blank line, it is easier to
2041 input one or more spaces and press the <return> key.
2043 See UNSET/STARTUP to remove a script.
2045 === 6^UNSET/STARTUP <call>^Remove a user startup script
2046 === 0^UNSET/STARTUP^Remove your own startup script
2047 You can remove your startup script with UNSET/STARTUP.
2049 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
2050 Tell the system that the call(s) are to be treated as DXSpider node and
2051 fed new style DX Protocol rather normal user commands.
2053 === 5^UNSET/SPIDER <call> [<call>..]^Make the callsign a normal user
2054 === 5^UNSET/ARCLUSTER <call> [<call>..]^Make the callsign a normal user
2055 === 5^UNSET/NODE <call> [<call>..]^Make the callsign a normal user
2056 === 5^UNSET/AK1A <call> [<call>..]^Make the callsign a normal user
2057 === 5^SET/USER <call> [<call>..]^Make the callsign a normal user
2059 === 0^SET/TALK^Allow TALK messages to come out on your terminal
2060 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
2062 === 9^SET/USDB <call> <state> <city>^add/update a US DB callsign
2063 This command allows you to add or alter a callsign in the US state
2064 database. Use with extreme caution. Anything you do here will be
2065 overwritten by any weekly updates that affect this callsign
2067 set/usdb g1tlh nh downtown rindge
2069 see also DELETE/USDB
2071 === 0^SET/USSTATE^Allow US State info on the end of DX announcements
2072 === 0^UNSET/USSTATE^Stop US State info on the end of DX announcements
2073 If the spotter's or spotted's US State is known it is output on the
2074 end of a DX announcement (there is just enough room).
2076 A spotter's state will appear on the RHS of the time (like
2077 SET/DXGRID) and the spotted's State will appear on the LHS of the
2078 time field. Any information found will override any locator
2079 information from SET/DXGRID.
2081 Some user programs cannot cope with this. You can use this command
2082 to reset (or set) this feature.
2084 Conflicts with: SET/DXCQ, SET/DXITU
2086 Do a STAT/USER to see which flags you have set if you are confused.
2088 === 0^SET/WANTRBN^[category ..]^Allow (some) RBN/Skimmer spots
2089 === 0^SET/SKIMMER^[category ..]^Allow (some) RBN/Skimmer spotsT
2090 === 0^UNSET/WANTRBN^Stop all RBN/Skimmer spots
2091 === 0^UNSET/SKIMMER^Stop all RBN/Skimmer spots
2092 === 9^SET/WANTRBN^<call> [category ..]^Allow (some) RBN/Skimmer spots
2093 === 9^SET/SKIMMER^<call> [category ..]^Allow (some) RBN/Skimmer spots
2094 This command allows curated Reverse Beacon Spots to come out on your
2097 If you want everything just type:
2103 Either command will do.
2105 If you want it all to just stop type:
2107 unset/skimmer (or unset/wantrbn)
2111 There five categories (or modes) of RBN/Skimmer spot available and one
2112 can limit the spots to one or more of these categories/modes:
2114 CW BEACON PSK RTTY FT
2116 together with a load of synonyms
2126 you will get psk, fsk, msk, ft4 and ft8 spots. if you want to break
2127 that down, then you will need to set filters accordingly - but your
2128 filter will only be offered spots from the categories that you have
2131 If you get into a muddle with this you can simply reset 'all on'
2132 with SET/SKIMMER or 'all off' with UNSET/SKIMMER.
2134 By default any filters that you have for "manual" spots will be
2135 automatically applied to your RBN/Skimmer feed. However it is possible
2136 to filter RBN/Skimmer spots differently by use ACCEPT/RBN and/or
2139 The RBN filters completely override any spot filters for these
2140 spots. But the spot filters will continue to filter "manual" spots as
2143 NOTE: Filters and this command CAN interact with each other. If you
2144 don't get the results that you expect, check your filters with
2147 Please see HELP RBN for an explanation of the spot format. It is NOT
2148 the same as one would get directly from the RBN/Skimmers. But it is
2149 recommended that you SET/DXCQ and UNSET/DXITU and UNSET/DXGRID (unless
2150 latter in more important to you with, for example, FT4/8 spots).
2152 === 0^SET/WCY^Allow WCY messages to come out on your terminal
2153 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
2155 === 0^SET/WWV^Allow WWV messages to come out on your terminal
2156 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
2158 === 0^SET/WX^Allow WX messages to come out on your terminal
2159 === 0^UNSET/WX^Stop WX messages coming out on your terminal
2161 === 0^SHOW/ANNOUNCE [<n>][<from>-<to>][<call>] ...^Show log of announces
2162 Show announcements that have come in.
2164 === 1^SHOW/BADDX^Show all the bad dx calls in the system
2165 Display all the bad dx callsigns in the system, see SET/BADDX
2166 for more information.
2168 === 1^SHOW/BADNODE^Show all the bad nodes in the system
2169 Display all the bad node callsigns in the system, see SET/BADNODE
2170 for more information.
2172 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
2173 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
2174 for more information.
2176 === 1^SHOW/BADWORD^Show all the bad words in the system
2177 Display all the bad words in the system, see SET/BADWORD
2178 for more information.
2180 === 0^SHOW/BANDS [band|region names]^Show the list of bands and regions
2181 Display the bands and regions (collections of bands) known to
2182 the system. If you supply band or region names to SHOW/BANDS,
2183 the command will display just those bands or regions, e.g.:
2188 === 0^SHOW/BUDDY^Show your list of buddies
2189 See SET/BUDDY for more information about buddies.
2191 === 0^SHOW/CHAT [<group>] [<lines>]^Show any chat or conferencing
2192 This command allows you to see any chat or conferencing that has
2193 occurred whilst you were away. SHOW/CHAT on its own will show data for
2194 all groups. If you use a group name then it will show only chat for
2197 === 9^SHOW/CMD_CACHE [pattern]^Show the real source path of commands
2198 It is possible in DXSpider to define local versions of commands.
2199 Sometimes one forgets that one has these. This command will show you
2200 the source path where the node is getting each one of its commands.
2202 If you find a local command that you don't want then then simply
2203 delete it, run LOAD/CMD_CACHE to clear out the command cache and
2204 try again. You will now be using the standard version.
2206 If you are looking for information on a specific command then
2207 just add a string, eg:
2214 set/dxgrid /spider/cmd/set/dxgrid.pl
2215 sh/dx /spider/cmd/show/dx.pl
2217 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
2218 This command allows you to see all the users that can be seen
2219 and the nodes to which they are connected.
2221 This command is normally abbreviated to: sh/c
2223 Normally, the list returned will be just for the nodes from your
2224 country (because the list otherwise will be very long).
2228 will produce a complete list of all nodes.
2230 BE WARNED: the list that is returned can be VERY long
2232 It is possible to supply a node or part of a prefix and you will get
2233 a list of the users for that node or list of nodes starting with
2240 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
2241 Show all the nodes connected to this node.
2243 === 1^SHOW/CONNECT^Show all the active connections
2244 This command shows information on all the active connections known to
2245 the node. This command gives slightly more information than WHO.
2247 === 0^SHOW/CONTEST [<year>] [<month>]^Show all the contests for a month
2248 Show all known contests which are maintained at http://www.sk3bg.se/contest/
2249 for a particular month or year. The format is reasonably flexible.
2257 If there is no month/year then the current month's contests are shown.
2259 Note that it expects ENGLISH (jan/feb/mar/apr/may/jun/jul/aug/sep/oct/nov/dec)
2262 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
2263 This is very nearly the same as SHOW/TIME, the only difference the format
2264 of the date string if no arguments are given.
2266 If no prefixes or callsigns are given then this command returns the local
2267 time and UTC as the computer has it right now. If you give some prefixes
2268 then it will show UTC and UTC + the local offset (not including DST) at
2269 the prefixes or callsigns that you specify.
2271 === 0^SHOW/DB0SDX <callsign>^Show QSL infomation from DB0SDX database
2272 This command queries the DB0SDX QSL server on the internet
2273 and returns any information available for that callsign. This service
2274 is provided for users of this software by http://www.qslinfo.de.
2276 See also SHOW/QRZ, SHOW/WM7D.
2278 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
2280 === 0^SHOW/DX^Interrogate the spot database
2281 If you just type SHOW/DX you will get the last so many spots
2282 (sysop configurable, but usually 10).
2284 In addition you can add any number of these commands in very nearly
2285 any order to the basic SHOW/DX command, they are:-
2287 on <band> - eg 160m 20m 2m 23cm 6mm
2288 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2289 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
2292 <number> - the number of spots you want
2293 <from>-<to> - <from> spot no <to> spot no in the selected list
2296 <prefix> - for a spotted callsign beginning with <prefix>
2297 *<suffix> - for a spotted callsign ending in <suffix>
2298 *<string>* - for a spotted callsign containing <string>
2299 <call> exact - for a spotted callsign *exactly* as typed.
2301 day <number> - starting <number> days ago
2302 day <from>-<to> - <from> days <to> days ago
2305 info <text> - any spots containing <text> in the info or remarks
2307 by <call> - any spots spotted by <call> (spotter <call> is the
2310 qsl - this automatically looks for any qsl info on the call
2311 held in the spot database.
2313 iota [<iota>] - If the iota island number is missing it will look for
2314 the string iota and anything which looks like an iota
2315 island number. If you specify then it will look for
2318 qra [<locator>] - this will look for the specific locator if you specify
2319 one or else anything that looks like a locator.
2321 dxcc - treat the prefix as a 'country' and look for spots
2322 from that country regardless of actual prefix.
2325 You can also use this with the 'by' keyword so
2328 real or rt - Format the output the same as for real time spots. The
2329 formats are deliberately different (so you can tell
2330 one sort from the other). This is useful for some
2331 logging programs that can't cope with normal sh/dx
2332 output. An alias of SHOW/FDX is available.
2334 filter - Filter the spots, before output, with the user's
2335 spot filter. An alias of SHOW/MYDX is available.
2337 zone <zones> - look for spots in the cq zone (or zones) specified.
2338 zones are numbers separated by commas.
2340 by_zone <zones> - look for spots spotted by people in the cq zone
2343 itu <itus> - look for spots in the itu zone (or zones) specified
2344 itu zones are numbers separated by commas.
2346 by_itu <itus> - look for spots spotted by people in the itu zone
2349 state <list> - look for spots in the US state (or states) specified
2350 The list is two letter state codes separated by commas.
2352 by_state <list> - look for spots spotted by people in the US state
2355 origin - the node from which this spot originated (must be an
2356 exact callsign with SSID e.g. gb7tlh-4)
2358 ip - the IP address of the spotter (either in IPV4 or IPV6)
2359 format. These addresses can be partial.
2364 SH/DX on 20m info iota
2365 SH/DX 9a on vhf day 30
2371 SH/DX dxcc oq2 by w dxcc
2375 SH/DX by_state in,oh
2377 SH/DX origin gb7tlh-4
2378 SH/DX ip 82.65.128.4 (or SH/DX ip 2a00:1450:4009:800::200e)
2380 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
2381 This command takes the <prefix> (which can be a full or partial
2382 callsign if desired), looks up which internal country number it is
2383 and then displays all the spots as per SH/DX for that country.
2385 This is now an alias for 'SHOW/DX DXCC'
2387 The options for SHOW/DX also apply to this command.
2391 SH/DXCC W on 20m iota
2393 This can be done with the SHOW/DX command like this:-
2396 SH/DX dxcc w on 20m iota
2398 This is an alias for: SH/DX dxcc
2400 === 0^SHOW/FDX^Show the DX data in realtime format.
2401 Normally SHOW/DX outputs spot data in a different format to the
2402 realtime data. This is a deliberate policy (so you can tell the
2403 difference between the two). Some logging programs cannot handle
2404 this so SHOW/FDX outputs historical data in real time format.
2406 This is an alias for: SHOW/DX real
2408 === 0^SHOW/DXSTATS [days] [date]^Show the DX Statistics
2409 Show the total DX spots for the last <days> no of days (default is 31),
2410 starting from a <date> (default: today).
2412 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
2413 SHOW/FILES on its own will show you a list of the various fileareas
2414 available on the system. To see the contents of a particular file
2417 where <filearea> is the name of the filearea you want to see the
2420 You can also use shell globbing characters like '*' and '?' in a
2421 string to see a selection of files in a filearea eg:-
2422 SH/FILES bulletins arld*
2424 See also TYPE - to see the contents of a file.
2426 === 0^SHOW/FILTER^Show the contents of all the filters you have set
2427 Show the contents of all the filters that are set. This command displays
2428 all the filters set - for all the various categories.
2430 === 0^SHOW/GRAYLINE [ndays] [<prefix>|<callsign>]^Show Civil dawn/dusk times
2431 This command is very similar to SHOW/SUN except that it shows the
2432 start and end of "Official" or "Civil" Dawn and Dusk. This is defined
2433 as when the Sun is 6 degrees below the horizon.
2435 If you don't specify any prefixes or callsigns, it will show the
2436 times for your QTH (assuming you have set it with either SET/LOCATION
2437 or SET/QRA), together with the current azimuth and elevation.
2439 If all else fails it will show the civil dawn and dusk times for
2440 the node that you are connected to.
2445 SH/GRAYLINE G1TLH W5UN
2447 You can also use this command to see into the past or the future, so
2448 if you want to see yesterday's times then do:-
2452 or in three days time:-
2456 Upto 366 days can be checked both in the past and in the future.
2458 Please note that the times are given as the UT times of the requested
2461 === 0^SHOW/HFSTATS [days] [date]^Show the HF DX Statistics
2462 Show the HF DX spots breakdown by band for the last <days> no of days
2463 (default is 31), starting from a <date> (default: today).
2465 === 0^SHOW/HFTABLE [days] [date] [prefix ...]^Show the HF DX Spotter Table
2466 Show the HF DX Spotter table for the list of prefixes for the last
2467 <days> no of days (default is 31), starting from a <date> (default: today).
2469 If there are no prefixes then it will show the table for your country.
2471 Remember that some countries have more than one "DXCC country" in them
2472 (eg G :-), to show them (assuming you are not in G already which is
2473 specially treated in the code) you must list all the relevant prefixes
2475 sh/hftable g gm gd gi gj gw gu
2477 Note that the prefixes are converted into country codes so you don't have
2478 to list all possible prefixes for each country.
2480 If you want more or less days than the default simply include the
2481 number you require:-
2485 If you want to start at a different day, simply add the date in some
2488 sh/hftable 2 25nov02
2489 sh/hftable 2 25-nov-02
2491 sh/hftable 2 25/11/02
2493 This will show the stats for your DXCC for that CQWW contest weekend.
2495 You can specify either prefixes or full callsigns (so you can see how you
2496 did against all your mates). You can also say 'all' which will then print
2497 the worldwide statistics.
2501 === 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
2502 This command shows the hop counts set up for a node. You can specify
2503 which category you want to see. If you leave the category out then
2504 all the categories will be listed.
2506 === 0^SHOW/IK3QAR <callsign>^Obtain QSL info from IK3QAR database
2507 Get QSL information from the online dabase run by IK3QAR.
2509 Your sysop needs to set up this command by obtaining a password from IK3QAR.
2510 Instructions are available in local/Internet.pm
2512 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
2514 === 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
2516 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
2517 This command outputs a short section of the system log. On its own
2518 it will output a general logfile. With the optional callsign it will
2519 show output from the log associated with that callsign.
2521 === 0^SHOW/MOON [ndays] [<prefix>|<callsign>]^Show Moon rise and set times
2522 Show the Moon rise and set times for a (list of) prefixes or callsigns,
2523 together with the azimuth and elevation of the sun currently at those
2526 If you don't specify any prefixes or callsigns, it will show the times for
2527 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2528 together with the current azimuth and elevation.
2530 In addition, it will show the illuminated fraction of the moons disk.
2532 If all else fails it will show the Moonrise and set times for the node
2533 that you are connected to.
2540 You can also use this command to see into the past or the future, so
2541 if you want to see yesterday's times then do:-
2545 or in three days time:-
2549 Upto 366 days can be checked both in the past and in the future.
2551 Please note that the rise and set times are given as the UT times of rise and
2552 set on the requested UT day.
2554 === 0^SHOW/MOTD^Show your MOTD (the Message of the Day)
2555 The Message of the Day is normally printed whenever one logs on. However
2556 many people now login using logging programs or something other than plain
2557 telnet or ax25 connections. This command allows the user (or the program)
2558 to see what is in the MOTD.
2560 The actual MOTD that you are shown depends on what carrier you are logged
2561 on via, whether you are registered and some other factors that your sysop
2564 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
2565 This command allow you to estimate the likelihood of you contacting
2566 a station with the prefix you have specified. The output assumes a modest
2567 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
2569 The result predicts the most likely operating frequencies and signal
2570 levels for high frequency (shortwave) radio propagation paths on
2571 specified days of the year and hours of the day. It is most useful for
2572 paths between 250 km and 6000 km, but can be used with reduced accuracy
2573 for paths shorter or longer than this.
2575 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2576 used to predict the MUF given the predicted flux, day of the year,
2577 hour of the day and geographic coordinates of the transmitter and
2578 receiver. This routine is reasonably accurate for the purposes here,
2579 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2580 than the programs used by major shortwave broadcasting organizations,
2581 such as the Voice of America.
2583 The command will display some header information detailing its
2584 assumptions, together with the locations, latitude and longitudes and
2585 bearings. It will then show UTC (UT), local time at the other end
2586 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2587 (Zen) and the likely signal strengths. Then for each frequency for which
2588 the system thinks there is a likelihood of a circuit it prints a value.
2590 The value is currently a likely S meter reading based on the conventional
2591 6dB / S point scale. If the value has a '+' appended it means that it is
2592 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
2593 there is likely to be much fading and by an 's' that the signal is likely
2596 By default SHOW/MUF will show the next two hours worth of data. You
2597 can specify anything up to 24 hours worth of data by appending the no of
2598 hours required after the prefix. For example:-
2604 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2605 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2606 Location Lat / Long Azim
2607 East Dereham, Norfolk 52 41 N 0 57 E 47
2608 United-States-W 43 0 N 87 54 W 299
2609 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2610 18 23 11.5 -35 mS0+ mS2 S3
2611 19 0 11.2 -41 mS0+ mS2 S3
2613 indicating that you will have weak, fading circuits on top band and
2614 80m but usable signals on 40m (about S3).
2620 will get you the above display, but with the next 24 hours worth of
2626 Gives you an estimate of the long path propagation characterics. It
2627 should be noted that the figures will probably not be very useful, nor
2628 terrible accurate, but it is included for completeness.
2630 === 0^SHOW/MYDX^Show the DX data filtered with your spot filter.
2631 SHOW/DX potentially shows all the spots available in the system. Using
2632 SHOW/MYDX will, instead, filter the availble spots using any spot filter
2633 that you have set, first.
2635 This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
2636 you to customise the spots that you receive.
2638 So if you have said: ACC/SPOT on hf
2640 Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
2641 options on SH/DX can still be used.
2643 === 0^SHOW/NEWCONFIGURATION [USERS|<node call>]^Show the cluster map
2644 Show the map of the whole cluster.
2646 This shows the structure of the cluster that you are connected to. By
2647 default it will only show the nodes that are known. By adding the keyword
2648 USER to the command it will show all the users as well.
2650 As there will be loops, you will see '...', this means that the information
2651 is as printed earlier and that is a looped connection from here on.
2653 BE WARNED: the list that is returned can be VERY long (particularly
2654 with the USER keyword)
2656 === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
2657 Show all the nodes connected to this node in the new format.
2659 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
2660 === 1^SHOW/NODE ALL^Show the type,version number of ALL known nodes
2661 Show the type and version (if connected) of the nodes specified on the
2662 command line. If no callsigns are specified then a sorted list of all
2663 the non-user callsigns connected to node will be displayed.
2665 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
2666 This command takes the <callsign> (which can be a full or partial
2667 callsign or a prefix), looks up which internal country number
2668 it is and then displays all the relevant prefixes for that country
2669 together with the internal country no, the CQ and ITU regions.
2673 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
2674 Show the name and location where every program module was load from. This
2675 is useful for checking where you think you have loaded a .pm file from.
2677 === 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
2678 === 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
2679 This is a multipurpose command that allows you either to calculate the
2680 distance and bearing between two locators or (if only one locator is
2681 given on the command line) the distance and beraing from your station
2682 to the locator. For example:-
2687 The first example will show the distance and bearing to the locator from
2688 yourself, the second example will calculate the distance and bearing from
2689 the first locator to the second. You can use 4 or 6 character locators.
2691 It is also possible to convert a latitude and longitude to a locator by
2692 using this command with a latitude and longitude as an argument, for
2695 SH/QRA 52 41 N 0 58 E
2697 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
2698 This command queries the QRZ callbook server on the internet
2699 and returns any information available for that callsign. This service
2700 is provided for users of this software by http://www.qrz.com
2702 See also SHOW/WM7D for an alternative.
2704 === 0^SHOW/DXQSL <callsign>^Show any QSL info gathered from spots
2705 The node collects information from the comment fields in spots (things
2706 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
2708 This command allows you to interrogate that database and if the callsign
2709 is found will display the manager(s) that people have spotted. This
2710 information is NOT reliable, but it is normally reasonably accurate if
2711 it is spotted enough times.
2717 You can check the raw input spots yourself with:-
2721 This gives you more background information.
2723 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
2725 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
2726 This command allows you to see to which node the callsigns specified are
2727 connected. It is a sort of inverse sh/config.
2731 === 1^SHOW/RBN [<callsign> ...]^Show which connected users want RBN spots
2732 === 1^SHOW/RBN ALL^Show ALL users that want RBN spots
2733 Show a list of the users that want RBN spots of any the callsigns
2734 specified on the command line. If no callsigns are specified then a
2735 sorted list of all connected users wanting RBN spots will be displayed
2739 will go through the user file and display ALL users that want RBN spots.
2741 === 9^SHOW/RCMD [<n>][<from>-<to>][<call>] ...^Show log of rcmds
2742 Show the rcmds that have come in and their replies.
2744 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
2745 Show the tracking data from your location to the satellite of your choice
2746 from now on for the next few hours.
2748 If you use this command without a satellite name it will display a list
2749 of all the satellites known currently to the system.
2751 If you give a name then you can obtain tracking data of all the passes
2752 that start and finish 5 degrees below the horizon. As default it will
2753 give information for the next three hours for every five minute period.
2755 You can alter the number of hours and the step size, within certain
2758 Each pass in a period is separated with a row of '-----' characters
2763 SH/SAT FENGYUN1 12 2
2765 === 6^SHOW/STARTUP <call>^View a user startup script
2766 === 0^SHOW/STARTUP^View your own startup script
2767 View the contents of a startup script created with SET/STARTUP.
2769 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
2770 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
2771 Show the information known about a callsign and whether (and where)
2772 that callsign is connected to the cluster.
2776 If no callsign is given then show the information for yourself.
2778 === 0^SHOW/SUN [ndays] [<prefix>|<callsign>]^Show sun rise and set times
2779 Show the sun rise and set times for a (list of) prefixes or callsigns,
2780 together with the azimuth and elevation of the sun currently at those
2783 If you don't specify any prefixes or callsigns, it will show the times for
2784 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2785 together with the current azimuth and elevation.
2787 If all else fails it will show the sunrise and set times for the node
2788 that you are connected to.
2793 SH/SUN G1TLH K9CW ZS
2795 You can also use this command to see into the past or the future, so
2796 if you want to see yesterday's times then do:-
2800 or in three days time:-
2804 Upto 366 days can be checked both in the past and in the future.
2806 Please note that the rise and set times are given as the UT times of rise
2807 and set on the requested UT day.
2809 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
2810 If no prefixes or callsigns are given then this command returns the local
2811 time and UTC as the computer has it right now. If you give some prefixes
2812 then it will show UTC and UTC + the local offset (not including DST) at
2813 the prefixes or callsigns that you specify.
2815 === 0^SHOW/USDB [call ..]^Show information held on the FCC Call database
2816 Show the City and State of a Callsign held on the FCC database if
2817 his is being run on this system, eg:-
2821 === 0^SHOW/VHFSTATS [days] [date]^Show the VHF DX Statistics
2822 Show the VHF DX spots breakdown by band for the last
2823 <days> no of days (default is 31), starting from a date (default: today).
2825 === 0^SHOW/VHFTABLE [days] [date] [prefix ...]^Show the VHF DX Spotter Table
2826 Show the VHF DX Spotter table for the list of prefixes for the last
2827 <days> no of days (default is 31), starting from a date (default: today).
2829 If there are no prefixes then it will show the table for your country.
2831 Remember that some countries have more than one "DXCC country" in them
2832 (eg G :-), to show them (assuming you are not in G already which is
2833 specially treated in the code) you must list all the relevant prefixes
2835 sh/vhftable g gm gd gi gj gw gu
2837 Note that the prefixes are converted into country codes so you don't have
2838 to list all possible prefixes for each country.
2840 If you want more or less days than the default simply include the
2841 number you require:-
2845 If you want to start at a different day, simply add the date in some
2848 sh/vhftable 2 25nov02
2849 sh/vhftable 2 25-nov-02
2850 sh/vhftable 2 021125
2851 sh/vhftable 2 25/11/02
2853 This will show the stats for your DXCC for that CQWW contest weekend.
2855 You can specify either prefixes or full callsigns (so you can see how you
2856 did against all your mates). You can also say 'all' which will then print
2857 the worldwide statistics.
2861 === 0^SHOW/WCY^Show last 10 WCY broadcasts
2862 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
2863 Display the most recent WCY information that has been received by the system
2865 === 0^SHOW/WM7D <callsign>^Show callbook details on a US callsigns
2866 This command queries the WM7D callbook server on the internet
2867 and returns any information available for that US callsign. This service
2868 is provided for users of this software by http://www.wm7d.net.
2872 === 0^SHOW/WWV^Show last 10 WWV broadcasts
2873 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
2874 Display the most recent WWV information that has been received by the system
2876 === 5^SHUTDOWN^Shutdown the cluster
2877 Shutdown the cluster and disconnect all the users
2879 === 9^SPOOF <call> <command>^Do a command as though you are another user
2880 This command is provided so that sysops can set a user's parameters without
2881 me having to write a special 'sysop' version for every user command. It
2882 allows you to pretend that you are doing the command as the user you specify.
2886 SPOOF G1TLH set/name Dirk
2887 SPOOF G1TLH set/qra JO02LQ
2889 === 5^STAT/DB <dbname>^Show the status of a database
2890 Show the internal status of a database descriptor.
2892 Depending on your privilege level you will see more or less information.
2893 This command is unlikely to be of much use to anyone other than a sysop.
2895 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
2896 Show the internal status of the channel object either for the channel that
2897 you are on or else for the callsign that you asked for.
2899 Only the fields that are defined (in perl term) will be displayed.
2901 === 1^STAT/MSG^Show the status of the message system
2902 === 1^STAT/MSG <msgno>^Show the status of a message
2903 This command shows the internal status of a message and includes information
2904 such as to whom it has been forwarded, its size, origin etc etc.
2906 If no message number is given then the status of the message system is
2909 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
2910 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
2912 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
2913 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
2915 === 5^STAT/USER [<callsign>]^Show the full status of a user
2916 Shows the full contents of a user record including all the secret flags
2919 Only the fields that are defined (in perl term) will be displayed.
2921 === 0^SYSOP^Regain your privileges if you login remotely
2922 The system automatically reduces your privilege level to that of a
2923 normal user if you login in remotely. This command allows you to
2924 regain your normal privilege level. It uses the normal system: five
2925 numbers are returned that are indexes into the character array that is
2926 your assigned password (see SET/PASSWORD). The indexes start from
2929 You are expected to return a string which contains the characters
2930 required in the correct order. You may intersperse those characters
2931 with others to obscure your reply for any watchers. For example (and
2932 these values are for explanation :-):
2934 password = 012345678901234567890123456789
2938 aa2bbbb0ccc5ddd7xxx3n
2942 They will all match. If there is no password you will still be offered
2943 numbers but nothing will happen when you input a string. Any match is
2946 === 0^TALK <call> [<text>]^Send a text message to another station
2947 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
2948 Send a short message to any other station that is visible on the cluster
2949 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2950 command, they don't have to be connected locally.
2952 The second form of TALK is used when other cluster nodes are connected
2953 with restricted information. This usually means that they don't send
2954 the user information usually associated with logging on and off the cluster.
2956 If you know that G3JNB is likely to be present on GB7TLH, but you can only
2957 see GB7TLH in the SH/C list but with no users, then you would use the
2958 second form of the talk message.
2960 If you want to have a ragchew with someone you can leave the text message
2961 out and the system will go into 'Talk' mode. What this means is that a
2962 short message is sent to the recipient telling them that you are in a
2963 'Talking' frame of mind and then you just type - everything you send will
2964 go to the station that you asked for.
2966 All the usual announcements, spots and so on will still come out on your
2969 If you want to do something (such as send a spot) you preceed the normal
2970 command with a '/' character, eg:-
2972 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2975 To leave talk mode type:
2979 If you are in 'Talk' mode, there is an extention to the '/' command which
2980 allows you to send the output to all the people you are talking to. You do
2981 with the '//' command. For example:-
2985 will send the hftable as you have it to all the people you are currently
2988 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
2989 Type out the contents of a file in a filearea. So, for example, in
2990 filearea 'bulletins' you want to look at file 'arld051' you would
2992 TYPE bulletins/arld051
2994 See also SHOW/FILES to see what fileareas are available and a
2997 === 0^WHO^Show who is physically connected
2998 This is a quick listing that shows which callsigns are connected and
2999 what sort of connection they have
3001 === 0^WX <text>^Send a weather message to local users
3002 === 0^WX FULL <text>^Send a weather message to all cluster users
3003 === 5^WX SYSOP <text>^Send a weather message to other clusters only
3004 Weather messages can sometimes be useful if you are experiencing an extreme
3005 that may indicate enhanced conditions