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 reject everything that is left, eg:
48 === 8^ACCEPT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
49 This version allows a sysop to set a filter for a callsign as well as the
50 default for nodes and users eg:-
53 accept/ann input node_default by G,M,2
54 accept/ann user_default by G,M,2
56 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
57 Create an 'accept this spot' line for a filter.
59 An accept filter line means that if the spot matches this filter it is
60 passed onto the user. See HELP FILTERS for more info. Please read this
61 to understand how filters work - it will save a lot of grief later on.
63 You can use any of the following things in this line:-
65 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
66 call <prefixes> eg: G,PA,HB9
67 info <string> eg: iota or qsl
69 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
81 acc/spot 2 freq vhf and (by_zone 14,15,16 or call_zone 14,15,16)
83 You can use the tag 'all' to reject everything that is left, eg:
87 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
88 This version allows a sysop to set a filter for a callsign as well as the
89 default for nodes and users eg:-
91 accept/spot db0sue-7 1 by_zone 14,15,16
92 accept/spot node_default all
93 set/hops node_default 10
95 accept/spot user_default by G,M,2
97 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
98 <text> is the text of the announcement you wish to broadcast
100 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
101 This will send your announcement cluster wide
103 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
105 === 0^APROPOS <string>^Search help database for <string>
106 Search the help database for <string> (it isn't case sensitive), and print
107 the names of all the commands that may be relevant.
109 === 0^BYE^Exit from the cluster
110 This will disconnect you from the cluster
112 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
113 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
114 When you send messages the fact that you have forwarded it to another node
115 is remembered so that it isn't sent again. When you have a new partner
116 node and you add their callsign to your /spider/msg/forward.pl file, all
117 outstanding non-private messages will be forwarded to them. This may well
118 be ALL the non-private messages. You can prevent this by using these
122 catchup GB7DJK 300 301 302 303 500-510
124 and to undo what you have just done:-
127 uncatchup GB7DJK 300 301 302 303 500-510
129 which will arrange for them to be forward candidates again.
131 Order is not important.
133 === 0^CLEAR/SPOTS [1|all]^Clear a spot filter line
134 This command allows you to clear (remove) a line in a spot filter or to
135 remove the whole filter.
137 If you have a filter:-
139 acc/spot 1 freq hf/cw
140 acc/spot 2 freq vhf and (by_zone 14,15,16 or call_zone 14,15,16)
146 you will be left with:-
148 acc/spot 2 freq vhf and (by_zone 14,15,16 or call_zone 14,15,16)
154 the filter will be completely removed.
156 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
157 Start a connection process that will culminate in a new connection to the
158 DX cluster <callsign>. This process creates a new 'client' process which will
159 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
160 necessary to traverse the network(s) to logon to the cluster <callsign>.
162 === 0^DBAVAIL^Show a list of all the Databases in the system
163 Title says it all really, this command lists all the databases defined
164 in the system. It is also aliased to SHOW/COMMAND.
166 === 9^DBCREATE <name>^Create a database entry
167 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
168 === 9^DBCREATE <name> remote <node>^Create a remote database entry
169 DBCREATE allows you to define a database in the system. It doesn't actually
170 create anything, just defines it.
172 The databases that are created are simple DB_File hash databases, they are
173 therefore already 'indexed'.
175 You can define a local database with the first form of the command eg:
179 You can also chain databases with the addition of the 'chain' keyword.
180 This will search each database one after the other. A typical example
183 DBCREATE sdx_qsl chain sql_ad
185 No checking is done to see if the any of the chained databases exist, in
186 fact it is usually better to do the above staement first then do each of
187 the chained databases.
189 Databases can exist offsite. To define a database that lives on another
192 DBCREATE buckmaster remote gb7dxc
194 Remote databases cannot be chained; however, the last database in a
195 a chain can be a remote database eg:
197 DBCREATE qsl chain gb7dxc
199 To see what databases have been defined do:
201 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
203 It would be normal for you to add an entry into your local Aliases file
204 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
205 need to add a line like:-
210 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
219 to work as they may be used to.
221 See DBIMPORT for the importing of existing AK1A format data to databases.
222 See DBSHOW for generic database enquiry
224 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
225 If you want to import or update data in bulk to a database you can use
226 this command. It will either create or update entries into an existing
227 database. For example:-
229 DBIMPORT oblast /tmp/OBLAST.FUL
231 will import the standard OBLAST database that comes with AK1A into the
232 oblast database held locally.
234 === 9^DBREMOVE <dbname>^Delete a database
235 DBREMOVE will completely remove a database entry and also delete any data
236 file that is associated with it.
238 There is no warning, no comeback, no safety net.
244 will remove the oblast database from the system and it will also remove
245 the associated datafile.
249 There is no warning, no comeback, no safety net.
251 You have been warned.
253 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
254 This is the generic user interface to the database to the database system.
255 It is expected that the sysop will add an entry to the local Aliases file
256 so that users can use the more familiar AK1A style of enquiry such as:
260 but if he hasn't and the database really does exist (use DBAVAIL or
261 SHOW/COMMAND to find out) you can do the same thing with:
265 === 9^DEBUG^Set the cluster program into debug mode
266 Executing this command will only have an effect if you are running the cluster
271 It will interrupt the cluster just after the debug command has finished.
272 === 0^DIRECTORY^List messages
273 === 0^DIRECTORY ALL^List all messages
274 === 0^DIRECTORY OWN^List your own messages
275 === 0^DIRECTORY NEW^List all new messages
276 === 0^DIRECTORY TO <call>^List all messages to <call>
277 === 0^DIRECTORY FROM <call>^List all messages from <call>
278 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
279 === 0^DIRECTORY <nn>^List last <nn> messages
280 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
281 List the messages in the messages directory.
283 If there is a 'p' one space after the message number then it is a
284 personal message. If there is a '-' between the message number and the
285 'p' then this indicates that the message has been read.
287 You can use shell escape characters such as '*' and '?' in the <call>
290 You can combine some of the various directory commands together eg:-
294 DIR SUBJECT IOTA 200-250
296 You can abbreviate all the commands to one letter and use ak1a syntax:-
302 Sysops can see all users' messages.
304 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
305 Disconnect any <call> connected locally
307 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
308 This is how you send a DX Spot to other users. You can, in fact, now
309 enter the <freq> and the <call> either way round.
315 will all give the same result. You can add some remarks to the end
316 of the command and they will be added to the spot.
318 DX FR0G 144600 this is a test
320 You can credit someone else by saying:-
322 DX by G1TLH FR0G 144.600 he isn't on the cluster
324 The <freq> is compared against the available bands set up in the
325 cluster. See SHOW/BANDS for more information.
327 === 9^EXPORT <msgno> <filename>^Export a message to a file
328 Export a message to a file. This command can only be executed on a local
329 console with a fully privileged user. The file produced will be in a form
330 ready to be imported back into the cluster by placing it in the import
331 directory (/spider/msg/import).
333 This command cannot overwrite an existing file. This is to provide some
334 measure of security. Any files written will owned by the same user as the
335 main cluster, otherwise you can put the new files anywhere the cluster can
336 access. For example:-
340 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
341 Export the users database to a file in ascii format. If no filename
342 is given then it will export the file to /spider/data/user_asc.
344 If the file already exists it will be renamed to <filename>.o. In fact
345 up to 5 generations of the file can be kept each one with an extra 'o' on the
348 BE WARNED: this will write to any file you have write access to. No check is
349 made on the filename (if any) that you specify.
351 === 0^FILTERING...^Filtering things in DXSpider
352 There are a number of things you can filter in the DXSpider system. They
353 all use the same general mechanism.
355 In general terms you can create a 'reject' or an 'accept' filter which can
356 have up to 10 lines in it. You do this using, for example:-
361 where ..... are the specific commands for that type of filter. There are
362 filters for spots, wwv, announce, wcy and (for sysops) connects. See each
363 different accept or reject command reference for more details.
365 There is also a command to clear out one or more lines in a filter and one
366 to show you what you have set. They are:-
375 There is clear/xxxx command for each type of filter.
377 For now we are going to use spots for the examples, but you can apply the
378 principles to all types of filter.
380 There are two main types of filter 'accept' or 'reject'; which you use depends
381 entirely on how you look at the world and what is least writing to achieve
382 what you want. Each filter has 10 lines (of any length) which are tried in
383 order. If a line matches then the action you have specified is taken (ie reject
384 means ignore it and accept means gimme it).
386 The important thing to remember is that if you specify a 'reject' filter (all
387 the lines in it say 'reject/spots' (for instance) then if a spot comes in that
388 doesn't match any of the lines then you will get it BUT if you specify an
389 'accept' filter then any spots that don't match are dumped. For example if I
390 have a one line accept filter:-
392 accept/spots freq vhf and (by_zone 14,15,16 or call_zone 14,15,16)
394 then automatically you will ONLY get VHF spots from or to CQ zones 14 15 and 16.
395 If you set a reject filter like:
397 reject/spots freq hf/cw
399 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
400 and will work it even on CW then you could say:-
402 reject/spots freq hf/cw and not info iota
404 But in that case you might only be interested in iota and say:-
406 accept/spots not freq hf/cw or info iota
408 which is exactly the same. You should choose one or the other until you are
409 confortable with the way it works. Yes, you can mix them (actually you can
410 have an accept AND a reject on the same line) but don't try this at home
411 until you can analyse the results that you get without ringing up the sysop
414 You can arrange your filter lines into logical units, either for your own
415 understanding or simply convenience. I have one set frequently:-
417 reject/spots 1 freq/cw
418 reject/spots 2 freq 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
420 What this does is to ignore all HF CW spots (being a class B I can't read
421 any CW and couldn't possibly be interested in HF :-) and also rejects any
422 spots on VHF which don't either originate or spot someone in Europe.
424 This is an exmaple where you would use the line number (1 and 2 in this case),
425 if you leave the digit out, the system assumes '1'. Digits '0'-'9' are
428 You can leave the word 'and' out if you want, it is implied. You can use any
429 number of brackets to make the 'expression' as you want it. There are things
430 called precedence rules working here which mean that you will NEED brackets
431 in a situation like line 2 because, without it, will assume:-
433 (freq 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
435 annoying, but that is the way it is. If you use OR - use brackets. Whilst we
436 are here CASE is not important. 'And BY_Zone' is just 'and by_zone'.
438 If you want to alter your filter you can just redefine one or more
439 lines of it or clear out one line. For example:-
441 reject/spots 1 freq/ssb
447 To remove the filter in its entirty:-
451 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
452 This command sends out any information held in the user file which can
453 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
454 and Homenode. PC41s are only sent for the information that is available.
456 === 0^HELP^The HELP Command
457 HELP is available for a number of commands. The syntax is:-
461 Where <cmd> is the name of the command you want help on.
463 All commands can be abbreviated, so SHOW/DX can be abbreviated
464 to SH/DX, ANNOUNCE can be shortened to AN and so on.
466 Look at the APROPOS <string> command which will search the help database
467 for the <string> you specify and give you a list of likely commands
468 to look at with HELP.
470 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
471 This command attempts to re-initialise a link to a (usually) AK1A node
472 that has got confused, usually by a protocol loop of some kind. It may
473 work - but you usually will be better off simply disconnecting it (or
474 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
477 Best of luck - you will need it.
479 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
480 Delete a message from the local system. You will only be able to
481 delete messages that you have originated or been sent (unless you are
484 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
485 Delete a message (usually a 'bulletin') from the whole cluster system.
487 This uses the subject field, so any messages that have exactly the
488 same subject will be deleted. Beware!
490 === 0^LINKS^Show which nodes is physically connected
491 This is a quick listing that shows which links are connected and
492 some information about them. See WHO for a list of all connections.
494 === 9^LOAD/ALIASES^Reload the command alias table
495 Reload the /spider/cmd/Aliases file after you have editted it. You
496 will need to do this if you change this file whilst the cluster is
497 running in order for the changes to take effect.
499 === 9^LOAD/BANDS^Reload the band limits table
500 Reload the /spider/data/bands.pl file if you have changed it manually whilst
501 the cluster is running.
503 === 9^LOAD/BADDX^Reload the bad DX table
504 Reload the /spider/data/baddx.pl file if you have changed it manually whilst
505 the cluster is running. This table contains the DX Calls that, if spotted,
506 will not be passed on. FR0G and TEST are classic examples.
508 === 9^LOAD/BADMSG^Reload the bad msg table
509 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
510 the cluster is running. This table contains a number of perl regular
511 expressions which are searched for in the fields targetted of each message.
512 If any of them match then that message is immediately deleted on receipt.
514 === 9^LOAD/BADWORDS^Reload the bad words table
515 Reload the /spider/data/badwords file if you have changed it manually whilst
516 the cluster is running. This file contains a list of words which, if found
517 on certain text portions of PC protocol, will cause those protocol frames
518 to be rejected. It will all put out a message if any of these words are
519 used on the announce, dx and talk commands. The words can be one or
520 more on a line, lines starting with '#' are ignored.
522 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
523 Normally, if you change a command file in the cmd or local_cmd tree it
524 will automatially be picked up by the cluster program. Sometimes it
525 can get confused if you are doing a lot of moving commands about or
526 delete a command in the local_cmd tree and want to use the normal one
527 again. Execute this command to reset everything back to the state it
528 was just after a cluster restart.
530 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
531 Reload the /spider/msg/forward.pl file if you have changed it
532 manually whilst the cluster is running.
534 === 9^LOAD/MESSAGES^Reload the system messages file
535 If you change the /spider/perl/Messages file (usually whilst
536 fiddling/writing new commands) you can have them take effect during a
537 cluster session by executing this command. You need to do this if get
540 unknown message 'xxxx' in lang 'en'
542 === 9^LOAD/PREFIXES^Reload the prefix table
543 Reload the /spider/data/prefix_data.pl file if you have changed it
544 manually whilst the cluster is running.
546 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
547 MERGE allows you to bring your spot and wwv database up to date. By default
548 it will request the last 10 spots and 5 WWVs from the node you select. The
549 node must be connected locally.
551 You can request any number of spots or wwv and although they will be appended
552 to your databases they will not duplicate any that have recently been added
553 (the last 2 days for spots and last month for WWV data).
555 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
556 Alter message parameters like To, From, Subject, whether private or bulletin
557 or return receipt (RR) is required or whether to keep this message from timing
560 MSG TO <msgno> <call> - change TO callsign to <call>
561 MSG FRom <msgno> <call> - change FROM callsign to <call>
562 MSG PRrivate <msgno> - set private flag
563 MSG NOPRrivate <msgno> - unset private flag
564 MSG RR <msgno> - set RR flag
565 MSG NORR <msgno> - unset RR flag
566 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
567 MSG NOKEep <msgno> - unset the keep flag
568 MSG SUbject <msgno> <new> - change the subject to <new>
569 MSG WAittime <msgno> - remove any waitting time for this message
570 MSG NOREad <msgno> - mark message as unread
571 MSG REad <msgno> - mark message as read
572 MSG QUeue - queue any outstanding bulletins
573 MSG QUeue 1 - queue any outstanding private messages
575 You can look at the status of a message by using:-
579 This will display more information on the message than DIR does.
581 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
582 Send some arbitrary text to a locally connected callsign. No
583 processing is done on the text. This command allows you to send PC
584 Protocol to unstick things if problems arise (messages get stuck
587 pc gb7djk PC33^GB7TLH^GB7DJK^400^
589 pc G1TLH Try doing that properly!!!
591 === 1^PING <node>^Send a ping command to another cluster
592 This command is used to estimate the quality of the link to another cluster.
593 The time returned is the length of time taken for a PC51 to go to another
594 cluster and be returned.
596 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
597 You can get rid of any message to or originating from your callsign using
598 this command. You can remove more than one message at a time.
600 === 5^KILL <from>-<to>^Remove a range of messages from the system
601 === 5^KILL FROM <call>^Remove all messages from a callsign
602 === 5^KILL TO <call>^Remove all messages to a callsign
603 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
604 Remove this message from the entire cluster system as well as your node.
607 As a sysop you can kill any message on the system.
609 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
610 Send any text you like to the callsign requested. This is used mainly to send
611 PC protocol to connected nodes either for testing or to unstick things.
613 You can also use in the same way as a talk command to a connected user but
614 without any processing, added of "from <blah> to <blah" or whatever.
616 === 1^PING <node call>^Find out the delays an a circuit to another node
617 This command will enable sysops to determine the speed of an inter-cluster
620 Any visible cluster node can be PINGed.
622 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
623 This command allows you to send nearly any command to another DX Cluster
624 node that is connected to the system.
626 Whether you get any output is dependant on a) whether the other system knows
627 that the node callsign of this cluster is in fact a node b) whether the
628 other system is allowing RCMDs from this node and c) whether you have
629 permission to send this command at all.
631 === 0^READ^Read the next unread personal message addressed to you
632 === 0^READ <msgno>^Read the specified message
633 You can read any messages that are sent as 'non-personal' and also any
634 message either sent by or sent to your callsign.
637 As a sysop you may read any message on the system
639 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set an 'reject' filter line for announce
640 Create an 'reject this announce' line for a filter.
642 An reject filter line means that if the announce matches this filter it is
643 passed onto the user. See HELP FILTERS for more info. Please read this
644 to understand how filters work - it will save a lot of grief later on.
646 You can use any of the following things in this line:-
648 info <string> eg: iota or qsl
649 by <prefixes> eg: G,M,2
651 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
653 origin_zone <numbers>
658 wx 1 filter WX announces
659 dest <prefixes> eg: 6MUK,WDX (distros)
663 rej/ann by_zone 14,15,16 and not by G,M,2
665 You can use the tag 'all' to reject everything that is left, eg:
669 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
670 This version allows a sysop to set a filter for a callsign as well as the
671 default for nodes and users eg:-
674 reject/ann input node_default by G,M,2
675 reject/ann user_default by G,M,2
677 === 0^REJECT/SPOTS [0-9] <pattern>^Set an 'reject' filter line for spots
678 Create an 'reject this spot' line for a filter.
680 An reject filter line means that if the spot matches this filter it is
681 dumped (not passed on). See HELP FILTERS for more info. Please read this
682 to understand how filters work - it will save a lot of grief later on.
684 You can use any of the following things in this line:-
686 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
687 call <prefixes> eg: G,PA,HB9
688 info <string> eg: iota or qsl
690 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
702 rej/spot 2 freq vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
704 You can use the tag 'all' to reject everything that is left, eg:
708 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
709 This version allows a sysop to set a filter for a callsign as well as the
710 default for nodes and users eg:-
712 reject/spot db0sue-7 1 by_zone 14,15,16
713 reject/spot node_default all
714 set/hops node_default 10
716 reject/spot user_default by G,M,2
718 === 0^REPLY^Reply (privately) to the last message that you have read
719 === 0^REPLY <msgno>^Reply (privately) to the specified message
720 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
721 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
722 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
723 You can reply to a message and the subject will automatically have
724 "Re:" inserted in front of it, if it isn't already present.
726 You can also use all the extra qualifiers such as RR, PRIVATE,
727 NOPRIVATE, B that you can use with the SEND command (see SEND
730 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
731 === 0^SEND RR <call>^Send a message and ask for a read receipt
732 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
733 === 0^SEND PRIVATE <call>^Send a personal message
734 === 0^SEND NOPRIVATE <call>^Send a message to all stations
735 All the SEND commands will create a message which will be sent either to
736 an individual callsign or to one of the 'bulletin' addresses.
738 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
739 it will mark the message as personal and send it to the cluster node that
740 that callsign is connected to.
742 You can have more than one callsign in all of the SEND commands.
744 You can have multiple qualifiers so that you can have for example:-
746 SEND RR COPY 123 PRIVATE G1TLH G0RDI
748 which should send a copy of message 123 to G1TLH and G0RDI and you will
749 receive a read receipt when they have read the message.
751 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
752 SP is an alias for SEND PRIVATE
754 === 0^SET/ADDRESS <your address>^Record your postal address
756 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
757 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
759 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
761 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
762 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
764 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
766 === 9^SET/DEBUG <name>^Add a debug level to the debug set
767 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
769 === 0^SET/DX^Allow DX messages to come out on your terminal
770 === 0^UNSET/DX^Stop DX messages coming out on your terminal
772 === 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements
773 === 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements
774 A standard feature which is enabled in version 1.43 and above is
775 that if the spotter's grid square is known it is output on the end
776 of a DX announcement (there is just enough room). Some user programs
777 cannot cope with this. You can use this command to reset (or set)
780 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
782 === 0^SET/ECHO^Make the cluster echo your input
783 === 0^UNSET/ECHO^Stop the cluster echoing your input
784 If you are connected via a telnet session, different implimentations
785 of telnet handle echo differently depending on whether you are
786 connected via port 23 or some other port. You can use this command
787 to change the setting appropriately.
789 The setting is stored in your user profile.
791 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
793 === 0^SET/HERE^Tell the system you are present at your terminal
794 === 0^UNSET/HERE^Tell the system you are absent from your terminal
796 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
797 Tell the cluster system where you normally connect to. Any Messages sent
798 to you will normally find their way there should you not be connected.
802 === 9^SET/ISOLATE^Isolate a node from the rest of the network
803 Connect a node to your system in such a way that you are a full protocol
804 member of its network and can see all spots on it, but nothing either leaks
805 out from it nor goes back into from the rest of the nodes connected to you.
807 You can potentially connect several nodes in this way.
809 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
810 Remove isolation from a node - SET/ISOLATE
812 === 0^SET/LANGUAGE <lang>^Set the language you want to use
813 You can select the language that you want the cluster to use. Currently
814 the languages available are en (english) and nl (dutch).
816 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
817 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
818 In order to get accurate headings and such like you must tell the system
819 what your latitude and longitude is. If you have not yet done a SET/QRA
820 then this command will set your QRA locator for you. For example:-
821 SET/LOCATION 52 22 N 0 57 E
823 === 0^SET/LOGININFO^Inform when a station logs in locally
824 === 0^UNSET/LOGININFO^Inform when a station logs out locally
826 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
827 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
829 === 0^SET/NAME <your name>^Set your name
830 Tell the system what your name is eg:-
833 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
834 Tell the system that the call(s) are to be treated as AK1A cluster and
835 fed PC Protocol rather normal user commands.
837 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
838 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
839 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
840 counter which is decremented on every outgoing ping and then reset to
841 the 'obscount' value on every incoming ping. The default value of this
844 What this means is that a neighbouring node will be pinged twice at
845 (default) 300 second intervals and if no reply has been heard just before
846 what would be the third attempt, that node is disconnected.
848 If a ping is heard then the obscount is reset to the full value. Using
849 default values, if a node has not responded to a ping within 15 minutes,
852 === 0^SET/PAGE <lines per page>^Set the lines per page
853 Tell the system how many lines you wish on a page when the number of line
854 of output from a command is more than this. The default is 20. Setting it
855 explicitly to 0 will disable paging.
859 The setting is stored in your user profile.
861 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
862 As from release 1.35 all neighbouring nodes are pinged at regular intervals
863 in order to determine the rolling quality of the link and, in future, to
864 affect routing decisions. The default interval is 300 secs or 5 minutes.
866 You can use this command to set a different interval. Please don't.
868 But if you do the value you enter is treated as minutes up 60 and seconds
869 for numbers greater than that.
871 This is used also to help determine when a link is down at the far end
872 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
873 for more information.
875 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
876 Set the privilege level on a callsign. The privilege levels that pertain
877 to commands are as default:-
879 1 - allow remote nodes normal user RCMDs
880 5 - various privileged commands (including shutdown, but not disc-
881 connect), the normal level for another node.
882 8 - more privileged commands (including disconnect)
883 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
885 If you are a sysop and you come in as a normal user on a remote connection
886 your privilege will automatically be set to 0.
888 === 9^SET/PASSWORD <callsign> <string>^Set a users password
889 The password for a user can only be set by a full sysop. The string
890 can contain any characters but any spaces are removed (you can type in
891 spaces - but they won't appear in the password). You can see the
892 result with STAT/USER.
894 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
895 Tell the system that the call(s) are to be treated as DXSpider node and
896 fed new style DX Protocol rather normal user commands.
898 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
899 === 0^SET/QRA <locator>^Set your QRA locator
900 Tell the system what your QRA (or Maidenhead) locator is. If you have not
901 done a SET/LOCATION then your latitude and longitude will be set roughly
902 correctly (assuming your locator is correct ;-). For example:-
905 === 0^SET/QTH <your qth>^Set your QTH
906 Tell the system where you are. For example:-
907 SET/QTH East Dereham, Norfolk
909 === 0^SET/TALK^Allow TALK messages to come out on your terminal
910 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
912 === 0^SET/WCY^Allow WCY messages to come out on your terminal
913 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
915 === 0^SET/WWV^Allow WWV messages to come out on your terminal
916 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
918 === 0^SET/WX^Allow WX messages to come out on your terminal
919 === 0^UNSET/WX^Stop WX messages coming out on your terminal
921 === 0^SHOW/CALL <callsign>^Show any callbook details on a callsign
922 This command queries an international callbook server on the internet
923 and returns any information available for that callsign.
925 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
926 This is very nearly the same as SHOW/TIME, the only difference the format
927 of the date string if no arguments are given.
929 If no prefixes or callsigns are given then this command returns the local
930 time and UTC as the computer has it right now. If you give some prefixes
931 then it will show UTC and UTC + the local offset (not including DST) at
932 the prefixes or callsigns that you specify.
934 === 0^SHOW/DX^Interrogate the spot database
935 If you just type SHOW/DX you will get the last so many spots
936 (sysop configurable, but usually 10).
938 In addition you can add any number of these commands in very nearly
939 any order to the basic SHOW/DX command, they are:-
941 on <band> - eg 160m 20m 2m 23cm 6mm
942 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
944 <number> - the number of spots you want
945 <from>-<to> - <from> spot no <to> spot no in the selected list
947 <prefix> - for a spotted callsign beginning with <prefix>
948 *<suffix> - for a spotted callsign ending in <suffix>
949 *<string>* - for a spotted callsign containing <string>
951 day <number> - starting <number> days ago
952 day <from>-<to> - <from> days <to> days ago
954 info <text> - any spots containing <text> in the info or remarks
956 by <call> - any spots spotted by <call> (spotter <call> is the
959 qsl - this automatically looks for any qsl info on the call
960 held in the spot database.
962 iota [<iota>] - If the iota island number is missing it will look for
963 the string iota and anything which looks like an iota
964 island number. If you specify then it will look for
967 qra [<locator>] - this will look for the specific locator if you specify
968 one or else anything that looks like a locator.
973 SH/DX on 20m info iota
974 SH/DX 9a on vhf day 30
980 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
981 This command takes the <prefix> (which can be a full or partial
982 callsign if desired), looks up which internal country number it is
983 and then displays all the spots as per SH/DX for that country.
985 The options for SHOW/DX also apply to this command.
989 SH/DXCC W on 20m info iota
991 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
992 SHOW/FILES on its own will show you a list of the various fileareas
993 available on the system. To see the contents of a particular file
996 where <filearea> is the name of the filearea you want to see the
999 You can also use shell globbing characters like '*' and '?' in a
1000 string to see a selection of files in a filearea eg:-
1001 SH/FILES bulletins arld*
1003 See also TYPE - to see the contents of a file.
1005 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1006 Show the contents of all the filters that are set. This command displays
1007 all the filters set - for all the various categories.
1009 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1011 === 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
1013 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
1014 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1015 together with the azimuth and elevation of the sun currently at those
1018 If you don't specify any prefixes or callsigns, it will show the times for
1019 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1020 together with the current azimuth and elevation.
1022 In addition, it will show the gain or loss dB relative to the nominal
1023 distance of 385,000Km due to the ellipsoidal nature of the orbit.
1025 If all else fails it will show the Moonrise and set times for the node
1026 that you are connected to.
1033 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1034 This command allow you to estimate the likelihood of you contacting
1035 a station with the prefix you have specified. The output assumes a modest
1036 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1038 The result predicts the most likely operating frequencies and signal
1039 levels for high frequency (shortwave) radio propagation paths on
1040 specified days of the year and hours of the day. It is most useful for
1041 paths between 250 km and 6000 km, but can be used with reduced accuracy
1042 for paths shorter or longer than this.
1044 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1045 used to predict the MUF given the predicted flux, day of the year,
1046 hour of the day and geographic coordinates of the transmitter and
1047 receiver. This routine is reasonably accurate for the purposes here,
1048 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1049 than the programs used by major shortwave broadcasting organizations,
1050 such as the Voice of America.
1052 The command will display some header information detailing its
1053 assumptions, together with the locations, latitude and longitudes and
1054 bearings. It will then show UTC (UT), local time at the other end
1055 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1056 (Zen) and the likely signal strengths. Then for each frequency for which
1057 the system thinks there is a likelihood of a circuit it prints a value.
1059 The value is currently a likely S meter reading based on the conventional
1060 6dB / S point scale. If the value has a '+' appended it means that it is
1061 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1062 there is likely to be much fading and by an 's' that the signal is likely
1065 By default SHOW/MUF will show the next two hours worth of data. You
1066 can specify anything up to 24 hours worth of data by appending the no of
1067 hours required after the prefix. For example:-
1073 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1074 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1075 Location Lat / Long Azim
1076 East Dereham, Norfolk 52 41 N 0 57 E 47
1077 United-States-W 43 0 N 87 54 W 299
1078 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1079 18 23 11.5 -35 mS0+ mS2 S3
1080 19 0 11.2 -41 mS0+ mS2 S3
1082 indicating that you will have weak, fading circuits on top band and
1083 80m but usable signals on 40m (about S3).
1089 will get you the above display, but with the next 24 hours worth of
1095 Gives you an estimate of the long path propagation characterics. It
1096 should be noted that the figures will probably not be very useful, nor
1097 terrible accurate, but it is included for completeness.
1099 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1100 Show the type and version (if connected) of the nodes specified on the
1101 command line. If no callsigns are specified then a sorted list of all
1102 the non-user callsigns known to the system will be displayed.
1104 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1105 This command takes the <callsign> (which can be a full or partial
1106 callsign or a prefix), looks up which internal country number
1107 it is and then displays all the relevant prefixes for that country
1108 together with the internal country no, the CQ and ITU regions.
1112 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1113 Show the name and location where every program module was load from. This
1114 is useful for checking where you think you have loaded a .pm file from.
1116 === 0^SHOW/QRA <locator> [<locator>]^Show distance between locators
1117 === 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
1118 This is a multipurpose command that allows you either to calculate the
1119 distance and bearing between two locators or (if only one locator is
1120 given on the command line) the distance and beraing from your station
1121 to the locator. For example:-
1126 The first example will show the distance and bearing to the locator from
1127 yourself, the second example will calculate the distance and bearing from
1128 the first locator to the second. You can use 4 or 6 character locators.
1130 It is also possible to convert a latitude and longitude to a locator by
1131 using this command with a latitude and longitude as an argument, for
1134 SH/QRA 52 41 N 0 58 E
1136 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1137 Show the tracking data from your location to the satellite of your choice
1138 from now on for the next few hours.
1140 If you use this command without a satellite name it will display a list
1141 of all the satellites known currently to the system.
1143 If you give a name then you can obtain tracking data of all the passes
1144 that start and finish 5 degrees below the horizon. As default it will
1145 give information for the next three hours for every five minute period.
1147 You can alter the number of hours and the step size, within certain
1150 Each pass in a period is separated with a row of '-----' characters
1155 SH/SAT FENGYUN1 12 2
1157 === 0^SHOW/SUN [<prefix>|<callsign>]^Show sun rise and set times
1158 Show the sun rise and set times for a (list of) prefixes or callsigns,
1159 together with the azimuth and elevation of the sun currently at those
1162 If you don't specify any prefixes or callsigns, it will show the times for
1163 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1164 together with the current azimuth and elevation.
1166 If all else fails it will show the sunrise and set times for the node
1167 that you are connected to.
1172 SH/SUN G1TLH K9CW ZS
1174 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
1175 If no prefixes or callsigns are given then this command returns the local
1176 time and UTC as the computer has it right now. If you give some prefixes
1177 then it will show UTC and UTC + the local offset (not including DST) at
1178 the prefixes or callsigns that you specify.
1180 === 0^SHOW/WCY^Show last 10 WCY broadcasts
1181 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
1182 Display the most recent WCY information that has been received by the system
1184 === 0^SHOW/WWV^Show last 10 WWV broadcasts
1185 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
1186 Display the most recent WWV information that has been received by the system
1188 === 5^SHUTDOWN^Shutdown the cluster
1189 Shutdown the cluster and disconnect all the users
1191 === 9^SPOOF <call> <command>^Do a command as though you are another user
1192 This command is provided so that sysops can set a user's parameters without
1193 me having to write a special 'sysop' version for every user command. It
1194 allows you to pretend that you are doing the command as the user you specify.
1198 SPOOF G1TLH set/name Dirk
1199 SPOOF G1TLH set/qra JO02LQ
1201 === 5^STAT/DB <dbname>^Show the status of a database
1202 Show the internal status of a database descriptor.
1204 Depending on your privilege level you will see more or less information.
1205 This command is unlikely to be of much use to anyone other than a sysop.
1207 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
1208 Show the internal status of the channel object either for the channel that
1209 you are on or else for the callsign that you asked for.
1211 Only the fields that are defined (in perl term) will be displayed.
1213 === 5^STAT/MSG <msgno>^Show the status of a message
1214 This command shows the internal status of a message and includes information
1215 such as to whom it has been forwarded, its size, origin etc etc.
1217 === 5^STAT/USER [<callsign>]^Show the full status of a user
1218 Shows the full contents of a user record including all the secret flags
1221 Only the fields that are defined (in perl term) will be displayed.
1223 === 0^SYSOP^Regain your privileges if you login remotely
1224 The system automatically reduces your privilege level to that of a
1225 normal user if you login in remotely. This command allows you to
1226 regain your normal privilege level. It uses the normal system: five
1227 numbers are returned that are indexes into the character array that is
1228 your assigned password (see SET/PASSWORD). The indexes start from
1231 You are expected to return a string which contains the characters
1232 required in the correct order. You may intersperse those characters
1233 with others to obscure your reply for any watchers. For example (and
1234 these values are for explanation :-):
1236 password = 012345678901234567890123456789
1240 aa2bbbb0ccc5ddd7xxx3n
1244 They will all match. If there is no password you will still be offered
1245 numbers but nothing will happen when you input a string. Any match is
1248 === 0^TALK <call> [<text>]^Send a text message to another station
1249 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
1250 Send a short message to any other station that is visible on the cluster
1251 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
1252 command, they don't have to be connected locally.
1254 The second form of TALK is used when other cluster nodes are connected
1255 with restricted information. This usually means that they don't send
1256 the user information usually associated with logging on and off the cluster.
1258 If you know that G3JNB is likely to be present on GB7TLH, but you can only
1259 see GB7TLH in the SH/C list but with no users, then you would use the
1260 second form of the talk message.
1262 If you want to have a ragchew with someone you can leave the text message
1263 out and the system will go into 'Talk' mode. What this means is that a
1264 short message is sent to the recipient telling them that you are in a
1265 'Talking' frame of mind and then you just type - everything you send will
1266 go to the station that you asked for.
1268 All the usual announcements, spots and so on will still come out on your
1271 If you want to do something (such as send a spot) you preceed the normal
1272 command with a '/' character, eg:-
1274 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
1277 To leave talk mode type:
1281 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
1282 Type out the contents of a file in a filearea. So, for example, in
1283 filearea 'bulletins' you want to look at file 'arld051' you would
1285 TYPE bulletins/arld051
1287 See also SHOW/FILES to see what fileareas are available and a
1290 === 0^WHO^Show who is physically connected
1291 This is a quick listing that shows which callsigns are connected and
1292 what sort of connection they have
1294 === 0^WX <text>^Send a weather message to local users
1295 === 0^WX FULL <text>^Send a weather message to all cluster users
1296 === 5^WX SYSOP <text>^Send a weather message to other clusters only
1297 Weather messages can sometimes be useful if you are experiencing an extreme
1298 that may indicate enhanced conditions