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 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
59 Create an 'accept this spot' line for a filter.
61 An accept filter line means that if the spot matches this filter it is
62 passed onto the user. See HELP 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 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
68 on <range> same as 'freq'
69 call <prefixes> eg: G,PA,HB9
70 info <string> eg: iota or qsl
72 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
81 For frequencies, you can use any of the band names defined in
82 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
83 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
84 this is more efficient than saying simply: freq HF (but don't get
85 too hung up about that)
90 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
92 You can use the tag 'all' to accept everything, eg:
96 but this probably for advanced users...
98 === 8^ACCEPT/route <call> [0-9] <pattern>^Set an 'accept' filter line for routing
99 Create an 'accept this routing PC Protocol' line for a filter.
101 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
102 it is passed thru that interface. See HELP FILTERING for more info. Please read this
103 to understand how filters work - it will save a lot of grief later on.
105 You can use any of the following things in this line:-
107 call <prefixes> the callsign of the thingy
108 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
111 origin <prefixes> really the interface it came in on
112 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
114 origin_zone <numbers>
118 acc/route gb7djk call_zone 61,38 (send only UK+EIRE nodes)
119 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
121 You can use the tag 'all' to accept everything eg:
126 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
127 This version allows a sysop to set a filter for a callsign as well as the
128 default for nodes and users eg:-
130 accept/spot db0sue-7 1 by_zone 14,15,16
131 accept/spot node_default all
132 set/hops node_default 10
134 accept/spot user_default by G,M,2
136 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
137 It is unlikely that you will want to do this, but if you do then you can
138 filter on the following fields:-
140 by <prefixes> eg: G,M,2
142 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
144 origin_zone <numbers>
150 There are no examples because WCY Broadcasts only come from one place and
151 you either want them or not (see UNSET/WCY if you don't want them).
153 This command is really provided for future use.
155 See HELP FILTER for information.
157 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
158 This version allows a sysop to set a filter for a callsign as well as the
159 default for nodes and users eg:-
161 accept/wcy node_default all
162 set/hops node_default 10
164 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
165 It is unlikely that you will want to do this, but if you do then you can
166 filter on the following fields:-
168 by <prefixes> eg: G,M,2
170 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
172 origin_zone <numbers>
182 is probably the only useful thing to do (which will only show WWV broadcasts
183 by stations in the US).
185 See HELP FILTER for information.
187 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
188 This version allows a sysop to set a filter for a callsign as well as the
189 default for nodes and users eg:-
191 accept/wwv db0sue-7 1 by_zone 4
192 accept/wwv node_default all
193 set/hops node_default 10
195 accept/wwv user_default by W,K
197 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
198 <text> is the text of the announcement you wish to broadcast
200 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
201 This will send your announcement cluster wide
203 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
205 === 0^APROPOS <string>^Search help database for <string>
206 Search the help database for <string> (it isn't case sensitive), and print
207 the names of all the commands that may be relevant.
209 === 0^BYE^Exit from the cluster
210 This will disconnect you from the cluster
212 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
213 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
214 When you send messages the fact that you have forwarded it to another node
215 is remembered so that it isn't sent again. When you have a new partner
216 node and you add their callsign to your /spider/msg/forward.pl file, all
217 outstanding non-private messages will be forwarded to them. This may well
218 be ALL the non-private messages. You can prevent this by using these
222 catchup GB7DJK 300 301 302 303 500-510
224 and to undo what you have just done:-
227 uncatchup GB7DJK 300 301 302 303 500-510
229 which will arrange for them to be forward candidates again.
231 Order is not important.
233 === 0^CLEAR/SPOTS [1|all]^Clear a spot filter line
234 This command allows you to clear (remove) a line in a spot filter or to
235 remove the whole filter.
237 If you have a filter:-
240 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
246 you will be left with:-
248 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
254 the filter will be completely removed.
256 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
257 Start a connection process that will culminate in a new connection to the
258 DX cluster <callsign>. This process creates a new 'client' process which will
259 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
260 necessary to traverse the network(s) to logon to the cluster <callsign>.
262 === 0^DBAVAIL^Show a list of all the Databases in the system
263 Title says it all really, this command lists all the databases defined
264 in the system. It is also aliased to SHOW/COMMAND.
266 === 9^DBCREATE <name>^Create a database entry
267 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
268 === 9^DBCREATE <name> remote <node>^Create a remote database entry
269 DBCREATE allows you to define a database in the system. It doesn't actually
270 create anything, just defines it.
272 The databases that are created are simple DB_File hash databases, they are
273 therefore already 'indexed'.
275 You can define a local database with the first form of the command eg:
279 You can also chain databases with the addition of the 'chain' keyword.
280 This will search each database one after the other. A typical example
283 DBCREATE sdx_qsl chain sql_ad
285 No checking is done to see if the any of the chained databases exist, in
286 fact it is usually better to do the above staement first then do each of
287 the chained databases.
289 Databases can exist offsite. To define a database that lives on another
292 DBCREATE buckmaster remote gb7dxc
294 Remote databases cannot be chained; however, the last database in a
295 a chain can be a remote database eg:
297 DBCREATE qsl chain gb7dxc
299 To see what databases have been defined do:
301 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
303 It would be normal for you to add an entry into your local Aliases file
304 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
305 need to add a line like:-
310 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
319 to work as they may be used to.
321 See DBIMPORT for the importing of existing AK1A format data to databases.
322 See DBSHOW for generic database enquiry
324 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
325 If you want to import or update data in bulk to a database you can use
326 this command. It will either create or update entries into an existing
327 database. For example:-
329 DBIMPORT oblast /tmp/OBLAST.FUL
331 will import the standard OBLAST database that comes with AK1A into the
332 oblast database held locally.
334 === 9^DBREMOVE <dbname>^Delete a database
335 DBREMOVE will completely remove a database entry and also delete any data
336 file that is associated with it.
338 There is no warning, no comeback, no safety net.
344 will remove the oblast database from the system and it will also remove
345 the associated datafile.
349 There is no warning, no comeback, no safety net.
351 You have been warned.
353 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
354 This is the generic user interface to the database to the database system.
355 It is expected that the sysop will add an entry to the local Aliases file
356 so that users can use the more familiar AK1A style of enquiry such as:
360 but if he hasn't and the database really does exist (use DBAVAIL or
361 SHOW/COMMAND to find out) you can do the same thing with:
365 === 9^DEBUG^Set the cluster program into debug mode
366 Executing this command will only have an effect if you are running the cluster
371 It will interrupt the cluster just after the debug command has finished.
373 === 0^DIRECTORY^List messages
374 === 0^DIRECTORY ALL^List all messages
375 === 0^DIRECTORY OWN^List your own messages
376 === 0^DIRECTORY NEW^List all new messages
377 === 0^DIRECTORY TO <call>^List all messages to <call>
378 === 0^DIRECTORY FROM <call>^List all messages from <call>
379 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
380 === 0^DIRECTORY <nn>^List last <nn> messages
381 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
382 List the messages in the messages directory.
384 If there is a 'p' one space after the message number then it is a
385 personal message. If there is a '-' between the message number and the
386 'p' then this indicates that the message has been read.
388 You can use shell escape characters such as '*' and '?' in the <call>
391 You can combine some of the various directory commands together eg:-
395 DIR SUBJECT IOTA 200-250
397 You can abbreviate all the commands to one letter and use ak1a syntax:-
403 Sysops can see all users' messages.
405 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
406 Disconnect any <call> connected locally
408 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
409 This is how you send a DX Spot to other users. You can, in fact, now
410 enter the <freq> and the <call> either way round.
416 will all give the same result. You can add some remarks to the end
417 of the command and they will be added to the spot.
419 DX FR0G 144600 this is a test
421 You can credit someone else by saying:-
423 DX by G1TLH FR0G 144.600 he isn't on the cluster
425 The <freq> is compared against the available bands set up in the
426 cluster. See SHOW/BANDS for more information.
428 === 9^EXPORT <msgno> <filename>^Export a message to a file
429 Export a message to a file. This command can only be executed on a local
430 console with a fully privileged user. The file produced will be in a form
431 ready to be imported back into the cluster by placing it in the import
432 directory (/spider/msg/import).
434 This command cannot overwrite an existing file. This is to provide some
435 measure of security. Any files written will owned by the same user as the
436 main cluster, otherwise you can put the new files anywhere the cluster can
437 access. For example:-
441 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
442 Export the users database to a file in ascii format. If no filename
443 is given then it will export the file to /spider/data/user_asc.
445 If the file already exists it will be renamed to <filename>.o. In fact
446 up to 5 generations of the file can be kept each one with an extra 'o' on the
449 BE WARNED: this will write to any file you have write access to. No check is
450 made on the filename (if any) that you specify.
452 === 0^FILTERING...^Filtering things in DXSpider
453 There are a number of things you can filter in the DXSpider system. They
454 all use the same general mechanism.
456 In general terms you can create a 'reject' or an 'accept' filter which
457 can have up to 10 lines in it. You do this using, for example:-
462 where ..... are the specific commands for that type of filter. There
463 are filters for spots, wwv, announce, wcy and (for sysops)
464 connects. See each different accept or reject command reference for
467 There is also a command to clear out one or more lines in a filter and
468 one to show you what you have set. They are:-
477 There is clear/xxxx command for each type of filter.
479 For now we are going to use spots for the examples, but you can apply
480 the principles to all types of filter.
482 There are two main types of filter 'accept' or 'reject'; which you use
483 depends entirely on how you look at the world and what is least
484 writing to achieve what you want. Each filter has 10 lines (of any
485 length) which are tried in order. If a line matches then the action
486 you have specified is taken (ie reject means ignore it and accept
489 The important thing to remember is that if you specify a 'reject'
490 filter (all the lines in it say 'reject/spots' (for instance) then if
491 a spot comes in that doesn't match any of the lines then you will get
492 it BUT if you specify an 'accept' filter then any spots that don't
493 match are dumped. For example if I have a one line accept filter:-
495 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
497 then automatically you will ONLY get VHF spots from or to CQ zones 14
498 15 and 16. If you set a reject filter like:
500 reject/spots on hf/cw
502 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
503 and will work it even on CW then you could say:-
505 reject/spots on hf/cw and not info iota
507 But in that case you might only be interested in iota and say:-
509 accept/spots not on hf/cw or info iota
511 which is exactly the same. You should choose one or the other until
512 you are confortable with the way it works. Yes, you can mix them
513 (actually you can have an accept AND a reject on the same line) but
514 don't try this at home until you can analyse the results that you get
515 without ringing up the sysop for help.
517 You can arrange your filter lines into logical units, either for your
518 own understanding or simply convenience. I have one set frequently:-
520 reject/spots 1 on hf/cw
521 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
523 What this does is to ignore all HF CW spots (being a class B I can't
524 read any CW and couldn't possibly be interested in HF :-) and also
525 rejects any spots on VHF which don't either originate or spot someone
528 This is an exmaple where you would use the line number (1 and 2 in
529 this case), if you leave the digit out, the system assumes '1'. Digits
530 '0'-'9' are available.
532 You can leave the word 'and' out if you want, it is implied. You can
533 use any number of brackets to make the 'expression' as you want
534 it. There are things called precedence rules working here which mean
535 that you will NEED brackets in a situation like line 2 because,
536 without it, will assume:-
538 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
540 annoying, but that is the way it is. If you use OR - use
541 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
544 If you want to alter your filter you can just redefine one or more
545 lines of it or clear out one line. For example:-
547 reject/spots 1 on hf/ssb
553 To remove the filter in its entirty:-
559 Once you are happy with the results you get, you may like to experiment.
561 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
562 can be written with a mixed filter, eg:
566 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
568 each filter slot actually has a 'reject' slot and an 'accept'
569 slot. The reject slot is executed BEFORE the accept slot.
571 It was mentioned earlier that after a reject test that doesn't match,
572 the default for following tests is 'accept', the reverse is true for
573 'accept'. In the example what happens is that the reject is executed
574 first, any non hf/cw spot is passed to the accept line, which lets
575 thru everything else on HF.
577 The next filter line lets through just VHF/UHF spots from EU.
579 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
580 This command sends all the latitude and longitude information that your
581 cluster is holding against callsigns. One advantage of recieving this
582 information is that more locator information is held by you. This
583 means that more locators are given on the DX line assuming you have
584 SET/DXGRID enabled. This could be a LOT of information though, so
585 it is not recommended on slow links.
587 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
588 This command sends out any information held in the user file which can
589 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
590 and Homenode. PC41s are only sent for the information that is available.
592 === 0^HELP^The HELP Command
593 HELP is available for a number of commands. The syntax is:-
597 Where <cmd> is the name of the command you want help on.
599 All commands can be abbreviated, so SHOW/DX can be abbreviated
600 to SH/DX, ANNOUNCE can be shortened to AN and so on.
602 Look at the APROPOS <string> command which will search the help database
603 for the <string> you specify and give you a list of likely commands
604 to look at with HELP.
606 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
607 This command attempts to re-initialise a link to a (usually) AK1A node
608 that has got confused, usually by a protocol loop of some kind. It may
609 work - but you usually will be better off simply disconnecting it (or
610 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
613 Best of luck - you will need it.
615 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
616 Delete a message from the local system. You will only be able to
617 delete messages that you have originated or been sent (unless you are
620 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
621 Delete a message (usually a 'bulletin') from the whole cluster system.
623 This uses the subject field, so any messages that have exactly the
624 same subject will be deleted. Beware!
626 === 0^LINKS^Show which nodes is physically connected
627 This is a quick listing that shows which links are connected and
628 some information about them. See WHO for a list of all connections.
630 === 9^LOAD/ALIASES^Reload the command alias table
631 Reload the /spider/cmd/Aliases file after you have editted it. You
632 will need to do this if you change this file whilst the cluster is
633 running in order for the changes to take effect.
635 === 9^LOAD/BANDS^Reload the band limits table
636 Reload the /spider/data/bands.pl file if you have changed it manually whilst
637 the cluster is running.
639 === 9^LOAD/BADMSG^Reload the bad msg table
640 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
641 the cluster is running. This table contains a number of perl regular
642 expressions which are searched for in the fields targetted of each message.
643 If any of them match then that message is immediately deleted on receipt.
645 === 9^LOAD/BADWORDS^Reload the bad words table
646 Reload the /spider/data/badwords file if you have changed it manually whilst
647 the cluster is running. This file contains a list of words which, if found
648 on certain text portions of PC protocol, will cause those protocol frames
649 to be rejected. It will all put out a message if any of these words are
650 used on the announce, dx and talk commands. The words can be one or
651 more on a line, lines starting with '#' are ignored.
653 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
654 Normally, if you change a command file in the cmd or local_cmd tree it
655 will automatially be picked up by the cluster program. Sometimes it
656 can get confused if you are doing a lot of moving commands about or
657 delete a command in the local_cmd tree and want to use the normal one
658 again. Execute this command to reset everything back to the state it
659 was just after a cluster restart.
661 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
662 Reload the /spider/msg/forward.pl file if you have changed it
663 manually whilst the cluster is running.
665 === 9^LOAD/MESSAGES^Reload the system messages file
666 If you change the /spider/perl/Messages file (usually whilst
667 fiddling/writing new commands) you can have them take effect during a
668 cluster session by executing this command. You need to do this if get
671 unknown message 'xxxx' in lang 'en'
673 === 9^LOAD/PREFIXES^Reload the prefix table
674 Reload the /spider/data/prefix_data.pl file if you have changed it
675 manually whilst the cluster is running.
677 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
678 MERGE allows you to bring your spot and wwv database up to date. By default
679 it will request the last 10 spots and 5 WWVs from the node you select. The
680 node must be connected locally.
682 You can request any number of spots or wwv and although they will be appended
683 to your databases they will not duplicate any that have recently been added
684 (the last 2 days for spots and last month for WWV data).
686 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
687 Alter message parameters like To, From, Subject, whether private or bulletin
688 or return receipt (RR) is required or whether to keep this message from timing
691 MSG TO <msgno> <call> - change TO callsign to <call>
692 MSG FRom <msgno> <call> - change FROM callsign to <call>
693 MSG PRrivate <msgno> - set private flag
694 MSG NOPRrivate <msgno> - unset private flag
695 MSG RR <msgno> - set RR flag
696 MSG NORR <msgno> - unset RR flag
697 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
698 MSG NOKEep <msgno> - unset the keep flag
699 MSG SUbject <msgno> <new> - change the subject to <new>
700 MSG WAittime <msgno> - remove any waitting time for this message
701 MSG NOREad <msgno> - mark message as unread
702 MSG REad <msgno> - mark message as read
703 MSG QUeue - queue any outstanding bulletins
704 MSG QUeue 1 - queue any outstanding private messages
706 You can look at the status of a message by using:-
710 This will display more information on the message than DIR does.
712 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
713 Send some arbitrary text to a locally connected callsign. No
714 processing is done on the text. This command allows you to send PC
715 Protocol to unstick things if problems arise (messages get stuck
718 pc gb7djk PC33^GB7TLH^GB7DJK^400^
720 pc G1TLH Try doing that properly!!!
722 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
723 You can get rid of any message to or originating from your callsign using
724 this command. You can remove more than one message at a time.
726 === 5^KILL <from>-<to>^Remove a range of messages from the system
727 === 5^KILL FROM <call>^Remove all messages from a callsign
728 === 5^KILL TO <call>^Remove all messages to a callsign
729 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
730 Remove this message from the entire cluster system as well as your node.
733 As a sysop you can kill any message on the system.
735 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
736 Send any text you like to the callsign requested. This is used mainly to send
737 PC protocol to connected nodes either for testing or to unstick things.
739 You can also use in the same way as a talk command to a connected user but
740 without any processing, added of "from <blah> to <blah" or whatever.
742 === 1^PING <node call>^Check the link quality between nodes
743 This command allows you to send a frame to another cluster node on
744 the network and get a return frame. The time it takes to do this
745 is a good indication of the quality of the link. The actual time
746 it takes is output to the console in seconds.
747 Any visible cluster node can be PINGed.
749 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
750 This command allows you to send nearly any command to another DX Cluster
751 node that is connected to the system.
753 Whether you get any output is dependant on a) whether the other system knows
754 that the node callsign of this cluster is in fact a node b) whether the
755 other system is allowing RCMDs from this node and c) whether you have
756 permission to send this command at all.
758 === 0^READ^Read the next unread personal message addressed to you
759 === 0^READ <msgno>^Read the specified message
760 You can read any messages that are sent as 'non-personal' and also any
761 message either sent by or sent to your callsign.
764 As a sysop you may read any message on the system
766 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
767 Create an 'reject this announce' line for a filter.
769 A reject filter line means that if the announce matches this filter it is
770 passed onto the user. See HELP FILTERING for more info. Please read this
771 to understand how filters work - it will save a lot of grief later on.
773 You can use any of the following things in this line:-
775 info <string> eg: iota or qsl
776 by <prefixes> eg: G,M,2
778 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
780 origin_zone <numbers>
785 wx 1 filter WX announces
786 dest <prefixes> eg: 6MUK,WDX (distros)
790 rej/ann by_zone 14,15,16 and not by G,M,2
792 You can use the tag 'all' to reject everything eg:
796 but this probably for advanced users...
798 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
799 This version allows a sysop to set a filter for a callsign as well as the
800 default for nodes and users eg:-
803 reject/ann input node_default by G,M,2
804 reject/ann user_default by G,M,2
806 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
807 Create a 'reject this spot' line for a filter.
809 A reject filter line means that if the spot matches this filter it is
810 dumped (not passed on). See HELP FILTERING for more info. Please read this
811 to understand how filters work - it will save a lot of grief later on.
813 You can use any of the following things in this line:-
815 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
816 on <range> same as 'freq'
817 call <prefixes> eg: G,PA,HB9
818 info <string> eg: iota or qsl
820 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
829 For frequencies, you can use any of the band names defined in
830 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
831 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
832 this is more efficient than saying simply: on HF (but don't get
833 too hung up about that)
838 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
840 You can use the tag 'all' to reject everything eg:
844 but this probably for advanced users...
846 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
847 Create an 'reject this routing PC Protocol' line for a filter.
849 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
850 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
851 read this to understand how filters work - it will save a lot of grief later on.
853 You can use any of the following things in this line:-
855 call <prefixes> the callsign of the thingy
856 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
859 origin <prefixes> really the interface it came in on
860 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
862 origin_zone <numbers>
866 rej/route gb7djk call_zone 61,38 (everything except UK+EIRE nodes)
868 You can use the tag 'all' to reject everything eg:
870 rej/route all (equiv to [very] restricted mode)
872 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
873 This version allows a sysop to set a filter for a callsign as well as the
874 default for nodes and users eg:-
876 reject/spot db0sue-7 1 by_zone 14,15,16
877 reject/spot node_default all
878 set/hops node_default 10
880 reject/spot user_default by G,M,2
882 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
883 It is unlikely that you will want to do this, but if you do then you can
884 filter on the following fields:-
886 by <prefixes> eg: G,M,2
888 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
890 origin_zone <numbers>
896 There are no examples because WCY Broadcasts only come from one place and
897 you either want them or not (see UNSET/WCY if you don't want them).
899 This command is really provided for future use.
901 See HELP FILTER for information.
903 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
904 This version allows a sysop to set a filter for a callsign as well as the
905 default for nodes and users eg:-
907 reject/wcy gb7djk all
909 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
910 It is unlikely that you will want to do this, but if you do then you can
911 filter on the following fields:-
913 by <prefixes> eg: G,M,2
915 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
917 origin_zone <numbers>
925 reject/wwv by_zone 14,15,16
927 is probably the only useful thing to do (which will only show WWV broadcasts
928 by stations in the US).
930 See HELP FILTER for information.
932 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
933 This version allows a sysop to set a filter for a callsign as well as the
934 default for nodes and users eg:-
936 reject/wwv db0sue-7 1 by_zone 4
937 reject/wwv node_default all
939 reject/wwv user_default by W
941 === 0^REPLY^Reply (privately) to the last message that you have read
942 === 0^REPLY <msgno>^Reply (privately) to the specified message
943 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
944 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
945 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
946 You can reply to a message and the subject will automatically have
947 "Re:" inserted in front of it, if it isn't already present.
949 You can also use all the extra qualifiers such as RR, PRIVATE,
950 NOPRIVATE, B that you can use with the SEND command (see SEND
953 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
954 === 0^SEND RR <call>^Send a message and ask for a read receipt
955 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
956 === 0^SEND PRIVATE <call>^Send a personal message
957 === 0^SEND NOPRIVATE <call>^Send a message to all stations
958 All the SEND commands will create a message which will be sent either to
959 an individual callsign or to one of the 'bulletin' addresses.
961 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
962 it will mark the message as personal and send it to the cluster node that
963 that callsign is connected to.
965 You can have more than one callsign in all of the SEND commands.
967 You can have multiple qualifiers so that you can have for example:-
969 SEND RR COPY 123 PRIVATE G1TLH G0RDI
971 which should send a copy of message 123 to G1TLH and G0RDI and you will
972 receive a read receipt when they have read the message.
974 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
975 SP is an alias for SEND PRIVATE
977 === 0^SET/ADDRESS <your address>^Record your postal address
979 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
980 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
982 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
984 === 8^SET/BADDX <call>..^Stop words we do not wish to see in the callsign field
985 of a dx spot being propagated
986 === 8^UNSET/BADDX <call>..^Allow a word to be seen again in a DX spot
987 Setting a word as 'baddx' will prevent spots with that word in the
988 callsign field of a DX spot from going any further. They will not be
989 displayed and they will not be sent onto other nodes.
991 The word must be wriiten in full, no wild cards are allowed eg:-
993 set/baddx FORSALE VIDEO FR0G
995 To allow a word again, use the following command ...
999 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1000 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1001 Setting a callsign as a 'badnode' will prevent spots from that node
1002 going any further. They will not be displayed and they will not be
1003 sent onto other nodes.
1005 The call must be a full eg:-
1009 will stop anything from K1TTT. If you want SSIDs as well then you must
1010 enter them specifically.
1014 will allow spots from him again.
1016 Use with extreme care. This command may well be superceeded by FILTERing.
1018 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1019 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1020 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1021 going any further. They will not be displayed and they will not be
1022 sent onto other nodes.
1024 The call must be written in full, no wild cards are allowed eg:-
1026 set/badspotter VE2STN
1028 will stop anything from VE2STN. If you want SSIDs as well then you must
1029 enter them specifically.
1031 unset/badspotter VE2STN
1033 will allow spots from him again.
1035 Use with extreme care. This command may well be superceded by FILTERing.
1037 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1038 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1040 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1042 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1044 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1045 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1046 You can choose to log several different levels. The levels are
1054 You can show what levels you are logging with SHOW/DEBUG
1056 === 0^SET/DX^Allow DX messages to come out on your terminal
1057 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1059 === 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements
1060 === 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements
1061 A standard feature which is enabled in version 1.43 and above is
1062 that if the spotter's grid square is known it is output on the end
1063 of a DX announcement (there is just enough room). Some user programs
1064 cannot cope with this. You can use this command to reset (or set)
1067 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1069 === 0^SET/ECHO^Make the cluster echo your input
1070 === 0^UNSET/ECHO^Stop the cluster echoing your input
1071 If you are connected via a telnet session, different implimentations
1072 of telnet handle echo differently depending on whether you are
1073 connected via port 23 or some other port. You can use this command
1074 to change the setting appropriately.
1076 The setting is stored in your user profile.
1078 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1080 === 0^SET/HERE^Tell the system you are present at your terminal
1081 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1083 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1084 Tell the cluster system where you normally connect to. Any Messages sent
1085 to you will normally find their way there should you not be connected.
1089 === 8^SET/HOPS <call> ann|spots|wwv|wcy <n>^Set hop count
1090 Set the hop count for a particular type of broadcast for a node.
1092 This command allows you to set up special hop counts for a node
1093 for currently: announce, spots, wwv and wcy broadcasts.
1096 set/hops gb7djk ann 10
1097 set/hops gb7mbc spots 20
1099 Set SHOW/HOPS for information on what is already set. This command
1100 creates a filter and works in conjunction with the filter system.
1102 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1103 Connect a node to your system in such a way that you are a full protocol
1104 member of its network and can see all spots on it, but nothing either leaks
1105 out from it nor goes back into from the rest of the nodes connected to you.
1107 You can potentially connect several nodes in this way.
1109 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1110 Remove isolation from a node - SET/ISOLATE
1112 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1113 You can select the language that you want the cluster to use. Currently
1114 the languages available are en (english) and nl (dutch).
1116 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1117 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1118 In order to get accurate headings and such like you must tell the system
1119 what your latitude and longitude is. If you have not yet done a SET/QRA
1120 then this command will set your QRA locator for you. For example:-
1121 SET/LOCATION 52 22 N 0 57 E
1123 === 0^SET/LOGININFO^Inform when a station logs in locally
1124 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1126 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1127 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1129 === 0^SET/NAME <your name>^Set your name
1130 Tell the system what your name is eg:-
1133 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1134 Tell the system that the call(s) are to be treated as AK1A cluster and
1135 fed PC Protocol rather normal user commands.
1137 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
1138 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1139 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1140 counter which is decremented on every outgoing ping and then reset to
1141 the 'obscount' value on every incoming ping. The default value of this
1144 What this means is that a neighbouring node will be pinged twice at
1145 (default) 300 second intervals and if no reply has been heard just before
1146 what would be the third attempt, that node is disconnected.
1148 If a ping is heard then the obscount is reset to the full value. Using
1149 default values, if a node has not responded to a ping within 15 minutes,
1152 You can set this parameter between 1 and 9.
1154 It is STRONGLY recommended that you don't change the default.
1156 === 0^SET/PAGE <lines per page>^Set the lines per page
1157 Tell the system how many lines you wish on a page when the number of line
1158 of output from a command is more than this. The default is 20. Setting it
1159 explicitly to 0 will disable paging.
1163 The setting is stored in your user profile.
1165 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1166 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1167 in order to determine the rolling quality of the link and, in future, to
1168 affect routing decisions. The default interval is 300 secs or 5 minutes.
1170 You can use this command to set a different interval. Please don't.
1172 But if you do the value you enter is treated as minutes up 30 and seconds
1173 for numbers greater than that.
1175 This is used also to help determine when a link is down at the far end
1176 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1177 for more information.
1179 If you must change it (and it may be useful for internet connected nodes
1180 on dynamic IP addresses that go away after a set time of usage) the time
1181 can be specified as:-
1183 5 which if less than 30 is converted to minutes otherwise is
1184 taken as the no of seconds between pings.
1189 Please be aware that this causes traffic to occur on the link, setting
1190 this value too low may annoy your neighbours beyond the point of
1193 You can switch this off by setting it to 0.
1195 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1196 Set the privilege level on a callsign. The privilege levels that pertain
1197 to commands are as default:-
1199 1 - allow remote nodes normal user RCMDs
1200 5 - various privileged commands (including shutdown, but not disc-
1201 connect), the normal level for another node.
1202 8 - more privileged commands (including disconnect)
1203 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1205 If you are a sysop and you come in as a normal user on a remote connection
1206 your privilege will automatically be set to 0.
1208 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1209 The password for a user can only be set by a full sysop. The string
1210 can contain any characters but any spaces are removed (you can type in
1211 spaces - but they won't appear in the password). You can see the
1212 result with STAT/USER.
1214 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1215 Tell the system that the call(s) are to be treated as DXSpider node and
1216 fed new style DX Protocol rather normal user commands.
1218 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
1219 === 0^SET/QRA <locator>^Set your QRA locator
1220 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1221 done a SET/LOCATION then your latitude and longitude will be set roughly
1222 correctly (assuming your locator is correct ;-). For example:-
1225 === 0^SET/QTH <your qth>^Set your QTH
1226 Tell the system where you are. For example:-
1227 SET/QTH East Dereham, Norfolk
1229 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1230 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1232 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1233 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1235 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1236 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1238 === 0^SET/WX^Allow WX messages to come out on your terminal
1239 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1241 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1242 Display all the bad dx callsigns in the system, see SET/BADDX
1243 for more information.
1245 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1246 Display all the bad node callsigns in the system, see SET/BADNODE
1247 for more information.
1249 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1250 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1251 for more information.
1253 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1254 This command allows you to see all the users that can be seen
1255 and the nodes to which they are connected.
1257 This command is normally abbreviated to: sh/c
1259 BE WARNED: the list that is returned can be VERY long
1261 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1262 Show all the nodes connected to this node.
1264 === 1^SHOW/CONNECT^Show all the active connections
1265 This command shows information on all the active connections known to
1266 the node. This command gives slightly more information than WHO.
1268 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1269 This is very nearly the same as SHOW/TIME, the only difference the format
1270 of the date string if no arguments are given.
1272 If no prefixes or callsigns are given then this command returns the local
1273 time and UTC as the computer has it right now. If you give some prefixes
1274 then it will show UTC and UTC + the local offset (not including DST) at
1275 the prefixes or callsigns that you specify.
1277 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1279 === 0^SHOW/DX^Interrogate the spot database
1280 If you just type SHOW/DX you will get the last so many spots
1281 (sysop configurable, but usually 10).
1283 In addition you can add any number of these commands in very nearly
1284 any order to the basic SHOW/DX command, they are:-
1286 on <band> - eg 160m 20m 2m 23cm 6mm
1287 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1289 <number> - the number of spots you want
1290 <from>-<to> - <from> spot no <to> spot no in the selected list
1292 <prefix> - for a spotted callsign beginning with <prefix>
1293 *<suffix> - for a spotted callsign ending in <suffix>
1294 *<string>* - for a spotted callsign containing <string>
1296 day <number> - starting <number> days ago
1297 day <from>-<to> - <from> days <to> days ago
1299 info <text> - any spots containing <text> in the info or remarks
1301 by <call> - any spots spotted by <call> (spotter <call> is the
1304 qsl - this automatically looks for any qsl info on the call
1305 held in the spot database.
1307 iota [<iota>] - If the iota island number is missing it will look for
1308 the string iota and anything which looks like an iota
1309 island number. If you specify then it will look for
1312 qra [<locator>] - this will look for the specific locator if you specify
1313 one or else anything that looks like a locator.
1318 SH/DX on 20m info iota
1319 SH/DX 9a on vhf day 30
1325 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1326 This command takes the <prefix> (which can be a full or partial
1327 callsign if desired), looks up which internal country number it is
1328 and then displays all the spots as per SH/DX for that country.
1330 The options for SHOW/DX also apply to this command.
1334 SH/DXCC W on 20m info iota
1336 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1337 SHOW/FILES on its own will show you a list of the various fileareas
1338 available on the system. To see the contents of a particular file
1341 where <filearea> is the name of the filearea you want to see the
1344 You can also use shell globbing characters like '*' and '?' in a
1345 string to see a selection of files in a filearea eg:-
1346 SH/FILES bulletins arld*
1348 See also TYPE - to see the contents of a file.
1350 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1351 Show the contents of all the filters that are set. This command displays
1352 all the filters set - for all the various categories.
1354 === 8^SHOW/HOPS <call> [ann|spots|wcy|wwv]^Show the hop counts for a node
1355 This command shows the hop counts set up for a node. You can specify
1356 which category you want to see. If you leave the category out then
1357 all the categories will be listed.
1359 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1361 === 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
1363 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
1364 This command outputs a short section of the system log. On its own
1365 it will output a general logfile. With the optional callsign it will
1366 show output from the log associated with that callsign.
1368 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
1369 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1370 together with the azimuth and elevation of the sun currently at those
1373 If you don't specify any prefixes or callsigns, it will show the times for
1374 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1375 together with the current azimuth and elevation.
1377 In addition, it will show the gain or loss dB relative to the nominal
1378 distance of 385,000Km due to the ellipsoidal nature of the orbit.
1380 If all else fails it will show the Moonrise and set times for the node
1381 that you are connected to.
1388 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1389 This command allow you to estimate the likelihood of you contacting
1390 a station with the prefix you have specified. The output assumes a modest
1391 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1393 The result predicts the most likely operating frequencies and signal
1394 levels for high frequency (shortwave) radio propagation paths on
1395 specified days of the year and hours of the day. It is most useful for
1396 paths between 250 km and 6000 km, but can be used with reduced accuracy
1397 for paths shorter or longer than this.
1399 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1400 used to predict the MUF given the predicted flux, day of the year,
1401 hour of the day and geographic coordinates of the transmitter and
1402 receiver. This routine is reasonably accurate for the purposes here,
1403 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1404 than the programs used by major shortwave broadcasting organizations,
1405 such as the Voice of America.
1407 The command will display some header information detailing its
1408 assumptions, together with the locations, latitude and longitudes and
1409 bearings. It will then show UTC (UT), local time at the other end
1410 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1411 (Zen) and the likely signal strengths. Then for each frequency for which
1412 the system thinks there is a likelihood of a circuit it prints a value.
1414 The value is currently a likely S meter reading based on the conventional
1415 6dB / S point scale. If the value has a '+' appended it means that it is
1416 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1417 there is likely to be much fading and by an 's' that the signal is likely
1420 By default SHOW/MUF will show the next two hours worth of data. You
1421 can specify anything up to 24 hours worth of data by appending the no of
1422 hours required after the prefix. For example:-
1428 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1429 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1430 Location Lat / Long Azim
1431 East Dereham, Norfolk 52 41 N 0 57 E 47
1432 United-States-W 43 0 N 87 54 W 299
1433 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1434 18 23 11.5 -35 mS0+ mS2 S3
1435 19 0 11.2 -41 mS0+ mS2 S3
1437 indicating that you will have weak, fading circuits on top band and
1438 80m but usable signals on 40m (about S3).
1444 will get you the above display, but with the next 24 hours worth of
1450 Gives you an estimate of the long path propagation characterics. It
1451 should be noted that the figures will probably not be very useful, nor
1452 terrible accurate, but it is included for completeness.
1454 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1455 Show the type and version (if connected) of the nodes specified on the
1456 command line. If no callsigns are specified then a sorted list of all
1457 the non-user callsigns known to the system will be displayed.
1459 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1460 This command takes the <callsign> (which can be a full or partial
1461 callsign or a prefix), looks up which internal country number
1462 it is and then displays all the relevant prefixes for that country
1463 together with the internal country no, the CQ and ITU regions.
1467 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1468 Show the name and location where every program module was load from. This
1469 is useful for checking where you think you have loaded a .pm file from.
1471 === 0^SHOW/QRA <locator> [<locator>]^Show distance between locators
1472 === 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
1473 This is a multipurpose command that allows you either to calculate the
1474 distance and bearing between two locators or (if only one locator is
1475 given on the command line) the distance and beraing from your station
1476 to the locator. For example:-
1481 The first example will show the distance and bearing to the locator from
1482 yourself, the second example will calculate the distance and bearing from
1483 the first locator to the second. You can use 4 or 6 character locators.
1485 It is also possible to convert a latitude and longitude to a locator by
1486 using this command with a latitude and longitude as an argument, for
1489 SH/QRA 52 41 N 0 58 E
1491 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
1492 This command queries the QRZ callbook server on the internet
1493 and returns any information available for that callsign. This service
1494 is provided for users of this software by http://www.qrz.com
1496 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
1497 This command allows you to see to which node the callsigns specified are
1498 connected. It is a sort of inverse sh/config.
1502 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1503 Show the tracking data from your location to the satellite of your choice
1504 from now on for the next few hours.
1506 If you use this command without a satellite name it will display a list
1507 of all the satellites known currently to the system.
1509 If you give a name then you can obtain tracking data of all the passes
1510 that start and finish 5 degrees below the horizon. As default it will
1511 give information for the next three hours for every five minute period.
1513 You can alter the number of hours and the step size, within certain
1516 Each pass in a period is separated with a row of '-----' characters
1521 SH/SAT FENGYUN1 12 2
1523 === 0^SHOW/SUN [<prefix>|<callsign>]^Show sun rise and set times
1524 Show the sun rise and set times for a (list of) prefixes or callsigns,
1525 together with the azimuth and elevation of the sun currently at those
1528 If you don't specify any prefixes or callsigns, it will show the times for
1529 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1530 together with the current azimuth and elevation.
1532 If all else fails it will show the sunrise and set times for the node
1533 that you are connected to.
1538 SH/SUN G1TLH K9CW ZS
1540 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
1541 If no prefixes or callsigns are given then this command returns the local
1542 time and UTC as the computer has it right now. If you give some prefixes
1543 then it will show UTC and UTC + the local offset (not including DST) at
1544 the prefixes or callsigns that you specify.
1546 === 0^SHOW/WCY^Show last 10 WCY broadcasts
1547 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
1548 Display the most recent WCY information that has been received by the system
1550 === 0^SHOW/WWV^Show last 10 WWV broadcasts
1551 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
1552 Display the most recent WWV information that has been received by the system
1554 === 5^SHUTDOWN^Shutdown the cluster
1555 Shutdown the cluster and disconnect all the users
1557 === 9^SPOOF <call> <command>^Do a command as though you are another user
1558 This command is provided so that sysops can set a user's parameters without
1559 me having to write a special 'sysop' version for every user command. It
1560 allows you to pretend that you are doing the command as the user you specify.
1564 SPOOF G1TLH set/name Dirk
1565 SPOOF G1TLH set/qra JO02LQ
1567 === 5^STAT/DB <dbname>^Show the status of a database
1568 Show the internal status of a database descriptor.
1570 Depending on your privilege level you will see more or less information.
1571 This command is unlikely to be of much use to anyone other than a sysop.
1573 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
1574 Show the internal status of the channel object either for the channel that
1575 you are on or else for the callsign that you asked for.
1577 Only the fields that are defined (in perl term) will be displayed.
1579 === 1^STAT/MSG^Show the status of the message system
1580 === 1^STAT/MSG <msgno>^Show the status of a message
1581 This command shows the internal status of a message and includes information
1582 such as to whom it has been forwarded, its size, origin etc etc.
1584 If no message number is given then the status of the message system is
1587 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
1589 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
1591 === 5^STAT/USER [<callsign>]^Show the full status of a user
1592 Shows the full contents of a user record including all the secret flags
1595 Only the fields that are defined (in perl term) will be displayed.
1597 === 0^SYSOP^Regain your privileges if you login remotely
1598 The system automatically reduces your privilege level to that of a
1599 normal user if you login in remotely. This command allows you to
1600 regain your normal privilege level. It uses the normal system: five
1601 numbers are returned that are indexes into the character array that is
1602 your assigned password (see SET/PASSWORD). The indexes start from
1605 You are expected to return a string which contains the characters
1606 required in the correct order. You may intersperse those characters
1607 with others to obscure your reply for any watchers. For example (and
1608 these values are for explanation :-):
1610 password = 012345678901234567890123456789
1614 aa2bbbb0ccc5ddd7xxx3n
1618 They will all match. If there is no password you will still be offered
1619 numbers but nothing will happen when you input a string. Any match is
1622 === 0^TALK <call> [<text>]^Send a text message to another station
1623 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
1624 Send a short message to any other station that is visible on the cluster
1625 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
1626 command, they don't have to be connected locally.
1628 The second form of TALK is used when other cluster nodes are connected
1629 with restricted information. This usually means that they don't send
1630 the user information usually associated with logging on and off the cluster.
1632 If you know that G3JNB is likely to be present on GB7TLH, but you can only
1633 see GB7TLH in the SH/C list but with no users, then you would use the
1634 second form of the talk message.
1636 If you want to have a ragchew with someone you can leave the text message
1637 out and the system will go into 'Talk' mode. What this means is that a
1638 short message is sent to the recipient telling them that you are in a
1639 'Talking' frame of mind and then you just type - everything you send will
1640 go to the station that you asked for.
1642 All the usual announcements, spots and so on will still come out on your
1645 If you want to do something (such as send a spot) you preceed the normal
1646 command with a '/' character, eg:-
1648 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
1651 To leave talk mode type:
1655 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
1656 Type out the contents of a file in a filearea. So, for example, in
1657 filearea 'bulletins' you want to look at file 'arld051' you would
1659 TYPE bulletins/arld051
1661 See also SHOW/FILES to see what fileareas are available and a
1664 === 0^WHO^Show who is physically connected
1665 This is a quick listing that shows which callsigns are connected and
1666 what sort of connection they have
1668 === 0^WX <text>^Send a weather message to local users
1669 === 0^WX FULL <text>^Send a weather message to all cluster users
1670 === 5^WX SYSOP <text>^Send a weather message to other clusters only
1671 Weather messages can sometimes be useful if you are experiencing an extreme
1672 that may indicate enhanced conditions