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^Set a filter to accept something
15 Create a filter to accept something
17 There are 2 types of filter, accept and reject. See HELP FILTERING for more
20 === 0^ACCEPT/ANNOUNCE [0-9] <pattern>^Set an 'accept' filter line for announce
21 Create an 'accept this announce' line for a filter.
23 An accept filter line means that if the announce matches this filter it is
24 passed onto the user. See HELP FILTERING for more info. Please read this
25 to understand how filters work - it will save a lot of grief later on.
27 You can use any of the following things in this line:-
29 info <string> eg: iota or qsl
30 by <prefixes> eg: G,M,2
32 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
33 origin_itu <prefixes or numbers> or: G,GM,GW
34 origin_zone <prefixes or numbers>
35 by_dxcc <prefixes or numbers>
36 by_itu <prefixes or numbers>
37 by_zone <prefixes or numbers>
39 wx 1 filter WX announces
40 dest <prefixes> eg: 6MUK,WDX (distros)
45 acc/ann 2 by_zone 14,15,16
46 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
50 You can use the tag 'all' to accept everything eg:
54 but this probably for advanced users...
56 === 8^ACCEPT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
57 This version allows a sysop to set a filter for a callsign as well as the
58 default for nodes and users eg:-
61 accept/ann input node_default by G,M,2
62 accept/ann user_default by G,M,2
64 === 8^ACCEPT/ROUTE <call> [0-9] <pattern>^Set an 'accept' filter line for routing
65 Create an 'accept this routing PC Protocol' line for a filter.
67 An accept filter line means that if a PC16/17/19/21/24/41/50 matches this filter
68 it is passed thru that interface. See HELP FILTERING for more info. Please read this
69 to understand how filters work - it will save a lot of grief later on.
71 You can use any of the following things in this line:-
73 call <prefixes> the callsign of the thingy
74 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
75 call_itu <prefixes or numbers> or: G,GM,GW
76 call_zone <prefixes or numbers>
77 origin <prefixes> really the interface it came in on
78 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
79 origin_itu <prefixes or numbers> or: G,GM,GW
80 origin_zone <prefixes or numbers>
84 acc/route gb7djk call_dxcc 61,38 (send only UK+EIRE nodes)
85 acc/route gb7djk call gb7djk (equiv to SET/ISOLATE)
87 You can use the tag 'all' to accept everything eg:
92 === 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
93 Create an 'accept this spot' line for a filter.
95 An accept filter line means that if the spot matches this filter it is
96 passed onto the user. See HELP FILTERING for more info. Please read this
97 to understand how filters work - it will save a lot of grief later on.
99 You can use any of the following things in this line:-
101 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
102 on <range> same as 'freq'
103 call <prefixes> eg: G,PA,HB9
104 info <string> eg: iota or qsl
106 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
107 call_itu <prefixes or numbers> or: G,GM,GW
108 call_zone <prefixes or numbers>
109 by_dxcc <prefixes or numbers>
110 by_itu <prefixes or numbers>
111 by_zone <prefixes or numbers>
115 For frequencies, you can use any of the band names defined in
116 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
117 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
118 this is more efficient than saying simply: freq HF (but don't get
119 too hung up about that)
124 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
126 You can use the tag 'all' to accept everything, eg:
130 but this probably for advanced users...
133 === 8^ACCEPT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
134 This version allows a sysop to set a filter for a callsign as well as the
135 default for nodes and users eg:-
137 accept/spot db0sue-7 1 by_zone 14,15,16
138 accept/spot node_default all
139 set/hops node_default 10
141 accept/spot user_default by G,M,2
143 === 0^ACCEPT/WCY [0-9] <pattern>^set an 'accept' WCY filter
144 It is unlikely that you will want to do this, but if you do then you can
145 filter on the following fields:-
147 by <prefixes> eg: G,M,2
149 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
150 origin_itu <prefixes or numbers> or: G,GM,GW
151 origin_zone <prefixes or numbers>
152 by_dxcc <prefixes or numbers>
153 by_itu <prefixes or numbers>
154 by_zone <prefixes or numbers>
157 There are no examples because WCY Broadcasts only come from one place and
158 you either want them or not (see UNSET/WCY if you don't want them).
160 This command is really provided for future use.
162 See HELP FILTER for information.
164 === 8^ACCEPT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
165 This version allows a sysop to set a filter for a callsign as well as the
166 default for nodes and users eg:-
168 accept/wcy node_default all
169 set/hops node_default 10
171 === 0^ACCEPT/WWV [0-9] <pattern>^set an 'accept' WWV filter
172 It is unlikely that you will want to do this, but if you do then you can
173 filter on the following fields:-
175 by <prefixes> eg: G,M,2
177 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
178 origin_itu <prefixes or numbers> or: G,GM,GW
179 origin_zone <prefixes or numbers>
180 by_dxcc <prefixes or numbers>
181 by_itu <prefixes or numbers>
182 by_zone <prefixes or numbers>
189 is probably the only useful thing to do (which will only show WWV broadcasts
190 by stations in the US).
192 See HELP FILTER for information.
194 === 8^ACCEPT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
195 This version allows a sysop to set a filter for a callsign as well as the
196 default for nodes and users eg:-
198 accept/wwv db0sue-7 1 by_zone 4
199 accept/wwv node_default all
200 set/hops node_default 10
202 accept/wwv user_default by W,K
204 === 0^ANNOUNCE <text>^Send an announcement to LOCAL users only
205 <text> is the text of the announcement you wish to broadcast
207 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
208 This will send your announcement cluster wide
210 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
212 === 0^APROPOS <string>^Search help database for <string>
213 Search the help database for <string> (it isn't case sensitive), and print
214 the names of all the commands that may be relevant.
216 === 0^BLANK [<string>] [<nn>]^Print nn (default 1) blank lines (or strings)
217 In its basic form this command prints one or more blank lines. However if
218 you pass it a string it will replicate the string for the width of the
219 screen (default 80) and then print that one or more times, so:
223 prints two blank lines
227 prints a row of - characters once.
231 prints 'abcabcabcabcabcabc....'
233 This is really only of any use in a script file and you can print a maximum
236 === 0^BYE^Exit from the cluster
237 This will disconnect you from the cluster
239 === 5^CATCHUP <node call> All|[<msgno> ...]^Mark a message as sent
240 === 5^UNCATCHUP <node call> All|[msgno> ...]^Unmark a message as sent
241 When you send messages the fact that you have forwarded it to another node
242 is remembered so that it isn't sent again. When you have a new partner
243 node and you add their callsign to your /spider/msg/forward.pl file, all
244 outstanding non-private messages will be forwarded to them. This may well
245 be ALL the non-private messages. You can prevent this by using these
249 catchup GB7DJK 300 301 302 303 500-510
251 and to undo what you have just done:-
254 uncatchup GB7DJK 300 301 302 303 500-510
256 which will arrange for them to be forward candidates again.
258 Order is not important.
260 === 0^CLEAR/ANNOUNCE [1|all]^Clear a announce filter line
261 This command allows you to clear (remove) a line in a annouce filter or to
262 remove the whole filter.
264 see CLEAR/SPOTS for a more detailed explanation.
266 === 8^CLEAR/ANNOUNCE [input] <callsign> [0-9|all]^Clear a announce filter line
267 A sysop can clear an input or normal output filter for a user or the
268 node_default or user_default.
270 === 0^CLEAR/ROUTE [1|all]^Clear a route filter line
271 This command allows you to clear (remove) a line in a route filter or to
272 remove the whole filter.
274 see CLEAR/SPOTS for a more detailed explanation.
276 === 8^CLEAR/ROUTE [input] <callsign> [0-9|all]^Clear a route filter line
277 A sysop can clear an input or normal output filter for a user or the
278 node_default or user_default.
280 === 0^CLEAR/SPOTS [0-9|all]^Clear a spot filter line
281 This command allows you to clear (remove) a line in a spot filter or to
282 remove the whole filter.
284 If you have a filter:-
287 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
293 you will be left with:-
295 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
301 the filter will be completely removed.
303 === 8^CLEAR/SPOTS [input] <callsign> [0-9|all]^Clear a spot filter line
304 A sysop can clear an input or normal output filter for a user or the
305 node_default or user_default.
307 === 0^CLEAR/WCY [1|all]^Clear a WCY filter line
308 This command allows you to clear (remove) a line in a WCY filter or to
309 remove the whole filter.
311 see CLEAR/SPOTS for a more detailed explanation.
313 === 8^CLEAR/WCY [input] <callsign> [0-9|all]^Clear a WCY filter line
314 A sysop can clear an input or normal output filter for a user or the
315 node_default or user_default.
317 === 0^CLEAR/WWV [1|all]^Clear a WWV filter line
318 This command allows you to clear (remove) a line in a WWV filter or to
319 remove the whole filter.
321 see CLEAR/SPOTS for a more detailed explanation.
323 === 8^CLEAR/WWV [input] <callsign> [0-9|all]^Clear a WWV filter line
324 A sysop can clear an input or normal output filter for a user or the
325 node_default or user_default.
327 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
328 Start a connection process that will culminate in a new connection to the
329 DX cluster <callsign>. This process creates a new 'client' process which will
330 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
331 necessary to traverse the network(s) to logon to the cluster <callsign>.
333 === 9^DELETE/USER <callsign> ...^Delete this user from the User Database
334 This command will completely remove a one or more users from the database.
336 There is NO SECOND CHANCE.
338 It goes without saying that you should use this command CAREFULLY!
340 === 0^DBAVAIL^Show a list of all the Databases in the system
341 Title says it all really, this command lists all the databases defined
342 in the system. It is also aliased to SHOW/COMMAND.
344 === 9^DBCREATE <name>^Create a database entry
345 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
346 === 9^DBCREATE <name> remote <node>^Create a remote database entry
347 DBCREATE allows you to define a database in the system. It doesn't actually
348 create anything, just defines it.
350 The databases that are created are simple DB_File hash databases, they are
351 therefore already 'indexed'.
353 You can define a local database with the first form of the command eg:
357 You can also chain databases with the addition of the 'chain' keyword.
358 This will search each database one after the other. A typical example
361 DBCREATE sdx_qsl chain sql_ad
363 No checking is done to see if the any of the chained databases exist, in
364 fact it is usually better to do the above staement first then do each of
365 the chained databases.
367 Databases can exist offsite. To define a database that lives on another
370 DBCREATE buckmaster remote gb7dxc
372 Remote databases cannot be chained; however, the last database in a
373 a chain can be a remote database eg:
375 DBCREATE qsl chain gb7dxc
377 To see what databases have been defined do:
379 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
381 It would be normal for you to add an entry into your local Aliases file
382 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
383 need to add a line like:-
388 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
397 to work as they may be used to.
399 See DBIMPORT for the importing of existing AK1A format data to databases.
400 See DBSHOW for generic database enquiry
402 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
403 If you want to import or update data in bulk to a database you can use
404 this command. It will either create or update entries into an existing
405 database. For example:-
407 DBIMPORT oblast /tmp/OBLAST.FUL
409 will import the standard OBLAST database that comes with AK1A into the
410 oblast database held locally.
412 === 9^DBREMOVE <dbname>^Delete a database
413 DBREMOVE will completely remove a database entry and also delete any data
414 file that is associated with it.
416 There is no warning, no comeback, no safety net.
422 will remove the oblast database from the system and it will also remove
423 the associated datafile.
427 There is no warning, no comeback, no safety net.
429 You have been warned.
431 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
432 This is the generic user interface to the database to the database system.
433 It is expected that the sysop will add an entry to the local Aliases file
434 so that users can use the more familiar AK1A style of enquiry such as:
438 but if he hasn't and the database really does exist (use DBAVAIL or
439 SHOW/COMMAND to find out) you can do the same thing with:
443 === 9^DEBUG^Set the cluster program into debug mode
444 Executing this command will only have an effect if you are running the cluster
449 It will interrupt the cluster just after the debug command has finished.
451 === 0^DIRECTORY^List messages
452 === 0^DIRECTORY ALL^List all messages
453 === 0^DIRECTORY OWN^List your own messages
454 === 0^DIRECTORY NEW^List all new messages
455 === 0^DIRECTORY TO <call>^List all messages to <call>
456 === 0^DIRECTORY FROM <call>^List all messages from <call>
457 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
458 === 0^DIRECTORY <nn>^List last <nn> messages
459 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
460 List the messages in the messages directory.
462 If there is a 'p' one space after the message number then it is a
463 personal message. If there is a '-' between the message number and the
464 'p' then this indicates that the message has been read.
466 You can use shell escape characters such as '*' and '?' in the <call>
469 You can combine some of the various directory commands together eg:-
473 DIR SUBJECT IOTA 200-250
475 You can abbreviate all the commands to one letter and use ak1a syntax:-
481 Sysops can see all users' messages.
483 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
484 Disconnect any <call> connected locally
486 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
487 This is how you send a DX Spot to other users. You can, in fact, now
488 enter the <freq> and the <call> either way round.
494 will all give the same result. You can add some remarks to the end
495 of the command and they will be added to the spot.
497 DX FR0G 144600 this is a test
499 You can credit someone else by saying:-
501 DX by G1TLH FR0G 144.600 he isn't on the cluster
503 The <freq> is compared against the available bands set up in the
504 cluster. See SHOW/BANDS for more information.
506 === 0^ECHO <line>^Echo the line to the output
507 This command is useful in scripts and so forth for printing the
508 line that you give to the command to the output. You can use this
509 in user_default scripts and the SAVE command for titling and so forth
511 The script will interpret certain standard "escape" sequences as follows:-
513 \t - becomes a TAB character (0x09 in ascii)
514 \a - becomes a BEEP character (0x07 in ascii)
515 \n - prints a new line
517 So the following example:-
519 echo GB7DJK is a dxcluster
523 GB7DJK is a dxcluster
525 on the output. You don't need a \n on the end of the line you want to send.
527 A more complex example:-
529 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
539 === 9^EXPORT <msgno> <filename>^Export a message to a file
540 Export a message to a file. This command can only be executed on a local
541 console with a fully privileged user. The file produced will be in a form
542 ready to be imported back into the cluster by placing it in the import
543 directory (/spider/msg/import).
545 This command cannot overwrite an existing file. This is to provide some
546 measure of security. Any files written will owned by the same user as the
547 main cluster, otherwise you can put the new files anywhere the cluster can
548 access. For example:-
552 === 9^EXPORT_USERS [<filename>]^Export the users database to ascii
553 Export the users database to a file in ascii format. If no filename
554 is given then it will export the file to /spider/data/user_asc.
556 If the file already exists it will be renamed to <filename>.o. In fact
557 up to 5 generations of the file can be kept each one with an extra 'o' on the
560 BE WARNED: this will write to any file you have write access to. No check is
561 made on the filename (if any) that you specify.
563 === 0^FILTERING...^Filtering things in DXSpider
564 There are a number of things you can filter in the DXSpider system. They
565 all use the same general mechanism.
567 In general terms you can create a 'reject' or an 'accept' filter which
568 can have up to 10 lines in it. You do this using, for example:-
573 where ..... are the specific commands for that type of filter. There
574 are filters for spots, wwv, announce, wcy and (for sysops)
575 connects. See each different accept or reject command reference for
578 There is also a command to clear out one or more lines in a filter and
579 one to show you what you have set. They are:-
588 There is clear/xxxx command for each type of filter.
590 For now we are going to use spots for the examples, but you can apply
591 the principles to all types of filter.
593 There are two main types of filter 'accept' or 'reject'; which you use
594 depends entirely on how you look at the world and what is least
595 writing to achieve what you want. Each filter has 10 lines (of any
596 length) which are tried in order. If a line matches then the action
597 you have specified is taken (ie reject means ignore it and accept
600 The important thing to remember is that if you specify a 'reject'
601 filter (all the lines in it say 'reject/spots' (for instance) then if
602 a spot comes in that doesn't match any of the lines then you will get
603 it BUT if you specify an 'accept' filter then any spots that don't
604 match are dumped. For example if I have a one line accept filter:-
606 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
608 then automatically you will ONLY get VHF spots from or to CQ zones 14
609 15 and 16. If you set a reject filter like:
611 reject/spots on hf/cw
613 Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
614 and will work it even on CW then you could say:-
616 reject/spots on hf/cw and not info iota
618 But in that case you might only be interested in iota and say:-
620 accept/spots not on hf/cw or info iota
622 which is exactly the same. You should choose one or the other until
623 you are confortable with the way it works. Yes, you can mix them
624 (actually you can have an accept AND a reject on the same line) but
625 don't try this at home until you can analyse the results that you get
626 without ringing up the sysop for help.
628 You can arrange your filter lines into logical units, either for your
629 own understanding or simply convenience. I have one set frequently:-
631 reject/spots 1 on hf/cw
632 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
634 What this does is to ignore all HF CW spots (being a class B I can't
635 read any CW and couldn't possibly be interested in HF :-) and also
636 rejects any spots on VHF which don't either originate or spot someone
639 This is an exmaple where you would use the line number (1 and 2 in
640 this case), if you leave the digit out, the system assumes '1'. Digits
641 '0'-'9' are available.
643 You can leave the word 'and' out if you want, it is implied. You can
644 use any number of brackets to make the 'expression' as you want
645 it. There are things called precedence rules working here which mean
646 that you will NEED brackets in a situation like line 2 because,
647 without it, will assume:-
649 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
651 annoying, but that is the way it is. If you use OR - use
652 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
655 If you want to alter your filter you can just redefine one or more
656 lines of it or clear out one line. For example:-
658 reject/spots 1 on hf/ssb
664 To remove the filter in its entirty:-
668 There are similar CLEAR commands for the other filters:-
676 Once you are happy with the results you get, you may like to experiment.
678 my example that filters hf/cw spots and accepts vhf/uhf spots from EU
679 can be written with a mixed filter, eg:
683 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
685 each filter slot actually has a 'reject' slot and an 'accept'
686 slot. The reject slot is executed BEFORE the accept slot.
688 It was mentioned earlier that after a reject test that doesn't match,
689 the default for following tests is 'accept', the reverse is true for
690 'accept'. In the example what happens is that the reject is executed
691 first, any non hf/cw spot is passed to the accept line, which lets
692 thru everything else on HF.
694 The next filter line lets through just VHF/UHF spots from EU.
696 === 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
697 This command sends all the latitude and longitude information that your
698 cluster is holding against callsigns. One advantage of recieving this
699 information is that more locator information is held by you. This
700 means that more locators are given on the DX line assuming you have
701 SET/DXGRID enabled. This could be a LOT of information though, so
702 it is not recommended on slow links.
704 === 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
705 This command sends out any information held in the user file which can
706 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
707 and Homenode. PC41s are only sent for the information that is available.
709 === 0^HELP^The HELP Command
710 HELP is available for a number of commands. The syntax is:-
714 Where <cmd> is the name of the command you want help on.
716 All commands can be abbreviated, so SHOW/DX can be abbreviated
717 to SH/DX, ANNOUNCE can be shortened to AN and so on.
719 Look at the APROPOS <string> command which will search the help database
720 for the <string> you specify and give you a list of likely commands
721 to look at with HELP.
723 === 5^INIT <node>^Re-initialise a link to an AK1A compatible node
724 This command attempts to re-initialise a link to a (usually) AK1A node
725 that has got confused, usually by a protocol loop of some kind. It may
726 work - but you usually will be better off simply disconnecting it (or
727 better, if it is a real AK1A node, doing an RCMD <node> DISC/F <your
730 Best of luck - you will need it.
732 === 9^DEMONSTRATE <call> <command>^Demonstrate a command to another user
733 This command is provided so that sysops can demonstrate commands to
734 other users. It runs a command as though that user had typed it in and
735 then sends the output to that user, together with the command that
738 DEMO g7brn sh/dx iota oc209
741 Note that this command is similar to SPOOF and will have the same side
742 effects. Commands are run at the privilege of the user which is being
745 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
746 === 0^KILL <from msgno>-<to msgno>^Delete a range of messages
747 === 0^KILL from <regex>^Delete messages FROM a callsign or pattern
748 === 0^KILL to <regex>^Delete messages TO a callsign or pattern
749 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
750 Delete a message from the local system. You will only be able to
751 delete messages that you have originated or been sent (unless you are
756 Will delete all the messages that you own between msgnos 1234 and 1255.
760 will delete all the messages from g1tlh (if you are g1tlh). Similarly:
764 will delete all messages to g1tlh.
768 will delete a message (usually a 'bulletin') from the whole cluster system.
770 This uses the subject field, so any messages that have exactly the
771 same subject will be deleted. Beware!
773 === 6^KILL EXPunge <msgno> [<msgno..]^Expunge a message
774 Deleting a message using the normal KILL commands only marks that message
775 for deletion. The actual deletion only happens later (usually two days later).
777 The KILL EXPUNGE command causes the message to be truly deleted more or less
780 It otherwise is used in the same way as the KILL command.
782 === 0^LINKS^Show which nodes is physically connected
783 This is a quick listing that shows which links are connected and
784 some information about them. See WHO for a list of all connections.
786 === 9^LOAD/ALIASES^Reload the command alias table
787 Reload the /spider/cmd/Aliases file after you have editted it. You
788 will need to do this if you change this file whilst the cluster is
789 running in order for the changes to take effect.
791 === 9^LOAD/BANDS^Reload the band limits table
792 Reload the /spider/data/bands.pl file if you have changed it manually whilst
793 the cluster is running.
795 === 9^LOAD/BADMSG^Reload the bad msg table
796 Reload the /spider/msg/badmsg.pl file if you have changed it manually whilst
797 the cluster is running. This table contains a number of perl regular
798 expressions which are searched for in the fields targetted of each message.
799 If any of them match then that message is immediately deleted on receipt.
801 === 9^LOAD/BADWORDS^Reload the bad words table
802 Reload the /spider/data/badwords file if you have changed it manually whilst
803 the cluster is running. This file contains a list of words which, if found
804 on certain text portions of PC protocol, will cause those protocol frames
805 to be rejected. It will all put out a message if any of these words are
806 used on the announce, dx and talk commands. The words can be one or
807 more on a line, lines starting with '#' are ignored.
809 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
810 Normally, if you change a command file in the cmd or local_cmd tree it
811 will automatially be picked up by the cluster program. Sometimes it
812 can get confused if you are doing a lot of moving commands about or
813 delete a command in the local_cmd tree and want to use the normal one
814 again. Execute this command to reset everything back to the state it
815 was just after a cluster restart.
817 === 9^LOAD/FORWARD^Reload the msg forwarding routing table
818 Reload the /spider/msg/forward.pl file if you have changed it
819 manually whilst the cluster is running.
821 === 5^LOAD/KEPS^Load new keps data
822 === 5^LOAD/KEPS [nn]^Load new keps data from message
823 If there is no message number then reload the current Keps data from
824 the Keps.pm data file. You create this file by running
826 /spider/perl/convkeps.pl <filename>
828 on a file containing NASA 2 line keps as a message issued by AMSAT.
830 If there is a message number, then it will take the message, run
831 convkeps.pl on it and then load the data, all in one step.
833 These messages are sent to ALL by GB7DJK (and others) from time to time.
835 === 9^LOAD/MESSAGES^Reload the system messages file
836 If you change the /spider/perl/Messages file (usually whilst
837 fiddling/writing new commands) you can have them take effect during a
838 cluster session by executing this command. You need to do this if get
841 unknown message 'xxxx' in lang 'en'
843 === 9^LOAD/PREFIXES^Reload the prefix table
844 Reload the /spider/data/prefix_data.pl file if you have changed it
845 manually whilst the cluster is running.
847 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
848 MERGE allows you to bring your spot and wwv database up to date. By default
849 it will request the last 10 spots and 5 WWVs from the node you select. The
850 node must be connected locally.
852 You can request any number of spots or wwv and although they will be appended
853 to your databases they will not duplicate any that have recently been added
854 (the last 2 days for spots and last month for WWV data).
856 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
857 Alter message parameters like To, From, Subject, whether private or bulletin
858 or return receipt (RR) is required or whether to keep this message from timing
861 MSG TO <msgno> <call> - change TO callsign to <call>
862 MSG FRom <msgno> <call> - change FROM callsign to <call>
863 MSG PRrivate <msgno> - set private flag
864 MSG NOPRrivate <msgno> - unset private flag
865 MSG RR <msgno> - set RR flag
866 MSG NORR <msgno> - unset RR flag
867 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
868 MSG NOKEep <msgno> - unset the keep flag
869 MSG SUbject <msgno> <new> - change the subject to <new>
870 MSG WAittime <msgno> - remove any waitting time for this message
871 MSG NOREad <msgno> - mark message as unread
872 MSG REad <msgno> - mark message as read
873 MSG QUeue - queue any outstanding bulletins
874 MSG QUeue 1 - queue any outstanding private messages
876 You can look at the status of a message by using:-
880 This will display more information on the message than DIR does.
882 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
883 Send some arbitrary text to a locally connected callsign. No
884 processing is done on the text. This command allows you to send PC
885 Protocol to unstick things if problems arise (messages get stuck
888 pc gb7djk PC33^GB7TLH^GB7DJK^400^
890 pc G1TLH Try doing that properly!!!
892 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
893 You can get rid of any message to or originating from your callsign using
894 this command. You can remove more than one message at a time.
896 === 5^KILL <from>-<to>^Remove a range of messages from the system
897 === 5^KILL FROM <call>^Remove all messages from a callsign
898 === 5^KILL TO <call>^Remove all messages to a callsign
899 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
900 Remove this message from the entire cluster system as well as your node.
903 As a sysop you can kill any message on the system.
905 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
906 Send any text you like to the callsign requested. This is used mainly to send
907 PC protocol to connected nodes either for testing or to unstick things.
909 You can also use in the same way as a talk command to a connected user but
910 without any processing, added of "from <blah> to <blah" or whatever.
912 === 1^PING <node call>^Check the link quality between nodes
913 This command allows you to send a frame to another cluster node on
914 the network and get a return frame. The time it takes to do this
915 is a good indication of the quality of the link. The actual time
916 it takes is output to the console in seconds.
917 Any visible cluster node can be PINGed.
919 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
920 This command allows you to send nearly any command to another DX Cluster
921 node that is connected to the system.
923 Whether you get any output is dependant on a) whether the other system knows
924 that the node callsign of this cluster is in fact a node b) whether the
925 other system is allowing RCMDs from this node and c) whether you have
926 permission to send this command at all.
928 === 0^READ^Read the next unread personal message addressed to you
929 === 0^READ <msgno>^Read the specified message
930 You can read any messages that are sent as 'non-personal' and also any
931 message either sent by or sent to your callsign.
934 As a sysop you may read any message on the system
936 === 0^REJECT^Set a filter to reject something
937 Create a filter to reject something
939 There are 2 types of filter, accept and reject. See HELP FILTERING for more
942 === 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
943 Create an 'reject this announce' line for a filter.
945 A reject filter line means that if the announce matches this filter it is
946 passed onto the user. See HELP FILTERING for more info. Please read this
947 to understand how filters work - it will save a lot of grief later on.
949 You can use any of the following things in this line:-
951 info <string> eg: iota or qsl
952 by <prefixes> eg: G,M,2
954 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
955 origin_itu <prefixes or numbers> or: G,GM,GW
956 origin_zone <prefixes or numbers>
957 by_dxcc <prefixes or numbers>
958 by_itu <prefixes or numbers>
959 by_zone <prefixes or numbers>
961 wx 1 filter WX announces
962 dest <prefixes> eg: 6MUK,WDX (distros)
966 rej/ann by_zone 14,15,16 and not by G,M,2
968 You can use the tag 'all' to reject everything eg:
972 but this probably for advanced users...
974 === 8^REJECT/ANNOUNCE <call> [input] [0-9] <pattern>^Announce filter sysop version
975 This version allows a sysop to set a filter for a callsign as well as the
976 default for nodes and users eg:-
979 reject/ann input node_default by G,M,2
980 reject/ann user_default by G,M,2
982 === 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
983 Create a 'reject this spot' line for a filter.
985 A reject filter line means that if the spot matches this filter it is
986 dumped (not passed on). See HELP FILTERING for more info. Please read this
987 to understand how filters work - it will save a lot of grief later on.
989 You can use any of the following things in this line:-
991 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
992 on <range> same as 'freq'
993 call <prefixes> eg: G,PA,HB9
994 info <string> eg: iota or qsl
996 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
997 call_itu <prefixes or numbers> or: G,GM,GW
998 call_zone <prefixes or numbers>
999 by_dxcc <prefixes or numbers>
1000 by_itu <prefixes or numbers>
1001 by_zone <prefixes or numbers>
1005 For frequencies, you can use any of the band names defined in
1006 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1007 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1008 this is more efficient than saying simply: on HF (but don't get
1009 too hung up about that)
1014 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1016 You can use the tag 'all' to reject everything eg:
1020 but this probably for advanced users...
1022 === 8^REJECT/ROUTE <call> [0-9] <pattern>^Set an 'reject' filter line for routing
1023 Create an 'reject this routing PC Protocol' line for a filter.
1025 An reject filter line means that if a PC16/17/19/21/24/41/50 matches this filter
1026 it is NOT passed thru that interface. See HELP FILTERING for more info. Please
1027 read this to understand how filters work - it will save a lot of grief later on.
1029 You can use any of the following things in this line:-
1031 call <prefixes> the callsign of the thingy
1032 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1033 call_itu <prefixes or numbers> or: G,GM,GW
1034 call_zone <prefixes or numbers>
1035 origin <prefixes> really the interface it came in on
1036 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1037 origin_itu <prefixes or numbers> or: G,GM,GW
1038 origin_zone <prefixes or numbers>
1042 rej/route gb7djk call_dxcc 61,38 (everything except UK+EIRE nodes)
1044 You can use the tag 'all' to reject everything eg:
1046 rej/route all (equiv to [very] restricted mode)
1048 === 8^REJECT/SPOTS <call> [input] [0-9] <pattern>^Spot filter sysop version
1049 This version allows a sysop to set a filter for a callsign as well as the
1050 default for nodes and users eg:-
1052 reject/spot db0sue-7 1 by_zone 14,15,16
1053 reject/spot node_default all
1054 set/hops node_default 10
1056 reject/spot user_default by G,M,2
1058 === 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
1059 It is unlikely that you will want to do this, but if you do then you can
1060 filter on the following fields:-
1062 by <prefixes> eg: G,M,2
1064 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1065 origin_itu <prefixes or numbers> or: G,GM,GW
1066 origin_zone <prefixes or numbers>
1067 by_dxcc <prefixes or numbers>
1068 by_itu <prefixes or numbers>
1069 by_zone <prefixes or numbers>
1072 There are no examples because WCY Broadcasts only come from one place and
1073 you either want them or not (see UNSET/WCY if you don't want them).
1075 This command is really provided for future use.
1077 See HELP FILTER for information.
1079 === 8^REJECT/WCY <call> [input] [0-9] <pattern>^WCY filter sysop version
1080 This version allows a sysop to set a filter for a callsign as well as the
1081 default for nodes and users eg:-
1083 reject/wcy gb7djk all
1085 === 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
1086 It is unlikely that you will want to do this, but if you do then you can
1087 filter on the following fields:-
1089 by <prefixes> eg: G,M,2
1091 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1092 origin_itu <prefixes or numbers> or: G,GM,GW
1093 origin_zone <prefixes or numbers>
1094 by_dxcc <prefixes or numbers>
1095 by_itu <prefixes or numbers>
1096 by_zone <prefixes or numbers>
1101 reject/wwv by_zone 14,15,16
1103 is probably the only useful thing to do (which will only show WWV broadcasts
1104 by stations in the US).
1106 See HELP FILTER for information.
1108 === 8^REJECT/WWV <call> [input] [0-9] <pattern>^WWV filter sysop version
1109 This version allows a sysop to set a filter for a callsign as well as the
1110 default for nodes and users eg:-
1112 reject/wwv db0sue-7 1 by_zone 4
1113 reject/wwv node_default all
1115 reject/wwv user_default by W
1117 === 0^REPLY^Reply (privately) to the last message that you have read
1118 === 0^REPLY <msgno>^Reply (privately) to the specified message
1119 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
1120 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
1121 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
1122 You can reply to a message and the subject will automatically have
1123 "Re:" inserted in front of it, if it isn't already present.
1125 You can also use all the extra qualifiers such as RR, PRIVATE,
1126 NOPRIVATE, B that you can use with the SEND command (see SEND
1127 for further details)
1129 === 9^SAVE [-d -t -a] <filename> "<cmd>" [...]^Save command output to a file
1130 This sysop only cammand allows you to save the output of one or more
1131 commands to a file. For example:-
1133 save /spider/packclus/dxstats show/dxstat
1135 will save the output of the normal command "show/dxstat" to the file
1136 "dxstats" in the files area.
1138 You can have some extra flags to the save which will either
1139 date stamp or time stamp or both the filename so:-
1141 save -d /tmp/a <cmd> creates /tmp/a_6-Jan-2002
1142 save -t /tmp/a <cmd> creates /tmp/a_2301Z
1143 save -d -t /tmp/a <cmd> creates /tmp/a_6-Jan-2002_2301Z
1145 The -a flag means append to the file instead of overwriting it.
1147 You can have more than one command on the line, to do this you MUST
1148 enclose each command in double quotes (") eg:-
1150 save /tmp/a "sh/hfstats" "blank +" "sh/vhfstats"
1154 save /tmp/a "sh/hfstats","blank +","sh/vhfstats"
1156 You can only write into places that the cluster has permission for (which
1157 is that of the "sysop" user [which had BETTER NOT BE "root"]), you will
1158 need to create any directories you want to put stuff in beforehand as well.
1160 It is likely that you will want to run these commands in a crontab type
1161 situation. You would do that something like:-
1163 0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')
1165 Note that you still enclose each command with (") characters but you must
1166 enclose the entire save command in (') characters.
1168 Now in fact, this can be varied if you know what you are doing. See the
1169 admin manual for more details.
1171 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
1172 === 0^SEND RR <call>^Send a message and ask for a read receipt
1173 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
1174 === 0^SEND PRIVATE <call>^Send a personal message
1175 === 0^SEND NOPRIVATE <call>^Send a message to all stations
1176 All the SEND commands will create a message which will be sent either to
1177 an individual callsign or to one of the 'bulletin' addresses.
1179 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1180 it will mark the message as personal and send it to the cluster node that
1181 that callsign is connected to. If the <call> you have specified is in fact
1182 a known bulletin category on your node (eg: ALL) then the message should
1183 automatically become a bulletin.
1185 You can have more than one callsign in all of the SEND commands.
1187 You can have multiple qualifiers so that you can have for example:-
1189 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1191 which should send a copy of message 123 to G1TLH and G0RDI and you will
1192 receive a read receipt when they have read the message.
1194 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1195 SP is an alias for SEND PRIVATE
1197 The system will ask you for a subject. Conventionally this should be
1198 no longer than 29 characters for compatibility. Most modern cluster
1199 software should accept more.
1201 You will now be prompted to start entering your text.
1203 You finish the message by entering '/EX' on a new line. For instance:
1210 If you have started a message and you don't want to keep it then you
1211 can abandon the message with '/ABORT' on a new line, like:-
1215 oh I just can't be bothered with this
1218 If you abort the message it will NOT be sent.
1220 When you are entering the text of your message, most normal output (such
1221 as DX announcements and so on are suppressed and stored for latter display
1222 (upto 20 such lines are stored, as new ones come along, so the oldest
1225 Also, you can enter normal commands commands (and get the output
1226 immediately) whilst in the middle of a message. You do this by typing
1227 the command preceeded by a '/' character on a new line, so:-
1229 /dx g1tlh 144010 strong signal
1231 Will issue a dx annoucement to the rest of the cluster.
1233 Also, you can add the output of a command to your message by preceeding
1234 the command with '//', thus :-
1238 This will show YOU the output from SH/VHFTABLE and also store it in the
1241 You can carry on with the message until you are ready to send it.
1242 === 0^SET/ADDRESS <your address>^Record your postal address
1244 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
1245 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
1247 === 0^SET/ANNTALK^Allow talk like announce messages on your terminal
1248 === 0^UNSET/ANNTALK^Stop talk like announce messages on your terminal
1249 The announce system on legacy cluster nodes is used as a talk
1250 substitute because the network is so poorly connected. If you:
1254 you will suppress several of these announces, you may miss the odd
1255 useful one as well, but you would probably miss them anyway in the
1256 welter of useless ones.
1260 allows you to see them again. This is the default.
1262 === 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
1264 === 8^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
1265 === 8^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
1266 Setting a word as 'baddx' will prevent spots with that word in the
1267 'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
1268 further. They will not be displayed and they will not be sent onto
1271 The word must be written in full, no wild cards are allowed eg:-
1273 set/baddx FORSALE VIDEO FR0G
1275 To allow a word again, use the following command ...
1279 === 8^SET/BADNODE <call>..^Stop spots from this node being propagated
1280 === 8^UNSET/BADNODE <call>..^Allow spots from this node again
1281 Setting a callsign as a 'badnode' will prevent spots from that node
1282 going any further. They will not be displayed and they will not be
1283 sent onto other nodes.
1285 The call must be a full eg:-
1289 will stop anything from K1TTT. If you want SSIDs as well then you must
1290 enter them specifically.
1294 will allow spots from him again.
1296 Use with extreme care. This command may well be superceeded by FILTERing.
1298 === 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
1299 === 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
1300 Setting a callsign as a 'badspotter' will prevent spots from this callsign
1301 going any further. They will not be displayed and they will not be
1302 sent onto other nodes.
1304 The call must be written in full, no wild cards are allowed eg:-
1306 set/badspotter VE2STN
1308 will stop anything from VE2STN. If you want SSIDs as well then you must
1309 enter them specifically.
1311 unset/badspotter VE2STN
1313 will allow spots from him again.
1315 Use with extreme care. This command may well be superceded by FILTERing.
1317 === 8^SET/BADWORD <word>..^Stop things with this word being propagated
1318 === 8^UNSET/BADWORD <word>..^Propagate things with this word again
1319 Setting a word as a 'badword' will prevent things like spots,
1320 announces or talks with this word in the the text part from going any
1321 further. They will not be displayed and they will not be sent onto
1324 The word must be written in full, no wild cards are allowed eg:-
1326 set/badword annihilate annihilated annihilation
1328 will stop anything with these words in the text.
1330 unset/badword annihilated
1332 will allow text with this word again.
1334 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
1335 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
1337 === 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
1339 === 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
1341 === 9^SET/DEBUG <name>^Add a debug level to the debug set
1342 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
1343 You can choose to log several different levels. The levels are
1351 You can show what levels you are logging with SHOW/DEBUG
1353 === 0^SET/DX^Allow DX messages to come out on your terminal
1354 === 0^UNSET/DX^Stop DX messages coming out on your terminal
1356 === 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
1357 === 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
1358 A standard feature which is enabled in version 1.43 and above is
1359 that if the spotter's grid square is known it is output on the end
1360 of a DX announcement (there is just enough room). Some user programs
1361 cannot cope with this. You can use this command to reset (or set)
1364 === 5^SET/DXNET <call> [<call>..]^Make the callsign an DXNet node
1366 === 0^SET/ECHO^Make the cluster echo your input
1367 === 0^UNSET/ECHO^Stop the cluster echoing your input
1368 If you are connected via a telnet session, different implimentations
1369 of telnet handle echo differently depending on whether you are
1370 connected via port 23 or some other port. You can use this command
1371 to change the setting appropriately.
1373 The setting is stored in your user profile.
1375 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1377 === 0^SET/EMAIL <email> ...^Set email address(es) and forward your personals
1378 === 0^UNSET/EMAIL^Stop personal msgs being forwarded by email
1379 If any personal messages come in for your callsign then you can use
1380 these commands to control whether they are forwarded onto your email
1381 address. To enable the forwarding do something like:-
1383 SET/EMAIL mike.tubby@somewhere.com
1385 You can have more than one email address (each one separated by a space).
1386 Emails are forwarded to all the email addresses you specify.
1388 You can disable forwarding by:-
1392 === 0^SET/HERE^Tell the system you are present at your terminal
1393 === 0^UNSET/HERE^Tell the system you are absent from your terminal
1395 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
1396 Tell the cluster system where you normally connect to. Any Messages sent
1397 to you will normally find their way there should you not be connected.
1401 === 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
1402 === 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
1403 Set the hop count for a particular type of broadcast for a node.
1405 This command allows you to set up special hop counts for a node
1406 for currently: announce, spots, wwv and wcy broadcasts.
1409 set/hops gb7djk ann 10
1410 set/hops gb7mbc spots 20
1412 Set SHOW/HOPS for information on what is already set. This command
1413 creates a filter and works in conjunction with the filter system.
1415 You can unset the hops with command UNSET/HOPS. For example:-
1417 unset/hops gb7djk ann
1418 unset/hops gb7mbc spots
1421 === 9^SET/ISOLATE^Isolate a node from the rest of the network
1422 Connect a node to your system in such a way that you are a full protocol
1423 member of its network and can see all spots on it, but nothing either leaks
1424 out from it nor goes back into from the rest of the nodes connected to you.
1426 You can potentially connect several nodes in this way.
1428 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
1429 Remove isolation from a node - SET/ISOLATE
1431 === 0^SET/LANGUAGE <lang>^Set the language you want to use
1432 You can select the language that you want the cluster to use. Currently
1433 the languages available are en (English), de (German), es (Spanish)
1436 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
1437 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
1438 In order to get accurate headings and such like you must tell the system
1439 what your latitude and longitude is. If you have not yet done a SET/QRA
1440 then this command will set your QRA locator for you. For example:-
1441 SET/LOCATION 52 22 N 0 57 E
1443 === 0^SET/LOGININFO^Inform when a station logs in locally
1444 === 0^UNSET/LOGININFO^Inform when a station logs out locally
1446 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
1447 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
1449 === 0^SET/NAME <your name>^Set your name
1450 Tell the system what your name is eg:-
1453 === 5^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
1454 Tell the system that the call(s) are to be treated as AK1A cluster and
1455 fed PC Protocol rather normal user commands.
1457 === 8^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
1458 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
1459 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
1460 counter which is decremented on every outgoing ping and then reset to
1461 the 'obscount' value on every incoming ping. The default value of this
1464 What this means is that a neighbouring node will be pinged twice at
1465 (default) 300 second intervals and if no reply has been heard just before
1466 what would be the third attempt, that node is disconnected.
1468 If a ping is heard then the obscount is reset to the full value. Using
1469 default values, if a node has not responded to a ping within 15 minutes,
1472 You can set this parameter between 1 and 9.
1474 It is STRONGLY recommended that you don't change the default.
1476 === 0^SET/PAGE <lines per page>^Set the lines per page
1477 Tell the system how many lines you wish on a page when the number of line
1478 of output from a command is more than this. The default is 20. Setting it
1479 explicitly to 0 will disable paging.
1483 The setting is stored in your user profile.
1485 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
1486 As from release 1.35 all neighbouring nodes are pinged at regular intervals
1487 in order to determine the rolling quality of the link and, in future, to
1488 affect routing decisions. The default interval is 300 secs or 5 minutes.
1490 You can use this command to set a different interval. Please don't.
1492 But if you do the value you enter is treated as minutes up 30 and seconds
1493 for numbers greater than that.
1495 This is used also to help determine when a link is down at the far end
1496 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
1497 for more information.
1499 If you must change it (and it may be useful for internet connected nodes
1500 on dynamic IP addresses that go away after a set time of usage) the time
1501 can be specified as:-
1503 5 which if less than 30 is converted to minutes otherwise is
1504 taken as the no of seconds between pings.
1509 Please be aware that this causes traffic to occur on the link, setting
1510 this value too low may annoy your neighbours beyond the point of
1513 You can switch this off by setting it to 0.
1515 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
1516 Set the privilege level on a callsign. The privilege levels that pertain
1517 to commands are as default:-
1519 1 - allow remote nodes normal user RCMDs
1520 5 - various privileged commands (including shutdown, but not disc-
1521 connect), the normal level for another node.
1522 8 - more privileged commands (including disconnect)
1523 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
1525 If you are a sysop and you come in as a normal user on a remote connection
1526 your privilege will automatically be set to 0.
1528 === 0^UNSET/PRIVILEGE^Remove any privilege for this session
1529 You can use this command to 'protect' this session from unauthorised
1530 use. If you want to get your normal privilege back you will need to
1531 either logout and login again (if you are on a console) or use the
1534 === 9^SET/PASSWORD <callsign> <string>^Set a users password
1535 The password for a user can only be set by a full sysop. The string
1536 can contain any characters.
1538 The way this field is used depends on context. If it is being used in
1539 the SYSOP command context then you are offered 5 random numbers and you
1540 have to supply the corresponding letters. This is now mainly for ax25
1543 If it is being used on incoming telnet connections then, if a password
1546 set/var $main::passwdreq = 1
1548 command is executed in the startup script, then a password prompt is
1549 given after the normal 'login: ' prompt.
1551 === 0^SET/PASSWORD^Set your own password
1552 This command only works for a 'telnet' user (currently). It will
1553 only work if you have a password already set. This initial password
1554 can only be set by the sysop.
1556 When you execute this command it will ask you for your old password,
1557 then ask you to type in your new password twice (to make sure you
1558 get it right). You may or may not see the data echoed on the screen
1559 as you type, depending on the type of telnet client you have.
1561 === 9^UNSET/PASSWORD <call> ...^Delete (remove) a user's password
1562 This command allows the sysop to completely delete and remove a
1563 password for a user.
1565 === 0^SET/PROMPT <string>^Set your prompt to <string>
1566 === 0^UNSET/PROMPT^Set your prompt back to default
1567 This command will set your user prompt to exactly the string that you
1568 say. The point of this command to enable a user to interface to programs
1569 that are looking for a specific prompt (or else you just want a different
1574 UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
1577 === 5^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
1578 Tell the system that the call(s) are to be treated as DXSpider node and
1579 fed new style DX Protocol rather normal user commands.
1581 === 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
1582 === 0^SET/QRA <locator>^Set your QRA Grid locator
1583 Tell the system what your QRA (or Maidenhead) locator is. If you have not
1584 done a SET/LOCATION then your latitude and longitude will be set roughly
1585 correctly (assuming your locator is correct ;-). For example:-
1588 === 0^SET/QTH <your qth>^Set your QTH
1589 Tell the system where you are. For example:-
1590 SET/QTH East Dereham, Norfolk
1592 === 9^SET/REGISTER <call> ...^Mark a user as registered
1593 === 9^UNSET/REGISTER <call> ...^Mark a user as not registered
1594 Registration is a concept that you can switch on by executing the
1596 set/var $main::regreq = 1
1598 command (usually in your startup file)
1600 If a user is NOT registered then, firstly, instead of the normal
1601 motd file (/spider/data/motd) being sent to the user at startup, the
1602 user is sent the motd_nor file instead. Secondly, the non registered
1603 user only has READ-ONLY access to the node. The non-registered user
1604 cannot use DX, ANN etc.
1606 The only exception to this is that a non-registered user can TALK or
1607 SEND messages to the sysop.
1609 === 0^SET/TALK^Allow TALK messages to come out on your terminal
1610 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
1612 === 0^SET/WCY^Allow WCY messages to come out on your terminal
1613 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
1615 === 0^SET/WWV^Allow WWV messages to come out on your terminal
1616 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
1618 === 0^SET/WX^Allow WX messages to come out on your terminal
1619 === 0^UNSET/WX^Stop WX messages coming out on your terminal
1621 === 1^SHOW/BADDX^Show all the bad dx calls in the system
1622 Display all the bad dx callsigns in the system, see SET/BADDX
1623 for more information.
1625 === 1^SHOW/BADNODE^Show all the bad nodes in the system
1626 Display all the bad node callsigns in the system, see SET/BADNODE
1627 for more information.
1629 === 1^SHOW/BADSPOTTER^Show all the bad spotters in the system
1630 Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
1631 for more information.
1633 === 1^SHOW/BADWORD^Show all the bad words in the system
1634 Display all the bad words in the system, see SET/BADWORD
1635 for more information.
1637 === 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
1638 This command allows you to see all the users that can be seen
1639 and the nodes to which they are connected.
1641 This command is normally abbreviated to: sh/c
1643 BE WARNED: the list that is returned can be VERY long
1645 === 0^SHOW/CONFIGURATION/NODE^Show all the nodes connected locally
1646 Show all the nodes connected to this node.
1648 === 1^SHOW/CONNECT^Show all the active connections
1649 This command shows information on all the active connections known to
1650 the node. This command gives slightly more information than WHO.
1652 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
1653 This is very nearly the same as SHOW/TIME, the only difference the format
1654 of the date string if no arguments are given.
1656 If no prefixes or callsigns are given then this command returns the local
1657 time and UTC as the computer has it right now. If you give some prefixes
1658 then it will show UTC and UTC + the local offset (not including DST) at
1659 the prefixes or callsigns that you specify.
1661 === 9^SHOW/DEBUG^Show what levels of debug information you are logging
1663 === 0^SHOW/DX^Interrogate the spot database
1664 If you just type SHOW/DX you will get the last so many spots
1665 (sysop configurable, but usually 10).
1667 In addition you can add any number of these commands in very nearly
1668 any order to the basic SHOW/DX command, they are:-
1670 on <band> - eg 160m 20m 2m 23cm 6mm
1671 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1672 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
1675 <number> - the number of spots you want
1676 <from>-<to> - <from> spot no <to> spot no in the selected list
1679 <prefix> - for a spotted callsign beginning with <prefix>
1680 *<suffix> - for a spotted callsign ending in <suffix>
1681 *<string>* - for a spotted callsign containing <string>
1683 day <number> - starting <number> days ago
1684 day <from>-<to> - <from> days <to> days ago
1687 info <text> - any spots containing <text> in the info or remarks
1689 by <call> - any spots spotted by <call> (spotter <call> is the
1692 qsl - this automatically looks for any qsl info on the call
1693 held in the spot database.
1695 iota [<iota>] - If the iota island number is missing it will look for
1696 the string iota and anything which looks like an iota
1697 island number. If you specify then it will look for
1700 qra [<locator>] - this will look for the specific locator if you specify
1701 one or else anything that looks like a locator.
1703 dxcc - treat the prefix as a 'country' and look for spots
1704 from that country regardless of actual prefix.
1707 You can also use this with the 'by' keyword so
1713 SH/DX on 20m info iota
1714 SH/DX 9a on vhf day 30
1720 SH/DX dxcc oq2 by w dxcc
1722 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
1723 This command takes the <prefix> (which can be a full or partial
1724 callsign if desired), looks up which internal country number it is
1725 and then displays all the spots as per SH/DX for that country.
1727 This is now an alias for 'SHOW/DX DXCC'
1729 The options for SHOW/DX also apply to this command.
1733 SH/DXCC W on 20m iota
1735 This can be done with the SHOW/DX command like this:-
1738 SH/DX dxcc w on 20m iota
1740 === 0^SHOW/DXSTATS^Show the DX Statistics for last 31 days
1741 Show the total DX spots for the last 31 days
1743 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
1744 SHOW/FILES on its own will show you a list of the various fileareas
1745 available on the system. To see the contents of a particular file
1748 where <filearea> is the name of the filearea you want to see the
1751 You can also use shell globbing characters like '*' and '?' in a
1752 string to see a selection of files in a filearea eg:-
1753 SH/FILES bulletins arld*
1755 See also TYPE - to see the contents of a file.
1757 === 0^SHOW/FILTER^Show the contents of all the filters you have set
1758 Show the contents of all the filters that are set. This command displays
1759 all the filters set - for all the various categories.
1761 === 0^SHOW/HFSTATS^Show the HF DX Statistics for last 31 days
1762 Show the HF DX spots breakdown by band for the last 31 days
1764 === 0^SHOW/HFTABLE^Show the HF DX Spotter Table for your country
1765 Show the HF DX Spotter table for your country for the last 31 days
1767 === 8^SHOW/HOPS <call> [ann|spots|route|wcy|wwv]^Show the hop counts for a node
1768 This command shows the hop counts set up for a node. You can specify
1769 which category you want to see. If you leave the category out then
1770 all the categories will be listed.
1772 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
1774 === 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
1776 === 8^SHOW/LOG [<callsign>]^Show excerpts from the system log
1777 This command outputs a short section of the system log. On its own
1778 it will output a general logfile. With the optional callsign it will
1779 show output from the log associated with that callsign.
1781 === 0^SHOW/MOON [ndays] [<prefix>|<callsign>]^Show Moon rise and set times
1782 Show the Moon rise and set times for a (list of) prefixes or callsigns,
1783 together with the azimuth and elevation of the sun currently at those
1786 If you don't specify any prefixes or callsigns, it will show the times for
1787 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1788 together with the current azimuth and elevation.
1790 In addition, it will show the illuminated fraction of the moons disk.
1792 If all else fails it will show the Moonrise and set times for the node
1793 that you are connected to.
1800 You can also use this command to see into the past or the future, so
1801 if you want to see yesterday's times then do:-
1805 or in three days time:-
1809 Upto 366 days can be checked both in the past and in the future.
1811 Please note that the rise and set times are given as the UT times of rise and
1812 set on the requested UT day.
1814 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
1815 This command allow you to estimate the likelihood of you contacting
1816 a station with the prefix you have specified. The output assumes a modest
1817 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
1819 The result predicts the most likely operating frequencies and signal
1820 levels for high frequency (shortwave) radio propagation paths on
1821 specified days of the year and hours of the day. It is most useful for
1822 paths between 250 km and 6000 km, but can be used with reduced accuracy
1823 for paths shorter or longer than this.
1825 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1826 used to predict the MUF given the predicted flux, day of the year,
1827 hour of the day and geographic coordinates of the transmitter and
1828 receiver. This routine is reasonably accurate for the purposes here,
1829 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1830 than the programs used by major shortwave broadcasting organizations,
1831 such as the Voice of America.
1833 The command will display some header information detailing its
1834 assumptions, together with the locations, latitude and longitudes and
1835 bearings. It will then show UTC (UT), local time at the other end
1836 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1837 (Zen) and the likely signal strengths. Then for each frequency for which
1838 the system thinks there is a likelihood of a circuit it prints a value.
1840 The value is currently a likely S meter reading based on the conventional
1841 6dB / S point scale. If the value has a '+' appended it means that it is
1842 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1843 there is likely to be much fading and by an 's' that the signal is likely
1846 By default SHOW/MUF will show the next two hours worth of data. You
1847 can specify anything up to 24 hours worth of data by appending the no of
1848 hours required after the prefix. For example:-
1854 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1855 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1856 Location Lat / Long Azim
1857 East Dereham, Norfolk 52 41 N 0 57 E 47
1858 United-States-W 43 0 N 87 54 W 299
1859 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1860 18 23 11.5 -35 mS0+ mS2 S3
1861 19 0 11.2 -41 mS0+ mS2 S3
1863 indicating that you will have weak, fading circuits on top band and
1864 80m but usable signals on 40m (about S3).
1870 will get you the above display, but with the next 24 hours worth of
1876 Gives you an estimate of the long path propagation characterics. It
1877 should be noted that the figures will probably not be very useful, nor
1878 terrible accurate, but it is included for completeness.
1880 === 0^SHOW/NEWCONFIGURATION [<node>]^Show all the nodes and users visible
1881 This command allows you to see all the users that can be seen
1882 and the nodes to which they are connected.
1884 This command produces essentially the same information as
1885 SHOW/CONFIGURATION except that it shows all the duplication of
1886 any routes that might be present It also uses a different format
1887 which may not take up quite as much space if you don't have any
1890 BE WARNED: the list that is returned can be VERY long
1892 === 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
1893 Show all the nodes connected to this node in the new format.
1895 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
1896 Show the type and version (if connected) of the nodes specified on the
1897 command line. If no callsigns are specified then a sorted list of all
1898 the non-user callsigns known to the system will be displayed.
1900 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
1901 This command takes the <callsign> (which can be a full or partial
1902 callsign or a prefix), looks up which internal country number
1903 it is and then displays all the relevant prefixes for that country
1904 together with the internal country no, the CQ and ITU regions.
1908 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
1909 Show the name and location where every program module was load from. This
1910 is useful for checking where you think you have loaded a .pm file from.
1912 === 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
1913 === 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
1914 This is a multipurpose command that allows you either to calculate the
1915 distance and bearing between two locators or (if only one locator is
1916 given on the command line) the distance and beraing from your station
1917 to the locator. For example:-
1922 The first example will show the distance and bearing to the locator from
1923 yourself, the second example will calculate the distance and bearing from
1924 the first locator to the second. You can use 4 or 6 character locators.
1926 It is also possible to convert a latitude and longitude to a locator by
1927 using this command with a latitude and longitude as an argument, for
1930 SH/QRA 52 41 N 0 58 E
1932 === 0^SHOW/QRZ <callsign>^Show any callbook details on a callsign
1933 This command queries the QRZ callbook server on the internet
1934 and returns any information available for that callsign. This service
1935 is provided for users of this software by http://www.qrz.com
1937 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
1939 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
1940 This command allows you to see to which node the callsigns specified are
1941 connected. It is a sort of inverse sh/config.
1945 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
1946 Show the tracking data from your location to the satellite of your choice
1947 from now on for the next few hours.
1949 If you use this command without a satellite name it will display a list
1950 of all the satellites known currently to the system.
1952 If you give a name then you can obtain tracking data of all the passes
1953 that start and finish 5 degrees below the horizon. As default it will
1954 give information for the next three hours for every five minute period.
1956 You can alter the number of hours and the step size, within certain
1959 Each pass in a period is separated with a row of '-----' characters
1964 SH/SAT FENGYUN1 12 2
1966 === 6^SHOW/STATION ALL [<regex>]^Show list of users in the system
1967 === 0^SHOW/STATION [<callsign> ..]^Show information about a callsign
1968 Show the information known about a callsign and whether (and where)
1969 that callsign is connected to the cluster.
1973 If no callsign is given then show the information for yourself.
1975 === 0^SHOW/SUN [ndays] [<prefix>|<callsign>]^Show sun rise and set times
1976 Show the sun rise and set times for a (list of) prefixes or callsigns,
1977 together with the azimuth and elevation of the sun currently at those
1980 If you don't specify any prefixes or callsigns, it will show the times for
1981 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1982 together with the current azimuth and elevation.
1984 If all else fails it will show the sunrise and set times for the node
1985 that you are connected to.
1990 SH/SUN G1TLH K9CW ZS
1992 You can also use this command to see into the past or the future, so
1993 if you want to see yesterday's times then do:-
1997 or in three days time:-
2001 Upto 366 days can be checked both in the past and in the future.
2003 Please note that the rise and set times are given as the UT times of rise
2004 and set on the requested UT day.
2006 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
2007 If no prefixes or callsigns are given then this command returns the local
2008 time and UTC as the computer has it right now. If you give some prefixes
2009 then it will show UTC and UTC + the local offset (not including DST) at
2010 the prefixes or callsigns that you specify.
2012 === 0^SHOW/VHFSTATS^Show the VHF DX Statistics for last 31 days
2013 Show the VHF DX spots breakdown by band for the last 31 days
2015 === 0^SHOW/VHFTABLE^Show the VHF DX Spotter Table for your country
2016 Show the VHF DX Spotter table for your country for the last 31 days
2018 === 0^SHOW/WCY^Show last 10 WCY broadcasts
2019 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
2020 Display the most recent WCY information that has been received by the system
2022 === 0^SHOW/WWV^Show last 10 WWV broadcasts
2023 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
2024 Display the most recent WWV information that has been received by the system
2026 === 5^SHUTDOWN^Shutdown the cluster
2027 Shutdown the cluster and disconnect all the users
2029 === 9^SPOOF <call> <command>^Do a command as though you are another user
2030 This command is provided so that sysops can set a user's parameters without
2031 me having to write a special 'sysop' version for every user command. It
2032 allows you to pretend that you are doing the command as the user you specify.
2036 SPOOF G1TLH set/name Dirk
2037 SPOOF G1TLH set/qra JO02LQ
2039 === 5^STAT/DB <dbname>^Show the status of a database
2040 Show the internal status of a database descriptor.
2042 Depending on your privilege level you will see more or less information.
2043 This command is unlikely to be of much use to anyone other than a sysop.
2045 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
2046 Show the internal status of the channel object either for the channel that
2047 you are on or else for the callsign that you asked for.
2049 Only the fields that are defined (in perl term) will be displayed.
2051 === 1^STAT/MSG^Show the status of the message system
2052 === 1^STAT/MSG <msgno>^Show the status of a message
2053 This command shows the internal status of a message and includes information
2054 such as to whom it has been forwarded, its size, origin etc etc.
2056 If no message number is given then the status of the message system is
2059 === 5^STAT/ROUTE_NODE <callsign>^Show the data in a Route::Node object
2060 === 5^STAT/ROUTE_NODE all^Show list of all Route::Node objects
2062 === 5^STAT/ROUTE_USER <callsign>^Show the data in a Route::User object
2063 === 5^STAT/ROUTE_USER all^Show list of all Route::User objects
2065 === 5^STAT/USER [<callsign>]^Show the full status of a user
2066 Shows the full contents of a user record including all the secret flags
2069 Only the fields that are defined (in perl term) will be displayed.
2071 === 0^SYSOP^Regain your privileges if you login remotely
2072 The system automatically reduces your privilege level to that of a
2073 normal user if you login in remotely. This command allows you to
2074 regain your normal privilege level. It uses the normal system: five
2075 numbers are returned that are indexes into the character array that is
2076 your assigned password (see SET/PASSWORD). The indexes start from
2079 You are expected to return a string which contains the characters
2080 required in the correct order. You may intersperse those characters
2081 with others to obscure your reply for any watchers. For example (and
2082 these values are for explanation :-):
2084 password = 012345678901234567890123456789
2088 aa2bbbb0ccc5ddd7xxx3n
2092 They will all match. If there is no password you will still be offered
2093 numbers but nothing will happen when you input a string. Any match is
2096 === 0^TALK <call> [<text>]^Send a text message to another station
2097 === 0^TALK <call> > <node> [<text>]^Send a text message to another station via a node
2098 Send a short message to any other station that is visible on the cluster
2099 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2100 command, they don't have to be connected locally.
2102 The second form of TALK is used when other cluster nodes are connected
2103 with restricted information. This usually means that they don't send
2104 the user information usually associated with logging on and off the cluster.
2106 If you know that G3JNB is likely to be present on GB7TLH, but you can only
2107 see GB7TLH in the SH/C list but with no users, then you would use the
2108 second form of the talk message.
2110 If you want to have a ragchew with someone you can leave the text message
2111 out and the system will go into 'Talk' mode. What this means is that a
2112 short message is sent to the recipient telling them that you are in a
2113 'Talking' frame of mind and then you just type - everything you send will
2114 go to the station that you asked for.
2116 All the usual announcements, spots and so on will still come out on your
2119 If you want to do something (such as send a spot) you preceed the normal
2120 command with a '/' character, eg:-
2122 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2125 To leave talk mode type:
2129 If you are in 'Talk' mode, there is an extention to the '/' command which
2130 allows you to send the output to all the people you are talking to. You do
2131 with the '//' command. For example:-
2135 will send the hftable as you have it to all the people you are currently
2138 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
2139 Type out the contents of a file in a filearea. So, for example, in
2140 filearea 'bulletins' you want to look at file 'arld051' you would
2142 TYPE bulletins/arld051
2144 See also SHOW/FILES to see what fileareas are available and a
2147 === 0^WHO^Show who is physically connected
2148 This is a quick listing that shows which callsigns are connected and
2149 what sort of connection they have
2151 === 0^WX <text>^Send a weather message to local users
2152 === 0^WX FULL <text>^Send a weather message to all cluster users
2153 === 5^WX SYSOP <text>^Send a weather message to other clusters only
2154 Weather messages can sometimes be useful if you are experiencing an extreme
2155 that may indicate enhanced conditions