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^ANNOUNCE <text>^Send an announcement to LOCAL users only
16 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
17 This will send your announcement cluster wide
19 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
22 <text> is the text of the announcement you wish to broadcast
24 === 0^APROPOS <string>^Search help database for <string>
25 Search the help database for <string> (it isn't case sensitive), and print
26 the names of all the commands that may be relevant.
28 === 0^BYE^Exit from the cluster
29 This will disconnect you from the cluster
31 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
32 Start a connection process that will culminate in a new connection to the
33 DX cluster <callsign>. This process creates a new 'client' process which will
34 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
35 necessary to traverse the network(s) to logon to the cluster <callsign>.
37 === 9^CATCH <node call> All|[<msgno> ...]^Mark a message as sent
38 === 9^UNCATCH <node call> All|[msgno> ...]^Unmark a message as sent
39 When you send messages the fact that you have forwarded it to another node
40 is remembered so that it isn't sent again. When you have a new partner
41 node and you add their callsign to your /spider/msg/forward.pl file, all
42 outstanding non-private messages will be forwarded to them. This may well
43 be ALL the non-private messages. You can prevent this by using these
47 catch GB7DJK 300 301 302 303
49 and to undo what you have just done:-
52 uncatch GB7DJK 300 301 302 303
54 which will arrange for them to be forward candidates again.
56 === 9^DEBUG^Set the cluster program into debug mode
57 Executing this command will only have an effect if you are running the cluster
62 It will interrupt the cluster just after the debug command has finished.
63 === 0^DIRECTORY^List messages
64 === 0^DIRECTORY ALL^List all messages
65 === 0^DIRECTORY OWN^List your own messages
66 === 0^DIRECTORY NEW^List all new messages
67 === 0^DIRECTORY TO <call>^List all messages to <call>
68 === 0^DIRECTORY FROM <call>^List all messages from <call>
69 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
70 === 0^DIRECTORY <nn>^List last <nn> messages
71 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
72 List the messages in the messages directory.
74 If there is a 'p' one space after the message number then it is a
75 personal message. If there is a '-' between the message number and the
76 'p' then this indicates that the message has been read.
78 You can use shell escape characters such as '*' and '?' in the <call>
81 You can combine some of the various directory commands together eg:-
85 DIR SUBJECT IOTA 200-250
87 You can abbreviate all the commands to one letter and use ak1a syntax:-
93 Sysops can see all users' messages.
95 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
96 Disconnect any <call> connected locally
98 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
99 This is how you send a DX Spot to other users. You can, in fact, now
100 enter the <freq> and the <call> either way round.
106 will all give the same result. You can add some remarks to the end
107 of the command and they will be added to the spot.
109 DX FR0G 144600 this is a test
111 You can credit someone else by saying:-
113 DX by G1TLH FR0G 144.600 he isn't on the cluster
115 The <freq> is compared against the available bands set up in the
116 cluster. See SHOW/BANDS for more information.
118 === 1^FORWARD/OPERNAME <call>^Send out information on this <call> to all clusters
119 This command sends out any information held in the user file which can
120 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
121 and Homenode. PC41s are only sent for the information that is available.
123 === 0^HELP^The HELP Command
124 HELP is available for a number of commands. The syntax is:-
128 Where <cmd> is the name of the command you want help on.
130 All commands can be abbreviated, so SHOW/DX can be abbreviated
131 to SH/DX, ANNOUNCE can be shortened to AN and so on.
133 Look at the APROPOS <string> command which will search the help database
134 for the <string> you specify and give you a list of likely commands
135 to look at with HELP.
137 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
138 Delete a message from the local system. You will only be able to delete messages
139 that you have originated or been sent (unless you are the sysop).
141 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
142 Delete a message (usually a 'bulletin') from the whole cluster system.
144 This uses the subject field, so any messages that have exactly the same subject
145 will be deleted. Beware!
147 === 9^LOAD/ALIASES^Reload the command alias table
148 Reload the /spider/cmd/Aliases file after you have editted it. You will need to
149 do this if you change this file whilst the cluster is running in order for the
150 changes to take effect.
152 === 9^LOAD/BANDS^Reload the band limits table
153 Reload the /spider/data/bands.pl file if you have changed it manually whilst
154 the cluster is running.
156 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
157 Normally, if you change a command file in the cmd or local_cmd tree it will
158 automatially be picked up by the cluster program. Sometimes it can get confused
159 if you are doing a lot of moving commands about or delete a command in the
160 local_cmd tree and want to use the normal one again. Execute this command to
161 reset everything back to the state it was just after a cluster restart.
163 === 9^LOAD/MESSAGES^Reload the system messages file
164 If you change the /spider/perl/Messages file (usually whilst fiddling/writing new
165 commands) you can have them take effect during a cluster session by executing this
166 command. You need to do this if get something like :-
168 unknown message 'xxxx' in lang 'en'
170 === 9^LOAD/PREFIXES^Reload the prefix table
171 Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst
172 the cluster is running.
174 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
175 MERGE allows you to bring your spot and wwv database up to date. By default
176 it will request the last 10 spots and 5 WWVs from the node you select. The
177 node must be connected locally.
179 You can request any number of spots or wwv and although they will be appended
180 to your databases they will not duplicate any that have recently been added
181 (the last 2 days for spots and last month for WWV data).
183 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
184 Alter message parameters like To, From, Subject, whether private or bulletin
185 or return receipt (RR) is required or whether to keep this message from timing
188 MSG TO <msgno> <call> - change TO callsign to <call>
189 MSG FRom <msgno> <call> - change FROM callsign to <call>
190 MSG PRrivate <msgno> - set private flag
191 MSG NOPRrivate <msgno> - unset private flag
192 MSG RR <msgno> - set RR flag
193 MSG NORR <msgno> - unset RR flag
194 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
195 MSG NOKEep <msgno> - unset the keep flag
196 MSG SUbject <msgno> <new> - change the subject to <new>
197 MSG WAittime <msgno> - remove any waitting time for this message
198 MSG QUeue - queue any outstanding bulletins
199 MSG QUeue 1 - queue any outstanding private messages
201 You can look at the status of a message by using:-
205 This will display more information on the message than DIR does.
207 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
208 Send some arbitrary text to a locally connected callsign. No processing is done on
209 the text. This command allows you to send PC Protocol to unstick things if problems
210 arise (messages get stuck etc). eg:-
211 pc gb7djk PC33^GB7TLH^GB7DJK^400^
213 pc G1TLH Try doing that properly!!!
215 === 1^PING <node>^Send a ping command to another cluster
216 This command is used to estimate the quality of the link to another cluster.
217 The time returned is the length of time taken for a PC51 to go to another
218 cluster and be returned.
220 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
221 You can get rid of any message to or originating from your callsign using
222 this command. You can remove more than one message at a time.
224 === 5^KILL <from>-<to>^Remove a range of messages from the system
225 === 5^KILL FROM <call>^Remove all messages from a callsign
226 === 5^KILL TO <call>^Remove all messages to a callsign
227 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
228 Remove this message from the entire cluster system as well as your node.
231 As a sysop you can kill any message on the system.
233 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
234 Send any text you like to the callsign requested. This is used mainly to send
235 PC protocol to connected nodes either for testing or to unstick things.
237 You can also use in the same way as a talk command to a connected user but
238 without any processing, added of "from <blah> to <blah" or whatever.
240 === 1^PING <node call>^Find out the delays an a circuit to another node
241 This command will enable sysops to determine the speed of an inter-cluster
244 Any visible cluster node can be PINGed.
246 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
247 This command allows you to send nearly any command to another DX Cluster
248 node that is connected to the system.
250 Whether you get any output is dependant on a) whether the other system knows
251 that the node callsign of this cluster is in fact a node b) whether the
252 other system is allowing RCMDs from this node and c) whether you have
253 permission to send this command at all.
255 === 0^READ^Read the next unread personal message addressed to you
256 === 0^READ <msgno>^Read the specified message
257 You can read any messages that are sent as 'non-personal' and also any
258 message either sent by or sent to your callsign.
261 As a sysop you may read any message on the system
263 === 0^REPLY^Reply (privately) to the last message that you have read
264 === 0^REPLY <msgno>^Reply (privately) to the specified message
265 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
266 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
267 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
268 You can reply to a message and the subject will automatically have
269 "Re:" inserted in front of it, if it isn't already present.
271 You can also use all the extra qualifiers such as RR, PRIVATE,
272 NOPRIVATE, B that you can use with the SEND command (see SEND
275 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
276 === 0^SEND RR <call>^Send a message and ask for a read receipt
277 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
278 === 0^SEND PRIVATE <call>^Send a personal message
279 === 0^SEND NOPRIVATE <call>^Send a message to all stations
280 All the SEND commands will create a message which will be sent either to
281 an individual callsign or to one of the 'bulletin' addresses.
283 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
284 it will mark the message as personal and send it to the cluster node that
285 that callsign is connected to.
287 You can have more than one callsign in all of the SEND commands.
289 You can have multiple qualifiers so that you can have for example:-
291 SEND RR COPY 123 PRIVATE G1TLH G0RDI
293 which should send a copy of message 123 to G1TLH and G0RDI and you will
294 receive a read receipt when they have read the message.
296 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
297 SP is an alias for SEND PRIVATE
299 === 0^SET/ADDRESS <your address>^Record your postal address
301 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
302 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
304 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
305 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
307 === 9^SET/DEBUG <name>^Add a debug level to the debug set
308 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
310 === 0^SET/DX^Allow DX messages to come out on your terminal
311 === 0^UNSET/DX^Stop DX messages coming out on your terminal
313 === 0^SET/HERE^Tell the system you are present at your terminal
314 === 0^UNSET/HERE^Tell the system you are absent from your terminal
316 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
317 Tell the cluster system where you normally connect to. Any Messages sent
318 to you will normally find their way there should you not be connected.
322 === 9^SET/ISOLATE^Isolate a node from the rest of the network
323 Connect a node to your system in such a way that you are a full protocol
324 member of its network and can see all spots on it, but nothing either leaks
325 out from it nor goes back into from the rest of the nodes connected to you.
327 You can potentially connect several nodes in this way.
329 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
330 Remove isolation from a node - SET/ISOLATE
332 === 0^SET/LANGUAGE <lang>^Set the language you want to use
333 You can select the language that you want the cluster to use. Currently
334 the languages available are en (english) and nl (dutch).
336 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
337 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
338 In order to get accurate headings and such like you must tell the system
339 what your latitude and longitude is. If you have not yet done a SET/QRA
340 then this command will set your QRA locator for you. For example:-
341 SET/LOCATION 52 22 N 0 57 E
343 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
344 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
346 === 0^SET/NAME <your name>^Set your name
347 Tell the system what your name is eg:-
350 === 9^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
351 Tell the system that the call(s) are to be treated as AK1A cluster and
352 fed PC Protocol rather normal user commands.
354 === 0^SET/PAGE <lines per page>^Set the lines per page
355 Tell the system how many lines you wish on a page when the number of line
356 of output from a command is more than this. The default is 20. Setting it
357 explicitly to 0 will disable paging.
361 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
362 Set the privilege level on a callsign. The privilege levels that pertain
363 to commands are as default:-
365 1 - allow remote nodes normal user RCMDs
366 5 - various privileged commands (including shutdown, but not disc-
367 connect), the normal level for another node.
368 8 - more privileged commands (including disconnect)
369 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
371 If you are a sysop and you come in as a normal user on a remote connection
372 your privilege will automatically be set to 0.
374 === 9^SET/PASSWORD <callsign> <string>^Set a users password
375 The password for a user can only be set by a full sysop. The string
376 can contain any characters but any spaces are removed (you can type in
377 spaces - but they won't appear in the password). You can see the
378 result with STAT/USER.
380 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
381 === 0^SET/QRA <locator>^Set your QRA locator
382 Tell the system what your QRA (or Maidenhead) locator is. If you have not
383 done a SET/LOCATION then your latitude and longitude will be set roughly
384 correctly (assuming your locator is correct ;-). For example:-
387 === 0^SET/QTH <your qth>^Set your QTH
388 Tell the system where you are. For example:-
389 SET/QTH East Dereham, Norfolk
391 === 0^SET/TALK^Allow TALK messages to come out on your terminal
392 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
394 === 0^SET/WWV^Allow WWV messages to come out on your terminal
395 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
397 === 0^SET/WX^Allow WX messages to come out on your terminal
398 === 0^UNSET/WX^Stop WX messages coming out on your terminal
400 === 0^SHOW/DX^Interrogate the spot database
401 If you just type SHOW/DX you will get the last so many spots
402 (sysop configurable, but usually 10).
404 In addition you can add any number of these commands in very nearly
405 any order to the basic SHOW/DX command, they are:-
407 on <band> - eg 160m 20m 2m 23cm 6mm
408 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
410 <number> - the number of spots you want
411 <from>-<to> - <from> spot no <to> spot no in the selected list
413 <prefix> - for a spotted callsign beginning with <prefix>
414 *<suffix> - for a spotted callsign ending in <suffix>
415 *<string>* - for a spotted callsign containing <string>
417 day <number> - starting <number> days ago
418 day <from>-<to> - <from> days <to> days ago
420 info <text> - any spots containing <text> in the info or remarks
422 by <call> - any spots spotted by <call> (spotter <call> is the
425 qsl - this automatically looks for any qsl info on the call
426 held in the spot database.
428 iota [<iota>] - If the iota island number is missing it will look for
429 the string iota and anything which looks like an iota
430 island number. If you specify then it will look for
433 qra [<locator>] - this will look for the specific locator if you specify
434 one or else anything that looks like a locator.
439 SH/DX on 20m info iota
440 SH/DX 9a on vhf day 30
446 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
447 This command takes the <prefix> (which can be a full or partial
448 callsign if desired), looks up which internal country number it is
449 and then displays all the spots as per SH/DX for that country.
451 The options for SHOW/DX also apply to this command.
455 SH/DXCC W on 20m info iota
457 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
458 SHOW/FILES on its own will show you a list of the various fileareas
459 available on the system. To see the contents of a particular file
462 where <filearea> is the name of the filearea you want to see the
465 You can also use shell globbing characters like '*' and '?' in a
466 string to see a selection of files in a filearea eg:-
467 SH/FILES bulletins arld*
469 See also TYPE - to see the contents of a file.
471 === 0^SHOW/MUF <prefix> [<hours>]^Show the likely propagation to a prefix
472 This command allow you to estimate the likelihood of you contacting
473 a station with the prefix you have specified. The output assumes a modest
474 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
476 The result predicts the most likely operating frequencies and signal
477 levels for high frequency (shortwave) radio propagation paths on
478 specified days of the year and hours of the day. It is most useful for
479 paths between 250 km and 6000 km, but can be used with reduced accuracy
480 for paths shorter or longer than this.
482 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
483 used to predict the MUF given the predicted flux, day of the year,
484 hour of the day and geographic coordinates of the transmitter and
485 receiver. This routine is reasonably accurate for the purposes here,
486 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
487 than the programs used by major shortwave broadcasting organizations,
488 such as the Voice of America.
490 The command will display some header information detailing its
491 assumptions, together with the locations, latitude and longitudes and
492 bearings. It will then show UTC (UT), local time at the other end
493 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
494 (Zen) and the likely signal strengths. Then for each frequency for which
495 the system thinks there is a likelihood of a circuit it prints a value.
497 The value is currently a likely S meter reading based on the conventional
498 6dB / S point scale. If the value has a '+' appended it means that it is
499 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
500 there is likely to be much fading and by an 's' that the signal is likely
503 By default SHOW/MUF will show the next two hours worth of data. You
504 can specify anything up to 24 hours worth of data by appending the no of
505 hours required after the prefix. For example:-
511 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
512 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
513 Location Lat / Long Azim
514 East Dereham, Norfolk 52 41 N 0 57 E 47
515 United-States-W 43 0 N 87 54 W 299
516 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
517 18 23 11.5 -35 mS0+ mS2 S3
518 19 0 11.2 -41 mS0+ mS2 S3
520 indicating that you will have weak, fading circuits on top band and
521 80m but usable signals on 40m (about S3).
527 will get you the above display, but with the next 24 hours worth of
530 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
531 This command takes the <callsign> (which can be a full or partial
532 callsign or a prefix), looks up which internal country number
533 it is and then displays all the relevant prefixes for that country
534 together with the internal country no, the CQ and ITU regions.
538 === 0^SHOW/PROGRAM^Show the locations of all the included program modules
539 Show the name and location where every program module was load from. This
540 is useful for checking where you think you have loaded a .pm file from.
542 === 0^SHOW/WWV^Show last 10 WWV broadcasts
543 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
544 Display the most recent WWV information that has been received by the system
546 === 5^SHUTDOWN^Shutdown the cluster
547 Shutdown the cluster and disconnect all the users
549 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
550 Show the internal status of the channel object either for the channel that
551 you are on or else for the callsign that you asked for.
553 Only the fields that are defined (in perl term) will be displayed.
555 === 5^STAT/USER [<callsign>]^Show the full status of a user
556 Shows the full contents of a user record including all the secret flags
559 Only the fields that are defined (in perl term) will be displayed.
561 === 0^SYSOP^Regain your privileges if you login remotely
562 The system automatically reduces your privilege level to that of a
563 normal user if you login in remotely. This command allows you to
564 regain your normal privilege level. It uses the normal system: five
565 numbers are returned that are indexes into the character array that is
566 your assigned password (see SET/PASSWORD). The indexes start from
569 You are expected to return a string which contains the characters
570 required in the correct order. You may intersperse those characters
571 with others to obscure your reply for any watchers. For example (and
572 these values are for explanation :-):
574 password = 012345678901234567890123456789
578 aa2bbbb0ccc5ddd7xxx3n
582 They will all match. If there is no password you will still be offered
583 numbers but nothing will happen when you input a string. Any match is
586 === 0^TALK <call> <text>^Send a text message to another station
587 === 0^TALK <call> > <node> <text>^Send a text message to another station via a node
588 Send a short message to any other station that is visible on the cluster
589 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
590 command, they don't have to be connected locally.
592 The second form of TALK is used when other cluster nodes are connected
593 with restricted information. This usually means that they don't send
594 the user information usually associated with logging on and off the cluster.
596 If you know that G3JNB is likely to be present on GB7TLH, but you can only
597 see GB7TLH in the SH/C list but with no users, then you would use the
598 second form of the talk message.
600 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
601 Type out the contents of a file in a filearea. So, for example, in
602 filearea 'bulletins' you want to look at file 'arld051' you would
604 TYPE bulletins/arld051
606 See also SHOW/FILES to see what fileareas are available and a
609 === 0^WHO^Show who is physically connected
610 This is a quick listing that shows which callsigns are connected and
611 what sort of connection they have
613 === 0^WX <text>^Send a weather message to local users
614 === 0^WX FULL <text>^Send a weather message to all cluster users
615 === 5^WX SYSOP <text>^Send a weather message to other clusters only
616 Weather messages can sometimes be useful if you are experiencing an extreme
617 that may indicate enhanced conditions