1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
4 <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
5 <TITLE>The DXSpider User Manual v1.51: The DXSpider Command Reference</TITLE>
6 <LINK HREF="usermanual_en-11.html" REL=previous>
7 <LINK HREF="usermanual_en.html#toc12" REL=contents>
8 <link rel=stylesheet href="style.css" type="text/css" title="default stylesheet">
12 <A HREF="usermanual_en-11.html">Previous</A>
13 <A HREF="usermanual_en.html#toc12">Contents</A>
15 <H2><A NAME="s12">12.</A> <A HREF="usermanual_en.html#toc12">The DXSpider Command Reference</A></H2>
17 <H2><A NAME="ss12.1">12.1</A> <A HREF="usermanual_en.html#toc12.1">accept</A>
20 <P><CODE><B>accept</B> Set a filter to accept something</CODE></P>
22 <P>Create a filter to accept something</P>
23 <P>There are 2 types of filter, accept and reject. See HELP FILTERING for more
25 <H2><A NAME="ss12.2">12.2</A> <A HREF="usermanual_en.html#toc12.2">accept/announce [0-9] <pattern></A>
28 <P><CODE><B>accept/announce [0-9] <pattern></B> Set an 'accept' filter line for announce</CODE></P>
30 <P>Create an 'accept this announce' line for a filter. </P>
31 <P>An accept filter line means that if the announce matches this filter it is
32 passed onto the user. See HELP FILTERING for more info. Please read this
33 to understand how filters work - it will save a lot of grief later on.</P>
34 <P>You can use any of the following things in this line:-</P>
38 info <string> eg: iota or qsl
39 by <prefixes> eg: G,M,2
40 origin <prefixes>
41 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
42 origin_itu <prefixes or numbers> or: G,GM,GW
43 origin_zone <prefixes or numbers>
44 origin_state <states> eg: VA,NH,RI,NH
45 by_dxcc <prefixes or numbers>
46 by_itu <prefixes or numbers>
47 by_zone <prefixes or numbers>
48 by_state <states>
49 channel <prefixes>
50 wx 1 filter WX announces
51 dest <prefixes> eg: 6MUK,WDX (distros)
55 <P>some examples:-</P>
60 acc/ann 2 by_zone 14,15,16
61 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
72 <P>for american states</P>
76 acc/ann by_state va,nh,ri,nh
80 <P>You can use the tag 'all' to accept everything eg:</P>
88 <P>but this probably for advanced users...</P>
89 <H2><A NAME="ss12.3">12.3</A> <A HREF="usermanual_en.html#toc12.3">accept/spots [0-9] <pattern></A>
92 <P><CODE><B>accept/spots [0-9] <pattern></B> Set an 'accept' filter line for spots</CODE></P>
94 <P>Create an 'accept this spot' line for a filter. </P>
95 <P>An accept filter line means that if the spot matches this filter it is
96 passed onto the user. See HELP FILTERING for more info. Please read this
97 to understand how filters work - it will save a lot of grief later on.</P>
98 <P>You can use any of the following things in this line:-</P>
102 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
103 on <range> same as 'freq'
104 call <prefixes> eg: G,PA,HB9
105 info <string> eg: iota or qsl
107 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
108 call_itu <prefixes or numbers> or: G,GM,GW
109 call_zone <prefixes or numbers>
110 call_state <states> eg: VA,NH,RI,ME
111 by_dxcc <prefixes or numbers>
112 by_itu <prefixes or numbers>
113 by_zone <prefixes or numbers>
114 by_state <states> eg: VA,NH,RI,ME
115 origin <prefixes>
116 channel <prefixes>
120 <P>'call' means the callsign that has spotted 'by' whoever.</P>
121 <P>For frequencies, you can use any of the band names defined in
122 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
123 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
124 this is more efficient than saying simply: freq HF (but don't get
125 too hung up about that)</P>
126 <P>some examples:-</P>
131 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
135 <P>You can use the tag 'all' to accept everything, eg:</P>
143 <P>for US states </P>
147 acc/spots by_state VA,NH,RI,MA,ME
151 <P>but this probably for advanced users...</P>
152 <H2><A NAME="ss12.4">12.4</A> <A HREF="usermanual_en.html#toc12.4">accept/wcy [0-9] <pattern></A>
155 <P><CODE><B>accept/wcy [0-9] <pattern></B> set an 'accept' WCY filter</CODE></P>
157 <P>It is unlikely that you will want to do this, but if you do then you can
158 filter on the following fields:-</P>
162 by <prefixes> eg: G,M,2
163 origin <prefixes>
164 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
165 origin_itu <prefixes or numbers> or: G,GM,GW
166 origin_zone <prefixes or numbers>
167 by_dxcc <prefixes or numbers>
168 by_itu <prefixes or numbers>
169 by_zone <prefixes or numbers>
170 channel <prefixes>
174 <P>There are no examples because WCY Broadcasts only come from one place and
175 you either want them or not (see UNSET/WCY if you don't want them).</P>
176 <P>This command is really provided for future use.</P>
177 <P>See HELP FILTER for information.</P>
178 <H2><A NAME="ss12.5">12.5</A> <A HREF="usermanual_en.html#toc12.5">accept/wwv [0-9] <pattern></A>
181 <P><CODE><B>accept/wwv [0-9] <pattern></B> set an 'accept' WWV filter</CODE></P>
183 <P>It is unlikely that you will want to do this, but if you do then you can
184 filter on the following fields:-</P>
188 by <prefixes> eg: G,M,2
189 origin <prefixes>
190 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
191 origin_itu <prefixes or numbers> or: G,GM,GW
192 origin_zone <prefixes or numbers>
193 by_dxcc <prefixes or numbers>
194 by_itu <prefixes or numbers>
195 by_zone <prefixes or numbers>
196 channel <prefixes>
208 <P>is probably the only useful thing to do (which will only show WWV broadcasts
209 by stations in the US).</P>
210 <P>See HELP FILTER for information.</P>
211 <H2><A NAME="ss12.6">12.6</A> <A HREF="usermanual_en.html#toc12.6">announce <text></A>
214 <P><CODE><B>announce <text></B> Send an announcement to LOCAL users only</CODE></P>
216 <P><text> is the text of the announcement you wish to broadcast </P>
217 <H2><A NAME="ss12.7">12.7</A> <A HREF="usermanual_en.html#toc12.7">announce full <text></A>
220 <P><CODE><B>announce full <text></B> Send an announcement cluster wide</CODE></P>
222 <P>This will send your announcement cluster wide</P>
223 <H2><A NAME="ss12.8">12.8</A> <A HREF="usermanual_en.html#toc12.8">apropos <string></A>
226 <P><CODE><B>apropos <string></B> Search help database for <string></CODE></P>
228 <P>Search the help database for <string> (it isn't case sensitive), and print
229 the names of all the commands that may be relevant.</P>
230 <H2><A NAME="ss12.9">12.9</A> <A HREF="usermanual_en.html#toc12.9">blank [<string>] [<nn>]</A>
233 <P><CODE><B>blank [<string>] [<nn>]</B> Print nn (default 1) blank lines (or strings)</CODE></P>
235 <P>In its basic form this command prints one or more blank lines. However if
236 you pass it a string it will replicate the string for the width of the
237 screen (default 80) and then print that one or more times, so:</P>
245 <P>prints two blank lines</P>
253 <P>prints a row of - characters once.</P>
261 <P>prints 'abcabcabcabcabcabc....'</P>
262 <P>This is really only of any use in a script file and you can print a maximum
264 <H2><A NAME="ss12.10">12.10</A> <A HREF="usermanual_en.html#toc12.10">bye</A>
267 <P><CODE><B>bye</B> Exit from the cluster</CODE></P>
269 <P>This will disconnect you from the cluster</P>
270 <H2><A NAME="ss12.11">12.11</A> <A HREF="usermanual_en.html#toc12.11">chat <group> <text></A>
273 <P><CODE><B>chat <group> <text></B> Chat or Conference to a group</CODE></P>
275 <P>It is now possible to JOIN a group and have network wide conferencing to that
276 group. DXSpider does not (and probably will not) implement the AK1A
277 conference mode as this seems very limiting, is hardly used and doesn't seem
278 to work too well anyway.</P>
279 <P>This system uses the existing ANN system and is compatible with both other
280 DXSpider nodes and AK1A clusters (they use ANN/<group>). </P>
281 <P>You can be a member of as many "groups" as you want. To join a group type:-</P>
285 JOIN FOC (where FOC is the group name)
289 <P>To leave a group type:-</P>
297 <P>You can see which groups you are in by typing:-</P>
305 <P>and you can see whether your mate is in the group, if he connects to the
306 same node as you, by typing:-</P>
314 <P>To send a message to a group type:-</P>
318 CHAT FOC hello everyone
326 CH #9000 hello I am back
330 <P>See also JOIN, LEAVE, SHOW/CHAT</P>
331 <H2><A NAME="ss12.12">12.12</A> <A HREF="usermanual_en.html#toc12.12">clear/announce [1|all]</A>
334 <P><CODE><B>clear/announce [1|all]</B> Clear a announce filter line</CODE></P>
336 <P>This command allows you to clear (remove) a line in a annouce filter or to
337 remove the whole filter.</P>
338 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
339 <H2><A NAME="ss12.13">12.13</A> <A HREF="usermanual_en.html#toc12.13">clear/route [1|all]</A>
342 <P><CODE><B>clear/route [1|all]</B> Clear a route filter line</CODE></P>
344 <P>This command allows you to clear (remove) a line in a route filter or to
345 remove the whole filter.</P>
346 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
347 <H2><A NAME="ss12.14">12.14</A> <A HREF="usermanual_en.html#toc12.14">clear/spots [0-9|all]</A>
350 <P><CODE><B>clear/spots [0-9|all]</B> Clear a spot filter line</CODE></P>
352 <P>This command allows you to clear (remove) a line in a spot filter or to
353 remove the whole filter.</P>
354 <P>If you have a filter:-</P>
359 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
371 <P>you will be left with:-</P>
375 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
387 <P>the filter will be completely removed.</P>
388 <H2><A NAME="ss12.15">12.15</A> <A HREF="usermanual_en.html#toc12.15">clear/wcy [1|all]</A>
391 <P><CODE><B>clear/wcy [1|all]</B> Clear a WCY filter line</CODE></P>
393 <P>This command allows you to clear (remove) a line in a WCY filter or to
394 remove the whole filter.</P>
395 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
396 <H2><A NAME="ss12.16">12.16</A> <A HREF="usermanual_en.html#toc12.16">clear/wwv [1|all]</A>
399 <P><CODE><B>clear/wwv [1|all]</B> Clear a WWV filter line</CODE></P>
401 <P>This command allows you to clear (remove) a line in a WWV filter or to
402 remove the whole filter.</P>
403 <P>see CLEAR/SPOTS for a more detailed explanation.</P>
404 <H2><A NAME="ss12.17">12.17</A> <A HREF="usermanual_en.html#toc12.17">dbavail</A>
407 <P><CODE><B>dbavail</B> Show a list of all the Databases in the system</CODE></P>
409 <P>Title says it all really, this command lists all the databases defined
410 in the system. It is also aliased to SHOW/COMMAND.</P>
411 <H2><A NAME="ss12.18">12.18</A> <A HREF="usermanual_en.html#toc12.18">dbshow <dbname> <key></A>
414 <P><CODE><B>dbshow <dbname> <key></B> Display an entry, if it exists, in a database</CODE></P>
416 <P>This is the generic user interface to the database to the database system.
417 It is expected that the sysop will add an entry to the local Aliases file
418 so that users can use the more familiar AK1A style of enquiry such as:</P>
426 <P>but if he hasn't and the database really does exist (use DBAVAIL or
427 SHOW/COMMAND to find out) you can do the same thing with:</P>
436 <H2><A NAME="ss12.19">12.19</A> <A HREF="usermanual_en.html#toc12.19">directory</A>
439 <P><CODE><B>directory</B> List messages </CODE></P>
442 <H2><A NAME="ss12.20">12.20</A> <A HREF="usermanual_en.html#toc12.20">directory <from>-<to></A>
445 <P><CODE><B>directory <from>-<to></B> List messages <from> message <to> message </CODE></P>
447 <P>List the messages in the messages directory.</P>
448 <P>If there is a 'p' one space after the message number then it is a
449 personal message. If there is a '-' between the message number and the
450 'p' then this indicates that the message has been read.</P>
451 <P>You can use shell escape characters such as '*' and '?' in the <call>
453 <P>You can combine some of the various directory commands together eg:-</P>
464 DIR SUBJECT IOTA 200-250
468 <P>You can abbreviate all the commands to one letter and use ak1a syntax:-</P>
478 <H2><A NAME="ss12.21">12.21</A> <A HREF="usermanual_en.html#toc12.21">directory <nn></A>
481 <P><CODE><B>directory <nn></B> List last <nn> messages</CODE></P>
484 <H2><A NAME="ss12.22">12.22</A> <A HREF="usermanual_en.html#toc12.22">directory all</A>
487 <P><CODE><B>directory all</B> List all messages</CODE></P>
490 <H2><A NAME="ss12.23">12.23</A> <A HREF="usermanual_en.html#toc12.23">directory from <call></A>
493 <P><CODE><B>directory from <call></B> List all messages from <call></CODE></P>
496 <H2><A NAME="ss12.24">12.24</A> <A HREF="usermanual_en.html#toc12.24">directory new</A>
499 <P><CODE><B>directory new</B> List all new messages</CODE></P>
502 <H2><A NAME="ss12.25">12.25</A> <A HREF="usermanual_en.html#toc12.25">directory own</A>
505 <P><CODE><B>directory own</B> List your own messages</CODE></P>
508 <H2><A NAME="ss12.26">12.26</A> <A HREF="usermanual_en.html#toc12.26">directory subject <string></A>
511 <P><CODE><B>directory subject <string></B> List all messages with <string> in subject</CODE></P>
514 <H2><A NAME="ss12.27">12.27</A> <A HREF="usermanual_en.html#toc12.27">directory to <call></A>
517 <P><CODE><B>directory to <call></B> List all messages to <call></CODE></P>
520 <H2><A NAME="ss12.28">12.28</A> <A HREF="usermanual_en.html#toc12.28">dx [by <call>] <freq> <call> <remarks></A>
523 <P><CODE><B>dx [by <call>] <freq> <call> <remarks></B> Send a DX spot</CODE></P>
525 <P>This is how you send a DX Spot to other users. You can, in fact, now
526 enter the <freq> and the <call> either way round. </P>
536 <P>will all give the same result. You can add some remarks to the end
537 of the command and they will be added to the spot.</P>
541 DX FR0G 144600 this is a test
545 <P>You can credit someone else by saying:-</P>
549 DX by G1TLH FR0G 144.600 he isn't on the cluster
553 <P>The <freq> is compared against the available bands set up in the
554 cluster. See SHOW/BANDS for more information.</P>
555 <H2><A NAME="ss12.29">12.29</A> <A HREF="usermanual_en.html#toc12.29">echo <line></A>
558 <P><CODE><B>echo <line></B> Echo the line to the output</CODE></P>
560 <P>This command is useful in scripts and so forth for printing the
561 line that you give to the command to the output. You can use this
562 in user_default scripts and the SAVE command for titling and so forth</P>
563 <P>The script will interpret certain standard "escape" sequences as follows:-</P>
567 \t - becomes a TAB character (0x09 in ascii)
568 \a - becomes a BEEP character (0x07 in ascii)
569 \n - prints a new line
573 <P>So the following example:-</P>
577 echo GB7DJK is a dxcluster
585 GB7DJK is a dxcluster
589 <P>on the output. You don't need a \n on the end of the line you want to send.</P>
590 <P>A more complex example:-</P>
594 echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
608 <P>on the output.</P>
610 <H2><A NAME="ss12.30">12.30</A> <A HREF="usermanual_en.html#toc12.30">filtering...</A>
613 <P><CODE><B>filtering...</B> Filtering things in DXSpider</CODE></P>
615 <P>There are a number of things you can filter in the DXSpider system. They
616 all use the same general mechanism.</P>
617 <P>In general terms you can create a 'reject' or an 'accept' filter which
618 can have up to 10 lines in it. You do this using, for example:-</P>
627 <P>where ..... are the specific commands for that type of filter. There
628 are filters for spots, wwv, announce, wcy and (for sysops)
629 connects. See each different accept or reject command reference for
631 <P>There is also a command to clear out one or more lines in a filter and
632 one to show you what you have set. They are:-</P>
649 <P>There is clear/xxxx command for each type of filter.</P>
650 <P>For now we are going to use spots for the examples, but you can apply
651 the principles to all types of filter.</P>
652 <P>There are two main types of filter 'accept' or 'reject'; which you use
653 depends entirely on how you look at the world and what is least
654 writing to achieve what you want. Each filter has 10 lines (of any
655 length) which are tried in order. If a line matches then the action
656 you have specified is taken (ie reject means ignore it and accept
658 <P>The important thing to remember is that if you specify a 'reject'
659 filter (all the lines in it say 'reject/spots' (for instance)) then if
660 a spot comes in that doesn't match any of the lines then you will get
661 it BUT if you specify an 'accept' filter then any spots that don't
662 match are dumped. For example if I have a one line accept filter:-</P>
666 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
670 <P>then automatically you will ONLY get VHF spots from or to CQ zones 14
671 15 and 16. If you set a reject filter like:</P>
675 reject/spots on hf/cw
679 <P>Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
680 and will work it even on CW then you could say:-</P>
684 reject/spots on hf/cw and not info iota
688 <P>But in that case you might only be interested in iota and say:-</P>
692 accept/spots not on hf/cw or info iota
696 <P>which is exactly the same. You should choose one or the other until
697 you are confortable with the way it works. Yes, you can mix them
698 (actually you can have an accept AND a reject on the same line) but
699 don't try this at home until you can analyse the results that you get
700 without ringing up the sysop for help.</P>
701 <P>Another useful addition now is filtering by US state</P>
705 accept/spots by_state VA,NH,RI,ME
709 <P>You can arrange your filter lines into logical units, either for your
710 own understanding or simply convenience. I have one set frequently:-</P>
714 reject/spots 1 on hf/cw
715 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
719 <P>What this does is to ignore all HF CW spots (being a class B I can't
720 read any CW and couldn't possibly be interested in HF :-) and also
721 rejects any spots on VHF which don't either originate or spot someone
723 <P>This is an exmaple where you would use the line number (1 and 2 in
724 this case), if you leave the digit out, the system assumes '1'. Digits
725 '0'-'9' are available.</P>
726 <P>You can leave the word 'and' out if you want, it is implied. You can
727 use any number of brackets to make the 'expression' as you want
728 it. There are things called precedence rules working here which mean
729 that you will NEED brackets in a situation like line 2 because,
730 without it, will assume:-</P>
734 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
738 <P>annoying, but that is the way it is. If you use OR - use
739 brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
740 just 'and by_zone'.</P>
741 <P>If you want to alter your filter you can just redefine one or more
742 lines of it or clear out one line. For example:-</P>
746 reject/spots 1 on hf/ssb
758 <P>To remove the filter in its entirty:-</P>
766 <P>There are similar CLEAR commands for the other filters:-</P>
776 <P>ADVANCED USERS:-</P>
777 <P>Once you are happy with the results you get, you may like to experiment. </P>
778 <P>my example that filters hf/cw spots and accepts vhf/uhf spots from EU
779 can be written with a mixed filter, eg:</P>
785 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
789 <P>each filter slot actually has a 'reject' slot and an 'accept'
790 slot. The reject slot is executed BEFORE the accept slot.</P>
791 <P>It was mentioned earlier that after a reject test that doesn't match,
792 the default for following tests is 'accept', the reverse is true for
793 'accept'. In the example what happens is that the reject is executed
794 first, any non hf/cw spot is passed to the accept line, which lets
795 thru everything else on HF.</P>
796 <P>The next filter line lets through just VHF/UHF spots from EU.</P>
797 <H2><A NAME="ss12.31">12.31</A> <A HREF="usermanual_en.html#toc12.31">help</A>
800 <P><CODE><B>help</B> The HELP Command</CODE></P>
802 <P>HELP is available for a number of commands. The syntax is:-</P>
810 <P>Where <cmd> is the name of the command you want help on.</P>
811 <P>All commands can be abbreviated, so SHOW/DX can be abbreviated
812 to SH/DX, ANNOUNCE can be shortened to AN and so on.</P>
813 <P>Look at the APROPOS <string> command which will search the help database
814 for the <string> you specify and give you a list of likely commands
815 to look at with HELP.</P>
816 <H2><A NAME="ss12.32">12.32</A> <A HREF="usermanual_en.html#toc12.32">join <group></A>
819 <P><CODE><B>join <group></B> Join a chat or conference group</CODE></P>
821 <P>JOIN allows you to join a network wide conference group. To join a
822 group (called FOC in this case) type:-</P>
830 <P>See also CHAT, LEAVE, SHOW/CHAT</P>
831 <H2><A NAME="ss12.33">12.33</A> <A HREF="usermanual_en.html#toc12.33">kill <from msgno>-<to msgno></A>
834 <P><CODE><B>kill <from msgno>-<to msgno></B> Delete a range of messages</CODE></P>
837 <H2><A NAME="ss12.34">12.34</A> <A HREF="usermanual_en.html#toc12.34">kill <msgno> [<msgno..]</A>
840 <P><CODE><B>kill <msgno> [<msgno..]</B> Delete a message from the local system</CODE></P>
843 <H2><A NAME="ss12.35">12.35</A> <A HREF="usermanual_en.html#toc12.35">kill <msgno> [<msgno> ...]</A>
846 <P><CODE><B>kill <msgno> [<msgno> ...]</B> Remove or erase a message from the system</CODE></P>
848 <P>You can get rid of any message to or originating from your callsign using
849 this command. You can remove more than one message at a time.</P>
850 <H2><A NAME="ss12.36">12.36</A> <A HREF="usermanual_en.html#toc12.36">kill from <regex></A>
853 <P><CODE><B>kill from <regex></B> Delete messages FROM a callsign or pattern</CODE></P>
856 <H2><A NAME="ss12.37">12.37</A> <A HREF="usermanual_en.html#toc12.37">kill to <regex></A>
859 <P><CODE><B>kill to <regex></B> Delete messages TO a callsign or pattern</CODE></P>
862 <H2><A NAME="ss12.38">12.38</A> <A HREF="usermanual_en.html#toc12.38">leave <group></A>
865 <P><CODE><B>leave <group></B> Leave a chat or conference group</CODE></P>
867 <P>LEAVE allows you to leave a network wide conference group. To leave a
868 group (called FOC in this case) type:-</P>
876 <P>See also CHAT, JOIN, SHOW/CHAT</P>
877 <H2><A NAME="ss12.39">12.39</A> <A HREF="usermanual_en.html#toc12.39">links</A>
880 <P><CODE><B>links</B> Show which nodes is physically connected</CODE></P>
882 <P>This is a quick listing that shows which links are connected and
883 some information about them. See WHO for a list of all connections.</P>
884 <H2><A NAME="ss12.40">12.40</A> <A HREF="usermanual_en.html#toc12.40">read</A>
887 <P><CODE><B>read</B> Read the next unread personal message addressed to you</CODE></P>
890 <H2><A NAME="ss12.41">12.41</A> <A HREF="usermanual_en.html#toc12.41">read <msgno></A>
893 <P><CODE><B>read <msgno></B> Read the specified message</CODE></P>
895 <P>You can read any messages that are sent as 'non-personal' and also any
896 message either sent by or sent to your callsign.</P>
897 <H2><A NAME="ss12.42">12.42</A> <A HREF="usermanual_en.html#toc12.42">reject</A>
900 <P><CODE><B>reject</B> Set a filter to reject something</CODE></P>
902 <P>Create a filter to reject something</P>
903 <P>There are 2 types of filter, accept and reject. See HELP FILTERING for more
905 <H2><A NAME="ss12.43">12.43</A> <A HREF="usermanual_en.html#toc12.43">reject/announce [0-9] <pattern></A>
908 <P><CODE><B>reject/announce [0-9] <pattern></B> Set a 'reject' filter line for announce</CODE></P>
910 <P>Create an 'reject this announce' line for a filter. </P>
911 <P>A reject filter line means that if the announce matches this filter it is
912 passed onto the user. See HELP FILTERING for more info. Please read this
913 to understand how filters work - it will save a lot of grief later on.</P>
914 <P>You can use any of the following things in this line:-</P>
918 info <string> eg: iota or qsl
919 by <prefixes> eg: G,M,2
920 origin <prefixes>
921 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
922 origin_itu <prefixes or numbers> or: G,GM,GW
923 origin_zone <prefixes or numbers>
924 origin_state <states> eg: VA,NH,RI,ME
925 by_dxcc <prefixes or numbers>
926 by_itu <prefixes or numbers>
927 by_zone <prefixes or numbers>
928 by_state <states> eg: VA,NH,RI,ME
929 channel <prefixes>
930 wx 1 filter WX announces
931 dest <prefixes> eg: 6MUK,WDX (distros)
935 <P>some examples:-</P>
939 rej/ann by_zone 14,15,16 and not by G,M,2
943 <P>You can use the tag 'all' to reject everything eg:</P>
951 <P>but this probably for advanced users...</P>
952 <H2><A NAME="ss12.44">12.44</A> <A HREF="usermanual_en.html#toc12.44">reject/spots [0-9] <pattern></A>
955 <P><CODE><B>reject/spots [0-9] <pattern></B> Set a 'reject' filter line for spots</CODE></P>
957 <P>Create a 'reject this spot' line for a filter. </P>
958 <P>A reject filter line means that if the spot matches this filter it is
959 dumped (not passed on). See HELP FILTERING for more info. Please read this
960 to understand how filters work - it will save a lot of grief later on.</P>
961 <P>You can use any of the following things in this line:-</P>
965 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
966 on <range> same as 'freq'
967 call <prefixes> eg: G,PA,HB9
968 info <string> eg: iota or qsl
970 call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
971 call_itu <prefixes or numbers> or: G,GM,GW
972 call_zone <prefixes or numbers>
973 call_state <states> eg: VA,NH,RI,ME
974 by_dxcc <prefixes or numbers>
975 by_itu <prefixes or numbers>
976 by_zone <prefixes or numbers>
977 by_state <states> eg: VA,NH,RI,ME
978 origin <prefixes>
979 channel <prefixes>
983 <P>'call' means the callsign that has spotted 'by' whoever.</P>
984 <P>For frequencies, you can use any of the band names defined in
985 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
986 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
987 this is more efficient than saying simply: on HF (but don't get
988 too hung up about that)</P>
989 <P>some examples:-</P>
994 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
998 <P>You can use the tag 'all' to reject everything eg:</P>
1004 </CODE></BLOCKQUOTE>
1006 <P>but this probably for advanced users...</P>
1007 <H2><A NAME="ss12.45">12.45</A> <A HREF="usermanual_en.html#toc12.45">reject/wcy [0-9] <pattern></A>
1010 <P><CODE><B>reject/wcy [0-9] <pattern></B> set a 'reject' WCY filter</CODE></P>
1012 <P>It is unlikely that you will want to do this, but if you do then you can
1013 filter on the following fields:-</P>
1017 by <prefixes> eg: G,M,2
1018 origin <prefixes>
1019 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1020 origin_itu <prefixes or numbers> or: G,GM,GW
1021 origin_zone <prefixes or numbers>
1022 by_dxcc <prefixes or numbers>
1023 by_itu <prefixes or numbers>
1024 by_zone <prefixes or numbers>
1025 channel <prefixes>
1027 </CODE></BLOCKQUOTE>
1029 <P>There are no examples because WCY Broadcasts only come from one place and
1030 you either want them or not (see UNSET/WCY if you don't want them).</P>
1031 <P>This command is really provided for future use.</P>
1032 <P>See HELP FILTER for information.</P>
1033 <H2><A NAME="ss12.46">12.46</A> <A HREF="usermanual_en.html#toc12.46">reject/wwv [0-9] <pattern></A>
1036 <P><CODE><B>reject/wwv [0-9] <pattern></B> set a 'reject' WWV filter</CODE></P>
1038 <P>It is unlikely that you will want to do this, but if you do then you can
1039 filter on the following fields:-</P>
1043 by <prefixes> eg: G,M,2
1044 origin <prefixes>
1045 origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
1046 origin_itu <prefixes or numbers> or: G,GM,GW
1047 origin_zone <prefixes or numbers>
1048 by_dxcc <prefixes or numbers>
1049 by_itu <prefixes or numbers>
1050 by_zone <prefixes or numbers>
1051 channel <prefixes>
1053 </CODE></BLOCKQUOTE>
1059 reject/wwv by_zone 14,15,16
1061 </CODE></BLOCKQUOTE>
1063 <P>is probably the only useful thing to do (which will only show WWV broadcasts
1064 by stations in the US).</P>
1065 <P>See HELP FILTER for information.</P>
1066 <H2><A NAME="ss12.47">12.47</A> <A HREF="usermanual_en.html#toc12.47">reply</A>
1069 <P><CODE><B>reply</B> Reply (privately) to the last message that you have read</CODE></P>
1072 <H2><A NAME="ss12.48">12.48</A> <A HREF="usermanual_en.html#toc12.48">reply <msgno></A>
1075 <P><CODE><B>reply <msgno></B> Reply (privately) to the specified message</CODE></P>
1078 <H2><A NAME="ss12.49">12.49</A> <A HREF="usermanual_en.html#toc12.49">reply b <msgno></A>
1081 <P><CODE><B>reply b <msgno></B> Reply as a Bulletin to the specified message</CODE></P>
1084 <H2><A NAME="ss12.50">12.50</A> <A HREF="usermanual_en.html#toc12.50">reply noprivate <msgno></A>
1087 <P><CODE><B>reply noprivate <msgno></B> Reply as a Bulletin to the specified message</CODE></P>
1090 <H2><A NAME="ss12.51">12.51</A> <A HREF="usermanual_en.html#toc12.51">reply rr <msgno></A>
1093 <P><CODE><B>reply rr <msgno></B> Reply to the specified message with read receipt</CODE></P>
1095 <P>You can reply to a message and the subject will automatically have
1096 "Re:" inserted in front of it, if it isn't already present.</P>
1097 <P>You can also use all the extra qualifiers such as RR, PRIVATE,
1098 NOPRIVATE, B that you can use with the SEND command (see SEND
1099 for further details)</P>
1100 <H2><A NAME="ss12.52">12.52</A> <A HREF="usermanual_en.html#toc12.52">send <call> [<call> ...]</A>
1103 <P><CODE><B>send <call> [<call> ...]</B> Send a message to one or more callsigns</CODE></P>
1106 <H2><A NAME="ss12.53">12.53</A> <A HREF="usermanual_en.html#toc12.53">send copy <msgno> <call></A>
1109 <P><CODE><B>send copy <msgno> <call></B> Send a copy of a message to someone</CODE></P>
1112 <H2><A NAME="ss12.54">12.54</A> <A HREF="usermanual_en.html#toc12.54">send noprivate <call></A>
1115 <P><CODE><B>send noprivate <call></B> Send a message to all stations</CODE></P>
1117 <P>All the SEND commands will create a message which will be sent either to
1118 an individual callsign or to one of the 'bulletin' addresses. </P>
1119 <P>SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
1120 it will mark the message as personal and send it to the cluster node that
1121 that callsign is connected to. If the <call> you have specified is in fact
1122 a known bulletin category on your node (eg: ALL) then the message should
1123 automatically become a bulletin.</P>
1124 <P>You can have more than one callsign in all of the SEND commands.</P>
1125 <P>You can have multiple qualifiers so that you can have for example:-</P>
1129 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1131 </CODE></BLOCKQUOTE>
1133 <P>which should send a copy of message 123 to G1TLH and G0RDI and you will
1134 receive a read receipt when they have read the message.</P>
1135 <P>SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
1136 SP is an alias for SEND PRIVATE</P>
1137 <P>The system will ask you for a subject. Conventionally this should be
1138 no longer than 29 characters for compatibility. Most modern cluster
1139 software should accept more.</P>
1140 <P>You will now be prompted to start entering your text. </P>
1141 <P>You finish the message by entering '/EX' on a new line. For instance:</P>
1150 </CODE></BLOCKQUOTE>
1152 <P>If you have started a message and you don't want to keep it then you
1153 can abandon the message with '/ABORT' on a new line, like:-</P>
1159 oh I just can't be bothered with this
1162 </CODE></BLOCKQUOTE>
1164 <P>If you abort the message it will NOT be sent.</P>
1165 <P>When you are entering the text of your message, most normal output (such
1166 as DX announcements and so on are suppressed and stored for latter display
1167 (upto 20 such lines are stored, as new ones come along, so the oldest
1168 lines are dropped).</P>
1169 <P>Also, you can enter normal commands commands (and get the output
1170 immediately) whilst in the middle of a message. You do this by typing
1171 the command preceeded by a '/' character on a new line, so:-</P>
1175 /dx g1tlh 144010 strong signal
1177 </CODE></BLOCKQUOTE>
1179 <P>Will issue a dx annoucement to the rest of the cluster. </P>
1180 <P>Also, you can add the output of a command to your message by preceeding
1181 the command with '//', thus :-</P>
1187 </CODE></BLOCKQUOTE>
1189 <P>This will show YOU the output from SH/VHFTABLE and also store it in the
1191 <P>You can carry on with the message until you are ready to send it. </P>
1192 <H2><A NAME="ss12.55">12.55</A> <A HREF="usermanual_en.html#toc12.55">send private <call></A>
1195 <P><CODE><B>send private <call></B> Send a personal message</CODE></P>
1198 <H2><A NAME="ss12.56">12.56</A> <A HREF="usermanual_en.html#toc12.56">send rr <call></A>
1201 <P><CODE><B>send rr <call></B> Send a message and ask for a read receipt</CODE></P>
1204 <H2><A NAME="ss12.57">12.57</A> <A HREF="usermanual_en.html#toc12.57">set/address <your address></A>
1207 <P><CODE><B>set/address <your address></B> Record your postal address</CODE></P>
1210 <H2><A NAME="ss12.58">12.58</A> <A HREF="usermanual_en.html#toc12.58">set/announce</A>
1213 <P><CODE><B>set/announce</B> Allow announce messages to come out on your terminal</CODE></P>
1216 <H2><A NAME="ss12.59">12.59</A> <A HREF="usermanual_en.html#toc12.59">set/anntalk</A>
1219 <P><CODE><B>set/anntalk</B> Allow talk like announce messages on your terminal</CODE></P>
1222 <H2><A NAME="ss12.60">12.60</A> <A HREF="usermanual_en.html#toc12.60">set/beep</A>
1225 <P><CODE><B>set/beep</B> Add a beep to DX and other messages on your terminal</CODE></P>
1228 <H2><A NAME="ss12.61">12.61</A> <A HREF="usermanual_en.html#toc12.61">set/dx</A>
1231 <P><CODE><B>set/dx</B> Allow DX messages to come out on your terminal</CODE></P>
1234 <H2><A NAME="ss12.62">12.62</A> <A HREF="usermanual_en.html#toc12.62">set/dxcq</A>
1237 <P><CODE><B>set/dxcq</B> Show CQ Zones on the end of DX announcements</CODE></P>
1240 <H2><A NAME="ss12.63">12.63</A> <A HREF="usermanual_en.html#toc12.63">set/dxgrid</A>
1243 <P><CODE><B>set/dxgrid</B> Allow QRA Grid Squares on the end of DX announcements</CODE></P>
1246 <H2><A NAME="ss12.64">12.64</A> <A HREF="usermanual_en.html#toc12.64">set/dxitu</A>
1249 <P><CODE><B>set/dxitu</B> Show ITU Zones on the end of DX announcements</CODE></P>
1252 <H2><A NAME="ss12.65">12.65</A> <A HREF="usermanual_en.html#toc12.65">set/echo</A>
1255 <P><CODE><B>set/echo</B> Make the cluster echo your input</CODE></P>
1258 <H2><A NAME="ss12.66">12.66</A> <A HREF="usermanual_en.html#toc12.66">set/email <email> ...</A>
1261 <P><CODE><B>set/email <email> ...</B> Set email address(es) and forward your personals</CODE></P>
1264 <H2><A NAME="ss12.67">12.67</A> <A HREF="usermanual_en.html#toc12.67">set/here</A>
1267 <P><CODE><B>set/here</B> Tell the system you are present at your terminal</CODE></P>
1270 <H2><A NAME="ss12.68">12.68</A> <A HREF="usermanual_en.html#toc12.68">set/homenode <node> </A>
1273 <P><CODE><B>set/homenode <node> </B> Set your normal cluster callsign</CODE></P>
1275 <P>Tell the cluster system where you normally connect to. Any Messages sent
1276 to you will normally find their way there should you not be connected.
1282 </CODE></BLOCKQUOTE>
1285 <H2><A NAME="ss12.69">12.69</A> <A HREF="usermanual_en.html#toc12.69">set/language <lang></A>
1288 <P><CODE><B>set/language <lang></B> Set the language you want to use</CODE></P>
1290 <P>You can select the language that you want the cluster to use. Currently
1291 the languages available are en (English), de (German), es (Spanish),
1292 Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).</P>
1293 <H2><A NAME="ss12.70">12.70</A> <A HREF="usermanual_en.html#toc12.70">set/location <lat & long></A>
1296 <P><CODE><B>set/location <lat & long></B> Set your latitude and longitude</CODE></P>
1299 <H2><A NAME="ss12.71">12.71</A> <A HREF="usermanual_en.html#toc12.71">set/logininfo</A>
1302 <P><CODE><B>set/logininfo</B> Inform when a station logs in/out locally</CODE></P>
1305 <H2><A NAME="ss12.72">12.72</A> <A HREF="usermanual_en.html#toc12.72">set/name <your name></A>
1308 <P><CODE><B>set/name <your name></B> Set your name</CODE></P>
1310 <P>Tell the system what your name is eg:-
1315 </CODE></BLOCKQUOTE>
1318 <H2><A NAME="ss12.73">12.73</A> <A HREF="usermanual_en.html#toc12.73">set/page <lines per page></A>
1321 <P><CODE><B>set/page <lines per page></B> Set the lines per page</CODE></P>
1323 <P>Tell the system how many lines you wish on a page when the number of line
1324 of output from a command is more than this. The default is 20. Setting it
1325 explicitly to 0 will disable paging.
1331 </CODE></BLOCKQUOTE>
1333 <P>The setting is stored in your user profile.</P>
1334 <H2><A NAME="ss12.74">12.74</A> <A HREF="usermanual_en.html#toc12.74">set/password</A>
1337 <P><CODE><B>set/password</B> Set your own password</CODE></P>
1339 <P>This command only works for a 'telnet' user (currently). It will
1340 only work if you have a password already set. This initial password
1341 can only be set by the sysop.</P>
1342 <P>When you execute this command it will ask you for your old password,
1343 then ask you to type in your new password twice (to make sure you
1344 get it right). You may or may not see the data echoed on the screen
1345 as you type, depending on the type of telnet client you have.</P>
1346 <H2><A NAME="ss12.75">12.75</A> <A HREF="usermanual_en.html#toc12.75">set/prompt <string></A>
1349 <P><CODE><B>set/prompt <string></B> Set your prompt to <string></CODE></P>
1352 <H2><A NAME="ss12.76">12.76</A> <A HREF="usermanual_en.html#toc12.76">set/qra <locator></A>
1355 <P><CODE><B>set/qra <locator></B> Set your QRA Grid locator</CODE></P>
1357 <P>Tell the system what your QRA (or Maidenhead) locator is. If you have not
1358 done a SET/LOCATION then your latitude and longitude will be set roughly
1359 correctly (assuming your locator is correct ;-). For example:-
1364 </CODE></BLOCKQUOTE>
1367 <H2><A NAME="ss12.77">12.77</A> <A HREF="usermanual_en.html#toc12.77">set/qth <your qth></A>
1370 <P><CODE><B>set/qth <your qth></B> Set your QTH</CODE></P>
1372 <P>Tell the system where you are. For example:-
1375 SET/QTH East Dereham, Norfolk
1377 </CODE></BLOCKQUOTE>
1380 <H2><A NAME="ss12.78">12.78</A> <A HREF="usermanual_en.html#toc12.78">set/startup</A>
1383 <P><CODE><B>set/startup</B> Create your own startup script</CODE></P>
1385 <P>Create a startup script of DXSpider commands which will be executed
1386 everytime that you login into this node. You can only input the whole
1387 script afresh, it is not possible to 'edit' it. Inputting a new script is
1388 just like typing in a message using SEND. To finish inputting type: /EX
1389 on a newline, to abandon the script type: /ABORT.</P>
1390 <P>You may find the (curiously named) command BLANK useful to break
1391 up the output. If you simply want a blank line, it is easier to
1392 input one or more spaces and press the <return> key.</P>
1393 <P>See UNSET/STARTUP to remove a script.</P>
1394 <H2><A NAME="ss12.79">12.79</A> <A HREF="usermanual_en.html#toc12.79">set/talk</A>
1397 <P><CODE><B>set/talk</B> Allow TALK messages to come out on your terminal</CODE></P>
1400 <H2><A NAME="ss12.80">12.80</A> <A HREF="usermanual_en.html#toc12.80">set/usstate</A>
1403 <P><CODE><B>set/usstate</B> Allow US State info on the end of DX announcements</CODE></P>
1406 <H2><A NAME="ss12.81">12.81</A> <A HREF="usermanual_en.html#toc12.81">set/wcy</A>
1409 <P><CODE><B>set/wcy</B> Allow WCY messages to come out on your terminal</CODE></P>
1412 <H2><A NAME="ss12.82">12.82</A> <A HREF="usermanual_en.html#toc12.82">set/wwv</A>
1415 <P><CODE><B>set/wwv</B> Allow WWV messages to come out on your terminal</CODE></P>
1418 <H2><A NAME="ss12.83">12.83</A> <A HREF="usermanual_en.html#toc12.83">set/wx</A>
1421 <P><CODE><B>set/wx</B> Allow WX messages to come out on your terminal</CODE></P>
1424 <H2><A NAME="ss12.84">12.84</A> <A HREF="usermanual_en.html#toc12.84">show/chat [<group>] [<lines>]</A>
1427 <P><CODE><B>show/chat [<group>] [<lines>]</B> Show any chat or conferencing </CODE></P>
1429 <P>This command allows you to see any chat or conferencing that has
1430 occurred whilst you were away. SHOW/CHAT on its own will show data for
1431 all groups. If you use a group name then it will show only chat for
1433 <H2><A NAME="ss12.85">12.85</A> <A HREF="usermanual_en.html#toc12.85">show/configuration [<node>]</A>
1436 <P><CODE><B>show/configuration [<node>]</B> Show all the nodes and users visible</CODE></P>
1438 <P>This command allows you to see all the users that can be seen
1439 and the nodes to which they are connected.</P>
1440 <P>This command is normally abbreviated to: sh/c</P>
1441 <P>Normally, the list returned will be just for the nodes from your
1442 country (because the list otherwise will be very long).</P>
1448 </CODE></BLOCKQUOTE>
1450 <P>will produce a complete list of all nodes. </P>
1451 <P>BE WARNED: the list that is returned can be VERY long</P>
1452 <P>It is possible to supply a node or part of a prefix and you will get
1453 a list of the users for that node or list of nodes starting with
1460 </CODE></BLOCKQUOTE>
1467 </CODE></BLOCKQUOTE>
1470 <H2><A NAME="ss12.86">12.86</A> <A HREF="usermanual_en.html#toc12.86">show/configuration/node</A>
1473 <P><CODE><B>show/configuration/node</B> Show all the nodes connected locally</CODE></P>
1475 <P>Show all the nodes connected to this node.</P>
1476 <H2><A NAME="ss12.87">12.87</A> <A HREF="usermanual_en.html#toc12.87">show/contest <year and month></A>
1479 <P><CODE><B>show/contest <year and month></B> Show all the contests for a month</CODE></P>
1481 <P>Show all known contests which are maintained at http://www.sk3bg.se/contest/
1482 for a particular month or year. The format is reasonably flexible.
1490 </CODE></BLOCKQUOTE>
1493 <H2><A NAME="ss12.88">12.88</A> <A HREF="usermanual_en.html#toc12.88">show/date [<prefix>|<callsign>]</A>
1496 <P><CODE><B>show/date [<prefix>|<callsign>]</B> Show the local time </CODE></P>
1498 <P>This is very nearly the same as SHOW/TIME, the only difference the format
1499 of the date string if no arguments are given.</P>
1500 <P>If no prefixes or callsigns are given then this command returns the local
1501 time and UTC as the computer has it right now. If you give some prefixes
1502 then it will show UTC and UTC + the local offset (not including DST) at
1503 the prefixes or callsigns that you specify.</P>
1504 <H2><A NAME="ss12.89">12.89</A> <A HREF="usermanual_en.html#toc12.89">show/db0sdx <callsign></A>
1507 <P><CODE><B>show/db0sdx <callsign></B> Show QSL infomation from DB0SDX database</CODE></P>
1509 <P>This command queries the DB0SDX QSL server on the internet
1510 and returns any information available for that callsign. This service
1511 is provided for users of this software by http://www.qslinfo.de.</P>
1512 <P>See also SHOW/QRZ, SHOW/WM7D.</P>
1513 <H2><A NAME="ss12.90">12.90</A> <A HREF="usermanual_en.html#toc12.90">show/dx</A>
1516 <P><CODE><B>show/dx</B> Interrogate the spot database</CODE></P>
1518 <P>If you just type SHOW/DX you will get the last so many spots
1519 (sysop configurable, but usually 10).</P>
1520 <P>In addition you can add any number of these commands in very nearly
1521 any order to the basic SHOW/DX command, they are:-</P>
1525 on <band> - eg 160m 20m 2m 23cm 6mm
1526 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
1527 on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
1528 <from>-<to>
1530 </CODE></BLOCKQUOTE>
1535 <number> - the number of spots you want
1536 <from>-<to> - <from> spot no <to> spot no in the selected list
1537 <from>/<to>
1539 </CODE></BLOCKQUOTE>
1544 <prefix> - for a spotted callsign beginning with <prefix>
1545 *<suffix> - for a spotted callsign ending in <suffix>
1546 *<string>* - for a spotted callsign containing <string>
1548 </CODE></BLOCKQUOTE>
1553 day <number> - starting <number> days ago
1554 day <from>-<to> - <from> days <to> days ago
1555 <from>/<to>
1557 </CODE></BLOCKQUOTE>
1562 info <text> - any spots containing <text> in the info or remarks
1564 </CODE></BLOCKQUOTE>
1569 by <call> - any spots spotted by <call> (spotter <call> is the
1572 </CODE></BLOCKQUOTE>
1577 qsl - this automatically looks for any qsl info on the call
1578 held in the spot database.
1580 </CODE></BLOCKQUOTE>
1585 iota [<iota>] - If the iota island number is missing it will look for
1586 the string iota and anything which looks like an iota
1587 island number. If you specify then it will look for
1590 </CODE></BLOCKQUOTE>
1595 qra [<locator>] - this will look for the specific locator if you specify
1596 one or else anything that looks like a locator.
1598 </CODE></BLOCKQUOTE>
1603 dxcc - treat the prefix as a 'country' and look for spots
1604 from that country regardless of actual prefix.
1607 </CODE></BLOCKQUOTE>
1612 You can also use this with the 'by' keyword so
1615 </CODE></BLOCKQUOTE>
1620 real or rt - Format the output the same as for real time spots. The
1621 formats are deliberately different (so you can tell
1622 one sort from the other). This is useful for some
1623 logging programs that can't cope with normal sh/dx
1624 output. An alias of SHOW/FDX is available.
1626 </CODE></BLOCKQUOTE>
1631 filter - Filter the spots, before output, with the user's
1632 spot filter. An alias of SHOW/MYDX is available.
1634 </CODE></BLOCKQUOTE>
1639 zone <zones> - look for spots in the cq zone (or zones) specified.
1640 zones are numbers separated by commas.
1642 </CODE></BLOCKQUOTE>
1647 by_zone <zones> - look for spots spotted by people in the cq zone
1650 </CODE></BLOCKQUOTE>
1655 itu <itus> - look for spots in the itu zone (or zones) specified
1656 itu zones are numbers separated by commas.
1658 </CODE></BLOCKQUOTE>
1663 by_itu <itus> - look for spots spotted by people in the itu zone
1666 </CODE></BLOCKQUOTE>
1671 state <list> - look for spots in the US state (or states) specified
1672 The list is two letter state codes separated by commas.
1674 </CODE></BLOCKQUOTE>
1679 by_state <list> - look for spots spotted by people in the US state
1682 </CODE></BLOCKQUOTE>
1689 </CODE></BLOCKQUOTE>
1695 SH/DX on 20m info iota
1696 SH/DX 9a on vhf day 30
1702 SH/DX dxcc oq2 by w dxcc
1706 SH/DX by_state in,oh
1708 </CODE></BLOCKQUOTE>
1711 <H2><A NAME="ss12.91">12.91</A> <A HREF="usermanual_en.html#toc12.91">show/dxcc <prefix></A>
1714 <P><CODE><B>show/dxcc <prefix></B> Interrogate the spot database by country</CODE></P>
1716 <P>This command takes the <prefix> (which can be a full or partial
1717 callsign if desired), looks up which internal country number it is
1718 and then displays all the spots as per SH/DX for that country.</P>
1719 <P>This is now an alias for 'SHOW/DX DXCC' </P>
1720 <P>The options for SHOW/DX also apply to this command.
1726 SH/DXCC W on 20m iota
1728 </CODE></BLOCKQUOTE>
1730 <P>This can be done with the SHOW/DX command like this:-</P>
1735 SH/DX dxcc w on 20m iota
1737 </CODE></BLOCKQUOTE>
1739 <P>This is an alias for: SH/DX dxcc</P>
1740 <H2><A NAME="ss12.92">12.92</A> <A HREF="usermanual_en.html#toc12.92">show/dxqsl <callsign></A>
1743 <P><CODE><B>show/dxqsl <callsign></B> Show any QSL info gathered from spots</CODE></P>
1745 <P>The node collects information from the comment fields in spots (things
1746 like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.</P>
1747 <P>This command allows you to interrogate that database and if the callsign
1748 is found will display the manager(s) that people have spotted. This
1749 information is NOT reliable, but it is normally reasonably accurate if
1750 it is spotted enough times.</P>
1751 <P>For example:-</P>
1757 </CODE></BLOCKQUOTE>
1759 <P>You can check the raw input spots yourself with:-</P>
1765 </CODE></BLOCKQUOTE>
1767 <P>This gives you more background information.</P>
1768 <H2><A NAME="ss12.93">12.93</A> <A HREF="usermanual_en.html#toc12.93">show/dxstats [days] [date]</A>
1771 <P><CODE><B>show/dxstats [days] [date]</B> Show the DX Statistics</CODE></P>
1773 <P>Show the total DX spots for the last <days> no of days (default is 31),
1774 starting from a <date> (default: today).</P>
1775 <H2><A NAME="ss12.94">12.94</A> <A HREF="usermanual_en.html#toc12.94">show/fdx</A>
1778 <P><CODE><B>show/fdx</B> Show the DX data in realtime format.</CODE></P>
1780 <P>Normally SHOW/DX outputs spot data in a different format to the
1781 realtime data. This is a deliberate policy (so you can tell the
1782 difference between the two). Some logging programs cannot handle
1783 this so SHOW/FDX outputs historical data in real time format.</P>
1784 <P>This is an alias for: SHOW/DX real</P>
1785 <H2><A NAME="ss12.95">12.95</A> <A HREF="usermanual_en.html#toc12.95">show/files [<filearea> [<string>]]</A>
1788 <P><CODE><B>show/files [<filearea> [<string>]]</B> List the contents of a filearea</CODE></P>
1790 <P>SHOW/FILES on its own will show you a list of the various fileareas
1791 available on the system. To see the contents of a particular file
1795 SH/FILES <filearea>
1797 </CODE></BLOCKQUOTE>
1799 where <filearea> is the name of the filearea you want to see the
1801 <P>You can also use shell globbing characters like '*' and '?' in a
1802 string to see a selection of files in a filearea eg:-
1805 SH/FILES bulletins arld*
1807 </CODE></BLOCKQUOTE>
1809 <P>See also TYPE - to see the contents of a file.</P>
1810 <H2><A NAME="ss12.96">12.96</A> <A HREF="usermanual_en.html#toc12.96">show/filter</A>
1813 <P><CODE><B>show/filter</B> Show the contents of all the filters you have set</CODE></P>
1815 <P>Show the contents of all the filters that are set. This command displays
1816 all the filters set - for all the various categories.</P>
1817 <H2><A NAME="ss12.97">12.97</A> <A HREF="usermanual_en.html#toc12.97">show/hfstats [days] [date]</A>
1820 <P><CODE><B>show/hfstats [days] [date]</B> Show the HF DX Statistics </CODE></P>
1822 <P>Show the HF DX spots breakdown by band for the last <days> no of days
1823 (default is 31), starting from a <date> (default: today).</P>
1824 <H2><A NAME="ss12.98">12.98</A> <A HREF="usermanual_en.html#toc12.98">show/hftable [days] [date] [prefix ...]</A>
1827 <P><CODE><B>show/hftable [days] [date] [prefix ...]</B> Show the HF DX Spotter Table</CODE></P>
1829 <P>Show the HF DX Spotter table for the list of prefixes for the last
1830 <days> no of days (default is 31), starting from a <date> (default: today).</P>
1831 <P>If there are no prefixes then it will show the table for your country.</P>
1832 <P>Remember that some countries have more than one "DXCC country" in them
1833 (eg G :-), to show them (assuming you are not in G already which is
1834 specially treated in the code) you must list all the relevant prefixes</P>
1838 sh/hftable g gm gd gi gj gw gu
1840 </CODE></BLOCKQUOTE>
1842 <P>Note that the prefixes are converted into country codes so you don't have
1843 to list all possible prefixes for each country.</P>
1844 <P>If you want more or less days than the default simply include the
1845 number you require:-</P>
1851 </CODE></BLOCKQUOTE>
1853 <P>If you want to start at a different day, simply add the date in some
1854 recognizable form:-</P>
1858 sh/hftable 2 25nov02
1859 sh/hftable 2 25-nov-02
1861 sh/hftable 2 25/11/02
1863 </CODE></BLOCKQUOTE>
1865 <P>This will show the stats for your DXCC for that CQWW contest weekend. </P>
1866 <P>You can specify either prefixes or full callsigns (so you can see how you
1867 did against all your mates). You can also say 'all' which will then print
1868 the worldwide statistics.</P>
1874 </CODE></BLOCKQUOTE>
1877 <H2><A NAME="ss12.99">12.99</A> <A HREF="usermanual_en.html#toc12.99">show/moon [ndays] [<prefix>|<callsign>]</A>
1880 <P><CODE><B>show/moon [ndays] [<prefix>|<callsign>]</B> Show Moon rise and set times</CODE></P>
1882 <P>Show the Moon rise and set times for a (list of) prefixes or callsigns,
1883 together with the azimuth and elevation of the sun currently at those
1885 <P>If you don't specify any prefixes or callsigns, it will show the times for
1886 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
1887 together with the current azimuth and elevation.</P>
1888 <P>In addition, it will show the illuminated fraction of the moons disk.</P>
1889 <P>If all else fails it will show the Moonrise and set times for the node
1890 that you are connected to. </P>
1891 <P>For example:-</P>
1898 </CODE></BLOCKQUOTE>
1900 <P>You can also use this command to see into the past or the future, so
1901 if you want to see yesterday's times then do:-</P>
1907 </CODE></BLOCKQUOTE>
1909 <P>or in three days time:-</P>
1915 </CODE></BLOCKQUOTE>
1917 <P>Upto 366 days can be checked both in the past and in the future.</P>
1918 <P>Please note that the rise and set times are given as the UT times of rise and
1919 set on the requested UT day.</P>
1920 <H2><A NAME="ss12.100">12.100</A> <A HREF="usermanual_en.html#toc12.100">show/muf <prefix> [<hours>][long]</A>
1923 <P><CODE><B>show/muf <prefix> [<hours>][long]</B> Show the likely propagation to a prefix</CODE></P>
1925 <P>This command allow you to estimate the likelihood of you contacting
1926 a station with the prefix you have specified. The output assumes a modest
1927 power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)</P>
1928 <P>The result predicts the most likely operating frequencies and signal
1929 levels for high frequency (shortwave) radio propagation paths on
1930 specified days of the year and hours of the day. It is most useful for
1931 paths between 250 km and 6000 km, but can be used with reduced accuracy
1932 for paths shorter or longer than this.</P>
1933 <P>The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
1934 used to predict the MUF given the predicted flux, day of the year,
1935 hour of the day and geographic coordinates of the transmitter and
1936 receiver. This routine is reasonably accurate for the purposes here,
1937 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
1938 than the programs used by major shortwave broadcasting organizations,
1939 such as the Voice of America.</P>
1940 <P>The command will display some header information detailing its
1941 assumptions, together with the locations, latitude and longitudes and
1942 bearings. It will then show UTC (UT), local time at the other end
1943 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
1944 (Zen) and the likely signal strengths. Then for each frequency for which
1945 the system thinks there is a likelihood of a circuit it prints a value.</P>
1946 <P>The value is currently a likely S meter reading based on the conventional
1947 6dB / S point scale. If the value has a '+' appended it means that it is
1948 1/2 an S point stronger. If the value is preceeded by an 'm' it means that
1949 there is likely to be much fading and by an 's' that the signal is likely
1951 <P>By default SHOW/MUF will show the next two hours worth of data. You
1952 can specify anything up to 24 hours worth of data by appending the no of
1953 hours required after the prefix. For example:-</P>
1959 </CODE></BLOCKQUOTE>
1965 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
1966 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
1967 Location Lat / Long Azim
1968 East Dereham, Norfolk 52 41 N 0 57 E 47
1969 United-States-W 43 0 N 87 54 W 299
1970 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
1971 18 23 11.5 -35 mS0+ mS2 S3
1972 19 0 11.2 -41 mS0+ mS2 S3
1974 </CODE></BLOCKQUOTE>
1976 <P>indicating that you will have weak, fading circuits on top band and
1977 80m but usable signals on 40m (about S3).</P>
1984 </CODE></BLOCKQUOTE>
1986 <P>will get you the above display, but with the next 24 hours worth of
1987 propagation data.</P>
1994 </CODE></BLOCKQUOTE>
1996 <P>Gives you an estimate of the long path propagation characterics. It
1997 should be noted that the figures will probably not be very useful, nor
1998 terrible accurate, but it is included for completeness.</P>
1999 <H2><A NAME="ss12.101">12.101</A> <A HREF="usermanual_en.html#toc12.101">show/mydx</A>
2002 <P><CODE><B>show/mydx</B> Show the DX data filtered with your spot filter.</CODE></P>
2004 <P>SHOW/DX potentially shows all the spots available in the system. Using
2005 SHOW/MYDX will, instead, filter the availble spots using any spot filter
2006 that you have set, first. </P>
2007 <P>This command, together with ACCEPT/SPOT or REJECT/SPOT, will allow
2008 you to customise the spots that you receive.</P>
2009 <P>So if you have said: ACC/SPOT on hf</P>
2010 <P>Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
2011 options on SH/DX can still be used.</P>
2012 <H2><A NAME="ss12.102">12.102</A> <A HREF="usermanual_en.html#toc12.102">show/newconfiguration [<node>]</A>
2015 <P><CODE><B>show/newconfiguration [<node>]</B> Show all the nodes and users visible</CODE></P>
2017 <P>This command allows you to see all the users that can be seen
2018 and the nodes to which they are connected. </P>
2019 <P>This command produces essentially the same information as
2020 SHOW/CONFIGURATION except that it shows all the duplication of
2021 any routes that might be present It also uses a different format
2022 which may not take up quite as much space if you don't have any
2024 <P>BE WARNED: the list that is returned can be VERY long</P>
2025 <H2><A NAME="ss12.103">12.103</A> <A HREF="usermanual_en.html#toc12.103">show/newconfiguration/node</A>
2028 <P><CODE><B>show/newconfiguration/node</B> Show all the nodes connected locally</CODE></P>
2030 <P>Show all the nodes connected to this node in the new format.</P>
2031 <H2><A NAME="ss12.104">12.104</A> <A HREF="usermanual_en.html#toc12.104">show/prefix <callsign></A>
2034 <P><CODE><B>show/prefix <callsign></B> Interrogate the prefix database </CODE></P>
2036 <P>This command takes the <callsign> (which can be a full or partial
2037 callsign or a prefix), looks up which internal country number
2038 it is and then displays all the relevant prefixes for that country
2039 together with the internal country no, the CQ and ITU regions. </P>
2040 <P>See also SHOW/DXCC</P>
2041 <H2><A NAME="ss12.105">12.105</A> <A HREF="usermanual_en.html#toc12.105">show/qra <lat> <long></A>
2044 <P><CODE><B>show/qra <lat> <long></B> Convert lat/long to a QRA Grid locator</CODE></P>
2046 <P>This is a multipurpose command that allows you either to calculate the
2047 distance and bearing between two locators or (if only one locator is
2048 given on the command line) the distance and beraing from your station
2049 to the locator. For example:-</P>
2056 </CODE></BLOCKQUOTE>
2058 <P>The first example will show the distance and bearing to the locator from
2059 yourself, the second example will calculate the distance and bearing from
2060 the first locator to the second. You can use 4 or 6 character locators.</P>
2061 <P>It is also possible to convert a latitude and longitude to a locator by
2062 using this command with a latitude and longitude as an argument, for
2067 SH/QRA 52 41 N 0 58 E
2069 </CODE></BLOCKQUOTE>
2072 <H2><A NAME="ss12.106">12.106</A> <A HREF="usermanual_en.html#toc12.106">show/qra <locator> [<locator>]</A>
2075 <P><CODE><B>show/qra <locator> [<locator>]</B> Show distance between QRA Grid locators</CODE></P>
2078 <H2><A NAME="ss12.107">12.107</A> <A HREF="usermanual_en.html#toc12.107">show/qrz <callsign></A>
2081 <P><CODE><B>show/qrz <callsign></B> Show any callbook details on a callsign</CODE></P>
2083 <P>This command queries the QRZ callbook server on the internet
2084 and returns any information available for that callsign. This service
2085 is provided for users of this software by http://www.qrz.com </P>
2086 <P>See also SHOW/WM7D for an alternative.</P>
2087 <H2><A NAME="ss12.108">12.108</A> <A HREF="usermanual_en.html#toc12.108">show/route <callsign> ...</A>
2090 <P><CODE><B>show/route <callsign> ...</B> Show the route to the callsign</CODE></P>
2092 <P>This command allows you to see to which node the callsigns specified are
2093 connected. It is a sort of inverse sh/config.</P>
2099 </CODE></BLOCKQUOTE>
2102 <H2><A NAME="ss12.109">12.109</A> <A HREF="usermanual_en.html#toc12.109">show/satellite <name> [<hours> <interval>]</A>
2105 <P><CODE><B>show/satellite <name> [<hours> <interval>]</B> Show tracking data</CODE></P>
2107 <P>Show the tracking data from your location to the satellite of your choice
2108 from now on for the next few hours.</P>
2109 <P>If you use this command without a satellite name it will display a list
2110 of all the satellites known currently to the system. </P>
2111 <P>If you give a name then you can obtain tracking data of all the passes
2112 that start and finish 5 degrees below the horizon. As default it will
2113 give information for the next three hours for every five minute period.</P>
2114 <P>You can alter the number of hours and the step size, within certain
2116 <P>Each pass in a period is separated with a row of '-----' characters</P>
2117 <P>So for example:-</P>
2122 SH/SAT FENGYUN1 12 2
2124 </CODE></BLOCKQUOTE>
2127 <H2><A NAME="ss12.110">12.110</A> <A HREF="usermanual_en.html#toc12.110">show/startup</A>
2130 <P><CODE><B>show/startup</B> View your own startup script</CODE></P>
2132 <P>View the contents of a startup script created with SET/STARTUP.</P>
2133 <H2><A NAME="ss12.111">12.111</A> <A HREF="usermanual_en.html#toc12.111">show/station [<callsign> ..]</A>
2136 <P><CODE><B>show/station [<callsign> ..]</B> Show information about a callsign</CODE></P>
2138 <P>Show the information known about a callsign and whether (and where)
2139 that callsign is connected to the cluster.</P>
2145 </CODE></BLOCKQUOTE>
2147 <P>If no callsign is given then show the information for yourself.</P>
2148 <H2><A NAME="ss12.112">12.112</A> <A HREF="usermanual_en.html#toc12.112">show/sun [ndays] [<prefix>|<callsign>]</A>
2151 <P><CODE><B>show/sun [ndays] [<prefix>|<callsign>]</B> Show sun rise and set times</CODE></P>
2153 <P>Show the sun rise and set times for a (list of) prefixes or callsigns,
2154 together with the azimuth and elevation of the sun currently at those
2156 <P>If you don't specify any prefixes or callsigns, it will show the times for
2157 your QTH (assuming you have set it with either SET/LOCATION or SET/QRA),
2158 together with the current azimuth and elevation.</P>
2159 <P>If all else fails it will show the sunrise and set times for the node
2160 that you are connected to. </P>
2161 <P>For example:-</P>
2166 SH/SUN G1TLH K9CW ZS
2168 </CODE></BLOCKQUOTE>
2170 <P>You can also use this command to see into the past or the future, so
2171 if you want to see yesterday's times then do:-</P>
2177 </CODE></BLOCKQUOTE>
2179 <P>or in three days time:-</P>
2185 </CODE></BLOCKQUOTE>
2187 <P>Upto 366 days can be checked both in the past and in the future.</P>
2188 <P>Please note that the rise and set times are given as the UT times of rise
2189 and set on the requested UT day.</P>
2190 <H2><A NAME="ss12.113">12.113</A> <A HREF="usermanual_en.html#toc12.113">show/time [<prefix>|<callsign>]</A>
2193 <P><CODE><B>show/time [<prefix>|<callsign>]</B> Show the local time </CODE></P>
2195 <P>If no prefixes or callsigns are given then this command returns the local
2196 time and UTC as the computer has it right now. If you give some prefixes
2197 then it will show UTC and UTC + the local offset (not including DST) at
2198 the prefixes or callsigns that you specify.</P>
2199 <H2><A NAME="ss12.114">12.114</A> <A HREF="usermanual_en.html#toc12.114">show/usdb [call ..]</A>
2202 <P><CODE><B>show/usdb [call ..]</B> Show information held on the FCC Call database</CODE></P>
2204 <P>Show the City and State of a Callsign held on the FCC database if
2205 his is being run on this system, eg:-</P>
2211 </CODE></BLOCKQUOTE>
2214 <H2><A NAME="ss12.115">12.115</A> <A HREF="usermanual_en.html#toc12.115">show/vhfstats [days] [date]</A>
2217 <P><CODE><B>show/vhfstats [days] [date]</B> Show the VHF DX Statistics</CODE></P>
2219 <P>Show the VHF DX spots breakdown by band for the last
2220 <days> no of days (default is 31), starting from a date (default: today).</P>
2221 <H2><A NAME="ss12.116">12.116</A> <A HREF="usermanual_en.html#toc12.116">show/vhftable [days] [date] [prefix ...]</A>
2224 <P><CODE><B>show/vhftable [days] [date] [prefix ...]</B> Show the VHF DX Spotter Table</CODE></P>
2226 <P>Show the VHF DX Spotter table for the list of prefixes for the last
2227 <days> no of days (default is 31), starting from a date (default: today).</P>
2228 <P>If there are no prefixes then it will show the table for your country.</P>
2229 <P>Remember that some countries have more than one "DXCC country" in them
2230 (eg G :-), to show them (assuming you are not in G already which is
2231 specially treated in the code) you must list all the relevant prefixes</P>
2235 sh/vhftable g gm gd gi gj gw gu
2237 </CODE></BLOCKQUOTE>
2239 <P>Note that the prefixes are converted into country codes so you don't have
2240 to list all possible prefixes for each country.</P>
2241 <P>If you want more or less days than the default simply include the
2242 number you require:-</P>
2248 </CODE></BLOCKQUOTE>
2250 <P>If you want to start at a different day, simply add the date in some
2251 recognizable form:-</P>
2255 sh/vhftable 2 25nov02
2256 sh/vhftable 2 25-nov-02
2257 sh/vhftable 2 021125
2258 sh/vhftable 2 25/11/02
2260 </CODE></BLOCKQUOTE>
2262 <P>This will show the stats for your DXCC for that CQWW contest weekend. </P>
2263 <P>You can specify either prefixes or full callsigns (so you can see how you
2264 did against all your mates). You can also say 'all' which will then print
2265 the worldwide statistics.</P>
2271 </CODE></BLOCKQUOTE>
2274 <H2><A NAME="ss12.117">12.117</A> <A HREF="usermanual_en.html#toc12.117">show/wcy</A>
2277 <P><CODE><B>show/wcy</B> Show last 10 WCY broadcasts</CODE></P>
2280 <H2><A NAME="ss12.118">12.118</A> <A HREF="usermanual_en.html#toc12.118">show/wcy <n></A>
2283 <P><CODE><B>show/wcy <n></B> Show last <n> WCY broadcasts</CODE></P>
2285 <P>Display the most recent WCY information that has been received by the system</P>
2287 <H2><A NAME="ss12.119">12.119</A> <A HREF="usermanual_en.html#toc12.119">show/wm7d <callsign></A>
2290 <P><CODE><B>show/wm7d <callsign></B> Show callbook details on a US callsigns</CODE></P>
2292 <P>This command queries the WM7D callbook server on the internet
2293 and returns any information available for that US callsign. This service
2294 is provided for users of this software by http://www.wm7d.net.</P>
2295 <P>See also SHOW/QRZ. </P>
2296 <H2><A NAME="ss12.120">12.120</A> <A HREF="usermanual_en.html#toc12.120">show/wwv</A>
2299 <P><CODE><B>show/wwv</B> Show last 10 WWV broadcasts</CODE></P>
2302 <H2><A NAME="ss12.121">12.121</A> <A HREF="usermanual_en.html#toc12.121">show/wwv <n></A>
2305 <P><CODE><B>show/wwv <n></B> Show last <n> WWV broadcasts</CODE></P>
2307 <P>Display the most recent WWV information that has been received by the system</P>
2308 <H2><A NAME="ss12.122">12.122</A> <A HREF="usermanual_en.html#toc12.122">sysop</A>
2311 <P><CODE><B>sysop</B> Regain your privileges if you login remotely</CODE></P>
2313 <P>The system automatically reduces your privilege level to that of a
2314 normal user if you login in remotely. This command allows you to
2315 regain your normal privilege level. It uses the normal system: five
2316 numbers are returned that are indexes into the character array that is
2317 your assigned password (see SET/PASSWORD). The indexes start from
2319 <P>You are expected to return a string which contains the characters
2320 required in the correct order. You may intersperse those characters
2321 with others to obscure your reply for any watchers. For example (and
2322 these values are for explanation :-):</P>
2326 password = 012345678901234567890123456789
2330 </CODE></BLOCKQUOTE>
2335 aa2bbbb0ccc5ddd7xxx3n
2339 </CODE></BLOCKQUOTE>
2341 <P>They will all match. If there is no password you will still be offered
2342 numbers but nothing will happen when you input a string. Any match is
2344 <H2><A NAME="ss12.123">12.123</A> <A HREF="usermanual_en.html#toc12.123">talk <call> > <node> [<text>]</A>
2347 <P><CODE><B>talk <call> > <node> [<text>]</B> Send a text message to another station via a node</CODE></P>
2349 <P>Send a short message to any other station that is visible on the cluster
2350 system. You can send it to anyone you can see with a SHOW/CONFIGURATION
2351 command, they don't have to be connected locally.</P>
2352 <P>The second form of TALK is used when other cluster nodes are connected
2353 with restricted information. This usually means that they don't send
2354 the user information usually associated with logging on and off the cluster.</P>
2355 <P>If you know that G3JNB is likely to be present on GB7TLH, but you can only
2356 see GB7TLH in the SH/C list but with no users, then you would use the
2357 second form of the talk message.</P>
2358 <P>If you want to have a ragchew with someone you can leave the text message
2359 out and the system will go into 'Talk' mode. What this means is that a
2360 short message is sent to the recipient telling them that you are in a
2361 'Talking' frame of mind and then you just type - everything you send will
2362 go to the station that you asked for. </P>
2363 <P>All the usual announcements, spots and so on will still come out on your
2365 <P>If you want to do something (such as send a spot) you preceed the normal
2366 command with a '/' character, eg:-</P>
2370 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2373 </CODE></BLOCKQUOTE>
2375 <P>To leave talk mode type:</P>
2381 </CODE></BLOCKQUOTE>
2383 <P>If you are in 'Talk' mode, there is an extention to the '/' command which
2384 allows you to send the output to all the people you are talking to. You do
2385 with the '//' command. For example:-</P>
2391 </CODE></BLOCKQUOTE>
2393 <P>will send the hftable as you have it to all the people you are currently
2395 <H2><A NAME="ss12.124">12.124</A> <A HREF="usermanual_en.html#toc12.124">talk <call> [<text>]</A>
2398 <P><CODE><B>talk <call> [<text>]</B> Send a text message to another station</CODE></P>
2401 <H2><A NAME="ss12.125">12.125</A> <A HREF="usermanual_en.html#toc12.125">type <filearea>/<name></A>
2404 <P><CODE><B>type <filearea>/<name></B> Look at the contents of a file in one of the fileareas</CODE></P>
2406 <P>Type out the contents of a file in a filearea. So, for example, in
2407 filearea 'bulletins' you want to look at file 'arld051' you would
2411 TYPE bulletins/arld051
2413 </CODE></BLOCKQUOTE>
2415 <P>See also SHOW/FILES to see what fileareas are available and a
2416 list of content.</P>
2417 <H2><A NAME="ss12.126">12.126</A> <A HREF="usermanual_en.html#toc12.126">unset/announce</A>
2420 <P><CODE><B>unset/announce</B> Stop announce messages coming out on your terminal</CODE></P>
2423 <H2><A NAME="ss12.127">12.127</A> <A HREF="usermanual_en.html#toc12.127">unset/anntalk</A>
2426 <P><CODE><B>unset/anntalk</B> Stop talk like announce messages on your terminal</CODE></P>
2428 <P>The announce system on legacy cluster nodes is used as a talk
2429 substitute because the network is so poorly connected. If you:</P>
2435 </CODE></BLOCKQUOTE>
2437 <P>you will suppress several of these announces, you may miss the odd
2438 useful one as well, but you would probably miss them anyway in the
2439 welter of useless ones.</P>
2445 </CODE></BLOCKQUOTE>
2447 <P>allows you to see them again. This is the default.</P>
2448 <H2><A NAME="ss12.128">12.128</A> <A HREF="usermanual_en.html#toc12.128">unset/beep</A>
2451 <P><CODE><B>unset/beep</B> Stop beeps for DX and other messages on your terminal</CODE></P>
2454 <H2><A NAME="ss12.129">12.129</A> <A HREF="usermanual_en.html#toc12.129">unset/dx</A>
2457 <P><CODE><B>unset/dx</B> Stop DX messages coming out on your terminal</CODE></P>
2460 <H2><A NAME="ss12.130">12.130</A> <A HREF="usermanual_en.html#toc12.130">unset/dxcq</A>
2463 <P><CODE><B>unset/dxcq</B> Stop CQ Zones on the end of DX announcements</CODE></P>
2465 <P>Display both the Spotter's and the Spotted's CQ Zone on the end
2466 of a DX announcement (there is just enough room). Some user programs
2467 cannot cope with this. The Spotter's CQ is on the RHS of the
2468 time, the Spotted's CQ is on the LHS.</P>
2469 <P>Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE</P>
2470 <P>Do a STAT/USER to see which flags you have set if you are confused. </P>
2471 <H2><A NAME="ss12.131">12.131</A> <A HREF="usermanual_en.html#toc12.131">unset/dxgrid</A>
2474 <P><CODE><B>unset/dxgrid</B> Stop QRA Grid Squares on the end of DX announcements</CODE></P>
2476 <P>A standard feature which is enabled in version 1.43 and above is
2477 that if the spotter's grid square is known it is output on the end
2478 of a DX announcement (there is just enough room). Some user programs
2479 cannot cope with this. You can use this command to reset (or set)
2481 <P>Conflicts with: SET/DXCQ, SET/DXITU</P>
2482 <P>Do a STAT/USER to see which flags you have set if you are confused. </P>
2483 <H2><A NAME="ss12.132">12.132</A> <A HREF="usermanual_en.html#toc12.132">unset/dxitu</A>
2486 <P><CODE><B>unset/dxitu</B> Stop ITU Zones on the end of DX announcements</CODE></P>
2488 <P>Display both the Spotter's and the Spotted's ITU Zone on the end
2489 of a DX announcement (there is just enough room). Some user programs
2490 cannot cope with this. The Spotter's ITU is on the RHS of the
2491 time, the Spotted's ITU is on the LHS.</P>
2492 <P>Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE</P>
2493 <P>Do a STAT/USER to see which flags you have set if you are confused. </P>
2494 <H2><A NAME="ss12.133">12.133</A> <A HREF="usermanual_en.html#toc12.133">unset/echo</A>
2497 <P><CODE><B>unset/echo</B> Stop the cluster echoing your input</CODE></P>
2499 <P>If you are connected via a telnet session, different implimentations
2500 of telnet handle echo differently depending on whether you are
2501 connected via port 23 or some other port. You can use this command
2502 to change the setting appropriately. </P>
2503 <P>The setting is stored in your user profile.</P>
2504 <P>YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.</P>
2505 <H2><A NAME="ss12.134">12.134</A> <A HREF="usermanual_en.html#toc12.134">unset/email</A>
2508 <P><CODE><B>unset/email</B> Stop personal msgs being forwarded by email</CODE></P>
2510 <P>If any personal messages come in for your callsign then you can use
2511 these commands to control whether they are forwarded onto your email
2512 address. To enable the forwarding do something like:-</P>
2516 SET/EMAIL mike.tubby@somewhere.com
2518 </CODE></BLOCKQUOTE>
2520 <P>You can have more than one email address (each one separated by a space).
2521 Emails are forwarded to all the email addresses you specify.</P>
2522 <P>You can disable forwarding by:-</P>
2528 </CODE></BLOCKQUOTE>
2531 <H2><A NAME="ss12.135">12.135</A> <A HREF="usermanual_en.html#toc12.135">unset/here</A>
2534 <P><CODE><B>unset/here</B> Tell the system you are absent from your terminal</CODE></P>
2537 <H2><A NAME="ss12.136">12.136</A> <A HREF="usermanual_en.html#toc12.136">unset/logininfo</A>
2540 <P><CODE><B>unset/logininfo</B> No longer inform when a station logs in/out locally</CODE></P>
2543 <H2><A NAME="ss12.137">12.137</A> <A HREF="usermanual_en.html#toc12.137">unset/privilege</A>
2546 <P><CODE><B>unset/privilege</B> Remove any privilege for this session</CODE></P>
2548 <P>You can use this command to 'protect' this session from unauthorised
2549 use. If you want to get your normal privilege back you will need to
2550 either logout and login again (if you are on a console) or use the
2552 <H2><A NAME="ss12.138">12.138</A> <A HREF="usermanual_en.html#toc12.138">unset/prompt</A>
2555 <P><CODE><B>unset/prompt</B> Set your prompt back to default</CODE></P>
2557 <P>This command will set your user prompt to the string that you
2558 say. The point of this command to enable a user to interface to programs
2559 that are looking for a specific prompt (or else you just want a different
2566 </CODE></BLOCKQUOTE>
2568 <P>There are some substitutions that can be added to the prompt:</P>
2572 %C - callsign [which will have ( and ) around it if not here]
2575 %M - cluster 'mycall'
2577 </CODE></BLOCKQUOTE>
2579 <P>The standard prompt is defined as:</P>
2583 SET/PROMPT %C de %M %D %T dxspider >
2585 </CODE></BLOCKQUOTE>
2587 <P>UNSET/PROMPT will undo the SET/PROMPT command and set your prompt back to
2589 <H2><A NAME="ss12.139">12.139</A> <A HREF="usermanual_en.html#toc12.139">unset/startup</A>
2592 <P><CODE><B>unset/startup</B> Remove your own startup script</CODE></P>
2594 <P>You can remove your startup script with UNSET/STARTUP. </P>
2595 <H2><A NAME="ss12.140">12.140</A> <A HREF="usermanual_en.html#toc12.140">unset/talk</A>
2598 <P><CODE><B>unset/talk</B> Stop TALK messages coming out on your terminal</CODE></P>
2601 <H2><A NAME="ss12.141">12.141</A> <A HREF="usermanual_en.html#toc12.141">unset/usstate</A>
2604 <P><CODE><B>unset/usstate</B> Stop US State info on the end of DX announcements</CODE></P>
2606 <P>If the spotter's or spotted's US State is known it is output on the
2607 end of a DX announcement (there is just enough room). </P>
2608 <P>A spotter's state will appear on the RHS of the time (like
2609 SET/DXGRID) and the spotted's State will appear on the LHS of the
2610 time field. Any information found will override any locator
2611 information from SET/DXGRID.</P>
2612 <P>Some user programs cannot cope with this. You can use this command
2613 to reset (or set) this feature.</P>
2614 <P>Conflicts with: SET/DXCQ, SET/DXITU</P>
2615 <P>Do a STAT/USER to see which flags you have set if you are confused. </P>
2616 <H2><A NAME="ss12.142">12.142</A> <A HREF="usermanual_en.html#toc12.142">unset/wcy</A>
2619 <P><CODE><B>unset/wcy</B> Stop WCY messages coming out on your terminal</CODE></P>
2622 <H2><A NAME="ss12.143">12.143</A> <A HREF="usermanual_en.html#toc12.143">unset/wwv</A>
2625 <P><CODE><B>unset/wwv</B> Stop WWV messages coming out on your terminal</CODE></P>
2628 <H2><A NAME="ss12.144">12.144</A> <A HREF="usermanual_en.html#toc12.144">unset/wx</A>
2631 <P><CODE><B>unset/wx</B> Stop WX messages coming out on your terminal</CODE></P>
2634 <H2><A NAME="ss12.145">12.145</A> <A HREF="usermanual_en.html#toc12.145">who</A>
2637 <P><CODE><B>who</B> Show who is physically connected</CODE></P>
2639 <P>This is a quick listing that shows which callsigns are connected and
2640 what sort of connection they have</P>
2641 <H2><A NAME="ss12.146">12.146</A> <A HREF="usermanual_en.html#toc12.146">wx <text></A>
2644 <P><CODE><B>wx <text></B> Send a weather message to local users</CODE></P>
2647 <H2><A NAME="ss12.147">12.147</A> <A HREF="usermanual_en.html#toc12.147">wx full <text></A>
2650 <P><CODE><B>wx full <text></B> Send a weather message to all cluster users</CODE></P>
2655 <A HREF="usermanual_en-11.html">Previous</A>
2656 <A HREF="usermanual_en.html#toc12">Contents</A>
projects / spider.git / blob