2 # please put your help in in alphabetical order
4 # a string search is done in the command field (case is ignored)
5 # and all commands matching the asked for command are printed out
7 # the order of the fields in each header is
8 # privilege, command, Description
9 # if the command ends in a - then that line isn't printed, but any
10 # subsequent lines are
12 # Comment lines are indented before printing
14 === 0^ACCEPT/ANNOUNCE [0-9] <pattern>^Set an 'accept' filter line for announce
15 Create an 'accept this announce' line for a filter.
17 An accept filter line means that if the announce matches this filter it is
18 passed onto the user. See HELP FILTERING for more info. Please read this
19 to understand how filters work - it will save a lot of grief later on.
21 You can use any of the following things in this line:-
23 info <string> eg: iota or qsl
24 by <prefixes> eg: G,M,2
26 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
33 wx 1 filter WX announces
34 dest <prefixes> eg: 6MUK,WDX (distros)
39 acc/ann 2 by_zone 14,15,16
40 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
44 You can use the tag 'all' to accept everything eg:
48 but this probably for advanced users...
50 === 8^ACCEPT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
51 This version allows a sysop to set a filter for a callsign as well as the
52 default for nodes and users eg:-
55 accept/ann input node_default by G,M,2
56 accept/ann user_default by G,M,2
58 === 8^ACCEPT/ROUTE <call> [0-9] <pattern>^Set an 'accept' filter line for routing
59 Create an 'accept this routing PC Protocol' line for a filter.
61 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
62 it is passed thru that interface. See HELP FILTERING for more info. Please read this
63 to understand how filters work - it will save a lot of grief later on.
65 You can use any of the following things in this line:-
67 call <prefixes> the callsign of the thingy
68 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
71 origin <prefixes> really the interface it came in on
72 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
78 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
79 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
81 You can use the tag 'all' to accept everything eg:
86 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
87 Create an 'accept this spot' line for a filter.
89 An accept filter line means that if the spot matches this filter it is
90 passed onto the user. See HELP FILTERING for more info. Please read this
91 to understand how filters work - it will save a lot of grief later on.
93 You can use any of the following things in this line:-
95 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
96 on <range> same as 'freq'
97 call <prefixes> eg: G,PA,HB9
98 info <string> eg: iota or qsl
100 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
109 For frequencies, you can use any of the band names defined in
110 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
111 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
112 this is more efficient than saying simply: freq HF (but don't get
113 too hung up about that)
118 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
120 You can use the tag 'all' to accept everything, eg:
124 but this probably for advanced users...
127 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
128 This version allows a sysop to set a filter for a callsign as well as the
129 default for nodes and users eg:-
131 accept/spot db0sue-7 1 by_zone 14,15,16
132 accept/spot node_default all
133 set/hops node_default 10
135 accept/spot user_default by G,M,2
137 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
138 It is unlikely that you will want to do this, but if you do then you can
139 filter on the following fields:-
141 by <prefixes> eg: G,M,2
143 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
145 origin_zone <numbers>
151 There are no examples because WCY Broadcasts only come from one place and
152 you either want them or not (see UNSET/WCY if you don't want them).
154 This command is really provided for future use.
156 See HELP FILTER for information.
158 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
159 This version allows a sysop to set a filter for a callsign as well as the
160 default for nodes and users eg:-
162 accept/wcy node_default all
163 set/hops node_default 10
165 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
166 It is unlikely that you will want to do this, but if you do then you can
167 filter on the following fields:-
169 by <prefixes> eg: G,M,2
171 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
173 origin_zone <numbers>
183 is probably the only useful thing to do (which will only show WWV broadcasts
184 by stations in the US).
186 See HELP FILTER for information.
188 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
189 This version allows a sysop to set a filter for a callsign as well as the
190 default for nodes and users eg:-
192 accept/wwv db0sue-7 1 by_zone 4
193 accept/wwv node_default all
194 set/hops node_default 10
196 accept/wwv user_default by W,K
198 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
199 <text> is the text of the announcement you wish to broadcast
201 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
202 This will send your announcement cluster wide
204 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
206 === 0^APROPOS <string>^Search help database for <string>
207 Search the help database for <string> (it isn't case sensitive), and print
208 the names of all the commands that may be relevant.
210 === 0^BYE^Exit from the cluster
211 This will disconnect you from the cluster
213 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
214 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
215 When you send messages the fact that you have forwarded it to another node
216 is remembered so that it isn't sent again. When you have a new partner
217 node and you add their callsign to your /spider/msg/forward.pl file, all
218 outstanding non-private messages will be forwarded to them. This may well
219 be ALL the non-private messages. You can prevent this by using these
223 catchup GB7DJK 300 301 302 303 500-510
225 and to undo what you have just done:-
228 uncatchup GB7DJK 300 301 302 303 500-510
230 which will arrange for them to be forward candidates again.
232 Order is not important.
234 === 0^CLEAR/SPOTS [1|all]^Clear a spot filter line
235 This command allows you to clear (remove) a line in a spot filter or to
236 remove the whole filter.
238 If you have a filter:-
241 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
247 you will be left with:-
249 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
255 the filter will be completely removed.
257 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
258 Start a connection process that will culminate in a new connection to the
259 DX cluster <callsign>. This process creates a new 'client' process which will
260 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
261 necessary to traverse the network(s) to logon to the cluster <callsign>.
263 === 0^DBAVAIL^Show a list of all the Databases in the system
264 Title says it all really, this command lists all the databases defined
265 in the system. It is also aliased to SHOW/COMMAND.
267 === 9^DBCREATE <name>^Create a database entry
268 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
269 === 9^DBCREATE <name> remote <node>^Create a remote database entry
270 DBCREATE allows you to define a database in the system. It doesn't actually
271 create anything, just defines it.
273 The databases that are created are simple DB_File hash databases, they are
274 therefore already 'indexed'.
276 You can define a local database with the first form of the command eg:
280 You can also chain databases with the addition of the 'chain' keyword.
281 This will search each database one after the other. A typical example
284 DBCREATE sdx_qsl chain sql_ad
286 No checking is done to see if the any of the chained databases exist, in
287 fact it is usually better to do the above staement first then do each of
288 the chained databases.
290 Databases can exist offsite. To define a database that lives on another
293 DBCREATE buckmaster remote gb7dxc
295 Remote databases cannot be chained; however, the last database in a
296 a chain can be a remote database eg:
298 DBCREATE qsl chain gb7dxc
300 To see what databases have been defined do:
302 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
304 It would be normal for you to add an entry into your local Aliases file
305 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
306 need to add a line like:-
311 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
320 to work as they may be used to.
322 See DBIMPORT for the importing of existing AK1A format data to databases.
323 See DBSHOW for generic database enquiry
325 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
326 If you want to import or update data in bulk to a database you can use
327 this command. It will either create or update entries into an existing
328 database. For example:-
330 DBIMPORT oblast /tmp/OBLAST.FUL
332 will import the standard OBLAST database that comes with AK1A into the
333 oblast database held locally.
335 === 9^DBREMOVE <dbname>^Delete a database
336 DBREMOVE will completely remove a database entry and also delete any data
337 file that is associated with it.
339 There is no warning, no comeback, no safety net.
345 will remove the oblast database from the system and it will also remove
346 the associated datafile.
350 There is no warning, no comeback, no safety net.
352 You have been warned.
354 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
355 This is the generic user interface to the database to the database system.
356 It is expected that the sysop will add an entry to the local Aliases file
357 so that users can use the more familiar AK1A style of enquiry such as:
361 but if he hasn't and the database really does exist (use DBAVAIL or
362 SHOW/COMMAND to find out) you can do the same thing with:
366 === 9^DEBUG^Set the cluster program into debug mode
367 Executing this command will only have an effect if you are running the cluster
372 It will interrupt the cluster just after the debug command has finished.
374 === 0^DIRECTORY^List messages
375 === 0^DIRECTORY ALL^List all messages
376 === 0^DIRECTORY OWN^List your own messages
377 === 0^DIRECTORY NEW^List all new messages
378 === 0^DIRECTORY TO <call>^List all messages to <call>
379 === 0^DIRECTORY FROM <call>^List all messages from <call>
380 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
381 === 0^DIRECTORY <nn>^List last <nn> messages
382 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
383 List the messages in the messages directory.
385 If there is a 'p' one space after the message number then it is a
386 personal message. If there is a '-' between the message number and the
387 'p' then this indicates that the message has been read.
389 You can use shell escape characters such as '*' and '?' in the <call>
392 You can combine some of the various directory commands together eg:-
396 DIR SUBJECT IOTA 200-250
398 You can abbreviate all the commands to one letter and use ak1a syntax:-
404 Sysops can see all users' messages.
406 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
407 Disconnect any <call> connected locally
409 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
410 This is how you send a DX Spot to other users. You can, in fact, now
411 enter the <freq> and the <call> either way round.
417 will all give the same result. You can add some remarks to the end
418 of the command and they will be added to the spot.
420 DX FR0G 144600 this is a test
422 You can credit someone else by saying:-
424 DX by G1TLH FR0G 144.600 he isn't on the cluster
426 The <freq> is compared against the available bands set up in the
427 cluster. See SHOW/BANDS for more information.
429 === 9^EXPORT <msgno> <filename>^Export a message to a file
430 Export a message to a file. This command can only be executed on a local
431 console with a fully privileged user. The file produced will be in a form
432 ready to be imported back into the cluster by placing it in the import
433 directory (/spider/msg/import).
435 This command cannot overwrite an existing file. This is to provide some
436 measure of security. Any files written will owned by the same user as the
437 main cluster, otherwise you can put the new files anywhere the cluster can
438 access. For example:-
442 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
443 Export the users database to a file in ascii format. If no filename
444 is given then it will export the file to /spider/data/user_asc.
446 If the file already exists it will be renamed to <filename>.o. In fact
447 up to 5 generations of the file can be kept each one with an extra 'o' on the
450 BE WARNED: this will write to any file you have write access to. No check is
451 made on the filename (if any) that you specify.
453 === 0^FILTERING...^Filtering things in DXSpider
454 There are a number of things you can filter in the DXSpider system. They
455 all use the same general mechanism.
457 In general terms you can create a 'reject' or an 'accept' filter which
458 can have up to 10 lines in it. You do this using, for example:-
463 where ..... are the specific commands for that type of filter. There
464 are filters for spots, wwv, announce, wcy and (for sysops)
465 connects. See each different accept or reject command reference for
468 There is also a command to clear out one or more lines in a filter and
469 one to show you what you have set. They are:-
478 There is clear/xxxx command for each type of filter.
480 For now we are going to use spots for the examples, but you can apply
481 the principles to all types of filter.
483 There are two main types of filter 'accept' or 'reject'; which you use
484 depends entirely on how you look at the world and what is least
485 writing to achieve what you want. Each filter has 10 lines (of any
486 length) which are tried in order. If a line matches then the action
487 you have specified is taken (ie reject means ignore it and accept
490 The important thing to remember is that if you specify a 'reject'
491 filter (all the lines in it say 'reject/spots' (for instance) then if
492 a spot comes in that doesn't match any of the lines then you will get
493 it BUT if you specify an 'accept' filter then any spots that don't
494 match are dumped. For example if I have a one line accept filter:-
496 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
498 then automatically you will ONLY get VHF spots from or to CQ zones 14
499 15 and 16. If you set a reject filter like:
501 reject/spots on hf/cw
503 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
504 and will work it even on CW then you could say:-
506 reject/spots on hf/cw and not info iota
508 But in that case you might only be interested in iota and say:-
510 accept/spots not on hf/cw or info iota
512 which is exactly the same. You should choose one or the other until
513 you are confortable with the way it works. Yes, you can mix them
514 (actually you can have an accept AND a reject on the same line) but
515 don't try this at home until you can analyse the results that you get
516 without ringing up the sysop for help.
518 You can arrange your filter lines into logical units, either for your
519 own understanding or simply convenience. I have one set frequently:-
521 reject/spots 1 on hf/cw
522 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
524 What this does is to ignore all HF CW spots (being a class B I can't
525 read any CW and couldn't possibly be interested in HF :-) and also
526 rejects any spots on VHF which don't either originate or spot someone
529 This is an exmaple where you would use the line number (1 and 2 in
530 this case), if you leave the digit out, the system assumes '1'. Digits
531 '0'-'9' are available.
533 You can leave the word 'and' out if you want, it is implied. You can
534 use any number of brackets to make the 'expression' as you want
535 it. There are things called precedence rules working here which mean
536 that you will NEED brackets in a situation like line 2 because,
537 without it, will assume:-
539 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
541 annoying, but that is the way it is. If you use OR - use
542 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
545 If you want to alter your filter you can just redefine one or more
546 lines of it or clear out one line. For example:-
548 reject/spots 1 on hf/ssb
554 To remove the filter in its entirty:-
560 Once you are happy with the results you get, you may like to experiment.
562 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
563 can be written with a mixed filter, eg:
567 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
569 each filter slot actually has a 'reject' slot and an 'accept'
570 slot. The reject slot is executed BEFORE the accept slot.
572 It was mentioned earlier that after a reject test that doesn't match,
573 the default for following tests is 'accept', the reverse is true for
574 'accept'. In the example what happens is that the reject is executed
575 first, any non hf/cw spot is passed to the accept line, which lets
576 thru everything else on HF.
578 The next filter line lets through just VHF/UHF spots from EU.
580 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
581 This command sends all the latitude and longitude information that your
582 cluster is holding against callsigns. One advantage of recieving this
583 information is that more locator information is held by you. This
584 means that more locators are given on the DX line assuming you have
585 SET/DXGRID enabled. This could be a LOT of information though, so
586 it is not recommended on slow links.
588 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
589 This command sends out any information held in the user file which can
590 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
591 and Homenode. PC41s are only sent for the information that is available.
593 === 0^HELP^The HELP Command
594 HELP is available for a number of commands. The syntax is:-
598 Where <cmd> is the name of the command you want help on.
600 All commands can be abbreviated, so SHOW/DX can be abbreviated
601 to SH/DX, ANNOUNCE can be shortened to AN and so on.
603 Look at the APROPOS <string> command which will search the help database
604 for the <string> you specify and give you a list of likely commands
605 to look at with HELP.
607 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
608 This command attempts to re-initialise a link to a (usually) AK1A node
609 that has got confused, usually by a protocol loop of some kind. It may
610 work - but you usually will be better off simply disconnecting it (or
611 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
614 Best of luck - you will need it.
616 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
617 Delete a message from the local system. You will only be able to
618 delete messages that you have originated or been sent (unless you are
621 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
622 Delete a message (usually a 'bulletin') from the whole cluster system.
624 This uses the subject field, so any messages that have exactly the
625 same subject will be deleted. Beware!
627 === 0^LINKS^Show which nodes is physically connected
628 This is a quick listing that shows which links are connected and
629 some information about them. See WHO for a list of all connections.
631 === 9^LOAD/ALIASES^Reload the command alias table
632 Reload the /spider/cmd/Aliases file after you have editted it. You
633 will need to do this if you change this file whilst the cluster is
634 running in order for the changes to take effect.
636 === 9^LOAD/BANDS^Reload the band limits table
637 Reload the /spider/data/bands.pl file if you have changed it manually whilst
638 the cluster is running.
640 === 9^LOAD/BADMSG^Reload the bad msg table
641 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
642 the cluster is running. This table contains a number of perl regular
643 expressions which are searched for in the fields targetted of each message.
644 If any of them match then that message is immediately deleted on receipt.
646 === 9^LOAD/BADWORDS^Reload the bad words table
647 Reload the /spider/data/badwords file if you have changed it manually whilst
648 the cluster is running. This file contains a list of words which, if found
649 on certain text portions of PC protocol, will cause those protocol frames
650 to be rejected. It will all put out a message if any of these words are
651 used on the announce, dx and talk commands. The words can be one or
652 more on a line, lines starting with '#' are ignored.
654 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
655 Normally, if you change a command file in the cmd or local_cmd tree it
656 will automatially be picked up by the cluster program. Sometimes it
657 can get confused if you are doing a lot of moving commands about or
658 delete a command in the local_cmd tree and want to use the normal one
659 again. Execute this command to reset everything back to the state it
660 was just after a cluster restart.
662 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
663 Reload the /spider/msg/forward.pl file if you have changed it
664 manually whilst the cluster is running.
666 === 9^LOAD/MESSAGES^Reload the system messages file
667 If you change the /spider/perl/Messages file (usually whilst
668 fiddling/writing new commands) you can have them take effect during a
669 cluster session by executing this command. You need to do this if get
672 unknown message 'xxxx' in lang 'en'
674 === 9^LOAD/PREFIXES^Reload the prefix table
675 Reload the /spider/data/prefix_data.pl file if you have changed it
676 manually whilst the cluster is running.
678 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
679 MERGE allows you to bring your spot and wwv database up to date. By default
680 it will request the last 10 spots and 5 WWVs from the node you select. The
681 node must be connected locally.
683 You can request any number of spots or wwv and although they will be appended
684 to your databases they will not duplicate any that have recently been added
685 (the last 2 days for spots and last month for WWV data).
687 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
688 Alter message parameters like To, From, Subject, whether private or bulletin
689 or return receipt (RR) is required or whether to keep this message from timing
692 MSG TO <msgno> <call> - change TO callsign to <call>
693 MSG FRom <msgno> <call> - change FROM callsign to <call>
694 MSG PRrivate <msgno> - set private flag
695 MSG NOPRrivate <msgno> - unset private flag
696 MSG RR <msgno> - set RR flag
697 MSG NORR <msgno> - unset RR flag
698 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
699 MSG NOKEep <msgno> - unset the keep flag
700 MSG SUbject <msgno> <new> - change the subject to <new>
701 MSG WAittime <msgno> - remove any waitting time for this message
702 MSG NOREad <msgno> - mark message as unread
703 MSG REad <msgno> - mark message as read
704 MSG QUeue - queue any outstanding bulletins
705 MSG QUeue 1 - queue any outstanding private messages
707 You can look at the status of a message by using:-
711 This will display more information on the message than DIR does.
713 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
714 Send some arbitrary text to a locally connected callsign. No
715 processing is done on the text. This command allows you to send PC
716 Protocol to unstick things if problems arise (messages get stuck
719 pc gb7djk PC33^GB7TLH^GB7DJK^400^
721 pc G1TLH Try doing that properly!!!
723 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
724 You can get rid of any message to or originating from your callsign using
725 this command. You can remove more than one message at a time.
727 === 5^KILL <from>-<to>^Remove a range of messages from the system
728 === 5^KILL FROM <call>^Remove all messages from a callsign
729 === 5^KILL TO <call>^Remove all messages to a callsign
730 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
731 Remove this message from the entire cluster system as well as your node.
734 As a sysop you can kill any message on the system.
736 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
737 Send any text you like to the callsign requested. This is used mainly to send
738 PC protocol to connected nodes either for testing or to unstick things.
740 You can also use in the same way as a talk command to a connected user but
741 without any processing, added of "from <blah> to <blah" or whatever.
743 === 1^PING <node call>^Check the link quality between nodes
744 This command allows you to send a frame to another cluster node on
745 the network and get a return frame. The time it takes to do this
746 is a good indication of the quality of the link. The actual time
747 it takes is output to the console in seconds.
748 Any visible cluster node can be PINGed.
750 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
751 This command allows you to send nearly any command to another DX Cluster
752 node that is connected to the system.
754 Whether you get any output is dependant on a) whether the other system knows
755 that the node callsign of this cluster is in fact a node b) whether the
756 other system is allowing RCMDs from this node and c) whether you have
757 permission to send this command at all.
759 === 0^READ^Read the next unread personal message addressed to you
760 === 0^READ <msgno>^Read the specified message
761 You can read any messages that are sent as 'non-personal' and also any
762 message either sent by or sent to your callsign.
765 As a sysop you may read any message on the system
767 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
768 Create an 'reject this announce' line for a filter.
770 A reject filter line means that if the announce matches this filter it is
771 passed onto the user. See HELP FILTERING for more info. Please read this
772 to understand how filters work - it will save a lot of grief later on.
774 You can use any of the following things in this line:-
776 info <string> eg: iota or qsl
777 by <prefixes> eg: G,M,2
779 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
781 origin_zone <numbers>
786 wx 1 filter WX announces
787 dest <prefixes> eg: 6MUK,WDX (distros)
791 rej/ann by_zone 14,15,16 and not by G,M,2
793 You can use the tag 'all' to reject everything eg:
797 but this probably for advanced users...
799 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
800 This version allows a sysop to set a filter for a callsign as well as the
801 default for nodes and users eg:-
804 reject/ann input node_default by G,M,2
805 reject/ann user_default by G,M,2
807 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
808 Create a 'reject this spot' line for a filter.
810 A reject filter line means that if the spot matches this filter it is
811 dumped (not passed on). See HELP FILTERING for more info. Please read this
812 to understand how filters work - it will save a lot of grief later on.
814 You can use any of the following things in this line:-
816 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
817 on <range> same as 'freq'
818 call <prefixes> eg: G,PA,HB9
819 info <string> eg: iota or qsl
821 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
830 For frequencies, you can use any of the band names defined in
831 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
832 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
833 this is more efficient than saying simply: on HF (but don't get
834 too hung up about that)
839 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
841 You can use the tag 'all' to reject everything eg:
845 but this probably for advanced users...
847 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
848 Create an 'reject this routing PC Protocol' line for a filter.
850 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
851 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
852 read this to understand how filters work - it will save a lot of grief later on.
854 You can use any of the following things in this line:-
856 call <prefixes> the callsign of the thingy
857 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
860 origin <prefixes> really the interface it came in on
861 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
863 origin_zone <numbers>
867 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
869 You can use the tag 'all' to reject everything eg:
871 rej/route all (equiv to [very] restricted mode)
873 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
874 This version allows a sysop to set a filter for a callsign as well as the
875 default for nodes and users eg:-
877 reject/spot db0sue-7 1 by_zone 14,15,16
878 reject/spot node_default all
879 set/hops node_default 10
881 reject/spot user_default by G,M,2
883 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
884 It is unlikely that you will want to do this, but if you do then you can
885 filter on the following fields:-
887 by <prefixes> eg: G,M,2
889 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
891 origin_zone <numbers>
897 There are no examples because WCY Broadcasts only come from one place and
898 you either want them or not (see UNSET/WCY if you don't want them).
900 This command is really provided for future use.
902 See HELP FILTER for information.
904 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
905 This version allows a sysop to set a filter for a callsign as well as the
906 default for nodes and users eg:-
908 reject/wcy gb7djk all
910 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
911 It is unlikely that you will want to do this, but if you do then you can
912 filter on the following fields:-
914 by <prefixes> eg: G,M,2
916 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
918 origin_zone <numbers>
926 reject/wwv by_zone 14,15,16
928 is probably the only useful thing to do (which will only show WWV broadcasts
929 by stations in the US).
931 See HELP FILTER for information.
933 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
934 This version allows a sysop to set a filter for a callsign as well as the
935 default for nodes and users eg:-
937 reject/wwv db0sue-7 1 by_zone 4
938 reject/wwv node_default all
940 reject/wwv user_default by W
942 === 0^REPLY^Reply (privately) to the last message that you have read
943 === 0^REPLY <msgno>^Reply (privately) to the specified message
944 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
945 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
946 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
947 You can reply to a message and the subject will automatically have
948 "Re:" inserted in front of it, if it isn't already present.
950 You can also use all the extra qualifiers such as RR, PRIVATE,
951 NOPRIVATE, B that you can use with the SEND command (see SEND
954 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
955 === 0^SEND RR <call>^Send a message and ask for a read receipt
956 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
957 === 0^SEND PRIVATE <call>^Send a personal message
958 === 0^SEND NOPRIVATE <call>^Send a message to all stations
959 All the SEND commands will create a message which will be sent either to
960 an individual callsign or to one of the 'bulletin' addresses.
962 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
963 it will mark the message as personal and send it to the cluster node that
964 that callsign is connected to.
966 You can have more than one callsign in all of the SEND commands.
968 You can have multiple qualifiers so that you can have for example:-
970 SEND RR COPY 123 PRIVATE G1TLH G0RDI
972 which should send a copy of message 123 to G1TLH and G0RDI and you will
973 receive a read receipt when they have read the message.
975 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
976 SP is an alias for SEND PRIVATE
978 === 0^SET/ADDRESS <your address>^Record your postal address
980 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
981 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
983 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
985 === 8^SET/BADDX <call>..^Stop words we do not wish to see in the callsign field
986 of a dx spot being propagated
987 === 8^UNSET/BADDX <call>..^Allow a word to be seen again in a DX spot
988 Setting a word as 'baddx' will prevent spots with that word in the
989 callsign field of a DX spot from going any further. They will not be
990 displayed and they will not be sent onto other nodes.
992 The word must be wriiten in full, no wild cards are allowed eg:-
994 set/baddx FORSALE VIDEO FR0G
996 To allow a word again, use the following command ...
1000 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1001 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1002 Setting a callsign as a 'badnode' will prevent spots from that node
1003 going any further. They will not be displayed and they will not be
1004 sent onto other nodes.
1006 The call must be a full eg:-
1010 will stop anything from K1TTT. If you want SSIDs as well then you must
1011 enter them specifically.
1015 will allow spots from him again.
1017 Use with extreme care. This command may well be superceeded by FILTERing.
1019 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1020 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1021 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1022 going any further. They will not be displayed and they will not be
1023 sent onto other nodes.
1025 The call must be written in full, no wild cards are allowed eg:-
1027 set/badspotter VE2STN
1029 will stop anything from VE2STN. If you want SSIDs as well then you must
1030 enter them specifically.
1032 unset/badspotter VE2STN
1034 will allow spots from him again.
1036 Use with extreme care. This command may well be superceded by FILTERing.
1038 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1039 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1041 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1043 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1045 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1046 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1047 You can choose to log several different levels. The levels are
1055 You can show what levels you are logging with SHOW/DEBUG
1057 === 0^SET/DX^Allow DX messages to come out on your terminal
1058 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1060 === 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements
1061 === 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements
1062 A standard feature which is enabled in version 1.43 and above is
1063 that if the spotter's grid square is known it is output on the end
1064 of a DX announcement (there is just enough room). Some user programs
1065 cannot cope with this. You can use this command to reset (or set)
1068 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1070 === 0^SET/ECHO^Make the cluster echo your input
1071 === 0^UNSET/ECHO^Stop the cluster echoing your input
1072 If you are connected via a telnet session, different implimentations
1073 of telnet handle echo differently depending on whether you are
1074 connected via port 23 or some other port. You can use this command
1075 to change the setting appropriately.
1077 The setting is stored in your user profile.
1079 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1081 === 0^SET/HERE^Tell the system you are present at your terminal
1082 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1084 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1085 Tell the cluster system where you normally connect to. Any Messages sent
1086 to you will normally find their way there should you not be connected.
1090 === 8^SET/HOPS <call> ann|spots|wwv|wcy <n>^Set hop count
1091 Set the hop count for a particular type of broadcast for a node.
1093 This command allows you to set up special hop counts for a node
1094 for currently: announce, spots, wwv and wcy broadcasts.
1097 set/hops gb7djk ann 10
1098 set/hops gb7mbc spots 20
1100 Set SHOW/HOPS for information on what is already set. This command
1101 creates a filter and works in conjunction with the filter system.
1103 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1104 Connect a node to your system in such a way that you are a full protocol
1105 member of its network and can see all spots on it, but nothing either leaks
1106 out from it nor goes back into from the rest of the nodes connected to you.
1108 You can potentially connect several nodes in this way.
1110 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1111 Remove isolation from a node - SET/ISOLATE
1113 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1114 You can select the language that you want the cluster to use. Currently
1115 the languages available are en (english) and nl (dutch).
1117 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1118 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1119 In order to get accurate headings and such like you must tell the system
1120 what your latitude and longitude is. If you have not yet done a SET/QRA
1121 then this command will set your QRA locator for you. For example:-
1122 SET/LOCATION 52 22 N 0 57 E
1124 === 0^SET/LOGININFO^Inform when a station logs in locally
1125 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1127 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1128 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1130 === 0^SET/NAME <your name>^Set your name
1131 Tell the system what your name is eg:-
1134 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1135 Tell the system that the call(s) are to be treated as AK1A cluster and
1136 fed PC Protocol rather normal user commands.
1138 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
1139 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1140 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1141 counter which is decremented on every outgoing ping and then reset to
1142 the 'obscount' value on every incoming ping. The default value of this
1145 What this means is that a neighbouring node will be pinged twice at
1146 (default) 300 second intervals and if no reply has been heard just before
1147 what would be the third attempt, that node is disconnected.
1149 If a ping is heard then the obscount is reset to the full value. Using
1150 default values, if a node has not responded to a ping within 15 minutes,
1153 You can set this parameter between 1 and 9.
1155 It is STRONGLY recommended that you don't change the default.
1157 === 0^SET/PAGE <lines per page>^Set the lines per page
1158 Tell the system how many lines you wish on a page when the number of line
1159 of output from a command is more than this. The default is 20. Setting it
1160 explicitly to 0 will disable paging.
1164 The setting is stored in your user profile.
1166 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1167 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1168 in order to determine the rolling quality of the link and, in future, to
1169 affect routing decisions. The default interval is 300 secs or 5 minutes.
1171 You can use this command to set a different interval. Please don't.
1173 But if you do the value you enter is treated as minutes up 30 and seconds
1174 for numbers greater than that.
1176 This is used also to help determine when a link is down at the far end
1177 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1178 for more information.
1180 If you must change it (and it may be useful for internet connected nodes
1181 on dynamic IP addresses that go away after a set time of usage) the time
1182 can be specified as:-
1184 5 which if less than 30 is converted to minutes otherwise is
1185 taken as the no of seconds between pings.
1190 Please be aware that this causes traffic to occur on the link, setting
1191 this value too low may annoy your neighbours beyond the point of
1194 You can switch this off by setting it to 0.
1196 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1197 Set the privilege level on a callsign. The privilege levels that pertain
1198 to commands are as default:-
1200 1 - allow remote nodes normal user RCMDs
1201 5 - various privileged commands (including shutdown, but not disc-
1202 connect), the normal level for another node.
1203 8 - more privileged commands (including disconnect)
1204 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1206 If you are a sysop and you come in as a normal user on a remote connection
1207 your privilege will automatically be set to 0.
1209 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1210 You can use this command to 'protect' this session from unauthorised
1211 use. If you want to get your normal privilege back you will need to
1212 either logout and login again (if you are on a console) or use the
1215 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1216 The password for a user can only be set by a full sysop. The string
1217 can contain any characters but any spaces are removed (you can type in
1218 spaces - but they won't appear in the password). You can see the
1219 result with STAT/USER.
1221 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1222 Tell the system that the call(s) are to be treated as DXSpider node and
1223 fed new style DX Protocol rather normal user commands.
1225 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
1226 === 0^SET/QRA <locator>^Set your QRA locator
1227 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1228 done a SET/LOCATION then your latitude and longitude will be set roughly
1229 correctly (assuming your locator is correct ;-). For example:-
1232 === 0^SET/QTH <your qth>^Set your QTH
1233 Tell the system where you are. For example:-
1234 SET/QTH East Dereham, Norfolk
1236 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1237 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1239 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1240 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1242 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1243 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1245 === 0^SET/WX^Allow WX messages to come out on your terminal
1246 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1248 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1249 Display all the bad dx callsigns in the system, see SET/BADDX
1250 for more information.
1252 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1253 Display all the bad node callsigns in the system, see SET/BADNODE
1254 for more information.
1256 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1257 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1258 for more information.
1260 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1261 This command allows you to see all the users that can be seen
1262 and the nodes to which they are connected.
1264 This command is normally abbreviated to: sh/c
1266 BE WARNED: the list that is returned can be VERY long
1268 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1269 Show all the nodes connected to this node.
1271 === 1^SHOW/CONNECT^Show all the active connections
1272 This command shows information on all the active connections known to
1273 the node. This command gives slightly more information than WHO.
1275 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1276 This is very nearly the same as SHOW/TIME, the only difference the format
1277 of the date string if no arguments are given.
1279 If no prefixes or callsigns are given then this command returns the local
1280 time and UTC as the computer has it right now. If you give some prefixes
1281 then it will show UTC and UTC + the local offset (not including DST) at
1282 the prefixes or callsigns that you specify.
1284 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1286 === 0^SHOW/DX^Interrogate the spot database
1287 If you just type SHOW/DX you will get the last so many spots
1288 (sysop configurable, but usually 10).
1290 In addition you can add any number of these commands in very nearly
1291 any order to the basic SHOW/DX command, they are:-
1293 on <band> - eg 160m 20m 2m 23cm 6mm
1294 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1296 <number> - the number of spots you want
1297 <from>-<to> - <from> spot no <to> spot no in the selected list
1299 <prefix> - for a spotted callsign beginning with <prefix>
1300 *<suffix> - for a spotted callsign ending in <suffix>
1301 *<string>* - for a spotted callsign containing <string>
1303 day <number> - starting <number> days ago
1304 day <from>-<to> - <from> days <to> days ago
1306 info <text> - any spots containing <text> in the info or remarks
1308 by <call> - any spots spotted by <call> (spotter <call> is the
1311 qsl - this automatically looks for any qsl info on the call
1312 held in the spot database.
1314 iota [<iota>] - If the iota island number is missing it will look for
1315 the string iota and anything which looks like an iota
1316 island number. If you specify then it will look for
1319 qra [<locator>] - this will look for the specific locator if you specify
1320 one or else anything that looks like a locator.
1325 SH/DX on 20m info iota
1326 SH/DX 9a on vhf day 30
1332 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1333 This command takes the <prefix> (which can be a full or partial
1334 callsign if desired), looks up which internal country number it is
1335 and then displays all the spots as per SH/DX for that country.
1337 The options for SHOW/DX also apply to this command.
1341 SH/DXCC W on 20m info iota
1343 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1344 SHOW/FILES on its own will show you a list of the various fileareas
1345 available on the system. To see the contents of a particular file
1348 where <filearea> is the name of the filearea you want to see the
1351 You can also use shell globbing characters like '*' and '?' in a
1352 string to see a selection of files in a filearea eg:-
1353 SH/FILES bulletins arld*
1355 See also TYPE - to see the contents of a file.
1357 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1358 Show the contents of all the filters that are set. This command displays
1359 all the filters set - for all the various categories.
1361 === 8^SHOW/HOPS <call> [ann|spots|wcy|wwv]^Show the hop counts for a node
1362 This command shows the hop counts set up for a node. You can specify
1363 which category you want to see. If you leave the category out then
1364 all the categories will be listed.
1366 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1368 === 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
1370 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
1371 This command outputs a short section of the system log. On its own
1372 it will output a general logfile. With the optional callsign it will
1373 show output from the log associated with that callsign.
1375 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
1376 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1377 together with the azimuth and elevation of the sun currently at those
1380 If you don't specify any prefixes or callsigns, it will show the times for
1381 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1382 together with the current azimuth and elevation.
1384 In addition, it will show the gain or loss dB relative to the nominal
1385 distance of 385,000Km due to the ellipsoidal nature of the orbit.
1387 If all else fails it will show the Moonrise and set times for the node
1388 that you are connected to.
1395 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1396 This command allow you to estimate the likelihood of you contacting
1397 a station with the prefix you have specified. The output assumes a modest
1398 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1400 The result predicts the most likely operating frequencies and signal
1401 levels for high frequency (shortwave) radio propagation paths on
1402 specified days of the year and hours of the day. It is most useful for
1403 paths between 250 km and 6000 km, but can be used with reduced accuracy
1404 for paths shorter or longer than this.
1406 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1407 used to predict the MUF given the predicted flux, day of the year,
1408 hour of the day and geographic coordinates of the transmitter and
1409 receiver. This routine is reasonably accurate for the purposes here,
1410 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1411 than the programs used by major shortwave broadcasting organizations,
1412 such as the Voice of America.
1414 The command will display some header information detailing its
1415 assumptions, together with the locations, latitude and longitudes and
1416 bearings. It will then show UTC (UT), local time at the other end
1417 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1418 (Zen) and the likely signal strengths. Then for each frequency for which
1419 the system thinks there is a likelihood of a circuit it prints a value.
1421 The value is currently a likely S meter reading based on the conventional
1422 6dB / S point scale. If the value has a '+' appended it means that it is
1423 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1424 there is likely to be much fading and by an 's' that the signal is likely
1427 By default SHOW/MUF will show the next two hours worth of data. You
1428 can specify anything up to 24 hours worth of data by appending the no of
1429 hours required after the prefix. For example:-
1435 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1436 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1437 Location Lat / Long Azim
1438 East Dereham, Norfolk 52 41 N 0 57 E 47
1439 United-States-W 43 0 N 87 54 W 299
1440 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1441 18 23 11.5 -35 mS0+ mS2 S3
1442 19 0 11.2 -41 mS0+ mS2 S3
1444 indicating that you will have weak, fading circuits on top band and
1445 80m but usable signals on 40m (about S3).
1451 will get you the above display, but with the next 24 hours worth of
1457 Gives you an estimate of the long path propagation characterics. It
1458 should be noted that the figures will probably not be very useful, nor
1459 terrible accurate, but it is included for completeness.
1461 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1462 Show the type and version (if connected) of the nodes specified on the
1463 command line. If no callsigns are specified then a sorted list of all
1464 the non-user callsigns known to the system will be displayed.
1466 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1467 This command takes the <callsign> (which can be a full or partial
1468 callsign or a prefix), looks up which internal country number
1469 it is and then displays all the relevant prefixes for that country
1470 together with the internal country no, the CQ and ITU regions.
1474 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1475 Show the name and location where every program module was load from. This
1476 is useful for checking where you think you have loaded a .pm file from.
1478 === 0^SHOW/QRA <locator> [<locator>]^Show distance between locators
1479 === 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
1480 This is a multipurpose command that allows you either to calculate the
1481 distance and bearing between two locators or (if only one locator is
1482 given on the command line) the distance and beraing from your station
1483 to the locator. For example:-
1488 The first example will show the distance and bearing to the locator from
1489 yourself, the second example will calculate the distance and bearing from
1490 the first locator to the second. You can use 4 or 6 character locators.
1492 It is also possible to convert a latitude and longitude to a locator by
1493 using this command with a latitude and longitude as an argument, for
1496 SH/QRA 52 41 N 0 58 E
1498 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
1499 This command queries the QRZ callbook server on the internet
1500 and returns any information available for that callsign. This service
1501 is provided for users of this software by http://www.qrz.com
1503 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
1504 This command allows you to see to which node the callsigns specified are
1505 connected. It is a sort of inverse sh/config.
1509 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1510 Show the tracking data from your location to the satellite of your choice
1511 from now on for the next few hours.
1513 If you use this command without a satellite name it will display a list
1514 of all the satellites known currently to the system.
1516 If you give a name then you can obtain tracking data of all the passes
1517 that start and finish 5 degrees below the horizon. As default it will
1518 give information for the next three hours for every five minute period.
1520 You can alter the number of hours and the step size, within certain
1523 Each pass in a period is separated with a row of '-----' characters
1528 SH/SAT FENGYUN1 12 2
1530 === 0^SHOW/SUN [<prefix>|<callsign>]^Show sun rise and set times
1531 Show the sun rise and set times for a (list of) prefixes or callsigns,
1532 together with the azimuth and elevation of the sun currently at those
1535 If you don't specify any prefixes or callsigns, it will show the times for
1536 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1537 together with the current azimuth and elevation.
1539 If all else fails it will show the sunrise and set times for the node
1540 that you are connected to.
1545 SH/SUN G1TLH K9CW ZS
1547 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
1548 If no prefixes or callsigns are given then this command returns the local
1549 time and UTC as the computer has it right now. If you give some prefixes
1550 then it will show UTC and UTC + the local offset (not including DST) at
1551 the prefixes or callsigns that you specify.
1553 === 0^SHOW/WCY^Show last 10 WCY broadcasts
1554 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
1555 Display the most recent WCY information that has been received by the system
1557 === 0^SHOW/WWV^Show last 10 WWV broadcasts
1558 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
1559 Display the most recent WWV information that has been received by the system
1561 === 5^SHUTDOWN^Shutdown the cluster
1562 Shutdown the cluster and disconnect all the users
1564 === 9^SPOOF <call> <command>^Do a command as though you are another user
1565 This command is provided so that sysops can set a user's parameters without
1566 me having to write a special 'sysop' version for every user command. It
1567 allows you to pretend that you are doing the command as the user you specify.
1571 SPOOF G1TLH set/name Dirk
1572 SPOOF G1TLH set/qra JO02LQ
1574 === 5^STAT/DB <dbname>^Show the status of a database
1575 Show the internal status of a database descriptor.
1577 Depending on your privilege level you will see more or less information.
1578 This command is unlikely to be of much use to anyone other than a sysop.
1580 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
1581 Show the internal status of the channel object either for the channel that
1582 you are on or else for the callsign that you asked for.
1584 Only the fields that are defined (in perl term) will be displayed.
1586 === 1^STAT/MSG^Show the status of the message system
1587 === 1^STAT/MSG <msgno>^Show the status of a message
1588 This command shows the internal status of a message and includes information
1589 such as to whom it has been forwarded, its size, origin etc etc.
1591 If no message number is given then the status of the message system is
1594 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
1596 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
1598 === 5^STAT/USER [<callsign>]^Show the full status of a user
1599 Shows the full contents of a user record including all the secret flags
1602 Only the fields that are defined (in perl term) will be displayed.
1604 === 0^SYSOP^Regain your privileges if you login remotely
1605 The system automatically reduces your privilege level to that of a
1606 normal user if you login in remotely. This command allows you to
1607 regain your normal privilege level. It uses the normal system: five
1608 numbers are returned that are indexes into the character array that is
1609 your assigned password (see SET/PASSWORD). The indexes start from
1612 You are expected to return a string which contains the characters
1613 required in the correct order. You may intersperse those characters
1614 with others to obscure your reply for any watchers. For example (and
1615 these values are for explanation :-):
1617 password = 012345678901234567890123456789
1621 aa2bbbb0ccc5ddd7xxx3n
1625 They will all match. If there is no password you will still be offered
1626 numbers but nothing will happen when you input a string. Any match is
1629 === 0^TALK <call> [<text>]^Send a text message to another station
1630 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
1631 Send a short message to any other station that is visible on the cluster
1632 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
1633 command, they don't have to be connected locally.
1635 The second form of TALK is used when other cluster nodes are connected
1636 with restricted information. This usually means that they don't send
1637 the user information usually associated with logging on and off the cluster.
1639 If you know that G3JNB is likely to be present on GB7TLH, but you can only
1640 see GB7TLH in the SH/C list but with no users, then you would use the
1641 second form of the talk message.
1643 If you want to have a ragchew with someone you can leave the text message
1644 out and the system will go into 'Talk' mode. What this means is that a
1645 short message is sent to the recipient telling them that you are in a
1646 'Talking' frame of mind and then you just type - everything you send will
1647 go to the station that you asked for.
1649 All the usual announcements, spots and so on will still come out on your
1652 If you want to do something (such as send a spot) you preceed the normal
1653 command with a '/' character, eg:-
1655 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
1658 To leave talk mode type:
1662 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
1663 Type out the contents of a file in a filearea. So, for example, in
1664 filearea 'bulletins' you want to look at file 'arld051' you would
1666 TYPE bulletins/arld051
1668 See also SHOW/FILES to see what fileareas are available and a
1671 === 0^WHO^Show who is physically connected
1672 This is a quick listing that shows which callsigns are connected and
1673 what sort of connection they have
1675 === 0^WX <text>^Send a weather message to local users
1676 === 0^WX FULL <text>^Send a weather message to all cluster users
1677 === 5^WX SYSOP <text>^Send a weather message to other clusters only
1678 Weather messages can sometimes be useful if you are experiencing an extreme
1679 that may indicate enhanced conditions