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: Hints, tips and common questions.</TITLE>
6 <LINK HREF="usermanual_en-10.html" REL=previous>
7 <LINK HREF="usermanual_en.html#toc11" REL=contents>
8 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="usermanual_en-10.html">Previous</A>
13 <A HREF="usermanual_en.html#toc11">Contents</A>
15 <H2><A NAME="s11">11.</A> <A HREF="usermanual_en.html#toc11">Hints, tips and common questions.</A></H2>
17 <P><B>Q.</B>These commands seem very long! Can I shorten them?</P>
18 <P><B>A.</B>Of course you can and the usual abbreviations work. If you
19 are unsure, try it. </P>
20 <P><B>Q.</B>I am not sure if this command is correct. Can I cause any
22 <P><B>A.</B>Do not be afraid to try a command to see if it will work,
23 at the worst you will get an error message. If you require any
24 help on a command, just type help followed by the command you
25 want help on. Look at the "DXSpider Command Reference" section to see
26 what help can be found.</P>
27 <P><B>Q.</B>How should I use the announce command?</P>
28 <P><B>A.</B>With respect. Use the command by all means, but please
29 only use the "full" extension if absolutely necessary. It can
30 create a LOT of messages passing between clusters.</P>
31 <P><B>Q.</B>I like to be working in the shack while logged into the
32 cluster but I can't be looking at the screen all the time. How
33 can I be alerted when anything happens?</P>
34 <P><B>A.</B>Use the <B>SET/BEEP</B> command. You can find information
35 on this in the "DXSpider Command Reference" section.</P>
36 <P><B>Q.</B>I got disconnected from the cluster and now I can't log
37 back in again. What is wrong?</P>
38 <P><B>A.</B>Probably the cluster thinks you are still logged on and
39 will not let you reconnect using the same call to prevent loops.
40 Try logging on again adding an ssid to your callsign as DXSpider
41 treats G0YLM and G0YLM-1 as different users.</P>
42 <P><B>Q.</B>How do I know if I have got the latest version of this
44 <P><B>A.</B>The latest and greatest will always be on the Website. It will
45 also be included with every release of DXSpider. As always, if unsure,
46 ask your sysop what version number is the latest. </P>
49 <H2><A NAME="ss11.1">11.1</A> <A HREF="usermanual_en.html#toc11.1">accept</A>
52 <P><CODE><B>accept</B> Set a filter to accept something</CODE></P>
54 <P>Create a filter to accept something</P>
55 <P>There are 2 types of filter, accept and reject. See HELP FILTERING for more
57 <H2><A NAME="ss11.2">11.2</A> <A HREF="usermanual_en.html#toc11.2">accept/announce [0-9] <pattern></A>
60 <P><CODE><B>accept/announce [0-9] <pattern></B> Set an 'accept' filter line for announce</CODE></P>
62 <P>Create an 'accept this announce' line for a filter. </P>
63 <P>An accept filter line means that if the announce matches this filter it is
64 passed onto the user. See HELP FILTERING for more info. Please read this
65 to understand how filters work - it will save a lot of grief later on.</P>
66 <P>You can use any of the following things in this line:-</P>
70 info <string> eg: iota or qsl
71 by <prefixes> eg: G,M,2
72 origin <prefixes>
73 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
74 origin_itu <prefixes or numbers> or: G,GM,GW
75 origin_zone <prefixes or numbers>
76 origin_state <states> eg: VA,NH,RI,NH
77 by_dxcc <prefixes or numbers>
78 by_itu <prefixes or numbers>
79 by_zone <prefixes or numbers>
80 by_state <states>
81 channel <prefixes>
82 wx 1 filter WX announces
83 dest <prefixes> eg: 6MUK,WDX (distros)
87 <P>some examples:-</P>
92 acc/ann 2 by_zone 14,15,16
93 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
104 <P>for american states</P>
108 acc/ann by_state va,nh,ri,nh
112 <P>You can use the tag 'all' to accept everything eg:</P>
120 <P>but this probably for advanced users...</P>
121 <H2><A NAME="ss11.3">11.3</A> <A HREF="usermanual_en.html#toc11.3">accept/spots [0-9] <pattern></A>
124 <P><CODE><B>accept/spots [0-9] <pattern></B> Set an 'accept' filter line for spots</CODE></P>
126 <P>Create an 'accept this spot' line for a filter. </P>
127 <P>An accept filter line means that if the spot matches this filter it is
128 passed onto the user. See HELP FILTERING for more info. Please read this
129 to understand how filters work - it will save a lot of grief later on.</P>
130 <P>You can use any of the following things in this line:-</P>
134 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
135 on <range> same as 'freq'
136 call <prefixes> eg: G,PA,HB9
137 info <string> eg: iota or qsl
139 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
140 call_itu <prefixes or numbers> or: G,GM,GW
141 call_zone <prefixes or numbers>
142 call_state <states> eg: VA,NH,RI,ME
143 by_dxcc <prefixes or numbers>
144 by_itu <prefixes or numbers>
145 by_zone <prefixes or numbers>
146 by_state <states> eg: VA,NH,RI,ME
147 origin <prefixes>
148 channel <prefixes>
152 <P>'call' means the callsign that has spotted 'by' whoever.</P>
153 <P>For frequencies, you can use any of the band names defined in
154 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
155 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
156 this is more efficient than saying simply: freq HF (but don't get
157 too hung up about that)</P>
158 <P>some examples:-</P>
163 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
167 <P>You can use the tag 'all' to accept everything, eg:</P>
175 <P>for US states </P>
179 acc/spots by_state VA,NH,RI,MA,ME
183 <P>but this probably for advanced users...</P>
184 <H2><A NAME="ss11.4">11.4</A> <A HREF="usermanual_en.html#toc11.4">accept/wcy [0-9] <pattern></A>
187 <P><CODE><B>accept/wcy [0-9] <pattern></B> set an 'accept' WCY filter</CODE></P>
189 <P>It is unlikely that you will want to do this, but if you do then you can
190 filter on the following fields:-</P>
194 by <prefixes> eg: G,M,2
195 origin <prefixes>
196 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
197 origin_itu <prefixes or numbers> or: G,GM,GW
198 origin_zone <prefixes or numbers>
199 by_dxcc <prefixes or numbers>
200 by_itu <prefixes or numbers>
201 by_zone <prefixes or numbers>
202 channel <prefixes>
206 <P>There are no examples because WCY Broadcasts only come from one place and
207 you either want them or not (see UNSET/WCY if you don't want them).</P>
208 <P>This command is really provided for future use.</P>
209 <P>See HELP FILTER for information.</P>
210 <H2><A NAME="ss11.5">11.5</A> <A HREF="usermanual_en.html#toc11.5">accept/wwv [0-9] <pattern></A>
213 <P><CODE><B>accept/wwv [0-9] <pattern></B> set an 'accept' WWV filter</CODE></P>
215 <P>It is unlikely that you will want to do this, but if you do then you can
216 filter on the following fields:-</P>
220 by <prefixes> eg: G,M,2
221 origin <prefixes>
222 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
223 origin_itu <prefixes or numbers> or: G,GM,GW
224 origin_zone <prefixes or numbers>
225 by_dxcc <prefixes or numbers>
226 by_itu <prefixes or numbers>
227 by_zone <prefixes or numbers>
228 channel <prefixes>
240 <P>is probably the only useful thing to do (which will only show WWV broadcasts
241 by stations in the US).</P>
242 <P>See HELP FILTER for information.</P>
243 <H2><A NAME="ss11.6">11.6</A> <A HREF="usermanual_en.html#toc11.6">announce <text></A>
246 <P><CODE><B>announce <text></B> Send an announcement to LOCAL users only</CODE></P>
248 <P><text> is the text of the announcement you wish to broadcast </P>
249 <H2><A NAME="ss11.7">11.7</A> <A HREF="usermanual_en.html#toc11.7">announce full <text></A>
252 <P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE></P>
254 <P>This will send your announcement cluster wide</P>
255 <H2><A NAME="ss11.8">11.8</A> <A HREF="usermanual_en.html#toc11.8">apropos <string></A>
258 <P><CODE><B>apropos <string></B> Search help database for <string></CODE></P>
260 <P>Search the help database for <string> (it isn't case sensitive), and print
261 the names of all the commands that may be relevant.</P>
262 <H2><A NAME="ss11.9">11.9</A> <A HREF="usermanual_en.html#toc11.9">blank [<string>] [<nn>]</A>
265 <P><CODE><B>blank [<string>] [<nn>]</B> Print nn (default 1) blank lines (or strings)</CODE></P>
267 <P>In its basic form this command prints one or more blank lines. However if
268 you pass it a string it will replicate the string for the width of the
269 screen (default 80) and then print that one or more times, so:</P>
277 <P>prints two blank lines</P>
285 <P>prints a row of - characters once.</P>
293 <P>prints 'abcabcabcabcabcabc....'</P>
294 <P>This is really only of any use in a script file and you can print a maximum
296 <H2><A NAME="ss11.10">11.10</A> <A HREF="usermanual_en.html#toc11.10">bye</A>
299 <P><CODE><B>bye</B> Exit from the cluster</CODE></P>
301 <P>This will disconnect you from the cluster</P>
302 <H2><A NAME="ss11.11">11.11</A> <A HREF="usermanual_en.html#toc11.11">chat <group> <text></A>
305 <P><CODE><B>chat <group> <text></B> Chat or Conference to a group</CODE></P>
307 <P>It is now possible to JOIN a group and have network wide conferencing to that
308 group. DXSpider does not (and probably will not) implement the AK1A
309 conference mode as this seems very limiting, is hardly used and doesn't seem
310 to work too well anyway.</P>
311 <P>This system uses the existing ANN system and is compatible with both other
312 DXSpider nodes and AK1A clusters (they use ANN/<group>). </P>
313 <P>You can be a member of as many "groups" as you want. To join a group type:-</P>
317 JOIN FOC (where FOC is the group name)
321 <P>To leave a group type:-</P>
329 <P>You can see which groups you are in by typing:-</P>
337 <P>and you can see whether your mate is in the group, if he connects to the
338 same node as you, by typing:-</P>
346 <P>To send a message to a group type:-</P>
350 CHAT FOC hello everyone
358 CH #9000 hello I am back
362 <P>See also JOIN, LEAVE, SHOW/CHAT</P>
363 <H2><A NAME="ss11.12">11.12</A> <A HREF="usermanual_en.html#toc11.12">clear/announce [1|all]</A>
366 <P><CODE><B>clear/announce [1|all]</B> Clear a announce filter line</CODE></P>
368 <P>This command allows you to clear (remove) a line in a annouce filter or to
369 remove the whole filter.</P>
370 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
371 <H2><A NAME="ss11.13">11.13</A> <A HREF="usermanual_en.html#toc11.13">clear/route [1|all]</A>
374 <P><CODE><B>clear/route [1|all]</B> Clear a route filter line</CODE></P>
376 <P>This command allows you to clear (remove) a line in a route filter or to
377 remove the whole filter.</P>
378 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
379 <H2><A NAME="ss11.14">11.14</A> <A HREF="usermanual_en.html#toc11.14">clear/spots [0-9|all]</A>
382 <P><CODE><B>clear/spots [0-9|all]</B> Clear a spot filter line</CODE></P>
384 <P>This command allows you to clear (remove) a line in a spot filter or to
385 remove the whole filter.</P>
386 <P>If you have a filter:-</P>
391 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
403 <P>you will be left with:-</P>
407 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
419 <P>the filter will be completely removed.</P>
420 <H2><A NAME="ss11.15">11.15</A> <A HREF="usermanual_en.html#toc11.15">clear/wcy [1|all]</A>
423 <P><CODE><B>clear/wcy [1|all]</B> Clear a WCY filter line</CODE></P>
425 <P>This command allows you to clear (remove) a line in a WCY filter or to
426 remove the whole filter.</P>
427 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
428 <H2><A NAME="ss11.16">11.16</A> <A HREF="usermanual_en.html#toc11.16">clear/wwv [1|all]</A>
431 <P><CODE><B>clear/wwv [1|all]</B> Clear a WWV filter line</CODE></P>
433 <P>This command allows you to clear (remove) a line in a WWV filter or to
434 remove the whole filter.</P>
435 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
436 <H2><A NAME="ss11.17">11.17</A> <A HREF="usermanual_en.html#toc11.17">dbavail</A>
439 <P><CODE><B>dbavail</B> Show a list of all the Databases in the system</CODE></P>
441 <P>Title says it all really, this command lists all the databases defined
442 in the system. It is also aliased to SHOW/COMMAND.</P>
443 <H2><A NAME="ss11.18">11.18</A> <A HREF="usermanual_en.html#toc11.18">dbshow <dbname> <key></A>
446 <P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE></P>
448 <P>This is the generic user interface to the database to the database system.
449 It is expected that the sysop will add an entry to the local Aliases file
450 so that users can use the more familiar AK1A style of enquiry such as:</P>
458 <P>but if he hasn't and the database really does exist (use DBAVAIL or
459 SHOW/COMMAND to find out) you can do the same thing with:</P>
468 <H2><A NAME="ss11.19">11.19</A> <A HREF="usermanual_en.html#toc11.19">directory</A>
471 <P><CODE><B>directory</B> List messages </CODE></P>
474 <H2><A NAME="ss11.20">11.20</A> <A HREF="usermanual_en.html#toc11.20">directory <from>-<to></A>
477 <P><CODE><B>directory <from>-<to></B> List messages <from> message <to> message </CODE></P>
479 <P>List the messages in the messages directory.</P>
480 <P>If there is a 'p' one space after the message number then it is a
481 personal message. If there is a '-' between the message number and the
482 'p' then this indicates that the message has been read.</P>
483 <P>You can use shell escape characters such as '*' and '?' in the <call>
485 <P>You can combine some of the various directory commands together eg:-</P>
496 DIR SUBJECT IOTA 200-250
500 <P>You can abbreviate all the commands to one letter and use ak1a syntax:-</P>
510 <H2><A NAME="ss11.21">11.21</A> <A HREF="usermanual_en.html#toc11.21">directory <nn></A>
513 <P><CODE><B>directory <nn></B> List last <nn> messages</CODE></P>
516 <H2><A NAME="ss11.22">11.22</A> <A HREF="usermanual_en.html#toc11.22">directory all</A>
519 <P><CODE><B>directory all</B> List all messages</CODE></P>
522 <H2><A NAME="ss11.23">11.23</A> <A HREF="usermanual_en.html#toc11.23">directory from <call></A>
525 <P><CODE><B>directory from <call></B> List all messages from <call></CODE></P>
528 <H2><A NAME="ss11.24">11.24</A> <A HREF="usermanual_en.html#toc11.24">directory new</A>
531 <P><CODE><B>directory new</B> List all new messages</CODE></P>
534 <H2><A NAME="ss11.25">11.25</A> <A HREF="usermanual_en.html#toc11.25">directory own</A>
537 <P><CODE><B>directory own</B> List your own messages</CODE></P>
540 <H2><A NAME="ss11.26">11.26</A> <A HREF="usermanual_en.html#toc11.26">directory subject <string></A>
543 <P><CODE><B>directory subject <string></B> List all messages with <string> in subject</CODE></P>
546 <H2><A NAME="ss11.27">11.27</A> <A HREF="usermanual_en.html#toc11.27">directory to <call></A>
549 <P><CODE><B>directory to <call></B> List all messages to <call></CODE></P>
552 <H2><A NAME="ss11.28">11.28</A> <A HREF="usermanual_en.html#toc11.28">dx [by <call>] <freq> <call> <remarks></A>
555 <P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE></P>
557 <P>This is how you send a DX Spot to other users. You can, in fact, now
558 enter the <freq> and the <call> either way round. </P>
568 <P>will all give the same result. You can add some remarks to the end
569 of the command and they will be added to the spot.</P>
573 DX FR0G 144600 this is a test
577 <P>You can credit someone else by saying:-</P>
581 DX by G1TLH FR0G 144.600 he isn't on the cluster
585 <P>The <freq> is compared against the available bands set up in the
586 cluster. See SHOW/BANDS for more information.</P>
587 <H2><A NAME="ss11.29">11.29</A> <A HREF="usermanual_en.html#toc11.29">echo <line></A>
590 <P><CODE><B>echo <line></B> Echo the line to the output</CODE></P>
592 <P>This command is useful in scripts and so forth for printing the
593 line that you give to the command to the output. You can use this
594 in user_default scripts and the SAVE command for titling and so forth</P>
595 <P>The script will interpret certain standard "escape" sequences as follows:-</P>
599 \t - becomes a TAB character (0x09 in ascii)
600 \a - becomes a BEEP character (0x07 in ascii)
601 \n - prints a new line
605 <P>So the following example:-</P>
609 echo GB7DJK is a dxcluster
617 GB7DJK is a dxcluster
621 <P>on the output. You don't need a \n on the end of the line you want to send.</P>
622 <P>A more complex example:-</P>
626 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
640 <P>on the output.</P>
642 <H2><A NAME="ss11.30">11.30</A> <A HREF="usermanual_en.html#toc11.30">filtering...</A>
645 <P><CODE><B>filtering...</B> Filtering things in DXSpider</CODE></P>
647 <P>There are a number of things you can filter in the DXSpider system. They
648 all use the same general mechanism.</P>
649 <P>In general terms you can create a 'reject' or an 'accept' filter which
650 can have up to 10 lines in it. You do this using, for example:-</P>
659 <P>where ..... are the specific commands for that type of filter. There
660 are filters for spots, wwv, announce, wcy and (for sysops)
661 connects. See each different accept or reject command reference for
663 <P>There is also a command to clear out one or more lines in a filter and
664 one to show you what you have set. They are:-</P>
681 <P>There is clear/xxxx command for each type of filter.</P>
682 <P>For now we are going to use spots for the examples, but you can apply
683 the principles to all types of filter.</P>
684 <P>There are two main types of filter 'accept' or 'reject'; which you use
685 depends entirely on how you look at the world and what is least
686 writing to achieve what you want. Each filter has 10 lines (of any
687 length) which are tried in order. If a line matches then the action
688 you have specified is taken (ie reject means ignore it and accept
690 <P>The important thing to remember is that if you specify a 'reject'
691 filter (all the lines in it say 'reject/spots' (for instance)) then if
692 a spot comes in that doesn't match any of the lines then you will get
693 it BUT if you specify an 'accept' filter then any spots that don't
694 match are dumped. For example if I have a one line accept filter:-</P>
698 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
702 <P>then automatically you will ONLY get VHF spots from or to CQ zones 14
703 15 and 16. If you set a reject filter like:</P>
707 reject/spots on hf/cw
711 <P>Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
712 and will work it even on CW then you could say:-</P>
716 reject/spots on hf/cw and not info iota
720 <P>But in that case you might only be interested in iota and say:-</P>
724 accept/spots not on hf/cw or info iota
728 <P>which is exactly the same. You should choose one or the other until
729 you are confortable with the way it works. Yes, you can mix them
730 (actually you can have an accept AND a reject on the same line) but
731 don't try this at home until you can analyse the results that you get
732 without ringing up the sysop for help.</P>
733 <P>Another useful addition now is filtering by US state</P>
737 accept/spots by_state VA,NH,RI,ME
741 <P>You can arrange your filter lines into logical units, either for your
742 own understanding or simply convenience. I have one set frequently:-</P>
746 reject/spots 1 on hf/cw
747 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
751 <P>What this does is to ignore all HF CW spots (being a class B I can't
752 read any CW and couldn't possibly be interested in HF :-) and also
753 rejects any spots on VHF which don't either originate or spot someone
755 <P>This is an exmaple where you would use the line number (1 and 2 in
756 this case), if you leave the digit out, the system assumes '1'. Digits
757 '0'-'9' are available.</P>
758 <P>You can leave the word 'and' out if you want, it is implied. You can
759 use any number of brackets to make the 'expression' as you want
760 it. There are things called precedence rules working here which mean
761 that you will NEED brackets in a situation like line 2 because,
762 without it, will assume:-</P>
766 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
770 <P>annoying, but that is the way it is. If you use OR - use
771 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
772 just 'and by_zone'.</P>
773 <P>If you want to alter your filter you can just redefine one or more
774 lines of it or clear out one line. For example:-</P>
778 reject/spots 1 on hf/ssb
790 <P>To remove the filter in its entirty:-</P>
798 <P>There are similar CLEAR commands for the other filters:-</P>
808 <P>ADVANCED USERS:-</P>
809 <P>Once you are happy with the results you get, you may like to experiment. </P>
810 <P>my example that filters hf/cw spots and accepts vhf/uhf spots from EU
811 can be written with a mixed filter, eg:</P>
817 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
821 <P>each filter slot actually has a 'reject' slot and an 'accept'
822 slot. The reject slot is executed BEFORE the accept slot.</P>
823 <P>It was mentioned earlier that after a reject test that doesn't match,
824 the default for following tests is 'accept', the reverse is true for
825 'accept'. In the example what happens is that the reject is executed
826 first, any non hf/cw spot is passed to the accept line, which lets
827 thru everything else on HF.</P>
828 <P>The next filter line lets through just VHF/UHF spots from EU.</P>
829 <H2><A NAME="ss11.31">11.31</A> <A HREF="usermanual_en.html#toc11.31">help</A>
832 <P><CODE><B>help</B> The HELP Command</CODE></P>
834 <P>HELP is available for a number of commands. The syntax is:-</P>
842 <P>Where <cmd> is the name of the command you want help on.</P>
843 <P>All commands can be abbreviated, so SHOW/DX can be abbreviated
844 to SH/DX, ANNOUNCE can be shortened to AN and so on.</P>
845 <P>Look at the APROPOS <string> command which will search the help database
846 for the <string> you specify and give you a list of likely commands
847 to look at with HELP.</P>
848 <H2><A NAME="ss11.32">11.32</A> <A HREF="usermanual_en.html#toc11.32">join <group></A>
851 <P><CODE><B>join <group></B> Join a chat or conference group</CODE></P>
853 <P>JOIN allows you to join a network wide conference group. To join a
854 group (called FOC in this case) type:-</P>
862 <P>See also CHAT, LEAVE, SHOW/CHAT</P>
863 <H2><A NAME="ss11.33">11.33</A> <A HREF="usermanual_en.html#toc11.33">kill <from msgno>-<to msgno></A>
866 <P><CODE><B>kill <from msgno>-<to msgno></B> Delete a range of messages</CODE></P>
869 <H2><A NAME="ss11.34">11.34</A> <A HREF="usermanual_en.html#toc11.34">kill <msgno> [<msgno..]</A>
872 <P><CODE><B>kill <msgno> [<msgno..]</B> Delete a message from the local system</CODE></P>
875 <H2><A NAME="ss11.35">11.35</A> <A HREF="usermanual_en.html#toc11.35">kill <msgno> [<msgno> ...]</A>
878 <P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system</CODE></P>
880 <P>You can get rid of any message to or originating from your callsign using
881 this command. You can remove more than one message at a time.</P>
882 <H2><A NAME="ss11.36">11.36</A> <A HREF="usermanual_en.html#toc11.36">kill from <regex></A>
885 <P><CODE><B>kill from <regex></B> Delete messages FROM a callsign or pattern</CODE></P>
888 <H2><A NAME="ss11.37">11.37</A> <A HREF="usermanual_en.html#toc11.37">kill to <regex></A>
891 <P><CODE><B>kill to <regex></B> Delete messages TO a callsign or pattern</CODE></P>
894 <H2><A NAME="ss11.38">11.38</A> <A HREF="usermanual_en.html#toc11.38">leave <group></A>
897 <P><CODE><B>leave <group></B> Leave a chat or conference group</CODE></P>
899 <P>LEAVE allows you to leave a network wide conference group. To leave a
900 group (called FOC in this case) type:-</P>
908 <P>See also CHAT, JOIN, SHOW/CHAT</P>
909 <H2><A NAME="ss11.39">11.39</A> <A HREF="usermanual_en.html#toc11.39">links</A>
912 <P><CODE><B>links</B> Show which nodes is physically connected</CODE></P>
914 <P>This is a quick listing that shows which links are connected and
915 some information about them. See WHO for a list of all connections.</P>
916 <H2><A NAME="ss11.40">11.40</A> <A HREF="usermanual_en.html#toc11.40">read</A>
919 <P><CODE><B>read</B> Read the next unread personal message addressed to you</CODE></P>
922 <H2><A NAME="ss11.41">11.41</A> <A HREF="usermanual_en.html#toc11.41">read <msgno></A>
925 <P><CODE><B>read <msgno></B> Read the specified message</CODE></P>
927 <P>You can read any messages that are sent as 'non-personal' and also any
928 message either sent by or sent to your callsign.</P>
929 <H2><A NAME="ss11.42">11.42</A> <A HREF="usermanual_en.html#toc11.42">reject</A>
932 <P><CODE><B>reject</B> Set a filter to reject something</CODE></P>
934 <P>Create a filter to reject something</P>
935 <P>There are 2 types of filter, accept and reject. See HELP FILTERING for more
937 <H2><A NAME="ss11.43">11.43</A> <A HREF="usermanual_en.html#toc11.43">reject/announce [0-9] <pattern></A>
940 <P><CODE><B>reject/announce [0-9] <pattern></B> Set a 'reject' filter line for announce</CODE></P>
942 <P>Create an 'reject this announce' line for a filter. </P>
943 <P>A reject filter line means that if the announce matches this filter it is
944 passed onto the user. See HELP FILTERING for more info. Please read this
945 to understand how filters work - it will save a lot of grief later on.</P>
946 <P>You can use any of the following things in this line:-</P>
950 info <string> eg: iota or qsl
951 by <prefixes> eg: G,M,2
952 origin <prefixes>
953 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
954 origin_itu <prefixes or numbers> or: G,GM,GW
955 origin_zone <prefixes or numbers>
956 origin_state <states> eg: VA,NH,RI,ME
957 by_dxcc <prefixes or numbers>
958 by_itu <prefixes or numbers>
959 by_zone <prefixes or numbers>
960 by_state <states> eg: VA,NH,RI,ME
961 channel <prefixes>
962 wx 1 filter WX announces
963 dest <prefixes> eg: 6MUK,WDX (distros)
967 <P>some examples:-</P>
971 rej/ann by_zone 14,15,16 and not by G,M,2
975 <P>You can use the tag 'all' to reject everything eg:</P>
983 <P>but this probably for advanced users...</P>
984 <H2><A NAME="ss11.44">11.44</A> <A HREF="usermanual_en.html#toc11.44">reject/spots [0-9] <pattern></A>
987 <P><CODE><B>reject/spots [0-9] <pattern></B> Set a 'reject' filter line for spots</CODE></P>
989 <P>Create a 'reject this spot' line for a filter. </P>
990 <P>A reject filter line means that if the spot matches this filter it is
991 dumped (not passed on). See HELP FILTERING for more info. Please read this
992 to understand how filters work - it will save a lot of grief later on.</P>
993 <P>You can use any of the following things in this line:-</P>
997 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
998 on <range> same as 'freq'
999 call <prefixes> eg: G,PA,HB9
1000 info <string> eg: iota or qsl
1002 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1003 call_itu <prefixes or numbers> or: G,GM,GW
1004 call_zone <prefixes or numbers>
1005 call_state <states> eg: VA,NH,RI,ME
1006 by_dxcc <prefixes or numbers>
1007 by_itu <prefixes or numbers>
1008 by_zone <prefixes or numbers>
1009 by_state <states> eg: VA,NH,RI,ME
1010 origin <prefixes>
1011 channel <prefixes>
1013 </CODE></BLOCKQUOTE>
1015 <P>'call' means the callsign that has spotted 'by' whoever.</P>
1016 <P>For frequencies, you can use any of the band names defined in
1017 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1018 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1019 this is more efficient than saying simply: on HF (but don't get
1020 too hung up about that)</P>
1021 <P>some examples:-</P>
1026 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1028 </CODE></BLOCKQUOTE>
1030 <P>You can use the tag 'all' to reject everything eg:</P>
1036 </CODE></BLOCKQUOTE>
1038 <P>but this probably for advanced users...</P>
1039 <H2><A NAME="ss11.45">11.45</A> <A HREF="usermanual_en.html#toc11.45">reject/wcy [0-9] <pattern></A>
1042 <P><CODE><B>reject/wcy [0-9] <pattern></B> set a 'reject' WCY filter</CODE></P>
1044 <P>It is unlikely that you will want to do this, but if you do then you can
1045 filter on the following fields:-</P>
1049 by <prefixes> eg: G,M,2
1050 origin <prefixes>
1051 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1052 origin_itu <prefixes or numbers> or: G,GM,GW
1053 origin_zone <prefixes or numbers>
1054 by_dxcc <prefixes or numbers>
1055 by_itu <prefixes or numbers>
1056 by_zone <prefixes or numbers>
1057 channel <prefixes>
1059 </CODE></BLOCKQUOTE>
1061 <P>There are no examples because WCY Broadcasts only come from one place and
1062 you either want them or not (see UNSET/WCY if you don't want them).</P>
1063 <P>This command is really provided for future use.</P>
1064 <P>See HELP FILTER for information.</P>
1065 <H2><A NAME="ss11.46">11.46</A> <A HREF="usermanual_en.html#toc11.46">reject/wwv [0-9] <pattern></A>
1068 <P><CODE><B>reject/wwv [0-9] <pattern></B> set a 'reject' WWV filter</CODE></P>
1070 <P>It is unlikely that you will want to do this, but if you do then you can
1071 filter on the following fields:-</P>
1075 by <prefixes> eg: G,M,2
1076 origin <prefixes>
1077 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1078 origin_itu <prefixes or numbers> or: G,GM,GW
1079 origin_zone <prefixes or numbers>
1080 by_dxcc <prefixes or numbers>
1081 by_itu <prefixes or numbers>
1082 by_zone <prefixes or numbers>
1083 channel <prefixes>
1085 </CODE></BLOCKQUOTE>
1091 reject/wwv by_zone 14,15,16
1093 </CODE></BLOCKQUOTE>
1095 <P>is probably the only useful thing to do (which will only show WWV broadcasts
1096 by stations in the US).</P>
1097 <P>See HELP FILTER for information.</P>
1098 <H2><A NAME="ss11.47">11.47</A> <A HREF="usermanual_en.html#toc11.47">reply</A>
1101 <P><CODE><B>reply</B> Reply (privately) to the last message that you have read</CODE></P>
1104 <H2><A NAME="ss11.48">11.48</A> <A HREF="usermanual_en.html#toc11.48">reply <msgno></A>
1107 <P><CODE><B>reply <msgno></B> Reply (privately) to the specified message</CODE></P>
1110 <H2><A NAME="ss11.49">11.49</A> <A HREF="usermanual_en.html#toc11.49">reply b <msgno></A>
1113 <P><CODE><B>reply b <msgno></B> Reply as a Bulletin to the specified message</CODE></P>
1116 <H2><A NAME="ss11.50">11.50</A> <A HREF="usermanual_en.html#toc11.50">reply noprivate <msgno></A>
1119 <P><CODE><B>reply noprivate <msgno></B> Reply as a Bulletin to the specified message</CODE></P>
1122 <H2><A NAME="ss11.51">11.51</A> <A HREF="usermanual_en.html#toc11.51">reply rr <msgno></A>
1125 <P><CODE><B>reply rr <msgno></B> Reply to the specified message with read receipt</CODE></P>
1127 <P>You can reply to a message and the subject will automatically have
1128 "Re:" inserted in front of it, if it isn't already present.</P>
1129 <P>You can also use all the extra qualifiers such as RR, PRIVATE,
1130 NOPRIVATE, B that you can use with the SEND command (see SEND
1131 for further details)</P>
1132 <H2><A NAME="ss11.52">11.52</A> <A HREF="usermanual_en.html#toc11.52">send <call> [<call> ...]</A>
1135 <P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns</CODE></P>
1138 <H2><A NAME="ss11.53">11.53</A> <A HREF="usermanual_en.html#toc11.53">send copy <msgno> <call></A>
1141 <P><CODE><B>send copy <msgno> <call></B> Send a copy of a message to someone</CODE></P>
1144 <H2><A NAME="ss11.54">11.54</A> <A HREF="usermanual_en.html#toc11.54">send noprivate <call></A>
1147 <P><CODE><B>send noprivate <call></B> Send a message to all stations</CODE></P>
1149 <P>All the SEND commands will create a message which will be sent either to
1150 an individual callsign or to one of the 'bulletin' addresses. </P>
1151 <P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1152 it will mark the message as personal and send it to the cluster node that
1153 that callsign is connected to. If the <call> you have specified is in fact
1154 a known bulletin category on your node (eg: ALL) then the message should
1155 automatically become a bulletin.</P>
1156 <P>You can have more than one callsign in all of the SEND commands.</P>
1157 <P>You can have multiple qualifiers so that you can have for example:-</P>
1161 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1163 </CODE></BLOCKQUOTE>
1165 <P>which should send a copy of message 123 to G1TLH and G0RDI and you will
1166 receive a read receipt when they have read the message.</P>
1167 <P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1168 SP is an alias for SEND PRIVATE</P>
1169 <P>The system will ask you for a subject. Conventionally this should be
1170 no longer than 29 characters for compatibility. Most modern cluster
1171 software should accept more.</P>
1172 <P>You will now be prompted to start entering your text. </P>
1173 <P>You finish the message by entering '/EX' on a new line. For instance:</P>
1182 </CODE></BLOCKQUOTE>
1184 <P>If you have started a message and you don't want to keep it then you
1185 can abandon the message with '/ABORT' on a new line, like:-</P>
1191 oh I just can't be bothered with this
1194 </CODE></BLOCKQUOTE>
1196 <P>If you abort the message it will NOT be sent.</P>
1197 <P>When you are entering the text of your message, most normal output (such
1198 as DX announcements and so on are suppressed and stored for latter display
1199 (upto 20 such lines are stored, as new ones come along, so the oldest
1200 lines are dropped).</P>
1201 <P>Also, you can enter normal commands commands (and get the output
1202 immediately) whilst in the middle of a message. You do this by typing
1203 the command preceeded by a '/' character on a new line, so:-</P>
1207 /dx g1tlh 144010 strong signal
1209 </CODE></BLOCKQUOTE>
1211 <P>Will issue a dx annoucement to the rest of the cluster. </P>
1212 <P>Also, you can add the output of a command to your message by preceeding
1213 the command with '//', thus :-</P>
1219 </CODE></BLOCKQUOTE>
1221 <P>This will show YOU the output from SH/VHFTABLE and also store it in the
1223 <P>You can carry on with the message until you are ready to send it. </P>
1224 <H2><A NAME="ss11.55">11.55</A> <A HREF="usermanual_en.html#toc11.55">send private <call></A>
1227 <P><CODE><B>send private <call></B> Send a personal message</CODE></P>
1230 <H2><A NAME="ss11.56">11.56</A> <A HREF="usermanual_en.html#toc11.56">send rr <call></A>
1233 <P><CODE><B>send rr <call></B> Send a message and ask for a read receipt</CODE></P>
1236 <H2><A NAME="ss11.57">11.57</A> <A HREF="usermanual_en.html#toc11.57">set/address <your address></A>
1239 <P><CODE><B>set/address <your address></B> Record your postal address</CODE></P>
1242 <H2><A NAME="ss11.58">11.58</A> <A HREF="usermanual_en.html#toc11.58">set/announce</A>
1245 <P><CODE><B>set/announce</B> Allow announce messages to come out on your terminal</CODE></P>
1248 <H2><A NAME="ss11.59">11.59</A> <A HREF="usermanual_en.html#toc11.59">set/anntalk</A>
1251 <P><CODE><B>set/anntalk</B> Allow talk like announce messages on your terminal</CODE></P>
1254 <H2><A NAME="ss11.60">11.60</A> <A HREF="usermanual_en.html#toc11.60">set/beep</A>
1257 <P><CODE><B>set/beep</B> Add a beep to DX and other messages on your terminal</CODE></P>
1260 <H2><A NAME="ss11.61">11.61</A> <A HREF="usermanual_en.html#toc11.61">set/dx</A>
1263 <P><CODE><B>set/dx</B> Allow DX messages to come out on your terminal</CODE></P>
1266 <H2><A NAME="ss11.62">11.62</A> <A HREF="usermanual_en.html#toc11.62">set/dxcq</A>
1269 <P><CODE><B>set/dxcq</B> Show CQ Zones on the end of DX announcements</CODE></P>
1272 <H2><A NAME="ss11.63">11.63</A> <A HREF="usermanual_en.html#toc11.63">set/dxgrid</A>
1275 <P><CODE><B>set/dxgrid</B> Allow QRA Grid Squares on the end of DX announcements</CODE></P>
1278 <H2><A NAME="ss11.64">11.64</A> <A HREF="usermanual_en.html#toc11.64">set/dxitu</A>
1281 <P><CODE><B>set/dxitu</B> Show ITU Zones on the end of DX announcements</CODE></P>
1284 <H2><A NAME="ss11.65">11.65</A> <A HREF="usermanual_en.html#toc11.65">set/echo</A>
1287 <P><CODE><B>set/echo</B> Make the cluster echo your input</CODE></P>
1290 <H2><A NAME="ss11.66">11.66</A> <A HREF="usermanual_en.html#toc11.66">set/email <email> ...</A>
1293 <P><CODE><B>set/email <email> ...</B> Set email address(es) and forward your personals</CODE></P>
1296 <H2><A NAME="ss11.67">11.67</A> <A HREF="usermanual_en.html#toc11.67">set/here</A>
1299 <P><CODE><B>set/here</B> Tell the system you are present at your terminal</CODE></P>
1302 <H2><A NAME="ss11.68">11.68</A> <A HREF="usermanual_en.html#toc11.68">set/homenode <node> </A>
1305 <P><CODE><B>set/homenode <node> </B> Set your normal cluster callsign</CODE></P>
1307 <P>Tell the cluster system where you normally connect to. Any Messages sent
1308 to you will normally find their way there should you not be connected.
1314 </CODE></BLOCKQUOTE>
1317 <H2><A NAME="ss11.69">11.69</A> <A HREF="usermanual_en.html#toc11.69">set/language <lang></A>
1320 <P><CODE><B>set/language <lang></B> Set the language you want to use</CODE></P>
1322 <P>You can select the language that you want the cluster to use. Currently
1323 the languages available are en (English), de (German), es (Spanish)
1325 <H2><A NAME="ss11.70">11.70</A> <A HREF="usermanual_en.html#toc11.70">set/location <lat & long></A>
1328 <P><CODE><B>set/location <lat & long></B> Set your latitude and longitude</CODE></P>
1331 <H2><A NAME="ss11.71">11.71</A> <A HREF="usermanual_en.html#toc11.71">set/logininfo</A>
1334 <P><CODE><B>set/logininfo</B> Inform when a station logs in locally</CODE></P>
1337 <H2><A NAME="ss11.72">11.72</A> <A HREF="usermanual_en.html#toc11.72">set/name <your name></A>
1340 <P><CODE><B>set/name <your name></B> Set your name</CODE></P>
1342 <P>Tell the system what your name is eg:-
1347 </CODE></BLOCKQUOTE>
1350 <H2><A NAME="ss11.73">11.73</A> <A HREF="usermanual_en.html#toc11.73">set/page <lines per page></A>
1353 <P><CODE><B>set/page <lines per page></B> Set the lines per page</CODE></P>
1355 <P>Tell the system how many lines you wish on a page when the number of line
1356 of output from a command is more than this. The default is 20. Setting it
1357 explicitly to 0 will disable paging.
1363 </CODE></BLOCKQUOTE>
1365 <P>The setting is stored in your user profile.</P>
1366 <H2><A NAME="ss11.74">11.74</A> <A HREF="usermanual_en.html#toc11.74">set/password</A>
1369 <P><CODE><B>set/password</B> Set your own password</CODE></P>
1371 <P>This command only works for a 'telnet' user (currently). It will
1372 only work if you have a password already set. This initial password
1373 can only be set by the sysop.</P>
1374 <P>When you execute this command it will ask you for your old password,
1375 then ask you to type in your new password twice (to make sure you
1376 get it right). You may or may not see the data echoed on the screen
1377 as you type, depending on the type of telnet client you have.</P>
1378 <H2><A NAME="ss11.75">11.75</A> <A HREF="usermanual_en.html#toc11.75">set/prompt <string></A>
1381 <P><CODE><B>set/prompt <string></B> Set your prompt to <string></CODE></P>
1384 <H2><A NAME="ss11.76">11.76</A> <A HREF="usermanual_en.html#toc11.76">set/qra <locator></A>
1387 <P><CODE><B>set/qra <locator></B> Set your QRA Grid locator</CODE></P>
1389 <P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
1390 done a SET/LOCATION then your latitude and longitude will be set roughly
1391 correctly (assuming your locator is correct ;-). For example:-
1396 </CODE></BLOCKQUOTE>
1399 <H2><A NAME="ss11.77">11.77</A> <A HREF="usermanual_en.html#toc11.77">set/qth <your qth></A>
1402 <P><CODE><B>set/qth <your qth></B> Set your QTH</CODE></P>
1404 <P>Tell the system where you are. For example:-
1407 SET/QTH East Dereham, Norfolk
1409 </CODE></BLOCKQUOTE>
1412 <H2><A NAME="ss11.78">11.78</A> <A HREF="usermanual_en.html#toc11.78">set/talk</A>
1415 <P><CODE><B>set/talk</B> Allow TALK messages to come out on your terminal</CODE></P>
1418 <H2><A NAME="ss11.79">11.79</A> <A HREF="usermanual_en.html#toc11.79">set/usstate</A>
1421 <P><CODE><B>set/usstate</B> Allow US State info on the end of DX announcements</CODE></P>
1424 <H2><A NAME="ss11.80">11.80</A> <A HREF="usermanual_en.html#toc11.80">set/wcy</A>
1427 <P><CODE><B>set/wcy</B> Allow WCY messages to come out on your terminal</CODE></P>
1430 <H2><A NAME="ss11.81">11.81</A> <A HREF="usermanual_en.html#toc11.81">set/wwv</A>
1433 <P><CODE><B>set/wwv</B> Allow WWV messages to come out on your terminal</CODE></P>
1436 <H2><A NAME="ss11.82">11.82</A> <A HREF="usermanual_en.html#toc11.82">set/wx</A>
1439 <P><CODE><B>set/wx</B> Allow WX messages to come out on your terminal</CODE></P>
1442 <H2><A NAME="ss11.83">11.83</A> <A HREF="usermanual_en.html#toc11.83">show/chat [<group>] [<lines>]</A>
1445 <P><CODE><B>show/chat [<group>] [<lines>]</B> Show any chat or conferencing </CODE></P>
1447 <P>This command allows you to see any chat or conferencing that has
1448 occurred whilst you were away. SHOW/CHAT on its own will show data for
1449 all groups. If you use a group name then it will show only chat for
1451 <H2><A NAME="ss11.84">11.84</A> <A HREF="usermanual_en.html#toc11.84">show/configuration [<node>]</A>
1454 <P><CODE><B>show/configuration [<node>]</B> Show all the nodes and users visible</CODE></P>
1456 <P>This command allows you to see all the users that can be seen
1457 and the nodes to which they are connected.</P>
1458 <P>This command is normally abbreviated to: sh/c</P>
1459 <P>Normally, the list returned will be just for the nodes from your
1460 country (because the list otherwise will be very long).</P>
1466 </CODE></BLOCKQUOTE>
1468 <P>will produce a complete list of all nodes. </P>
1469 <P>BE WARNED: the list that is returned can be VERY long</P>
1470 <P>It is possible to supply a node or part of a prefix and you will get
1471 a list of the users for that node or list of nodes starting with
1478 </CODE></BLOCKQUOTE>
1485 </CODE></BLOCKQUOTE>
1488 <H2><A NAME="ss11.85">11.85</A> <A HREF="usermanual_en.html#toc11.85">show/configuration/node</A>
1491 <P><CODE><B>show/configuration/node</B> Show all the nodes connected locally</CODE></P>
1493 <P>Show all the nodes connected to this node.</P>
1494 <H2><A NAME="ss11.86">11.86</A> <A HREF="usermanual_en.html#toc11.86">show/contest <year and month></A>
1497 <P><CODE><B>show/contest <year and month></B> Show all the contests for a month</CODE></P>
1499 <P>Show all known contests which are maintained at http://www.sk3bg.se/contest/
1500 for a particular month or year. The format is reasonably flexible.
1508 </CODE></BLOCKQUOTE>
1511 <H2><A NAME="ss11.87">11.87</A> <A HREF="usermanual_en.html#toc11.87">show/date [<prefix>|<callsign>]</A>
1514 <P><CODE><B>show/date [<prefix>|<callsign>]</B> Show the local time </CODE></P>
1516 <P>This is very nearly the same as SHOW/TIME, the only difference the format
1517 of the date string if no arguments are given.</P>
1518 <P>If no prefixes or callsigns are given then this command returns the local
1519 time and UTC as the computer has it right now. If you give some prefixes
1520 then it will show UTC and UTC + the local offset (not including DST) at
1521 the prefixes or callsigns that you specify.</P>
1522 <H2><A NAME="ss11.88">11.88</A> <A HREF="usermanual_en.html#toc11.88">show/db0sdx <callsign></A>
1525 <P><CODE><B>show/db0sdx <callsign></B> Show QSL infomation from DB0SDX database</CODE></P>
1527 <P>This command queries the DB0SDX QSL server on the internet
1528 and returns any information available for that callsign. This service
1529 is provided for users of this software by http://www.qslinfo.de.</P>
1530 <P>See also SHOW/QRZ, SHOW/WM7D.</P>
1531 <H2><A NAME="ss11.89">11.89</A> <A HREF="usermanual_en.html#toc11.89">show/dx</A>
1534 <P><CODE><B>show/dx</B> Interrogate the spot database</CODE></P>
1536 <P>If you just type SHOW/DX you will get the last so many spots
1537 (sysop configurable, but usually 10).</P>
1538 <P>In addition you can add any number of these commands in very nearly
1539 any order to the basic SHOW/DX command, they are:-</P>
1543 on <band> - eg 160m 20m 2m 23cm 6mm
1544 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1545 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
1546 <from>-<to>
1548 </CODE></BLOCKQUOTE>
1553 <number> - the number of spots you want
1554 <from>-<to> - <from> spot no <to> spot no in the selected list
1555 <from>/<to>
1557 </CODE></BLOCKQUOTE>
1562 <prefix> - for a spotted callsign beginning with <prefix>
1563 *<suffix> - for a spotted callsign ending in <suffix>
1564 *<string>* - for a spotted callsign containing <string>
1566 </CODE></BLOCKQUOTE>
1571 day <number> - starting <number> days ago
1572 day <from>-<to> - <from> days <to> days ago
1573 <from>/<to>
1575 </CODE></BLOCKQUOTE>
1580 info <text> - any spots containing <text> in the info or remarks
1582 </CODE></BLOCKQUOTE>
1587 by <call> - any spots spotted by <call> (spotter <call> is the
1590 </CODE></BLOCKQUOTE>
1595 qsl - this automatically looks for any qsl info on the call
1596 held in the spot database.
1598 </CODE></BLOCKQUOTE>
1603 iota [<iota>] - If the iota island number is missing it will look for
1604 the string iota and anything which looks like an iota
1605 island number. If you specify then it will look for
1608 </CODE></BLOCKQUOTE>
1613 qra [<locator>] - this will look for the specific locator if you specify
1614 one or else anything that looks like a locator.
1616 </CODE></BLOCKQUOTE>
1621 dxcc - treat the prefix as a 'country' and look for spots
1622 from that country regardless of actual prefix.
1625 </CODE></BLOCKQUOTE>
1630 You can also use this with the 'by' keyword so
1633 </CODE></BLOCKQUOTE>
1640 </CODE></BLOCKQUOTE>
1646 SH/DX on 20m info iota
1647 SH/DX 9a on vhf day 30
1653 SH/DX dxcc oq2 by w dxcc
1655 </CODE></BLOCKQUOTE>
1658 <H2><A NAME="ss11.90">11.90</A> <A HREF="usermanual_en.html#toc11.90">show/dxcc <prefix></A>
1661 <P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE></P>
1663 <P>This command takes the <prefix> (which can be a full or partial
1664 callsign if desired), looks up which internal country number it is
1665 and then displays all the spots as per SH/DX for that country.</P>
1666 <P>This is now an alias for 'SHOW/DX DXCC' </P>
1667 <P>The options for SHOW/DX also apply to this command.
1673 SH/DXCC W on 20m iota
1675 </CODE></BLOCKQUOTE>
1677 <P>This can be done with the SHOW/DX command like this:-</P>
1682 SH/DX dxcc w on 20m iota
1684 </CODE></BLOCKQUOTE>
1687 <H2><A NAME="ss11.91">11.91</A> <A HREF="usermanual_en.html#toc11.91">show/dxqsl <callsign></A>
1690 <P><CODE><B>show/dxqsl <callsign></B> Show any QSL info gathered from spots</CODE></P>
1692 <P>The node collects information from the comment fields in spots (things
1693 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.</P>
1694 <P>This command allows you to interrogate that database and if the callsign
1695 is found will display the manager(s) that people have spotted. This
1696 information is NOT reliable, but it is normally reasonably accurate if
1697 it is spotted enough times.</P>
1698 <P>For example:-</P>
1704 </CODE></BLOCKQUOTE>
1706 <P>You can check the raw input spots yourself with:-</P>
1712 </CODE></BLOCKQUOTE>
1714 <P>This gives you more background information.</P>
1715 <H2><A NAME="ss11.92">11.92</A> <A HREF="usermanual_en.html#toc11.92">show/dxstats [days] [date]</A>
1718 <P><CODE><B>show/dxstats [days] [date]</B> Show the DX Statistics</CODE></P>
1720 <P>Show the total DX spots for the last <days> no of days (default is 31),
1721 starting from a <date> (default: today).</P>
1722 <H2><A NAME="ss11.93">11.93</A> <A HREF="usermanual_en.html#toc11.93">show/files [<filearea> [<string>]]</A>
1725 <P><CODE><B>show/files [<filearea> [<string>]]</B> List the contents of a filearea</CODE></P>
1727 <P>SHOW/FILES on its own will show you a list of the various fileareas
1728 available on the system. To see the contents of a particular file
1732 SH/FILES <filearea>
1734 </CODE></BLOCKQUOTE>
1736 where <filearea> is the name of the filearea you want to see the
1738 <P>You can also use shell globbing characters like '*' and '?' in a
1739 string to see a selection of files in a filearea eg:-
1742 SH/FILES bulletins arld*
1744 </CODE></BLOCKQUOTE>
1746 <P>See also TYPE - to see the contents of a file.</P>
1747 <H2><A NAME="ss11.94">11.94</A> <A HREF="usermanual_en.html#toc11.94">show/filter</A>
1750 <P><CODE><B>show/filter</B> Show the contents of all the filters you have set</CODE></P>
1752 <P>Show the contents of all the filters that are set. This command displays
1753 all the filters set - for all the various categories.</P>
1754 <H2><A NAME="ss11.95">11.95</A> <A HREF="usermanual_en.html#toc11.95">show/hfstats [days] [date]</A>
1757 <P><CODE><B>show/hfstats [days] [date]</B> Show the HF DX Statistics </CODE></P>
1759 <P>Show the HF DX spots breakdown by band for the last <days> no of days
1760 (default is 31), starting from a <date> (default: today).</P>
1761 <H2><A NAME="ss11.96">11.96</A> <A HREF="usermanual_en.html#toc11.96">show/hftable [days] [date] [prefix ...]</A>
1764 <P><CODE><B>show/hftable [days] [date] [prefix ...]</B> Show the HF DX Spotter Table</CODE></P>
1766 <P>Show the HF DX Spotter table for the list of prefixes for the last
1767 <days> no of days (default is 31), starting from a <date> (default: today).</P>
1768 <P>If there are no prefixes then it will show the table for your country.</P>
1769 <P>Remember that some countries have more than one "DXCC country" in them
1770 (eg G :-), to show them (assuming you are not in G already which is
1771 specially treated in the code) you must list all the relevant prefixes</P>
1775 sh/hftable g gm gd gi gj gw gu
1777 </CODE></BLOCKQUOTE>
1779 <P>Note that the prefixes are converted into country codes so you don't have
1780 to list all possible prefixes for each country.</P>
1781 <P>If you want more or less days than the default simply include the
1782 number you require:-</P>
1788 </CODE></BLOCKQUOTE>
1790 <P>If you want to start at a different day, simply add the date in some
1791 recognizable form:-</P>
1795 sh/hftable 2 25nov02
1796 sh/hftable 2 25-nov-02
1798 sh/hftable 2 25/11/02
1800 </CODE></BLOCKQUOTE>
1802 <P>This will show the stats for your DXCC for that CQWW contest weekend. </P>
1803 <P>You can specify either prefixes or full callsigns (so you can see how you
1804 did against all your mates). You can also say 'all' which will then print
1805 the worldwide statistics.</P>
1811 </CODE></BLOCKQUOTE>
1814 <H2><A NAME="ss11.97">11.97</A> <A HREF="usermanual_en.html#toc11.97">show/moon [ndays] [<prefix>|<callsign>]</A>
1817 <P><CODE><B>show/moon [ndays] [<prefix>|<callsign>]</B> Show Moon rise and set times</CODE></P>
1819 <P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
1820 together with the azimuth and elevation of the sun currently at those
1822 <P>If you don't specify any prefixes or callsigns, it will show the times for
1823 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1824 together with the current azimuth and elevation.</P>
1825 <P>In addition, it will show the illuminated fraction of the moons disk.</P>
1826 <P>If all else fails it will show the Moonrise and set times for the node
1827 that you are connected to. </P>
1828 <P>For example:-</P>
1835 </CODE></BLOCKQUOTE>
1837 <P>You can also use this command to see into the past or the future, so
1838 if you want to see yesterday's times then do:-</P>
1844 </CODE></BLOCKQUOTE>
1846 <P>or in three days time:-</P>
1852 </CODE></BLOCKQUOTE>
1854 <P>Upto 366 days can be checked both in the past and in the future.</P>
1855 <P>Please note that the rise and set times are given as the UT times of rise and
1856 set on the requested UT day.</P>
1857 <H2><A NAME="ss11.98">11.98</A> <A HREF="usermanual_en.html#toc11.98">show/muf <prefix> [<hours>][long]</A>
1860 <P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show the likely propagation to a prefix</CODE></P>
1862 <P>This command allow you to estimate the likelihood of you contacting
1863 a station with the prefix you have specified. The output assumes a modest
1864 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)</P>
1865 <P>The result predicts the most likely operating frequencies and signal
1866 levels for high frequency (shortwave) radio propagation paths on
1867 specified days of the year and hours of the day. It is most useful for
1868 paths between 250 km and 6000 km, but can be used with reduced accuracy
1869 for paths shorter or longer than this.</P>
1870 <P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1871 used to predict the MUF given the predicted flux, day of the year,
1872 hour of the day and geographic coordinates of the transmitter and
1873 receiver. This routine is reasonably accurate for the purposes here,
1874 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1875 than the programs used by major shortwave broadcasting organizations,
1876 such as the Voice of America.</P>
1877 <P>The command will display some header information detailing its
1878 assumptions, together with the locations, latitude and longitudes and
1879 bearings. It will then show UTC (UT), local time at the other end
1880 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1881 (Zen) and the likely signal strengths. Then for each frequency for which
1882 the system thinks there is a likelihood of a circuit it prints a value.</P>
1883 <P>The value is currently a likely S meter reading based on the conventional
1884 6dB / S point scale. If the value has a '+' appended it means that it is
1885 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1886 there is likely to be much fading and by an 's' that the signal is likely
1888 <P>By default SHOW/MUF will show the next two hours worth of data. You
1889 can specify anything up to 24 hours worth of data by appending the no of
1890 hours required after the prefix. For example:-</P>
1896 </CODE></BLOCKQUOTE>
1902 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1903 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1904 Location Lat / Long Azim
1905 East Dereham, Norfolk 52 41 N 0 57 E 47
1906 United-States-W 43 0 N 87 54 W 299
1907 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1908 18 23 11.5 -35 mS0+ mS2 S3
1909 19 0 11.2 -41 mS0+ mS2 S3
1911 </CODE></BLOCKQUOTE>
1913 <P>indicating that you will have weak, fading circuits on top band and
1914 80m but usable signals on 40m (about S3).</P>
1921 </CODE></BLOCKQUOTE>
1923 <P>will get you the above display, but with the next 24 hours worth of
1924 propagation data.</P>
1931 </CODE></BLOCKQUOTE>
1933 <P>Gives you an estimate of the long path propagation characterics. It
1934 should be noted that the figures will probably not be very useful, nor
1935 terrible accurate, but it is included for completeness.</P>
1936 <H2><A NAME="ss11.99">11.99</A> <A HREF="usermanual_en.html#toc11.99">show/newconfiguration [<node>]</A>
1939 <P><CODE><B>show/newconfiguration [<node>]</B> Show all the nodes and users visible</CODE></P>
1941 <P>This command allows you to see all the users that can be seen
1942 and the nodes to which they are connected. </P>
1943 <P>This command produces essentially the same information as
1944 SHOW/CONFIGURATION except that it shows all the duplication of
1945 any routes that might be present It also uses a different format
1946 which may not take up quite as much space if you don't have any
1948 <P>BE WARNED: the list that is returned can be VERY long</P>
1949 <H2><A NAME="ss11.100">11.100</A> <A HREF="usermanual_en.html#toc11.100">show/newconfiguration/node</A>
1952 <P><CODE><B>show/newconfiguration/node</B> Show all the nodes connected locally</CODE></P>
1954 <P>Show all the nodes connected to this node in the new format.</P>
1955 <H2><A NAME="ss11.101">11.101</A> <A HREF="usermanual_en.html#toc11.101">show/prefix <callsign></A>
1958 <P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database </CODE></P>
1960 <P>This command takes the <callsign> (which can be a full or partial
1961 callsign or a prefix), looks up which internal country number
1962 it is and then displays all the relevant prefixes for that country
1963 together with the internal country no, the CQ and ITU regions. </P>
1964 <P>See also SHOW/DXCC</P>
1965 <H2><A NAME="ss11.102">11.102</A> <A HREF="usermanual_en.html#toc11.102">show/qra <lat> <long></A>
1968 <P><CODE><B>show/qra <lat> <long></B> Convert lat/long to a QRA Grid locator</CODE></P>
1970 <P>This is a multipurpose command that allows you either to calculate the
1971 distance and bearing between two locators or (if only one locator is
1972 given on the command line) the distance and beraing from your station
1973 to the locator. For example:-</P>
1980 </CODE></BLOCKQUOTE>
1982 <P>The first example will show the distance and bearing to the locator from
1983 yourself, the second example will calculate the distance and bearing from
1984 the first locator to the second. You can use 4 or 6 character locators.</P>
1985 <P>It is also possible to convert a latitude and longitude to a locator by
1986 using this command with a latitude and longitude as an argument, for
1991 SH/QRA 52 41 N 0 58 E
1993 </CODE></BLOCKQUOTE>
1996 <H2><A NAME="ss11.103">11.103</A> <A HREF="usermanual_en.html#toc11.103">show/qra <locator> [<locator>]</A>
1999 <P><CODE><B>show/qra <locator> [<locator>]</B> Show distance between QRA Grid locators</CODE></P>
2002 <H2><A NAME="ss11.104">11.104</A> <A HREF="usermanual_en.html#toc11.104">show/qrz <callsign></A>
2005 <P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE></P>
2007 <P>This command queries the QRZ callbook server on the internet
2008 and returns any information available for that callsign. This service
2009 is provided for users of this software by http://www.qrz.com </P>
2010 <P>See also SHOW/WM7D for an alternative.</P>
2011 <H2><A NAME="ss11.105">11.105</A> <A HREF="usermanual_en.html#toc11.105">show/route <callsign> ...</A>
2014 <P><CODE><B>show/route <callsign> ...</B> Show the route to the callsign</CODE></P>
2016 <P>This command allows you to see to which node the callsigns specified are
2017 connected. It is a sort of inverse sh/config.</P>
2023 </CODE></BLOCKQUOTE>
2026 <H2><A NAME="ss11.106">11.106</A> <A HREF="usermanual_en.html#toc11.106">show/satellite <name> [<hours> <interval>]</A>
2029 <P><CODE><B>show/satellite <name> [<hours> <interval>]</B> Show tracking data</CODE></P>
2031 <P>Show the tracking data from your location to the satellite of your choice
2032 from now on for the next few hours.</P>
2033 <P>If you use this command without a satellite name it will display a list
2034 of all the satellites known currently to the system. </P>
2035 <P>If you give a name then you can obtain tracking data of all the passes
2036 that start and finish 5 degrees below the horizon. As default it will
2037 give information for the next three hours for every five minute period.</P>
2038 <P>You can alter the number of hours and the step size, within certain
2040 <P>Each pass in a period is separated with a row of '-----' characters</P>
2041 <P>So for example:-</P>
2046 SH/SAT FENGYUN1 12 2
2048 </CODE></BLOCKQUOTE>
2051 <H2><A NAME="ss11.107">11.107</A> <A HREF="usermanual_en.html#toc11.107">show/station [<callsign> ..]</A>
2054 <P><CODE><B>show/station [<callsign> ..]</B> Show information about a callsign</CODE></P>
2056 <P>Show the information known about a callsign and whether (and where)
2057 that callsign is connected to the cluster.</P>
2063 </CODE></BLOCKQUOTE>
2065 <P>If no callsign is given then show the information for yourself.</P>
2066 <H2><A NAME="ss11.108">11.108</A> <A HREF="usermanual_en.html#toc11.108">show/sun [ndays] [<prefix>|<callsign>]</A>
2069 <P><CODE><B>show/sun [ndays] [<prefix>|<callsign>]</B> Show sun rise and set times</CODE></P>
2071 <P>Show the sun rise and set times for a (list of) prefixes or callsigns,
2072 together with the azimuth and elevation of the sun currently at those
2074 <P>If you don't specify any prefixes or callsigns, it will show the times for
2075 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2076 together with the current azimuth and elevation.</P>
2077 <P>If all else fails it will show the sunrise and set times for the node
2078 that you are connected to. </P>
2079 <P>For example:-</P>
2084 SH/SUN G1TLH K9CW ZS
2086 </CODE></BLOCKQUOTE>
2088 <P>You can also use this command to see into the past or the future, so
2089 if you want to see yesterday's times then do:-</P>
2095 </CODE></BLOCKQUOTE>
2097 <P>or in three days time:-</P>
2103 </CODE></BLOCKQUOTE>
2105 <P>Upto 366 days can be checked both in the past and in the future.</P>
2106 <P>Please note that the rise and set times are given as the UT times of rise
2107 and set on the requested UT day.</P>
2108 <H2><A NAME="ss11.109">11.109</A> <A HREF="usermanual_en.html#toc11.109">show/time [<prefix>|<callsign>]</A>
2111 <P><CODE><B>show/time [<prefix>|<callsign>]</B> Show the local time </CODE></P>
2113 <P>If no prefixes or callsigns are given then this command returns the local
2114 time and UTC as the computer has it right now. If you give some prefixes
2115 then it will show UTC and UTC + the local offset (not including DST) at
2116 the prefixes or callsigns that you specify.</P>
2117 <H2><A NAME="ss11.110">11.110</A> <A HREF="usermanual_en.html#toc11.110">show/usdb [call ..]</A>
2120 <P><CODE><B>show/usdb [call ..]</B> Show information held on the FCC Call database</CODE></P>
2122 <P>Show the City and State of a Callsign held on the FCC database if
2123 his is being run on this system, eg:-</P>
2129 </CODE></BLOCKQUOTE>
2132 <H2><A NAME="ss11.111">11.111</A> <A HREF="usermanual_en.html#toc11.111">show/vhfstats [days] [date]</A>
2135 <P><CODE><B>show/vhfstats [days] [date]</B> Show the VHF DX Statistics</CODE></P>
2137 <P>Show the VHF DX spots breakdown by band for the last
2138 <days> no of days (default is 31), starting from a date (default: today).</P>
2139 <H2><A NAME="ss11.112">11.112</A> <A HREF="usermanual_en.html#toc11.112">show/vhftable [days] [date] [prefix ...]</A>
2142 <P><CODE><B>show/vhftable [days] [date] [prefix ...]</B> Show the VHF DX Spotter Table</CODE></P>
2144 <P>Show the VHF DX Spotter table for the list of prefixes for the last
2145 <days> no of days (default is 31), starting from a date (default: today).</P>
2146 <P>If there are no prefixes then it will show the table for your country.</P>
2147 <P>Remember that some countries have more than one "DXCC country" in them
2148 (eg G :-), to show them (assuming you are not in G already which is
2149 specially treated in the code) you must list all the relevant prefixes</P>
2153 sh/vhftable g gm gd gi gj gw gu
2155 </CODE></BLOCKQUOTE>
2157 <P>Note that the prefixes are converted into country codes so you don't have
2158 to list all possible prefixes for each country.</P>
2159 <P>If you want more or less days than the default simply include the
2160 number you require:-</P>
2166 </CODE></BLOCKQUOTE>
2168 <P>If you want to start at a different day, simply add the date in some
2169 recognizable form:-</P>
2173 sh/vhftable 2 25nov02
2174 sh/vhftable 2 25-nov-02
2175 sh/vhftable 2 021125
2176 sh/vhftable 2 25/11/02
2178 </CODE></BLOCKQUOTE>
2180 <P>This will show the stats for your DXCC for that CQWW contest weekend. </P>
2181 <P>You can specify either prefixes or full callsigns (so you can see how you
2182 did against all your mates). You can also say 'all' which will then print
2183 the worldwide statistics.</P>
2189 </CODE></BLOCKQUOTE>
2192 <H2><A NAME="ss11.113">11.113</A> <A HREF="usermanual_en.html#toc11.113">show/wcy</A>
2195 <P><CODE><B>show/wcy</B> Show last 10 WCY broadcasts</CODE></P>
2198 <H2><A NAME="ss11.114">11.114</A> <A HREF="usermanual_en.html#toc11.114">show/wcy <n></A>
2201 <P><CODE><B>show/wcy <n></B> Show last <n> WCY broadcasts</CODE></P>
2203 <P>Display the most recent WCY information that has been received by the system</P>
2205 <H2><A NAME="ss11.115">11.115</A> <A HREF="usermanual_en.html#toc11.115">show/wm7d <callsign></A>
2208 <P><CODE><B>show/wm7d <callsign></B> Show callbook details on a US callsigns</CODE></P>
2210 <P>This command queries the WM7D callbook server on the internet
2211 and returns any information available for that US callsign. This service
2212 is provided for users of this software by http://www.wm7d.net.</P>
2213 <P>See also SHOW/QRZ. </P>
2214 <H2><A NAME="ss11.116">11.116</A> <A HREF="usermanual_en.html#toc11.116">show/wwv</A>
2217 <P><CODE><B>show/wwv</B> Show last 10 WWV broadcasts</CODE></P>
2220 <H2><A NAME="ss11.117">11.117</A> <A HREF="usermanual_en.html#toc11.117">show/wwv <n></A>
2223 <P><CODE><B>show/wwv <n></B> Show last <n> WWV broadcasts</CODE></P>
2225 <P>Display the most recent WWV information that has been received by the system</P>
2226 <H2><A NAME="ss11.118">11.118</A> <A HREF="usermanual_en.html#toc11.118">sysop</A>
2229 <P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE></P>
2231 <P>The system automatically reduces your privilege level to that of a
2232 normal user if you login in remotely. This command allows you to
2233 regain your normal privilege level. It uses the normal system: five
2234 numbers are returned that are indexes into the character array that is
2235 your assigned password (see SET/PASSWORD). The indexes start from
2237 <P>You are expected to return a string which contains the characters
2238 required in the correct order. You may intersperse those characters
2239 with others to obscure your reply for any watchers. For example (and
2240 these values are for explanation :-):</P>
2244 password = 012345678901234567890123456789
2248 </CODE></BLOCKQUOTE>
2253 aa2bbbb0ccc5ddd7xxx3n
2257 </CODE></BLOCKQUOTE>
2259 <P>They will all match. If there is no password you will still be offered
2260 numbers but nothing will happen when you input a string. Any match is
2262 <H2><A NAME="ss11.119">11.119</A> <A HREF="usermanual_en.html#toc11.119">talk <call> > <node> [<text>]</A>
2265 <P><CODE><B>talk <call> > <node> [<text>]</B> Send a text message to another station via a node</CODE></P>
2267 <P>Send a short message to any other station that is visible on the cluster
2268 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2269 command, they don't have to be connected locally.</P>
2270 <P>The second form of TALK is used when other cluster nodes are connected
2271 with restricted information. This usually means that they don't send
2272 the user information usually associated with logging on and off the cluster.</P>
2273 <P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
2274 see GB7TLH in the SH/C list but with no users, then you would use the
2275 second form of the talk message.</P>
2276 <P>If you want to have a ragchew with someone you can leave the text message
2277 out and the system will go into 'Talk' mode. What this means is that a
2278 short message is sent to the recipient telling them that you are in a
2279 'Talking' frame of mind and then you just type - everything you send will
2280 go to the station that you asked for. </P>
2281 <P>All the usual announcements, spots and so on will still come out on your
2283 <P>If you want to do something (such as send a spot) you preceed the normal
2284 command with a '/' character, eg:-</P>
2288 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2291 </CODE></BLOCKQUOTE>
2293 <P>To leave talk mode type:</P>
2299 </CODE></BLOCKQUOTE>
2301 <P>If you are in 'Talk' mode, there is an extention to the '/' command which
2302 allows you to send the output to all the people you are talking to. You do
2303 with the '//' command. For example:-</P>
2309 </CODE></BLOCKQUOTE>
2311 <P>will send the hftable as you have it to all the people you are currently
2313 <H2><A NAME="ss11.120">11.120</A> <A HREF="usermanual_en.html#toc11.120">talk <call> [<text>]</A>
2316 <P><CODE><B>talk <call> [<text>]</B> Send a text message to another station</CODE></P>
2319 <H2><A NAME="ss11.121">11.121</A> <A HREF="usermanual_en.html#toc11.121">type <filearea>/<name></A>
2322 <P><CODE><B>type <filearea>/<name></B> Look at the contents of a file in one of the fileareas</CODE></P>
2324 <P>Type out the contents of a file in a filearea. So, for example, in
2325 filearea 'bulletins' you want to look at file 'arld051' you would
2329 TYPE bulletins/arld051
2331 </CODE></BLOCKQUOTE>
2333 <P>See also SHOW/FILES to see what fileareas are available and a
2334 list of content.</P>
2335 <H2><A NAME="ss11.122">11.122</A> <A HREF="usermanual_en.html#toc11.122">unset/announce</A>
2338 <P><CODE><B>unset/announce</B> Stop announce messages coming out on your terminal</CODE></P>
2341 <H2><A NAME="ss11.123">11.123</A> <A HREF="usermanual_en.html#toc11.123">unset/anntalk</A>
2344 <P><CODE><B>unset/anntalk</B> Stop talk like announce messages on your terminal</CODE></P>
2346 <P>The announce system on legacy cluster nodes is used as a talk
2347 substitute because the network is so poorly connected. If you:</P>
2353 </CODE></BLOCKQUOTE>
2355 <P>you will suppress several of these announces, you may miss the odd
2356 useful one as well, but you would probably miss them anyway in the
2357 welter of useless ones.</P>
2363 </CODE></BLOCKQUOTE>
2365 <P>allows you to see them again. This is the default.</P>
2366 <H2><A NAME="ss11.124">11.124</A> <A HREF="usermanual_en.html#toc11.124">unset/beep</A>
2369 <P><CODE><B>unset/beep</B> Stop beeps for DX and other messages on your terminal</CODE></P>
2372 <H2><A NAME="ss11.125">11.125</A> <A HREF="usermanual_en.html#toc11.125">unset/dx</A>
2375 <P><CODE><B>unset/dx</B> Stop DX messages coming out on your terminal</CODE></P>
2378 <H2><A NAME="ss11.126">11.126</A> <A HREF="usermanual_en.html#toc11.126">unset/dxcq</A>
2381 <P><CODE><B>unset/dxcq</B> Stop CQ Zones on the end of DX announcements</CODE></P>
2383 <P>Display both the Spotter's and the Spotted's CQ Zone on the end
2384 of a DX announcement (there is just enough room). Some user programs
2385 cannot cope with this. The Spotter's CQ is on the RHS of the
2386 time, the Spotted's CQ is on the LHS.</P>
2387 <P>Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE</P>
2388 <P>Do a STAT/USER to see which flags you have set if you are confused. </P>
2389 <H2><A NAME="ss11.127">11.127</A> <A HREF="usermanual_en.html#toc11.127">unset/dxgrid</A>
2392 <P><CODE><B>unset/dxgrid</B> Stop QRA Grid Squares on the end of DX announcements</CODE></P>
2394 <P>A standard feature which is enabled in version 1.43 and above is
2395 that if the spotter's grid square is known it is output on the end
2396 of a DX announcement (there is just enough room). Some user programs
2397 cannot cope with this. You can use this command to reset (or set)
2399 <P>Conflicts with: SET/DXCQ, SET/DXITU</P>
2400 <P>Do a STAT/USER to see which flags you have set if you are confused. </P>
2401 <H2><A NAME="ss11.128">11.128</A> <A HREF="usermanual_en.html#toc11.128">unset/dxitu</A>
2404 <P><CODE><B>unset/dxitu</B> Stop ITU Zones on the end of DX announcements</CODE></P>
2406 <P>Display both the Spotter's and the Spotted's ITU Zone on the end
2407 of a DX announcement (there is just enough room). Some user programs
2408 cannot cope with this. The Spotter's ITU is on the RHS of the
2409 time, the Spotted's ITU is on the LHS.</P>
2410 <P>Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE</P>
2411 <P>Do a STAT/USER to see which flags you have set if you are confused. </P>
2412 <H2><A NAME="ss11.129">11.129</A> <A HREF="usermanual_en.html#toc11.129">unset/echo</A>
2415 <P><CODE><B>unset/echo</B> Stop the cluster echoing your input</CODE></P>
2417 <P>If you are connected via a telnet session, different implimentations
2418 of telnet handle echo differently depending on whether you are
2419 connected via port 23 or some other port. You can use this command
2420 to change the setting appropriately. </P>
2421 <P>The setting is stored in your user profile.</P>
2422 <P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.</P>
2423 <H2><A NAME="ss11.130">11.130</A> <A HREF="usermanual_en.html#toc11.130">unset/email</A>
2426 <P><CODE><B>unset/email</B> Stop personal msgs being forwarded by email</CODE></P>
2428 <P>If any personal messages come in for your callsign then you can use
2429 these commands to control whether they are forwarded onto your email
2430 address. To enable the forwarding do something like:-</P>
2434 SET/EMAIL mike.tubby@somewhere.com
2436 </CODE></BLOCKQUOTE>
2438 <P>You can have more than one email address (each one separated by a space).
2439 Emails are forwarded to all the email addresses you specify.</P>
2440 <P>You can disable forwarding by:-</P>
2446 </CODE></BLOCKQUOTE>
2449 <H2><A NAME="ss11.131">11.131</A> <A HREF="usermanual_en.html#toc11.131">unset/here</A>
2452 <P><CODE><B>unset/here</B> Tell the system you are absent from your terminal</CODE></P>
2455 <H2><A NAME="ss11.132">11.132</A> <A HREF="usermanual_en.html#toc11.132">unset/logininfo</A>
2458 <P><CODE><B>unset/logininfo</B> Inform when a station logs out locally</CODE></P>
2461 <H2><A NAME="ss11.133">11.133</A> <A HREF="usermanual_en.html#toc11.133">unset/privilege</A>
2464 <P><CODE><B>unset/privilege</B> Remove any privilege for this session</CODE></P>
2466 <P>You can use this command to 'protect' this session from unauthorised
2467 use. If you want to get your normal privilege back you will need to
2468 either logout and login again (if you are on a console) or use the
2470 <H2><A NAME="ss11.134">11.134</A> <A HREF="usermanual_en.html#toc11.134">unset/prompt</A>
2473 <P><CODE><B>unset/prompt</B> Set your prompt back to default</CODE></P>
2475 <P>This command will set your user prompt to exactly the string that you
2476 say. The point of this command to enable a user to interface to programs
2477 that are looking for a specific prompt (or else you just want a different
2484 </CODE></BLOCKQUOTE>
2486 <P>UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back to
2488 <H2><A NAME="ss11.135">11.135</A> <A HREF="usermanual_en.html#toc11.135">unset/talk</A>
2491 <P><CODE><B>unset/talk</B> Stop TALK messages coming out on your terminal</CODE></P>
2494 <H2><A NAME="ss11.136">11.136</A> <A HREF="usermanual_en.html#toc11.136">unset/usstate</A>
2497 <P><CODE><B>unset/usstate</B> Stop US State info on the end of DX announcements</CODE></P>
2499 <P>If the spotter's or spotted's US State is known it is output on the
2500 end of a DX announcement (there is just enough room). </P>
2501 <P>A spotter's state will appear on the RHS of the time (like
2502 SET/DXGRID) and the spotted's State will appear on the LHS of the
2503 time field. Any information found will override any locator
2504 information from SET/DXGRID.</P>
2505 <P>Some user programs cannot cope with this. You can use this command
2506 to reset (or set) this feature.</P>
2507 <P>Conflicts with: SET/DXCQ, SET/DXITU</P>
2508 <P>Do a STAT/USER to see which flags you have set if you are confused. </P>
2509 <H2><A NAME="ss11.137">11.137</A> <A HREF="usermanual_en.html#toc11.137">unset/wcy</A>
2512 <P><CODE><B>unset/wcy</B> Stop WCY messages coming out on your terminal</CODE></P>
2515 <H2><A NAME="ss11.138">11.138</A> <A HREF="usermanual_en.html#toc11.138">unset/wwv</A>
2518 <P><CODE><B>unset/wwv</B> Stop WWV messages coming out on your terminal</CODE></P>
2521 <H2><A NAME="ss11.139">11.139</A> <A HREF="usermanual_en.html#toc11.139">unset/wx</A>
2524 <P><CODE><B>unset/wx</B> Stop WX messages coming out on your terminal</CODE></P>
2527 <H2><A NAME="ss11.140">11.140</A> <A HREF="usermanual_en.html#toc11.140">who</A>
2530 <P><CODE><B>who</B> Show who is physically connected</CODE></P>
2532 <P>This is a quick listing that shows which callsigns are connected and
2533 what sort of connection they have</P>
2534 <H2><A NAME="ss11.141">11.141</A> <A HREF="usermanual_en.html#toc11.141">wx <text></A>
2537 <P><CODE><B>wx <text></B> Send a weather message to local users</CODE></P>
2540 <H2><A NAME="ss11.142">11.142</A> <A HREF="usermanual_en.html#toc11.142">wx full <text></A>
2543 <P><CODE><B>wx full <text></B> Send a weather message to all cluster users</CODE></P>
2548 <A HREF="usermanual_en-10.html">Previous</A>
2549 <A HREF="usermanual_en.html#toc11">Contents</A>
projects / spider.git / blob