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
15 <text> is the text of the announcement you wish to broadcast
17 === 0^ANNOUNCE FULL <text>^Send an announcement cluster wide
18 This will send your announcement cluster wide
20 === 5^ANNOUNCE SYSOP <text>^Send an announcement to Sysops only
22 === 0^APROPOS <string>^Search help database for <string>
23 Search the help database for <string> (it isn't case sensitive), and print
24 the names of all the commands that may be relevant.
26 === 0^BYE^Exit from the cluster
27 This will disconnect you from the cluster
29 === 5^CONNECT <callsign>^Start a connection to another DX Cluster
30 Start a connection process that will culminate in a new connection to the
31 DX cluster <callsign>. This process creates a new 'client' process which will
32 use the script in /spider/connect/<callsign> to effect the 'chat' exchange
33 necessary to traverse the network(s) to logon to the cluster <callsign>.
35 === 9^CATCH <node call> All|[<msgno> ...]^Mark a message as sent
36 === 9^UNCATCH <node call> All|[msgno> ...]^Unmark a message as sent
37 When you send messages the fact that you have forwarded it to another node
38 is remembered so that it isn't sent again. When you have a new partner
39 node and you add their callsign to your /spider/msg/forward.pl file, all
40 outstanding non-private messages will be forwarded to them. This may well
41 be ALL the non-private messages. You can prevent this by using these
45 catch GB7DJK 300 301 302 303
47 and to undo what you have just done:-
50 uncatch GB7DJK 300 301 302 303
52 which will arrange for them to be forward candidates again.
54 === 0^DBAVAIL^Show a list of all the Databases in the system
55 Title says it all really, this command lists all the databases defined
56 in the system. It is also aliased to SHOW/COMMAND.
58 === 9^DBCREATE <name>^Create a database entry
59 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
60 === 9^DBCREATE <name> remote <node>^Create a remote database entry
61 DBCREATE allows you to define a database in the system. It doesn't actually
62 create anything, just defines it.
64 The databases that are created are simple DB_File hash databases, they are
65 therefore already 'indexed'.
67 You can define a local database with the first form of the command eg:
71 You can also chain databases with the addition of the 'chain' keyword.
72 This will search each database one after the other. A typical example
75 DBCREATE sdx_qsl chain sql_ad
77 No checking is done to see if the any of the chained databases exist, in
78 fact it is usually better to do the above staement first then do each of
79 the chained databases.
81 Databases can exist offsite. To define a database that lives on another
84 DBCREATE buckmaster remote gb7dxc
86 Remote databases cannot be chained; however, the last database in a
87 a chain can be a remote database eg:
89 DBCREATE qsl chain gb7dxc
91 To see what databases have been defined do:
93 DBAVAIL (or it will have been aliased to SHOW/COMMAND)
95 It would be normal for you to add an entry into your local Aliases file
96 to allow people to use the 'SHOW/<dbname>' style syntax. So you would
97 need to add a line like:-
102 '^sh\w*/buc', 'dbshow buckmaster', 'dbshow',
111 to work as they may be used to.
113 See DBIMPORT for the importing of existing AK1A format data to databases.
114 See DBSHOW for generic database enquiry
116 === 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
117 If you want to import or update data in bulk to a database you can use
118 this command. It will either create or update entries into an existing
119 database. For example:-
121 DBIMPORT oblast /tmp/OBLAST.FUL
123 will import the standard OBLAST database that comes with AK1A into the
124 oblast database held locally.
126 === 9^DBREMOVE <dbname>^Delete a database
127 DBREMOVE will completely remove a database entry and also delete any data
128 file that is associated with it.
130 There is no warning, no comeback, no safety net.
136 will remove the oblast database from the system and it will also remove
137 the associated datafile.
141 There is no warning, no comeback, no safety net.
143 You have been warned.
145 === 0^DBSHOW <dbname> <key>^Display an entry, if it exists, in a database
146 This is the generic user interface to the database to the database system.
147 It is expected that the sysop will add an entry to the local Aliases file
148 so that users can use the more familiar AK1A style of enquiry such as:
152 but if he hasn't and the database really does exist (use DBAVAIL or
153 SHOW/COMMAND to find out) you can do the same thing with:
157 === 9^DEBUG^Set the cluster program into debug mode
158 Executing this command will only have an effect if you are running the cluster
163 It will interrupt the cluster just after the debug command has finished.
164 === 0^DIRECTORY^List messages
165 === 0^DIRECTORY ALL^List all messages
166 === 0^DIRECTORY OWN^List your own messages
167 === 0^DIRECTORY NEW^List all new messages
168 === 0^DIRECTORY TO <call>^List all messages to <call>
169 === 0^DIRECTORY FROM <call>^List all messages from <call>
170 === 0^DIRECTORY SUBJECT <string>^List all messages with <string> in subject
171 === 0^DIRECTORY <nn>^List last <nn> messages
172 === 0^DIRECTORY <from>-<to>^List messages <from> message <to> message
173 List the messages in the messages directory.
175 If there is a 'p' one space after the message number then it is a
176 personal message. If there is a '-' between the message number and the
177 'p' then this indicates that the message has been read.
179 You can use shell escape characters such as '*' and '?' in the <call>
182 You can combine some of the various directory commands together eg:-
186 DIR SUBJECT IOTA 200-250
188 You can abbreviate all the commands to one letter and use ak1a syntax:-
194 Sysops can see all users' messages.
196 === 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
197 Disconnect any <call> connected locally
199 === 0^DX [BY <call>] <freq> <call> <remarks>^Send a DX spot
200 This is how you send a DX Spot to other users. You can, in fact, now
201 enter the <freq> and the <call> either way round.
207 will all give the same result. You can add some remarks to the end
208 of the command and they will be added to the spot.
210 DX FR0G 144600 this is a test
212 You can credit someone else by saying:-
214 DX by G1TLH FR0G 144.600 he isn't on the cluster
216 The <freq> is compared against the available bands set up in the
217 cluster. See SHOW/BANDS for more information.
219 === 9^EXPORT <msgno> <filename>^Export a message to a file
220 Export a message to a file. This command can only be executed on a local
221 console with a fully privileged user. The file produced will be in a form
222 ready to be imported back into the cluster by placing it in the import
223 directory (/spider/msg/import).
225 This command cannot overwrite an existing file. This is to provide some
226 measure of security. Any files written will owned by the same user as the
227 main cluster, otherwise you can put the new files anywhere the cluster can
228 access. For example:-
233 === 1^FORWARD/OPERNAME <call>^Send out information on this <call> to all clusters
234 This command sends out any information held in the user file which can
235 be broadcast in PC41 protocol packets. This information is Name, QTH, Location
236 and Homenode. PC41s are only sent for the information that is available.
238 === 0^HELP^The HELP Command
239 HELP is available for a number of commands. The syntax is:-
243 Where <cmd> is the name of the command you want help on.
245 All commands can be abbreviated, so SHOW/DX can be abbreviated
246 to SH/DX, ANNOUNCE can be shortened to AN and so on.
248 Look at the APROPOS <string> command which will search the help database
249 for the <string> you specify and give you a list of likely commands
250 to look at with HELP.
252 === 0^KILL <msgno> [<msgno..]^Delete a message from the local system
253 Delete a message from the local system. You will only be able to delete messages
254 that you have originated or been sent (unless you are the sysop).
256 === 5^KILL FULL <msgno> [<msgno..]^Delete a message from the whole cluster
257 Delete a message (usually a 'bulletin') from the whole cluster system.
259 This uses the subject field, so any messages that have exactly the same subject
260 will be deleted. Beware!
262 === 0^LINKS^Show which nodes is physically connected
263 This is a quick listing that shows which links are connected and
264 some information about them. See WHO for a list of all connections.
266 === 9^LOAD/ALIASES^Reload the command alias table
267 Reload the /spider/cmd/Aliases file after you have editted it. You will need to
268 do this if you change this file whilst the cluster is running in order for the
269 changes to take effect.
271 === 9^LOAD/BANDS^Reload the band limits table
272 Reload the /spider/data/bands.pl file if you have changed it manually whilst
273 the cluster is running.
275 === 9^LOAD/CMD_CACHE^Reload the automatic command cache
276 Normally, if you change a command file in the cmd or local_cmd tree it will
277 automatially be picked up by the cluster program. Sometimes it can get confused
278 if you are doing a lot of moving commands about or delete a command in the
279 local_cmd tree and want to use the normal one again. Execute this command to
280 reset everything back to the state it was just after a cluster restart.
282 === 9^LOAD/MESSAGES^Reload the system messages file
283 If you change the /spider/perl/Messages file (usually whilst fiddling/writing new
284 commands) you can have them take effect during a cluster session by executing this
285 command. You need to do this if get something like :-
287 unknown message 'xxxx' in lang 'en'
289 === 9^LOAD/PREFIXES^Reload the prefix table
290 Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst
291 the cluster is running.
293 === 5^MERGE <node> [<no spots>/<no wwv>]^Ask for the latest spots and WWV
294 MERGE allows you to bring your spot and wwv database up to date. By default
295 it will request the last 10 spots and 5 WWVs from the node you select. The
296 node must be connected locally.
298 You can request any number of spots or wwv and although they will be appended
299 to your databases they will not duplicate any that have recently been added
300 (the last 2 days for spots and last month for WWV data).
302 === 9^MSG <cmd> <msgno> [data ... ]^Alter various message parameters
303 Alter message parameters like To, From, Subject, whether private or bulletin
304 or return receipt (RR) is required or whether to keep this message from timing
307 MSG TO <msgno> <call> - change TO callsign to <call>
308 MSG FRom <msgno> <call> - change FROM callsign to <call>
309 MSG PRrivate <msgno> - set private flag
310 MSG NOPRrivate <msgno> - unset private flag
311 MSG RR <msgno> - set RR flag
312 MSG NORR <msgno> - unset RR flag
313 MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
314 MSG NOKEep <msgno> - unset the keep flag
315 MSG SUbject <msgno> <new> - change the subject to <new>
316 MSG WAittime <msgno> - remove any waitting time for this message
317 MSG NOREad <msgno> - mark message as unread
318 MSG REad <msgno> - mark message as read
319 MSG QUeue - queue any outstanding bulletins
320 MSG QUeue 1 - queue any outstanding private messages
322 You can look at the status of a message by using:-
326 This will display more information on the message than DIR does.
328 === 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
329 Send some arbitrary text to a locally connected callsign. No processing is done on
330 the text. This command allows you to send PC Protocol to unstick things if problems
331 arise (messages get stuck etc). eg:-
332 pc gb7djk PC33^GB7TLH^GB7DJK^400^
334 pc G1TLH Try doing that properly!!!
336 === 1^PING <node>^Send a ping command to another cluster
337 This command is used to estimate the quality of the link to another cluster.
338 The time returned is the length of time taken for a PC51 to go to another
339 cluster and be returned.
341 === 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
342 You can get rid of any message to or originating from your callsign using
343 this command. You can remove more than one message at a time.
345 === 5^KILL <from>-<to>^Remove a range of messages from the system
346 === 5^KILL FROM <call>^Remove all messages from a callsign
347 === 5^KILL TO <call>^Remove all messages to a callsign
348 === 5^KILL FULL <msgno> [<msgno]^Remove a message from the entire cluster
349 Remove this message from the entire cluster system as well as your node.
352 As a sysop you can kill any message on the system.
354 === 8^PC <call> <text>^Send arbitrary text to a connected callsign
355 Send any text you like to the callsign requested. This is used mainly to send
356 PC protocol to connected nodes either for testing or to unstick things.
358 You can also use in the same way as a talk command to a connected user but
359 without any processing, added of "from <blah> to <blah" or whatever.
361 === 1^PING <node call>^Find out the delays an a circuit to another node
362 This command will enable sysops to determine the speed of an inter-cluster
365 Any visible cluster node can be PINGed.
367 === 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
368 This command allows you to send nearly any command to another DX Cluster
369 node that is connected to the system.
371 Whether you get any output is dependant on a) whether the other system knows
372 that the node callsign of this cluster is in fact a node b) whether the
373 other system is allowing RCMDs from this node and c) whether you have
374 permission to send this command at all.
376 === 0^READ^Read the next unread personal message addressed to you
377 === 0^READ <msgno>^Read the specified message
378 You can read any messages that are sent as 'non-personal' and also any
379 message either sent by or sent to your callsign.
382 As a sysop you may read any message on the system
384 === 0^REPLY^Reply (privately) to the last message that you have read
385 === 0^REPLY <msgno>^Reply (privately) to the specified message
386 === 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
387 === 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
388 === 0^REPLY RR <msgno>^Reply to the specified message with read receipt
389 You can reply to a message and the subject will automatically have
390 "Re:" inserted in front of it, if it isn't already present.
392 You can also use all the extra qualifiers such as RR, PRIVATE,
393 NOPRIVATE, B that you can use with the SEND command (see SEND
396 === 0^SEND <call> [<call> ...]^Send a message to one or more callsigns
397 === 0^SEND RR <call>^Send a message and ask for a read receipt
398 === 0^SEND COPY <msgno> <call>^Send a copy of a message to someone
399 === 0^SEND PRIVATE <call>^Send a personal message
400 === 0^SEND NOPRIVATE <call>^Send a message to all stations
401 All the SEND commands will create a message which will be sent either to
402 an individual callsign or to one of the 'bulletin' addresses.
404 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
405 it will mark the message as personal and send it to the cluster node that
406 that callsign is connected to.
408 You can have more than one callsign in all of the SEND commands.
410 You can have multiple qualifiers so that you can have for example:-
412 SEND RR COPY 123 PRIVATE G1TLH G0RDI
414 which should send a copy of message 123 to G1TLH and G0RDI and you will
415 receive a read receipt when they have read the message.
417 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
418 SP is an alias for SEND PRIVATE
420 === 0^SET/ADDRESS <your address>^Record your postal address
422 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
423 === 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
425 === 0^SET/BEEP^Add a beep to DX and other messages on your terminal
426 === 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
428 === 9^SET/DEBUG <name>^Add a debug level to the debug set
429 === 9^UNSET/DEBUG <name>^Remove a debug level from the debug set
431 === 0^SET/DX^Allow DX messages to come out on your terminal
432 === 0^UNSET/DX^Stop DX messages coming out on your terminal
434 === 0^SET/ECHO^Make the cluster echo your input
435 === 0^UNSET/ECHO^Stop the cluster echoing your input
436 If you are connected via a telnet session, different implimentations
437 of telnet handle echo differently depending on whether you are
438 connected via port 23 or some other port. You can use this command
439 to change the setting appropriately.
441 The setting is stored in your user profile.
443 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
445 === 0^SET/HERE^Tell the system you are present at your terminal
446 === 0^UNSET/HERE^Tell the system you are absent from your terminal
448 === 0^SET/HOMENODE <node> ^Set your normal cluster callsign
449 Tell the cluster system where you normally connect to. Any Messages sent
450 to you will normally find their way there should you not be connected.
454 === 9^SET/ISOLATE^Isolate a node from the rest of the network
455 Connect a node to your system in such a way that you are a full protocol
456 member of its network and can see all spots on it, but nothing either leaks
457 out from it nor goes back into from the rest of the nodes connected to you.
459 You can potentially connect several nodes in this way.
461 === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network
462 Remove isolation from a node - SET/ISOLATE
464 === 0^SET/LANGUAGE <lang>^Set the language you want to use
465 You can select the language that you want the cluster to use. Currently
466 the languages available are en (english) and nl (dutch).
468 === 0^SET/LOCATION <lat & long>^Set your latitude and longitude
469 === 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
470 In order to get accurate headings and such like you must tell the system
471 what your latitude and longitude is. If you have not yet done a SET/QRA
472 then this command will set your QRA locator for you. For example:-
473 SET/LOCATION 52 22 N 0 57 E
475 === 0^SET/LOGININFO^Inform when a station logs in locally
476 === 0^UNSET/LOGININFO^Inform when a station logs out locally
478 === 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
479 === 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
481 === 0^SET/NAME <your name>^Set your name
482 Tell the system what your name is eg:-
485 === 9^SET/NODE <call> [<call>..]^Make the callsign an AK1A cluster
486 Tell the system that the call(s) are to be treated as AK1A cluster and
487 fed PC Protocol rather normal user commands.
489 === 9^SET/OBSCOUNT <count> <nodecall>^Set the 'pump-up' obscelence counter
490 From 1.35 onwards neighbouring nodes are pinged at regular intervals (see
491 SET/PINGINTERVAL), usually 300 seconds or 5 minutes. There is a 'pump-up'
492 counter which is decremented on every outgoing ping and then reset to
493 the 'obscount' value on every incoming ping. The default value of this
496 What this means is that a neighbouring node will be pinged twice at
497 (default) 300 second intervals and if no reply has been heard just before
498 what would be the third attempt, that node is disconnected.
500 If a ping is heard then the obscount is reset to the full value. Using
501 default values, if a node has not responded to a ping within 15 minutes,
504 === 0^SET/PAGE <lines per page>^Set the lines per page
505 Tell the system how many lines you wish on a page when the number of line
506 of output from a command is more than this. The default is 20. Setting it
507 explicitly to 0 will disable paging.
511 The setting is stored in your user profile.
513 === 9^SET/PINGINTERVAL <time> <nodecall>^Set ping time to neighbouring nodes
514 As from release 1.35 all neighbouring nodes are pinged at regular intervals
515 in order to determine the rolling quality of the link and, in future, to
516 affect routing decisions. The default interval is 300 secs or 5 minutes.
518 You can use this command to set a different interval. Please don't.
520 But if you do the value you enter is treated as minutes up 60 and seconds
521 for numbers greater than that.
523 This is used also to help determine when a link is down at the far end
524 (as certain cluster software doesn't always notice), see SET/OBSCOUNT
525 for more information.
527 === 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
528 Set the privilege level on a callsign. The privilege levels that pertain
529 to commands are as default:-
531 1 - allow remote nodes normal user RCMDs
532 5 - various privileged commands (including shutdown, but not disc-
533 connect), the normal level for another node.
534 8 - more privileged commands (including disconnect)
535 9 - local sysop privilege. DO NOT SET ANY REMOTE USER OR NODE TO THIS
537 If you are a sysop and you come in as a normal user on a remote connection
538 your privilege will automatically be set to 0.
540 === 9^SET/PASSWORD <callsign> <string>^Set a users password
541 The password for a user can only be set by a full sysop. The string
542 can contain any characters but any spaces are removed (you can type in
543 spaces - but they won't appear in the password). You can see the
544 result with STAT/USER.
546 === 9^SET/SPIDER <call> [<call>..]^Make the callsign an DXSpider node
547 Tell the system that the call(s) are to be treated as DXSpider node and
548 fed new style DX Protocol rather normal user commands.
550 === 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
551 === 0^SET/QRA <locator>^Set your QRA locator
552 Tell the system what your QRA (or Maidenhead) locator is. If you have not
553 done a SET/LOCATION then your latitude and longitude will be set roughly
554 correctly (assuming your locator is correct ;-). For example:-
557 === 0^SET/QTH <your qth>^Set your QTH
558 Tell the system where you are. For example:-
559 SET/QTH East Dereham, Norfolk
561 === 0^SET/TALK^Allow TALK messages to come out on your terminal
562 === 0^UNSET/TALK^Stop TALK messages coming out on your terminal
564 === 0^SET/WCY^Allow WCY messages to come out on your terminal
565 === 0^UNSET/WCY^Stop WCY messages coming out on your terminal
567 === 0^SET/WWV^Allow WWV messages to come out on your terminal
568 === 0^UNSET/WWV^Stop WWV messages coming out on your terminal
570 === 0^SET/WX^Allow WX messages to come out on your terminal
571 === 0^UNSET/WX^Stop WX messages coming out on your terminal
573 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
574 This is very nearly the same as SHOW/TIME, the only difference the format
575 of the date string if no arguments are given.
577 If no prefixes or callsigns are given then this command returns the local
578 time and UTC as the computer has it right now. If you give some prefixes
579 then it will show UTC and UTC + the local offset (not including DST) at
580 the prefixes or callsigns that you specify.
582 === 0^SHOW/DX^Interrogate the spot database
583 If you just type SHOW/DX you will get the last so many spots
584 (sysop configurable, but usually 10).
586 In addition you can add any number of these commands in very nearly
587 any order to the basic SHOW/DX command, they are:-
589 on <band> - eg 160m 20m 2m 23cm 6mm
590 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
592 <number> - the number of spots you want
593 <from>-<to> - <from> spot no <to> spot no in the selected list
595 <prefix> - for a spotted callsign beginning with <prefix>
596 *<suffix> - for a spotted callsign ending in <suffix>
597 *<string>* - for a spotted callsign containing <string>
599 day <number> - starting <number> days ago
600 day <from>-<to> - <from> days <to> days ago
602 info <text> - any spots containing <text> in the info or remarks
604 by <call> - any spots spotted by <call> (spotter <call> is the
607 qsl - this automatically looks for any qsl info on the call
608 held in the spot database.
610 iota [<iota>] - If the iota island number is missing it will look for
611 the string iota and anything which looks like an iota
612 island number. If you specify then it will look for
615 qra [<locator>] - this will look for the specific locator if you specify
616 one or else anything that looks like a locator.
621 SH/DX on 20m info iota
622 SH/DX 9a on vhf day 30
628 === 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
629 This command takes the <prefix> (which can be a full or partial
630 callsign if desired), looks up which internal country number it is
631 and then displays all the spots as per SH/DX for that country.
633 The options for SHOW/DX also apply to this command.
637 SH/DXCC W on 20m info iota
639 === 0^SHOW/FILES [<filearea> [<string>]]^List the contents of a filearea
640 SHOW/FILES on its own will show you a list of the various fileareas
641 available on the system. To see the contents of a particular file
644 where <filearea> is the name of the filearea you want to see the
647 You can also use shell globbing characters like '*' and '?' in a
648 string to see a selection of files in a filearea eg:-
649 SH/FILES bulletins arld*
651 See also TYPE - to see the contents of a file.
653 === 1^SHOW/ISOLATE^Show list of ISOLATED nodes
655 === 9^SHOW/LOCKOUT^Show the list of locked out or excluded callsigns
657 === 0^SHOW/MOON [<prefix>|<callsign>]^Show Moon rise and set times
658 Show the Moon rise and set times for a (list of) prefixes or callsigns,
659 together with the azimuth and elevation of the sun currently at those
662 If you don't specify any prefixes or callsigns, it will show the times for
663 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
664 together with the current azimuth and elevation.
666 In addition, it will show the gain or loss dB relative to the nominal
667 distance of 385,000Km due to the ellipsoidal nature of the orbit.
669 If all else fails it will show the Moonrise and set times for the node
670 that you are connected to.
677 === 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a prefix
678 This command allow you to estimate the likelihood of you contacting
679 a station with the prefix you have specified. The output assumes a modest
680 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)
682 The result predicts the most likely operating frequencies and signal
683 levels for high frequency (shortwave) radio propagation paths on
684 specified days of the year and hours of the day. It is most useful for
685 paths between 250 km and 6000 km, but can be used with reduced accuracy
686 for paths shorter or longer than this.
688 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
689 used to predict the MUF given the predicted flux, day of the year,
690 hour of the day and geographic coordinates of the transmitter and
691 receiver. This routine is reasonably accurate for the purposes here,
692 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
693 than the programs used by major shortwave broadcasting organizations,
694 such as the Voice of America.
696 The command will display some header information detailing its
697 assumptions, together with the locations, latitude and longitudes and
698 bearings. It will then show UTC (UT), local time at the other end
699 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
700 (Zen) and the likely signal strengths. Then for each frequency for which
701 the system thinks there is a likelihood of a circuit it prints a value.
703 The value is currently a likely S meter reading based on the conventional
704 6dB / S point scale. If the value has a '+' appended it means that it is
705 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
706 there is likely to be much fading and by an 's' that the signal is likely
709 By default SHOW/MUF will show the next two hours worth of data. You
710 can specify anything up to 24 hours worth of data by appending the no of
711 hours required after the prefix. For example:-
717 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
718 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
719 Location Lat / Long Azim
720 East Dereham, Norfolk 52 41 N 0 57 E 47
721 United-States-W 43 0 N 87 54 W 299
722 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
723 18 23 11.5 -35 mS0+ mS2 S3
724 19 0 11.2 -41 mS0+ mS2 S3
726 indicating that you will have weak, fading circuits on top band and
727 80m but usable signals on 40m (about S3).
733 will get you the above display, but with the next 24 hours worth of
739 Gives you an estimate of the long path propagation characterics. It
740 should be noted that the figures will probably not be very useful, nor
741 terrible accurate, but it is included for completeness.
743 === 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
744 Show the type and version (if connected) of the nodes specified on the
745 command line. If no callsigns are specified then a sorted list of all
746 the non-user callsigns known to the system will be displayed.
748 === 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
749 This command takes the <callsign> (which can be a full or partial
750 callsign or a prefix), looks up which internal country number
751 it is and then displays all the relevant prefixes for that country
752 together with the internal country no, the CQ and ITU regions.
756 === 5^SHOW/PROGRAM^Show the locations of all the included program modules
757 Show the name and location where every program module was load from. This
758 is useful for checking where you think you have loaded a .pm file from.
760 === 0^SHOW/QRA <locator> [<locator>]^Show distance between locators
761 === 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
762 This is a multipurpose command that allows you either to calculate the
763 distance and bearing between two locators or (if only one locator is
764 given on the command line) the distance and beraing from your station
765 to the locator. For example:-
770 The first example will show the distance and bearing to the locator from
771 yourself, the second example will calculate the distance and bearing from
772 the first locator to the second. You can use 4 or 6 character locators.
774 It is also possible to convert a latitude and longitude to a locator by
775 using this command with a latitude and longitude as an argument, for
778 SH/QRA 52 41 N 0 58 E
780 === 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
781 Show the tracking data from your location to the satellite of your choice
782 from now on for the next few hours.
784 If you use this command without a satellite name it will display a list
785 of all the satellites known currently to the system.
787 If you give a name then you can obtain tracking data of all the passes
788 that start and finish 5 degrees below the horizon. As default it will
789 give information for the next three hours for every five minute period.
791 You can alter the number of hours and the step size, within certain
794 Each pass in a period is separated with a row of '-----' characters
801 === 0^SHOW/SUN [<prefix>|<callsign>]^Show sun rise and set times
802 Show the sun rise and set times for a (list of) prefixes or callsigns,
803 together with the azimuth and elevation of the sun currently at those
806 If you don't specify any prefixes or callsigns, it will show the times for
807 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
808 together with the current azimuth and elevation.
810 If all else fails it will show the sunrise and set times for the node
811 that you are connected to.
818 === 0^SHOW/TIME [<prefix>|<callsign>]^Show the local time
819 If no prefixes or callsigns are given then this command returns the local
820 time and UTC as the computer has it right now. If you give some prefixes
821 then it will show UTC and UTC + the local offset (not including DST) at
822 the prefixes or callsigns that you specify.
824 === 0^SHOW/WCY^Show last 10 WCY broadcasts
825 === 0^SHOW/WCY <n>^Show last <n> WCY broadcasts
826 Display the most recent WCY information that has been received by the system
828 === 0^SHOW/WWV^Show last 10 WWV broadcasts
829 === 0^SHOW/WWV <n>^Show last <n> WWV broadcasts
830 Display the most recent WWV information that has been received by the system
832 === 5^SHUTDOWN^Shutdown the cluster
833 Shutdown the cluster and disconnect all the users
835 === 5^STAT/DB <dbname>^Show the status of a database
836 Show the internal status of a database descriptor.
838 Depending on your privilege level you will see more or less information.
839 This command is unlikely to be of much use to anyone other than a sysop.
841 === 5^STAT/CHANNEL [<callsign>]^Show the status of a channel on the cluster
842 Show the internal status of the channel object either for the channel that
843 you are on or else for the callsign that you asked for.
845 Only the fields that are defined (in perl term) will be displayed.
847 === 5^STAT/MSG <msgno>^Show the status of a message
848 This command shows the internal status of a message and includes information
849 such as to whom it has been forwarded, its size, origin etc etc.
851 === 5^STAT/USER [<callsign>]^Show the full status of a user
852 Shows the full contents of a user record including all the secret flags
855 Only the fields that are defined (in perl term) will be displayed.
857 === 0^SYSOP^Regain your privileges if you login remotely
858 The system automatically reduces your privilege level to that of a
859 normal user if you login in remotely. This command allows you to
860 regain your normal privilege level. It uses the normal system: five
861 numbers are returned that are indexes into the character array that is
862 your assigned password (see SET/PASSWORD). The indexes start from
865 You are expected to return a string which contains the characters
866 required in the correct order. You may intersperse those characters
867 with others to obscure your reply for any watchers. For example (and
868 these values are for explanation :-):
870 password = 012345678901234567890123456789
874 aa2bbbb0ccc5ddd7xxx3n
878 They will all match. If there is no password you will still be offered
879 numbers but nothing will happen when you input a string. Any match is
882 === 0^TALK <call> <text>^Send a text message to another station
883 === 0^TALK <call> > <node> <text>^Send a text message to another station via a node
884 Send a short message to any other station that is visible on the cluster
885 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
886 command, they don't have to be connected locally.
888 The second form of TALK is used when other cluster nodes are connected
889 with restricted information. This usually means that they don't send
890 the user information usually associated with logging on and off the cluster.
892 If you know that G3JNB is likely to be present on GB7TLH, but you can only
893 see GB7TLH in the SH/C list but with no users, then you would use the
894 second form of the talk message.
896 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
897 Type out the contents of a file in a filearea. So, for example, in
898 filearea 'bulletins' you want to look at file 'arld051' you would
900 TYPE bulletins/arld051
902 See also SHOW/FILES to see what fileareas are available and a
905 === 0^WHO^Show who is physically connected
906 This is a quick listing that shows which callsigns are connected and
907 what sort of connection they have
909 === 0^WX <text>^Send a weather message to local users
910 === 0^WX FULL <text>^Send a weather message to all cluster users
911 === 5^WX SYSOP <text>^Send a weather message to other clusters only
912 Weather messages can sometimes be useful if you are experiencing an extreme
913 that may indicate enhanced conditions