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 === 9^DOWNLOAD <url>^Download a file into local_data
620 This command is a direct replacement for the unix 'wget -Qn' command
621 that is used to download files like badip, spot data, user databases
622 like usdb. It is designed to work either on the command line in a console
623 or (more likely) in the crontab, like the example below:
625 24 * * * * run_cmd('download http://www.dxspider.net/download/badip.torexit')
626 24 * * * * run_cmd('download http://www.dxspider.net/download/badip.torrelay')
627 24 * * * * run_cmd('download http://www.dxspider.net/download/badip.global')
628 25 * * * * run_cmd('load/badip')
630 If you do use the crontab then *please* use a random minute between 15-40
631 and not all use minute 24.
633 Windows users may well find this particularly useful.
635 === 0^DX <freq> <call> <remarks>^Send a DX spot
636 === 2^DX [BY <call>] [ip <ipaddress>] <freq> <call> <remarks>^Send a DX spot
637 This is how you send a DX Spot to other users. You can, in fact, now
638 enter the <freq> and the <call> either way round.
644 will all give the same result. You can add some remarks to the end
645 of the command and they will be added to the spot.
647 DX FR0G 144600 this is a test
649 You can credit someone else by saying:-
651 DX by G1TLH FR0G 144.600 he isn't on the cluster
653 The <freq> is compared against the available bands set up in the
654 cluster. See SHOW/BANDS for more information.
656 === 9^DXQSL_EXPORT <filename>^Export SH/DXSQL information to a file
657 The SHOW/DXQSL command shows any QSL managers that have been extracted
658 from comments on a DX spot.
660 Use this command to export the current state of the information to
661 a CSV style text file. For example:
663 DXQSL_EXPORT /tmp/qsl.csv
665 NOTE: this command will overwrite any file that you have write
668 See also DXQSL_IMPORT to import one of these files.
670 === 9^DXQSL_IMPORT <filename>^Import SH/DXSQL information from a file
671 The SHOW/DXQSL command shows any QSL managers that have been extracted
672 from comments on a DX spot.
674 Use this command to restore a file created by the DXSQL_EXPORT command.
677 DXQSL_IMPORT /tmp/qsl.csv
679 The data in this file will UPDATE any information that may already be
680 present. This may not be what you want. To make the data the same as
681 the import file then you must:
684 * remove /spider/data/qsl.v1
689 Preferably before too many DX spots with qsl manager info come in.
691 === 0^ECHO <line>^Echo the line to the output
692 This command is useful in scripts and so forth for printing the
693 line that you give to the command to the output. You can use this
694 in user_default scripts and the SAVE command for titling and so forth
696 The script will interpret certain standard "escape" sequences as follows:-
698 \t - becomes a TAB character (0x09 in ascii)
699 \a - becomes a BEEP character (0x07 in ascii)
700 \n - prints a new line
702 So the following example:-
704 echo GB7DJK is a dxcluster
708 GB7DJK is a dxcluster
710 on the output. You don't need a \n on the end of the line you want to send.
712 A more complex example:-
714 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
724 === 9^EXPORT <msgno> <filename>^Export a message to a file
725 Export a message to a file. This command can only be executed on a local
726 console with a fully privileged user. The file produced will be in a form
727 ready to be imported back into the cluster by placing it in the import
728 directory (/spider/msg/import).
730 This command cannot overwrite an existing file. This is to provide some
731 measure of security. Any files written will owned by the same user as the
732 main cluster, otherwise you can put the new files anywhere the cluster can
733 access. For example:-
737 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
738 Export the users database to a file in ascii format. If no filename
739 is given then it will export the file to /spider/data/user_asc.
741 If the file already exists it will be renamed to <filename>.o. In fact
742 up to 5 generations of the file can be kept each one with an extra 'o' on the
745 BE WARNED: this will write to any file you have write access to. No check is
746 made on the filename (if any) that you specify.
748 === 0^FILTERING...^Filtering things in DXSpider
749 There are a number of things you can filter in the DXSpider system. They
750 all use the same general mechanism.
752 In general terms you can create a 'reject' or an 'accept' filter which
753 can have up to 10 lines in it. You do this using, for example:-
758 where ..... are the specific commands for that type of filter. There
759 are filters for spots, wwv, announce, wcy and (for sysops)
760 connects. See each different accept or reject command reference for
763 There is also a command to clear out one or more lines in a filter and
764 one to show you what you have set. They are:-
773 There is clear/xxxx command for each type of filter.
775 For now we are going to use spots for the examples, but you can apply
776 the principles to all types of filter.
778 There are two main types of filter 'accept' or 'reject'; which you use
779 depends entirely on how you look at the world and what is least
780 writing to achieve what you want. Each filter has 10 lines (of any
781 length) which are tried in order. If a line matches then the action
782 you have specified is taken (ie reject means ignore it and accept
785 The important thing to remember is that if you specify a 'reject'
786 filter (all the lines in it say 'reject/spots' (for instance)) then if
787 a spot comes in that doesn't match any of the lines then you will get
788 it BUT if you specify an 'accept' filter then any spots that don't
789 match are dumped. For example if I have a one line accept filter:-
791 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
793 then automatically you will ONLY get VHF spots from or to CQ zones 14
794 15 and 16. If you set a reject filter like:
796 reject/spots on hf/cw
798 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
799 and will work it even on CW then you could say:-
801 reject/spots on hf/cw and not info iota
803 But in that case you might only be interested in iota and say:-
805 accept/spots not on hf/cw or info iota
807 which is exactly the same. You should choose one or the other until
808 you are confortable with the way it works. Yes, you can mix them
809 (actually you can have an accept AND a reject on the same line) but
810 don't try this at home until you can analyse the results that you get
811 without ringing up the sysop for help.
813 Another useful addition now is filtering by US state
815 accept/spots by_state VA,NH,RI,ME
817 You can arrange your filter lines into logical units, either for your
818 own understanding or simply convenience. I have one set frequently:-
820 reject/spots 1 on hf/cw
821 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
823 What this does is to ignore all HF CW spots (being a class B I can't
824 read any CW and couldn't possibly be interested in HF :-) and also
825 rejects any spots on VHF which don't either originate or spot someone
828 This is an exmaple where you would use the line number (1 and 2 in
829 this case), if you leave the digit out, the system assumes '1'. Digits
830 '0'-'9' are available.
832 You can leave the word 'and' out if you want, it is implied. You can
833 use any number of brackets to make the 'expression' as you want
834 it. There are things called precedence rules working here which mean
835 that you will NEED brackets in a situation like line 2 because,
836 without it, will assume:-
838 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
840 annoying, but that is the way it is. If you use OR - use
841 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
844 If you want to alter your filter you can just redefine one or more
845 lines of it or clear out one line. For example:-
847 reject/spots 1 on hf/ssb
853 To remove the filter in its entirty:-
857 There are similar CLEAR commands for the other filters:-
865 Once you are happy with the results you get, you may like to experiment.
867 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
868 can be written with a mixed filter, eg:
872 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
874 each filter slot actually has a 'reject' slot and an 'accept'
875 slot. The reject slot is executed BEFORE the accept slot.
877 It was mentioned earlier that after a reject test that doesn't match,
878 the default for following tests is 'accept', the reverse is true for
879 'accept'. In the example what happens is that the reject is executed
880 first, any non hf/cw spot is passed to the accept line, which lets
881 thru everything else on HF.
883 The next filter line lets through just VHF/UHF spots from EU.
885 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
886 This command sends all the latitude and longitude information that your
887 cluster is holding against callsigns. One advantage of recieving this
888 information is that more locator information is held by you. This
889 means that more locators are given on the DX line assuming you have
890 SET/DXGRID enabled. This could be a LOT of information though, so
891 it is not recommended on slow links.
893 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
894 This command sends out any information held in the user file which can
895 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
896 and Homenode. PC41s are only sent for the information that is available.
898 === 8^GET/KEPS^Obtain the latest AMSAT Keplarian Elements from the web
899 There are various ways that one can obtain the AMSAT keps. Traditionally the
900 regular method was to get on the mailing list and then arrange for the email
901 to be piped into convkeps.pl and arrange from the crontab to run LOAD/KEPS.
902 For various reasons, it was quite easy for one to be silently dropped
903 from this mailing list.
905 With the advent of asynchronous (web) connections in DXSpider it is now
906 possible to use this command to get the latest keps direct from the
907 AMSAT web site. One can do this from the command line or one can add a line
908 in the local DXSpider crontab file to do periodically (say once a week).
910 This command will clear out the existing keps and then run LOAD/KEPS
911 for you (but only) after a successful download from the AMSAT website.
913 === 0^HELP^The HELP Command
914 HELP is available for a number of commands. The syntax is:-
918 Where <cmd> is the name of the command you want help on.
920 All commands can be abbreviated, so SHOW/DX can be abbreviated
921 to SH/DX, ANNOUNCE can be shortened to AN and so on.
923 Look at the APROPOS <string> command which will search the help database
924 for the <string> you specify and give you a list of likely commands
925 to look at with HELP.
927 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
928 This command attempts to re-initialise a link to a (usually) AK1A node
929 that has got confused, usually by a protocol loop of some kind. It may
930 work - but you usually will be better off simply disconnecting it (or
931 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
934 Best of luck - you will need it.
936 === 9^DEMONSTRATE <call> <command>^Demonstrate a command to another user
937 This command is provided so that sysops can demonstrate commands to
938 other users. It runs a command as though that user had typed it in and
939 then sends the output to that user, together with the command that
942 DEMO g7brn sh/dx iota oc209
945 Note that this command is similar to SPOOF and will have the same side
946 effects. Commands are run at the privilege of the user which is being
949 === 0^JOIN <group>^Join a chat or conference group
950 JOIN allows you to join a network wide conference group. To join a
951 group (called FOC in this case) type:-
955 See also CHAT, LEAVE, SHOW/CHAT
957 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
958 === 0^KILL <from msgno>-<to msgno>^Delete a range of messages
959 === 0^KILL from <regex>^Delete messages FROM a callsign or pattern
960 === 0^KILL to <regex>^Delete messages TO a callsign or pattern
961 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
962 Delete a message from the local system. You will only be able to
963 delete messages that you have originated or been sent (unless you are
968 Will delete all the messages that you own between msgnos 1234 and 1255.
972 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
976 will delete all messages to g1tlh.
980 will delete a message (usually a 'bulletin') from the whole cluster system.
982 This uses the subject field, so any messages that have exactly the
983 same subject will be deleted. Beware!
985 === 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
986 Deleting a message using the normal KILL commands only marks that message
987 for deletion. The actual deletion only happens later (usually two days later).
989 The KILL EXPUNGE command causes the message to be truly deleted more or less
992 It otherwise is used in the same way as the KILL command.
994 === 0^LEAVE <group>^Leave a chat or conference group
995 LEAVE allows you to leave a network wide conference group. To leave a
996 group (called FOC in this case) type:-
1000 See also CHAT, JOIN, SHOW/CHAT
1002 === 0^LINKS^Show which nodes is physically connected
1003 This is a quick listing that shows which links are connected and
1004 some information about them. See WHO for a list of all connections.
1006 === 9^LOAD/ALIASES^Reload the command alias table
1007 Reload the /spider/cmd/Aliases file after you have editted it. You
1008 will need to do this if you change this file whilst the cluster is
1009 running in order for the changes to take effect.
1011 === 9^LOAD/BANDS^Reload the band limits table
1012 Reload the /spider/data/bands.pl file if you have changed it manually whilst
1013 the cluster is running.
1015 === 6^LOAD/BADIP^Reload the bad IP address table
1016 Reload the badip address file(s) if you have changed any of them manually
1017 whilst the cluster is running.
1019 You can edit the badip.* files manually in local_data or (for instance)
1020 obtain some bad IP addresses from the web to replace badip.base for TOR
1021 IP addresses (this filename may change).
1023 There is (currently) no UNSET/BADIP command so you will need to edit
1024 the badip.local file to remove IP addresses.
1026 After modification, you can reload the database with:
1030 === 9^LOAD/BADMSG^Reload the bad msg table
1031 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
1032 the cluster is running. This table contains a number of perl regular
1033 expressions which are searched for in the fields targetted of each message.
1034 If any of them match then that message is immediately deleted on receipt.
1036 === 9^LOAD/BADWORDS^Reload the bad words table
1037 Reload the /spider/data/badwords file if you have changed it manually whilst
1038 the cluster is running. This file contains a list of words which, if found
1039 on certain text portions of PC protocol, will cause those protocol frames
1040 to be rejected. It will all put out a message if any of these words are
1041 used on the announce, dx and talk commands. The words can be one or
1042 more on a line, lines starting with '#' are ignored.
1044 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
1045 Normally, if you change a command file in the cmd or local_cmd tree it
1046 will automatially be picked up by the cluster program. Sometimes it
1047 can get confused if you are doing a lot of moving commands about or
1048 delete a command in the local_cmd tree and want to use the normal one
1049 again. Execute this command to reset everything back to the state it
1050 was just after a cluster restart. To see what is in the command cache
1053 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
1054 Reload the /spider/msg/forward.pl file if you have changed it
1055 manually whilst the cluster is running.
1057 === 5^LOAD/KEPS^Load new keps data
1058 === 5^LOAD/KEPS [nn]^Load new keps data from message
1059 If there is no message number then reload the current Keps data from
1060 the Keps.pm data file. You create this file by running
1062 /spider/perl/convkeps.pl <filename>
1064 on a file containing NASA 2 line keps as a message issued by AMSAT.
1066 If there is a message number, then it will take the message, run
1067 convkeps.pl on it and then load the data, all in one step.
1069 These messages are sent to ALL by GB7DJK (and others) from time to time.
1071 === 9^LOAD/MESSAGES^Reload the system messages file
1072 If you change the /spider/perl/Messages file (usually whilst
1073 fiddling/writing new commands) you can have them take effect during a
1074 cluster session by executing this command. You need to do this if get
1077 unknown message 'xxxx' in lang 'en'
1079 === 9^LOAD/PREFIXES^Reload the prefix table
1080 Reload the /spider/data/prefix_data.pl file if you have changed it
1081 manually whilst the cluster is running.
1083 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
1084 MERGE allows you to bring your spot and wwv database up to date. By default
1085 it will request the last 10 spots and 5 WWVs from the node you select. The
1086 node must be connected locally.
1088 You can request any number of spots or wwv and although they will be appended
1089 to your databases they will not duplicate any that have recently been added
1090 (the last 2 days for spots and last month for WWV data).
1092 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
1093 Alter message parameters like To, From, Subject, whether private or bulletin
1094 or return receipt (RR) is required or whether to keep this message from timing
1097 MSG TO <msgno> <call> - change TO callsign to <call>
1098 MSG FRom <msgno> <call> - change FROM callsign to <call>
1099 MSG PRrivate <msgno> - set private flag
1100 MSG NOPRrivate <msgno> - unset private flag
1101 MSG RR <msgno> - set RR flag
1102 MSG NORR <msgno> - unset RR flag
1103 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
1104 MSG NOKEep <msgno> - unset the keep flag
1105 MSG SUbject <msgno> <new> - change the subject to <new>
1106 MSG WAittime <msgno> - remove any waitting time for this message
1107 MSG NOREad <msgno> - mark message as unread
1108 MSG REad <msgno> - mark message as read
1109 MSG QUeue - queue any outstanding bulletins
1110 MSG QUeue 1 - queue any outstanding private messages
1112 You can look at the status of a message by using:-
1116 This will display more information on the message than DIR does.
1118 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
1119 Send some arbitrary text to a locally connected callsign. No
1120 processing is done on the text. This command allows you to send PC
1121 Protocol to unstick things if problems arise (messages get stuck
1124 pc gb7djk PC33^GB7TLH^GB7DJK^400^
1126 pc G1TLH Try doing that properly!!!
1128 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
1129 You can get rid of any message to or originating from your callsign using
1130 this command. You can remove more than one message at a time.
1132 === 5^KILL <from>-<to>^Remove a range of messages from the system
1133 === 5^KILL FROM <call>^Remove all messages from a callsign
1134 === 5^KILL TO <call>^Remove all messages to a callsign
1135 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
1136 Remove this message from the entire cluster system as well as your node.
1139 As a sysop you can kill any message on the system.
1141 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
1142 Send any text you like to the callsign requested. This is used mainly to send
1143 PC protocol to connected nodes either for testing or to unstick things.
1145 You can also use in the same way as a talk command to a connected user but
1146 without any processing, added of "from <blah> to <blah" or whatever.
1148 === 0^PING [argument]^User level link check command
1149 At the user level, this command allows the user to check that they
1150 are still connected to a functioning node. If the command is
1151 issued with no arguments it will return string 'PONG 123' where
1152 '123' is a node global counter starting at 1. This number cannot
1153 be relied to run consecutively as it is shared by all users.
1155 If an argument is supplied then the return is 'PONG ARGUMENT'. So it
1156 you are a client program and you need a counter or some other unique
1157 string to satisfy yourself that you are not being spoofed, then you
1158 will need to supply the argument and check that reply is what you
1161 ping 23 or ping xyzzy
1165 PONG 23 or PONG XYZZY
1169 === 1^PING <node call>^Check the link quality between nodes
1170 This command allows you to send a frame to another cluster node on
1171 the network and get a return frame. The time it takes to do this
1172 is a good indication of the quality of the link. The actual time
1173 it takes is output to the console in seconds.
1174 Any visible cluster node can be PINGed.
1176 === 0^RBN^The Reverse Beacon or Skimmer System
1177 DXSpider now has the ability to show spots from the Reverse Beacon Network
1178 or "Skimmers", if your sysop has enabled the feed(s) (and has the bandwidth
1179 to both receive the feeds and also to pass them on to you.
1181 Currently there are two RBN/Skimmer feeds available which, at busy
1182 times can send up to 50,000 spots/hour EACH. Somewhere in the low
1183 1000s is more normal. Clearly this is not much use to the average user
1184 and so DXSpider "curates" them by removing duplicates and checking for
1185 invalid callsigns or prefixes, as well as using some algorithms to fix
1186 the rather variable frequencies that some skimmers produce
1187 (particularly for CW spots).
1189 This means that the format of the spot that you see is completely
1190 different to the spots that the RBN feeds supply and, as a result of
1191 the "curation" reduces the volume of spots to you by between 8 and 11
1194 See SET/SKIMMER (or SET/WANTRBN) for more information on enabling
1195 RBN/Skimmer spots and also on selecting particular categories (e.g CW
1196 or FT8/FT4) - which has the side benefit of reducing the volume of
1197 spots that you receive even more!
1199 Here are some examples of the output:
1201 DX de LZ4UX-#: 14015.5 ON7TQ CW 6dB Q:9 Z:5,14,15,40 14 0646Z 20
1202 DX de VE7CC-#: 3573.0 N8ADO FT8 -14dB Q:4 Z:4,5 4 0647Z 3
1203 DX de DM7EE-#: 14027.5 R1AC CW 9dB Q:9* Z:5,15,17,20 16 0643Z 14
1204 DX de WE9V-#: 7074.0 EA7ALL FT8 -9dB Q:2+ Z:5 14 0641Z 4
1206 Note that UNSET/DXGRID, UNSET/DXITU and SET/DXCQ are in operation in
1207 these examples. This is completely optional.
1209 The comment field has been completely changed in order provide as much
1210 information, in as smaller space, as possible. All the irrelevant
1211 information has been removed.
1213 You can use the Category (CW and FT8 in these examples) to with
1214 SET/SKIMMER (or SET/WANTRBN) to, rather coarsely, select which spots
1215 you require. You can refine this further by the use of Filtering. See
1216 SET/SKIMMER or SET/WANTRBN for more information. But the short answer
1217 is that these are spots and are filtered like any other spot, unless
1218 you want to filter these spots differently, in which case you can use
1219 REJECT/RBN and ACCEPT/RBN in exactly the same way as ACCEPT/SPOT and
1220 REJECT/SPOT. If you don't use RBN filters then these spots will be
1221 filter by any spot filters that you may have.
1223 The next field (6dB, -14dB etc) is the LOWEST reported signal that was
1226 The Q: field is the number of skimmers that heard this spot (up to 9
1227 shown, but it could easily be many more). If Q: is > 1 (especially on
1228 CW) then you can be reasonably certain that the callsign is accurate,
1229 especially on CW. 'Q' stands for "Qualitee" :-)
1231 If there is a '*', it means that there was a disagreement about
1232 frequency. In fact, particularly for CW spots, I have see
1233 disagreements of 600Hz. Which is a worry. The frequency that is shown
1234 is the majority view of all the skimmers spotting this call. You may
1235 have to fossick about the airwaves to find the actual frequency :-)
1237 There are stations that are permanently on, like Beacons, and also
1238 others that have long sessions on the same frequency and do a lot of
1239 CQing. If they have been on for a certain length of time and they
1240 reappear before their cache entry expires (about 2 hours), then they
1241 are respotted. This is indicated by the '+'. NOTE - if they change
1242 frequency, this will generate new spots. Each callsign/frequency pair
1243 could respotted separately for as long as any individual
1244 callsign/frequency pair remain in the cache.
1246 The Z: field is present then that indicates the other CQ zones that
1247 heard this spot - not including the skimmer that is shown. I show as
1248 many as there are in whatever space is left in the comment
1249 field. Note: if you have any of the optional flags around the time
1250 then they may overwrite part of this field.
1252 If there is NO filter in operation, then the skimmer spot with the
1253 LOWEST signal strength will be shown. This implies that if any extra
1254 Z: zones are shown, then the signal will be higher in those zones.
1256 If you have a filter (for instance: ACCEPT/SPOT by_zone 14 and not
1257 zone 14 or zone 14 and not by_zone 14) where '14' is your QTH CQ
1258 zone. You will, instead be served with the lowest signal strength spot
1259 that satisfies that filter. Incidentally, this particular style of
1260 filter is quite useful for RBN spots, as it reduces the volume and is
1261 likely to be more relevant for casual use. If this filter is too broad
1262 (or narrow) for your normal spotting requirements, then you can use
1263 ACCEPT/RBN with the same filter specification and it will only apply
1264 to RBN spots. You can also replace '14' with a list like '14,15' if
1265 you want to broaden it out. You will still get the same Z: list (if
1266 any) whether you filter or not.
1268 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
1269 This command allows you to send nearly any command to another DX Cluster
1270 node that is connected to the system.
1272 Whether you get any output is dependant on a) whether the other system knows
1273 that the node callsign of this cluster is in fact a node b) whether the
1274 other system is allowing RCMDs from this node and c) whether you have
1275 permission to send this command at all.
1277 === 0^READ^Read the next unread personal message addressed to you
1278 === 0^READ <msgno>^Read the specified message
1279 You can read any messages that are sent as 'non-personal' and also any
1280 message either sent by or sent to your callsign.
1283 As a sysop you may read any message on the system
1285 === 0^REJECT^Set a filter to reject something
1286 Create a filter to reject something
1288 There are 2 types of filter, accept and reject. See HELP FILTERING for more
1291 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
1292 Create an 'reject this announce' line for a filter.
1294 A reject filter line means that if the announce matches this filter it is
1295 passed onto the user. See HELP FILTERING for more info. Please read this
1296 to understand how filters work - it will save a lot of grief later on.
1298 You can use any of the following things in this line:-
1300 info <string> eg: iota or qsl
1301 by <prefixes> eg: G,M,2
1303 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1304 origin_itu <prefixes or numbers> or: G,GM,GW
1305 origin_zone <prefixes or numbers>
1306 origin_state <states> eg: VA,NH,RI,ME
1307 by_dxcc <prefixes or numbers>
1308 by_itu <prefixes or numbers>
1309 by_zone <prefixes or numbers>
1310 by_state <states> eg: VA,NH,RI,ME
1312 wx 1 filter WX announces
1313 dest <prefixes> eg: 6MUK,WDX (distros)
1317 rej/ann by_zone 14,15,16 and not by G,M,2
1319 You can use the tag 'all' to reject everything eg:
1323 but this probably for advanced users...
1325 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
1326 This version allows a sysop to set a filter for a callsign as well as the
1327 default for nodes and users eg:-
1330 reject/ann input node_default by G,M,2
1331 reject/ann user_default by G,M,2
1333 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
1334 === 0^REJECT/RBN [0-9] <pattern>^Set a 'reject' filter line for RBN spots
1335 Create a 'reject this spot' line for a filter.
1337 A reject filter line means that if the spot matches this filter it is
1338 dumped (not passed on). See HELP FILTERING for more info. Please read this
1339 to understand how filters work - it will save a lot of grief later on.
1341 You can use any of the following things in this line:-
1343 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1344 on <range> same as 'freq'
1345 call <prefixes> eg: G,PA,HB9
1346 info <string> eg: iota or qsl
1348 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1349 call_itu <prefixes or numbers> or: G,GM,GW
1350 call_zone <prefixes or numbers>
1351 call_state <states> eg: VA,NH,RI,ME
1352 by_dxcc <prefixes or numbers>
1353 by_itu <prefixes or numbers>
1354 by_zone <prefixes or numbers>
1355 by_state <states> eg: VA,NH,RI,ME
1359 'call' means the callsign that has spotted 'by' whoever.
1361 For frequencies, you can use any of the band names defined in
1362 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1363 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1364 this is more efficient than saying simply: on HF (but don't get
1365 too hung up about that)
1370 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1372 You can use the tag 'all' to reject everything eg:
1376 but this probably for advanced users...
1378 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
1379 Create an 'reject this routing PC Protocol' line for a filter.
1381 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1382 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1383 read this to understand how filters work - it will save a lot of grief later on.
1385 You can use any of the following things in this line:-
1387 call <prefixes> the callsign of the thingy
1388 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1389 call_itu <prefixes or numbers> or: G,GM,GW
1390 call_zone <prefixes or numbers>
1391 call_state <states> eg: VA,NH,RI,ME
1392 origin <prefixes> really the interface it came in on
1393 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1394 origin_itu <prefixes or numbers> or: G,GM,GW
1395 origin_zone <prefixes or numbers>
1396 origin_state <states> eg: VA,NH,RI,ME
1400 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1402 You can use the tag 'all' to reject everything eg:
1404 rej/route all (equiv to [very] restricted mode)
1406 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
1408 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
1409 This version allows a sysop to set a filter for a callsign as well as the
1410 default for nodes and users eg:-
1412 reject/spot db0sue-7 1 by_zone 14,15,16
1413 reject/spot node_default all
1414 set/hops node_default 10
1416 reject/spot user_default by G,M,2
1418 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
1419 It is unlikely that you will want to do this, but if you do then you can
1420 filter on the following fields:-
1422 by <prefixes> eg: G,M,2
1424 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1425 origin_itu <prefixes or numbers> or: G,GM,GW
1426 origin_zone <prefixes or numbers>
1427 by_dxcc <prefixes or numbers>
1428 by_itu <prefixes or numbers>
1429 by_zone <prefixes or numbers>
1432 There are no examples because WCY Broadcasts only come from one place and
1433 you either want them or not (see UNSET/WCY if you don't want them).
1435 This command is really provided for future use.
1437 See HELP FILTER for information.
1439 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
1440 This version allows a sysop to set a filter for a callsign as well as the
1441 default for nodes and users eg:-
1443 reject/wcy gb7djk all
1445 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
1446 It is unlikely that you will want to do this, but if you do then you can
1447 filter on the following fields:-
1449 by <prefixes> eg: G,M,2
1451 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1452 origin_itu <prefixes or numbers> or: G,GM,GW
1453 origin_zone <prefixes or numbers>
1454 by_dxcc <prefixes or numbers>
1455 by_itu <prefixes or numbers>
1456 by_zone <prefixes or numbers>
1461 reject/wwv by_zone 14,15,16
1463 is probably the only useful thing to do (which will only show WWV broadcasts
1464 by stations in the US).
1466 See HELP FILTER for information.
1468 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
1469 This version allows a sysop to set a filter for a callsign as well as the
1470 default for nodes and users eg:-
1472 reject/wwv db0sue-7 1 by_zone 4
1473 reject/wwv node_default all
1475 reject/wwv user_default by W
1477 === 0^REPLY^Reply (privately) to the last message that you have read
1478 === 0^REPLY <msgno>^Reply (privately) to the specified message
1479 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1480 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1481 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1482 You can reply to a message and the subject will automatically have
1483 "Re:" inserted in front of it, if it isn't already present.
1485 You can also use all the extra qualifiers such as RR, PRIVATE,
1486 NOPRIVATE, B that you can use with the SEND command (see SEND
1487 for further details)
1489 === 9^SAVE [-d -t -a] <filename> "<cmd>" [...]^Save command output to a file
1490 This sysop only cammand allows you to save the output of one or more
1491 commands to a file. For example:-
1493 save /spider/packclus/dxstats show/dxstat
1495 will save the output of the normal command "show/dxstat" to the file
1496 "dxstats" in the files area.
1498 You can have some extra flags to the save which will either
1499 date stamp or time stamp or both the filename so:-
1501 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
1502 save -t /tmp/a <cmd> creates /tmp/a_2301Z
1503 save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
1505 The -a flag means append to the file instead of overwriting it.
1507 You can have more than one command on the line, to do this you MUST
1508 enclose each command in double quotes (") eg:-
1510 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
1514 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
1516 You can only write into places that the cluster has permission for (which
1517 is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
1518 need to create any directories you want to put stuff in beforehand as well.
1520 It is likely that you will want to run these commands in a crontab type
1521 situation. You would do that something like:-
1523 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
1525 Note that you still enclose each command with (") characters but you must
1526 enclose the entire save command in (') characters.
1528 Now in fact, this can be varied if you know what you are doing. See the
1529 admin manual for more details.
1531 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1532 === 0^SEND RR <call>^Send a message and ask for a read receipt
1533 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1534 === 0^SEND PRIVATE <call>^Send a personal message
1535 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1536 All the SEND commands will create a message which will be sent either to
1537 an individual callsign or to one of the 'bulletin' addresses.
1539 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1540 it will mark the message as personal and send it to the cluster node that
1541 that callsign is connected to. If the <call> you have specified is in fact
1542 a known bulletin category on your node (eg: ALL) then the message should
1543 automatically become a bulletin.
1545 You can have more than one callsign in all of the SEND commands.
1547 You can have multiple qualifiers so that you can have for example:-
1549 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1551 which should send a copy of message 123 to G1TLH and G0RDI and you will
1552 receive a read receipt when they have read the message.
1554 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1555 SP is an alias for SEND PRIVATE
1557 The system will ask you for a subject. Conventionally this should be
1558 no longer than 29 characters for compatibility. Most modern cluster
1559 software should accept more.
1561 You will now be prompted to start entering your text.
1563 You finish the message by entering '/EX' on a new line. For instance:
1570 If you have started a message and you don't want to keep it then you
1571 can abandon the message with '/ABORT' on a new line, like:-
1575 oh I just can't be bothered with this
1578 If you abort the message it will NOT be sent.
1580 When you are entering the text of your message, most normal output (such
1581 as DX announcements and so on are suppressed and stored for latter display
1582 (upto 20 such lines are stored, as new ones come along, so the oldest
1585 Also, you can enter normal commands commands (and get the output
1586 immediately) whilst in the middle of a message. You do this by typing
1587 the command preceeded by a '/' character on a new line, so:-
1589 /dx g1tlh 144010 strong signal
1591 Will issue a dx annoucement to the rest of the cluster.
1593 Also, you can add the output of a command to your message by preceeding
1594 the command with '//', thus :-
1598 This will show YOU the output from SH/VHFTABLE and also store it in the
1601 You can carry on with the message until you are ready to send it.
1603 === 6^SEND_CONFIG^Broadcast PC92 C records
1604 This is the PC92 equivalent of INIT. In that it will send out a new
1605 PC92 C record to all interfaces. This can be used to bring other nodes
1606 up to date quicker after a restart.
1608 === 0^SET/ADDRESS <your address>^Record your postal address
1610 === 9^SET/AGWENGINE^Enable the AGW Engine
1611 === 9^UNSET/AGWENGINE^Disable the AGW Engine
1612 These commands assume that /spider/local/AGWConnect.pm has been setup
1613 correctly and you wish to do some testing or otherwise want to alter
1614 the default state of your connection to the AGW Engine.
1616 === 9^SET/AGWMONITOR^Enable Monitoring on the AGW Engine
1617 === 9^UNSET/AGWMONITOR^Disable Monitoring on the AGW Engine
1619 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1620 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1622 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1623 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1624 The announce system on legacy cluster nodes is used as a talk
1625 substitute because the network is so poorly connected. If you:
1629 you will suppress several of these announces, you may miss the odd
1630 useful one as well, but you would probably miss them anyway in the
1631 welter of useless ones.
1635 allows you to see them again. This is the default.
1637 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1639 === 6^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1640 === 6^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1641 Setting a word as 'baddx' will prevent spots with that word in the
1642 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1643 further. They will not be displayed and they will not be sent onto
1646 The word must be written in full, no wild cards are allowed eg:-
1648 set/baddx FORSALE VIDEO FR0G
1650 To allow a word again, use the following command ...
1654 === 6^SET/BADIP <ip address>..^Stop logins and spots with this IP address
1655 This command will prevent logins to this node from this IP address.
1656 It will also drop spots (PC61) from this address thus preventing them
1657 from being propagated.
1659 set/badip 217.61.58.23
1661 === 6^SET/BADNODE <call>..^Stop spots from this node being propagated
1662 === 6^UNSET/BADNODE <call>..^Allow spots from this node again
1663 Setting a callsign as a 'badnode' will prevent spots from that node
1664 going any further. They will not be displayed and they will not be
1665 sent onto other nodes.
1667 The call must be a full eg:-
1671 will stop anything from K1TTT. If you want SSIDs as well then you must
1672 enter them specifically.
1676 will allow spots from him again.
1678 Use with extreme care. This command may well be superceeded by FILTERing.
1680 === 6^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1681 === 6^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1682 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1683 going any further. They will not be displayed and they will not be
1684 sent onto other nodes.
1686 The call must be written in full, no wild cards are allowed eg:-
1688 set/badspotter VE2STN
1690 will stop anything from VE2STN. This command will automatically
1691 stop spots from this user, regardless of whether or which SSID
1692 he uses. DO NOT USE SSIDs in the callsign, just use the callsign
1695 unset/badspotter VE2STN
1697 will allow spots from him again.
1699 Use with extreme care. This command may well be superceded by FILTERing.
1701 This command will also stop TALK and ANNOUNCE/FULL from any user marked
1704 === 6^SET/BADWORD <word>..^Stop things like this word being propagated
1705 Setting a word as a 'badword' will prevent things like spots,
1706 announces or talks with this word in the the text part from going any
1707 further. They will not be displayed and they will not be sent onto
1710 This has changed its meaning from the master release. All words entered
1711 are reduced to the minimum regex that will match words starting like
1714 set/badword annihilate
1716 will stop anything that starts with these words in the text
1719 annihilate annihilated
1721 but it will also stop things like this:
1723 anihilate annni11ihhh ii lllattt eee
1725 A few common 'leet' substitutions are automatically matched:
1727 b0ll0cks bo0lll0ccckks fr1iigging
1731 It will not stop some things like:
1733 The base word FRIG will stop 'friiigging' but not 'friiig ging'
1735 === 6^UNSET/BADWORD <word>..^Propagate things like this word again
1736 This is the opposite of set/badword <word>
1740 will allow text with this word again (if it has been set as a bad word.
1742 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1743 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1745 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1747 === 0^SET/BUDDY <call> [<call>..]^Add this call to my buddy list
1748 === 0^UNSET/BUDDY <call> [<call>..]^Remove this call from my buddy list
1749 A notification message
1750 is sent to you automatically if anybody on your buddy list logs in or
1751 out of any node in this cluster.
1753 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1755 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1756 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1757 You can choose to log several different levels. The levels are
1765 You can show what levels you are logging with SHOW/DEBUG
1767 === 0^SET/DX^Allow DX messages to come out on your terminal
1768 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1770 === 0^SET/DXCQ^Show CQ Zones on the end of DX announcements
1771 === 0^UNSET/DXCQ^Stop CQ Zones on the end of DX announcements
1772 Display both the Spotter's and the Spotted's CQ Zone on the end
1773 of a DX announcement (there is just enough room). Some user programs
1774 cannot cope with this. The Spotter's CQ is on the RHS of the
1775 time, the Spotted's CQ is on the LHS.
1777 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
1779 Do a STAT/USER to see which flags you have set if you are confused.
1781 === 0^SET/DXITU^Show ITU Zones on the end of DX announcements
1782 === 0^UNSET/DXITU^Stop ITU Zones on the end of DX announcements
1783 Display both the Spotter's and the Spotted's ITU Zone on the end
1784 of a DX announcement (there is just enough room). Some user programs
1785 cannot cope with this. The Spotter's ITU is on the RHS of the
1786 time, the Spotted's ITU is on the LHS.
1788 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
1790 Do a STAT/USER to see which flags you have set if you are confused.
1792 === 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
1793 === 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
1794 A standard feature which is enabled in version 1.43 and above is
1795 that if the spotter's grid square is known it is output on the end
1796 of a DX announcement (there is just enough room). Some user programs
1797 cannot cope with this. You can use this command to reset (or set)
1800 Conflicts with: SET/DXCQ, SET/DXITU
1802 Do a STAT/USER to see which flags you have set if you are confused.
1804 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1806 === 0^SET/ECHO^Make the cluster echo your input
1807 === 0^UNSET/ECHO^Stop the cluster echoing your input
1808 If you are connected via a telnet session, different implimentations
1809 of telnet handle echo differently depending on whether you are
1810 connected via port 23 or some other port. You can use this command
1811 to change the setting appropriately.
1813 The setting is stored in your user profile.
1815 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1817 === 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
1818 === 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
1819 If any personal messages come in for your callsign then you can use
1820 these commands to control whether they are forwarded onto your email
1821 address. To enable the forwarding do something like:-
1823 SET/EMAIL mike.tubby@somewhere.com
1825 You can have more than one email address (each one separated by a space).
1826 Emails are forwarded to all the email addresses you specify.
1828 You can disable forwarding by:-
1832 === 0^SET/HERE^Tell the system you are present at your terminal
1833 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1835 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1836 Tell the cluster system where you normally connect to. Any Messages sent
1837 to you will normally find their way there should you not be connected.
1841 === 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
1842 === 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
1843 Set the hop count for a particular type of broadcast for a node.
1845 This command allows you to set up special hop counts for a node
1846 for currently: announce, spots, wwv and wcy broadcasts.
1849 set/hops gb7djk ann 10
1850 set/hops gb7mbc spots 20
1852 Set SHOW/HOPS for information on what is already set. This command
1853 creates a filter and works in conjunction with the filter system.
1855 You can unset the hops with command UNSET/HOPS. For example:-
1857 unset/hops gb7djk ann
1858 unset/hops gb7mbc spots
1861 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1862 Connect a node to your system in such a way that you are a full protocol
1863 member of its network and can see all spots on it, but nothing either leaks
1864 out from it nor goes back into from the rest of the nodes connected to you.
1866 You can potentially connect several nodes in this way.
1868 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1869 Remove isolation from a node - SET/ISOLATE
1871 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1872 You can select the language that you want the cluster to use. Currently
1873 the languages available are en (English), de (German), es (Spanish),
1874 Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
1876 === 5^SET/LOCAL_NODE^Add node to the local_node group
1877 === 5^UNSET/LOCAL_NODE^Remove node from the local_node group
1878 The 'local_node' group is a group of nodes that you want a user
1879 to perceive as effectively one big node. At the moment, this extends
1880 only to announcing whenever a user is logging in or out of one of
1881 the nodes in the group (if those users have SET/LOGININFO).
1883 The local node group is as setup on this node. If you want the other
1884 nodes to also include this node and all the other nodes specified, then
1885 you must get those nodes to also run this command (or rcmd them to do
1888 In principle, therefore, each node determines its own local node group
1889 and these can overlap with other nodes' views.
1891 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1892 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1893 In order to get accurate headings and such like you must tell the system
1894 what your latitude and longitude is. If you have not yet done a SET/QRA
1895 then this command will set your QRA locator for you. For example:-
1896 SET/LOCATION 52 22 N 0 57 E
1898 === 0^SET/LOGININFO^Inform when a station logs in/out locally
1899 === 0^UNSET/LOGININFO^No longer inform when a station logs in/out locally
1901 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1902 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1904 === 8^SET/MAXCONNECT <value> [<call> ..]^Set max incoming connections for user/node
1905 Set the maximum no of connections (parents) an incoming user or node is
1906 allowed to have. If this incoming connection takes it over the separate
1907 limits for users and nodes (defaults: 3 and 8 respectively), then the
1908 connection is refused (with a polite message).
1910 The idea behind this to limit the number of copies of messages that
1911 are sent to users (and nodes). Nodes really don't need to have more than
1912 5 or 6 partners and users don't need more than two connections into the
1915 This check is only for INCOMING connections, no check is performed for
1916 outgoing connections.
1918 === 0^SET/NAME <your name>^Set your name
1919 Tell the system what your name is eg:-
1922 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1923 Tell the system that the call(s) are to be treated as AK1A cluster and
1924 fed PC Protocol rather normal user commands.
1926 === 8^SET/OBSCOUNT <count> <call>^Set the 'pump-up' obscelence PING counter
1927 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1928 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1929 counter which is decremented on every outgoing ping and then reset to
1930 the 'obscount' value on every incoming ping. The default value of this
1933 What this means is that a neighbouring node will be pinged twice at
1934 (default) 300 second intervals and if no reply has been heard just before
1935 what would be the third attempt, that node is disconnected.
1937 If a ping is heard then the obscount is reset to the full value. Using
1938 default values, if a node has not responded to a ping within 15 minutes,
1941 You can set this parameter between 1 and 9.
1943 It is STRONGLY recommended that you don't change the default.
1945 === 0^SET/PAGE <lines per page>^Set the lines per page
1946 Tell the system how many lines you wish on a page when the number of line
1947 of output from a command is more than this. The default is 20. Setting it
1948 explicitly to 0 will disable paging.
1952 The setting is stored in your user profile.
1954 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1955 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1956 in order to determine the rolling quality of the link and, in future, to
1957 affect routing decisions. The default interval is 300 secs or 5 minutes.
1959 You can use this command to set a different interval. Please don't.
1961 But if you do the value you enter is treated as minutes up 30 and seconds
1962 for numbers greater than that.
1964 This is used also to help determine when a link is down at the far end
1965 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1966 for more information.
1968 If you must change it (and it may be useful for internet connected nodes
1969 on dynamic IP addresses that go away after a set time of usage) the time
1970 can be specified as:-
1972 5 which if less than 30 is converted to minutes otherwise is
1973 taken as the no of seconds between pings.
1978 Please be aware that this causes traffic to occur on the link, setting
1979 this value too low may annoy your neighbours beyond the point of
1982 You can switch this off by setting it to 0.
1984 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1985 Set the privilege level on a callsign. The privilege levels that pertain
1986 to commands are as default:-
1988 1 - allow remote nodes normal user RCMDs
1989 5 - various privileged commands (including shutdown, but not disc-
1990 connect), the normal level for another node.
1991 8 - more privileged commands (including disconnect)
1992 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1994 If you are a sysop and you come in as a normal user on a remote connection
1995 your privilege will automatically be set to 0.
1997 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1998 You can use this command to 'protect' this session from unauthorised
1999 use. If you want to get your normal privilege back you will need to
2000 either logout and login again (if you are on a console) or use the
2003 === 9^SET/PASSWORD <callsign> <string>^Set a users password
2004 The password for a user can only be set by a full sysop. The string
2005 can contain any characters.
2007 The way this field is used depends on context. If it is being used in
2008 the SYSOP command context then you are offered 5 random numbers and you
2009 have to supply the corresponding letters. This is now mainly for ax25
2012 If it is being used on incoming telnet connections then, if a password
2015 set/var $main::passwdreq = 1
2017 command is executed in the startup script, then a password prompt is
2018 given after the normal 'login: ' prompt.
2020 === 0^SET/PASSWORD^Set your own password
2021 This command only works for a 'telnet' user (currently). It will
2022 only work if you have a password already set. This initial password
2023 can only be set by the sysop.
2025 When you execute this command it will ask you for your old password,
2026 then ask you to type in your new password twice (to make sure you
2027 get it right). You may or may not see the data echoed on the screen
2028 as you type, depending on the type of telnet client you have.
2030 === 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
2031 This command allows the sysop to completely delete and remove a
2032 password for a user.
2034 === 0^SET/PROMPT <string>^Set your prompt to <string>
2035 === 0^UNSET/PROMPT^Set your prompt back to default
2036 This command will set your user prompt to the string that you
2037 say. The point of this command to enable a user to interface to programs
2038 that are looking for a specific prompt (or else you just want a different
2043 There are some substitutions that can be added to the prompt:
2045 %C - callsign [which will have ( and ) around it if not here]
2048 %M - cluster 'mycall'
2050 The standard prompt is defined as:
2052 SET/PROMPT %C de %M %D %T dxspider >
2054 UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to
2057 === 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
2058 === 0^SET/QRA <locator>^Set your QRA Grid locator
2059 Tell the system what your QRA (or Maidenhead) locator is. If you have not
2060 done a SET/LOCATION then your latitude and longitude will be set roughly
2061 correctly (assuming your locator is correct ;-). For example:-
2064 === 0^SET/QTH <your qth>^Set your QTH
2065 Tell the system where you are. For example:-
2066 SET/QTH East Dereham, Norfolk
2068 === 9^SET/RBN <call> ...^Mark this call as an RBN node
2069 This will mark this callsign as a Reverse Beacon
2070 Network client. It's not a node in the normal sense of that word
2071 in DXSpider. But it will generate spots from the RBN/Skimmers and
2072 will act like a specialised node just for RBN spots.
2074 You will need to use this command to create your skimmer node
2075 connections. Normally one per RBN port (7000, 7001) but, in principle
2076 you could connect to any skimmer that uses the same spot format.
2078 === 9^SET/REGISTER <call> ...^Mark a user as registered
2079 === 9^UNSET/REGISTER <call> ...^Mark a user as not registered
2080 Registration is a concept that you can switch on by executing the
2082 set/var $main::regreq = 1
2084 command (usually in your startup file)
2086 If a user is NOT registered then, firstly, instead of the normal
2087 motd file (/spider/data/motd) being sent to the user at startup, the
2088 user is sent the motd_nor file instead. Secondly, the non registered
2089 user only has READ-ONLY access to the node. The non-registered user
2090 cannot use DX, ANN etc.
2092 The only exception to this is that a non-registered user can TALK or
2093 SEND messages to the sysop.
2095 === 6^SET/STARTUP <call>^Create a user startup script
2096 === 0^SET/STARTUP^Create your own startup script
2097 Create a startup script of DXSpider commands which will be executed
2098 everytime that you login into this node. You can only input the whole
2099 script afresh, it is not possible to 'edit' it. Inputting a new script is
2100 just like typing in a message using SEND. To finish inputting type: /EX
2101 on a newline, to abandon the script type: /ABORT.
2103 You may find the (curiously named) command BLANK useful to break
2104 up the output. If you simply want a blank line, it is easier to
2105 input one or more spaces and press the <return> key.
2107 See UNSET/STARTUP to remove a script.
2109 === 6^UNSET/STARTUP <call>^Remove a user startup script
2110 === 0^UNSET/STARTUP^Remove your own startup script
2111 You can remove your startup script with UNSET/STARTUP.
2113 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
2114 Tell the system that the call(s) are to be treated as DXSpider node and
2115 fed new style DX Protocol rather normal user commands.
2117 === 5^UNSET/SPIDER <call> [<call>..]^Make the callsign a normal user
2118 === 5^UNSET/ARCLUSTER <call> [<call>..]^Make the callsign a normal user
2119 === 5^UNSET/NODE <call> [<call>..]^Make the callsign a normal user
2120 === 5^UNSET/AK1A <call> [<call>..]^Make the callsign a normal user
2121 === 5^SET/USER <call> [<call>..]^Make the callsign a normal user
2123 === 0^SET/TALK^Allow TALK messages to come out on your terminal
2124 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
2126 === 9^SET/USDB <call> <state> <city>^add/update a US DB callsign
2127 This command allows you to add or alter a callsign in the US state
2128 database. Use with extreme caution. Anything you do here will be
2129 overwritten by any weekly updates that affect this callsign
2131 set/usdb g1tlh nh downtown rindge
2133 see also DELETE/USDB
2135 === 0^SET/USSTATE^Allow US State info on the end of DX announcements
2136 === 0^UNSET/USSTATE^Stop US State info on the end of DX announcements
2137 If the spotter's or spotted's US State is known it is output on the
2138 end of a DX announcement (there is just enough room).
2140 A spotter's state will appear on the RHS of the time (like
2141 SET/DXGRID) and the spotted's State will appear on the LHS of the
2142 time field. Any information found will override any locator
2143 information from SET/DXGRID.
2145 Some user programs cannot cope with this. You can use this command
2146 to reset (or set) this feature.
2148 Conflicts with: SET/DXCQ, SET/DXITU
2150 Do a STAT/USER to see which flags you have set if you are confused.
2152 === 0^SET/WANTRBN^[category ..]^Allow (some) RBN/Skimmer spots
2153 === 0^SET/SKIMMER^[category ..]^Allow (some) RBN/Skimmer spotsT
2154 === 0^UNSET/WANTRBN^Stop all RBN/Skimmer spots
2155 === 0^UNSET/SKIMMER^Stop all RBN/Skimmer spots
2156 === 9^SET/WANTRBN^<call> [category ..]^Allow (some) RBN/Skimmer spots
2157 === 9^SET/SKIMMER^<call> [category ..]^Allow (some) RBN/Skimmer spots
2158 This command allows curated Reverse Beacon Spots to come out on your
2161 If you want everything just type:
2167 Either command will do.
2169 If you want it all to just stop type:
2171 unset/skimmer (or unset/wantrbn)
2175 There five categories (or modes) of RBN/Skimmer spot available and one
2176 can limit the spots to one or more of these categories/modes:
2178 CW BEACON PSK RTTY FT
2180 together with a load of synonyms
2190 you will get psk, fsk, msk, ft4 and ft8 spots. if you want to break
2191 that down, then you will need to set filters accordingly - but your
2192 filter will only be offered spots from the categories that you have
2195 If you get into a muddle with this you can simply reset 'all on'
2196 with SET/SKIMMER or 'all off' with UNSET/SKIMMER.
2198 By default any filters that you have for "manual" spots will be
2199 automatically applied to your RBN/Skimmer feed. However it is possible
2200 to filter RBN/Skimmer spots differently by use ACCEPT/RBN and/or
2203 The RBN filters completely override any spot filters for these
2204 spots. But the spot filters will continue to filter "manual" spots as
2207 NOTE: Filters and this command CAN interact with each other. If you
2208 don't get the results that you expect, check your filters with
2211 Please see HELP RBN for an explanation of the spot format. It is NOT
2212 the same as one would get directly from the RBN/Skimmers. But it is
2213 recommended that you SET/DXCQ and UNSET/DXITU and UNSET/DXGRID (unless
2214 latter in more important to you with, for example, FT4/8 spots).
2216 === 0^SET/WCY^Allow WCY messages to come out on your terminal
2217 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
2219 === 0^SET/WWV^Allow WWV messages to come out on your terminal
2220 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
2222 === 0^SET/WX^Allow WX messages to come out on your terminal
2223 === 0^UNSET/WX^Stop WX messages coming out on your terminal
2225 === 0^SHOW/ANNOUNCE [<n>][<from>-<to>][<call>] ...^Show log of announces
2226 Show announcements that have come in.
2228 === 1^SHOW/BADDX^Show all the bad dx calls in the system
2229 Display all the bad dx callsigns in the system, see SET/BADDX
2230 for more information.
2232 === 1^SHOW/BADNODE^Show all the bad nodes in the system
2233 Display all the bad node callsigns in the system, see SET/BADNODE
2234 for more information.
2236 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
2237 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
2238 for more information.
2240 === 6^SHOW/BADWORD^Show all the bad words in the system
2241 === 6^SHOW/BADWORD full^Show all badwords with their Regex
2242 === 6^SHOW/BADWORD <word> ...^Show all badwords with their Regex
2243 Display all the bad words in the system, see SET/BADWORD
2244 for more information.
2246 The first form shows all the base words that are stored in a simple list.
2248 The second form list all words with their associated perl regex.
2250 The third form shows just the regexes for the words asked for. If no
2251 answer for a word is given then it is not defined.
2253 === 0^SHOW/BANDS [band|region names]^Show the list of bands and regions
2254 Display the bands and regions (collections of bands) known to
2255 the system. If you supply band or region names to SHOW/BANDS,
2256 the command will display just those bands or regions, e.g.:
2261 === 0^SHOW/BUDDY^Show your list of buddies
2262 See SET/BUDDY for more information about buddies.
2264 === 0^SHOW/CHAT [<group>] [<lines>]^Show any chat or conferencing
2265 This command allows you to see any chat or conferencing that has
2266 occurred whilst you were away. SHOW/CHAT on its own will show data for
2267 all groups. If you use a group name then it will show only chat for
2270 === 9^SHOW/CMD_CACHE [pattern]^Show the real source path of commands
2271 It is possible in DXSpider to define local versions of commands.
2272 Sometimes one forgets that one has these. This command will show you
2273 the source path where the node is getting each one of its commands.
2275 If you find a local command that you don't want then then simply
2276 delete it, run LOAD/CMD_CACHE to clear out the command cache and
2277 try again. You will now be using the standard version.
2279 If you are looking for information on a specific command then
2280 just add a string, eg:
2287 set/dxgrid /spider/cmd/set/dxgrid.pl
2288 sh/dx /spider/cmd/show/dx.pl
2290 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
2291 This command allows you to see all the users that can be seen
2292 and the nodes to which they are connected.
2294 This command is normally abbreviated to: sh/c
2296 Normally, the list returned will be just for the nodes from your
2297 country (because the list otherwise will be very long).
2301 will produce a complete list of all nodes.
2303 BE WARNED: the list that is returned can be VERY long
2305 It is possible to supply a node or part of a prefix and you will get
2306 a list of the users for that node or list of nodes starting with
2313 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
2314 Show all the nodes connected to this node.
2316 === 1^SHOW/CONNECT^Show all the active connections
2317 This command shows information on all the active connections known to
2318 the node. This command gives slightly more information than WHO.
2320 === 0^SHOW/CONTEST [<year>] [<month>]^Show all the contests for a month
2321 Show all known contests which are maintained at http://www.sk3bg.se/contest/
2322 for a particular month or year. The format is reasonably flexible.
2330 If there is no month/year then the current month's contests are shown.
2332 Note that it expects ENGLISH (jan/feb/mar/apr/may/jun/jul/aug/sep/oct/nov/dec)
2335 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
2336 This is very nearly the same as SHOW/TIME, the only difference the format
2337 of the date string if no arguments are given.
2339 If no prefixes or callsigns are given then this command returns the local
2340 time and UTC as the computer has it right now. If you give some prefixes
2341 then it will show UTC and UTC + the local offset (not including DST) at
2342 the prefixes or callsigns that you specify.
2344 === 0^SHOW/DB0SDX <callsign>^Show QSL infomation from DB0SDX database
2345 This command queries the DB0SDX QSL server on the internet
2346 and returns any information available for that callsign. This service
2347 is provided for users of this software by http://www.qslinfo.de.
2349 See also SHOW/QRZ, SHOW/WM7D.
2351 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
2353 === 0^SHOW/DX^Interrogate the spot database
2354 If you just type SHOW/DX you will get the last so many spots
2355 (sysop configurable, but usually 10).
2357 In addition you can add any number of these commands in very nearly
2358 any order to the basic SHOW/DX command, they are:-
2360 on <band> - eg 160m 20m 2m 23cm 6mm
2361 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2362 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
2365 <number> - the number of spots you want
2366 <from>-<to> - <from> spot no <to> spot no in the selected list
2369 <prefix> - for a spotted callsign beginning with <prefix>
2370 *<suffix> - for a spotted callsign ending in <suffix>
2371 *<string>* - for a spotted callsign containing <string>
2372 <call> exact - for a spotted callsign *exactly* as typed.
2374 day <number> - starting <number> days ago
2375 day <from>-<to> - <from> days <to> days ago
2378 info <text> - any spots containing <text> in the info or remarks
2380 by <call> - any spots spotted by <call> (spotter <call> is the
2383 qsl - this automatically looks for any qsl info on the call
2384 held in the spot database.
2386 iota [<iota>] - If the iota island number is missing it will look for
2387 the string iota and anything which looks like an iota
2388 island number. If you specify then it will look for
2391 qra [<locator>] - this will look for the specific locator if you specify
2392 one or else anything that looks like a locator.
2394 dxcc - treat the prefix as a 'country' and look for spots
2395 from that country regardless of actual prefix.
2398 You can also use this with the 'by' keyword so
2401 real or rt - Format the output the same as for real time spots. The
2402 formats are deliberately different (so you can tell
2403 one sort from the other). This is useful for some
2404 logging programs that can't cope with normal sh/dx
2405 output. An alias of SHOW/FDX is available.
2407 filter - Filter the spots, before output, with the user's
2408 spot filter. An alias of SHOW/MYDX is available.
2410 zone <zones> - look for spots in the cq zone (or zones) specified.
2411 zones are numbers separated by commas.
2413 by_zone <zones> - look for spots spotted by people in the cq zone
2416 itu <itus> - look for spots in the itu zone (or zones) specified
2417 itu zones are numbers separated by commas.
2419 by_itu <itus> - look for spots spotted by people in the itu zone
2422 state <list> - look for spots in the US state (or states) specified
2423 The list is two letter state codes separated by commas.
2425 by_state <list> - look for spots spotted by people in the US state
2428 origin - the node from which this spot originated (must be an
2429 exact callsign with SSID e.g. gb7tlh-4)
2431 ip - the IP address of the spotter (either in IPV4 or IPV6)
2432 format. These addresses can be partial.
2437 SH/DX on 20m info iota
2438 SH/DX 9a on vhf day 30
2444 SH/DX dxcc oq2 by w dxcc
2448 SH/DX by_state in,oh
2450 SH/DX origin gb7tlh-4
2451 SH/DX ip 82.65.128.4 (or SH/DX ip 2a00:1450:4009:800::200e)
2453 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
2454 This command takes the <prefix> (which can be a full or partial
2455 callsign if desired), looks up which internal country number it is
2456 and then displays all the spots as per SH/DX for that country.
2458 This is now an alias for 'SHOW/DX DXCC'
2460 The options for SHOW/DX also apply to this command.
2464 SH/DXCC W on 20m iota
2466 This can be done with the SHOW/DX command like this:-
2469 SH/DX dxcc w on 20m iota
2471 This is an alias for: SH/DX dxcc
2473 === 0^SHOW/FDX^Show the DX data in realtime format.
2474 Normally SHOW/DX outputs spot data in a different format to the
2475 realtime data. This is a deliberate policy (so you can tell the
2476 difference between the two). Some logging programs cannot handle
2477 this so SHOW/FDX outputs historical data in real time format.
2479 This is an alias for: SHOW/DX real
2481 === 0^SHOW/DXSTATS [days] [date]^Show the DX Statistics
2482 Show the total DX spots for the last <days> no of days (default is 31),
2483 starting from a <date> (default: today).
2485 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
2486 SHOW/FILES on its own will show you a list of the various fileareas
2487 available on the system. To see the contents of a particular file
2490 where <filearea> is the name of the filearea you want to see the
2493 You can also use shell globbing characters like '*' and '?' in a
2494 string to see a selection of files in a filearea eg:-
2495 SH/FILES bulletins arld*
2497 See also TYPE - to see the contents of a file.
2499 === 0^SHOW/FILTER^Show the contents of all the filters you have set
2500 Show the contents of all the filters that are set. This command displays
2501 all the filters set - for all the various categories.
2503 === 0^SHOW/GRAYLINE [ndays] [<prefix>|<callsign>]^Show Civil dawn/dusk times
2504 This command is very similar to SHOW/SUN except that it shows the
2505 start and end of "Official" or "Civil" Dawn and Dusk. This is defined
2506 as when the Sun is 6 degrees below the horizon.
2508 If you don't specify any prefixes or callsigns, it will show the
2509 times for your QTH (assuming you have set it with either SET/LOCATION
2510 or SET/QRA), together with the current azimuth and elevation.
2512 If all else fails it will show the civil dawn and dusk times for
2513 the node that you are connected to.
2518 SH/GRAYLINE G1TLH W5UN
2520 You can also use this command to see into the past or the future, so
2521 if you want to see yesterday's times then do:-
2525 or in three days time:-
2529 Upto 366 days can be checked both in the past and in the future.
2531 Please note that the times are given as the UT times of the requested
2534 === 0^SHOW/HFSTATS [days] [date]^Show the HF DX Statistics
2535 Show the HF DX spots breakdown by band for the last <days> no of days
2536 (default is 31), starting from a <date> (default: today).
2538 === 0^SHOW/HFTABLE [days] [date] [prefix ...]^Show the HF DX Spotter Table
2539 Show the HF DX Spotter table for the list of prefixes for the last
2540 <days> no of days (default is 31), starting from a <date> (default: today).
2542 If there are no prefixes then it will show the table for your country.
2544 Remember that some countries have more than one "DXCC country" in them
2545 (eg G :-), to show them (assuming you are not in G already which is
2546 specially treated in the code) you must list all the relevant prefixes
2548 sh/hftable g gm gd gi gj gw gu
2550 Note that the prefixes are converted into country codes so you don't have
2551 to list all possible prefixes for each country.
2553 If you want more or less days than the default simply include the
2554 number you require:-
2558 If you want to start at a different day, simply add the date in some
2561 sh/hftable 2 25nov02
2562 sh/hftable 2 25-nov-02
2564 sh/hftable 2 25/11/02
2566 This will show the stats for your DXCC for that CQWW contest weekend.
2568 You can specify either prefixes or full callsigns (so you can see how you
2569 did against all your mates). You can also say 'all' which will then print
2570 the worldwide statistics.
2574 === 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
2575 This command shows the hop counts set up for a node. You can specify
2576 which category you want to see. If you leave the category out then
2577 all the categories will be listed.
2579 === 0^SHOW/IK3QAR <callsign>^Obtain QSL info from IK3QAR database
2580 Get QSL information from the online dabase run by IK3QAR.
2582 Your sysop needs to set up this command by obtaining a password from IK3QAR.
2583 Instructions are available in local/Internet.pm
2585 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
2587 === 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
2589 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
2590 This command outputs a short section of the system log. On its own
2591 it will output a general logfile. With the optional callsign it will
2592 show output from the log associated with that callsign.
2594 === 0^SHOW/MOON [ndays] [<prefix>|<callsign>]^Show Moon rise and set times
2595 Show the Moon rise and set times for a (list of) prefixes or callsigns,
2596 together with the azimuth and elevation of the sun currently at those
2599 If you don't specify any prefixes or callsigns, it will show the times for
2600 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2601 together with the current azimuth and elevation.
2603 In addition, it will show the illuminated fraction of the moons disk.
2605 If all else fails it will show the Moonrise and set times for the node
2606 that you are connected to.
2613 You can also use this command to see into the past or the future, so
2614 if you want to see yesterday's times then do:-
2618 or in three days time:-
2622 Upto 366 days can be checked both in the past and in the future.
2624 Please note that the rise and set times are given as the UT times of rise and
2625 set on the requested UT day.
2627 === 0^SHOW/MOTD^Show your MOTD (the Message of the Day)
2628 The Message of the Day is normally printed whenever one logs on. However
2629 many people now login using logging programs or something other than plain
2630 telnet or ax25 connections. This command allows the user (or the program)
2631 to see what is in the MOTD.
2633 The actual MOTD that you are shown depends on what carrier you are logged
2634 on via, whether you are registered and some other factors that your sysop
2637 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
2638 This command allow you to estimate the likelihood of you contacting
2639 a station with the prefix you have specified. The output assumes a modest
2640 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
2642 The result predicts the most likely operating frequencies and signal
2643 levels for high frequency (shortwave) radio propagation paths on
2644 specified days of the year and hours of the day. It is most useful for
2645 paths between 250 km and 6000 km, but can be used with reduced accuracy
2646 for paths shorter or longer than this.
2648 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2649 used to predict the MUF given the predicted flux, day of the year,
2650 hour of the day and geographic coordinates of the transmitter and
2651 receiver. This routine is reasonably accurate for the purposes here,
2652 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2653 than the programs used by major shortwave broadcasting organizations,
2654 such as the Voice of America.
2656 The command will display some header information detailing its
2657 assumptions, together with the locations, latitude and longitudes and
2658 bearings. It will then show UTC (UT), local time at the other end
2659 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2660 (Zen) and the likely signal strengths. Then for each frequency for which
2661 the system thinks there is a likelihood of a circuit it prints a value.
2663 The value is currently a likely S meter reading based on the conventional
2664 6dB / S point scale. If the value has a '+' appended it means that it is
2665 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
2666 there is likely to be much fading and by an 's' that the signal is likely
2669 By default SHOW/MUF will show the next two hours worth of data. You
2670 can specify anything up to 24 hours worth of data by appending the no of
2671 hours required after the prefix. For example:-
2677 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2678 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2679 Location Lat / Long Azim
2680 East Dereham, Norfolk 52 41 N 0 57 E 47
2681 United-States-W 43 0 N 87 54 W 299
2682 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2683 18 23 11.5 -35 mS0+ mS2 S3
2684 19 0 11.2 -41 mS0+ mS2 S3
2686 indicating that you will have weak, fading circuits on top band and
2687 80m but usable signals on 40m (about S3).
2693 will get you the above display, but with the next 24 hours worth of
2699 Gives you an estimate of the long path propagation characterics. It
2700 should be noted that the figures will probably not be very useful, nor
2701 terrible accurate, but it is included for completeness.
2703 === 0^SHOW/MYDX^Show the DX data filtered with your spot filter.
2704 SHOW/DX potentially shows all the spots available in the system. Using
2705 SHOW/MYDX will, instead, filter the availble spots using any spot filter
2706 that you have set, first.
2708 This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
2709 you to customise the spots that you receive.
2711 So if you have said: ACC/SPOT on hf
2713 Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
2714 options on SH/DX can still be used.
2716 === 0^SHOW/NEWCONFIGURATION [USERS|<node call>]^Show the cluster map
2717 Show the map of the whole cluster.
2719 This shows the structure of the cluster that you are connected to. By
2720 default it will only show the nodes that are known. By adding the keyword
2721 USER to the command it will show all the users as well.
2723 As there will be loops, you will see '...', this means that the information
2724 is as printed earlier and that is a looped connection from here on.
2726 BE WARNED: the list that is returned can be VERY long (particularly
2727 with the USER keyword)
2729 === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
2730 Show all the nodes connected to this node in the new format.
2732 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
2733 === 1^SHOW/NODE ALL^Show the type,version number of ALL known nodes
2734 Show the type and version (if connected) of the nodes specified on the
2735 command line. If no callsigns are specified then a sorted list of all
2736 the non-user callsigns connected to node will be displayed.
2738 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
2739 This command takes the <callsign> (which can be a full or partial
2740 callsign or a prefix), looks up which internal country number
2741 it is and then displays all the relevant prefixes for that country
2742 together with the internal country no, the CQ and ITU regions.
2746 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
2747 Show the name and location where every program module was load from. This
2748 is useful for checking where you think you have loaded a .pm file from.
2750 === 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
2751 === 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
2752 This is a multipurpose command that allows you either to calculate the
2753 distance and bearing between two locators or (if only one locator is
2754 given on the command line) the distance and beraing from your station
2755 to the locator. For example:-
2760 The first example will show the distance and bearing to the locator from
2761 yourself, the second example will calculate the distance and bearing from
2762 the first locator to the second. You can use 4 or 6 character locators.
2764 It is also possible to convert a latitude and longitude to a locator by
2765 using this command with a latitude and longitude as an argument, for
2768 SH/QRA 52 41 N 0 58 E
2770 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
2771 This command queries the QRZ callbook server on the internet
2772 and returns any information available for that callsign. This service
2773 is provided for users of this software by http://www.qrz.com
2775 See also SHOW/WM7D for an alternative.
2777 === 0^SHOW/DXQSL <callsign>^Show any QSL info gathered from spots
2778 The node collects information from the comment fields in spots (things
2779 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
2781 This command allows you to interrogate that database and if the callsign
2782 is found will display the manager(s) that people have spotted. This
2783 information is NOT reliable, but it is normally reasonably accurate if
2784 it is spotted enough times.
2790 You can check the raw input spots yourself with:-
2794 This gives you more background information.
2796 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
2798 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
2799 This command allows you to see to which node the callsigns specified are
2800 connected. It is a sort of inverse sh/config.
2804 === 1^SHOW/RBN [<callsign> ...]^Show which connected users want RBN spots
2805 === 1^SHOW/RBN ALL^Show ALL users that want RBN spots
2806 Show a list of the users that want RBN spots of any the callsigns
2807 specified on the command line. If no callsigns are specified then a
2808 sorted list of all connected users wanting RBN spots will be displayed
2812 will go through the user file and display ALL users that want RBN spots.
2814 === 9^SHOW/RCMD [<n>][<from>-<to>][<call>] ...^Show log of rcmds
2815 Show the rcmds that have come in and their replies.
2817 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
2818 Show the tracking data from your location to the satellite of your choice
2819 from now on for the next few hours.
2821 If you use this command without a satellite name it will display a list
2822 of all the satellites known currently to the system.
2824 If you give a name then you can obtain tracking data of all the passes
2825 that start and finish 5 degrees below the horizon. As default it will
2826 give information for the next three hours for every five minute period.
2828 You can alter the number of hours and the step size, within certain
2831 Each pass in a period is separated with a row of '-----' characters
2836 SH/SAT FENGYUN1 12 2
2838 === 1^SHOW/SPOTSTATS^Show the current Spot statistics
2839 View the current unique spot sentences seen since the last restart.
2841 It shows the number of PC11 and PC61 sentences and the percentage
2842 of PC11s received of the total of both. It also shows the number
2843 of PC11s that have been promoted to PC61 before being passed on
2844 plus a total percentage of incoming PC11 that have been promoted.
2846 A PC11 can be promoted to PC61 by a stored IP address in the routing
2847 table or it can be promoted by being delayed to a short for any
2848 passing PC61 from another node.
2850 === 6^SHOW/STARTUP <call>^View a user startup script
2851 === 0^SHOW/STARTUP^View your own startup script
2852 View the contents of a startup script created with SET/STARTUP.
2854 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
2855 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
2856 Show the information known about a callsign and whether (and where)
2857 that callsign is connected to the cluster.
2861 If no callsign is given then show the information for yourself.
2863 === 0^SHOW/SUN [ndays] [<prefix>|<callsign>]^Show sun rise and set times
2864 Show the sun rise and set times for a (list of) prefixes or callsigns,
2865 together with the azimuth and elevation of the sun currently at those
2868 If you don't specify any prefixes or callsigns, it will show the times for
2869 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2870 together with the current azimuth and elevation.
2872 If all else fails it will show the sunrise and set times for the node
2873 that you are connected to.
2878 SH/SUN G1TLH K9CW ZS
2880 You can also use this command to see into the past or the future, so
2881 if you want to see yesterday's times then do:-
2885 or in three days time:-
2889 Upto 366 days can be checked both in the past and in the future.
2891 Please note that the rise and set times are given as the UT times of rise
2892 and set on the requested UT day.
2894 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
2895 If no prefixes or callsigns are given then this command returns the local
2896 time and UTC as the computer has it right now. If you give some prefixes
2897 then it will show UTC and UTC + the local offset (not including DST) at
2898 the prefixes or callsigns that you specify.
2900 === 0^SHOW/USDB [call ..]^Show information held on the FCC Call database
2901 Show the City and State of a Callsign held on the FCC database if
2902 his is being run on this system, eg:-
2906 === 0^SHOW/VHFSTATS [days] [date]^Show the VHF DX Statistics
2907 Show the VHF DX spots breakdown by band for the last
2908 <days> no of days (default is 31), starting from a date (default: today).
2910 === 0^SHOW/VHFTABLE [days] [date] [prefix ...]^Show the VHF DX Spotter Table
2911 Show the VHF DX Spotter table for the list of prefixes for the last
2912 <days> no of days (default is 31), starting from a date (default: today).
2914 If there are no prefixes then it will show the table for your country.
2916 Remember that some countries have more than one "DXCC country" in them
2917 (eg G :-), to show them (assuming you are not in G already which is
2918 specially treated in the code) you must list all the relevant prefixes
2920 sh/vhftable g gm gd gi gj gw gu
2922 Note that the prefixes are converted into country codes so you don't have
2923 to list all possible prefixes for each country.
2925 If you want more or less days than the default simply include the
2926 number you require:-
2930 If you want to start at a different day, simply add the date in some
2933 sh/vhftable 2 25nov02
2934 sh/vhftable 2 25-nov-02
2935 sh/vhftable 2 021125
2936 sh/vhftable 2 25/11/02
2938 This will show the stats for your DXCC for that CQWW contest weekend.
2940 You can specify either prefixes or full callsigns (so you can see how you
2941 did against all your mates). You can also say 'all' which will then print
2942 the worldwide statistics.
2946 === 0^SHOW/WCY^Show last 10 WCY broadcasts
2947 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
2948 Display the most recent WCY information that has been received by the system
2950 === 0^SHOW/WM7D <callsign>^Show callbook details on a US callsigns
2951 This command queries the WM7D callbook server on the internet
2952 and returns any information available for that US callsign. This service
2953 is provided for users of this software by http://www.wm7d.net.
2957 === 0^SHOW/WWV^Show last 10 WWV broadcasts
2958 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
2959 Display the most recent WWV information that has been received by the system
2961 === 5^SHUTDOWN^Shutdown the cluster
2962 Shutdown the cluster and disconnect all the users
2964 === 9^SPOOF <call> <command>^Do a command as though you are another user
2965 This command is provided so that sysops can set a user's parameters without
2966 me having to write a special 'sysop' version for every user command. It
2967 allows you to pretend that you are doing the command as the user you specify.
2971 SPOOF G1TLH set/name Dirk
2972 SPOOF G1TLH set/qra JO02LQ
2974 === 5^STAT/DB <dbname>^Show the status of a database
2975 Show the internal status of a database descriptor.
2977 Depending on your privilege level you will see more or less information.
2978 This command is unlikely to be of much use to anyone other than a sysop.
2980 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
2981 Show the internal status of the channel object either for the channel that
2982 you are on or else for the callsign that you asked for.
2984 Only the fields that are defined (in perl term) will be displayed.
2986 === 1^STAT/MSG^Show the status of the message system
2987 === 1^STAT/MSG <msgno>^Show the status of a message
2988 This command shows the internal status of a message and includes information
2989 such as to whom it has been forwarded, its size, origin etc etc.
2991 If no message number is given then the status of the message system is
2994 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
2995 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
2997 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
2998 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
3000 === 5^STAT/USER [<callsign>]^Show the full status of a user
3001 Shows the full contents of a user record including all the secret flags
3004 Only the fields that are defined (in perl term) will be displayed.
3006 === 0^SYSOP^Regain your privileges if you login remotely
3007 The system automatically reduces your privilege level to that of a
3008 normal user if you login in remotely. This command allows you to
3009 regain your normal privilege level. It uses the normal system: five
3010 numbers are returned that are indexes into the character array that is
3011 your assigned password (see SET/PASSWORD). The indexes start from
3014 You are expected to return a string which contains the characters
3015 required in the correct order. You may intersperse those characters
3016 with others to obscure your reply for any watchers. For example (and
3017 these values are for explanation :-):
3019 password = 012345678901234567890123456789
3023 aa2bbbb0ccc5ddd7xxx3n
3027 They will all match. If there is no password you will still be offered
3028 numbers but nothing will happen when you input a string. Any match is
3031 === 0^TALK <call> [<text>]^Send a text message to another station
3032 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
3033 Send a short message to any other station that is visible on the cluster
3034 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
3035 command, they don't have to be connected locally.
3037 The second form of TALK is used when other cluster nodes are connected
3038 with restricted information. This usually means that they don't send
3039 the user information usually associated with logging on and off the cluster.
3041 If you know that G3JNB is likely to be present on GB7TLH, but you can only
3042 see GB7TLH in the SH/C list but with no users, then you would use the
3043 second form of the talk message.
3045 If you want to have a ragchew with someone you can leave the text message
3046 out and the system will go into 'Talk' mode. What this means is that a
3047 short message is sent to the recipient telling them that you are in a
3048 'Talking' frame of mind and then you just type - everything you send will
3049 go to the station that you asked for.
3051 All the usual announcements, spots and so on will still come out on your
3054 If you want to do something (such as send a spot) you preceed the normal
3055 command with a '/' character, eg:-
3057 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
3060 To leave talk mode type:
3064 If you are in 'Talk' mode, there is an extention to the '/' command which
3065 allows you to send the output to all the people you are talking to. You do
3066 with the '//' command. For example:-
3070 will send the hftable as you have it to all the people you are currently
3073 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
3074 Type out the contents of a file in a filearea. So, for example, in
3075 filearea 'bulletins' you want to look at file 'arld051' you would
3077 TYPE bulletins/arld051
3079 See also SHOW/FILES to see what fileareas are available and a
3082 === 0^WHO^Show who is physically connected
3083 This is a quick listing that shows which callsigns are connected and
3084 what sort of connection they have
3086 === 0^WX <text>^Send a weather message to local users
3087 === 0^WX FULL <text>^Send a weather message to all cluster users
3088 === 5^WX SYSOP <text>^Send a weather message to other clusters only
3089 Weather messages can sometimes be useful if you are experiencing an extreme
3090 that may indicate enhanced conditions