1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.16">
5 <TITLE>The DXSpider User Manual v1.50: The DXSpider command reference</TITLE>
6 <LINK HREF="usermanual-11.html" REL=previous>
7 <LINK HREF="usermanual.html#toc12" REL=contents>
8 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="usermanual-11.html">Previous</A>
13 <A HREF="usermanual.html#toc12">Contents</A>
15 <H2><A NAME="s12">12.</A> <A HREF="usermanual.html#toc12">The DXSpider command reference</A></H2>
17 <P>Below is a complete list of commands available from the cluster prompt.
18 These are listed below in alphabetical order. </P>
20 <H2><A NAME="ss12.1">12.1</A> <A HREF="usermanual.html#toc12.1">accept/announce</A>
23 <P><CODE><B>accept/announce [0-9] <pattern></B> Set an accept filter
24 line for announce</CODE></P>
26 <P>Create an 'accept this announce' line for a filter. </P>
27 <P>An accept filter line means that if the announce matches this filter it is
28 passed onto the user. See HELP FILTERS for more info. Please read this
29 to understand how filters work - it will save a lot of grief later on.</P>
30 <P>You can use any of the following things in this line:-</P>
34 info <string> eg: iota or qsl
35 by <prefixes> eg: G,M,2
37 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
38 origin_itu <numbers>
39 origin_zone <numbers>
44 wx 1 filter WX announces
45 dest <prefixes> eg: 6MUK,WDX (distros)
49 <P>some examples:-</P>
54 acc/ann 2 by_zone 14,15,16
55 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
67 <P>This filter would only allow announces that were posted buy UK stations.
68 You can use the tag 'all' to accept everything eg:</P>
76 <P>but this probably for advanced users...</P>
78 <H2><A NAME="ss12.2">12.2</A> <A HREF="usermanual.html#toc12.2">accept/spots </A>
81 <P><CODE><B>accept/spots [0-9] <pattern></B> Set an accept filter line for spots</CODE></P>
83 <P>Create an 'accept this spot' line for a filter.</P>
85 <P>An accept filter line means that if the spot matches this filter it is
86 passed onto the user. See HELP FILTERS for more info. Please read this
87 to understand how filters work - it will save a lot of grief later on.</P>
88 <P>You can use any of the following things in this line:-</P>
92 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
93 on <range> same as 'freq'
94 call <prefixes> eg: G,PA,HB9
95 info <string> eg: iota or qsl
97 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
99 call_zone <numbers>
104 channel <prefixes>
109 <P>For frequencies, you can use any of the band names defined in
110 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
111 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
112 this is more efficient than saying simply: freq HF (but don't get
113 too hung up about that)</P>
114 <P>some examples:-</P>
119 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
123 <P>You can use the tag 'all' to accept everything, eg:</P>
131 <P>but this probably for advanced users...</P>
133 <H2><A NAME="ss12.3">12.3</A> <A HREF="usermanual.html#toc12.3">accept/wcy </A>
136 <P><CODE><B>accept/wcy [0-9] <pattern></B> set an accept WCY filter</CODE></P>
138 <P>It is unlikely that you will want to do this, but if you do then you can
139 filter on the following fields:-</P>
143 by <prefixes> eg: G,M,2
145 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
146 origin_itu <numbers>
147 origin_zone <numbers>
151 channel <prefixes>
156 <P>There are no examples because WCY Broadcasts only come from one place and
157 you either want them or not (see UNSET/WCY if you don't want them).</P>
158 <P>This command is really provided for future use.</P>
159 <P>See HELP FILTER for information.</P>
161 <H2><A NAME="ss12.4">12.4</A> <A HREF="usermanual.html#toc12.4">accept/wwv </A>
164 <P><CODE><B>accept/wwv [0-9] <pattern></B> Set an accept WWV filter</CODE></P>
166 <P>It is unlikely that you will want to do this, but if you do then you can
167 filter on the following fields:-</P>
171 by <prefixes> eg: G,M,2
173 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
174 origin_itu <numbers>
175 origin_zone <numbers>
179 channel <prefixes>
191 <P>is probably the only useful thing to do (which will only show WWV broadcasts
192 by stations in the US).</P>
193 <P>See HELP FILTER for information.</P>
195 <H2><A NAME="ss12.5">12.5</A> <A HREF="usermanual.html#toc12.5">announce </A>
198 <P><CODE><B>announce <text></B> Send an announcement to local users</CODE></P>
200 <P>Send an announcement to LOCAL users only, where <text> is the text
201 of the announcement you wish to broadcast</P>
203 <H2><A NAME="ss12.6">12.6</A> <A HREF="usermanual.html#toc12.6">announce full </A>
206 <P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE></P>
208 <P>This command will send your announcement across the whole cluster
211 <H2><A NAME="ss12.7">12.7</A> <A HREF="usermanual.html#toc12.7">apropos </A>
214 <P><CODE><B>apropos <string></B> Search the help database</CODE></P>
216 <P>Search the help database for <string> (it isn't case sensitive),
217 and print the names of all the commands that may be relevant.</P>
219 <H2><A NAME="ss12.8">12.8</A> <A HREF="usermanual.html#toc12.8">bye </A>
222 <P><CODE><B>bye</B> Exit from the cluster</CODE></P>
224 <P>This will disconnect you from the cluster</P>
226 <H2><A NAME="ss12.9">12.9</A> <A HREF="usermanual.html#toc12.9">clear/spots </A>
229 <P><CODE><B>clear/spots [1|all]</B> Clear a spot filter line</CODE></P>
231 <P>This command allows you to clear (remove) a line in a spot filter or to
232 remove the whole filter.</P>
233 <P>If you have a filter:-</P>
238 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
250 <P>you will be left with:-</P>
254 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
266 <P>the filter will be completely removed.</P>
268 <H2><A NAME="ss12.10">12.10</A> <A HREF="usermanual.html#toc12.10">dbavail </A>
271 <P><CODE><B>dbavail</B> Show a list of all the databases in the system</CODE></P>
273 <P>The title says it all really, this command lists all the databases defined
274 in the system. It is also aliased to SHOW/COMMAND.</P>
276 <H2><A NAME="ss12.11">12.11</A> <A HREF="usermanual.html#toc12.11">dbshow </A>
279 <P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE></P>
281 <P>This is the generic user interface to the database to the database system.
282 It is expected that the sysop will add an entry to the local Aliases file
283 so that users can use the more familiar AK1A style of enquiry such as:</P>
291 <P>but if he hasn't and the database really does exist (use DBAVAIL or
292 SHOW/COMMAND to find out) you can do the same thing with:</P>
301 <H2><A NAME="ss12.12">12.12</A> <A HREF="usermanual.html#toc12.12">directory </A>
304 <P><CODE><B>directory</B> List messages<BR> <B>directory all</B> List all messages<BR>
305 <B>directory own</B> List your own messages<BR>
306 <B>directory new</B> List all new messages<BR>
307 <B>directory to <call></B> List all messages to <call><BR>
308 <B>directory from <call></B> List all messages from <call><BR>
309 <B>directory subject <string></B> List all messages with <string> in subject<BR>
310 <B>directory <nn></B> List last <nn> messages<BR>
311 <B>directory <from>-<to></B> List messages <from> message <to> message <BR></CODE></P>
313 <P>List the messages in the messages directory.</P>
314 <P>If there is a 'p' one space after the message number then it is a
315 personal message. If there is a '-' between the message number and the
316 'p' then this indicates that the message has been read.</P>
317 <P>You can use shell escape characters such as '*' and '?' in the <call>
319 <P>You can combine some of the various directory commands together eg:-</P>
325 DIR SUBJECT IOTA 200-250
329 <P>You can abbreviate all the commands to one letter and use ak1a syntax:-</P>
339 <H2><A NAME="ss12.13">12.13</A> <A HREF="usermanual.html#toc12.13">dx </A>
342 <P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE></P>
344 <P>This is how you send a DX Spot to other users. You can, in fact, now
345 enter the <freq> and the <call> either way round. </P>
355 <P>will all give the same result. You can add some remarks to the end
356 of the command and they will be added to the spot.</P>
360 DX FR0G 144600 this is a test
364 <P>You can credit someone else by saying:-</P>
368 DX by G1TLH FR0G 144.600 he isn't on the cluster
372 <P>The <freq> is compared against the available bands set up in the
373 cluster. See SHOW/BANDS for more information.</P>
375 <H2><A NAME="ss12.14">12.14</A> <A HREF="usermanual.html#toc12.14">help </A>
378 <P><CODE><B>help <cmd></B> Get help on a command</CODE></P>
380 <P>All commands can be abbreviated, so SHOW/DX can be abbreviated
381 to SH/DX, ANNOUNCE can be shortened to AN and so on.</P>
382 <P>Look at the APROPOS <string> command which will search the help database
383 for the <string> you specify and give you a list of likely commands
384 to look at with HELP.</P>
386 <H2><A NAME="ss12.15">12.15</A> <A HREF="usermanual.html#toc12.15">kill </A>
389 <P><CODE><B>kill <msgno> [<msgno> ..]</B> Delete a message from the local system</CODE></P>
391 <P>Delete a message from the local system. You will only be able to
392 delete messages that you have originated or been sent (unless you are
395 <H2><A NAME="ss12.16">12.16</A> <A HREF="usermanual.html#toc12.16">links </A>
398 <P><CODE><B>links</B> Show which nodes are physically connected</CODE></P>
400 <P>This is a quick listing that shows which links are connected and
401 some information about them. See WHO for a list of all connections.</P>
403 <H2><A NAME="ss12.17">12.17</A> <A HREF="usermanual.html#toc12.17">read </A>
406 <P><CODE><B>read</B> Read the next unread personal message addressed to you<BR>
407 <B>read <msgno></B> Read the specified message<BR></CODE></P>
409 <P>You can read any messages that are sent as 'non-personal' and also any
410 message either sent by or sent to your callsign.</P>
412 <H2><A NAME="ss12.18">12.18</A> <A HREF="usermanual.html#toc12.18">reject/announce</A>
415 <P><CODE><B>reject/announce [0-9] <pattern></B> Set a reject filter
416 for announce</CODE></P>
418 <P>Create an 'reject this announce' line for a filter. </P>
419 <P>An reject filter line means that if the announce matches this filter it is
420 passed onto the user. See HELP FILTERS for more info. Please read this
421 to understand how filters work - it will save a lot of grief later on.</P>
422 <P>You can use any of the following things in this line:-</P>
426 info <string> eg: iota or qsl
427 by <prefixes> eg: G,M,2
429 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
430 origin_itu <numbers>
431 origin_zone <numbers>
435 channel <prefixes>
436 wx 1 filter WX announces
437 dest <prefixes> eg: 6MUK,WDX (distros)
441 <P>some examples:-</P>
445 rej/ann by_zone 14,15,16 and not by G,M,2
449 <P>You can use the tag 'all' to reject everything eg:</P>
457 <P>but this probably for advanced users...</P>
459 <H2><A NAME="ss12.19">12.19</A> <A HREF="usermanual.html#toc12.19">reject/spots </A>
462 <P><CODE><B>reject/spots [0-9] <pattern></B> Set a reject filter line for spots</CODE></P>
464 <P>Create a 'reject this spot' line for a filter. </P>
465 <P>A reject filter line means that if the spot matches this filter it is
466 dumped (not passed on). See HELP FILTERS for more info. Please read this
467 to understand how filters work - it will save a lot of grief later on.</P>
468 <P>You can use any of the following things in this line:-</P>
472 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
473 on <range> same as 'freq'
474 call <prefixes> eg: G,PA,HB9
475 info <string> eg: iota or qsl
477 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
478 call_itu <numbers>
479 call_zone <numbers>
484 channel <prefixes>
488 <P>For frequencies, you can use any of the band names defined in
489 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
490 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
491 this is more efficient than saying simply: on HF (but don't get
492 too hung up about that)</P>
493 <P>some examples:-</P>
498 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
502 <P>You can use the tag 'all' to reject everything eg:</P>
510 <P>but this probably for advanced users...</P>
512 <H2><A NAME="ss12.20">12.20</A> <A HREF="usermanual.html#toc12.20">reject/wcy </A>
515 <P><CODE><B>reject/wcy [0-9] <pattern></B> Set a reject WCY filter</CODE></P>
517 <P>It is unlikely that you will want to do this, but if you do then you can
518 filter on the following fields:-</P>
522 by <prefixes> eg: G,M,2
524 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
525 origin_itu <numbers>
526 origin_zone <numbers>
530 channel <prefixes>
534 <P>There are no examples because WCY Broadcasts only come from one place and
535 you either want them or not (see UNSET/WCY if you don't want them).</P>
536 <P>This command is really provided for future use.</P>
537 <P>See HELP FILTER for information.</P>
539 <H2><A NAME="ss12.21">12.21</A> <A HREF="usermanual.html#toc12.21">reject/wwv </A>
542 <P><CODE><B>reject/wwv [0-9] <pattern></B> Set a reject WWV filter</CODE></P>
544 <P>It is unlikely that you will want to do this, but if you do then you can
545 filter on the following fields:-</P>
549 by <prefixes> eg: G,M,2
551 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
552 origin_itu <numbers>
553 origin_zone <numbers>
557 channel <prefixes>
565 reject/wwv by_zone 14,15,16
569 <P>is probably the only useful thing to do (which will only show WWV broadcasts
570 by stations in the US).</P>
571 <P>See HELP FILTER for information.</P>
573 <H2><A NAME="ss12.22">12.22</A> <A HREF="usermanual.html#toc12.22">reply </A>
576 <P><CODE><B>reply</B> Reply (privately) to the last message that you have read<BR>
577 <B>reply <msgno></B> Reply (privately) to the specified message<BR>
578 <B>reply B <msgno></B> Reply as a Bulletin to the specified message<BR>
579 <B>reply NOPrivate <msgno></B> Reply as a Bulletin to the specified
581 <B>reply RR <msgno></B> Reply to the specified message with read receipt<BR></CODE></P>
583 <P>You can reply to a message and the subject will automatically have
584 "Re:" inserted in front of it, if it isn't already present.</P>
585 <P>You can also use all the extra qualifiers such as RR, PRIVATE,
586 NOPRIVATE, B that you can use with the SEND command (see SEND
587 for further details)</P>
589 <H2><A NAME="ss12.23">12.23</A> <A HREF="usermanual.html#toc12.23">send </A>
592 <P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns<BR>
593 <B>send RR <call></B> Send a message and ask for a read receipt<BR>
594 <B>send COPY <msgno> <call></B> Send a copy of a message to someone<BR>
595 <B>send PRIVATE <call></B> Send a personal message<BR>
596 <B>send NOPRIVATE <call></B> Send a message to all stations<BR></CODE></P>
598 <P>All the SEND commands will create a message which will be sent either to
599 an individual callsign or to one of the 'bulletin' addresses. </P>
600 <P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
601 it will mark the message as personal and send it to the cluster node that
602 that callsign is connected to.</P>
603 <P>You can have more than one callsign in all of the SEND commands.</P>
604 <P>You can have multiple qualifiers so that you can have for example:-</P>
608 SEND RR COPY 123 PRIVATE G1TLH G0RDI
612 <P>which should send a copy of message 123 to G1TLH and G0RDI and you will
613 receive a read receipt when they have read the message.</P>
614 <P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
615 SP is an alias for SEND PRIVATE</P>
617 <H2><A NAME="ss12.24">12.24</A> <A HREF="usermanual.html#toc12.24">set/address </A>
620 <P><CODE><B>set/address <your_address></B> Record your postal address</CODE></P>
622 <P>Literally, record your address details on the cluster.</P>
624 <H2><A NAME="ss12.25">12.25</A> <A HREF="usermanual.html#toc12.25">set/announce </A>
627 <P><CODE><B>set/announce</B> Allow announce messages</CODE></P>
629 <P>Allow announce messages to arrive at your terminal.</P>
631 <H2><A NAME="ss12.26">12.26</A> <A HREF="usermanual.html#toc12.26">set/beep </A>
634 <P><CODE><B>set/beep</B> Add beeps to terminal messages</CODE></P>
636 <P>Add a beep to DX and other terminal messages.</P>
638 <H2><A NAME="ss12.27">12.27</A> <A HREF="usermanual.html#toc12.27">set/dx </A>
641 <P><CODE><B>set/dx</B>Allow DX messages to arrive at your terminal</CODE></P>
643 <P>You can stop DX messages with the <EM>unset/dx</EM> command</P>
645 <H2><A NAME="ss12.28">12.28</A> <A HREF="usermanual.html#toc12.28">set/dxgrid</A>
648 <P><CODE><B>set/dxgrid</B>Allow grid squares on the end of DX messages</CODE></P>
650 <P>Some logging programs do not like the additional information at
651 the end of a DX spot. If this is the case, use the <EM>unset/dxgrid</EM>
652 command to remove the grid squares.</P>
654 <H2><A NAME="ss12.29">12.29</A> <A HREF="usermanual.html#toc12.29">set/echo </A>
657 <P><CODE><B>set/echo</B> Make the cluster echo your input</CODE></P>
659 <P>If you are connected via a telnet session, different implimentations
660 of telnet handle echo differently depending on whether you are
661 connected via port 23 or some other port. You can use this command
662 to change the setting appropriately. </P>
663 <P>You can remove the echo with the <EM>unset/echo</EM> command</P>
664 <P>The setting is stored in your user profile.</P>
665 <P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.</P>
667 <H2><A NAME="ss12.30">12.30</A> <A HREF="usermanual.html#toc12.30">set/here</A>
670 <P><CODE><B>set/here</B> Set the here flag</CODE></P>
672 <P>Let others on the cluster know you are here by only displaying your
673 callsign. If you are away from your terminal you can use the <EM>unset/here</EM>
674 command to let people know you are away. This simply puts brackets
675 around your callsign to indicate you are not available.</P>
677 <H2><A NAME="ss12.31">12.31</A> <A HREF="usermanual.html#toc12.31">set/homenode </A>
680 <P><CODE><B>set/homenode <node_call></B> Set your home cluster</CODE></P>
682 <P>Tell the cluster system where you normally connect to. Any Messages sent
683 to you will normally find their way there should you not be connected.
693 <H2><A NAME="ss12.32">12.32</A> <A HREF="usermanual.html#toc12.32">set/language </A>
696 <P><CODE><B>set/language <language></B> Set the language you wish to use</CODE></P>
698 <P>You can select the language that you want the cluster to use. Currently
699 the languages available are <EM>en</EM> (English) <EM>sp</EM> (Spanish)
700 and <EM>nl</EM> (Dutch).</P>
702 <H2><A NAME="ss12.33">12.33</A> <A HREF="usermanual.html#toc12.33">set/location </A>
705 <P><CODE><B>set/location <lat and long></B> Set your latitude and longitude</CODE></P>
707 <P>You can set your latitude and longitude manually or alternatively use the
708 <EM>set/qra</EM> command which will do the conversion for you.</P>
712 set/location 54 04 N 2 02 E
717 <H2><A NAME="ss12.34">12.34</A> <A HREF="usermanual.html#toc12.34">set/logininfo </A>
720 <P><CODE><B>set/logininfo</B> Show logins and logouts of nodes and users</CODE></P>
722 <P>Show users and nodes when they log in and out of the local cluster. You
723 can stop these messages by using the <EM>unset/logininfo</EM> command.</P>
725 <H2><A NAME="ss12.35">12.35</A> <A HREF="usermanual.html#toc12.35">set/name </A>
728 <P><CODE><B>set/name <your_name></B> Set your name</CODE></P>
730 <P>Tell the cluster what your name is, eg:-</P>
739 <H2><A NAME="ss12.36">12.36</A> <A HREF="usermanual.html#toc12.36">set/page </A>
742 <P><CODE><B>set/page <n></B> Set the number of lines per page</CODE></P>
744 <P>Tell the system how many lines you wish on a page when the number of lines
745 of output from a command is more than this. The default is 20. Setting it
746 explicitly to 0 will disable paging. </P>
755 <P>The setting is stored in your user profile.</P>
757 <H2><A NAME="ss12.37">12.37</A> <A HREF="usermanual.html#toc12.37">set/qra </A>
760 <P><CODE><B>set/qra <locator></B> Set your QRA locator</CODE></P>
762 <P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
763 done a SET/LOCATION then your latitude and longitude will be set roughly
764 correctly (assuming your locator is correct ;-). For example:-</P>
773 <H2><A NAME="ss12.38">12.38</A> <A HREF="usermanual.html#toc12.38">set/qth</A>
776 <P><CODE><B>set/qth <your QTH></B> Set your QTH</CODE></P>
778 <P>Tell the system where your are. For example:-</P>
782 set/qth East Dereham, Norfolk
787 <H2><A NAME="ss12.39">12.39</A> <A HREF="usermanual.html#toc12.39">set/talk</A>
790 <P><CODE><B>set/talk</B> Allow talk messages to be seen at your console</CODE></P>
792 <P>Allow talk messages to arrive at your console. You can switch off
793 talks with the <EM>unset/talk</EM> command.</P>
795 <H2><A NAME="ss12.40">12.40</A> <A HREF="usermanual.html#toc12.40">set/wcy</A>
798 <P><CODE><B>set/wcy</B> Allow WCY messages to be seen at your console</CODE></P>
800 <P>Allow WCY information to be seen at your console. You can switch off
801 WCY messages with the <EM>unset/wcy</EM> command.</P>
803 <H2><A NAME="ss12.41">12.41</A> <A HREF="usermanual.html#toc12.41">set/wwv</A>
806 <P><CODE><B>set/wwv</B> Allow WWV messages to be seen at your console</CODE></P>
808 <P>Allow WWV information to be seen at your console. You can switch off
809 WWV messages with the <EM>unset/wwv</EM> command.</P>
811 <H2><A NAME="ss12.42">12.42</A> <A HREF="usermanual.html#toc12.42">set/wx </A>
814 <P><CODE><B>set/wx</B> Allow WX messages to be seen at your console</CODE></P>
816 <P>Allow WX information to be seen at your console. You can switch off
817 WX messages with the <EM>unset/wx</EM> command.</P>
819 <H2><A NAME="ss12.43">12.43</A> <A HREF="usermanual.html#toc12.43">show/configuration</A>
822 <P><CODE><B>show/configuration [<node>]</B> Show all visible nodes and their users</CODE></P>
824 <P>This command allows you to see all the users that can be seen
825 and the nodes to which they are connected. With the optional <EM>node</EM>,
826 you can specify a particular node to look at.</P>
827 <P>This command is normally abbreviated to: sh/c</P>
828 <P>BE WARNED: the list that is returned can be VERY long</P>
830 <H2><A NAME="ss12.44">12.44</A> <A HREF="usermanual.html#toc12.44">show/configuration/node</A>
833 <P><CODE><B>show/configuration/node</B> Show all the nodes connected</CODE></P>
835 <P>Show all the nodes connected locally and the nodes they have connected.</P>
838 <H2><A NAME="ss12.45">12.45</A> <A HREF="usermanual.html#toc12.45">show/date </A>
841 <P><CODE><B>show/date [<prefix>|<callsign>]</B> Show
842 the local time</CODE></P>
844 <P>This is very nearly the same as SHOW/TIME, the only difference the format
845 of the date string if no arguments are given.</P>
846 <P>If no prefixes or callsigns are given then this command returns the local
847 time and UTC as the computer has it right now. If you give some prefixes
848 then it will show UTC and UTC + the local offset (not including DST) at
849 the prefixes or callsigns that you specify.</P>
851 <H2><A NAME="ss12.46">12.46</A> <A HREF="usermanual.html#toc12.46">show/dx </A>
854 <P><CODE><B>show/dx [options]</B> interrogate the spot database</CODE></P>
856 <P>If you just type SHOW/DX you will get the last so many spots
857 (sysop configurable, but usually 10).</P>
858 <P>In addition you can add any number of these options in very nearly
859 any order to the basic SHOW/DX command, they are:-</P>
864 on <band> - eg 160m 20m 2m 23cm 6mm
865 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
867 <number> - the number of spots you want
868 <from>-<to> - <from> spot no <to> spot no in
871 <prefix> - for a spotted callsign beginning with <prefix>
872 *<suffix> - for a spotted callsign ending in <suffix>
873 *<string>* - for a spotted callsign containing <string>
875 day <number> - starting <number> days ago
876 day <from>-<to> - <from> days <to> days ago
878 info <text> - any spots containing <text> in the info or remarks
880 by <call> - any spots spotted by <call> (spotter <call>
883 qsl - this automatically looks for any qsl info on the call
884 held in the spot database.
886 iota [<iota>] - If the iota island number is missing it will
887 look for the string iota and anything which looks like
888 an iota island number. If you specify then it will look
891 qra [<locator>] - this will look for the specific locator if
892 you specify one or else anything that looks like a locator.
902 SH/DX on 20m info iota
903 SH/DX 9a on vhf day 30
912 <H2><A NAME="ss12.47">12.47</A> <A HREF="usermanual.html#toc12.47">show/dxcc </A>
915 <P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE></P>
917 <P>This command takes the <prefix> (which can be a full or partial
918 callsign if desired), looks up which internal country number it is
919 and then displays all the spots as per SH/DX for that country.</P>
920 <P>The options for SHOW/DX also apply to this command.
927 SH/DXCC W on 20m info iota
932 <H2><A NAME="ss12.48">12.48</A> <A HREF="usermanual.html#toc12.48">show/files </A>
935 <P><CODE><B>show/files [<filearea> [<string>]]</B> List
936 the contents of a filearea</CODE></P>
938 <P>SHOW/FILES on its own will show you a list of the various fileareas
939 available on the system. To see the contents of a particular file
944 SH/FILES <filearea>
948 <P>where <filearea> is the name of the filearea you want to see the
950 <P>You can also use shell globbing characters like '*' and '?' in a
951 string to see a selection of files in a filearea eg:-</P>
955 SH/FILES bulletins arld*
959 <P>See also TYPE - to see the contents of a file.</P>
961 <H2><A NAME="ss12.49">12.49</A> <A HREF="usermanual.html#toc12.49">show/filter </A>
964 <P><CODE><B>show/filter</B> Show the filters you have set</CODE></P>
966 <P>Show the contents of all the filters that are set by you. This command
967 displays all the filters set - for all the various categories.</P>
969 <H2><A NAME="ss12.50">12.50</A> <A HREF="usermanual.html#toc12.50">show/moon </A>
972 <P><CODE><B>show/moon [<prefix>|<callsign>]</B> Show moon
973 rise and set times</CODE></P>
975 <P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
976 together with the azimuth and elevation of the sun currently at those
978 <P>If you don't specify any prefixes or callsigns, it will show the times for
979 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
980 together with the current azimuth and elevation.</P>
981 <P>In addition, it will show the gain or loss dB relative to the nominal
982 distance of 385,000Km due to the ellipsoidal nature of the orbit.</P>
983 <P>If all else fails it will show the Moonrise and set times for the node
984 that you are connected to. </P>
995 <H2><A NAME="ss12.51">12.51</A> <A HREF="usermanual.html#toc12.51">show/muf </A>
998 <P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show
999 the likely propagation to <prefix></CODE></P>
1001 <P>This command allow you to estimate the likelihood of you contacting
1002 a station with the prefix you have specified. The output assumes a modest
1003 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)</P>
1004 <P>The result predicts the most likely operating frequencies and signal
1005 levels for high frequency (shortwave) radio propagation paths on
1006 specified days of the year and hours of the day. It is most useful for
1007 paths between 250 km and 6000 km, but can be used with reduced accuracy
1008 for paths shorter or longer than this.</P>
1009 <P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1010 used to predict the MUF given the predicted flux, day of the year,
1011 hour of the day and geographic coordinates of the transmitter and
1012 receiver. This routine is reasonably accurate for the purposes here,
1013 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1014 than the programs used by major shortwave broadcasting organizations,
1015 such as the Voice of America.</P>
1016 <P>The command will display some header information detailing its
1017 assumptions, together with the locations, latitude and longitudes and
1018 bearings. It will then show UTC (UT), local time at the other end
1019 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1020 (Zen) and the likely signal strengths. Then for each frequency for which
1021 the system thinks there is a likelihood of a circuit it prints a value.</P>
1022 <P>The value is currently a likely S meter reading based on the conventional
1023 6dB / S point scale. If the value has a '+' appended it means that it is
1024 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1025 there is likely to be much fading and by an 's' that the signal is likely
1027 <P>By default SHOW/MUF will show the next two hours worth of data. You
1028 can specify anything up to 24 hours worth of data by appending the no of
1029 hours required after the prefix. For example:-</P>
1035 </CODE></BLOCKQUOTE>
1041 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1042 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1043 Location Lat / Long Azim
1044 East Dereham, Norfolk 52 41 N 0 57 E 47
1045 United-States-W 43 0 N 87 54 W 299
1046 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1047 18 23 11.5 -35 mS0+ mS2 S3
1048 19 0 11.2 -41 mS0+ mS2 S3
1050 </CODE></BLOCKQUOTE>
1052 <P>indicating that you will have weak, fading circuits on top band and
1053 80m but usable signals on 40m (about S3).</P>
1060 </CODE></BLOCKQUOTE>
1062 <P>will get you the above display, but with the next 24 hours worth of
1063 propagation data.</P>
1070 </CODE></BLOCKQUOTE>
1072 <P>Gives you an estimate of the long path propagation characterics. It
1073 should be noted that the figures will probably not be very useful, nor
1074 terrible accurate, but it is included for completeness.</P>
1076 <H2><A NAME="ss12.52">12.52</A> <A HREF="usermanual.html#toc12.52">show/prefix </A>
1079 <P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database</CODE></P>
1081 <P>This command takes the <callsign> (which can be a full or partial
1082 callsign or a prefix), looks up which internal country number
1083 it is and then displays all the relevant prefixes for that country
1084 together with the internal country no, the CQ and ITU regions. </P>
1085 <P>See also SHOW/DXCC</P>
1087 <H2><A NAME="ss12.53">12.53</A> <A HREF="usermanual.html#toc12.53">show/qra </A>
1090 <P><CODE><B>show/qra <locator> [<locator>]</B> Show the distance
1091 between locators<BR>
1092 <B>show/qra <lat> <long></B> Convert latitude and longitude to a locator</CODE></P>
1094 <P>This is a multipurpose command that allows you either to calculate the
1095 distance and bearing between two locators or (if only one locator is
1096 given on the command line) the distance and beraing from your station
1097 to the locator. For example:-</P>
1104 </CODE></BLOCKQUOTE>
1106 <P>The first example will show the distance and bearing to the locator from
1107 yourself, the second example will calculate the distance and bearing from
1108 the first locator to the second. You can use 4 or 6 character locators.</P>
1109 <P>It is also possible to convert a latitude and longitude to a locator by
1110 using this command with a latitude and longitude as an argument, for
1115 SH/QRA 52 41 N 0 58 E
1117 </CODE></BLOCKQUOTE>
1120 <H2><A NAME="ss12.54">12.54</A> <A HREF="usermanual.html#toc12.54">show/qrz</A>
1123 <P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE></P>
1125 <P>This command queries the QRZ callbook server on the internet
1126 and returns any information available for that callsign. This service
1127 is provided for users of this software by http://www.qrz.com </P>
1129 <H2><A NAME="ss12.55">12.55</A> <A HREF="usermanual.html#toc12.55">show/route </A>
1132 <P><CODE><B>show/route <callsign></B> Show the route to <callsign></CODE></P>
1134 <P>This command allows you to see to which node the callsigns specified are
1135 connected. It is a sort of inverse sh/config.</P>
1141 </CODE></BLOCKQUOTE>
1144 <H2><A NAME="ss12.56">12.56</A> <A HREF="usermanual.html#toc12.56">show/satellite </A>
1147 <P><CODE><B>show/satellite <name> [<hours> <interval>]</B>
1148 Show satellite tracking data</CODE></P>
1150 <P>Show the tracking data from your location to the satellite of your choice
1151 from now on for the next few hours.</P>
1152 <P>If you use this command without a satellite name it will display a list
1153 of all the satellites known currently to the system. </P>
1154 <P>If you give a name then you can obtain tracking data of all the passes
1155 that start and finish 5 degrees below the horizon. As default it will
1156 give information for the next three hours for every five minute period.</P>
1157 <P>You can alter the number of hours and the step size, within certain
1159 <P>Each pass in a period is separated with a row of '-----' characters</P>
1160 <P>So for example:-</P>
1165 SH/SAT FENGYUN1 12 2
1167 </CODE></BLOCKQUOTE>
1170 <H2><A NAME="ss12.57">12.57</A> <A HREF="usermanual.html#toc12.57">show/sun </A>
1173 <P><CODE><B>show/sun [<prefix>|<callsign>]</B> Show
1174 sun rise and set times</CODE></P>
1176 <P>Show the sun rise and set times for a (list of) prefixes or callsigns,
1177 together with the azimuth and elevation of the sun currently at those
1179 <P>If you don't specify any prefixes or callsigns, it will show the times for
1180 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1181 together with the current azimuth and elevation.</P>
1182 <P>If all else fails it will show the sunrise and set times for the node
1183 that you are connected to. </P>
1184 <P>For example:-</P>
1189 SH/SUN G1TLH K9CW ZS
1191 </CODE></BLOCKQUOTE>
1194 <H2><A NAME="ss12.58">12.58</A> <A HREF="usermanual.html#toc12.58">show/time </A>
1197 <P><CODE><B>show/time [<prefix>|<callsign>]</B> Show
1198 the local time</CODE></P>
1200 <P>If no prefixes or callsigns are given then this command returns the local
1201 time and UTC as the computer has it right now. If you give some prefixes
1202 then it will show UTC and UTC + the local offset (not including DST) at
1203 the prefixes or callsigns that you specify.</P>
1205 <H2><A NAME="ss12.59">12.59</A> <A HREF="usermanual.html#toc12.59">show/wcy </A>
1208 <P><CODE><B>show/wcy</B> Show the last 10 WCY broadcasts<BR>
1209 <B>show/wcy <n></B> Show the last <n> WCY broadcasts</CODE></P>
1211 <P>Display the most recent WCY information that has been received by the system</P>
1213 <H2><A NAME="ss12.60">12.60</A> <A HREF="usermanual.html#toc12.60">show/wwv</A>
1216 <P><CODE><B>show/wwv</B> Show the last 10 WWV broadcasts<BR>
1217 <B>show/wwv <n></B> Show the last <n> WWV broadcasts</CODE></P>
1219 <P>Display the most recent WWV information that has been received by the system</P>
1221 <H2><A NAME="ss12.61">12.61</A> <A HREF="usermanual.html#toc12.61">sysop </A>
1224 <P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE></P>
1226 <P>The system automatically reduces your privilege level to that of a
1227 normal user if you login in remotely. This command allows you to
1228 regain your normal privilege level. It uses the normal system: five
1229 numbers are returned that are indexes into the character array that is
1230 your assigned password (see SET/PASSWORD). The indexes start from
1232 <P>You are expected to return a string which contains the characters
1233 required in the correct order. You may intersperse those characters
1234 with others to obscure your reply for any watchers. For example (and
1235 these values are for explanation :-):</P>
1239 password = 012345678901234567890123456789
1243 </CODE></BLOCKQUOTE>
1249 aa2bbbb0ccc5ddd7xxx3n
1253 </CODE></BLOCKQUOTE>
1255 <P>They will all match. If there is no password you will still be offered
1256 numbers but nothing will happen when you input a string. Any match is
1259 <H2><A NAME="ss12.62">12.62</A> <A HREF="usermanual.html#toc12.62">talk </A>
1262 <P><CODE><B>talk <callsign></B> Enter talk mode with <callsign><BR>
1263 <B>talk <callsign> <text></B> Send a text message to <callsign><BR>
1264 <B>talk <callsign> > <node_call> [<text>]</B>
1265 Send a text message to <callsign> via <node_call></CODE></P>
1267 <P>Send a short message to any other station that is visible on the cluster
1268 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
1269 command, they don't have to be connected locally.</P>
1270 <P>The second form of TALK is used when other cluster nodes are connected
1271 with restricted information. This usually means that they don't send
1272 the user information usually associated with logging on and off the cluster.</P>
1273 <P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
1274 see GB7TLH in the SH/C list but with no users, then you would use the
1275 second form of the talk message.</P>
1276 <P>If you want to have a ragchew with someone you can leave the text message
1277 out and the system will go into 'Talk' mode. What this means is that a
1278 short message is sent to the recipient telling them that you are in a 'Talking'
1279 frame of mind and then you just type - everything you send will go to the
1280 station that you asked for. </P>
1281 <P>All the usual announcements, spots and so on will still come out on your
1283 <P>If you want to do something (such as send a spot) you precede the normal
1284 command with a '/' character, eg:-</P>
1288 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
1291 </CODE></BLOCKQUOTE>
1293 <P>To leave talk mode type:</P>
1299 </CODE></BLOCKQUOTE>
1302 <H2><A NAME="ss12.63">12.63</A> <A HREF="usermanual.html#toc12.63">type </A>
1305 <P><CODE><B>type <filearea>/<name></B> Look at a file in one of the fileareas</CODE></P>
1307 <P>Type out the contents of a file in a filearea. So, for example, in
1308 filearea 'bulletins' you want to look at file 'arld051' you would
1313 TYPE bulletins/arld051
1315 </CODE></BLOCKQUOTE>
1317 <P>See also SHOW/FILES to see what fileareas are available and a
1318 list of content.</P>
1320 <H2><A NAME="ss12.64">12.64</A> <A HREF="usermanual.html#toc12.64">who </A>
1323 <P><CODE><B>who</B> Show who is physically connected locally</CODE></P>
1325 <P>This is a quick listing that shows which callsigns are connected and
1326 what sort of connection they have</P>
1328 <H2><A NAME="ss12.65">12.65</A> <A HREF="usermanual.html#toc12.65">wx </A>
1331 <P><CODE><B>wx <text></B> Send a weather message to local users<BR>
1332 <B>wx full <text> </B> Send a weather message to all cluster users</CODE></P>
1334 <P>Weather messages can sometimes be useful if you are experiencing an extreme
1335 that may indicate enhanced conditions</P>
1339 <A HREF="usermanual-11.html">Previous</A>
1340 <A HREF="usermanual.html#toc12">Contents</A>