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/ANNOUNCE [0-9] <pattern>^Set an 'accept' filter line for announce
15 Create an 'accept this announce' line for a filter.
17 An accept filter line means that if the announce matches this filter it is
18 passed onto the user. See HELP FILTERING for more info. Please read this
19 to understand how filters work - it will save a lot of grief later on.
21 You can use any of the following things in this line:-
23 info <string> eg: iota or qsl
24 by <prefixes> eg: G,M,2
26 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
33 wx 1 filter WX announces
34 dest <prefixes> eg: 6MUK,WDX (distros)
39 acc/ann 2 by_zone 14,15,16
40 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
44 You can use the tag 'all' to accept everything eg:
48 but this probably for advanced users...
50 === 8^ACCEPT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
51 This version allows a sysop to set a filter for a callsign as well as the
52 default for nodes and users eg:-
55 accept/ann input node_default by G,M,2
56 accept/ann user_default by G,M,2
58 === 8^ACCEPT/ROUTE <call> [0-9] <pattern>^Set an 'accept' filter line for routing
59 Create an 'accept this routing PC Protocol' line for a filter.
61 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
62 it is passed thru that interface. See HELP FILTERING for more info. Please read this
63 to understand how filters work - it will save a lot of grief later on.
65 You can use any of the following things in this line:-
67 call <prefixes> the callsign of the thingy
68 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
71 origin <prefixes> really the interface it came in on
72 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
78 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
79 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
81 You can use the tag 'all' to accept everything eg:
86 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
87 Create an 'accept this spot' line for a filter.
89 An accept filter line means that if the spot matches this filter it is
90 passed onto the user. See HELP FILTERING for more info. Please read this
91 to understand how filters work - it will save a lot of grief later on.
93 You can use any of the following things in this line:-
95 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
96 on <range> same as 'freq'
97 call <prefixes> eg: G,PA,HB9
98 info <string> eg: iota or qsl
100 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
109 For frequencies, you can use any of the band names defined in
110 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
111 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
112 this is more efficient than saying simply: freq HF (but don't get
113 too hung up about that)
118 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
120 You can use the tag 'all' to accept everything, eg:
124 but this probably for advanced users...
127 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
128 This version allows a sysop to set a filter for a callsign as well as the
129 default for nodes and users eg:-
131 accept/spot db0sue-7 1 by_zone 14,15,16
132 accept/spot node_default all
133 set/hops node_default 10
135 accept/spot user_default by G,M,2
137 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
138 It is unlikely that you will want to do this, but if you do then you can
139 filter on the following fields:-
141 by <prefixes> eg: G,M,2
143 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
145 origin_zone <numbers>
151 There are no examples because WCY Broadcasts only come from one place and
152 you either want them or not (see UNSET/WCY if you don't want them).
154 This command is really provided for future use.
156 See HELP FILTER for information.
158 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
159 This version allows a sysop to set a filter for a callsign as well as the
160 default for nodes and users eg:-
162 accept/wcy node_default all
163 set/hops node_default 10
165 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
166 It is unlikely that you will want to do this, but if you do then you can
167 filter on the following fields:-
169 by <prefixes> eg: G,M,2
171 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
173 origin_zone <numbers>
183 is probably the only useful thing to do (which will only show WWV broadcasts
184 by stations in the US).
186 See HELP FILTER for information.
188 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
189 This version allows a sysop to set a filter for a callsign as well as the
190 default for nodes and users eg:-
192 accept/wwv db0sue-7 1 by_zone 4
193 accept/wwv node_default all
194 set/hops node_default 10
196 accept/wwv user_default by W,K
198 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
199 <text> is the text of the announcement you wish to broadcast
201 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
202 This will send your announcement cluster wide
204 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
206 === 0^APROPOS <string>^Search help database for <string>
207 Search the help database for <string> (it isn't case sensitive), and print
208 the names of all the commands that may be relevant.
210 === 0^BYE^Exit from the cluster
211 This will disconnect you from the cluster
213 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
214 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
215 When you send messages the fact that you have forwarded it to another node
216 is remembered so that it isn't sent again. When you have a new partner
217 node and you add their callsign to your /spider/msg/forward.pl file, all
218 outstanding non-private messages will be forwarded to them. This may well
219 be ALL the non-private messages. You can prevent this by using these
223 catchup GB7DJK 300 301 302 303 500-510
225 and to undo what you have just done:-
228 uncatchup GB7DJK 300 301 302 303 500-510
230 which will arrange for them to be forward candidates again.
232 Order is not important.
234 === 0^CLEAR/SPOTS [1|all]^Clear a spot filter line
235 This command allows you to clear (remove) a line in a spot filter or to
236 remove the whole filter.
238 If you have a filter:-
241 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
247 you will be left with:-
249 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
255 the filter will be completely removed.
257 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
258 Start a connection process that will culminate in a new connection to the
259 DX cluster <callsign>. This process creates a new 'client' process which will
260 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
261 necessary to traverse the network(s) to logon to the cluster <callsign>.
263 === 9^DELELE/USER <callsign> ...^Delete this user from the User Database
264 This command will completely remove a one or more users from the database.
265 It goes without saying that you should use this command CAREFULLY!
267 === 0^DBAVAIL^Show a list of all the Databases in the system
268 Title says it all really, this command lists all the databases defined
269 in the system. It is also aliased to SHOW/COMMAND.
271 === 9^DBCREATE <name>^Create a database entry
272 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
273 === 9^DBCREATE <name> remote <node>^Create a remote database entry
274 DBCREATE allows you to define a database in the system. It doesn't actually
275 create anything, just defines it.
277 The databases that are created are simple DB_File hash databases, they are
278 therefore already 'indexed'.
280 You can define a local database with the first form of the command eg:
284 You can also chain databases with the addition of the 'chain' keyword.
285 This will search each database one after the other. A typical example
288 DBCREATE sdx_qsl chain sql_ad
290 No checking is done to see if the any of the chained databases exist, in
291 fact it is usually better to do the above staement first then do each of
292 the chained databases.
294 Databases can exist offsite. To define a database that lives on another
297 DBCREATE buckmaster remote gb7dxc
299 Remote databases cannot be chained; however, the last database in a
300 a chain can be a remote database eg:
302 DBCREATE qsl chain gb7dxc
304 To see what databases have been defined do:
306 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
308 It would be normal for you to add an entry into your local Aliases file
309 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
310 need to add a line like:-
315 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
324 to work as they may be used to.
326 See DBIMPORT for the importing of existing AK1A format data to databases.
327 See DBSHOW for generic database enquiry
329 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
330 If you want to import or update data in bulk to a database you can use
331 this command. It will either create or update entries into an existing
332 database. For example:-
334 DBIMPORT oblast /tmp/OBLAST.FUL
336 will import the standard OBLAST database that comes with AK1A into the
337 oblast database held locally.
339 === 9^DBREMOVE <dbname>^Delete a database
340 DBREMOVE will completely remove a database entry and also delete any data
341 file that is associated with it.
343 There is no warning, no comeback, no safety net.
349 will remove the oblast database from the system and it will also remove
350 the associated datafile.
354 There is no warning, no comeback, no safety net.
356 You have been warned.
358 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
359 This is the generic user interface to the database to the database system.
360 It is expected that the sysop will add an entry to the local Aliases file
361 so that users can use the more familiar AK1A style of enquiry such as:
365 but if he hasn't and the database really does exist (use DBAVAIL or
366 SHOW/COMMAND to find out) you can do the same thing with:
370 === 9^DEBUG^Set the cluster program into debug mode
371 Executing this command will only have an effect if you are running the cluster
376 It will interrupt the cluster just after the debug command has finished.
378 === 0^DIRECTORY^List messages
379 === 0^DIRECTORY ALL^List all messages
380 === 0^DIRECTORY OWN^List your own messages
381 === 0^DIRECTORY NEW^List all new messages
382 === 0^DIRECTORY TO <call>^List all messages to <call>
383 === 0^DIRECTORY FROM <call>^List all messages from <call>
384 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
385 === 0^DIRECTORY <nn>^List last <nn> messages
386 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
387 List the messages in the messages directory.
389 If there is a 'p' one space after the message number then it is a
390 personal message. If there is a '-' between the message number and the
391 'p' then this indicates that the message has been read.
393 You can use shell escape characters such as '*' and '?' in the <call>
396 You can combine some of the various directory commands together eg:-
400 DIR SUBJECT IOTA 200-250
402 You can abbreviate all the commands to one letter and use ak1a syntax:-
408 Sysops can see all users' messages.
410 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
411 Disconnect any <call> connected locally
413 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
414 This is how you send a DX Spot to other users. You can, in fact, now
415 enter the <freq> and the <call> either way round.
421 will all give the same result. You can add some remarks to the end
422 of the command and they will be added to the spot.
424 DX FR0G 144600 this is a test
426 You can credit someone else by saying:-
428 DX by G1TLH FR0G 144.600 he isn't on the cluster
430 The <freq> is compared against the available bands set up in the
431 cluster. See SHOW/BANDS for more information.
433 === 9^EXPORT <msgno> <filename>^Export a message to a file
434 Export a message to a file. This command can only be executed on a local
435 console with a fully privileged user. The file produced will be in a form
436 ready to be imported back into the cluster by placing it in the import
437 directory (/spider/msg/import).
439 This command cannot overwrite an existing file. This is to provide some
440 measure of security. Any files written will owned by the same user as the
441 main cluster, otherwise you can put the new files anywhere the cluster can
442 access. For example:-
446 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
447 Export the users database to a file in ascii format. If no filename
448 is given then it will export the file to /spider/data/user_asc.
450 If the file already exists it will be renamed to <filename>.o. In fact
451 up to 5 generations of the file can be kept each one with an extra 'o' on the
454 BE WARNED: this will write to any file you have write access to. No check is
455 made on the filename (if any) that you specify.
457 === 0^FILTERING...^Filtering things in DXSpider
458 There are a number of things you can filter in the DXSpider system. They
459 all use the same general mechanism.
461 In general terms you can create a 'reject' or an 'accept' filter which
462 can have up to 10 lines in it. You do this using, for example:-
467 where ..... are the specific commands for that type of filter. There
468 are filters for spots, wwv, announce, wcy and (for sysops)
469 connects. See each different accept or reject command reference for
472 There is also a command to clear out one or more lines in a filter and
473 one to show you what you have set. They are:-
482 There is clear/xxxx command for each type of filter.
484 For now we are going to use spots for the examples, but you can apply
485 the principles to all types of filter.
487 There are two main types of filter 'accept' or 'reject'; which you use
488 depends entirely on how you look at the world and what is least
489 writing to achieve what you want. Each filter has 10 lines (of any
490 length) which are tried in order. If a line matches then the action
491 you have specified is taken (ie reject means ignore it and accept
494 The important thing to remember is that if you specify a 'reject'
495 filter (all the lines in it say 'reject/spots' (for instance) then if
496 a spot comes in that doesn't match any of the lines then you will get
497 it BUT if you specify an 'accept' filter then any spots that don't
498 match are dumped. For example if I have a one line accept filter:-
500 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
502 then automatically you will ONLY get VHF spots from or to CQ zones 14
503 15 and 16. If you set a reject filter like:
505 reject/spots on hf/cw
507 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
508 and will work it even on CW then you could say:-
510 reject/spots on hf/cw and not info iota
512 But in that case you might only be interested in iota and say:-
514 accept/spots not on hf/cw or info iota
516 which is exactly the same. You should choose one or the other until
517 you are confortable with the way it works. Yes, you can mix them
518 (actually you can have an accept AND a reject on the same line) but
519 don't try this at home until you can analyse the results that you get
520 without ringing up the sysop for help.
522 You can arrange your filter lines into logical units, either for your
523 own understanding or simply convenience. I have one set frequently:-
525 reject/spots 1 on hf/cw
526 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
528 What this does is to ignore all HF CW spots (being a class B I can't
529 read any CW and couldn't possibly be interested in HF :-) and also
530 rejects any spots on VHF which don't either originate or spot someone
533 This is an exmaple where you would use the line number (1 and 2 in
534 this case), if you leave the digit out, the system assumes '1'. Digits
535 '0'-'9' are available.
537 You can leave the word 'and' out if you want, it is implied. You can
538 use any number of brackets to make the 'expression' as you want
539 it. There are things called precedence rules working here which mean
540 that you will NEED brackets in a situation like line 2 because,
541 without it, will assume:-
543 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
545 annoying, but that is the way it is. If you use OR - use
546 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
549 If you want to alter your filter you can just redefine one or more
550 lines of it or clear out one line. For example:-
552 reject/spots 1 on hf/ssb
558 To remove the filter in its entirty:-
564 Once you are happy with the results you get, you may like to experiment.
566 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
567 can be written with a mixed filter, eg:
571 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
573 each filter slot actually has a 'reject' slot and an 'accept'
574 slot. The reject slot is executed BEFORE the accept slot.
576 It was mentioned earlier that after a reject test that doesn't match,
577 the default for following tests is 'accept', the reverse is true for
578 'accept'. In the example what happens is that the reject is executed
579 first, any non hf/cw spot is passed to the accept line, which lets
580 thru everything else on HF.
582 The next filter line lets through just VHF/UHF spots from EU.
584 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
585 This command sends all the latitude and longitude information that your
586 cluster is holding against callsigns. One advantage of recieving this
587 information is that more locator information is held by you. This
588 means that more locators are given on the DX line assuming you have
589 SET/DXGRID enabled. This could be a LOT of information though, so
590 it is not recommended on slow links.
592 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
593 This command sends out any information held in the user file which can
594 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
595 and Homenode. PC41s are only sent for the information that is available.
597 === 0^HELP^The HELP Command
598 HELP is available for a number of commands. The syntax is:-
602 Where <cmd> is the name of the command you want help on.
604 All commands can be abbreviated, so SHOW/DX can be abbreviated
605 to SH/DX, ANNOUNCE can be shortened to AN and so on.
607 Look at the APROPOS <string> command which will search the help database
608 for the <string> you specify and give you a list of likely commands
609 to look at with HELP.
611 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
612 This command attempts to re-initialise a link to a (usually) AK1A node
613 that has got confused, usually by a protocol loop of some kind. It may
614 work - but you usually will be better off simply disconnecting it (or
615 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
618 Best of luck - you will need it.
620 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
621 Delete a message from the local system. You will only be able to
622 delete messages that you have originated or been sent (unless you are
625 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
626 Delete a message (usually a 'bulletin') from the whole cluster system.
628 This uses the subject field, so any messages that have exactly the
629 same subject will be deleted. Beware!
631 === 0^LINKS^Show which nodes is physically connected
632 This is a quick listing that shows which links are connected and
633 some information about them. See WHO for a list of all connections.
635 === 9^LOAD/ALIASES^Reload the command alias table
636 Reload the /spider/cmd/Aliases file after you have editted it. You
637 will need to do this if you change this file whilst the cluster is
638 running in order for the changes to take effect.
640 === 9^LOAD/BANDS^Reload the band limits table
641 Reload the /spider/data/bands.pl file if you have changed it manually whilst
642 the cluster is running.
644 === 9^LOAD/BADMSG^Reload the bad msg table
645 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
646 the cluster is running. This table contains a number of perl regular
647 expressions which are searched for in the fields targetted of each message.
648 If any of them match then that message is immediately deleted on receipt.
650 === 9^LOAD/BADWORDS^Reload the bad words table
651 Reload the /spider/data/badwords file if you have changed it manually whilst
652 the cluster is running. This file contains a list of words which, if found
653 on certain text portions of PC protocol, will cause those protocol frames
654 to be rejected. It will all put out a message if any of these words are
655 used on the announce, dx and talk commands. The words can be one or
656 more on a line, lines starting with '#' are ignored.
658 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
659 Normally, if you change a command file in the cmd or local_cmd tree it
660 will automatially be picked up by the cluster program. Sometimes it
661 can get confused if you are doing a lot of moving commands about or
662 delete a command in the local_cmd tree and want to use the normal one
663 again. Execute this command to reset everything back to the state it
664 was just after a cluster restart.
666 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
667 Reload the /spider/msg/forward.pl file if you have changed it
668 manually whilst the cluster is running.
670 === 9^LOAD/MESSAGES^Reload the system messages file
671 If you change the /spider/perl/Messages file (usually whilst
672 fiddling/writing new commands) you can have them take effect during a
673 cluster session by executing this command. You need to do this if get
676 unknown message 'xxxx' in lang 'en'
678 === 9^LOAD/PREFIXES^Reload the prefix table
679 Reload the /spider/data/prefix_data.pl file if you have changed it
680 manually whilst the cluster is running.
682 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
683 MERGE allows you to bring your spot and wwv database up to date. By default
684 it will request the last 10 spots and 5 WWVs from the node you select. The
685 node must be connected locally.
687 You can request any number of spots or wwv and although they will be appended
688 to your databases they will not duplicate any that have recently been added
689 (the last 2 days for spots and last month for WWV data).
691 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
692 Alter message parameters like To, From, Subject, whether private or bulletin
693 or return receipt (RR) is required or whether to keep this message from timing
696 MSG TO <msgno> <call> - change TO callsign to <call>
697 MSG FRom <msgno> <call> - change FROM callsign to <call>
698 MSG PRrivate <msgno> - set private flag
699 MSG NOPRrivate <msgno> - unset private flag
700 MSG RR <msgno> - set RR flag
701 MSG NORR <msgno> - unset RR flag
702 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
703 MSG NOKEep <msgno> - unset the keep flag
704 MSG SUbject <msgno> <new> - change the subject to <new>
705 MSG WAittime <msgno> - remove any waitting time for this message
706 MSG NOREad <msgno> - mark message as unread
707 MSG REad <msgno> - mark message as read
708 MSG QUeue - queue any outstanding bulletins
709 MSG QUeue 1 - queue any outstanding private messages
711 You can look at the status of a message by using:-
715 This will display more information on the message than DIR does.
717 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
718 Send some arbitrary text to a locally connected callsign. No
719 processing is done on the text. This command allows you to send PC
720 Protocol to unstick things if problems arise (messages get stuck
723 pc gb7djk PC33^GB7TLH^GB7DJK^400^
725 pc G1TLH Try doing that properly!!!
727 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
728 You can get rid of any message to or originating from your callsign using
729 this command. You can remove more than one message at a time.
731 === 5^KILL <from>-<to>^Remove a range of messages from the system
732 === 5^KILL FROM <call>^Remove all messages from a callsign
733 === 5^KILL TO <call>^Remove all messages to a callsign
734 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
735 Remove this message from the entire cluster system as well as your node.
738 As a sysop you can kill any message on the system.
740 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
741 Send any text you like to the callsign requested. This is used mainly to send
742 PC protocol to connected nodes either for testing or to unstick things.
744 You can also use in the same way as a talk command to a connected user but
745 without any processing, added of "from <blah> to <blah" or whatever.
747 === 1^PING <node call>^Check the link quality between nodes
748 This command allows you to send a frame to another cluster node on
749 the network and get a return frame. The time it takes to do this
750 is a good indication of the quality of the link. The actual time
751 it takes is output to the console in seconds.
752 Any visible cluster node can be PINGed.
754 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
755 This command allows you to send nearly any command to another DX Cluster
756 node that is connected to the system.
758 Whether you get any output is dependant on a) whether the other system knows
759 that the node callsign of this cluster is in fact a node b) whether the
760 other system is allowing RCMDs from this node and c) whether you have
761 permission to send this command at all.
763 === 0^READ^Read the next unread personal message addressed to you
764 === 0^READ <msgno>^Read the specified message
765 You can read any messages that are sent as 'non-personal' and also any
766 message either sent by or sent to your callsign.
769 As a sysop you may read any message on the system
771 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
772 Create an 'reject this announce' line for a filter.
774 A reject filter line means that if the announce matches this filter it is
775 passed onto the user. See HELP FILTERING for more info. Please read this
776 to understand how filters work - it will save a lot of grief later on.
778 You can use any of the following things in this line:-
780 info <string> eg: iota or qsl
781 by <prefixes> eg: G,M,2
783 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
785 origin_zone <numbers>
790 wx 1 filter WX announces
791 dest <prefixes> eg: 6MUK,WDX (distros)
795 rej/ann by_zone 14,15,16 and not by G,M,2
797 You can use the tag 'all' to reject everything eg:
801 but this probably for advanced users...
803 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
804 This version allows a sysop to set a filter for a callsign as well as the
805 default for nodes and users eg:-
808 reject/ann input node_default by G,M,2
809 reject/ann user_default by G,M,2
811 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
812 Create a 'reject this spot' line for a filter.
814 A reject filter line means that if the spot matches this filter it is
815 dumped (not passed on). See HELP FILTERING for more info. Please read this
816 to understand how filters work - it will save a lot of grief later on.
818 You can use any of the following things in this line:-
820 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
821 on <range> same as 'freq'
822 call <prefixes> eg: G,PA,HB9
823 info <string> eg: iota or qsl
825 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
834 For frequencies, you can use any of the band names defined in
835 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
836 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
837 this is more efficient than saying simply: on HF (but don't get
838 too hung up about that)
843 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
845 You can use the tag 'all' to reject everything eg:
849 but this probably for advanced users...
851 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
852 Create an 'reject this routing PC Protocol' line for a filter.
854 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
855 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
856 read this to understand how filters work - it will save a lot of grief later on.
858 You can use any of the following things in this line:-
860 call <prefixes> the callsign of the thingy
861 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
864 origin <prefixes> really the interface it came in on
865 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
867 origin_zone <numbers>
871 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
873 You can use the tag 'all' to reject everything eg:
875 rej/route all (equiv to [very] restricted mode)
877 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
878 This version allows a sysop to set a filter for a callsign as well as the
879 default for nodes and users eg:-
881 reject/spot db0sue-7 1 by_zone 14,15,16
882 reject/spot node_default all
883 set/hops node_default 10
885 reject/spot user_default by G,M,2
887 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
888 It is unlikely that you will want to do this, but if you do then you can
889 filter on the following fields:-
891 by <prefixes> eg: G,M,2
893 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
895 origin_zone <numbers>
901 There are no examples because WCY Broadcasts only come from one place and
902 you either want them or not (see UNSET/WCY if you don't want them).
904 This command is really provided for future use.
906 See HELP FILTER for information.
908 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
909 This version allows a sysop to set a filter for a callsign as well as the
910 default for nodes and users eg:-
912 reject/wcy gb7djk all
914 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
915 It is unlikely that you will want to do this, but if you do then you can
916 filter on the following fields:-
918 by <prefixes> eg: G,M,2
920 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
922 origin_zone <numbers>
930 reject/wwv by_zone 14,15,16
932 is probably the only useful thing to do (which will only show WWV broadcasts
933 by stations in the US).
935 See HELP FILTER for information.
937 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
938 This version allows a sysop to set a filter for a callsign as well as the
939 default for nodes and users eg:-
941 reject/wwv db0sue-7 1 by_zone 4
942 reject/wwv node_default all
944 reject/wwv user_default by W
946 === 0^REPLY^Reply (privately) to the last message that you have read
947 === 0^REPLY <msgno>^Reply (privately) to the specified message
948 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
949 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
950 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
951 You can reply to a message and the subject will automatically have
952 "Re:" inserted in front of it, if it isn't already present.
954 You can also use all the extra qualifiers such as RR, PRIVATE,
955 NOPRIVATE, B that you can use with the SEND command (see SEND
958 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
959 === 0^SEND RR <call>^Send a message and ask for a read receipt
960 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
961 === 0^SEND PRIVATE <call>^Send a personal message
962 === 0^SEND NOPRIVATE <call>^Send a message to all stations
963 All the SEND commands will create a message which will be sent either to
964 an individual callsign or to one of the 'bulletin' addresses.
966 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
967 it will mark the message as personal and send it to the cluster node that
968 that callsign is connected to.
970 You can have more than one callsign in all of the SEND commands.
972 You can have multiple qualifiers so that you can have for example:-
974 SEND RR COPY 123 PRIVATE G1TLH G0RDI
976 which should send a copy of message 123 to G1TLH and G0RDI and you will
977 receive a read receipt when they have read the message.
979 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
980 SP is an alias for SEND PRIVATE
982 === 0^SET/ADDRESS <your address>^Record your postal address
984 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
985 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
987 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
989 === 8^SET/BADDX <call>..^Stop words we do not wish to see in the callsign field
990 of a dx spot being propagated
991 === 8^UNSET/BADDX <call>..^Allow a word to be seen again in a DX spot
992 Setting a word as 'baddx' will prevent spots with that word in the
993 callsign field of a DX spot from going any further. They will not be
994 displayed and they will not be sent onto other nodes.
996 The word must be wriiten in full, no wild cards are allowed eg:-
998 set/baddx FORSALE VIDEO FR0G
1000 To allow a word again, use the following command ...
1004 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1005 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1006 Setting a callsign as a 'badnode' will prevent spots from that node
1007 going any further. They will not be displayed and they will not be
1008 sent onto other nodes.
1010 The call must be a full eg:-
1014 will stop anything from K1TTT. If you want SSIDs as well then you must
1015 enter them specifically.
1019 will allow spots from him again.
1021 Use with extreme care. This command may well be superceeded by FILTERing.
1023 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1024 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1025 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1026 going any further. They will not be displayed and they will not be
1027 sent onto other nodes.
1029 The call must be written in full, no wild cards are allowed eg:-
1031 set/badspotter VE2STN
1033 will stop anything from VE2STN. If you want SSIDs as well then you must
1034 enter them specifically.
1036 unset/badspotter VE2STN
1038 will allow spots from him again.
1040 Use with extreme care. This command may well be superceded by FILTERing.
1042 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1043 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1045 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1047 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1049 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1050 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1051 You can choose to log several different levels. The levels are
1059 You can show what levels you are logging with SHOW/DEBUG
1061 === 0^SET/DX^Allow DX messages to come out on your terminal
1062 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1064 === 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements
1065 === 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements
1066 A standard feature which is enabled in version 1.43 and above is
1067 that if the spotter's grid square is known it is output on the end
1068 of a DX announcement (there is just enough room). Some user programs
1069 cannot cope with this. You can use this command to reset (or set)
1072 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1074 === 0^SET/ECHO^Make the cluster echo your input
1075 === 0^UNSET/ECHO^Stop the cluster echoing your input
1076 If you are connected via a telnet session, different implimentations
1077 of telnet handle echo differently depending on whether you are
1078 connected via port 23 or some other port. You can use this command
1079 to change the setting appropriately.
1081 The setting is stored in your user profile.
1083 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1085 === 0^SET/HERE^Tell the system you are present at your terminal
1086 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1088 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1089 Tell the cluster system where you normally connect to. Any Messages sent
1090 to you will normally find their way there should you not be connected.
1094 === 8^SET/HOPS <call> ann|spots|wwv|wcy <n>^Set hop count
1095 Set the hop count for a particular type of broadcast for a node.
1097 This command allows you to set up special hop counts for a node
1098 for currently: announce, spots, wwv and wcy broadcasts.
1101 set/hops gb7djk ann 10
1102 set/hops gb7mbc spots 20
1104 Set SHOW/HOPS for information on what is already set. This command
1105 creates a filter and works in conjunction with the filter system.
1107 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1108 Connect a node to your system in such a way that you are a full protocol
1109 member of its network and can see all spots on it, but nothing either leaks
1110 out from it nor goes back into from the rest of the nodes connected to you.
1112 You can potentially connect several nodes in this way.
1114 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1115 Remove isolation from a node - SET/ISOLATE
1117 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1118 You can select the language that you want the cluster to use. Currently
1119 the languages available are en (english) and nl (dutch).
1121 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1122 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1123 In order to get accurate headings and such like you must tell the system
1124 what your latitude and longitude is. If you have not yet done a SET/QRA
1125 then this command will set your QRA locator for you. For example:-
1126 SET/LOCATION 52 22 N 0 57 E
1128 === 0^SET/LOGININFO^Inform when a station logs in locally
1129 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1131 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1132 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1134 === 0^SET/NAME <your name>^Set your name
1135 Tell the system what your name is eg:-
1138 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1139 Tell the system that the call(s) are to be treated as AK1A cluster and
1140 fed PC Protocol rather normal user commands.
1142 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
1143 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1144 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1145 counter which is decremented on every outgoing ping and then reset to
1146 the 'obscount' value on every incoming ping. The default value of this
1149 What this means is that a neighbouring node will be pinged twice at
1150 (default) 300 second intervals and if no reply has been heard just before
1151 what would be the third attempt, that node is disconnected.
1153 If a ping is heard then the obscount is reset to the full value. Using
1154 default values, if a node has not responded to a ping within 15 minutes,
1157 You can set this parameter between 1 and 9.
1159 It is STRONGLY recommended that you don't change the default.
1161 === 0^SET/PAGE <lines per page>^Set the lines per page
1162 Tell the system how many lines you wish on a page when the number of line
1163 of output from a command is more than this. The default is 20. Setting it
1164 explicitly to 0 will disable paging.
1168 The setting is stored in your user profile.
1170 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1171 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1172 in order to determine the rolling quality of the link and, in future, to
1173 affect routing decisions. The default interval is 300 secs or 5 minutes.
1175 You can use this command to set a different interval. Please don't.
1177 But if you do the value you enter is treated as minutes up 30 and seconds
1178 for numbers greater than that.
1180 This is used also to help determine when a link is down at the far end
1181 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1182 for more information.
1184 If you must change it (and it may be useful for internet connected nodes
1185 on dynamic IP addresses that go away after a set time of usage) the time
1186 can be specified as:-
1188 5 which if less than 30 is converted to minutes otherwise is
1189 taken as the no of seconds between pings.
1194 Please be aware that this causes traffic to occur on the link, setting
1195 this value too low may annoy your neighbours beyond the point of
1198 You can switch this off by setting it to 0.
1200 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1201 Set the privilege level on a callsign. The privilege levels that pertain
1202 to commands are as default:-
1204 1 - allow remote nodes normal user RCMDs
1205 5 - various privileged commands (including shutdown, but not disc-
1206 connect), the normal level for another node.
1207 8 - more privileged commands (including disconnect)
1208 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1210 If you are a sysop and you come in as a normal user on a remote connection
1211 your privilege will automatically be set to 0.
1213 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1214 You can use this command to 'protect' this session from unauthorised
1215 use. If you want to get your normal privilege back you will need to
1216 either logout and login again (if you are on a console) or use the
1219 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1220 The password for a user can only be set by a full sysop. The string
1221 can contain any characters but any spaces are removed (you can type in
1222 spaces - but they won't appear in the password). You can see the
1223 result with STAT/USER.
1225 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1226 Tell the system that the call(s) are to be treated as DXSpider node and
1227 fed new style DX Protocol rather normal user commands.
1229 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
1230 === 0^SET/QRA <locator>^Set your QRA locator
1231 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1232 done a SET/LOCATION then your latitude and longitude will be set roughly
1233 correctly (assuming your locator is correct ;-). For example:-
1236 === 0^SET/QTH <your qth>^Set your QTH
1237 Tell the system where you are. For example:-
1238 SET/QTH East Dereham, Norfolk
1240 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1241 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1243 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1244 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1246 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1247 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1249 === 0^SET/WX^Allow WX messages to come out on your terminal
1250 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1252 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1253 Display all the bad dx callsigns in the system, see SET/BADDX
1254 for more information.
1256 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1257 Display all the bad node callsigns in the system, see SET/BADNODE
1258 for more information.
1260 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1261 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1262 for more information.
1264 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1265 This command allows you to see all the users that can be seen
1266 and the nodes to which they are connected.
1268 This command is normally abbreviated to: sh/c
1270 BE WARNED: the list that is returned can be VERY long
1272 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1273 Show all the nodes connected to this node.
1275 === 1^SHOW/CONNECT^Show all the active connections
1276 This command shows information on all the active connections known to
1277 the node. This command gives slightly more information than WHO.
1279 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1280 This is very nearly the same as SHOW/TIME, the only difference the format
1281 of the date string if no arguments are given.
1283 If no prefixes or callsigns are given then this command returns the local
1284 time and UTC as the computer has it right now. If you give some prefixes
1285 then it will show UTC and UTC + the local offset (not including DST) at
1286 the prefixes or callsigns that you specify.
1288 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1290 === 0^SHOW/DX^Interrogate the spot database
1291 If you just type SHOW/DX you will get the last so many spots
1292 (sysop configurable, but usually 10).
1294 In addition you can add any number of these commands in very nearly
1295 any order to the basic SHOW/DX command, they are:-
1297 on <band> - eg 160m 20m 2m 23cm 6mm
1298 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1300 <number> - the number of spots you want
1301 <from>-<to> - <from> spot no <to> spot no in the selected list
1303 <prefix> - for a spotted callsign beginning with <prefix>
1304 *<suffix> - for a spotted callsign ending in <suffix>
1305 *<string>* - for a spotted callsign containing <string>
1307 day <number> - starting <number> days ago
1308 day <from>-<to> - <from> days <to> days ago
1310 info <text> - any spots containing <text> in the info or remarks
1312 by <call> - any spots spotted by <call> (spotter <call> is the
1315 qsl - this automatically looks for any qsl info on the call
1316 held in the spot database.
1318 iota [<iota>] - If the iota island number is missing it will look for
1319 the string iota and anything which looks like an iota
1320 island number. If you specify then it will look for
1323 qra [<locator>] - this will look for the specific locator if you specify
1324 one or else anything that looks like a locator.
1329 SH/DX on 20m info iota
1330 SH/DX 9a on vhf day 30
1336 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1337 This command takes the <prefix> (which can be a full or partial
1338 callsign if desired), looks up which internal country number it is
1339 and then displays all the spots as per SH/DX for that country.
1341 The options for SHOW/DX also apply to this command.
1345 SH/DXCC W on 20m info iota
1347 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1348 SHOW/FILES on its own will show you a list of the various fileareas
1349 available on the system. To see the contents of a particular file
1352 where <filearea> is the name of the filearea you want to see the
1355 You can also use shell globbing characters like '*' and '?' in a
1356 string to see a selection of files in a filearea eg:-
1357 SH/FILES bulletins arld*
1359 See also TYPE - to see the contents of a file.
1361 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1362 Show the contents of all the filters that are set. This command displays
1363 all the filters set - for all the various categories.
1365 === 8^SHOW/HOPS <call> [ann|spots|wcy|wwv]^Show the hop counts for a node
1366 This command shows the hop counts set up for a node. You can specify
1367 which category you want to see. If you leave the category out then
1368 all the categories will be listed.
1370 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1372 === 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
1374 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
1375 This command outputs a short section of the system log. On its own
1376 it will output a general logfile. With the optional callsign it will
1377 show output from the log associated with that callsign.
1379 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
1380 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1381 together with the azimuth and elevation of the sun currently at those
1384 If you don't specify any prefixes or callsigns, it will show the times for
1385 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1386 together with the current azimuth and elevation.
1388 In addition, it will show the gain or loss dB relative to the nominal
1389 distance of 385,000Km due to the ellipsoidal nature of the orbit.
1391 If all else fails it will show the Moonrise and set times for the node
1392 that you are connected to.
1399 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1400 This command allow you to estimate the likelihood of you contacting
1401 a station with the prefix you have specified. The output assumes a modest
1402 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1404 The result predicts the most likely operating frequencies and signal
1405 levels for high frequency (shortwave) radio propagation paths on
1406 specified days of the year and hours of the day. It is most useful for
1407 paths between 250 km and 6000 km, but can be used with reduced accuracy
1408 for paths shorter or longer than this.
1410 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1411 used to predict the MUF given the predicted flux, day of the year,
1412 hour of the day and geographic coordinates of the transmitter and
1413 receiver. This routine is reasonably accurate for the purposes here,
1414 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1415 than the programs used by major shortwave broadcasting organizations,
1416 such as the Voice of America.
1418 The command will display some header information detailing its
1419 assumptions, together with the locations, latitude and longitudes and
1420 bearings. It will then show UTC (UT), local time at the other end
1421 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1422 (Zen) and the likely signal strengths. Then for each frequency for which
1423 the system thinks there is a likelihood of a circuit it prints a value.
1425 The value is currently a likely S meter reading based on the conventional
1426 6dB / S point scale. If the value has a '+' appended it means that it is
1427 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1428 there is likely to be much fading and by an 's' that the signal is likely
1431 By default SHOW/MUF will show the next two hours worth of data. You
1432 can specify anything up to 24 hours worth of data by appending the no of
1433 hours required after the prefix. For example:-
1439 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1440 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1441 Location Lat / Long Azim
1442 East Dereham, Norfolk 52 41 N 0 57 E 47
1443 United-States-W 43 0 N 87 54 W 299
1444 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1445 18 23 11.5 -35 mS0+ mS2 S3
1446 19 0 11.2 -41 mS0+ mS2 S3
1448 indicating that you will have weak, fading circuits on top band and
1449 80m but usable signals on 40m (about S3).
1455 will get you the above display, but with the next 24 hours worth of
1461 Gives you an estimate of the long path propagation characterics. It
1462 should be noted that the figures will probably not be very useful, nor
1463 terrible accurate, but it is included for completeness.
1465 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1466 Show the type and version (if connected) of the nodes specified on the
1467 command line. If no callsigns are specified then a sorted list of all
1468 the non-user callsigns known to the system will be displayed.
1470 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1471 This command takes the <callsign> (which can be a full or partial
1472 callsign or a prefix), looks up which internal country number
1473 it is and then displays all the relevant prefixes for that country
1474 together with the internal country no, the CQ and ITU regions.
1478 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1479 Show the name and location where every program module was load from. This
1480 is useful for checking where you think you have loaded a .pm file from.
1482 === 0^SHOW/QRA <locator> [<locator>]^Show distance between locators
1483 === 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
1484 This is a multipurpose command that allows you either to calculate the
1485 distance and bearing between two locators or (if only one locator is
1486 given on the command line) the distance and beraing from your station
1487 to the locator. For example:-
1492 The first example will show the distance and bearing to the locator from
1493 yourself, the second example will calculate the distance and bearing from
1494 the first locator to the second. You can use 4 or 6 character locators.
1496 It is also possible to convert a latitude and longitude to a locator by
1497 using this command with a latitude and longitude as an argument, for
1500 SH/QRA 52 41 N 0 58 E
1502 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
1503 This command queries the QRZ callbook server on the internet
1504 and returns any information available for that callsign. This service
1505 is provided for users of this software by http://www.qrz.com
1507 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
1508 This command allows you to see to which node the callsigns specified are
1509 connected. It is a sort of inverse sh/config.
1513 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1514 Show the tracking data from your location to the satellite of your choice
1515 from now on for the next few hours.
1517 If you use this command without a satellite name it will display a list
1518 of all the satellites known currently to the system.
1520 If you give a name then you can obtain tracking data of all the passes
1521 that start and finish 5 degrees below the horizon. As default it will
1522 give information for the next three hours for every five minute period.
1524 You can alter the number of hours and the step size, within certain
1527 Each pass in a period is separated with a row of '-----' characters
1532 SH/SAT FENGYUN1 12 2
1534 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
1535 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
1536 Show the information known about a callsign and whether (and where)
1537 that callsign is connected to the cluster.
1541 If no callsign is given then show the information for yourself.
1543 === 0^SHOW/SUN [<prefix>|<callsign>]^Show sun rise and set times
1544 Show the sun rise and set times for a (list of) prefixes or callsigns,
1545 together with the azimuth and elevation of the sun currently at those
1548 If you don't specify any prefixes or callsigns, it will show the times for
1549 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1550 together with the current azimuth and elevation.
1552 If all else fails it will show the sunrise and set times for the node
1553 that you are connected to.
1558 SH/SUN G1TLH K9CW ZS
1560 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
1561 If no prefixes or callsigns are given then this command returns the local
1562 time and UTC as the computer has it right now. If you give some prefixes
1563 then it will show UTC and UTC + the local offset (not including DST) at
1564 the prefixes or callsigns that you specify.
1566 === 0^SHOW/WCY^Show last 10 WCY broadcasts
1567 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
1568 Display the most recent WCY information that has been received by the system
1570 === 0^SHOW/WWV^Show last 10 WWV broadcasts
1571 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
1572 Display the most recent WWV information that has been received by the system
1574 === 5^SHUTDOWN^Shutdown the cluster
1575 Shutdown the cluster and disconnect all the users
1577 === 9^SPOOF <call> <command>^Do a command as though you are another user
1578 This command is provided so that sysops can set a user's parameters without
1579 me having to write a special 'sysop' version for every user command. It
1580 allows you to pretend that you are doing the command as the user you specify.
1584 SPOOF G1TLH set/name Dirk
1585 SPOOF G1TLH set/qra JO02LQ
1587 === 5^STAT/DB <dbname>^Show the status of a database
1588 Show the internal status of a database descriptor.
1590 Depending on your privilege level you will see more or less information.
1591 This command is unlikely to be of much use to anyone other than a sysop.
1593 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
1594 Show the internal status of the channel object either for the channel that
1595 you are on or else for the callsign that you asked for.
1597 Only the fields that are defined (in perl term) will be displayed.
1599 === 1^STAT/MSG^Show the status of the message system
1600 === 1^STAT/MSG <msgno>^Show the status of a message
1601 This command shows the internal status of a message and includes information
1602 such as to whom it has been forwarded, its size, origin etc etc.
1604 If no message number is given then the status of the message system is
1607 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
1608 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
1610 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
1611 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
1613 === 5^STAT/USER [<callsign>]^Show the full status of a user
1614 Shows the full contents of a user record including all the secret flags
1617 Only the fields that are defined (in perl term) will be displayed.
1619 === 0^SYSOP^Regain your privileges if you login remotely
1620 The system automatically reduces your privilege level to that of a
1621 normal user if you login in remotely. This command allows you to
1622 regain your normal privilege level. It uses the normal system: five
1623 numbers are returned that are indexes into the character array that is
1624 your assigned password (see SET/PASSWORD). The indexes start from
1627 You are expected to return a string which contains the characters
1628 required in the correct order. You may intersperse those characters
1629 with others to obscure your reply for any watchers. For example (and
1630 these values are for explanation :-):
1632 password = 012345678901234567890123456789
1636 aa2bbbb0ccc5ddd7xxx3n
1640 They will all match. If there is no password you will still be offered
1641 numbers but nothing will happen when you input a string. Any match is
1644 === 0^TALK <call> [<text>]^Send a text message to another station
1645 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
1646 Send a short message to any other station that is visible on the cluster
1647 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
1648 command, they don't have to be connected locally.
1650 The second form of TALK is used when other cluster nodes are connected
1651 with restricted information. This usually means that they don't send
1652 the user information usually associated with logging on and off the cluster.
1654 If you know that G3JNB is likely to be present on GB7TLH, but you can only
1655 see GB7TLH in the SH/C list but with no users, then you would use the
1656 second form of the talk message.
1658 If you want to have a ragchew with someone you can leave the text message
1659 out and the system will go into 'Talk' mode. What this means is that a
1660 short message is sent to the recipient telling them that you are in a
1661 'Talking' frame of mind and then you just type - everything you send will
1662 go to the station that you asked for.
1664 All the usual announcements, spots and so on will still come out on your
1667 If you want to do something (such as send a spot) you preceed the normal
1668 command with a '/' character, eg:-
1670 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
1673 To leave talk mode type:
1677 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
1678 Type out the contents of a file in a filearea. So, for example, in
1679 filearea 'bulletins' you want to look at file 'arld051' you would
1681 TYPE bulletins/arld051
1683 See also SHOW/FILES to see what fileareas are available and a
1686 === 0^WHO^Show who is physically connected
1687 This is a quick listing that shows which callsigns are connected and
1688 what sort of connection they have
1690 === 0^WX <text>^Send a weather message to local users
1691 === 0^WX FULL <text>^Send a weather message to all cluster users
1692 === 5^WX SYSOP <text>^Send a weather message to other clusters only
1693 Weather messages can sometimes be useful if you are experiencing an extreme
1694 that may indicate enhanced conditions