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
12 # Comment lines are indented before printing
14 === 0^ACCEPT^Set a filter to accept something
15 Create a filter to accept something
17 There are 2 types of filter, accept and reject. See HELP FILTERING for more
20 === 0^ACCEPT/ANNOUNCE [0-9] <pattern>^Set an 'accept' filter line for announce
21 Create an 'accept this announce' line for a filter.
23 An accept filter line means that if the announce matches this filter it is
24 passed onto the user. See HELP FILTERING for more info. Please read this
25 to understand how filters work - it will save a lot of grief later on.
27 You can use any of the following things in this line:-
29 info <string> eg: iota or qsl
30 by <prefixes> eg: G,M,2
32 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
33 origin_itu <prefixes or numbers> or: G,GM,GW
34 origin_zone <prefixes or numbers>
35 origin_state <states> eg: VA,NH,RI,NH
36 by_dxcc <prefixes or numbers>
37 by_itu <prefixes or numbers>
38 by_zone <prefixes or numbers>
41 wx 1 filter WX announces
42 dest <prefixes> eg: 6MUK,WDX (distros)
47 acc/ann 2 by_zone 14,15,16
48 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
54 acc/ann by_state va,nh,ri,nh
56 You can use the tag 'all' to accept everything eg:
60 but this probably for advanced users...
62 === 8^ACCEPT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
63 This version allows a sysop to set a filter for a callsign as well as the
64 default for nodes and users eg:-
67 accept/ann input node_default by G,M,2
68 accept/ann user_default by G,M,2
70 === 8^ACCEPT/ROUTE <call> [0-9] <pattern>^Set an 'accept' filter line for routing
71 Create an 'accept this routing PC Protocol' line for a filter.
73 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
74 it is passed thru that interface. See HELP FILTERING for more info. Please read this
75 to understand how filters work - it will save a lot of grief later on.
77 You can use any of the following things in this line:-
79 call <prefixes> the callsign of the thingy
80 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
81 call_itu <prefixes or numbers> or: G,GM,GW
82 call_zone <prefixes or numbers>
83 call_state <states> eg: VA,NH,RI,NH
84 origin <prefixes> really the interface it came in on
85 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
86 origin_itu <prefixes or numbers> or: G,GM,GW
87 origin_zone <prefixes or numbers>
88 origin_state <states> eg: VA,NH,RI,NH
92 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
93 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
95 you can now use 'by' as a synonym for 'call' so:
102 You can use the tag 'all' to accept everything eg:
107 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
108 Create an 'accept this spot' line for a filter.
110 An accept filter line means that if the spot matches this filter it is
111 passed onto the user. See HELP FILTERING for more info. Please read this
112 to understand how filters work - it will save a lot of grief later on.
114 You can use any of the following things in this line:-
116 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
117 on <range> same as 'freq'
118 call <prefixes> eg: G,PA,HB9
119 info <string> eg: iota or qsl
121 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
122 call_itu <prefixes or numbers> or: G,GM,GW
123 call_zone <prefixes or numbers>
124 call_state <states> eg: VA,NH,RI,ME
125 by_dxcc <prefixes or numbers>
126 by_itu <prefixes or numbers>
127 by_zone <prefixes or numbers>
128 by_state <states> eg: VA,NH,RI,ME
132 'call' means the callsign that has spotted 'by' whoever.
134 For frequencies, you can use any of the band names defined in
135 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
136 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
137 this is more efficient than saying simply: freq HF (but don't get
138 too hung up about that)
143 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
145 You can use the tag 'all' to accept everything, eg:
151 acc/spots by_state VA,NH,RI,MA,ME
153 but this probably for advanced users...
156 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
157 This version allows a sysop to set a filter for a callsign as well as the
158 default for nodes and users eg:-
160 accept/spot db0sue-7 1 by_zone 14,15,16
161 accept/spot node_default all
162 set/hops node_default 10
164 accept/spot user_default by G,M,2
166 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
167 It is unlikely that you will want to do this, but if you do then you can
168 filter on the following fields:-
170 by <prefixes> eg: G,M,2
172 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
173 origin_itu <prefixes or numbers> or: G,GM,GW
174 origin_zone <prefixes or numbers>
175 by_dxcc <prefixes or numbers>
176 by_itu <prefixes or numbers>
177 by_zone <prefixes or numbers>
180 There are no examples because WCY Broadcasts only come from one place and
181 you either want them or not (see UNSET/WCY if you don't want them).
183 This command is really provided for future use.
185 See HELP FILTER for information.
187 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
188 This version allows a sysop to set a filter for a callsign as well as the
189 default for nodes and users eg:-
191 accept/wcy node_default all
192 set/hops node_default 10
194 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
195 It is unlikely that you will want to do this, but if you do then you can
196 filter on the following fields:-
198 by <prefixes> eg: G,M,2
200 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
201 origin_itu <prefixes or numbers> or: G,GM,GW
202 origin_zone <prefixes or numbers>
203 by_dxcc <prefixes or numbers>
204 by_itu <prefixes or numbers>
205 by_zone <prefixes or numbers>
212 is probably the only useful thing to do (which will only show WWV broadcasts
213 by stations in the US).
215 See HELP FILTER for information.
217 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
218 This version allows a sysop to set a filter for a callsign as well as the
219 default for nodes and users eg:-
221 accept/wwv db0sue-7 1 by_zone 4
222 accept/wwv node_default all
223 set/hops node_default 10
225 accept/wwv user_default by W,K
227 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
228 <text> is the text of the announcement you wish to broadcast
230 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
231 This will send your announcement cluster wide
233 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
235 === 0^APROPOS <string>^Search help database for <string>
236 Search the help database for <string> (it isn't case sensitive), and print
237 the names of all the commands that may be relevant.
239 === 0^BLANK [<string>] [<nn>]^Print nn (default 1) blank lines (or strings)
240 In its basic form this command prints one or more blank lines. However if
241 you pass it a string it will replicate the string for the width of the
242 screen (default 80) and then print that one or more times, so:
246 prints two blank lines
250 prints a row of - characters once.
254 prints 'abcabcabcabcabcabc....'
256 This is really only of any use in a script file and you can print a maximum
259 === 0^BYE^Exit from the cluster
260 This will disconnect you from the cluster
262 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
263 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
264 When you send messages the fact that you have forwarded it to another node
265 is remembered so that it isn't sent again. When you have a new partner
266 node and you add their callsign to your /spider/msg/forward.pl file, all
267 outstanding non-private messages will be forwarded to them. This may well
268 be ALL the non-private messages. You can prevent this by using these
272 catchup GB7DJK 300 301 302 303 500-510
274 and to undo what you have just done:-
277 uncatchup GB7DJK 300 301 302 303 500-510
279 which will arrange for them to be forward candidates again.
281 Order is not important.
283 === 0^CHAT <group> <text>^Chat or Conference to a group
284 It is now possible to JOIN a group and have network wide conferencing to that
285 group. DXSpider does not (and probably will not) implement the AK1A
286 conference mode as this seems very limiting, is hardly used and doesn't seem
287 to work too well anyway.
289 This system uses the existing ANN system and is compatible with both other
290 DXSpider nodes and AK1A clusters (they use ANN/<group>).
292 You can be a member of as many "groups" as you want. To join a group type:-
294 JOIN FOC (where FOC is the group name)
296 To leave a group type:-
300 You can see which groups you are in by typing:-
304 and you can see whether your mate is in the group, if he connects to the
305 same node as you, by typing:-
309 To send a message to a group type:-
311 CHAT FOC hello everyone
315 CH #9000 hello I am back
317 See also JOIN, LEAVE, SHOW/CHAT
319 === 0^CLEAR/ANNOUNCE [1|all]^Clear a announce filter line
320 This command allows you to clear (remove) a line in a annouce filter or to
321 remove the whole filter.
323 see CLEAR/SPOTS for a more detailed explanation.
325 === 8^CLEAR/ANNOUNCE <callsign> [input] [0-9|all]^Clear a announce filter line
326 A sysop can clear an input or normal output filter for a user or the
327 node_default or user_default.
329 === 0^CLEAR/ROUTE [1|all]^Clear a route filter line
330 This command allows you to clear (remove) a line in a route filter or to
331 remove the whole filter.
333 see CLEAR/SPOTS for a more detailed explanation.
335 === 8^CLEAR/ROUTE <callsign> [input] [0-9|all]^Clear a route filter line
336 A sysop can clear an input or normal output filter for a user or the
337 node_default or user_default.
339 === 0^CLEAR/SPOTS [0-9|all]^Clear a spot filter line
340 This command allows you to clear (remove) a line in a spot filter or to
341 remove the whole filter.
343 If you have a filter:-
346 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
352 you will be left with:-
354 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
360 the filter will be completely removed.
362 === 8^CLEAR/SPOTS <callsign> [input] [0-9|all]^Clear a spot filter line
363 A sysop can clear an input or normal output filter for a user or the
364 node_default or user_default.
366 === 0^CLEAR/WCY [1|all]^Clear a WCY filter line
367 This command allows you to clear (remove) a line in a WCY filter or to
368 remove the whole filter.
370 see CLEAR/SPOTS for a more detailed explanation.
372 === 8^CLEAR/WCY <callsign> [input] [0-9|all]^Clear a WCY filter line
373 A sysop can clear an input or normal output filter for a user or the
374 node_default or user_default.
376 === 0^CLEAR/WWV [1|all]^Clear a WWV filter line
377 This command allows you to clear (remove) a line in a WWV filter or to
378 remove the whole filter.
380 see CLEAR/SPOTS for a more detailed explanation.
382 === 8^CLEAR/WWV <callsign> [input] [0-9|all]^Clear a WWV filter line
383 A sysop can clear an input or normal output filter for a user or the
384 node_default or user_default.
386 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
387 Start a connection process that will culminate in a new connection to the
388 DX cluster <callsign>. This process creates a new 'client' process which will
389 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
390 necessary to traverse the network(s) to logon to the cluster <callsign>.
392 === 9^DELETE/USDB <callsign> ...^Delete this user from the US State Database
393 This command will completely remove a one or more callsigns
394 from the US States database.
396 There is NO SECOND CHANCE.
398 It goes without saying that you should use this command CAREFULLY!
400 Note that these callsign may be re-instated by any weekly updates from
403 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
404 This command will completely remove a one or more users from the database.
406 There is NO SECOND CHANCE.
408 It goes without saying that you should use this command CAREFULLY!
410 === 0^DBAVAIL^Show a list of all the Databases in the system
411 Title says it all really, this command lists all the databases defined
412 in the system. It is also aliased to SHOW/COMMAND.
414 === 9^DBCREATE <name>^Create a database entry
415 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
416 === 9^DBCREATE <name> remote <node>^Create a remote database entry
417 === 9^DBCREATE <name> cmd <dxspider command>^make a local command available as a DB
418 DBCREATE allows you to define a database in the system. It doesn't actually
419 create anything, just defines it.
421 The databases that are created are simple DB_File hash databases, they are
422 therefore already 'indexed'.
424 You can define a local database with the first form of the command eg:
428 You can also chain databases with the addition of the 'chain' keyword.
429 This will search each database one after the other. A typical example
432 DBCREATE sdx_qsl chain sql_ad
434 No checking is done to see if the any of the chained databases exist, in
435 fact it is usually better to do the above staement first then do each of
436 the chained databases.
438 Databases can exist offsite. To define a database that lives on another
441 DBCREATE buckmaster remote gb7dxc
443 Remote databases cannot be chained; however, the last database in a
444 a chain can be a remote database eg:
446 DBCREATE qsl chain gb7dxc
448 To see what databases have been defined do:
450 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
452 It would be normal for you to add an entry into your local Aliases file
453 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
454 need to add a line like:-
459 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
468 to work as they may be used to.
470 You can also make local commands available as 'pseudo' databases. You
471 can therefore make spider special commands available as a database. I
472 imagine that this will be primarily useful for remote access from
473 legacy nodes. For example:-
475 DBCREATE dxqsl cmd show/dxqsl
477 You also use one of these databases in a chain. This may be useful
480 See DBIMPORT for the importing of existing AK1A format data to databases.
481 See DBSHOW for generic database enquiry
483 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
484 If you want to import or update data in bulk to a database you can use
485 this command. It will either create or update entries into an existing
486 database. For example:-
488 DBIMPORT oblast /tmp/OBLAST.FUL
490 will import the standard OBLAST database that comes with AK1A into the
491 oblast database held locally.
493 === 9^DBREMOVE <dbname>^Delete a database
494 DBREMOVE will completely remove a database entry and also delete any data
495 file that is associated with it.
497 There is no warning, no comeback, no safety net.
503 will remove the oblast database from the system and it will also remove
504 the associated datafile.
508 There is no warning, no comeback, no safety net.
510 You have been warned.
512 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
513 This is the generic user interface to the database to the database system.
514 It is expected that the sysop will add an entry to the local Aliases file
515 so that users can use the more familiar AK1A style of enquiry such as:
519 but if he hasn't and the database really does exist (use DBAVAIL or
520 SHOW/COMMAND to find out) you can do the same thing with:
524 === 9^DEBUG^Set the cluster program into debug mode
525 Executing this command will only have an effect if you are running the cluster
530 It will interrupt the cluster just after the debug command has finished.
532 === 0^DIRECTORY^List messages
533 === 0^DIRECTORY ALL^List all messages
534 === 0^DIRECTORY OWN^List your own messages
535 === 0^DIRECTORY NEW^List all new messages
536 === 0^DIRECTORY TO <call>^List all messages to <call>
537 === 0^DIRECTORY FROM <call>^List all messages from <call>
538 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
539 === 0^DIRECTORY <nn>^List last <nn> messages
540 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
541 List the messages in the messages directory.
543 If there is a 'p' one space after the message number then it is a
544 personal message. If there is a '-' between the message number and the
545 'p' then this indicates that the message has been read.
547 You can use shell escape characters such as '*' and '?' in the <call>
550 You can combine some of the various directory commands together eg:-
554 DIR SUBJECT IOTA 200-250
556 You can abbreviate all the commands to one letter and use ak1a syntax:-
562 Sysops can see all users' messages.
564 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
565 Disconnect any <call> connected locally
567 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
568 This is how you send a DX Spot to other users. You can, in fact, now
569 enter the <freq> and the <call> either way round.
575 will all give the same result. You can add some remarks to the end
576 of the command and they will be added to the spot.
578 DX FR0G 144600 this is a test
580 You can credit someone else by saying:-
582 DX by G1TLH FR0G 144.600 he isn't on the cluster
584 The <freq> is compared against the available bands set up in the
585 cluster. See SHOW/BANDS for more information.
587 === 0^ECHO <line>^Echo the line to the output
588 This command is useful in scripts and so forth for printing the
589 line that you give to the command to the output. You can use this
590 in user_default scripts and the SAVE command for titling and so forth
592 The script will interpret certain standard "escape" sequences as follows:-
594 \t - becomes a TAB character (0x09 in ascii)
595 \a - becomes a BEEP character (0x07 in ascii)
596 \n - prints a new line
598 So the following example:-
600 echo GB7DJK is a dxcluster
604 GB7DJK is a dxcluster
606 on the output. You don't need a \n on the end of the line you want to send.
608 A more complex example:-
610 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
620 === 9^EXPORT <msgno> <filename>^Export a message to a file
621 Export a message to a file. This command can only be executed on a local
622 console with a fully privileged user. The file produced will be in a form
623 ready to be imported back into the cluster by placing it in the import
624 directory (/spider/msg/import).
626 This command cannot overwrite an existing file. This is to provide some
627 measure of security. Any files written will owned by the same user as the
628 main cluster, otherwise you can put the new files anywhere the cluster can
629 access. For example:-
633 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
634 Export the users database to a file in ascii format. If no filename
635 is given then it will export the file to /spider/data/user_asc.
637 If the file already exists it will be renamed to <filename>.o. In fact
638 up to 5 generations of the file can be kept each one with an extra 'o' on the
641 BE WARNED: this will write to any file you have write access to. No check is
642 made on the filename (if any) that you specify.
644 === 0^FILTERING...^Filtering things in DXSpider
645 There are a number of things you can filter in the DXSpider system. They
646 all use the same general mechanism.
648 In general terms you can create a 'reject' or an 'accept' filter which
649 can have up to 10 lines in it. You do this using, for example:-
654 where ..... are the specific commands for that type of filter. There
655 are filters for spots, wwv, announce, wcy and (for sysops)
656 connects. See each different accept or reject command reference for
659 There is also a command to clear out one or more lines in a filter and
660 one to show you what you have set. They are:-
669 There is clear/xxxx command for each type of filter.
671 For now we are going to use spots for the examples, but you can apply
672 the principles to all types of filter.
674 There are two main types of filter 'accept' or 'reject'; which you use
675 depends entirely on how you look at the world and what is least
676 writing to achieve what you want. Each filter has 10 lines (of any
677 length) which are tried in order. If a line matches then the action
678 you have specified is taken (ie reject means ignore it and accept
681 The important thing to remember is that if you specify a 'reject'
682 filter (all the lines in it say 'reject/spots' (for instance)) then if
683 a spot comes in that doesn't match any of the lines then you will get
684 it BUT if you specify an 'accept' filter then any spots that don't
685 match are dumped. For example if I have a one line accept filter:-
687 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
689 then automatically you will ONLY get VHF spots from or to CQ zones 14
690 15 and 16. If you set a reject filter like:
692 reject/spots on hf/cw
694 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
695 and will work it even on CW then you could say:-
697 reject/spots on hf/cw and not info iota
699 But in that case you might only be interested in iota and say:-
701 accept/spots not on hf/cw or info iota
703 which is exactly the same. You should choose one or the other until
704 you are confortable with the way it works. Yes, you can mix them
705 (actually you can have an accept AND a reject on the same line) but
706 don't try this at home until you can analyse the results that you get
707 without ringing up the sysop for help.
709 Another useful addition now is filtering by US state
711 accept/spots by_state VA,NH,RI,ME
713 You can arrange your filter lines into logical units, either for your
714 own understanding or simply convenience. I have one set frequently:-
716 reject/spots 1 on hf/cw
717 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
719 What this does is to ignore all HF CW spots (being a class B I can't
720 read any CW and couldn't possibly be interested in HF :-) and also
721 rejects any spots on VHF which don't either originate or spot someone
724 This is an exmaple where you would use the line number (1 and 2 in
725 this case), if you leave the digit out, the system assumes '1'. Digits
726 '0'-'9' are available.
728 You can leave the word 'and' out if you want, it is implied. You can
729 use any number of brackets to make the 'expression' as you want
730 it. There are things called precedence rules working here which mean
731 that you will NEED brackets in a situation like line 2 because,
732 without it, will assume:-
734 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
736 annoying, but that is the way it is. If you use OR - use
737 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
740 If you want to alter your filter you can just redefine one or more
741 lines of it or clear out one line. For example:-
743 reject/spots 1 on hf/ssb
749 To remove the filter in its entirty:-
753 There are similar CLEAR commands for the other filters:-
761 Once you are happy with the results you get, you may like to experiment.
763 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
764 can be written with a mixed filter, eg:
768 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
770 each filter slot actually has a 'reject' slot and an 'accept'
771 slot. The reject slot is executed BEFORE the accept slot.
773 It was mentioned earlier that after a reject test that doesn't match,
774 the default for following tests is 'accept', the reverse is true for
775 'accept'. In the example what happens is that the reject is executed
776 first, any non hf/cw spot is passed to the accept line, which lets
777 thru everything else on HF.
779 The next filter line lets through just VHF/UHF spots from EU.
781 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
782 This command sends all the latitude and longitude information that your
783 cluster is holding against callsigns. One advantage of recieving this
784 information is that more locator information is held by you. This
785 means that more locators are given on the DX line assuming you have
786 SET/DXGRID enabled. This could be a LOT of information though, so
787 it is not recommended on slow links.
789 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
790 This command sends out any information held in the user file which can
791 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
792 and Homenode. PC41s are only sent for the information that is available.
794 === 0^HELP^The HELP Command
795 HELP is available for a number of commands. The syntax is:-
799 Where <cmd> is the name of the command you want help on.
801 All commands can be abbreviated, so SHOW/DX can be abbreviated
802 to SH/DX, ANNOUNCE can be shortened to AN and so on.
804 Look at the APROPOS <string> command which will search the help database
805 for the <string> you specify and give you a list of likely commands
806 to look at with HELP.
808 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
809 This command attempts to re-initialise a link to a (usually) AK1A node
810 that has got confused, usually by a protocol loop of some kind. It may
811 work - but you usually will be better off simply disconnecting it (or
812 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
815 Best of luck - you will need it.
817 === 9^DEMONSTRATE <call> <command>^Demonstrate a command to another user
818 This command is provided so that sysops can demonstrate commands to
819 other users. It runs a command as though that user had typed it in and
820 then sends the output to that user, together with the command that
823 DEMO g7brn sh/dx iota oc209
826 Note that this command is similar to SPOOF and will have the same side
827 effects. Commands are run at the privilege of the user which is being
830 === 0^JOIN <group>^Join a chat or conference group
831 JOIN allows you to join a network wide conference group. To join a
832 group (called FOC in this case) type:-
836 See also CHAT, LEAVE, SHOW/CHAT
838 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
839 === 0^KILL <from msgno>-<to msgno>^Delete a range of messages
840 === 0^KILL from <regex>^Delete messages FROM a callsign or pattern
841 === 0^KILL to <regex>^Delete messages TO a callsign or pattern
842 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
843 Delete a message from the local system. You will only be able to
844 delete messages that you have originated or been sent (unless you are
849 Will delete all the messages that you own between msgnos 1234 and 1255.
853 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
857 will delete all messages to g1tlh.
861 will delete a message (usually a 'bulletin') from the whole cluster system.
863 This uses the subject field, so any messages that have exactly the
864 same subject will be deleted. Beware!
866 === 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
867 Deleting a message using the normal KILL commands only marks that message
868 for deletion. The actual deletion only happens later (usually two days later).
870 The KILL EXPUNGE command causes the message to be truly deleted more or less
873 It otherwise is used in the same way as the KILL command.
875 === 0^LEAVE <group>^Leave a chat or conference group
876 LEAVE allows you to leave a network wide conference group. To leave a
877 group (called FOC in this case) type:-
881 See also CHAT, JOIN, SHOW/CHAT
883 === 0^LINKS^Show which nodes is physically connected
884 This is a quick listing that shows which links are connected and
885 some information about them. See WHO for a list of all connections.
887 === 9^LOAD/ALIASES^Reload the command alias table
888 Reload the /spider/cmd/Aliases file after you have editted it. You
889 will need to do this if you change this file whilst the cluster is
890 running in order for the changes to take effect.
892 === 9^LOAD/BANDS^Reload the band limits table
893 Reload the /spider/data/bands.pl file if you have changed it manually whilst
894 the cluster is running.
896 === 9^LOAD/BADMSG^Reload the bad msg table
897 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
898 the cluster is running. This table contains a number of perl regular
899 expressions which are searched for in the fields targetted of each message.
900 If any of them match then that message is immediately deleted on receipt.
902 === 9^LOAD/BADWORDS^Reload the bad words table
903 Reload the /spider/data/badwords file if you have changed it manually whilst
904 the cluster is running. This file contains a list of words which, if found
905 on certain text portions of PC protocol, will cause those protocol frames
906 to be rejected. It will all put out a message if any of these words are
907 used on the announce, dx and talk commands. The words can be one or
908 more on a line, lines starting with '#' are ignored.
910 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
911 Normally, if you change a command file in the cmd or local_cmd tree it
912 will automatially be picked up by the cluster program. Sometimes it
913 can get confused if you are doing a lot of moving commands about or
914 delete a command in the local_cmd tree and want to use the normal one
915 again. Execute this command to reset everything back to the state it
916 was just after a cluster restart.
918 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
919 Reload the /spider/msg/forward.pl file if you have changed it
920 manually whilst the cluster is running.
922 === 5^LOAD/KEPS^Load new keps data
923 === 5^LOAD/KEPS [nn]^Load new keps data from message
924 If there is no message number then reload the current Keps data from
925 the Keps.pm data file. You create this file by running
927 /spider/perl/convkeps.pl <filename>
929 on a file containing NASA 2 line keps as a message issued by AMSAT.
931 If there is a message number, then it will take the message, run
932 convkeps.pl on it and then load the data, all in one step.
934 These messages are sent to ALL by GB7DJK (and others) from time to time.
936 === 9^LOAD/MESSAGES^Reload the system messages file
937 If you change the /spider/perl/Messages file (usually whilst
938 fiddling/writing new commands) you can have them take effect during a
939 cluster session by executing this command. You need to do this if get
942 unknown message 'xxxx' in lang 'en'
944 === 9^LOAD/PREFIXES^Reload the prefix table
945 Reload the /spider/data/prefix_data.pl file if you have changed it
946 manually whilst the cluster is running.
948 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
949 MERGE allows you to bring your spot and wwv database up to date. By default
950 it will request the last 10 spots and 5 WWVs from the node you select. The
951 node must be connected locally.
953 You can request any number of spots or wwv and although they will be appended
954 to your databases they will not duplicate any that have recently been added
955 (the last 2 days for spots and last month for WWV data).
957 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
958 Alter message parameters like To, From, Subject, whether private or bulletin
959 or return receipt (RR) is required or whether to keep this message from timing
962 MSG TO <msgno> <call> - change TO callsign to <call>
963 MSG FRom <msgno> <call> - change FROM callsign to <call>
964 MSG PRrivate <msgno> - set private flag
965 MSG NOPRrivate <msgno> - unset private flag
966 MSG RR <msgno> - set RR flag
967 MSG NORR <msgno> - unset RR flag
968 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
969 MSG NOKEep <msgno> - unset the keep flag
970 MSG SUbject <msgno> <new> - change the subject to <new>
971 MSG WAittime <msgno> - remove any waitting time for this message
972 MSG NOREad <msgno> - mark message as unread
973 MSG REad <msgno> - mark message as read
974 MSG QUeue - queue any outstanding bulletins
975 MSG QUeue 1 - queue any outstanding private messages
977 You can look at the status of a message by using:-
981 This will display more information on the message than DIR does.
983 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
984 Send some arbitrary text to a locally connected callsign. No
985 processing is done on the text. This command allows you to send PC
986 Protocol to unstick things if problems arise (messages get stuck
989 pc gb7djk PC33^GB7TLH^GB7DJK^400^
991 pc G1TLH Try doing that properly!!!
993 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
994 You can get rid of any message to or originating from your callsign using
995 this command. You can remove more than one message at a time.
997 === 5^KILL <from>-<to>^Remove a range of messages from the system
998 === 5^KILL FROM <call>^Remove all messages from a callsign
999 === 5^KILL TO <call>^Remove all messages to a callsign
1000 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
1001 Remove this message from the entire cluster system as well as your node.
1004 As a sysop you can kill any message on the system.
1006 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
1007 Send any text you like to the callsign requested. This is used mainly to send
1008 PC protocol to connected nodes either for testing or to unstick things.
1010 You can also use in the same way as a talk command to a connected user but
1011 without any processing, added of "from <blah> to <blah" or whatever.
1013 === 1^PING <node call>^Check the link quality between nodes
1014 This command allows you to send a frame to another cluster node on
1015 the network and get a return frame. The time it takes to do this
1016 is a good indication of the quality of the link. The actual time
1017 it takes is output to the console in seconds.
1018 Any visible cluster node can be PINGed.
1020 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
1021 This command allows you to send nearly any command to another DX Cluster
1022 node that is connected to the system.
1024 Whether you get any output is dependant on a) whether the other system knows
1025 that the node callsign of this cluster is in fact a node b) whether the
1026 other system is allowing RCMDs from this node and c) whether you have
1027 permission to send this command at all.
1029 === 0^READ^Read the next unread personal message addressed to you
1030 === 0^READ <msgno>^Read the specified message
1031 You can read any messages that are sent as 'non-personal' and also any
1032 message either sent by or sent to your callsign.
1035 As a sysop you may read any message on the system
1037 === 0^REJECT^Set a filter to reject something
1038 Create a filter to reject something
1040 There are 2 types of filter, accept and reject. See HELP FILTERING for more
1043 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
1044 Create an 'reject this announce' line for a filter.
1046 A reject filter line means that if the announce matches this filter it is
1047 passed onto the user. See HELP FILTERING for more info. Please read this
1048 to understand how filters work - it will save a lot of grief later on.
1050 You can use any of the following things in this line:-
1052 info <string> eg: iota or qsl
1053 by <prefixes> eg: G,M,2
1055 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1056 origin_itu <prefixes or numbers> or: G,GM,GW
1057 origin_zone <prefixes or numbers>
1058 origin_state <states> eg: VA,NH,RI,ME
1059 by_dxcc <prefixes or numbers>
1060 by_itu <prefixes or numbers>
1061 by_zone <prefixes or numbers>
1062 by_state <states> eg: VA,NH,RI,ME
1064 wx 1 filter WX announces
1065 dest <prefixes> eg: 6MUK,WDX (distros)
1069 rej/ann by_zone 14,15,16 and not by G,M,2
1071 You can use the tag 'all' to reject everything eg:
1075 but this probably for advanced users...
1077 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
1078 This version allows a sysop to set a filter for a callsign as well as the
1079 default for nodes and users eg:-
1082 reject/ann input node_default by G,M,2
1083 reject/ann user_default by G,M,2
1085 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
1086 Create a 'reject this spot' line for a filter.
1088 A reject filter line means that if the spot matches this filter it is
1089 dumped (not passed on). See HELP FILTERING for more info. Please read this
1090 to understand how filters work - it will save a lot of grief later on.
1092 You can use any of the following things in this line:-
1094 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1095 on <range> same as 'freq'
1096 call <prefixes> eg: G,PA,HB9
1097 info <string> eg: iota or qsl
1099 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1100 call_itu <prefixes or numbers> or: G,GM,GW
1101 call_zone <prefixes or numbers>
1102 call_state <states> eg: VA,NH,RI,ME
1103 by_dxcc <prefixes or numbers>
1104 by_itu <prefixes or numbers>
1105 by_zone <prefixes or numbers>
1106 by_state <states> eg: VA,NH,RI,ME
1110 'call' means the callsign that has spotted 'by' whoever.
1112 For frequencies, you can use any of the band names defined in
1113 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1114 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1115 this is more efficient than saying simply: on HF (but don't get
1116 too hung up about that)
1121 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1123 You can use the tag 'all' to reject everything eg:
1127 but this probably for advanced users...
1129 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
1130 Create an 'reject this routing PC Protocol' line for a filter.
1132 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1133 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1134 read this to understand how filters work - it will save a lot of grief later on.
1136 You can use any of the following things in this line:-
1138 call <prefixes> the callsign of the thingy
1139 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1140 call_itu <prefixes or numbers> or: G,GM,GW
1141 call_zone <prefixes or numbers>
1142 call_state <states> eg: VA,NH,RI,ME
1143 origin <prefixes> really the interface it came in on
1144 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1145 origin_itu <prefixes or numbers> or: G,GM,GW
1146 origin_zone <prefixes or numbers>
1147 origin_state <states> eg: VA,NH,RI,ME
1151 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1153 You can use the tag 'all' to reject everything eg:
1155 rej/route all (equiv to [very] restricted mode)
1157 as with ACCEPT/ROUTE 'by' is now a synonym for 'call'.
1159 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
1160 This version allows a sysop to set a filter for a callsign as well as the
1161 default for nodes and users eg:-
1163 reject/spot db0sue-7 1 by_zone 14,15,16
1164 reject/spot node_default all
1165 set/hops node_default 10
1167 reject/spot user_default by G,M,2
1169 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
1170 It is unlikely that you will want to do this, but if you do then you can
1171 filter on the following fields:-
1173 by <prefixes> eg: G,M,2
1175 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1176 origin_itu <prefixes or numbers> or: G,GM,GW
1177 origin_zone <prefixes or numbers>
1178 by_dxcc <prefixes or numbers>
1179 by_itu <prefixes or numbers>
1180 by_zone <prefixes or numbers>
1183 There are no examples because WCY Broadcasts only come from one place and
1184 you either want them or not (see UNSET/WCY if you don't want them).
1186 This command is really provided for future use.
1188 See HELP FILTER for information.
1190 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
1191 This version allows a sysop to set a filter for a callsign as well as the
1192 default for nodes and users eg:-
1194 reject/wcy gb7djk all
1196 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
1197 It is unlikely that you will want to do this, but if you do then you can
1198 filter on the following fields:-
1200 by <prefixes> eg: G,M,2
1202 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1203 origin_itu <prefixes or numbers> or: G,GM,GW
1204 origin_zone <prefixes or numbers>
1205 by_dxcc <prefixes or numbers>
1206 by_itu <prefixes or numbers>
1207 by_zone <prefixes or numbers>
1212 reject/wwv by_zone 14,15,16
1214 is probably the only useful thing to do (which will only show WWV broadcasts
1215 by stations in the US).
1217 See HELP FILTER for information.
1219 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
1220 This version allows a sysop to set a filter for a callsign as well as the
1221 default for nodes and users eg:-
1223 reject/wwv db0sue-7 1 by_zone 4
1224 reject/wwv node_default all
1226 reject/wwv user_default by W
1228 === 0^REPLY^Reply (privately) to the last message that you have read
1229 === 0^REPLY <msgno>^Reply (privately) to the specified message
1230 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1231 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1232 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1233 You can reply to a message and the subject will automatically have
1234 "Re:" inserted in front of it, if it isn't already present.
1236 You can also use all the extra qualifiers such as RR, PRIVATE,
1237 NOPRIVATE, B that you can use with the SEND command (see SEND
1238 for further details)
1240 === 9^SAVE [-d -t -a] <filename> "<cmd>" [...]^Save command output to a file
1241 This sysop only cammand allows you to save the output of one or more
1242 commands to a file. For example:-
1244 save /spider/packclus/dxstats show/dxstat
1246 will save the output of the normal command "show/dxstat" to the file
1247 "dxstats" in the files area.
1249 You can have some extra flags to the save which will either
1250 date stamp or time stamp or both the filename so:-
1252 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
1253 save -t /tmp/a <cmd> creates /tmp/a_2301Z
1254 save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
1256 The -a flag means append to the file instead of overwriting it.
1258 You can have more than one command on the line, to do this you MUST
1259 enclose each command in double quotes (") eg:-
1261 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
1265 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
1267 You can only write into places that the cluster has permission for (which
1268 is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
1269 need to create any directories you want to put stuff in beforehand as well.
1271 It is likely that you will want to run these commands in a crontab type
1272 situation. You would do that something like:-
1274 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
1276 Note that you still enclose each command with (") characters but you must
1277 enclose the entire save command in (') characters.
1279 Now in fact, this can be varied if you know what you are doing. See the
1280 admin manual for more details.
1282 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1283 === 0^SEND RR <call>^Send a message and ask for a read receipt
1284 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1285 === 0^SEND PRIVATE <call>^Send a personal message
1286 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1287 All the SEND commands will create a message which will be sent either to
1288 an individual callsign or to one of the 'bulletin' addresses.
1290 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1291 it will mark the message as personal and send it to the cluster node that
1292 that callsign is connected to. If the <call> you have specified is in fact
1293 a known bulletin category on your node (eg: ALL) then the message should
1294 automatically become a bulletin.
1296 You can have more than one callsign in all of the SEND commands.
1298 You can have multiple qualifiers so that you can have for example:-
1300 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1302 which should send a copy of message 123 to G1TLH and G0RDI and you will
1303 receive a read receipt when they have read the message.
1305 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1306 SP is an alias for SEND PRIVATE
1308 The system will ask you for a subject. Conventionally this should be
1309 no longer than 29 characters for compatibility. Most modern cluster
1310 software should accept more.
1312 You will now be prompted to start entering your text.
1314 You finish the message by entering '/EX' on a new line. For instance:
1321 If you have started a message and you don't want to keep it then you
1322 can abandon the message with '/ABORT' on a new line, like:-
1326 oh I just can't be bothered with this
1329 If you abort the message it will NOT be sent.
1331 When you are entering the text of your message, most normal output (such
1332 as DX announcements and so on are suppressed and stored for latter display
1333 (upto 20 such lines are stored, as new ones come along, so the oldest
1336 Also, you can enter normal commands commands (and get the output
1337 immediately) whilst in the middle of a message. You do this by typing
1338 the command preceeded by a '/' character on a new line, so:-
1340 /dx g1tlh 144010 strong signal
1342 Will issue a dx annoucement to the rest of the cluster.
1344 Also, you can add the output of a command to your message by preceeding
1345 the command with '//', thus :-
1349 This will show YOU the output from SH/VHFTABLE and also store it in the
1352 You can carry on with the message until you are ready to send it.
1353 === 0^SET/ADDRESS <your address>^Record your postal address
1355 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1356 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1358 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1359 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1360 The announce system on legacy cluster nodes is used as a talk
1361 substitute because the network is so poorly connected. If you:
1365 you will suppress several of these announces, you may miss the odd
1366 useful one as well, but you would probably miss them anyway in the
1367 welter of useless ones.
1371 allows you to see them again. This is the default.
1373 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1375 === 8^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1376 === 8^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1377 Setting a word as 'baddx' will prevent spots with that word in the
1378 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1379 further. They will not be displayed and they will not be sent onto
1382 The word must be written in full, no wild cards are allowed eg:-
1384 set/baddx FORSALE VIDEO FR0G
1386 To allow a word again, use the following command ...
1390 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1391 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1392 Setting a callsign as a 'badnode' will prevent spots from that node
1393 going any further. They will not be displayed and they will not be
1394 sent onto other nodes.
1396 The call must be a full eg:-
1400 will stop anything from K1TTT. If you want SSIDs as well then you must
1401 enter them specifically.
1405 will allow spots from him again.
1407 Use with extreme care. This command may well be superceeded by FILTERing.
1409 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1410 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1411 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1412 going any further. They will not be displayed and they will not be
1413 sent onto other nodes.
1415 The call must be written in full, no wild cards are allowed eg:-
1417 set/badspotter VE2STN
1419 will stop anything from VE2STN. This command will automatically
1420 stop spots from this user, regardless of whether or which SSID
1421 he uses. DO NOT USE SSIDs in the callsign, just use the callsign
1424 unset/badspotter VE2STN
1426 will allow spots from him again.
1428 Use with extreme care. This command may well be superceded by FILTERing.
1430 === 8^SET/BADWORD <word>..^Stop things with this word being propagated
1431 === 8^UNSET/BADWORD <word>..^Propagate things with this word again
1432 Setting a word as a 'badword' will prevent things like spots,
1433 announces or talks with this word in the the text part from going any
1434 further. They will not be displayed and they will not be sent onto
1437 The word must be written in full, no wild cards are allowed eg:-
1439 set/badword annihilate annihilated annihilation
1441 will stop anything with these words in the text.
1443 unset/badword annihilated
1445 will allow text with this word again.
1447 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1448 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1450 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1452 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1454 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1455 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1456 You can choose to log several different levels. The levels are
1464 You can show what levels you are logging with SHOW/DEBUG
1466 === 0^SET/DX^Allow DX messages to come out on your terminal
1467 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1469 === 0^SET/DXCQ^Show CQ Zones on the end of DX announcements
1470 === 0^UNSET/DXCQ^Stop CQ Zones on the end of DX announcements
1471 Display both the Spotter's and the Spotted's CQ Zone on the end
1472 of a DX announcement (there is just enough room). Some user programs
1473 cannot cope with this. The Spotter's CQ is on the RHS of the
1474 time, the Spotted's CQ is on the LHS.
1476 Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE
1478 Do a STAT/USER to see which flags you have set if you are confused.
1480 === 0^SET/DXITU^Show ITU Zones on the end of DX announcements
1481 === 0^UNSET/DXITU^Stop ITU Zones on the end of DX announcements
1482 Display both the Spotter's and the Spotted's ITU Zone on the end
1483 of a DX announcement (there is just enough room). Some user programs
1484 cannot cope with this. The Spotter's ITU is on the RHS of the
1485 time, the Spotted's ITU is on the LHS.
1487 Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE
1489 Do a STAT/USER to see which flags you have set if you are confused.
1491 === 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
1492 === 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
1493 A standard feature which is enabled in version 1.43 and above is
1494 that if the spotter's grid square is known it is output on the end
1495 of a DX announcement (there is just enough room). Some user programs
1496 cannot cope with this. You can use this command to reset (or set)
1499 Conflicts with: SET/DXCQ, SET/DXITU
1501 Do a STAT/USER to see which flags you have set if you are confused.
1503 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1505 === 0^SET/ECHO^Make the cluster echo your input
1506 === 0^UNSET/ECHO^Stop the cluster echoing your input
1507 If you are connected via a telnet session, different implimentations
1508 of telnet handle echo differently depending on whether you are
1509 connected via port 23 or some other port. You can use this command
1510 to change the setting appropriately.
1512 The setting is stored in your user profile.
1514 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1516 === 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
1517 === 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
1518 If any personal messages come in for your callsign then you can use
1519 these commands to control whether they are forwarded onto your email
1520 address. To enable the forwarding do something like:-
1522 SET/EMAIL mike.tubby@somewhere.com
1524 You can have more than one email address (each one separated by a space).
1525 Emails are forwarded to all the email addresses you specify.
1527 You can disable forwarding by:-
1531 === 0^SET/HERE^Tell the system you are present at your terminal
1532 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1534 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1535 Tell the cluster system where you normally connect to. Any Messages sent
1536 to you will normally find their way there should you not be connected.
1540 === 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
1541 === 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
1542 Set the hop count for a particular type of broadcast for a node.
1544 This command allows you to set up special hop counts for a node
1545 for currently: announce, spots, wwv and wcy broadcasts.
1548 set/hops gb7djk ann 10
1549 set/hops gb7mbc spots 20
1551 Set SHOW/HOPS for information on what is already set. This command
1552 creates a filter and works in conjunction with the filter system.
1554 You can unset the hops with command UNSET/HOPS. For example:-
1556 unset/hops gb7djk ann
1557 unset/hops gb7mbc spots
1560 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1561 Connect a node to your system in such a way that you are a full protocol
1562 member of its network and can see all spots on it, but nothing either leaks
1563 out from it nor goes back into from the rest of the nodes connected to you.
1565 You can potentially connect several nodes in this way.
1567 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1568 Remove isolation from a node - SET/ISOLATE
1570 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1571 You can select the language that you want the cluster to use. Currently
1572 the languages available are en (English), de (German), es (Spanish),
1573 Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
1575 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1576 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1577 In order to get accurate headings and such like you must tell the system
1578 what your latitude and longitude is. If you have not yet done a SET/QRA
1579 then this command will set your QRA locator for you. For example:-
1580 SET/LOCATION 52 22 N 0 57 E
1582 === 0^SET/LOGININFO^Inform when a station logs in locally
1583 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1585 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1586 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1588 === 0^SET/NAME <your name>^Set your name
1589 Tell the system what your name is eg:-
1592 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1593 Tell the system that the call(s) are to be treated as AK1A cluster and
1594 fed PC Protocol rather normal user commands.
1596 === 8^SET/OBSCOUNT <count> <call>^Set the 'pump-up' obscelence PING counter
1597 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1598 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1599 counter which is decremented on every outgoing ping and then reset to
1600 the 'obscount' value on every incoming ping. The default value of this
1603 What this means is that a neighbouring node will be pinged twice at
1604 (default) 300 second intervals and if no reply has been heard just before
1605 what would be the third attempt, that node is disconnected.
1607 If a ping is heard then the obscount is reset to the full value. Using
1608 default values, if a node has not responded to a ping within 15 minutes,
1611 You can set this parameter between 1 and 9.
1613 It is STRONGLY recommended that you don't change the default.
1615 === 0^SET/PAGE <lines per page>^Set the lines per page
1616 Tell the system how many lines you wish on a page when the number of line
1617 of output from a command is more than this. The default is 20. Setting it
1618 explicitly to 0 will disable paging.
1622 The setting is stored in your user profile.
1624 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1625 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1626 in order to determine the rolling quality of the link and, in future, to
1627 affect routing decisions. The default interval is 300 secs or 5 minutes.
1629 You can use this command to set a different interval. Please don't.
1631 But if you do the value you enter is treated as minutes up 30 and seconds
1632 for numbers greater than that.
1634 This is used also to help determine when a link is down at the far end
1635 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1636 for more information.
1638 If you must change it (and it may be useful for internet connected nodes
1639 on dynamic IP addresses that go away after a set time of usage) the time
1640 can be specified as:-
1642 5 which if less than 30 is converted to minutes otherwise is
1643 taken as the no of seconds between pings.
1648 Please be aware that this causes traffic to occur on the link, setting
1649 this value too low may annoy your neighbours beyond the point of
1652 You can switch this off by setting it to 0.
1654 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1655 Set the privilege level on a callsign. The privilege levels that pertain
1656 to commands are as default:-
1658 1 - allow remote nodes normal user RCMDs
1659 5 - various privileged commands (including shutdown, but not disc-
1660 connect), the normal level for another node.
1661 8 - more privileged commands (including disconnect)
1662 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1664 If you are a sysop and you come in as a normal user on a remote connection
1665 your privilege will automatically be set to 0.
1667 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1668 You can use this command to 'protect' this session from unauthorised
1669 use. If you want to get your normal privilege back you will need to
1670 either logout and login again (if you are on a console) or use the
1673 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1674 The password for a user can only be set by a full sysop. The string
1675 can contain any characters.
1677 The way this field is used depends on context. If it is being used in
1678 the SYSOP command context then you are offered 5 random numbers and you
1679 have to supply the corresponding letters. This is now mainly for ax25
1682 If it is being used on incoming telnet connections then, if a password
1685 set/var $main::passwdreq = 1
1687 command is executed in the startup script, then a password prompt is
1688 given after the normal 'login: ' prompt.
1690 === 0^SET/PASSWORD^Set your own password
1691 This command only works for a 'telnet' user (currently). It will
1692 only work if you have a password already set. This initial password
1693 can only be set by the sysop.
1695 When you execute this command it will ask you for your old password,
1696 then ask you to type in your new password twice (to make sure you
1697 get it right). You may or may not see the data echoed on the screen
1698 as you type, depending on the type of telnet client you have.
1700 === 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
1701 This command allows the sysop to completely delete and remove a
1702 password for a user.
1704 === 0^SET/PROMPT <string>^Set your prompt to <string>
1705 === 0^UNSET/PROMPT^Set your prompt back to default
1706 This command will set your user prompt to exactly the string that you
1707 say. The point of this command to enable a user to interface to programs
1708 that are looking for a specific prompt (or else you just want a different
1713 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
1716 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1717 Tell the system that the call(s) are to be treated as DXSpider node and
1718 fed new style DX Protocol rather normal user commands.
1720 === 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
1721 === 0^SET/QRA <locator>^Set your QRA Grid locator
1722 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1723 done a SET/LOCATION then your latitude and longitude will be set roughly
1724 correctly (assuming your locator is correct ;-). For example:-
1727 === 0^SET/QTH <your qth>^Set your QTH
1728 Tell the system where you are. For example:-
1729 SET/QTH East Dereham, Norfolk
1731 === 9^SET/REGISTER <call> ...^Mark a user as registered
1732 === 9^UNSET/REGISTER <call> ...^Mark a user as not registered
1733 Registration is a concept that you can switch on by executing the
1735 set/var $main::regreq = 1
1737 command (usually in your startup file)
1739 If a user is NOT registered then, firstly, instead of the normal
1740 motd file (/spider/data/motd) being sent to the user at startup, the
1741 user is sent the motd_nor file instead. Secondly, the non registered
1742 user only has READ-ONLY access to the node. The non-registered user
1743 cannot use DX, ANN etc.
1745 The only exception to this is that a non-registered user can TALK or
1746 SEND messages to the sysop.
1748 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1749 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1751 === 9^SET/USDB <call> <state> <city>^add/update a US DB callsign
1752 This command allows you to add or alter a callsign in the US state
1753 database. Use with extreme caution. Anything you do here will be
1754 overwritten by any weekly updates that affect this callsign
1756 set/usdb g1tlh nh downtown rindge
1758 see also DELETE/USDB
1760 === 0^SET/USSTATE^Allow US State info on the end of DX announcements
1761 === 0^UNSET/USSTATE^Stop US State info on the end of DX announcements
1762 If the spotter's or spotted's US State is known it is output on the
1763 end of a DX announcement (there is just enough room).
1765 A spotter's state will appear on the RHS of the time (like
1766 SET/DXGRID) and the spotted's State will appear on the LHS of the
1767 time field. Any information found will override any locator
1768 information from SET/DXGRID.
1770 Some user programs cannot cope with this. You can use this command
1771 to reset (or set) this feature.
1773 Conflicts with: SET/DXCQ, SET/DXITU
1775 Do a STAT/USER to see which flags you have set if you are confused.
1777 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1778 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1780 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1781 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1783 === 0^SET/WX^Allow WX messages to come out on your terminal
1784 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1786 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1787 Display all the bad dx callsigns in the system, see SET/BADDX
1788 for more information.
1790 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1791 Display all the bad node callsigns in the system, see SET/BADNODE
1792 for more information.
1794 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1795 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1796 for more information.
1798 === 1^SHOW/BADWORD^Show all the bad words in the system
1799 Display all the bad words in the system, see SET/BADWORD
1800 for more information.
1802 === 0^SHOW/CHAT [<group>] [<lines>]^Show any chat or conferencing
1803 This command allows you to see any chat or conferencing that has
1804 occurred whilst you were away. SHOW/CHAT on its own will show data for
1805 all groups. If you use a group name then it will show only chat for
1808 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1809 This command allows you to see all the users that can be seen
1810 and the nodes to which they are connected.
1812 This command is normally abbreviated to: sh/c
1814 Normally, the list returned will be just for the nodes from your
1815 country (because the list otherwise will be very long).
1819 will produce a complete list of all nodes.
1821 BE WARNED: the list that is returned can be VERY long
1823 It is possible to supply a node or part of a prefix and you will get
1824 a list of the users for that node or list of nodes starting with
1831 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1832 Show all the nodes connected to this node.
1834 === 1^SHOW/CONNECT^Show all the active connections
1835 This command shows information on all the active connections known to
1836 the node. This command gives slightly more information than WHO.
1838 === 0^SHOW/CONTEST <year and month>^Show all the contests for a month
1839 Show all known contests which are maintained at http://www.sk3bg.se/contest/
1840 for a particular month or year. The format is reasonably flexible.
1846 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1847 This is very nearly the same as SHOW/TIME, the only difference the format
1848 of the date string if no arguments are given.
1850 If no prefixes or callsigns are given then this command returns the local
1851 time and UTC as the computer has it right now. If you give some prefixes
1852 then it will show UTC and UTC + the local offset (not including DST) at
1853 the prefixes or callsigns that you specify.
1855 === 0^SHOW/DB0SDX <callsign>^Show QSL infomation from DB0SDX database
1856 This command queries the DB0SDX QSL server on the internet
1857 and returns any information available for that callsign. This service
1858 is provided for users of this software by http://www.qslinfo.de.
1860 See also SHOW/QRZ, SHOW/WM7D.
1862 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1864 === 0^SHOW/DX^Interrogate the spot database
1865 If you just type SHOW/DX you will get the last so many spots
1866 (sysop configurable, but usually 10).
1868 In addition you can add any number of these commands in very nearly
1869 any order to the basic SHOW/DX command, they are:-
1871 on <band> - eg 160m 20m 2m 23cm 6mm
1872 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1873 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
1876 <number> - the number of spots you want
1877 <from>-<to> - <from> spot no <to> spot no in the selected list
1880 <prefix> - for a spotted callsign beginning with <prefix>
1881 *<suffix> - for a spotted callsign ending in <suffix>
1882 *<string>* - for a spotted callsign containing <string>
1884 day <number> - starting <number> days ago
1885 day <from>-<to> - <from> days <to> days ago
1888 info <text> - any spots containing <text> in the info or remarks
1890 by <call> - any spots spotted by <call> (spotter <call> is the
1893 qsl - this automatically looks for any qsl info on the call
1894 held in the spot database.
1896 iota [<iota>] - If the iota island number is missing it will look for
1897 the string iota and anything which looks like an iota
1898 island number. If you specify then it will look for
1901 qra [<locator>] - this will look for the specific locator if you specify
1902 one or else anything that looks like a locator.
1904 dxcc - treat the prefix as a 'country' and look for spots
1905 from that country regardless of actual prefix.
1908 You can also use this with the 'by' keyword so
1911 real or rt - Format the output the same as for real time spots. The
1912 formats are deliberately different (so you can tell
1913 one sort from the other). This is useful for some
1914 logging programs that can't cope with normal sh/dx
1915 output. An alias of SHOW/FDX is available.
1917 filter - Filter the spots, before output, with the user's
1918 spot filter. An alias of SHOW/MYDX is available.
1920 zone <zones> - look for spots in the cq zone (or zones) specified.
1921 zones are numbers separated by commas.
1923 by_zone <zones> - look for spots spotted by people in the cq zone
1926 itu <itus> - look for spots in the itu zone (or zones) specified
1927 itu zones are numbers separated by commas.
1929 by_itu <itus> - look for spots spotted by people in the itu zone
1932 state <list> - look for spots in the US state (or states) specified
1933 The list is two letter state codes separated by commas.
1935 by_state <list> - look for spots spotted by people in the US state
1941 SH/DX on 20m info iota
1942 SH/DX 9a on vhf day 30
1948 SH/DX dxcc oq2 by w dxcc
1952 SH/DX by_state in,oh
1954 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1955 This command takes the <prefix> (which can be a full or partial
1956 callsign if desired), looks up which internal country number it is
1957 and then displays all the spots as per SH/DX for that country.
1959 This is now an alias for 'SHOW/DX DXCC'
1961 The options for SHOW/DX also apply to this command.
1965 SH/DXCC W on 20m iota
1967 This can be done with the SHOW/DX command like this:-
1970 SH/DX dxcc w on 20m iota
1972 This is an alias for: SH/DX dxcc
1974 === 0^SHOW/FDX^Show the DX data in realtime format.
1975 Normally SHOW/DX outputs spot data in a different format to the
1976 realtime data. This is a deliberate policy (so you can tell the
1977 difference between the two). Some logging programs cannot handle
1978 this so SHOW/FDX outputs historical data in real time format.
1980 This is an alias for: SHOW/DX real
1982 === 0^SHOW/DXSTATS [days] [date]^Show the DX Statistics
1983 Show the total DX spots for the last <days> no of days (default is 31),
1984 starting from a <date> (default: today).
1986 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1987 SHOW/FILES on its own will show you a list of the various fileareas
1988 available on the system. To see the contents of a particular file
1991 where <filearea> is the name of the filearea you want to see the
1994 You can also use shell globbing characters like '*' and '?' in a
1995 string to see a selection of files in a filearea eg:-
1996 SH/FILES bulletins arld*
1998 See also TYPE - to see the contents of a file.
2000 === 0^SHOW/FILTER^Show the contents of all the filters you have set
2001 Show the contents of all the filters that are set. This command displays
2002 all the filters set - for all the various categories.
2004 === 0^SHOW/HFSTATS [days] [date]^Show the HF DX Statistics
2005 Show the HF DX spots breakdown by band for the last <days> no of days
2006 (default is 31), starting from a <date> (default: today).
2008 === 0^SHOW/HFTABLE [days] [date] [prefix ...]^Show the HF DX Spotter Table
2009 Show the HF DX Spotter table for the list of prefixes for the last
2010 <days> no of days (default is 31), starting from a <date> (default: today).
2012 If there are no prefixes then it will show the table for your country.
2014 Remember that some countries have more than one "DXCC country" in them
2015 (eg G :-), to show them (assuming you are not in G already which is
2016 specially treated in the code) you must list all the relevant prefixes
2018 sh/hftable g gm gd gi gj gw gu
2020 Note that the prefixes are converted into country codes so you don't have
2021 to list all possible prefixes for each country.
2023 If you want more or less days than the default simply include the
2024 number you require:-
2028 If you want to start at a different day, simply add the date in some
2031 sh/hftable 2 25nov02
2032 sh/hftable 2 25-nov-02
2034 sh/hftable 2 25/11/02
2036 This will show the stats for your DXCC for that CQWW contest weekend.
2038 You can specify either prefixes or full callsigns (so you can see how you
2039 did against all your mates). You can also say 'all' which will then print
2040 the worldwide statistics.
2044 === 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
2045 This command shows the hop counts set up for a node. You can specify
2046 which category you want to see. If you leave the category out then
2047 all the categories will be listed.
2049 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
2051 === 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
2053 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
2054 This command outputs a short section of the system log. On its own
2055 it will output a general logfile. With the optional callsign it will
2056 show output from the log associated with that callsign.
2058 === 0^SHOW/MOON [ndays] [<prefix>|<callsign>]^Show Moon rise and set times
2059 Show the Moon rise and set times for a (list of) prefixes or callsigns,
2060 together with the azimuth and elevation of the sun currently at those
2063 If you don't specify any prefixes or callsigns, it will show the times for
2064 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2065 together with the current azimuth and elevation.
2067 In addition, it will show the illuminated fraction of the moons disk.
2069 If all else fails it will show the Moonrise and set times for the node
2070 that you are connected to.
2077 You can also use this command to see into the past or the future, so
2078 if you want to see yesterday's times then do:-
2082 or in three days time:-
2086 Upto 366 days can be checked both in the past and in the future.
2088 Please note that the rise and set times are given as the UT times of rise and
2089 set on the requested UT day.
2091 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
2092 This command allow you to estimate the likelihood of you contacting
2093 a station with the prefix you have specified. The output assumes a modest
2094 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
2096 The result predicts the most likely operating frequencies and signal
2097 levels for high frequency (shortwave) radio propagation paths on
2098 specified days of the year and hours of the day. It is most useful for
2099 paths between 250 km and 6000 km, but can be used with reduced accuracy
2100 for paths shorter or longer than this.
2102 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2103 used to predict the MUF given the predicted flux, day of the year,
2104 hour of the day and geographic coordinates of the transmitter and
2105 receiver. This routine is reasonably accurate for the purposes here,
2106 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2107 than the programs used by major shortwave broadcasting organizations,
2108 such as the Voice of America.
2110 The command will display some header information detailing its
2111 assumptions, together with the locations, latitude and longitudes and
2112 bearings. It will then show UTC (UT), local time at the other end
2113 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2114 (Zen) and the likely signal strengths. Then for each frequency for which
2115 the system thinks there is a likelihood of a circuit it prints a value.
2117 The value is currently a likely S meter reading based on the conventional
2118 6dB / S point scale. If the value has a '+' appended it means that it is
2119 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
2120 there is likely to be much fading and by an 's' that the signal is likely
2123 By default SHOW/MUF will show the next two hours worth of data. You
2124 can specify anything up to 24 hours worth of data by appending the no of
2125 hours required after the prefix. For example:-
2131 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2132 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2133 Location Lat / Long Azim
2134 East Dereham, Norfolk 52 41 N 0 57 E 47
2135 United-States-W 43 0 N 87 54 W 299
2136 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2137 18 23 11.5 -35 mS0+ mS2 S3
2138 19 0 11.2 -41 mS0+ mS2 S3
2140 indicating that you will have weak, fading circuits on top band and
2141 80m but usable signals on 40m (about S3).
2147 will get you the above display, but with the next 24 hours worth of
2153 Gives you an estimate of the long path propagation characterics. It
2154 should be noted that the figures will probably not be very useful, nor
2155 terrible accurate, but it is included for completeness.
2157 === 0^SHOW/MYDX^Show the DX data filtered with your spot filter.
2158 SHOW/DX potentially shows all the spots available in the system. Using
2159 SHOW/MYDX will, instead, filter the availble spots using any spot filter
2160 that you have set, first.
2162 This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
2163 you to customise the spots that you receive.
2165 So if you have said: ACC/SPOT on hf
2167 Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
2168 options on SH/DX can still be used.
2170 === 0^SHOW/NEWCONFIGURATION [<node>]^Show all the nodes and users visible
2171 This command allows you to see all the users that can be seen
2172 and the nodes to which they are connected.
2174 This command produces essentially the same information as
2175 SHOW/CONFIGURATION except that it shows all the duplication of
2176 any routes that might be present It also uses a different format
2177 which may not take up quite as much space if you don't have any
2180 BE WARNED: the list that is returned can be VERY long
2182 === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
2183 Show all the nodes connected to this node in the new format.
2185 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
2186 Show the type and version (if connected) of the nodes specified on the
2187 command line. If no callsigns are specified then a sorted list of all
2188 the non-user callsigns known to the system will be displayed.
2190 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
2191 This command takes the <callsign> (which can be a full or partial
2192 callsign or a prefix), looks up which internal country number
2193 it is and then displays all the relevant prefixes for that country
2194 together with the internal country no, the CQ and ITU regions.
2198 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
2199 Show the name and location where every program module was load from. This
2200 is useful for checking where you think you have loaded a .pm file from.
2202 === 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
2203 === 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
2204 This is a multipurpose command that allows you either to calculate the
2205 distance and bearing between two locators or (if only one locator is
2206 given on the command line) the distance and beraing from your station
2207 to the locator. For example:-
2212 The first example will show the distance and bearing to the locator from
2213 yourself, the second example will calculate the distance and bearing from
2214 the first locator to the second. You can use 4 or 6 character locators.
2216 It is also possible to convert a latitude and longitude to a locator by
2217 using this command with a latitude and longitude as an argument, for
2220 SH/QRA 52 41 N 0 58 E
2222 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
2223 This command queries the QRZ callbook server on the internet
2224 and returns any information available for that callsign. This service
2225 is provided for users of this software by http://www.qrz.com
2227 See also SHOW/WM7D for an alternative.
2229 === 0^SHOW/DXQSL <callsign>^Show any QSL info gathered from spots
2230 The node collects information from the comment fields in spots (things
2231 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
2233 This command allows you to interrogate that database and if the callsign
2234 is found will display the manager(s) that people have spotted. This
2235 information is NOT reliable, but it is normally reasonably accurate if
2236 it is spotted enough times.
2242 You can check the raw input spots yourself with:-
2246 This gives you more background information.
2248 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
2250 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
2251 This command allows you to see to which node the callsigns specified are
2252 connected. It is a sort of inverse sh/config.
2256 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
2257 Show the tracking data from your location to the satellite of your choice
2258 from now on for the next few hours.
2260 If you use this command without a satellite name it will display a list
2261 of all the satellites known currently to the system.
2263 If you give a name then you can obtain tracking data of all the passes
2264 that start and finish 5 degrees below the horizon. As default it will
2265 give information for the next three hours for every five minute period.
2267 You can alter the number of hours and the step size, within certain
2270 Each pass in a period is separated with a row of '-----' characters
2275 SH/SAT FENGYUN1 12 2
2277 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
2278 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
2279 Show the information known about a callsign and whether (and where)
2280 that callsign is connected to the cluster.
2284 If no callsign is given then show the information for yourself.
2286 === 0^SHOW/SUN [ndays] [<prefix>|<callsign>]^Show sun rise and set times
2287 Show the sun rise and set times for a (list of) prefixes or callsigns,
2288 together with the azimuth and elevation of the sun currently at those
2291 If you don't specify any prefixes or callsigns, it will show the times for
2292 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2293 together with the current azimuth and elevation.
2295 If all else fails it will show the sunrise and set times for the node
2296 that you are connected to.
2301 SH/SUN G1TLH K9CW ZS
2303 You can also use this command to see into the past or the future, so
2304 if you want to see yesterday's times then do:-
2308 or in three days time:-
2312 Upto 366 days can be checked both in the past and in the future.
2314 Please note that the rise and set times are given as the UT times of rise
2315 and set on the requested UT day.
2317 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
2318 If no prefixes or callsigns are given then this command returns the local
2319 time and UTC as the computer has it right now. If you give some prefixes
2320 then it will show UTC and UTC + the local offset (not including DST) at
2321 the prefixes or callsigns that you specify.
2323 === 0^SHOW/USDB [call ..]^Show information held on the FCC Call database
2324 Show the City and State of a Callsign held on the FCC database if
2325 his is being run on this system, eg:-
2329 === 0^SHOW/VHFSTATS [days] [date]^Show the VHF DX Statistics
2330 Show the VHF DX spots breakdown by band for the last
2331 <days> no of days (default is 31), starting from a date (default: today).
2333 === 0^SHOW/VHFTABLE [days] [date] [prefix ...]^Show the VHF DX Spotter Table
2334 Show the VHF DX Spotter table for the list of prefixes for the last
2335 <days> no of days (default is 31), starting from a date (default: today).
2337 If there are no prefixes then it will show the table for your country.
2339 Remember that some countries have more than one "DXCC country" in them
2340 (eg G :-), to show them (assuming you are not in G already which is
2341 specially treated in the code) you must list all the relevant prefixes
2343 sh/vhftable g gm gd gi gj gw gu
2345 Note that the prefixes are converted into country codes so you don't have
2346 to list all possible prefixes for each country.
2348 If you want more or less days than the default simply include the
2349 number you require:-
2353 If you want to start at a different day, simply add the date in some
2356 sh/vhftable 2 25nov02
2357 sh/vhftable 2 25-nov-02
2358 sh/vhftable 2 021125
2359 sh/vhftable 2 25/11/02
2361 This will show the stats for your DXCC for that CQWW contest weekend.
2363 You can specify either prefixes or full callsigns (so you can see how you
2364 did against all your mates). You can also say 'all' which will then print
2365 the worldwide statistics.
2369 === 0^SHOW/WCY^Show last 10 WCY broadcasts
2370 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
2371 Display the most recent WCY information that has been received by the system
2373 === 0^SHOW/WM7D <callsign>^Show callbook details on a US callsigns
2374 This command queries the WM7D callbook server on the internet
2375 and returns any information available for that US callsign. This service
2376 is provided for users of this software by http://www.wm7d.net.
2380 === 0^SHOW/WWV^Show last 10 WWV broadcasts
2381 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
2382 Display the most recent WWV information that has been received by the system
2384 === 5^SHUTDOWN^Shutdown the cluster
2385 Shutdown the cluster and disconnect all the users
2387 === 9^SPOOF <call> <command>^Do a command as though you are another user
2388 This command is provided so that sysops can set a user's parameters without
2389 me having to write a special 'sysop' version for every user command. It
2390 allows you to pretend that you are doing the command as the user you specify.
2394 SPOOF G1TLH set/name Dirk
2395 SPOOF G1TLH set/qra JO02LQ
2397 === 5^STAT/DB <dbname>^Show the status of a database
2398 Show the internal status of a database descriptor.
2400 Depending on your privilege level you will see more or less information.
2401 This command is unlikely to be of much use to anyone other than a sysop.
2403 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
2404 Show the internal status of the channel object either for the channel that
2405 you are on or else for the callsign that you asked for.
2407 Only the fields that are defined (in perl term) will be displayed.
2409 === 1^STAT/MSG^Show the status of the message system
2410 === 1^STAT/MSG <msgno>^Show the status of a message
2411 This command shows the internal status of a message and includes information
2412 such as to whom it has been forwarded, its size, origin etc etc.
2414 If no message number is given then the status of the message system is
2417 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
2418 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
2420 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
2421 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
2423 === 5^STAT/USER [<callsign>]^Show the full status of a user
2424 Shows the full contents of a user record including all the secret flags
2427 Only the fields that are defined (in perl term) will be displayed.
2429 === 0^SYSOP^Regain your privileges if you login remotely
2430 The system automatically reduces your privilege level to that of a
2431 normal user if you login in remotely. This command allows you to
2432 regain your normal privilege level. It uses the normal system: five
2433 numbers are returned that are indexes into the character array that is
2434 your assigned password (see SET/PASSWORD). The indexes start from
2437 You are expected to return a string which contains the characters
2438 required in the correct order. You may intersperse those characters
2439 with others to obscure your reply for any watchers. For example (and
2440 these values are for explanation :-):
2442 password = 012345678901234567890123456789
2446 aa2bbbb0ccc5ddd7xxx3n
2450 They will all match. If there is no password you will still be offered
2451 numbers but nothing will happen when you input a string. Any match is
2454 === 0^TALK <call> [<text>]^Send a text message to another station
2455 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
2456 Send a short message to any other station that is visible on the cluster
2457 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2458 command, they don't have to be connected locally.
2460 The second form of TALK is used when other cluster nodes are connected
2461 with restricted information. This usually means that they don't send
2462 the user information usually associated with logging on and off the cluster.
2464 If you know that G3JNB is likely to be present on GB7TLH, but you can only
2465 see GB7TLH in the SH/C list but with no users, then you would use the
2466 second form of the talk message.
2468 If you want to have a ragchew with someone you can leave the text message
2469 out and the system will go into 'Talk' mode. What this means is that a
2470 short message is sent to the recipient telling them that you are in a
2471 'Talking' frame of mind and then you just type - everything you send will
2472 go to the station that you asked for.
2474 All the usual announcements, spots and so on will still come out on your
2477 If you want to do something (such as send a spot) you preceed the normal
2478 command with a '/' character, eg:-
2480 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2483 To leave talk mode type:
2487 If you are in 'Talk' mode, there is an extention to the '/' command which
2488 allows you to send the output to all the people you are talking to. You do
2489 with the '//' command. For example:-
2493 will send the hftable as you have it to all the people you are currently
2496 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
2497 Type out the contents of a file in a filearea. So, for example, in
2498 filearea 'bulletins' you want to look at file 'arld051' you would
2500 TYPE bulletins/arld051
2502 See also SHOW/FILES to see what fileareas are available and a
2505 === 0^WHO^Show who is physically connected
2506 This is a quick listing that shows which callsigns are connected and
2507 what sort of connection they have
2509 === 0^WX <text>^Send a weather message to local users
2510 === 0^WX FULL <text>^Send a weather message to all cluster users
2511 === 5^WX SYSOP <text>^Send a weather message to other clusters only
2512 Weather messages can sometimes be useful if you are experiencing an extreme
2513 that may indicate enhanced conditions