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 FILTERS 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 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
59 Create an 'accept this spot' line for a filter.
61 An accept filter line means that if the spot matches this filter it is
62 passed onto the user. See HELP FILTERS 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 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
68 on <range> same as 'freq'
69 call <prefixes> eg: G,PA,HB9
70 info <string> eg: iota or qsl
72 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
81 For frequencies, you can use any of the band names defined in
82 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
83 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
84 this is more efficient than saying simply: freq HF (but don't get
85 too hung up about that)
90 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
92 You can use the tag 'all' to accept everything, eg:
96 but this probably for advanced users...
98 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
99 This version allows a sysop to set a filter for a callsign as well as the
100 default for nodes and users eg:-
102 accept/spot db0sue-7 1 by_zone 14,15,16
103 accept/spot node_default all
104 set/hops node_default 10
106 accept/spot user_default by G,M,2
108 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
109 It is unlikely that you will want to do this, but if you do then you can
110 filter on the following fields:-
112 by <prefixes> eg: G,M,2
114 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
116 origin_zone <numbers>
122 There are no examples because WCY Broadcasts only come from one place and
123 you either want them or not (see UNSET/WCY if you don't want them).
125 This command is really provided for future use.
127 See HELP FILTER for information.
129 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
130 This version allows a sysop to set a filter for a callsign as well as the
131 default for nodes and users eg:-
133 accept/wcy node_default all
134 set/hops node_default 10
136 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
137 It is unlikely that you will want to do this, but if you do then you can
138 filter on the following fields:-
140 by <prefixes> eg: G,M,2
142 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
144 origin_zone <numbers>
154 is probably the only useful thing to do (which will only show WWV broadcasts
155 by stations in the US).
157 See HELP FILTER for information.
159 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
160 This version allows a sysop to set a filter for a callsign as well as the
161 default for nodes and users eg:-
163 accept/wwv db0sue-7 1 by_zone 4
164 accept/wwv node_default all
165 set/hops node_default 10
167 accept/wwv user_default by W,K
169 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
170 <text> is the text of the announcement you wish to broadcast
172 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
173 This will send your announcement cluster wide
175 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
177 === 0^APROPOS <string>^Search help database for <string>
178 Search the help database for <string> (it isn't case sensitive), and print
179 the names of all the commands that may be relevant.
181 === 0^BYE^Exit from the cluster
182 This will disconnect you from the cluster
184 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
185 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
186 When you send messages the fact that you have forwarded it to another node
187 is remembered so that it isn't sent again. When you have a new partner
188 node and you add their callsign to your /spider/msg/forward.pl file, all
189 outstanding non-private messages will be forwarded to them. This may well
190 be ALL the non-private messages. You can prevent this by using these
194 catchup GB7DJK 300 301 302 303 500-510
196 and to undo what you have just done:-
199 uncatchup GB7DJK 300 301 302 303 500-510
201 which will arrange for them to be forward candidates again.
203 Order is not important.
205 === 0^CLEAR/SPOTS [1|all]^Clear a spot filter line
206 This command allows you to clear (remove) a line in a spot filter or to
207 remove the whole filter.
209 If you have a filter:-
212 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
218 you will be left with:-
220 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
226 the filter will be completely removed.
228 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
229 Start a connection process that will culminate in a new connection to the
230 DX cluster <callsign>. This process creates a new 'client' process which will
231 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
232 necessary to traverse the network(s) to logon to the cluster <callsign>.
234 === 0^DBAVAIL^Show a list of all the Databases in the system
235 Title says it all really, this command lists all the databases defined
236 in the system. It is also aliased to SHOW/COMMAND.
238 === 9^DBCREATE <name>^Create a database entry
239 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
240 === 9^DBCREATE <name> remote <node>^Create a remote database entry
241 DBCREATE allows you to define a database in the system. It doesn't actually
242 create anything, just defines it.
244 The databases that are created are simple DB_File hash databases, they are
245 therefore already 'indexed'.
247 You can define a local database with the first form of the command eg:
251 You can also chain databases with the addition of the 'chain' keyword.
252 This will search each database one after the other. A typical example
255 DBCREATE sdx_qsl chain sql_ad
257 No checking is done to see if the any of the chained databases exist, in
258 fact it is usually better to do the above staement first then do each of
259 the chained databases.
261 Databases can exist offsite. To define a database that lives on another
264 DBCREATE buckmaster remote gb7dxc
266 Remote databases cannot be chained; however, the last database in a
267 a chain can be a remote database eg:
269 DBCREATE qsl chain gb7dxc
271 To see what databases have been defined do:
273 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
275 It would be normal for you to add an entry into your local Aliases file
276 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
277 need to add a line like:-
282 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
291 to work as they may be used to.
293 See DBIMPORT for the importing of existing AK1A format data to databases.
294 See DBSHOW for generic database enquiry
296 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
297 If you want to import or update data in bulk to a database you can use
298 this command. It will either create or update entries into an existing
299 database. For example:-
301 DBIMPORT oblast /tmp/OBLAST.FUL
303 will import the standard OBLAST database that comes with AK1A into the
304 oblast database held locally.
306 === 9^DBREMOVE <dbname>^Delete a database
307 DBREMOVE will completely remove a database entry and also delete any data
308 file that is associated with it.
310 There is no warning, no comeback, no safety net.
316 will remove the oblast database from the system and it will also remove
317 the associated datafile.
321 There is no warning, no comeback, no safety net.
323 You have been warned.
325 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
326 This is the generic user interface to the database to the database system.
327 It is expected that the sysop will add an entry to the local Aliases file
328 so that users can use the more familiar AK1A style of enquiry such as:
332 but if he hasn't and the database really does exist (use DBAVAIL or
333 SHOW/COMMAND to find out) you can do the same thing with:
337 === 9^DEBUG^Set the cluster program into debug mode
338 Executing this command will only have an effect if you are running the cluster
343 It will interrupt the cluster just after the debug command has finished.
344 === 0^DIRECTORY^List messages
345 === 0^DIRECTORY ALL^List all messages
346 === 0^DIRECTORY OWN^List your own messages
347 === 0^DIRECTORY NEW^List all new messages
348 === 0^DIRECTORY TO <call>^List all messages to <call>
349 === 0^DIRECTORY FROM <call>^List all messages from <call>
350 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
351 === 0^DIRECTORY <nn>^List last <nn> messages
352 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
353 List the messages in the messages directory.
355 If there is a 'p' one space after the message number then it is a
356 personal message. If there is a '-' between the message number and the
357 'p' then this indicates that the message has been read.
359 You can use shell escape characters such as '*' and '?' in the <call>
362 You can combine some of the various directory commands together eg:-
366 DIR SUBJECT IOTA 200-250
368 You can abbreviate all the commands to one letter and use ak1a syntax:-
374 Sysops can see all users' messages.
376 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
377 Disconnect any <call> connected locally
379 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
380 This is how you send a DX Spot to other users. You can, in fact, now
381 enter the <freq> and the <call> either way round.
387 will all give the same result. You can add some remarks to the end
388 of the command and they will be added to the spot.
390 DX FR0G 144600 this is a test
392 You can credit someone else by saying:-
394 DX by G1TLH FR0G 144.600 he isn't on the cluster
396 The <freq> is compared against the available bands set up in the
397 cluster. See SHOW/BANDS for more information.
399 === 9^EXPORT <msgno> <filename>^Export a message to a file
400 Export a message to a file. This command can only be executed on a local
401 console with a fully privileged user. The file produced will be in a form
402 ready to be imported back into the cluster by placing it in the import
403 directory (/spider/msg/import).
405 This command cannot overwrite an existing file. This is to provide some
406 measure of security. Any files written will owned by the same user as the
407 main cluster, otherwise you can put the new files anywhere the cluster can
408 access. For example:-
412 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
413 Export the users database to a file in ascii format. If no filename
414 is given then it will export the file to /spider/data/user_asc.
416 If the file already exists it will be renamed to <filename>.o. In fact
417 up to 5 generations of the file can be kept each one with an extra 'o' on the
420 BE WARNED: this will write to any file you have write access to. No check is
421 made on the filename (if any) that you specify.
423 === 0^FILTERING...^Filtering things in DXSpider
424 There are a number of things you can filter in the DXSpider system. They
425 all use the same general mechanism.
427 In general terms you can create a 'reject' or an 'accept' filter which
428 can have up to 10 lines in it. You do this using, for example:-
433 where ..... are the specific commands for that type of filter. There
434 are filters for spots, wwv, announce, wcy and (for sysops)
435 connects. See each different accept or reject command reference for
438 There is also a command to clear out one or more lines in a filter and
439 one to show you what you have set. They are:-
448 There is clear/xxxx command for each type of filter.
450 For now we are going to use spots for the examples, but you can apply
451 the principles to all types of filter.
453 There are two main types of filter 'accept' or 'reject'; which you use
454 depends entirely on how you look at the world and what is least
455 writing to achieve what you want. Each filter has 10 lines (of any
456 length) which are tried in order. If a line matches then the action
457 you have specified is taken (ie reject means ignore it and accept
460 The important thing to remember is that if you specify a 'reject'
461 filter (all the lines in it say 'reject/spots' (for instance) then if
462 a spot comes in that doesn't match any of the lines then you will get
463 it BUT if you specify an 'accept' filter then any spots that don't
464 match are dumped. For example if I have a one line accept filter:-
466 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
468 then automatically you will ONLY get VHF spots from or to CQ zones 14
469 15 and 16. If you set a reject filter like:
471 reject/spots on hf/cw
473 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
474 and will work it even on CW then you could say:-
476 reject/spots on hf/cw and not info iota
478 But in that case you might only be interested in iota and say:-
480 accept/spots not on hf/cw or info iota
482 which is exactly the same. You should choose one or the other until
483 you are confortable with the way it works. Yes, you can mix them
484 (actually you can have an accept AND a reject on the same line) but
485 don't try this at home until you can analyse the results that you get
486 without ringing up the sysop for help.
488 You can arrange your filter lines into logical units, either for your
489 own understanding or simply convenience. I have one set frequently:-
491 reject/spots 1 on hf/cw
492 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
494 What this does is to ignore all HF CW spots (being a class B I can't
495 read any CW and couldn't possibly be interested in HF :-) and also
496 rejects any spots on VHF which don't either originate or spot someone
499 This is an exmaple where you would use the line number (1 and 2 in
500 this case), if you leave the digit out, the system assumes '1'. Digits
501 '0'-'9' are available.
503 You can leave the word 'and' out if you want, it is implied. You can
504 use any number of brackets to make the 'expression' as you want
505 it. There are things called precedence rules working here which mean
506 that you will NEED brackets in a situation like line 2 because,
507 without it, will assume:-
509 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
511 annoying, but that is the way it is. If you use OR - use
512 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
515 If you want to alter your filter you can just redefine one or more
516 lines of it or clear out one line. For example:-
518 reject/spots 1 on hf/ssb
524 To remove the filter in its entirty:-
530 Once you are happy with the results you get, you may like to experiment.
532 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
533 can be written with a mixed filter, eg:
537 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
539 each filter slot actually has a 'reject' slot and an 'accept'
540 slot. The reject slot is executed BEFORE the accept slot.
542 It was mentioned earlier that after a reject test that doesn't match,
543 the default for following tests is 'accept', the reverse is true for
544 'accept'. In the example what happens is that the reject is executed
545 first, any non hf/cw spot is passed to the accept line, which lets
546 thru everything else on HF.
548 The next filter line lets through just VHF/UHF spots from EU.
550 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
551 This command sends all the latitude and longitude information that your
552 cluster is holding against callsigns. One advantage of recieving this
553 information is that more locator information is held by you. This
554 means that more locators are given on the DX line assuming you have
555 SET/DXGRID enabled. This could be a LOT of information though, so
556 it is not recommended on slow links.
558 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
559 This command sends out any information held in the user file which can
560 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
561 and Homenode. PC41s are only sent for the information that is available.
563 === 0^HELP^The HELP Command
564 HELP is available for a number of commands. The syntax is:-
568 Where <cmd> is the name of the command you want help on.
570 All commands can be abbreviated, so SHOW/DX can be abbreviated
571 to SH/DX, ANNOUNCE can be shortened to AN and so on.
573 Look at the APROPOS <string> command which will search the help database
574 for the <string> you specify and give you a list of likely commands
575 to look at with HELP.
577 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
578 This command attempts to re-initialise a link to a (usually) AK1A node
579 that has got confused, usually by a protocol loop of some kind. It may
580 work - but you usually will be better off simply disconnecting it (or
581 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
584 Best of luck - you will need it.
586 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
587 Delete a message from the local system. You will only be able to
588 delete messages that you have originated or been sent (unless you are
591 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
592 Delete a message (usually a 'bulletin') from the whole cluster system.
594 This uses the subject field, so any messages that have exactly the
595 same subject will be deleted. Beware!
597 === 0^LINKS^Show which nodes is physically connected
598 This is a quick listing that shows which links are connected and
599 some information about them. See WHO for a list of all connections.
601 === 9^LOAD/ALIASES^Reload the command alias table
602 Reload the /spider/cmd/Aliases file after you have editted it. You
603 will need to do this if you change this file whilst the cluster is
604 running in order for the changes to take effect.
606 === 9^LOAD/BANDS^Reload the band limits table
607 Reload the /spider/data/bands.pl file if you have changed it manually whilst
608 the cluster is running.
610 === 9^LOAD/BADMSG^Reload the bad msg table
611 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
612 the cluster is running. This table contains a number of perl regular
613 expressions which are searched for in the fields targetted of each message.
614 If any of them match then that message is immediately deleted on receipt.
616 === 9^LOAD/BADWORDS^Reload the bad words table
617 Reload the /spider/data/badwords file if you have changed it manually whilst
618 the cluster is running. This file contains a list of words which, if found
619 on certain text portions of PC protocol, will cause those protocol frames
620 to be rejected. It will all put out a message if any of these words are
621 used on the announce, dx and talk commands. The words can be one or
622 more on a line, lines starting with '#' are ignored.
624 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
625 Normally, if you change a command file in the cmd or local_cmd tree it
626 will automatially be picked up by the cluster program. Sometimes it
627 can get confused if you are doing a lot of moving commands about or
628 delete a command in the local_cmd tree and want to use the normal one
629 again. Execute this command to reset everything back to the state it
630 was just after a cluster restart.
632 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
633 Reload the /spider/msg/forward.pl file if you have changed it
634 manually whilst the cluster is running.
636 === 9^LOAD/MESSAGES^Reload the system messages file
637 If you change the /spider/perl/Messages file (usually whilst
638 fiddling/writing new commands) you can have them take effect during a
639 cluster session by executing this command. You need to do this if get
642 unknown message 'xxxx' in lang 'en'
644 === 9^LOAD/PREFIXES^Reload the prefix table
645 Reload the /spider/data/prefix_data.pl file if you have changed it
646 manually whilst the cluster is running.
648 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
649 MERGE allows you to bring your spot and wwv database up to date. By default
650 it will request the last 10 spots and 5 WWVs from the node you select. The
651 node must be connected locally.
653 You can request any number of spots or wwv and although they will be appended
654 to your databases they will not duplicate any that have recently been added
655 (the last 2 days for spots and last month for WWV data).
657 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
658 Alter message parameters like To, From, Subject, whether private or bulletin
659 or return receipt (RR) is required or whether to keep this message from timing
662 MSG TO <msgno> <call> - change TO callsign to <call>
663 MSG FRom <msgno> <call> - change FROM callsign to <call>
664 MSG PRrivate <msgno> - set private flag
665 MSG NOPRrivate <msgno> - unset private flag
666 MSG RR <msgno> - set RR flag
667 MSG NORR <msgno> - unset RR flag
668 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
669 MSG NOKEep <msgno> - unset the keep flag
670 MSG SUbject <msgno> <new> - change the subject to <new>
671 MSG WAittime <msgno> - remove any waitting time for this message
672 MSG NOREad <msgno> - mark message as unread
673 MSG REad <msgno> - mark message as read
674 MSG QUeue - queue any outstanding bulletins
675 MSG QUeue 1 - queue any outstanding private messages
677 You can look at the status of a message by using:-
681 This will display more information on the message than DIR does.
683 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
684 Send some arbitrary text to a locally connected callsign. No
685 processing is done on the text. This command allows you to send PC
686 Protocol to unstick things if problems arise (messages get stuck
689 pc gb7djk PC33^GB7TLH^GB7DJK^400^
691 pc G1TLH Try doing that properly!!!
693 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
694 You can get rid of any message to or originating from your callsign using
695 this command. You can remove more than one message at a time.
697 === 5^KILL <from>-<to>^Remove a range of messages from the system
698 === 5^KILL FROM <call>^Remove all messages from a callsign
699 === 5^KILL TO <call>^Remove all messages to a callsign
700 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
701 Remove this message from the entire cluster system as well as your node.
704 As a sysop you can kill any message on the system.
706 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
707 Send any text you like to the callsign requested. This is used mainly to send
708 PC protocol to connected nodes either for testing or to unstick things.
710 You can also use in the same way as a talk command to a connected user but
711 without any processing, added of "from <blah> to <blah" or whatever.
713 === 1^PING <node call>^Check the link quality between nodes
714 This command allows you to send a frame to another cluster node on
715 the network and get a return frame. The time it takes to do this
716 is a good indication of the quality of the link. The actual time
717 it takes is output to the console in seconds.
718 Any visible cluster node can be PINGed.
720 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
721 This command allows you to send nearly any command to another DX Cluster
722 node that is connected to the system.
724 Whether you get any output is dependant on a) whether the other system knows
725 that the node callsign of this cluster is in fact a node b) whether the
726 other system is allowing RCMDs from this node and c) whether you have
727 permission to send this command at all.
729 === 0^READ^Read the next unread personal message addressed to you
730 === 0^READ <msgno>^Read the specified message
731 You can read any messages that are sent as 'non-personal' and also any
732 message either sent by or sent to your callsign.
735 As a sysop you may read any message on the system
737 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
738 Create an 'reject this announce' line for a filter.
740 A reject filter line means that if the announce matches this filter it is
741 passed onto the user. See HELP FILTERS for more info. Please read this
742 to understand how filters work - it will save a lot of grief later on.
744 You can use any of the following things in this line:-
746 info <string> eg: iota or qsl
747 by <prefixes> eg: G,M,2
749 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
751 origin_zone <numbers>
756 wx 1 filter WX announces
757 dest <prefixes> eg: 6MUK,WDX (distros)
761 rej/ann by_zone 14,15,16 and not by G,M,2
763 You can use the tag 'all' to reject everything eg:
767 but this probably for advanced users...
769 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
770 This version allows a sysop to set a filter for a callsign as well as the
771 default for nodes and users eg:-
774 reject/ann input node_default by G,M,2
775 reject/ann user_default by G,M,2
777 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
778 Create a 'reject this spot' line for a filter.
780 A reject filter line means that if the spot matches this filter it is
781 dumped (not passed on). See HELP FILTERS for more info. Please read this
782 to understand how filters work - it will save a lot of grief later on.
784 You can use any of the following things in this line:-
786 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
787 on <range> same as 'freq'
788 call <prefixes> eg: G,PA,HB9
789 info <string> eg: iota or qsl
791 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
800 For frequencies, you can use any of the band names defined in
801 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
802 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
803 this is more efficient than saying simply: on HF (but don't get
804 too hung up about that)
809 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
811 You can use the tag 'all' to reject everything eg:
815 but this probably for advanced users...
817 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
818 This version allows a sysop to set a filter for a callsign as well as the
819 default for nodes and users eg:-
821 reject/spot db0sue-7 1 by_zone 14,15,16
822 reject/spot node_default all
823 set/hops node_default 10
825 reject/spot user_default by G,M,2
827 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
828 It is unlikely that you will want to do this, but if you do then you can
829 filter on the following fields:-
831 by <prefixes> eg: G,M,2
833 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
835 origin_zone <numbers>
841 There are no examples because WCY Broadcasts only come from one place and
842 you either want them or not (see UNSET/WCY if you don't want them).
844 This command is really provided for future use.
846 See HELP FILTER for information.
848 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
849 This version allows a sysop to set a filter for a callsign as well as the
850 default for nodes and users eg:-
852 reject/wcy gb7djk all
854 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
855 It is unlikely that you will want to do this, but if you do then you can
856 filter on the following fields:-
858 by <prefixes> eg: G,M,2
860 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
862 origin_zone <numbers>
870 reject/wwv by_zone 14,15,16
872 is probably the only useful thing to do (which will only show WWV broadcasts
873 by stations in the US).
875 See HELP FILTER for information.
877 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV 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/wwv db0sue-7 1 by_zone 4
882 reject/wwv node_default all
884 reject/wwv user_default by W
886 === 0^REPLY^Reply (privately) to the last message that you have read
887 === 0^REPLY <msgno>^Reply (privately) to the specified message
888 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
889 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
890 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
891 You can reply to a message and the subject will automatically have
892 "Re:" inserted in front of it, if it isn't already present.
894 You can also use all the extra qualifiers such as RR, PRIVATE,
895 NOPRIVATE, B that you can use with the SEND command (see SEND
898 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
899 === 0^SEND RR <call>^Send a message and ask for a read receipt
900 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
901 === 0^SEND PRIVATE <call>^Send a personal message
902 === 0^SEND NOPRIVATE <call>^Send a message to all stations
903 All the SEND commands will create a message which will be sent either to
904 an individual callsign or to one of the 'bulletin' addresses.
906 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
907 it will mark the message as personal and send it to the cluster node that
908 that callsign is connected to.
910 You can have more than one callsign in all of the SEND commands.
912 You can have multiple qualifiers so that you can have for example:-
914 SEND RR COPY 123 PRIVATE G1TLH G0RDI
916 which should send a copy of message 123 to G1TLH and G0RDI and you will
917 receive a read receipt when they have read the message.
919 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
920 SP is an alias for SEND PRIVATE
922 === 0^SET/ADDRESS <your address>^Record your postal address
924 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
925 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
927 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
929 === 8^SET/BADDX <call>..^Stop words we do not wish to see in the callsign field
930 of a dx spot being propagated
931 === 8^UNSET/BADDX <call>..^Allow a word to be seen again in a DX spot
932 Setting a word as 'baddx' will prevent spots with that word in the
933 callsign field of a DX spot from going any further. They will not be
934 displayed and they will not be sent onto other nodes.
936 The word must be wriiten in full, no wild cards are allowed eg:-
938 set/baddx FORSALE VIDEO FR0G
940 To allow a word again, use the following command ...
944 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
945 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
946 Setting a callsign as a 'badnode' will prevent spots from that node
947 going any further. They will not be displayed and they will not be
948 sent onto other nodes.
950 The call must be a full eg:-
954 will stop anything from K1TTT. If you want SSIDs as well then you must
955 enter them specifically.
959 will allow spots from him again.
961 Use with extreme care. This command may well be superceeded by FILTERing.
963 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
964 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
965 Setting a callsign as a 'badspotter' will prevent spots from this callsign
966 going any further. They will not be displayed and they will not be
967 sent onto other nodes.
969 The call must be written in full, no wild cards are allowed eg:-
971 set/badspotter VE2STN
973 will stop anything from VE2STN. If you want SSIDs as well then you must
974 enter them specifically.
976 unset/badspotter VE2STN
978 will allow spots from him again.
980 Use with extreme care. This command may well be superceded by FILTERing.
982 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
983 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
985 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
987 === 9^SET/DEBUG <name>^Add a debug level to the debug set
988 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
990 === 0^SET/DX^Allow DX messages to come out on your terminal
991 === 0^UNSET/DX^Stop DX messages coming out on your terminal
993 === 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements
994 === 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements
995 A standard feature which is enabled in version 1.43 and above is
996 that if the spotter's grid square is known it is output on the end
997 of a DX announcement (there is just enough room). Some user programs
998 cannot cope with this. You can use this command to reset (or set)
1001 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1003 === 0^SET/ECHO^Make the cluster echo your input
1004 === 0^UNSET/ECHO^Stop the cluster echoing your input
1005 If you are connected via a telnet session, different implimentations
1006 of telnet handle echo differently depending on whether you are
1007 connected via port 23 or some other port. You can use this command
1008 to change the setting appropriately.
1010 The setting is stored in your user profile.
1012 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1014 === 0^SET/HERE^Tell the system you are present at your terminal
1015 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1017 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1018 Tell the cluster system where you normally connect to. Any Messages sent
1019 to you will normally find their way there should you not be connected.
1023 === 8^SET/HOPS <call> ann|spots|wwv|wcy <n>^Set hop count
1024 Set the hop count for a particular type of broadcast for a node.
1026 This command allows you to set up special hop counts for a node
1027 for currently: announce, spots, wwv and wcy broadcasts.
1030 set/hops gb7djk ann 10
1031 set/hops gb7mbc spots 20
1033 Set SHOW/HOPS for information on what is already set. This command
1034 creates a filter and works in conjunction with the filter system.
1036 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1037 Connect a node to your system in such a way that you are a full protocol
1038 member of its network and can see all spots on it, but nothing either leaks
1039 out from it nor goes back into from the rest of the nodes connected to you.
1041 You can potentially connect several nodes in this way.
1043 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1044 Remove isolation from a node - SET/ISOLATE
1046 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1047 You can select the language that you want the cluster to use. Currently
1048 the languages available are en (english) and nl (dutch).
1050 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1051 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1052 In order to get accurate headings and such like you must tell the system
1053 what your latitude and longitude is. If you have not yet done a SET/QRA
1054 then this command will set your QRA locator for you. For example:-
1055 SET/LOCATION 52 22 N 0 57 E
1057 === 0^SET/LOGININFO^Inform when a station logs in locally
1058 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1060 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1061 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1063 === 0^SET/NAME <your name>^Set your name
1064 Tell the system what your name is eg:-
1067 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1068 Tell the system that the call(s) are to be treated as AK1A cluster and
1069 fed PC Protocol rather normal user commands.
1071 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
1072 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1073 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1074 counter which is decremented on every outgoing ping and then reset to
1075 the 'obscount' value on every incoming ping. The default value of this
1078 What this means is that a neighbouring node will be pinged twice at
1079 (default) 300 second intervals and if no reply has been heard just before
1080 what would be the third attempt, that node is disconnected.
1082 If a ping is heard then the obscount is reset to the full value. Using
1083 default values, if a node has not responded to a ping within 15 minutes,
1086 You can set this parameter between 1 and 9.
1088 It is STRONGLY recommended that you don't change the default.
1090 === 0^SET/PAGE <lines per page>^Set the lines per page
1091 Tell the system how many lines you wish on a page when the number of line
1092 of output from a command is more than this. The default is 20. Setting it
1093 explicitly to 0 will disable paging.
1097 The setting is stored in your user profile.
1099 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1100 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1101 in order to determine the rolling quality of the link and, in future, to
1102 affect routing decisions. The default interval is 300 secs or 5 minutes.
1104 You can use this command to set a different interval. Please don't.
1106 But if you do the value you enter is treated as minutes up 30 and seconds
1107 for numbers greater than that.
1109 This is used also to help determine when a link is down at the far end
1110 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1111 for more information.
1113 If you must change it (and it may be useful for internet connected nodes
1114 on dynamic IP addresses that go away after a set time of usage) the time
1115 can be specified as:-
1117 5 which if less than 30 is converted to minutes otherwise is
1118 taken as the no of seconds between pings.
1123 Please be aware that this causes traffic to occur on the link, setting
1124 this value too low may annoy your neighbours beyond the point of
1127 You can switch this off by setting it to 0.
1129 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1130 Set the privilege level on a callsign. The privilege levels that pertain
1131 to commands are as default:-
1133 1 - allow remote nodes normal user RCMDs
1134 5 - various privileged commands (including shutdown, but not disc-
1135 connect), the normal level for another node.
1136 8 - more privileged commands (including disconnect)
1137 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1139 If you are a sysop and you come in as a normal user on a remote connection
1140 your privilege will automatically be set to 0.
1142 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1143 The password for a user can only be set by a full sysop. The string
1144 can contain any characters but any spaces are removed (you can type in
1145 spaces - but they won't appear in the password). You can see the
1146 result with STAT/USER.
1148 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1149 Tell the system that the call(s) are to be treated as DXSpider node and
1150 fed new style DX Protocol rather normal user commands.
1152 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
1153 === 0^SET/QRA <locator>^Set your QRA locator
1154 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1155 done a SET/LOCATION then your latitude and longitude will be set roughly
1156 correctly (assuming your locator is correct ;-). For example:-
1159 === 0^SET/QTH <your qth>^Set your QTH
1160 Tell the system where you are. For example:-
1161 SET/QTH East Dereham, Norfolk
1163 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1164 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1166 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1167 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1169 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1170 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1172 === 0^SET/WX^Allow WX messages to come out on your terminal
1173 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1175 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1176 Display all the bad dx callsigns in the system, see SET/BADDX
1177 for more information.
1179 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1180 Display all the bad node callsigns in the system, see SET/BADNODE
1181 for more information.
1183 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1184 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1185 for more information.
1187 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1188 This is very nearly the same as SHOW/TIME, the only difference the format
1189 of the date string if no arguments are given.
1191 If no prefixes or callsigns are given then this command returns the local
1192 time and UTC as the computer has it right now. If you give some prefixes
1193 then it will show UTC and UTC + the local offset (not including DST) at
1194 the prefixes or callsigns that you specify.
1196 === 0^SHOW/DX^Interrogate the spot database
1197 If you just type SHOW/DX you will get the last so many spots
1198 (sysop configurable, but usually 10).
1200 In addition you can add any number of these commands in very nearly
1201 any order to the basic SHOW/DX command, they are:-
1203 on <band> - eg 160m 20m 2m 23cm 6mm
1204 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1206 <number> - the number of spots you want
1207 <from>-<to> - <from> spot no <to> spot no in the selected list
1209 <prefix> - for a spotted callsign beginning with <prefix>
1210 *<suffix> - for a spotted callsign ending in <suffix>
1211 *<string>* - for a spotted callsign containing <string>
1213 day <number> - starting <number> days ago
1214 day <from>-<to> - <from> days <to> days ago
1216 info <text> - any spots containing <text> in the info or remarks
1218 by <call> - any spots spotted by <call> (spotter <call> is the
1221 qsl - this automatically looks for any qsl info on the call
1222 held in the spot database.
1224 iota [<iota>] - If the iota island number is missing it will look for
1225 the string iota and anything which looks like an iota
1226 island number. If you specify then it will look for
1229 qra [<locator>] - this will look for the specific locator if you specify
1230 one or else anything that looks like a locator.
1235 SH/DX on 20m info iota
1236 SH/DX 9a on vhf day 30
1242 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1243 This command takes the <prefix> (which can be a full or partial
1244 callsign if desired), looks up which internal country number it is
1245 and then displays all the spots as per SH/DX for that country.
1247 The options for SHOW/DX also apply to this command.
1251 SH/DXCC W on 20m info iota
1253 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1254 SHOW/FILES on its own will show you a list of the various fileareas
1255 available on the system. To see the contents of a particular file
1258 where <filearea> is the name of the filearea you want to see the
1261 You can also use shell globbing characters like '*' and '?' in a
1262 string to see a selection of files in a filearea eg:-
1263 SH/FILES bulletins arld*
1265 See also TYPE - to see the contents of a file.
1267 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1268 Show the contents of all the filters that are set. This command displays
1269 all the filters set - for all the various categories.
1271 === 8^SHOW/HOPS <call> [ann|spots|wcy|wwv]^Show the hop counts for a node
1272 This command shows the hop counts set up for a node. You can specify
1273 which category you want to see. If you leave the category out then
1274 all the categories will be listed.
1276 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1278 === 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
1280 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
1281 This command outputs a short section of the system log. On its own
1282 it will output a general logfile. With the optional callsign it will
1283 show output from the log associated with that callsign.
1285 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
1286 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1287 together with the azimuth and elevation of the sun currently at those
1290 If you don't specify any prefixes or callsigns, it will show the times for
1291 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1292 together with the current azimuth and elevation.
1294 In addition, it will show the gain or loss dB relative to the nominal
1295 distance of 385,000Km due to the ellipsoidal nature of the orbit.
1297 If all else fails it will show the Moonrise and set times for the node
1298 that you are connected to.
1305 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1306 This command allow you to estimate the likelihood of you contacting
1307 a station with the prefix you have specified. The output assumes a modest
1308 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1310 The result predicts the most likely operating frequencies and signal
1311 levels for high frequency (shortwave) radio propagation paths on
1312 specified days of the year and hours of the day. It is most useful for
1313 paths between 250 km and 6000 km, but can be used with reduced accuracy
1314 for paths shorter or longer than this.
1316 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1317 used to predict the MUF given the predicted flux, day of the year,
1318 hour of the day and geographic coordinates of the transmitter and
1319 receiver. This routine is reasonably accurate for the purposes here,
1320 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1321 than the programs used by major shortwave broadcasting organizations,
1322 such as the Voice of America.
1324 The command will display some header information detailing its
1325 assumptions, together with the locations, latitude and longitudes and
1326 bearings. It will then show UTC (UT), local time at the other end
1327 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1328 (Zen) and the likely signal strengths. Then for each frequency for which
1329 the system thinks there is a likelihood of a circuit it prints a value.
1331 The value is currently a likely S meter reading based on the conventional
1332 6dB / S point scale. If the value has a '+' appended it means that it is
1333 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1334 there is likely to be much fading and by an 's' that the signal is likely
1337 By default SHOW/MUF will show the next two hours worth of data. You
1338 can specify anything up to 24 hours worth of data by appending the no of
1339 hours required after the prefix. For example:-
1345 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1346 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1347 Location Lat / Long Azim
1348 East Dereham, Norfolk 52 41 N 0 57 E 47
1349 United-States-W 43 0 N 87 54 W 299
1350 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1351 18 23 11.5 -35 mS0+ mS2 S3
1352 19 0 11.2 -41 mS0+ mS2 S3
1354 indicating that you will have weak, fading circuits on top band and
1355 80m but usable signals on 40m (about S3).
1361 will get you the above display, but with the next 24 hours worth of
1367 Gives you an estimate of the long path propagation characterics. It
1368 should be noted that the figures will probably not be very useful, nor
1369 terrible accurate, but it is included for completeness.
1371 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1372 Show the type and version (if connected) of the nodes specified on the
1373 command line. If no callsigns are specified then a sorted list of all
1374 the non-user callsigns known to the system will be displayed.
1376 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1377 This command takes the <callsign> (which can be a full or partial
1378 callsign or a prefix), looks up which internal country number
1379 it is and then displays all the relevant prefixes for that country
1380 together with the internal country no, the CQ and ITU regions.
1384 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1385 Show the name and location where every program module was load from. This
1386 is useful for checking where you think you have loaded a .pm file from.
1388 === 0^SHOW/QRA <locator> [<locator>]^Show distance between locators
1389 === 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
1390 This is a multipurpose command that allows you either to calculate the
1391 distance and bearing between two locators or (if only one locator is
1392 given on the command line) the distance and beraing from your station
1393 to the locator. For example:-
1398 The first example will show the distance and bearing to the locator from
1399 yourself, the second example will calculate the distance and bearing from
1400 the first locator to the second. You can use 4 or 6 character locators.
1402 It is also possible to convert a latitude and longitude to a locator by
1403 using this command with a latitude and longitude as an argument, for
1406 SH/QRA 52 41 N 0 58 E
1408 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
1409 This command queries the QRZ callbook server on the internet
1410 and returns any information available for that callsign. This service
1411 is provided for users of this software by http://www.qrz.com
1413 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
1414 This command allows you to see to which node the callsigns specified are
1415 connected. It is a sort of inverse sh/config.
1419 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1420 Show the tracking data from your location to the satellite of your choice
1421 from now on for the next few hours.
1423 If you use this command without a satellite name it will display a list
1424 of all the satellites known currently to the system.
1426 If you give a name then you can obtain tracking data of all the passes
1427 that start and finish 5 degrees below the horizon. As default it will
1428 give information for the next three hours for every five minute period.
1430 You can alter the number of hours and the step size, within certain
1433 Each pass in a period is separated with a row of '-----' characters
1438 SH/SAT FENGYUN1 12 2
1440 === 0^SHOW/SUN [<prefix>|<callsign>]^Show sun rise and set times
1441 Show the sun rise and set times for a (list of) prefixes or callsigns,
1442 together with the azimuth and elevation of the sun currently at those
1445 If you don't specify any prefixes or callsigns, it will show the times for
1446 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1447 together with the current azimuth and elevation.
1449 If all else fails it will show the sunrise and set times for the node
1450 that you are connected to.
1455 SH/SUN G1TLH K9CW ZS
1457 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
1458 If no prefixes or callsigns are given then this command returns the local
1459 time and UTC as the computer has it right now. If you give some prefixes
1460 then it will show UTC and UTC + the local offset (not including DST) at
1461 the prefixes or callsigns that you specify.
1463 === 0^SHOW/WCY^Show last 10 WCY broadcasts
1464 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
1465 Display the most recent WCY information that has been received by the system
1467 === 0^SHOW/WWV^Show last 10 WWV broadcasts
1468 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
1469 Display the most recent WWV information that has been received by the system
1471 === 5^SHUTDOWN^Shutdown the cluster
1472 Shutdown the cluster and disconnect all the users
1474 === 9^SPOOF <call> <command>^Do a command as though you are another user
1475 This command is provided so that sysops can set a user's parameters without
1476 me having to write a special 'sysop' version for every user command. It
1477 allows you to pretend that you are doing the command as the user you specify.
1481 SPOOF G1TLH set/name Dirk
1482 SPOOF G1TLH set/qra JO02LQ
1484 === 5^STAT/DB <dbname>^Show the status of a database
1485 Show the internal status of a database descriptor.
1487 Depending on your privilege level you will see more or less information.
1488 This command is unlikely to be of much use to anyone other than a sysop.
1490 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
1491 Show the internal status of the channel object either for the channel that
1492 you are on or else for the callsign that you asked for.
1494 Only the fields that are defined (in perl term) will be displayed.
1496 === 5^STAT/MSG <msgno>^Show the status of a message
1497 This command shows the internal status of a message and includes information
1498 such as to whom it has been forwarded, its size, origin etc etc.
1500 === 5^STAT/USER [<callsign>]^Show the full status of a user
1501 Shows the full contents of a user record including all the secret flags
1504 Only the fields that are defined (in perl term) will be displayed.
1506 === 0^SYSOP^Regain your privileges if you login remotely
1507 The system automatically reduces your privilege level to that of a
1508 normal user if you login in remotely. This command allows you to
1509 regain your normal privilege level. It uses the normal system: five
1510 numbers are returned that are indexes into the character array that is
1511 your assigned password (see SET/PASSWORD). The indexes start from
1514 You are expected to return a string which contains the characters
1515 required in the correct order. You may intersperse those characters
1516 with others to obscure your reply for any watchers. For example (and
1517 these values are for explanation :-):
1519 password = 012345678901234567890123456789
1523 aa2bbbb0ccc5ddd7xxx3n
1527 They will all match. If there is no password you will still be offered
1528 numbers but nothing will happen when you input a string. Any match is
1531 === 0^TALK <call> [<text>]^Send a text message to another station
1532 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
1533 Send a short message to any other station that is visible on the cluster
1534 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
1535 command, they don't have to be connected locally.
1537 The second form of TALK is used when other cluster nodes are connected
1538 with restricted information. This usually means that they don't send
1539 the user information usually associated with logging on and off the cluster.
1541 If you know that G3JNB is likely to be present on GB7TLH, but you can only
1542 see GB7TLH in the SH/C list but with no users, then you would use the
1543 second form of the talk message.
1545 If you want to have a ragchew with someone you can leave the text message
1546 out and the system will go into 'Talk' mode. What this means is that a
1547 short message is sent to the recipient telling them that you are in a
1548 'Talking' frame of mind and then you just type - everything you send will
1549 go to the station that you asked for.
1551 All the usual announcements, spots and so on will still come out on your
1554 If you want to do something (such as send a spot) you preceed the normal
1555 command with a '/' character, eg:-
1557 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
1560 To leave talk mode type:
1564 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
1565 Type out the contents of a file in a filearea. So, for example, in
1566 filearea 'bulletins' you want to look at file 'arld051' you would
1568 TYPE bulletins/arld051
1570 See also SHOW/FILES to see what fileareas are available and a
1573 === 0^WHO^Show who is physically connected
1574 This is a quick listing that shows which callsigns are connected and
1575 what sort of connection they have
1577 === 0^WX <text>^Send a weather message to local users
1578 === 0^WX FULL <text>^Send a weather message to all cluster users
1579 === 5^WX SYSOP <text>^Send a weather message to other clusters only
1580 Weather messages can sometimes be useful if you are experiencing an extreme
1581 that may indicate enhanced conditions