--- /dev/null
+ The DXSpider User Manual v1.50
+ Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
+ September 2002 revision 0.1
+
+ A complete reference for users of the DXSpider DXCluster program.
+ ______________________________________________________________________
+
+ Table of Contents
+
+
+
+ 1. Introduction
+ 1.1 What is a DX Cluster?
+ 1.2 So what is DXSpider?
+
+ 2. Logins and logouts.
+ 2.1 AX25 logins.
+ 2.2 Netrom logins.
+ 2.3 Telnet logins.
+ 2.4 Logouts.
+
+ 3. Setting your personal details.
+ 4. Getting and posting DX.
+ 4.1 Receiving DX.
+ 4.2 Posting DX.
+
+ 5. Headings and propagation
+ 5.1 Sun
+ 5.2 Moon
+ 5.3 Heading
+
+ 6. Announcements.
+ 6.1 Making announcements.
+ 6.2 Listing announcements.
+
+ 7. Nodes and users.
+ 8. Talk mode.
+ 9. Mail.
+ 9.1 The "directory" command.
+ 9.2 Reading mail.
+ 9.3 Sending mail.
+ 9.4 Replying to mail.
+ 9.5 Deleting mail
+
+ 10. Filtering (From version 1.45)
+ 10.1 General filter rules
+ 10.2 Types of filter
+ 10.3 Filter options
+ 10.4 Advanced filtering
+
+ 11. Hints, tips and common questions.
+ 12. The DXSpider command reference
+ 12.1 accept
+ 12.2 accept/announce [0-9] <pattern>
+ 12.3 accept/spots [0-9] <pattern>
+ 12.4 accept/wcy [0-9] <pattern>
+ 12.5 accept/wwv [0-9] <pattern>
+ 12.6 announce <text>
+ 12.7 announce full <text>
+ 12.8 apropos <string>
+ 12.9 blank [<string>] [<nn>]
+ 12.10 bye
+ 12.11 clear/announce [1|all]
+ 12.12 clear/route [1|all]
+ 12.13 clear/spots [0-9|all]
+ 12.14 clear/wcy [1|all]
+ 12.15 clear/wwv [1|all]
+ 12.16 dbavail
+ 12.17 dbshow <dbname> <key>
+ 12.18 directory
+ 12.19 directory <from>-<to>
+ 12.20 directory <nn>
+ 12.21 directory all
+ 12.22 directory from <call>
+ 12.23 directory new
+ 12.24 directory own
+ 12.25 directory subject <string>
+ 12.26 directory to <call>
+ 12.27 dx [by <call>] <freq> <call> <remarks>
+ 12.28 echo <line>
+ 12.29 filtering...
+ 12.30 help
+ 12.31 kill <from msgno>-<to msgno>
+ 12.32 kill <msgno> [<msgno..]
+ 12.33 kill <msgno> [<msgno> ...]
+ 12.34 kill from <regex>
+ 12.35 kill to <regex>
+ 12.36 links
+ 12.37 read
+ 12.38 read <msgno>
+ 12.39 reject
+ 12.40 reject/announce [0-9] <pattern>
+ 12.41 reject/spots [0-9] <pattern>
+ 12.42 reject/wcy [0-9] <pattern>
+ 12.43 reject/wwv [0-9] <pattern>
+ 12.44 reply
+ 12.45 reply <msgno>
+ 12.46 reply b <msgno>
+ 12.47 reply noprivate <msgno>
+ 12.48 reply rr <msgno>
+ 12.49 send <call> [<call> ...]
+ 12.50 send copy <msgno> <call>
+ 12.51 send noprivate <call>
+ 12.52 send private <call>
+ 12.53 send rr <call>
+ 12.54 set/address <your address>
+ 12.55 set/announce
+ 12.56 set/anntalk
+ 12.57 set/beep
+ 12.58 set/dx
+ 12.59 set/dxgrid
+ 12.60 set/echo
+ 12.61 set/email <email> ...
+ 12.62 set/here
+ 12.63 set/homenode <node>
+ 12.64 set/language <lang>
+ 12.65 set/location <lat & long>
+ 12.66 set/logininfo
+ 12.67 set/name <your name>
+ 12.68 set/page <lines per page>
+ 12.69 set/password
+ 12.70 set/prompt <string>
+ 12.71 set/qra <locator>
+ 12.72 set/qth <your qth>
+ 12.73 set/talk
+ 12.74 set/wcy
+ 12.75 set/wwv
+ 12.76 set/wx
+ 12.77 show/configuration [<node>]
+ 12.78 show/configuration/node
+ 12.79 show/date [<prefix>|<callsign>]
+ 12.80 show/dx
+ 12.81 show/dxcc <prefix>
+ 12.82 show/dxstats [days] [date]
+ 12.83 show/files [<filearea> [<string>]]
+ 12.84 show/filter
+ 12.85 show/hfstats [days] [date]
+ 12.86 show/hftable [days] [date] [prefix ...]
+ 12.87 show/moon [ndays] [<prefix>|<callsign>]
+ 12.88 show/muf <prefix> [<hours>][long]
+ 12.89 show/newconfiguration [<node>]
+ 12.90 show/newconfiguration/node
+ 12.91 show/prefix <callsign>
+ 12.92 show/qra <lat> <long>
+ 12.93 show/qra <locator> [<locator>]
+ 12.94 show/qrz <callsign>
+ 12.95 show/route <callsign> ...
+ 12.96 show/satellite <name> [<hours> <interval>]
+ 12.97 show/station [<callsign> ..]
+ 12.98 show/sun [ndays] [<prefix>|<callsign>]
+ 12.99 show/time [<prefix>|<callsign>]
+ 12.100 show/usdb [call ..]
+ 12.101 show/vhfstats [days] [date]
+ 12.102 show/vhftable [days] [date] [prefix ...]
+ 12.103 show/wcy
+ 12.104 show/wcy <n>
+ 12.105 show/wwv
+ 12.106 show/wwv <n>
+ 12.107 sysop
+ 12.108 talk <call> > <node> [<text>]
+ 12.109 talk <call> [<text>]
+ 12.110 type <filearea>/<name>
+ 12.111 unset/announce
+ 12.112 unset/anntalk
+ 12.113 unset/beep
+ 12.114 unset/dx
+ 12.115 unset/dxgrid
+ 12.116 unset/echo
+ 12.117 unset/email
+ 12.118 unset/here
+ 12.119 unset/logininfo
+ 12.120 unset/privilege
+ 12.121 unset/prompt
+ 12.122 unset/talk
+ 12.123 unset/wcy
+ 12.124 unset/wwv
+ 12.125 unset/wx
+ 12.126 who
+ 12.127 wx <text>
+ 12.128 wx full <text>
+
+
+ ______________________________________________________________________
+
+ 1\b1.\b. I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
+
+ 1\b1.\b.1\b1.\b. W\bWh\bha\bat\bt i\bis\bs a\ba D\bDX\bX C\bCl\blu\bus\bst\bte\ber\br?\b?
+
+ A DX Cluster is a packet node where DX chasers on any band or mode can
+ post rare or interesting stations that they have worked or heard. Of
+ course other people are doing the same thing too, so you can find new
+ DX as well as telling others about the stations you have worked.
+ Clusters tend to be linked to each other so that the amount of people
+ using them is increased, thereby increasing the amount of posted DX.
+ Other information can be found on clusters such as on-line call books,
+ mail etc. You can talk to other stations connected to the cluster
+ network too, in real time, whether at the node you are logged into or
+ on another node connected to the network. You can also use converse
+ mode, where several stations can talk to each other in the same way.
+ Of course, the DX is still posted to you all the while!
+
+
+ 1\b1.\b.2\b2.\b. S\bSo\bo w\bwh\bha\bat\bt i\bis\bs D\bDX\bXS\bSp\bpi\bid\bde\ber\br?\b?
+
+ PacketCluster nodes have been around since roughly 1985. The original
+ PacketCluster idea came from Dick Newell, AK1A, and ran under DOS. In
+ about 1992 Dick stopped the development of the PacketCluster software
+ for amateur radio. Many systems are still using this relatively old
+ DOS software today.
+ There are several new compatible cluster programs around now,
+ including DXSpider. DXSpider is a clone of PacketCluster software
+ that runs under several operating systems including Linux and Windows.
+ Linux is fast becoming the choice for amateur radio stations because
+ of it's flexibility, reliability and the lack of the memory
+ limitations of DOS. Linux supports multitasking and is also
+ multiuser. It has support for AX25, ROSE, NetROM and TCPIP built in,
+ making it the ideal choice for amateur radio. It is also totally
+ free!
+
+ DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
+ exercise in perl programming. It has developed rapidly and today is a
+ very powerful cluster program. It was designed to be totally
+ compatible with the AK1A program, although several commands have been
+ extended to improve functionality.
+
+ This manual is designed to help you become familiar with the commands
+ that DXSpider supports and to help you get the best from the program
+ so you can enjoy working that rare DX! As DXSpider is being improved
+ all the time, commands will be added as time goes by, so make sure you
+ have the most upto date version of this manual. The latest version
+ will always be included with the cluster program so if you are unsure,
+ simply ask your sysop. The manual will also be available on the
+ wesite.
+
+
+
+ 2\b2.\b. L\bLo\bog\bgi\bin\bns\bs a\ban\bnd\bd l\blo\bog\bgo\bou\but\bts\bs.\b.
+
+ You might not think that there is a lot of point of including a
+ section on how to log in and out of DXSpider. However, you would be
+ suprised at the difficulties some people have in simply getting in and
+ out of the cluster!
+
+ There are several ways a login might be achieved, dependant on how the
+ sysop has DXSpider configured. It is impossible for me to cover all
+ variations but here are the basic ones.
+
+
+ 2\b2.\b.1\b1.\b. A\bAX\bX2\b25\b5 l\blo\bog\bgi\bin\bns\bs.\b.
+
+ Simplicity itself. The usual C\bCO\bON\bNN\bNE\bEC\bCT\bT command will log you straight
+ into the cluster and you will not have to do anything else.
+ Obviously, you will have to connect to the correct callsign. Some
+ nodes use an SSID with their call so you would have to add that.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ connect GB7MBC
+ connect GB7MBC-1
+
+
+
+ 2\b2.\b.2\b2.\b. N\bNe\bet\btr\bro\bom\bm l\blo\bog\bgi\bin\bns\bs.\b.
+
+ There are several possibilities here, dependant on how the sysop has
+ configured his system. If you are connecting via netrom then you are
+ most probably connecting from another station. Listing the nodes in
+ that station with the N\bNO\bOD\bDE\bES\bS command will tell you what callsign or
+ netrom alias to connect to. Then just issue the connect command from
+ there. It is possible that the netrom alias may connect you to a node
+ with an alias for the cluster, such as DXC. Just type this and you
+ will be connected.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+ connect MBCDX
+
+
+
+ 2\b2.\b.3\b3.\b. T\bTe\bel\bln\bne\bet\bt l\blo\bog\bgi\bin\bns\bs.\b.
+
+ With telnet connections, the source callsign is not seen by DXSpider,
+ so you will be asked to login with your callsign. To telnet to
+ DXSpider, you would connect to a specific port. There is no standard
+ at the moment for a cluster telnet port but ask the sysop if you are
+ unsure.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ telnet gb7mbc 8000
+
+
+
+ All the above are possible ways of connecting to a DXSpider cluster.
+ You may have some or all of these available to you. There may be one
+ or two additional ways to connect dependant on the network local to
+ you. However I am sure you get the idea.
+
+
+ 2\b2.\b.4\b4.\b. L\bLo\bog\bgo\bou\but\bts\bs.\b.
+
+ Logging out can be done by simply issuing the standard B\bBY\bYE\bE command.
+
+ You could also send a disconnect if you are using AX25, or a C\bCL\bLO\bOS\bSE\bE
+ command if you are connected via telnet. If you do not log out
+ gracefully using one of the above commands, you may find you are
+ unable to get a full connect next time. This may also happen if a
+ netrom connection drops. You may get connected, but nothing else will
+ happen because the program thinks you are still connected and will not
+ let you connect twice under the same call. However you could
+ reconnect by adding a number to the end of your call, for example
+ G0YLM-2. This can be done by either altering your MYCALL setting in
+ the TNC or by altering your program configuration.
+
+
+
+ 3\b3.\b. S\bSe\bet\btt\bti\bin\bng\bg y\byo\bou\bur\br p\bpe\ber\brs\bso\bon\bna\bal\bl d\bde\bet\bta\bai\bil\bls\bs.\b.
+
+ Once logged in to the cluster, you should set your details so that
+ anybody who wishes to contact you can find out who and where you are.
+ There are four items to set, your name, qth, location and home node.
+ Setting these details also allows the use of the SHOW/HEADING and
+ SHOW/SUN commands from within the cluster. Unless you set your QTH
+ and location, these commands cannot function. Once you have set your
+ name, DXSpider will greet you with it next time you login. Your QTH
+ setting is where you live and it is a good idea to add your locator to
+ this as the location setting is converted to latitude and longitude
+ once inputted. You can actually set your location in
+ latitude/longitude or as a locator. Setting your home node will tell
+ the program where you wish mail to be sent to you.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ set/name Ian
+ set/qth Morecambe, Lancashire IO84NB
+ set/location 48 34 n 12 12 e
+ set/qra IO84NB
+ set/home gb7mbc
+
+
+
+ 4\b4.\b. G\bGe\bet\btt\bti\bin\bng\bg a\ban\bnd\bd p\bpo\bos\bst\bti\bin\bng\bg D\bDX\bX.\b.
+
+ When all is said and done, this is the main function of a DX cluster.
+ In its simplest form you can just connect to the node and you will
+ start to receive DX spots almost immediately! You can check on recent
+ postings in either a general manner or on a particular band or mode.
+ You can even check DX by callsign or a fragment of a callsign. Of
+ course, once you get the hang of things, it is expected that you start
+ posting some yourself! After all, there would be no clusters if
+ people did not post DX and you get the added thrill of the hunt!
+
+
+ 4\b4.\b.1\b1.\b. R\bRe\bec\bce\bei\biv\bvi\bin\bng\bg D\bDX\bX.\b.
+
+ As we have already said, it is possible just to connect to the cluster
+ and you will receive spots automatically. However, you may wish to
+ check on spots just posted. Maybe you wish to see if a particular
+ band is open or if a certain callsign is active, perhaps a DXpedition.
+ The command to do this is S\bSH\bHO\bOW\bW/\b/D\bDX\bX. Without any other arguments, this
+ command will output the last 10 spots posted. It is possible to look
+ at more than this, for example the last 20 or 50 spots, by adding the
+ number to the command. You can make it even more specific by adding a
+ band in either wavelength or frequency, and/or any additional
+ information such as QSL details.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ show/dx
+ show/dx 5
+ show/dx 20
+
+
+
+ will show the last 10, 5 and 20 spots received by the cluster
+ respectively.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs
+
+
+
+ show/dx on 20m
+ show/dx 10 on 20m
+ show/dx 20 on 20m
+
+
+
+ will show the last 5, 10 or 20 spots on 20 metres only.
+
+ It is also possible to check for certain callsigns, or fragments of
+ callsigns in the same way.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ show/dx g0vgs
+ show/dx 10 g0vgs
+
+
+
+ would show the last 5 or 10 dx spots containing the callsign g0vgs.
+
+
+ You can check for DX by offset and also by specifying a comment to
+ search for.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ show/dx 30-40
+ show/dx 14000-14033
+ show/dx iota
+
+
+
+ would show the spots that arrived between 30 and 40 spots ago and any
+ spots with the word _\bi_\bo_\bt_\ba in the comment field. The case of the
+ comment is not important.
+
+ Checking DX posted on a certain day is possible too. All you have to
+ do here is to specify how many days ago it was like this ...
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/dx day 30
+
+
+
+ It is of course possible to specify multiple arguments.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/dx 20 prefix 9a on vhf day 30
+
+
+
+ This would show the last 20 spots posted by or about calls with the
+ prefix 9a on vhf 30 days ago.
+
+ As you can see the S\bSH\bHO\bOW\bW/\b/D\bDX\bX command is very flexible, so if you are not
+ sure whether something will work or not, try it and see! More
+ information can be found in the Command Set section.
+
+
+
+ 4\b4.\b.2\b2.\b. P\bPo\bos\bst\bti\bin\bng\bg D\bDX\bX.\b.
+
+ To post DX you use the D\bDX\bX command. The syntax is shown below.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ dx (frequency) (callsign) (remarks)
+
+
+
+ Where frequency is in kilohertz and the callsign is the callsign of
+ the station you have worked or heard, (ie not your own callsign!).
+ The remarks section allows you to add information like the operators
+ name or perhaps a location. Actually DXSpider will allow the
+ frequency and callsign fields to be entered in any order.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ dx 14004 pa3ezl OP Aurelio 599
+
+
+
+ In fact, all the following will give the same result...
+
+
+
+ dx 14004 pa3ezl OP Aurelio 599
+ dx pa3ezl 14004 OP Aurelio 599
+ dx pa3ezl 14.004 OP Aurelio 599
+
+
+
+ This posting, or callout as it is known, will be forwarded to all
+ other connected stations both at the cluster you are connected to and
+ other active clusters in the network. The callout will also be sent
+ to you as proof of receipt.
+
+
+ 5\b5.\b. H\bHe\bea\bad\bdi\bin\bng\bgs\bs a\ban\bnd\bd p\bpr\bro\bop\bpa\bag\bga\bat\bti\bio\bon\bn
+
+ There are three commands in DXSpider to help you get the best DX
+ possible. These are S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN, S\bSH\bHO\bOW\bW/\b/M\bMO\bOO\bON\bN and S\bSH\bHO\bOW\bW/\b/H\bHE\bEA\bAD\bDI\bIN\bNG\bG. These
+ commands will only work for you if you have entered your personal
+ details. They use your entered location as a reference, so if you
+ have not entered it or have entered it incorrectly they will not
+ return the correct information.
+
+
+ 5\b5.\b.1\b1.\b. S\bSu\bun\bn
+
+ The S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN command can be used in three different ways. It can be
+ used to show sunrise and sunset times for your own station, a
+ particular callsign or a prefix.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/sun
+
+
+
+ The output from this would look something like this ..
+
+
+
+ sh/sun
+ Location Rise Set Azim Elev
+ G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
+
+
+
+ sh/sun 5b4
+
+
+
+ would look like this ...
+
+
+
+ sh/sun 5b4
+ Location Rise Set Azim Elev
+ 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
+
+
+
+ You can also specify multiple arguments like this ...
+
+
+
+ sh/sun gw4veq 5b4ab zs
+
+
+
+ and then the output would look like this ...
+
+
+
+ sh/sun gw4veq 5b4ab zs
+ Location Rise Set Azim Elev
+ GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9
+ 5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
+ ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
+ ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
+ ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
+
+
+
+ 5\b5.\b.2\b2.\b. M\bMo\boo\bon\bn
+
+ The S\bSH\bHO\bOW\bW/\b/M\bMO\bOO\bON\bN command works in the same way as the S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN command.
+ This program however, calculates the rise and set times of the moon
+ for a prefix or callsign, together with the current azimuth and
+ elevation of the sun at these locations.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/moon ea
+
+
+
+ The output from this command would look like this ..
+
+
+
+ sh/moon ea
+ Location Rise Set Azim Elev RGain dB
+ EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
+
+
+
+ You can see that the output is similar to the S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN command, with
+ slightly different fields.
+
+
+ 5\b5.\b.3\b3.\b. H\bHe\bea\bad\bdi\bin\bng\bg
+
+ The S\bSH\bHO\bOW\bW/\b/H\bHE\bEA\bAD\bDI\bIN\bNG\bG command works in the same way as the S\bSH\bHO\bOW\bW/\b/S\bSU\bUN\bN and
+ S\bSH\bHO\bOW\bW/\b/M\bMO\bOO\bON\bN commands but outputs beam headings for a specified callsign
+ or prefix. Reciprocal beam headings are also calculated.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be
+
+
+
+ show/heading zl
+
+
+
+ The output from this command would look like this ..
+
+
+
+ sh/heading zl
+ ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
+ ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
+ ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
+ ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
+
+
+
+ 6\b6.\b. A\bAn\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs.\b.
+
+ 6\b6.\b.1\b1.\b. M\bMa\bak\bki\bin\bng\bg a\ban\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs.\b.
+
+ Occasionally, you may wish to post something that does not fall into
+ the normal parameters for a DX callout. You may wish to tell
+ everybody connected that 10 FM is open for example, or ask if anyone
+ knows the QSL manager for a certain callsign etc. You can do this
+ using the A\bAN\bNN\bNO\bOU\bUN\bNC\bCE\bE command.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+ announce 10 FM is open in IO84NB to europe.
+
+
+
+ That would let everyone know locally that this was the case, however
+ it would not be forwarded to other nodes connected. To send
+ announcements to other connected nodes as well, you would use the F\bFU\bUL\bLL\bL
+ extension.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ announce full Anyone seen EA7WA today?
+
+
+
+ Be cautious in your use of announce full. There are many other tools
+ available to get the information you require and the judicious use of
+ this command is frowned upon as it creates a great deal of traffic
+ across the network.
+
+
+ 6\b6.\b.2\b2.\b. L\bLi\bis\bst\bti\bin\bng\bg a\ban\bnn\bno\bou\bun\bnc\bce\bem\bme\ben\bnt\bts\bs.\b.
+
+ You can list previous announcements in the standard format with the
+ S\bSH\bHO\bOW\bW command. As before you can list just the last 5 or as many as
+ you wish.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/announcements
+ show/announcements 10
+
+
+
+ 7\b7.\b. N\bNo\bod\bde\bes\bs a\ban\bnd\bd u\bus\bse\ber\brs\bs.\b.
+
+ You can check which nodes are connected in the network, who is logged
+ on locally, who is logged on at all the nodes or even just one node in
+ particular. This is handy if you wish to see whether a friend is
+ connected at the node they use. To see who is connected to the nodes,
+ the S\bSH\bHO\bOW\bW/\b/C\bCO\bON\bNF\bFI\bIG\bGU\bUR\bRA\bAT\bTI\bIO\bON\bN command is used.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/configuration
+ show/configuration/nodes
+ show/configuration (node_call)
+ show/configuration (prefix)
+
+
+
+ The first of our three examples would output something like this,
+
+
+
+ sh/c
+ Node Callsigns
+ EI5TCR (7 users)
+ GB7ADX
+ GB7BAA G4FPV G8TIC
+ GB7BIG (GD0TEP) GD3UMW
+ GB7BPQ (G0INA) G0RCI G3AKU G3OCA
+ (GB7CDX) G3JNB G4ALR
+ GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
+ G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
+ ON7WP
+ GB7DXA G0RDI G8SJP
+ GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
+ G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
+ GB7DXE G1NNB
+ (GB7DXG) GU6EFB GU7DHI
+ GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
+ G4XQY G7GAN
+ GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
+ M0BCT M1EMF
+
+
+
+ You will notice that EI5TCR is showing only that it has 7 users and
+ not giving the actual callsigns. This means that this node is on a
+ limited protocol of some kind, probably because of a contest situation
+ where slow radio links can block up and fail if too much information
+ is sent between nodes.
+
+ The second example would just show the nodes connected in the network,
+ like this,
+
+
+
+ sh/c/n
+ Node Callsigns
+ GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
+ GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
+ GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
+ GB7YDX KL7G N2TLY (ON0DXK)
+ GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
+ GB7MBC
+ PA4AB-14 PA4AB-14
+ PI4TUE-8 PI4TUE-8
+
+
+
+ If we insert the node_call pi4tue-8 into the third example, then this
+ would be the output,
+
+
+
+ Node Callsigns
+ PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
+ F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
+ ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
+ PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
+ YT1XX
+
+
+
+ As you can see, only the users of the requested node are shown.
+
+ You can also use a prefix to show only a group of nodes. For example
+ you may only wish to see who is connected to the nodes in the UK. To
+ do this simply use a prefix like this ...
+
+
+ show/configuration gb7
+
+
+
+ To show the locally connected users, the S\bSH\bHO\bOW\bW/\b/U\bUS\bSE\bER\bRS\bS command is used
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ show/users
+
+
+
+ The output of this command would look like this,
+
+
+
+ Callsigns connected to GB7MBC
+ G0JHC G0NEI G0VGS G0VGS-2 G0YLM
+ G3JAG G3OWO G3UEU
+
+
+
+ 8\b8.\b. T\bTa\bal\blk\bk m\bmo\bod\bde\be.\b.
+
+ You can send a single comment or start a dedicated talk session to
+ another user by using the T\bTA\bAL\bLK\bK command.
+
+
+ Talk mode is used to send a one line comment or greeting to a specific
+ user connected either at your node or another in the network. You can
+ also enter into a dedicated talk session with another user. Talks
+ will be automatically forwarded to other nodes if the station you are
+ talking to is not connected locally. You can find out who is
+ connected by using the S\bSH\bHO\bOW\bW/\b/C\bCO\bON\bNF\bFI\bIG\bGU\bUR\bRA\bAT\bTI\bIO\bON\bN command, (described
+ earlier).
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ talk g0rdi Having a good day Iain?
+
+
+
+ This example would send the line "Having a good day Iain?" to the user
+ g0rdi but would leave you in normal mode.
+
+
+
+ talk g0rdi
+ Entering Talkmode, /EX to end, /<cmd> to run a command
+ Talk (G0RDI)>
+
+
+ As you can see, you can still run commands whilst in talk mode.
+ Simply prefix the command with a / like /sh/dx and you will get the
+ expected output. If the user is connected to another node, you may
+ have to use a slightly extended version of the T\bTA\bAL\bLK\bK command.
+
+
+
+ talk g0rdi > gb7djk
+
+
+
+ To exit talk mode, you issue the command /\b/e\bex\bx.
+
+ Whilst in talk mode you will still receive DX spots. This means that
+ you can chat to a friend whilst working DX.
+
+
+ 9\b9.\b. M\bMa\bai\bil\bl.\b.
+
+ You can send and receive both personal mail and bulletins with
+ DXSpider quite easily.
+
+
+ 9\b9.\b.1\b1.\b. T\bTh\bhe\be "\b"d\bdi\bir\bre\bec\bct\bto\bor\bry\by"\b" c\bco\bom\bmm\bma\ban\bnd\bd.\b.
+
+ To list mail you would use the D\bDI\bIR\bRE\bEC\bCT\bTO\bOR\bRY\bY command. On its own, this
+ command will output the last ten messages received by the node, either
+ to or from yourself or bulletins such as "DX" and "ALL". As with
+ other commands you can display more by specifying a number with the
+ command. You should be aware that Spider will accept these commands
+ by separating with either a slash or a space, so _\bd_\bi_\br _\bn_\be_\bw and _\bd_\bi_\br_\b/_\bn_\be_\bw
+ work in the same way.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ directory
+ directory/20
+ directory 20
+
+
+
+ Of course most of the time you will only want to list new mail sent to
+ you personally since your last login. However you might also like to
+ check for general mail received by the node. In fact if there is new
+ mail for you, the cluster will tell you when you login. You will also
+ be informed if new mail arrives for you during the time you are logged
+ in. Mail is not only sent to callsigns though. Mail can also be sent
+ to subjects like "all" or "local" or "dx" etc. You can treat these
+ bulletins in the same way as personal mail with the directory command.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\bes\bs:\b:
+
+
+
+ directory/new
+ directory/own
+ directory/own/10
+ directory/all
+ directory/from <call>
+
+
+
+ The last option will only show mail from a callsign if it was sent to
+ you personally or was sent as a bulletin. There are some additional
+ commands and these can be found in the DXSpider Command Reference
+ section.
+
+
+ 9\b9.\b.2\b2.\b. R\bRe\bea\bad\bdi\bin\bng\bg m\bma\bai\bil\bl.\b.
+
+ The output of the D\bDI\bIR\bRE\bEC\bCT\bTO\bOR\bRY\bY command could be something like this.
+
+
+
+ dir
+ 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
+ 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
+ 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
+ 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
+ 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
+ 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
+ 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
+ 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
+ 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
+ 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
+ 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
+
+
+
+ The first column is the actual message number. If the message is a
+ personal one to you, you will see a letter 'p' after this number. If
+ the message has been read, there will be a '-' between the message
+ number and the 'p'. This only works for personal messages. The next
+ column shows the file size of the message. The third column shows the
+ address the message was sent to and the next column shows who sent it.
+ The rest is fairly self-explanatory.
+
+ Reading a message is as simple as typing read, followed by the message
+ number that you wish to read.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ read 25
+
+
+
+ will read message number 25. However the mail will be displayed in
+ it's entirety unless you specify a page length. You can set your page
+ length to any number you like and when the message reaches that number
+ of lines you will get a prompt giving you options.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ set/page 20
+
+
+
+ 9\b9.\b.3\b3.\b. S\bSe\ben\bnd\bdi\bin\bng\bg m\bma\bai\bil\bl.\b.
+
+ Sending mail is done in the time honoured way. First you specify a
+ recipient for the message, then you will be prompted for a subject.
+ Once you have done this you will be asked to type your message.
+ Please remember that there is no automatic word wrap, so unless you
+ are using a client that wraps lines automatically, remember to hit
+ return at the end of each line.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ send m0azm
+ Enter Subject (30 characters):
+ See you Thursday
+ Enter Message /EX to send or /ABORT to exit
+ Hi Ian,
+ Just a quick note to say that I can make Thursday after all. The
+ appointment I had has cancelled so we are go!
+ Cheers
+ Ian
+
+
+
+ At this point you can either hit return and enter /ex to send the
+ message or use /abort at any time to abort it. You can now display
+ the message in the normal way. There are several send options and
+ these are listed in the Command Set section. These include sending
+ mail to several recipients and asking for a return receipt.
+
+
+
+ 9\b9.\b.4\b4.\b. R\bRe\bep\bpl\bly\byi\bin\bng\bg t\bto\bo m\bma\bai\bil\bl.\b.
+
+ If mail is addressed to you or to a bulletin address, you can use the
+ R\bRE\bEP\bPL\bLY\bY command to reply to it. Using this command, the subject will be
+ automatically set for you as "Re: subject", whatever the subject was.
+
+ E\bEx\bxa\bam\bmp\bpl\ble\be:\b:
+
+
+
+ reply 2500
+
+
+
+ 9\b9.\b.5\b5.\b. D\bDe\bel\ble\bet\bti\bin\bng\bg m\bma\bai\bil\bl
+
+ To delete a message, you use the _\bd_\be_\bl_\be_\bt_\be command. You can only delete
+ messages sent to or received by yourself. Bulletins are dealt with
+ automatically or by the sysop.
+
+
+ 1\b10\b0.\b. F\bFi\bil\blt\bte\ber\bri\bin\bng\bg (\b(F\bFr\bro\bom\bm v\bve\ber\brs\bsi\bio\bon\bn 1\b1.\b.4\b45\b5)\b)
+
+ 1\b10\b0.\b.1\b1.\b. G\bGe\ben\bne\ber\bra\bal\bl f\bfi\bil\blt\bte\ber\br r\bru\bul\ble\bes\bs
+
+ Upto v1.44 it was not possible for the user to set their own filters.
+ From v1.45 though that has all changed. It is now possible to set
+ filters for just about anything you wish. If you have just updated
+ from an older version of DXSpider you will need to update your new
+ filters. You do not need to do anything with your old filters, they
+ will be renamed as you update.
+
+
+ There are 3 basic commands involved in setting and manipulating
+ filters. These are _\ba_\bc_\bc_\be_\bp_\bt, _\br_\be_\bj_\be_\bc_\bt and _\bc_\bl_\be_\ba_\br. First we will look
+ generally at filtering. There are a number of things you can filter in
+ the DXSpider system. They all use the same general mechanism.
+
+
+ In general terms you can create a 'reject' or an 'accept' filter which
+ can have up to 10 lines in it. You do this using, for example ...
+
+
+
+ accept/spots .....
+ reject/spots .....
+
+
+
+ where ..... are the specific commands for that type of filter. There
+ are filters for spots, wwv, announce, wcy and (for sysops) connects.
+ See each different accept or reject command reference for more
+ details.
+
+ There is also a command to clear out one or more lines in a filter.
+ They are ...
+
+
+
+ clear/spots 1
+ clear/spots all
+
+
+
+ There is clear/xxxx command for each type of filter.
+
+
+ and you can check that your filters have worked by the command ...
+
+
+
+ show/filter
+
+
+
+ For now we are going to use spots for the examples, but you can apply
+ the same principles to all types of filter.
+
+
+ 1\b10\b0.\b.2\b2.\b. T\bTy\byp\bpe\bes\bs o\bof\bf f\bfi\bil\blt\bte\ber\br
+
+ There are two main types of filter, _\ba_\bc_\bc_\be_\bp_\bt or _\br_\be_\bj_\be_\bc_\bt. You can use
+ either to achieve the result you want dependent on your own preference
+ and which is more simple to do. It is pointless writing 8 lines of
+ reject filters when 1 accept filter would do the same thing! Each
+ filter has 10 lines (of any length) which are tried in order. If a
+ line matches then the action you have specified is taken (ie reject
+ means ignore it and accept means take it)
+
+
+ If you specify reject filters, then any lines that arrive that match
+ the filter will be dumped but all else will be accepted. If you use
+ an accept filter, then ONLY the lines in the filter will be accepted
+ and all else will be dumped. For example if you have a single line
+ _\ba_\bc_\bc_\be_\bp_\bt filter ...
+
+
+
+ accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+ then you will _\bO_\bN_\bL_\bY get VHF spots _\bf_\br_\bo_\bm or _\bt_\bo CQ zones 14, 15 and 16.
+
+
+ If you set a reject filter like this ...
+
+
+
+ reject/spots on hf/cw
+
+
+
+ Then you will get everything _\bE_\bX_\bC_\bE_\bP_\bT HF CW spots. You could make this
+ single filter even more flexible. For example, if you are interested
+ in IOTA and will work it even on CW even though normally you are not
+ interested in CW, then you could say ...
+
+
+
+ reject/spots on hf/cw and not info iota
+
+
+
+ But in that case you might only be interested in iota and say:-
+
+
+
+ accept/spots not on hf/cw or info iota
+
+
+
+ which achieves exactly the same thing. You should choose one or the
+ other until you are comfortable with the way it works. You can mix
+ them if you wish (actually you can have an accept AND a reject on the
+ same line) but don't attempt this until you are sure you know what you
+ are doing!
+
+
+ You can arrange your filter lines into logical units, either for your
+ own understanding or simply convenience. Here is an example ...
+
+
+
+ reject/spots 1 on hf/cw
+ reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+ What this does is to ignore all HF CW spots and also rejects any spots
+ on VHF which don't either originate or spot someone in Europe.
+ This is an example where you would use a line number (1 and 2 in this
+ case), if you leave the digit out, the system assumes '1'. Digits
+ '0'-'9' are available. This make it easier to see just what filters
+ you have set. It also makes it more simple to remove individual
+ filters, during a contest for example.
+
+
+ You will notice in the above example that the second line has
+ brackets. Look at the line logically. You can see there are 2
+ separate sections to it. We are saying reject spots that are VHF or
+ above _\bA_\bP_\bA_\bR_\bT from those in zones 14, 15 and 16 (either spotted there or
+ originated there). If you did not have the brackets to separate the 2
+ sections, then Spider would read it logically from the front and see a
+ different expression entirely ...
+
+
+
+ (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+
+
+
+ The simple way to remember this is, if you use OR - use brackets.
+ Whilst we are here CASE is not important. 'And BY_Zone' is just the
+ same as 'and by_zone'.
+
+ As mentioned earlier, setting several filters can be more flexible
+ than simply setting one complex one. Doing it in this way means that
+ if you want to alter your filter you can just redefine or remove one
+ or more lines of it or one line. For example ...
+
+
+
+ reject/spots 1 on hf/ssb
+
+
+
+ would redefine our earlier example, or
+
+
+
+ clear/spots 1
+
+
+
+ To remove all the filter lines in the spot filter ...
+
+
+
+ clear/spots all
+
+
+
+ 1\b10\b0.\b.3\b3.\b. F\bFi\bil\blt\bte\ber\br o\bop\bpt\bti\bio\bon\bns\bs
+
+ You can filter in several different ways. The options are listed in
+ the various helpfiles for accept, reject and filter.
+
+
+
+ 1\b10\b0.\b.4\b4.\b. A\bAd\bdv\bva\ban\bnc\bce\bed\bd f\bfi\bil\blt\bte\ber\bri\bin\bng\bg
+
+ Once you are happy with the results you get, you may like to
+ experiment.
+
+
+ The previous example that filters hf/cw spots and accepts vhf/uhf
+ spots from EU can be written with a mixed filter, for example ...
+
+
+
+ rej/spot on hf/cw
+ acc/spot on 0/30000
+ acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+ Note that the first filter has not been specified with a number. This
+ will automatically be assumed to be number 1. In this case, we have
+ said _\br_\be_\bj_\be_\bc_\bt _\ba_\bl_\bl _\bH_\bF _\bs_\bp_\bo_\bt_\bs _\bi_\bn _\bt_\bh_\be _\bC_\bW _\bs_\be_\bc_\bt_\bi_\bo_\bn _\bo_\bf _\bt_\bh_\be _\bb_\ba_\bn_\bd_\bs _\bb_\bu_\bt _\ba_\bc_\bc_\be_\bp_\bt _\ba_\bl_\bl
+ _\bo_\bt_\bh_\be_\br_\bs _\ba_\bt _\bH_\bF_\b. _\bA_\bl_\bs_\bo _\ba_\bc_\bc_\be_\bp_\bt _\ba_\bn_\by_\bt_\bh_\bi_\bn_\bg _\bi_\bn _\bV_\bH_\bF _\ba_\bn_\bd _\ba_\bb_\bo_\bv_\be _\bs_\bp_\bo_\bt_\bt_\be_\bd _\bi_\bn _\bo_\br _\bb_\by
+ _\bo_\bp_\be_\br_\ba_\bt_\bo_\br_\bs _\bi_\bn _\bt_\bh_\be _\bz_\bo_\bn_\be_\bs _\b1_\b4_\b, _\b1_\b5 _\ba_\bn_\bd _\b1_\b6. Each filter slot actually has a
+ 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
+ the accept slot.
+
+
+ It was mentioned earlier that after a reject test that doesn't match,
+ the default for following tests is 'accept', the reverse is true for
+ 'accept'. In the example what happens is that the reject is executed
+ first, any non hf/cw spot is passed to the accept line, which lets
+ through everything else on HF. The next filter line lets through just
+ VHF/UHF spots from EU.
+
+
+
+ 1\b11\b1.\b. H\bHi\bin\bnt\bts\bs,\b, t\bti\bip\bps\bs a\ban\bnd\bd c\bco\bom\bmm\bmo\bon\bn q\bqu\bue\bes\bst\bti\bio\bon\bns\bs.\b.
+
+ Q\bQ.\b.These commands seem very long! Can I shorten them?
+
+ A\bA.\b.Of course you can and the usual abbreviations work. If you are
+ unsure, try it.
+
+ Q\bQ.\b.I am not sure if this command is correct. Can I cause any harm if I
+ try it?
+
+ A\bA.\b.Do not be afraid to try a command to see if it will work, at the
+ worst you will get an error message. If you require any help on a
+ command, just type help followed by the command you want help on.
+ Look at the "DXSpider Command Reference" section to see what help can
+ be found.
+
+ Q\bQ.\b.How should I use the announce command?
+
+ A\bA.\b.With respect. Use the command by all means, but please only use the
+ "full" extension if absolutely necessary. It can create a LOT of
+ messages passing between clusters.
+
+ Q\bQ.\b.I like to be working in the shack while logged into the cluster but
+ I can't be looking at the screen all the time. How can I be alerted
+ when anything happens?
+
+ A\bA.\b.Use the S\bSE\bET\bT/\b/B\bBE\bEE\bEP\bP command. You can find information on this in the
+ "DXSpider Command Reference" section.
+
+
+ Q\bQ.\b.I got disconnected from the cluster and now I can't log back in
+ again. What is wrong?
+
+ A\bA.\b.Probably the cluster thinks you are still logged on and will not let
+ you reconnect using the same call to prevent loops. Try logging on
+ again adding an ssid to your callsign as DXSpider treats G0YLM and
+ G0YLM-1 as different users.
+
+ Q\bQ.\b.How do I know if I have got the latest version of this user manual?
+
+ A\bA.\b.The latest and greatest will always be on the Website. It will also
+ be included with every release of DXSpider. As always, if unsure, ask
+ your sysop what version number is the latest.
+
+
+ 1\b12\b2.\b. T\bTh\bhe\be D\bDX\bXS\bSp\bpi\bid\bde\ber\br c\bco\bom\bmm\bma\ban\bnd\bd r\bre\bef\bfe\ber\bre\ben\bnc\bce\be
+
+ 1\b12\b2.\b.1\b1.\b. a\bac\bcc\bce\bep\bpt\bt
+
+ a\bac\bcc\bce\bep\bpt\bt Set a filter to accept something
+
+
+ Create a filter to accept something
+
+ There are 2 types of filter, accept and reject. See HELP FILTERING
+ for more info.
+
+ 1
\b12
\b2.
\b.2
\b2.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b>
+
+ a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set an 'accept' filter line for
+ announce
+
+
+ Create an 'accept this announce' line for a filter.
+
+ An accept filter line means that if the announce matches this filter
+ it is passed onto the user. See HELP FILTERING for more info. Please
+ read this to understand how filters work - it will save a lot of grief
+ later on.
+
+ You can use any of the following things in this line:-
+
+
+
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ origin_state <states> eg: VA,NH,RI,NH
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ by_state <states>
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+
+
+
+ some examples:-
+
+
+
+ acc/ann dest 6MUK
+ acc/ann 2 by_zone 14,15,16
+ (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
+
+
+
+ or
+
+
+ acc/ann by G,M,2
+
+
+
+ for american states
+
+
+
+ acc/ann by_state va,nh,ri,nh
+
+
+
+ You can use the tag 'all' to accept everything eg:
+
+
+
+ acc/ann all
+
+
+
+ but this probably for advanced users...
+
+ 1
\b12
\b2.
\b.3
\b3.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b>
+
+ a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set an 'accept' filter line for spots
+
+
+ Create an 'accept this spot' line for a filter.
+
+ An accept filter line means that if the spot matches this filter it is
+ passed onto the user. See HELP FILTERING for more info. Please read
+ this to understand how filters work - it will save a lot of grief
+ later on.
+
+ You can use any of the following things in this line:-
+
+
+
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <prefixes or numbers> or: G,GM,GW
+ call_zone <prefixes or numbers>
+ call_state <states> eg: VA,NH,RI,ME
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ by_state <states> eg: VA,NH,RI,ME
+ origin <prefixes>
+ channel <prefixes>
+
+
+
+ For frequencies, you can use any of the band names defined in
+ SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+ thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+ this is more efficient than saying simply: freq HF (but don't get too
+ hung up about that)
+
+ some examples:-
+
+
+
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+ You can use the tag 'all' to accept everything, eg:
+
+
+
+ acc/spot 3 all
+
+
+
+ for US states
+
+
+
+ acc/spots by_state VA,NH,RI,MA,ME
+
+
+
+ but this probably for advanced users...
+
+ 1
\b12
\b2.
\b.4
\b4.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bwc
\bcy
\by [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b>
+
+ a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bwc
\bcy
\by [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> set an 'accept' WCY filter
+
+
+ It is unlikely that you will want to do this, but if you do then you
+ can filter on the following fields:-
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ channel <prefixes>
+
+
+
+ There are no examples because WCY Broadcasts only come from one place
+ and you either want them or not (see UNSET/WCY if you don't want
+ them).
+
+ This command is really provided for future use.
+
+ See HELP FILTER for information.
+
+ 1
\b12
\b2.
\b.5
\b5.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b>
+
+ a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> set an 'accept' WWV filter
+
+
+ It is unlikely that you will want to do this, but if you do then you
+ can filter on the following fields:-
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ channel <prefixes>
+
+
+
+ for example
+
+
+
+ accept/wwv by_zone 4
+
+
+
+ is probably the only useful thing to do (which will only show WWV
+ broadcasts by stations in the US).
+
+ See HELP FILTER for information.
+
+ 1\b12\b2.\b.6\b6.\b. a\ban\bnn\bno\bou\bun\bnc\bce\be <\b<t\bte\bex\bxt\bt>\b>
+
+ a\ban\bnn\bno\bou\bun\bnc\bce\be <\b<t\bte\bex\bxt\bt>\b> Send an announcement to LOCAL users only
+
+
+ <text> is the text of the announcement you wish to broadcast
+
+
+ 1\b12\b2.\b.7\b7.\b. a\ban\bnn\bno\bou\bun\bnc\bce\be f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b>
+
+ a\ban\bnn\bno\bou\bun\bnc\bce\be f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b> Send an announcement cluster wide
+
+
+ This will send your announcement cluster wide
+
+ 1\b12\b2.\b.8\b8.\b. a\bap\bpr\bro\bop\bpo\bos\bs <\b<s\bst\btr\bri\bin\bng\bg>\b>
+
+ a\bap\bpr\bro\bop\bpo\bos\bs <\b<s\bst\btr\bri\bin\bng\bg>\b> Search help database for <string>
+
+
+ Search the help database for <string> (it isn't case sensitive), and
+ print the names of all the commands that may be relevant.
+
+ 1\b12\b2.\b.9\b9.\b. b\bbl\bla\ban\bnk\bk [\b[<\b<s\bst\btr\bri\bin\bng\bg>\b>]\b] [\b[<\b<n\bnn\bn>\b>]\b]
+
+ b\bbl\bla\ban\bnk\bk [\b[<\b<s\bst\btr\bri\bin\bng\bg>\b>]\b] [\b[<\b<n\bnn\bn>\b>]\b] Print nn (default 1) blank lines (or strings)
+
+
+ In its basic form this command prints one or more blank lines. However
+ if you pass it a string it will replicate the string for the width of
+ the screen (default 80) and then print that one or more times, so:
+
+
+
+ blank 2
+
+
+
+ prints two blank lines
+
+
+
+ blank -
+
+
+
+ prints a row of - characters once.
+
+
+
+ blank abc
+
+
+
+ prints 'abcabcabcabcabcabc....'
+
+ This is really only of any use in a script file and you can print a
+ maximum of 9 lines.
+
+ 1\b12\b2.\b.1\b10\b0.\b. b\bby\bye\be
+
+ b\bby\bye\be Exit from the cluster
+
+
+ This will disconnect you from the cluster
+
+ 1\b12\b2.\b.1\b11\b1.\b. c\bcl\ble\bea\bar\br/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be [\b[1\b1|\b|a\bal\bll\bl]\b]
+
+ c\bcl\ble\bea\bar\br/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be [\b[1\b1|\b|a\bal\bll\bl]\b] Clear a announce filter line
+
+
+ This command allows you to clear (remove) a line in a annouce filter
+ or to remove the whole filter.
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+ 1\b12\b2.\b.1\b12\b2.\b. c\bcl\ble\bea\bar\br/\b/r\bro\bou\but\bte\be [\b[1\b1|\b|a\bal\bll\bl]\b]
+
+ c\bcl\ble\bea\bar\br/\b/r\bro\bou\but\bte\be [\b[1\b1|\b|a\bal\bll\bl]\b] Clear a route filter line
+
+
+ This command allows you to clear (remove) a line in a route filter or
+ to remove the whole filter.
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+ 1\b12\b2.\b.1\b13\b3.\b. c\bcl\ble\bea\bar\br/\b/s\bsp\bpo\bot\bts\bs [\b[0\b0-\b-9\b9|\b|a\bal\bll\bl]\b]
+
+ c\bcl\ble\bea\bar\br/\b/s\bsp\bpo\bot\bts\bs [\b[0\b0-\b-9\b9|\b|a\bal\bll\bl]\b] Clear a spot filter line
+
+
+ This command allows you to clear (remove) a line in a spot filter or
+ to remove the whole filter.
+
+ If you have a filter:-
+
+
+
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+ and you say:-
+
+
+
+ clear/spot 1
+
+
+
+ you will be left with:-
+
+
+
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+ If you do:
+
+
+
+ clear/spot all
+
+
+
+ the filter will be completely removed.
+
+ 1\b12\b2.\b.1\b14\b4.\b. c\bcl\ble\bea\bar\br/\b/w\bwc\bcy\by [\b[1\b1|\b|a\bal\bll\bl]\b]
+
+ c\bcl\ble\bea\bar\br/\b/w\bwc\bcy\by [\b[1\b1|\b|a\bal\bll\bl]\b] Clear a WCY filter line
+
+ This command allows you to clear (remove) a line in a WCY filter or to
+ remove the whole filter.
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+ 1\b12\b2.\b.1\b15\b5.\b. c\bcl\ble\bea\bar\br/\b/w\bww\bwv\bv [\b[1\b1|\b|a\bal\bll\bl]\b]
+
+ c\bcl\ble\bea\bar\br/\b/w\bww\bwv\bv [\b[1\b1|\b|a\bal\bll\bl]\b] Clear a WWV filter line
+
+
+ This command allows you to clear (remove) a line in a WWV filter or to
+ remove the whole filter.
+
+ see CLEAR/SPOTS for a more detailed explanation.
+
+ 1\b12\b2.\b.1\b16\b6.\b. d\bdb\bba\bav\bva\bai\bil\bl
+
+ d\bdb\bba\bav\bva\bai\bil\bl Show a list of all the Databases in the system
+
+
+ Title says it all really, this command lists all the databases defined
+ in the system. It is also aliased to SHOW/COMMAND.
+
+ 1\b12\b2.\b.1\b17\b7.\b. d\bdb\bbs\bsh\bho\bow\bw <\b<d\bdb\bbn\bna\bam\bme\be>\b> <\b<k\bke\bey\by>\b>
+
+ d\bdb\bbs\bsh\bho\bow\bw <\b<d\bdb\bbn\bna\bam\bme\be>\b> <\b<k\bke\bey\by>\b> Display an entry, if it exists, in a database
+
+
+ This is the generic user interface to the database to the database
+ system. It is expected that the sysop will add an entry to the local
+ Aliases file so that users can use the more familiar AK1A style of
+ enquiry such as:
+
+
+
+ SH/BUCK G1TLH
+
+
+
+ but if he hasn't and the database really does exist (use DBAVAIL or
+ SHOW/COMMAND to find out) you can do the same thing with:
+
+
+
+ DBSHOW buck G1TLH
+
+
+
+ 1\b12\b2.\b.1\b18\b8.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by
+
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by List messages
+
+
+
+ 1\b12\b2.\b.1\b19\b9.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by <\b<f\bfr\bro\bom\bm>\b>-\b-<\b<t\bto\bo>\b>
+
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by <\b<f\bfr\bro\bom\bm>\b>-\b-<\b<t\bto\bo>\b> List messages <from> message <to> message
+
+
+ List the messages in the messages directory.
+
+ If there is a 'p' one space after the message number then it is a
+ personal message. If there is a '-' between the message number and the
+ You can use shell escape characters such as '*' and '?' in the <call>
+ fields.
+
+ You can combine some of the various directory commands together eg:-
+
+
+
+ DIR TO G1TLH 5
+
+
+
+ or
+
+
+ DIR SUBJECT IOTA 200-250
+
+
+
+ You can abbreviate all the commands to one letter and use ak1a
+ syntax:-
+
+
+
+ DIR/T G1* 10
+ DIR/S QSL 10-100 5
+
+
+
+ 1\b12\b2.\b.2\b20\b0.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by <\b<n\bnn\bn>\b>
+
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by <\b<n\bnn\bn>\b> List last <nn> messages
+
+
+
+ 1\b12\b2.\b.2\b21\b1.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by a\bal\bll\bl
+
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by a\bal\bll\bl List all messages
+
+
+
+ 1\b12\b2.\b.2\b22\b2.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by f\bfr\bro\bom\bm <\b<c\bca\bal\bll\bl>\b>
+
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by f\bfr\bro\bom\bm <\b<c\bca\bal\bll\bl>\b> List all messages from <call>
+
+
+
+ 1\b12\b2.\b.2\b23\b3.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by n\bne\bew\bw
+
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by n\bne\bew\bw List all new messages
+
+
+
+ 1\b12\b2.\b.2\b24\b4.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by o\bow\bwn\bn
+
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by o\bow\bwn\bn List your own messages
+
+
+
+ 1\b12\b2.\b.2\b25\b5.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by s\bsu\bub\bbj\bje\bec\bct\bt <\b<s\bst\btr\bri\bin\bng\bg>\b>
+
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by s\bsu\bub\bbj\bje\bec\bct\bt <\b<s\bst\btr\bri\bin\bng\bg>\b> List all messages with <string> in subject
+
+ 1\b12\b2.\b.2\b26\b6.\b. d\bdi\bir\bre\bec\bct\bto\bor\bry\by t\bto\bo <\b<c\bca\bal\bll\bl>\b>
+
+ d\bdi\bir\bre\bec\bct\bto\bor\bry\by t\bto\bo <\b<c\bca\bal\bll\bl>\b> List all messages to <call>
+
+
+
+ 1\b12\b2.\b.2\b27\b7.\b. d\bdx\bx [\b[b\bby\by <\b<c\bca\bal\bll\bl>\b>]\b] <\b<f\bfr\bre\beq\bq>\b> <\b<c\bca\bal\bll\bl>\b> <\b<r\bre\bem\bma\bar\brk\bks\bs>\b>
+
+ d\bdx\bx [\b[b\bby\by <\b<c\bca\bal\bll\bl>\b>]\b] <\b<f\bfr\bre\beq\bq>\b> <\b<c\bca\bal\bll\bl>\b> <\b<r\bre\bem\bma\bar\brk\bks\bs>\b> Send a DX spot
+
+
+ This is how you send a DX Spot to other users. You can, in fact, now
+ enter the <freq> and the <call> either way round.
+
+
+
+ DX FR0G 144.600
+ DX 144.600 FR0G
+ DX 144600 FR0G
+
+
+
+ will all give the same result. You can add some remarks to the end of
+ the command and they will be added to the spot.
+
+
+
+ DX FR0G 144600 this is a test
+
+
+
+ You can credit someone else by saying:-
+
+
+
+ DX by G1TLH FR0G 144.600 he isn't on the cluster
+
+
+
+ The <freq> is compared against the available bands set up in the
+ cluster. See SHOW/BANDS for more information.
+
+ 1\b12\b2.\b.2\b28\b8.\b. e\bec\bch\bho\bo <\b<l\bli\bin\bne\be>\b>
+
+ e\bec\bch\bho\bo <\b<l\bli\bin\bne\be>\b> Echo the line to the output
+
+
+ This command is useful in scripts and so forth for printing the line
+ that you give to the command to the output. You can use this in
+ user_default scripts and the SAVE command for titling and so forth
+
+ The script will interpret certain standard "escape" sequences as
+ follows:-
+
+
+
+ \t - becomes a TAB character (0x09 in ascii)
+ \a - becomes a BEEP character (0x07 in ascii)
+ \n - prints a new line
+
+
+
+ So the following example:-
+
+
+
+ echo GB7DJK is a dxcluster
+
+
+
+ produces:-
+
+
+
+ GB7DJK is a dxcluster
+
+
+
+ on the output. You don't need a \n on the end of the line you want to
+ send.
+
+ A more complex example:-
+
+
+
+ echo GB7DJK\n\tg1tlh\tDirk\n\tg3xvf\tRichard
+
+
+
+ produces:-
+
+
+
+ GB7DJK
+ g1tlh Dirk
+ g3xvf Richard
+
+
+
+ on the output.
+
+
+ 1\b12\b2.\b.2\b29\b9.\b. f\bfi\bil\blt\bte\ber\bri\bin\bng\bg.\b..\b..\b.
+
+ f\bfi\bil\blt\bte\ber\bri\bin\bng\bg.\b..\b..\b. Filtering things in DXSpider
+
+
+ There are a number of things you can filter in the DXSpider system.
+ They all use the same general mechanism.
+
+ In general terms you can create a 'reject' or an 'accept' filter which
+ can have up to 10 lines in it. You do this using, for example:-
+
+
+
+ accept/spots .....
+ reject/spots .....
+
+
+
+ where ..... are the specific commands for that type of filter. There
+ are filters for spots, wwv, announce, wcy and (for sysops) connects.
+ See each different accept or reject command reference for more
+ details.
+
+ There is also a command to clear out one or more lines in a filter and
+ one to show you what you have set. They are:-
+
+
+
+ clear/spots 1
+ clear/spots all
+
+
+
+ and
+
+
+
+ show/filter
+
+
+
+ There is clear/xxxx command for each type of filter.
+
+ For now we are going to use spots for the examples, but you can apply
+ the principles to all types of filter.
+
+ There are two main types of filter 'accept' or 'reject'; which you use
+ depends entirely on how you look at the world and what is least
+ writing to achieve what you want. Each filter has 10 lines (of any
+ length) which are tried in order. If a line matches then the action
+ you have specified is taken (ie reject means ignore it and accept
+ means gimme it).
+
+ The important thing to remember is that if you specify a 'reject'
+ filter (all the lines in it say 'reject/spots' (for instance)) then if
+ a spot comes in that doesn't match any of the lines then you will get
+ it BUT if you specify an 'accept' filter then any spots that don't
+ match are dumped. For example if I have a one line accept filter:-
+
+
+
+ accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+ then automatically you will ONLY get VHF spots from or to CQ zones 14
+ 15 and 16. If you set a reject filter like:
+
+
+
+ reject/spots on hf/cw
+
+
+
+ Then you will get everything EXCEPT HF CW spots, If you am interested
+ in IOTA and will work it even on CW then you could say:-
+
+
+
+ reject/spots on hf/cw and not info iota
+
+
+
+ But in that case you might only be interested in iota and say:-
+
+
+
+ accept/spots not on hf/cw or info iota
+
+
+
+ which is exactly the same. You should choose one or the other until
+ you are confortable with the way it works. Yes, you can mix them
+ (actually you can have an accept AND a reject on the same line) but
+ don't try this at home until you can analyse the results that you get
+ without ringing up the sysop for help.
+
+ Another useful addition now is filtering by US state
+
+
+
+ accept/spots by_state VA,NH,RI,ME
+
+
+
+ You can arrange your filter lines into logical units, either for your
+ own understanding or simply convenience. I have one set frequently:-
+
+
+
+ reject/spots 1 on hf/cw
+ reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+ What this does is to ignore all HF CW spots (being a class B I can't
+ read any CW and couldn't possibly be interested in HF :-) and also
+ rejects any spots on VHF which don't either originate or spot someone
+ in Europe.
+
+ This is an exmaple where you would use the line number (1 and 2 in
+ this case), if you leave the digit out, the system assumes '1'. Digits
+
+ You can leave the word 'and' out if you want, it is implied. You can
+ use any number of brackets to make the 'expression' as you want it.
+ There are things called precedence rules working here which mean that
+ you will NEED brackets in a situation like line 2 because, without it,
+ will assume:-
+
+
+
+ (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+
+
+
+ annoying, but that is the way it is. If you use OR - use brackets.
+ Whilst we are here CASE is not important. 'And BY_Zone' is just 'and
+ by_zone'.
+
+ If you want to alter your filter you can just redefine one or more
+ lines of it or clear out one line. For example:-
+
+
+
+ reject/spots 1 on hf/ssb
+
+
+
+ or
+
+
+
+ clear/spots 1
+
+
+
+ To remove the filter in its entirty:-
+
+
+
+ clear/spots all
+
+
+
+ There are similar CLEAR commands for the other filters:-
+
+
+
+ clear/announce
+ clear/wcy
+ clear/wwv
+
+
+
+ ADVANCED USERS:-
+
+ Once you are happy with the results you get, you may like to
+ experiment.
+
+ my example that filters hf/cw spots and accepts vhf/uhf spots from EU
+ can be written with a mixed filter, eg:
+
+
+
+ rej/spot on hf/cw
+ acc/spot on 0/30000
+ acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+ each filter slot actually has a 'reject' slot and an 'accept' slot.
+ The reject slot is executed BEFORE the accept slot.
+
+ It was mentioned earlier that after a reject test that doesn't match,
+ the default for following tests is 'accept', the reverse is true for
+ first, any non hf/cw spot is passed to the accept line, which lets
+ thru everything else on HF.
+
+ The next filter line lets through just VHF/UHF spots from EU.
+
+ 1\b12\b2.\b.3\b30\b0.\b. h\bhe\bel\blp\bp
+
+ h\bhe\bel\blp\bp The HELP Command
+
+
+ HELP is available for a number of commands. The syntax is:-
+
+
+
+ HELP <cmd>
+
+
+
+ Where <cmd> is the name of the command you want help on.
+
+ All commands can be abbreviated, so SHOW/DX can be abbreviated to
+ SH/DX, ANNOUNCE can be shortened to AN and so on.
+
+ Look at the APROPOS <string> command which will search the help
+ database for the <string> you specify and give you a list of likely
+ commands to look at with HELP.
+
+ 1\b12\b2.\b.3\b31\b1.\b. k\bki\bil\bll\bl <\b<f\bfr\bro\bom\bm m\bms\bsg\bgn\bno\bo>\b>-\b-<\b<t\bto\bo m\bms\bsg\bgn\bno\bo>\b>
+
+ k\bki\bil\bll\bl <\b<f\bfr\bro\bom\bm m\bms\bsg\bgn\bno\bo>\b>-\b-<\b<t\bto\bo m\bms\bsg\bgn\bno\bo>\b> Delete a range of messages
+
+
+
+ 1\b12\b2.\b.3\b32\b2.\b. k\bki\bil\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo.\b..\b.]\b]
+
+ k\bki\bil\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo.\b..\b.]\b] Delete a message from the local system
+
+
+
+ 1\b12\b2.\b.3\b33\b3.\b. k\bki\bil\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b> .\b..\b..\b.]\b]
+
+ k\bki\bil\bll\bl <\b<m\bms\bsg\bgn\bno\bo>\b> [\b[<\b<m\bms\bsg\bgn\bno\bo>\b> .\b..\b..\b.]\b] Remove or erase a message from the system
+
+
+ You can get rid of any message to or originating from your callsign
+ using this command. You can remove more than one message at a time.
+
+ 1\b12\b2.\b.3\b34\b4.\b. k\bki\bil\bll\bl f\bfr\bro\bom\bm <\b<r\bre\beg\bge\bex\bx>\b>
+
+ k\bki\bil\bll\bl f\bfr\bro\bom\bm <\b<r\bre\beg\bge\bex\bx>\b> Delete messages FROM a callsign or pattern
+
+
+
+ 1\b12\b2.\b.3\b35\b5.\b. k\bki\bil\bll\bl t\bto\bo <\b<r\bre\beg\bge\bex\bx>\b>
+
+ k\bki\bil\bll\bl t\bto\bo <\b<r\bre\beg\bge\bex\bx>\b> Delete messages TO a callsign or pattern
+
+
+
+ 1\b12\b2.\b.3\b36\b6.\b. l\bli\bin\bnk\bks\bs
+
+ l\bli\bin\bnk\bks\bs Show which nodes is physically connected
+
+
+ This is a quick listing that shows which links are connected and some
+ information about them. See WHO for a list of all connections.
+
+ 1\b12\b2.\b.3\b37\b7.\b. r\bre\bea\bad\bd
+
+ r\bre\bea\bad\bd Read the next unread personal message addressed to you
+
+
+
+ 1\b12\b2.\b.3\b38\b8.\b. r\bre\bea\bad\bd <\b<m\bms\bsg\bgn\bno\bo>\b>
+
+ r\bre\bea\bad\bd <\b<m\bms\bsg\bgn\bno\bo>\b> Read the specified message
+
+
+ You can read any messages that are sent as 'non-personal' and also any
+ message either sent by or sent to your callsign.
+
+ 1\b12\b2.\b.3\b39\b9.\b. r\bre\bej\bje\bec\bct\bt
+
+ r\bre\bej\bje\bec\bct\bt Set a filter to reject something
+
+
+ Create a filter to reject something
+
+ There are 2 types of filter, accept and reject. See HELP FILTERING
+ for more info.
+
+ 1
\b12
\b2.
\b.4
\b40
\b0.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b>
+
+ r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a 'reject' filter line for
+ announce
+
+
+ Create an 'reject this announce' line for a filter.
+
+ A reject filter line means that if the announce matches this filter it
+ is passed onto the user. See HELP FILTERING for more info. Please read
+ this to understand how filters work - it will save a lot of grief
+ later on.
+
+ You can use any of the following things in this line:-
+
+
+
+ info <string> eg: iota or qsl
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ origin_state <states> eg: VA,NH,RI,ME
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ by_state <states> eg: VA,NH,RI,ME
+ channel <prefixes>
+ wx 1 filter WX announces
+ dest <prefixes> eg: 6MUK,WDX (distros)
+
+
+
+ some examples:-
+
+
+
+ rej/ann by_zone 14,15,16 and not by G,M,2
+
+
+
+ You can use the tag 'all' to reject everything eg:
+
+
+
+ rej/ann all
+
+
+
+ but this probably for advanced users...
+
+ 1
\b12
\b2.
\b.4
\b41
\b1.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b>
+
+ r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> Set a 'reject' filter line for spots
+
+
+ Create a 'reject this spot' line for a filter.
+
+ A reject filter line means that if the spot matches this filter it is
+ dumped (not passed on). See HELP FILTERING for more info. Please read
+ this to understand how filters work - it will save a lot of grief
+ later on.
+
+ You can use any of the following things in this line:-
+
+
+
+ freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
+ on <range> same as 'freq'
+ call <prefixes> eg: G,PA,HB9
+ info <string> eg: iota or qsl
+ by <prefixes>
+ call_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ call_itu <prefixes or numbers> or: G,GM,GW
+ call_zone <prefixes or numbers>
+ call_state <states> eg: VA,NH,RI,ME
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ by_state <states> eg: VA,NH,RI,ME
+ origin <prefixes>
+ channel <prefixes>
+
+
+
+ For frequencies, you can use any of the band names defined in
+ SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
+ thus: hf/ssb. You can also just have a simple range like: 0/30000 -
+ this is more efficient than saying simply: on HF (but don't get too
+ hung up about that)
+
+ some examples:-
+
+
+
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+
+
+
+ You can use the tag 'all' to reject everything eg:
+
+
+
+ rej/spot 3 all
+
+
+ but this probably for advanced users...
+
+ 1
\b12
\b2.
\b.4
\b42
\b2.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bwc
\bcy
\by [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b>
+
+ r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bwc
\bcy
\by [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> set a 'reject' WCY filter
+
+
+ It is unlikely that you will want to do this, but if you do then you
+ can filter on the following fields:-
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ channel <prefixes>
+
+
+
+ There are no examples because WCY Broadcasts only come from one place
+ and you either want them or not (see UNSET/WCY if you don't want
+ them).
+
+ This command is really provided for future use.
+
+ See HELP FILTER for information.
+
+ 1
\b12
\b2.
\b.4
\b43
\b3.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bww
\bwv
\bv [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b>
+
+ r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bww
\bwv
\bv [
\b[0
\b0-
\b-9
\b9]
\b] <
\b<p
\bpa
\bat
\btt
\bte
\ber
\brn
\bn>
\b> set a 'reject' WWV filter
+
+
+ It is unlikely that you will want to do this, but if you do then you
+ can filter on the following fields:-
+
+
+
+ by <prefixes> eg: G,M,2
+ origin <prefixes>
+ origin_dxcc <prefixes or numbers> eg: 61,62 (from eg: sh/pre G)
+ origin_itu <prefixes or numbers> or: G,GM,GW
+ origin_zone <prefixes or numbers>
+ by_dxcc <prefixes or numbers>
+ by_itu <prefixes or numbers>
+ by_zone <prefixes or numbers>
+ channel <prefixes>
+
+
+
+ for example
+
+
+
+ reject/wwv by_zone 14,15,16
+
+
+
+ is probably the only useful thing to do (which will only show WWV
+ broadcasts by stations in the US).
+
+ See HELP FILTER for information.
+
+ 1\b12\b2.\b.4\b44\b4.\b. r\bre\bep\bpl\bly\by
+
+ r\bre\bep\bpl\bly\by Reply (privately) to the last message that you have read
+
+
+
+ 1\b12\b2.\b.4\b45\b5.\b. r\bre\bep\bpl\bly\by <\b<m\bms\bsg\bgn\bno\bo>\b>
+
+ r\bre\bep\bpl\bly\by <\b<m\bms\bsg\bgn\bno\bo>\b> Reply (privately) to the specified message
+
+
+
+ 1\b12\b2.\b.4\b46\b6.\b. r\bre\bep\bpl\bly\by b\bb <\b<m\bms\bsg\bgn\bno\bo>\b>
+
+ r\bre\bep\bpl\bly\by b\bb <\b<m\bms\bsg\bgn\bno\bo>\b> Reply as a Bulletin to the specified message
+
+
+
+ 1\b12\b2.\b.4\b47\b7.\b. r\bre\bep\bpl\bly\by n\bno\bop\bpr\bri\biv\bva\bat\bte\be <\b<m\bms\bsg\bgn\bno\bo>\b>
+
+ r\bre\bep\bpl\bly\by n\bno\bop\bpr\bri\biv\bva\bat\bte\be <\b<m\bms\bsg\bgn\bno\bo>\b> Reply as a Bulletin to the specified message
+
+
+
+ 1\b12\b2.\b.4\b48\b8.\b. r\bre\bep\bpl\bly\by r\brr\br <\b<m\bms\bsg\bgn\bno\bo>\b>
+
+ r\bre\bep\bpl\bly\by r\brr\br <\b<m\bms\bsg\bgn\bno\bo>\b> Reply to the specified message with read receipt
+
+
+ You can reply to a message and the subject will automatically have
+ "Re:" inserted in front of it, if it isn't already present.
+
+ You can also use all the extra qualifiers such as RR, PRIVATE,
+ NOPRIVATE, B that you can use with the SEND command (see SEND for
+ further details)
+
+ 1\b12\b2.\b.4\b49\b9.\b. s\bse\ben\bnd\bd <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b]
+
+ s\bse\ben\bnd\bd <\b<c\bca\bal\bll\bl>\b> [\b[<\b<c\bca\bal\bll\bl>\b> .\b..\b..\b.]\b] Send a message to one or more callsigns
+
+
+
+ 1\b12\b2.\b.5\b50\b0.\b. s\bse\ben\bnd\bd c\bco\bop\bpy\by <\b<m\bms\bsg\bgn\bno\bo>\b> <\b<c\bca\bal\bll\bl>\b>
+
+ s\bse\ben\bnd\bd c\bco\bop\bpy\by <\b<m\bms\bsg\bgn\bno\bo>\b> <\b<c\bca\bal\bll\bl>\b> Send a copy of a message to someone
+
+
+
+ 1\b12\b2.\b.5\b51\b1.\b. s\bse\ben\bnd\bd n\bno\bop\bpr\bri\biv\bva\bat\bte\be <\b<c\bca\bal\bll\bl>\b>
+
+ s\bse\ben\bnd\bd n\bno\bop\bpr\bri\biv\bva\bat\bte\be <\b<c\bca\bal\bll\bl>\b> Send a message to all stations
+
+
+ All the SEND commands will create a message which will be sent either
+ to an individual callsign or to one of the 'bulletin' addresses.
+
+ SEND <call> on its own acts as though you had typed SEND PRIVATE, that
+ is it will mark the message as personal and send it to the cluster
+ node that that callsign is connected to. If the <call> you have
+ specified is in fact a known bulletin category on your node (eg: ALL)
+ then the message should automatically become a bulletin.
+ You can have more than one callsign in all of the SEND commands.
+
+ You can have multiple qualifiers so that you can have for example:-
+
+
+
+ SEND RR COPY 123 PRIVATE G1TLH G0RDI
+
+
+
+ which should send a copy of message 123 to G1TLH and G0RDI and you
+ will receive a read receipt when they have read the message.
+
+ SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
+ is an alias for SEND PRIVATE
+
+ The system will ask you for a subject. Conventionally this should be
+ no longer than 29 characters for compatibility. Most modern cluster
+ software should accept more.
+
+ You will now be prompted to start entering your text.
+
+ You finish the message by entering '/EX' on a new line. For instance:
+
+
+
+ ...
+ bye then Jim
+ 73 Dirk
+ /ex
+
+
+
+ If you have started a message and you don't want to keep it then you
+ can abandon the message with '/ABORT' on a new line, like:-
+
+
+
+ line 1
+ line 2
+ oh I just can't be bothered with this
+ /abort
+
+
+
+ If you abort the message it will NOT be sent.
+
+ When you are entering the text of your message, most normal output
+ (such as DX announcements and so on are suppressed and stored for
+ latter display (upto 20 such lines are stored, as new ones come along,
+ so the oldest lines are dropped).
+
+ Also, you can enter normal commands commands (and get the output
+ immediately) whilst in the middle of a message. You do this by typing
+ the command preceeded by a '/' character on a new line, so:-
+
+
+
+ /dx g1tlh 144010 strong signal
+
+
+
+ Will issue a dx annoucement to the rest of the cluster.
+
+ Also, you can add the output of a command to your message by
+ preceeding the command with '//', thus :-
+
+
+
+ //sh/vhftable
+
+
+
+ This will show YOU the output from SH/VHFTABLE and also store it in
+ the message.
+
+ You can carry on with the message until you are ready to send it.
+
+ 1\b12\b2.\b.5\b52\b2.\b. s\bse\ben\bnd\bd p\bpr\bri\biv\bva\bat\bte\be <\b<c\bca\bal\bll\bl>\b>
+
+ s\bse\ben\bnd\bd p\bpr\bri\biv\bva\bat\bte\be <\b<c\bca\bal\bll\bl>\b> Send a personal message
+
+
+
+ 1\b12\b2.\b.5\b53\b3.\b. s\bse\ben\bnd\bd r\brr\br <\b<c\bca\bal\bll\bl>\b>
+
+ s\bse\ben\bnd\bd r\brr\br <\b<c\bca\bal\bll\bl>\b> Send a message and ask for a read receipt
+
+
+
+ 1\b12\b2.\b.5\b54\b4.\b. s\bse\bet\bt/\b/a\bad\bdd\bdr\bre\bes\bss\bs <\b<y\byo\bou\bur\br a\bad\bdd\bdr\bre\bes\bss\bs>\b>
+
+ s\bse\bet\bt/\b/a\bad\bdd\bdr\bre\bes\bss\bs <\b<y\byo\bou\bur\br a\bad\bdd\bdr\bre\bes\bss\bs>\b> Record your postal address
+
+
+
+ 1\b12\b2.\b.5\b55\b5.\b. s\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be
+
+ s\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be Allow announce messages to come out on your terminal
+
+
+
+ 1\b12\b2.\b.5\b56\b6.\b. s\bse\bet\bt/\b/a\ban\bnn\bnt\bta\bal\blk\bk
+
+ s\bse\bet\bt/\b/a\ban\bnn\bnt\bta\bal\blk\bk Allow talk like announce messages on your terminal
+
+
+
+ 1\b12\b2.\b.5\b57\b7.\b. s\bse\bet\bt/\b/b\bbe\bee\bep\bp
+
+ s\bse\bet\bt/\b/b\bbe\bee\bep\bp Add a beep to DX and other messages on your terminal
+
+
+
+ 1\b12\b2.\b.5\b58\b8.\b. s\bse\bet\bt/\b/d\bdx\bx
+
+ s\bse\bet\bt/\b/d\bdx\bx Allow DX messages to come out on your terminal
+
+
+
+ 1\b12\b2.\b.5\b59\b9.\b. s\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bd
+
+ s\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bd Allow QRA Grid Squares on the end of DX announcements
+
+
+
+ 1\b12\b2.\b.6\b60\b0.\b. s\bse\bet\bt/\b/e\bec\bch\bho\bo
+
+ s\bse\bet\bt/\b/e\bec\bch\bho\bo Make the cluster echo your input
+
+
+
+ 1\b12\b2.\b.6\b61\b1.\b. s\bse\bet\bt/\b/e\bem\bma\bai\bil\bl <\b<e\bem\bma\bai\bil\bl>\b> .\b..\b..\b.
+
+ s\bse\bet\bt/\b/e\bem\bma\bai\bil\bl <\b<e\bem\bma\bai\bil\bl>\b> .\b..\b..\b. Set email address(es) and forward your personals
+
+
+
+ 1\b12\b2.\b.6\b62\b2.\b. s\bse\bet\bt/\b/h\bhe\ber\bre\be
+
+ s\bse\bet\bt/\b/h\bhe\ber\bre\be Tell the system you are present at your terminal
+
+
+
+ 1\b12\b2.\b.6\b63\b3.\b. s\bse\bet\bt/\b/h\bho\bom\bme\ben\bno\bod\bde\be <\b<n\bno\bod\bde\be>\b>
+
+ s\bse\bet\bt/\b/h\bho\bom\bme\ben\bno\bod\bde\be <\b<n\bno\bod\bde\be>\b> Set your normal cluster callsign
+
+
+ Tell the cluster system where you normally connect to. Any Messages
+ sent to you will normally find their way there should you not be
+ connected. eg:-
+
+
+ SET/HOMENODE gb7djk
+
+
+
+ 1\b12\b2.\b.6\b64\b4.\b. s\bse\bet\bt/\b/l\bla\ban\bng\bgu\bua\bag\bge\be <\b<l\bla\ban\bng\bg>\b>
+
+ s\bse\bet\bt/\b/l\bla\ban\bng\bgu\bua\bag\bge\be <\b<l\bla\ban\bng\bg>\b> Set the language you want to use
+
+
+ You can select the language that you want the cluster to use.
+ Currently the languages available are en (English), de (German), es
+ (Spanish) and nl (Dutch).
+
+ 1\b12\b2.\b.6\b65\b5.\b. s\bse\bet\bt/\b/l\blo\boc\bca\bat\bti\bio\bon\bn <\b<l\bla\bat\bt &\b& l\blo\bon\bng\bg>\b>
+
+ s\bse\bet\bt/\b/l\blo\boc\bca\bat\bti\bio\bon\bn <\b<l\bla\bat\bt &\b& l\blo\bon\bng\bg>\b> Set your latitude and longitude
+
+
+
+ 1\b12\b2.\b.6\b66\b6.\b. s\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo
+
+ s\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo Inform when a station logs in locally
+
+
+
+ 1\b12\b2.\b.6\b67\b7.\b. s\bse\bet\bt/\b/n\bna\bam\bme\be <\b<y\byo\bou\bur\br n\bna\bam\bme\be>\b>
+
+ s\bse\bet\bt/\b/n\bna\bam\bme\be <\b<y\byo\bou\bur\br n\bna\bam\bme\be>\b> Set your name
+
+
+ Tell the system what your name is eg:-
+
+
+ SET/NAME Dirk
+
+
+ 1\b12\b2.\b.6\b68\b8.\b. s\bse\bet\bt/\b/p\bpa\bag\bge\be <\b<l\bli\bin\bne\bes\bs p\bpe\ber\br p\bpa\bag\bge\be>\b>
+
+ s\bse\bet\bt/\b/p\bpa\bag\bge\be <\b<l\bli\bin\bne\bes\bs p\bpe\ber\br p\bpa\bag\bge\be>\b> Set the lines per page
+
+
+ Tell the system how many lines you wish on a page when the number of
+ line of output from a command is more than this. The default is 20.
+ Setting it explicitly to 0 will disable paging.
+
+
+ SET/PAGE 30
+ SET/PAGE 0
+
+
+
+ The setting is stored in your user profile.
+
+ 1\b12\b2.\b.6\b69\b9.\b. s\bse\bet\bt/\b/p\bpa\bas\bss\bsw\bwo\bor\brd\bd
+
+ s\bse\bet\bt/\b/p\bpa\bas\bss\bsw\bwo\bor\brd\bd Set your own password
+
+
+ This command only works for a 'telnet' user (currently). It will only
+ work if you have a password already set. This initial password can
+ only be set by the sysop.
+
+ When you execute this command it will ask you for your old password,
+ then ask you to type in your new password twice (to make sure you get
+ it right). You may or may not see the data echoed on the screen as you
+ type, depending on the type of telnet client you have.
+
+ 1\b12\b2.\b.7\b70\b0.\b. s\bse\bet\bt/\b/p\bpr\bro\bom\bmp\bpt\bt <\b<s\bst\btr\bri\bin\bng\bg>\b>
+
+ s\bse\bet\bt/\b/p\bpr\bro\bom\bmp\bpt\bt <\b<s\bst\btr\bri\bin\bng\bg>\b> Set your prompt to <string>
+
+
+
+ 1\b12\b2.\b.7\b71\b1.\b. s\bse\bet\bt/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b>
+
+ s\bse\bet\bt/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> Set your QRA Grid locator
+
+
+ Tell the system what your QRA (or Maidenhead) locator is. If you have
+ not done a SET/LOCATION then your latitude and longitude will be set
+ roughly correctly (assuming your locator is correct ;-). For example:-
+
+
+ SET/QRA JO02LQ
+
+
+
+ 1\b12\b2.\b.7\b72\b2.\b. s\bse\bet\bt/\b/q\bqt\bth\bh <\b<y\byo\bou\bur\br q\bqt\bth\bh>\b>
+
+ s\bse\bet\bt/\b/q\bqt\bth\bh <\b<y\byo\bou\bur\br q\bqt\bth\bh>\b> Set your QTH
+
+
+ Tell the system where you are. For example:-
+
+
+ SET/QTH East Dereham, Norfolk
+
+
+
+ 1\b12\b2.\b.7\b73\b3.\b. s\bse\bet\bt/\b/t\bta\bal\blk\bk
+
+ s\bse\bet\bt/\b/t\bta\bal\blk\bk Allow TALK messages to come out on your terminal
+
+
+
+ 1\b12\b2.\b.7\b74\b4.\b. s\bse\bet\bt/\b/w\bwc\bcy\by
+
+ s\bse\bet\bt/\b/w\bwc\bcy\by Allow WCY messages to come out on your terminal
+
+
+
+ 1\b12\b2.\b.7\b75\b5.\b. s\bse\bet\bt/\b/w\bww\bwv\bv
+
+ s\bse\bet\bt/\b/w\bww\bwv\bv Allow WWV messages to come out on your terminal
+
+
+
+ 1\b12\b2.\b.7\b76\b6.\b. s\bse\bet\bt/\b/w\bwx\bx
+
+ s\bse\bet\bt/\b/w\bwx\bx Allow WX messages to come out on your terminal
+
+
+
+ 1\b12\b2.\b.7\b77\b7.\b. s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn [\b[<\b<n\bno\bod\bde\be>\b>]\b]
+
+ s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn [\b[<\b<n\bno\bod\bde\be>\b>]\b] Show all the nodes and users visible
+
+
+ This command allows you to see all the users that can be seen and the
+ nodes to which they are connected.
+
+ This command is normally abbreviated to: sh/c
+
+ Normally, the list returned will be just for the nodes from your
+ country (because the list otherwise will be very long).
+
+
+
+ SH/C ALL
+
+
+
+ will produce a complete list of all nodes.
+
+ BE WARNED: the list that is returned can be VERY long
+
+ It is possible to supply a node or part of a prefix and you will get a
+ list of the users for that node or list of nodes starting with that
+ prefix.
+
+
+
+ SH/C GB7DJK
+
+
+
+ SH/C SK
+
+
+
+ 1\b12\b2.\b.7\b78\b8.\b. s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn/\b/n\bno\bod\bde\be
+
+ s\bsh\bho\bow\bw/\b/c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn/\b/n\bno\bod\bde\be Show all the nodes connected locally
+
+
+ Show all the nodes connected to this node.
+
+ 1
\b12
\b2.
\b.7
\b79
\b9.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bda
\bat
\bte
\be [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b]
+
+ s
\bsh
\bho
\bow
\bw/
\b/d
\bda
\bat
\bte
\be [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show the local time
+
+
+ This is very nearly the same as SHOW/TIME, the only difference the
+ format of the date string if no arguments are given.
+
+ If no prefixes or callsigns are given then this command returns the
+ local time and UTC as the computer has it right now. If you give some
+ prefixes then it will show UTC and UTC + the local offset (not
+ including DST) at the prefixes or callsigns that you specify.
+
+ 1\b12\b2.\b.8\b80\b0.\b. s\bsh\bho\bow\bw/\b/d\bdx\bx
+
+ s\bsh\bho\bow\bw/\b/d\bdx\bx Interrogate the spot database
+
+
+ If you just type SHOW/DX you will get the last so many spots (sysop
+ configurable, but usually 10).
+
+ In addition you can add any number of these commands in very nearly
+ any order to the basic SHOW/DX command, they are:-
+
+
+
+ on <band> - eg 160m 20m 2m 23cm 6mm
+ on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
+ on <from>/<to> - eg 1000/4000 14000-30000 (in Khz)
+ <from>-<to>
+
+
+
+ <number> - the number of spots you want
+ <from>-<to> - <from> spot no <to> spot no in the selected list
+ <from>/<to>
+
+
+
+ <prefix> - for a spotted callsign beginning with <prefix>
+ *<suffix> - for a spotted callsign ending in <suffix>
+ *<string>* - for a spotted callsign containing <string>
+
+
+
+ day <number> - starting <number> days ago
+ day <from>-<to> - <from> days <to> days ago
+ <from>/<to>
+
+
+ info <text> - any spots containing <text> in the info or remarks
+
+
+
+ by <call> - any spots spotted by <call> (spotter <call> is the
+ same).
+
+
+
+ qsl - this automatically looks for any qsl info on the call
+ held in the spot database.
+
+
+
+ iota [<iota>] - If the iota island number is missing it will look for
+ the string iota and anything which looks like an iota
+ island number. If you specify then it will look for
+ that island.
+
+
+
+ qra [<locator>] - this will look for the specific locator if you specify
+ one or else anything that looks like a locator.
+
+
+
+ dxcc - treat the prefix as a 'country' and look for spots
+ from that country regardless of actual prefix.
+ eg dxcc oq2
+
+
+
+ You can also use this with the 'by' keyword so
+ eg by W dxcc
+
+
+
+ e.g.
+
+
+
+ SH/DX 9m0
+ SH/DX on 20m info iota
+ SH/DX 9a on vhf day 30
+ SH/DX rf1p qsl
+ SH/DX iota
+ SH/DX iota eu-064
+ SH/DX qra jn86
+ SH/DX dxcc oq2
+ SH/DX dxcc oq2 by w dxcc
+
+
+
+ 1
\b12
\b2.
\b.8
\b81
\b1.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bxc
\bcc
\bc <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>
+
+ s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bxc
\bcc
\bc <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b> Interrogate the spot database by country
+
+
+ This command takes the <prefix> (which can be a full or partial
+ callsign if desired), looks up which internal country number it is and
+ then displays all the spots as per SH/DX for that country.
+
+ This is now an alias for 'SHOW/DX DXCC'
+
+ The options for SHOW/DX also apply to this command. e.g.
+
+
+
+ SH/DXCC G
+ SH/DXCC W on 20m iota
+
+
+
+ This can be done with the SHOW/DX command like this:-
+
+
+
+ SH/DX dxcc g
+ SH/DX dxcc w on 20m iota
+
+
+
+ 1\b12\b2.\b.8\b82\b2.\b. s\bsh\bho\bow\bw/\b/d\bdx\bxs\bst\bta\bat\bts\bs [\b[d\bda\bay\bys\bs]\b] [\b[d\bda\bat\bte\be]\b]
+
+ s\bsh\bho\bow\bw/\b/d\bdx\bxs\bst\bta\bat\bts\bs [\b[d\bda\bay\bys\bs]\b] [\b[d\bda\bat\bte\be]\b] Show the DX Statistics
+
+
+ Show the total DX spots for the last <days> no of days (default is
+ 31), starting from a <date> (default: today).
+
+ 1\b12\b2.\b.8\b83\b3.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\ble\bes\bs [\b[<\b<f\bfi\bil\ble\bea\bar\bre\bea\ba>\b> [\b[<\b<s\bst\btr\bri\bin\bng\bg>\b>]\b]]\b]
+
+ s\bsh\bho\bow\bw/\b/f\bfi\bil\ble\bes\bs [\b[<\b<f\bfi\bil\ble\bea\bar\bre\bea\ba>\b> [\b[<\b<s\bst\btr\bri\bin\bng\bg>\b>]\b]]\b] List the contents of a filearea
+
+
+ SHOW/FILES on its own will show you a list of the various fileareas
+ available on the system. To see the contents of a particular file area
+ type:-
+
+
+ SH/FILES <filearea>
+
+ where <filearea> is the name of the filearea you want to see the con-
+ tents of.
+
+ You can also use shell globbing characters like '*' and '?' in a
+ string to see a selection of files in a filearea eg:-
+
+
+ SH/FILES bulletins arld*
+
+
+
+ See also TYPE - to see the contents of a file.
+
+ 1\b12\b2.\b.8\b84\b4.\b. s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br
+
+ s\bsh\bho\bow\bw/\b/f\bfi\bil\blt\bte\ber\br Show the contents of all the filters you have set
+
+
+ Show the contents of all the filters that are set. This command
+ displays all the filters set - for all the various categories.
+
+ 1\b12\b2.\b.8\b85\b5.\b. s\bsh\bho\bow\bw/\b/h\bhf\bfs\bst\bta\bat\bts\bs [\b[d\bda\bay\bys\bs]\b] [\b[d\bda\bat\bte\be]\b]
+
+ s\bsh\bho\bow\bw/\b/h\bhf\bfs\bst\bta\bat\bts\bs [\b[d\bda\bay\bys\bs]\b] [\b[d\bda\bat\bte\be]\b] Show the HF DX Statistics
+
+
+ Show the HF DX spots breakdown by band for the last <days> no of days
+ (default is 31), starting from a <date> (default: today).
+
+ 1\b12\b2.\b.8\b86\b6.\b. s\bsh\bho\bow\bw/\b/h\bhf\bft\bta\bab\bbl\ble\be [\b[d\bda\bay\bys\bs]\b] [\b[d\bda\bat\bte\be]\b] [\b[p\bpr\bre\bef\bfi\bix\bx .\b..\b..\b.]\b]
+
+ s\bsh\bho\bow\bw/\b/h\bhf\bft\bta\bab\bbl\ble\be [\b[d\bda\bay\bys\bs]\b] [\b[d\bda\bat\bte\be]\b] [\b[p\bpr\bre\bef\bfi\bix\bx .\b..\b..\b.]\b] Show the HF DX Spotter Table
+
+
+ Show the HF DX Spotter table for the list of prefixes for the last
+ <days> no of days (default is 31), starting from a <date> (default:
+ today).
+
+ If there are no prefixes then it will show the table for your country.
+
+ Remember that some countries have more than one "DXCC country" in them
+ (eg G :-), to show them (assuming you are not in G already which is
+ specially treated in the code) you must list all the relevant prefixes
+
+
+
+ sh/hftable g gm gd gi gj gw gu
+
+
+
+ Note that the prefixes are converted into country codes so you don't
+ have to list all possible prefixes for each country.
+
+ If you want more or less days than the default simply include the
+ number you require:-
+
+
+
+ sh/hftable 20 pa
+
+
+
+ If you want to start at a different day, simply add the date in some
+ recognizable form:-
+
+
+
+ sh/hftable 2 25nov02
+ sh/hftable 2 25-nov-02
+ sh/hftable 2 021125
+ sh/hftable 2 25/11/02
+
+
+
+ This will show the stats for your DXCC for that CQWW contest weekend.
+
+ You can specify either prefixes or full callsigns (so you can see how
+ you did against all your mates). You can also say 'all' which will
+ then print the worldwide statistics.
+
+
+
+ sh/hftable all
+
+
+
+ 1
\b12
\b2.
\b.8
\b87
\b7.
\b. s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn [
\b[n
\bnd
\bda
\bay
\bys
\bs]
\b] [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b]
+
+ s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn [
\b[n
\bnd
\bda
\bay
\bys
\bs]
\b] [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show Moon rise and set times
+
+
+ Show the Moon rise and set times for a (list of) prefixes or
+ callsigns, together with the azimuth and elevation of the sun
+ currently at those locations.
+
+ If you don't specify any prefixes or callsigns, it will show the times
+ for your QTH (assuming you have set it with either SET/LOCATION or
+ SET/QRA), together with the current azimuth and elevation.
+
+ In addition, it will show the illuminated fraction of the moons disk.
+
+ If all else fails it will show the Moonrise and set times for the node
+ that you are connected to.
+
+ For example:-
+
+
+
+ SH/MOON
+ SH/MOON G1TLH W5UN
+
+
+
+ You can also use this command to see into the past or the future, so
+ if you want to see yesterday's times then do:-
+
+
+
+ SH/MOON -1
+
+
+
+ or in three days time:-
+
+
+
+ SH/MOON +3 W9
+
+
+
+ Upto 366 days can be checked both in the past and in the future.
+
+ Please note that the rise and set times are given as the UT times of
+ rise and set on the requested UT day.
+
+ 1
\b12
\b2.
\b.8
\b88
\b8.
\b. s
\bsh
\bho
\bow
\bw/
\b/m
\bmu
\buf
\bf <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b> [
\b[<
\b<h
\bho
\bou
\bur
\brs
\bs>
\b>]
\b][
\b[l
\blo
\bon
\bng
\bg]
\b]
+
+ s
\bsh
\bho
\bow
\bw/
\b/m
\bmu
\buf
\bf <
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b> [
\b[<
\b<h
\bho
\bou
\bur
\brs
\bs>
\b>]
\b][
\b[l
\blo
\bon
\bng
\bg]
\b] Show the likely propagation to a
+ prefix
+
+
+ This command allow you to estimate the likelihood of you contacting a
+ station with the prefix you have specified. The output assumes a
+ modest power of 20dBW and receiver sensitivity of -123dBm (about
+ 0.15muV/10dB SINAD)
+
+ The result predicts the most likely operating frequencies and signal
+ levels for high frequency (shortwave) radio propagation paths on
+ specified days of the year and hours of the day. It is most useful for
+ paths between 250 km and 6000 km, but can be used with reduced
+ accuracy for paths shorter or longer than this.
+
+ The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
+ used to predict the MUF given the predicted flux, day of the year,
+ hour of the day and geographic coordinates of the transmitter and
+ receiver. This routine is reasonably accurate for the purposes here,
+ with a claimed RMS error of 3.8 MHz, but much smaller and less complex
+ than the programs used by major shortwave broadcasting organizations,
+ such as the Voice of America.
+
+ The command will display some header information detailing its
+ assumptions, together with the locations, latitude and longitudes and
+ bearings. It will then show UTC (UT), local time at the other end
+ (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
+ (Zen) and the likely signal strengths. Then for each frequency for
+ which the system thinks there is a likelihood of a circuit it prints a
+ value.
+
+ The value is currently a likely S meter reading based on the
+ conventional 6dB / S point scale. If the value has a '+' appended it
+ means that it is 1/2 an S point stronger. If the value is preceeded by
+ an 'm' it means that there is likely to be much fading and by an 's'
+ that the signal is likely to be noisy.
+
+ By default SHOW/MUF will show the next two hours worth of data. You
+ can specify anything up to 24 hours worth of data by appending the no
+ of hours required after the prefix. For example:-
+
+
+
+ SH/MUF W
+
+
+
+ produces:
+
+ RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
+ Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
+ Location Lat / Long Azim
+ East Dereham, Norfolk 52 41 N 0 57 E 47
+ United-States-W 43 0 N 87 54 W 299
+ UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
+ 18 23 11.5 -35 mS0+ mS2 S3
+ 19 0 11.2 -41 mS0+ mS2 S3
+
+
+
+ indicating that you will have weak, fading circuits on top band and
+ 80m but usable signals on 40m (about S3).
+
+ inputing:-
+
+
+
+ SH/MUF W 24
+
+
+
+ will get you the above display, but with the next 24 hours worth of
+ propagation data.
+
+
+
+ SH/MUF W L 24
+ SH/MUF W 24 Long
+
+
+
+ Gives you an estimate of the long path propagation characterics. It
+ should be noted that the figures will probably not be very useful, nor
+ terrible accurate, but it is included for completeness.
+
+ 1\b12\b2.\b.8\b89\b9.\b. s\bsh\bho\bow\bw/\b/n\bne\bew\bwc\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn [\b[<\b<n\bno\bod\bde\be>\b>]\b]
+
+ s\bsh\bho\bow\bw/\b/n\bne\bew\bwc\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn [\b[<\b<n\bno\bod\bde\be>\b>]\b] Show all the nodes and users visible
+
+
+ This command allows you to see all the users that can be seen and the
+ nodes to which they are connected.
+
+ This command produces essentially the same information as
+ SHOW/CONFIGURATION except that it shows all the duplication of any
+ routes that might be present It also uses a different format which may
+ not take up quite as much space if you don't have any loops.
+
+ BE WARNED: the list that is returned can be VERY long
+
+ 1\b12\b2.\b.9\b90\b0.\b. s\bsh\bho\bow\bw/\b/n\bne\bew\bwc\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn/\b/n\bno\bod\bde\be
+
+ s\bsh\bho\bow\bw/\b/n\bne\bew\bwc\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn/\b/n\bno\bod\bde\be Show all the nodes connected locally
+
+
+ Show all the nodes connected to this node in the new format.
+
+ 1\b12\b2.\b.9\b91\b1.\b. s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b>
+
+ s\bsh\bho\bow\bw/\b/p\bpr\bre\bef\bfi\bix\bx <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Interrogate the prefix database
+
+
+ This command takes the <callsign> (which can be a full or partial
+ callsign or a prefix), looks up which internal country number it is
+ and then displays all the relevant prefixes for that country together
+ with the internal country no, the CQ and ITU regions.
+
+ See also SHOW/DXCC
+
+ 1\b12\b2.\b.9\b92\b2.\b. s\bsh\bho\bow\bw/\b/q\bqr\bra\ba <\b<l\bla\bat\bt>\b> <\b<l\blo\bon\bng\bg>\b>
+
+ s\bsh\bho\bow\bw/\b/q\bqr\bra\ba <\b<l\bla\bat\bt>\b> <\b<l\blo\bon\bng\bg>\b> Convert lat/long to a QRA Grid locator
+
+
+ This is a multipurpose command that allows you either to calculate the
+ distance and bearing between two locators or (if only one locator is
+ given on the command line) the distance and beraing from your station
+ to the locator. For example:-
+
+
+
+ SH/QRA IO92QL
+ SH/QRA JN06 IN73
+
+
+
+ The first example will show the distance and bearing to the locator
+ from yourself, the second example will calculate the distance and
+ bearing from the first locator to the second. You can use 4 or 6
+ character locators.
+
+ It is also possible to convert a latitude and longitude to a locator
+ by using this command with a latitude and longitude as an argument,
+ for example:-
+
+
+
+ SH/QRA 52 41 N 0 58 E
+
+
+
+ 1\b12\b2.\b.9\b93\b3.\b. s\bsh\bho\bow\bw/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> [\b[<\b<l\blo\boc\bca\bat\bto\bor\br>\b>]\b]
+
+ s\bsh\bho\bow\bw/\b/q\bqr\bra\ba <\b<l\blo\boc\bca\bat\bto\bor\br>\b> [\b[<\b<l\blo\boc\bca\bat\bto\bor\br>\b>]\b] Show distance between QRA Grid locators
+
+
+
+ 1\b12\b2.\b.9\b94\b4.\b. s\bsh\bho\bow\bw/\b/q\bqr\brz\bz <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b>
+
+ s\bsh\bho\bow\bw/\b/q\bqr\brz\bz <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> Show any callbook details on a callsign
+
+
+ This command queries the QRZ callbook server on the internet and
+ returns any information available for that callsign. This service is
+ provided for users of this software by http://www.qrz.com
+
+ 1\b12\b2.\b.9\b95\b5.\b. s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> .\b..\b..\b.
+
+ s\bsh\bho\bow\bw/\b/r\bro\bou\but\bte\be <\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> .\b..\b..\b. Show the route to the callsign
+
+
+ This command allows you to see to which node the callsigns specified
+ are connected. It is a sort of inverse sh/config.
+
+
+ sh/route n2tly
+
+
+
+ 1\b12\b2.\b.9\b96\b6.\b. s\bsh\bho\bow\bw/\b/s\bsa\bat\bte\bel\bll\bli\bit\bte\be <\b<n\bna\bam\bme\be>\b> [\b[<\b<h\bho\bou\bur\brs\bs>\b> <\b<i\bin\bnt\bte\ber\brv\bva\bal\bl>\b>]\b]
+
+ s\bsh\bho\bow\bw/\b/s\bsa\bat\bte\bel\bll\bli\bit\bte\be <\b<n\bna\bam\bme\be>\b> [\b[<\b<h\bho\bou\bur\brs\bs>\b> <\b<i\bin\bnt\bte\ber\brv\bva\bal\bl>\b>]\b] Show tracking data
+
+
+ Show the tracking data from your location to the satellite of your
+ choice from now on for the next few hours.
+
+ If you use this command without a satellite name it will display a
+ list of all the satellites known currently to the system.
+
+ If you give a name then you can obtain tracking data of all the passes
+ that start and finish 5 degrees below the horizon. As default it will
+ give information for the next three hours for every five minute
+ period.
+
+ You can alter the number of hours and the step size, within certain
+ limits.
+
+ Each pass in a period is separated with a row of '-----' characters
+
+ So for example:-
+
+
+
+ SH/SAT AO-10
+ SH/SAT FENGYUN1 12 2
+
+
+
+ 1\b12\b2.\b.9\b97\b7.\b. s\bsh\bho\bow\bw/\b/s\bst\bta\bat\bti\bio\bon\bn [\b[<\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> .\b..\b.]\b]
+
+ s\bsh\bho\bow\bw/\b/s\bst\bta\bat\bti\bio\bon\bn [\b[<\b<c\bca\bal\bll\bls\bsi\big\bgn\bn>\b> .\b..\b.]\b] Show information about a callsign
+
+
+ Show the information known about a callsign and whether (and where)
+ that callsign is connected to the cluster.
+
+
+
+ SH/ST G1TLH
+
+
+
+ If no callsign is given then show the information for yourself.
+
+ 1
\b12
\b2.
\b.9
\b98
\b8.
\b. s
\bsh
\bho
\bow
\bw/
\b/s
\bsu
\bun
\bn [
\b[n
\bnd
\bda
\bay
\bys
\bs]
\b] [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b]
+
+ s
\bsh
\bho
\bow
\bw/
\b/s
\bsu
\bun
\bn [
\b[n
\bnd
\bda
\bay
\bys
\bs]
\b] [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show sun rise and set times
+
+
+ Show the sun rise and set times for a (list of) prefixes or callsigns,
+ together with the azimuth and elevation of the sun currently at those
+ locations.
+
+ If you don't specify any prefixes or callsigns, it will show the times
+ for your QTH (assuming you have set it with either SET/LOCATION or
+ SET/QRA), together with the current azimuth and elevation.
+
+ If all else fails it will show the sunrise and set times for the node
+ that you are connected to.
+
+ For example:-
+
+
+
+ SH/SUN
+ SH/SUN G1TLH K9CW ZS
+
+
+
+ You can also use this command to see into the past or the future, so
+ if you want to see yesterday's times then do:-
+
+
+
+ SH/SUN -1
+
+
+
+ or in three days time:-
+
+
+
+ SH/SUN +3 W9
+
+
+
+ Upto 366 days can be checked both in the past and in the future.
+
+ Please note that the rise and set times are given as the UT times of
+ rise and set on the requested UT day.
+
+ 1
\b12
\b2.
\b.9
\b99
\b9.
\b. s
\bsh
\bho
\bow
\bw/
\b/t
\bti
\bim
\bme
\be [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b]
+
+ s
\bsh
\bho
\bow
\bw/
\b/t
\bti
\bim
\bme
\be [
\b[<
\b<p
\bpr
\bre
\bef
\bfi
\bix
\bx>
\b>|
\b|<
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b>]
\b] Show the local time
+
+
+ If no prefixes or callsigns are given then this command returns the
+ local time and UTC as the computer has it right now. If you give some
+ prefixes then it will show UTC and UTC + the local offset (not
+ including DST) at the prefixes or callsigns that you specify.
+
+ 1\b12\b2.\b.1\b10\b00\b0.\b. s\bsh\bho\bow\bw/\b/u\bus\bsd\bdb\bb [\b[c\bca\bal\bll\bl .\b..\b.]\b]
+
+ s\bsh\bho\bow\bw/\b/u\bus\bsd\bdb\bb [\b[c\bca\bal\bll\bl .\b..\b.]\b] Show information held on the FCC Call database
+
+
+ Show the City and State of a Callsign held on the FCC database if his
+ is being run on this system, eg:-
+
+
+
+ sh/usdb k1xx
+
+
+
+ 1\b12\b2.\b.1\b10\b01\b1.\b. s\bsh\bho\bow\bw/\b/v\bvh\bhf\bfs\bst\bta\bat\bts\bs [\b[d\bda\bay\bys\bs]\b] [\b[d\bda\bat\bte\be]\b]
+
+ s\bsh\bho\bow\bw/\b/v\bvh\bhf\bfs\bst\bta\bat\bts\bs [\b[d\bda\bay\bys\bs]\b] [\b[d\bda\bat\bte\be]\b] Show the VHF DX Statistics
+
+
+ Show the VHF DX spots breakdown by band for the last <days> no of days
+ (default is 31), starting from a date (default: today).
+
+ 1\b12\b2.\b.1\b10\b02\b2.\b. s\bsh\bho\bow\bw/\b/v\bvh\bhf\bft\bta\bab\bbl\ble\be [\b[d\bda\bay\bys\bs]\b] [\b[d\bda\bat\bte\be]\b] [\b[p\bpr\bre\bef\bfi\bix\bx .\b..\b..\b.]\b]
+
+ s\bsh\bho\bow\bw/\b/v\bvh\bhf\bft\bta\bab\bbl\ble\be [\b[d\bda\bay\bys\bs]\b] [\b[d\bda\bat\bte\be]\b] [\b[p\bpr\bre\bef\bfi\bix\bx .\b..\b..\b.]\b] Show the VHF DX Spotter Table
+
+
+ Show the VHF DX Spotter table for the list of prefixes for the last
+ <days> no of days (default is 31), starting from a date (default:
+ today).
+
+ If there are no prefixes then it will show the table for your country.
+
+ Remember that some countries have more than one "DXCC country" in them
+ (eg G :-), to show them (assuming you are not in G already which is
+ specially treated in the code) you must list all the relevant prefixes
+
+
+
+ sh/vhftable g gm gd gi gj gw gu
+
+
+
+ Note that the prefixes are converted into country codes so you don't
+ have to list all possible prefixes for each country.
+
+ If you want more or less days than the default simply include the
+ number you require:-
+
+
+
+ sh/vhftable 20 pa
+
+
+
+ If you want to start at a different day, simply add the date in some
+ recognizable form:-
+
+
+
+ sh/vhftable 2 25nov02
+ sh/vhftable 2 25-nov-02
+ sh/vhftable 2 021125
+ sh/vhftable 2 25/11/02
+
+
+
+ This will show the stats for your DXCC for that CQWW contest weekend.
+
+ You can specify either prefixes or full callsigns (so you can see how
+ you did against all your mates). You can also say 'all' which will
+ then print the worldwide statistics.
+
+
+
+ sh/vhftable all
+
+ 1\b12\b2.\b.1\b10\b03\b3.\b. s\bsh\bho\bow\bw/\b/w\bwc\bcy\by
+
+ s\bsh\bho\bow\bw/\b/w\bwc\bcy\by Show last 10 WCY broadcasts
+
+
+
+ 1\b12\b2.\b.1\b10\b04\b4.\b. s\bsh\bho\bow\bw/\b/w\bwc\bcy\by <\b<n\bn>\b>
+
+ s\bsh\bho\bow\bw/\b/w\bwc\bcy\by <\b<n\bn>\b> Show last <n> WCY broadcasts
+
+
+ Display the most recent WCY information that has been received by the
+ system
+
+ 1\b12\b2.\b.1\b10\b05\b5.\b. s\bsh\bho\bow\bw/\b/w\bww\bwv\bv
+
+ s\bsh\bho\bow\bw/\b/w\bww\bwv\bv Show last 10 WWV broadcasts
+
+
+
+ 1\b12\b2.\b.1\b10\b06\b6.\b. s\bsh\bho\bow\bw/\b/w\bww\bwv\bv <\b<n\bn>\b>
+
+ s\bsh\bho\bow\bw/\b/w\bww\bwv\bv <\b<n\bn>\b> Show last <n> WWV broadcasts
+
+
+ Display the most recent WWV information that has been received by the
+ system
+
+ 1\b12\b2.\b.1\b10\b07\b7.\b. s\bsy\bys\bso\bop\bp
+
+ s\bsy\bys\bso\bop\bp Regain your privileges if you login remotely
+
+
+ The system automatically reduces your privilege level to that of a
+ normal user if you login in remotely. This command allows you to
+ regain your normal privilege level. It uses the normal system: five
+ numbers are returned that are indexes into the character array that is
+ your assigned password (see SET/PASSWORD). The indexes start from
+ zero.
+
+ You are expected to return a string which contains the characters
+ required in the correct order. You may intersperse those characters
+ with others to obscure your reply for any watchers. For example (and
+ these values are for explanation :-):
+
+
+
+ password = 012345678901234567890123456789
+ > sysop
+ 22 10 15 17 3
+
+
+
+ you type:-
+
+
+ aa2bbbb0ccc5ddd7xxx3n
+ or 2 0 5 7 3
+ or 20573
+
+
+
+ They will all match. If there is no password you will still be offered
+ numbers but nothing will happen when you input a string. Any match is
+ case sensitive.
+
+ 1\b12\b2.\b.1\b10\b08\b8.\b. t\bta\bal\blk\bk <\b<c\bca\bal\bll\bl>\b> >\b> <\b<n\bno\bod\bde\be>\b> [\b[<\b<t\bte\bex\bxt\bt>\b>]\b]
+
+ t\bta\bal\blk\bk <\b<c\bca\bal\bll\bl>\b> >\b> <\b<n\bno\bod\bde\be>\b> [\b[<\b<t\bte\bex\bxt\bt>\b>]\b] Send a text message to another station
+ via a node
+
+
+ Send a short message to any other station that is visible on the
+ cluster system. You can send it to anyone you can see with a
+ SHOW/CONFIGURATION command, they don't have to be connected locally.
+
+ The second form of TALK is used when other cluster nodes are connected
+ with restricted information. This usually means that they don't send
+ the user information usually associated with logging on and off the
+ cluster.
+
+ If you know that G3JNB is likely to be present on GB7TLH, but you can
+ only see GB7TLH in the SH/C list but with no users, then you would use
+ the second form of the talk message.
+
+ If you want to have a ragchew with someone you can leave the text
+ message out and the system will go into 'Talk' mode. What this means
+ is that a short message is sent to the recipient telling them that you
+ are in a go to the station that you asked for.
+
+ All the usual announcements, spots and so on will still come out on
+ your terminal.
+
+ If you want to do something (such as send a spot) you preceed the
+ normal command with a '/' character, eg:-
+
+
+
+ /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
+ /HELP talk
+
+
+
+ To leave talk mode type:
+
+
+
+ /EX
+
+
+
+ If you are in 'Talk' mode, there is an extention to the '/' command
+ which allows you to send the output to all the people you are talking
+ to. You do with the '//' command. For example:-
+
+
+
+ //sh/hftable
+
+
+
+ will send the hftable as you have it to all the people you are
+ currently talking to.
+
+
+
+ 1\b12\b2.\b.1\b10\b09\b9.\b. t\bta\bal\blk\bk <\b<c\bca\bal\bll\bl>\b> [\b[<\b<t\bte\bex\bxt\bt>\b>]\b]
+
+ t\bta\bal\blk\bk <\b<c\bca\bal\bll\bl>\b> [\b[<\b<t\bte\bex\bxt\bt>\b>]\b] Send a text message to another station
+
+
+
+ 1\b12\b2.\b.1\b11\b10\b0.\b. t\bty\byp\bpe\be <\b<f\bfi\bil\ble\bea\bar\bre\bea\ba>\b>/\b/<\b<n\bna\bam\bme\be>\b>
+
+ t\bty\byp\bpe\be <\b<f\bfi\bil\ble\bea\bar\bre\bea\ba>\b>/\b/<\b<n\bna\bam\bme\be>\b> Look at the contents of a file in one of the
+ fileareas
+
+
+ Type out the contents of a file in a filearea. So, for example, in
+ filearea 'bulletins' you want to look at file 'arld051' you would
+ enter:-
+
+
+ TYPE bulletins/arld051
+
+
+
+ See also SHOW/FILES to see what fileareas are available and a list of
+ content.
+
+ 1\b12\b2.\b.1\b11\b11\b1.\b. u\bun\bns\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be
+
+ u\bun\bns\bse\bet\bt/\b/a\ban\bnn\bno\bou\bun\bnc\bce\be Stop announce messages coming out on your terminal
+
+
+
+ 1\b12\b2.\b.1\b11\b12\b2.\b. u\bun\bns\bse\bet\bt/\b/a\ban\bnn\bnt\bta\bal\blk\bk
+
+ u\bun\bns\bse\bet\bt/\b/a\ban\bnn\bnt\bta\bal\blk\bk Stop talk like announce messages on your terminal
+
+
+ The announce system on legacy cluster nodes is used as a talk
+ substitute because the network is so poorly connected. If you:
+
+
+
+ unset/anntalk
+
+
+
+ you will suppress several of these announces, you may miss the odd
+ useful one as well, but you would probably miss them anyway in the
+ welter of useless ones.
+
+
+
+ set/anntalk
+
+
+
+ allows you to see them again. This is the default.
+
+ 1\b12\b2.\b.1\b11\b13\b3.\b. u\bun\bns\bse\bet\bt/\b/b\bbe\bee\bep\bp
+
+ u\bun\bns\bse\bet\bt/\b/b\bbe\bee\bep\bp Stop beeps for DX and other messages on your terminal
+
+
+
+ 1\b12\b2.\b.1\b11\b14\b4.\b. u\bun\bns\bse\bet\bt/\b/d\bdx\bx
+
+ u\bun\bns\bse\bet\bt/\b/d\bdx\bx Stop DX messages coming out on your terminal
+
+
+
+ 1\b12\b2.\b.1\b11\b15\b5.\b. u\bun\bns\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bd
+
+ u\bun\bns\bse\bet\bt/\b/d\bdx\bxg\bgr\bri\bid\bd Stop QRA Grid Squares on the end of DX announcements
+
+
+ A standard feature which is enabled in version 1.43 and above is that
+ if the spotter's grid square is known it is output on the end of a DX
+ announcement (there is just enough room). Some user programs cannot
+ cope with this. You can use this command to reset (or set) this
+ feature.
+
+ 1\b12\b2.\b.1\b11\b16\b6.\b. u\bun\bns\bse\bet\bt/\b/e\bec\bch\bho\bo
+
+ u\bun\bns\bse\bet\bt/\b/e\bec\bch\bho\bo Stop the cluster echoing your input
+
+
+ If you are connected via a telnet session, different implimentations
+ of telnet handle echo differently depending on whether you are
+ connected via port 23 or some other port. You can use this command to
+ change the setting appropriately.
+
+ The setting is stored in your user profile.
+
+ YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
+
+ 1\b12\b2.\b.1\b11\b17\b7.\b. u\bun\bns\bse\bet\bt/\b/e\bem\bma\bai\bil\bl
+
+ u\bun\bns\bse\bet\bt/\b/e\bem\bma\bai\bil\bl Stop personal msgs being forwarded by email
+
+
+ If any personal messages come in for your callsign then you can use
+ these commands to control whether they are forwarded onto your email
+ address. To enable the forwarding do something like:-
+
+
+
+ SET/EMAIL mike.tubby@somewhere.com
+
+
+
+ You can have more than one email address (each one separated by a
+ space). Emails are forwarded to all the email addresses you specify.
+
+ You can disable forwarding by:-
+
+
+
+ UNSET/EMAIL
+
+
+
+ 1\b12\b2.\b.1\b11\b18\b8.\b. u\bun\bns\bse\bet\bt/\b/h\bhe\ber\bre\be
+
+ u\bun\bns\bse\bet\bt/\b/h\bhe\ber\bre\be Tell the system you are absent from your terminal
+
+
+
+ 1\b12\b2.\b.1\b11\b19\b9.\b. u\bun\bns\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo
+
+ u\bun\bns\bse\bet\bt/\b/l\blo\bog\bgi\bin\bni\bin\bnf\bfo\bo Inform when a station logs out locally
+
+
+
+ 1\b12\b2.\b.1\b12\b20\b0.\b. u\bun\bns\bse\bet\bt/\b/p\bpr\bri\biv\bvi\bil\ble\beg\bge\be
+
+ u\bun\bns\bse\bet\bt/\b/p\bpr\bri\biv\bvi\bil\ble\beg\bge\be Remove any privilege for this session
+
+
+ You can use this command to 'protect' this session from unauthorised
+ use. If you want to get your normal privilege back you will need to
+ either logout and login again (if you are on a console) or use the
+ SYSOP command.
+
+ 1\b12\b2.\b.1\b12\b21\b1.\b. u\bun\bns\bse\bet\bt/\b/p\bpr\bro\bom\bmp\bpt\bt
+
+ u\bun\bns\bse\bet\bt/\b/p\bpr\bro\bom\bmp\bpt\bt Set your prompt back to default
+
+
+ This command will set your user prompt to exactly the string that you
+ say. The point of this command to enable a user to interface to
+ programs that are looking for a specific prompt (or else you just want
+ a different fixed prompt).
+
+
+
+ SET/PROMPT clx >
+
+
+
+ UNSET/PROMPT will undo the SET/PROMPT command and set you prompt back
+ to normal.
+
+ 1\b12\b2.\b.1\b12\b22\b2.\b. u\bun\bns\bse\bet\bt/\b/t\bta\bal\blk\bk
+
+ u\bun\bns\bse\bet\bt/\b/t\bta\bal\blk\bk Stop TALK messages coming out on your terminal
+
+
+
+ 1\b12\b2.\b.1\b12\b23\b3.\b. u\bun\bns\bse\bet\bt/\b/w\bwc\bcy\by
+
+ u\bun\bns\bse\bet\bt/\b/w\bwc\bcy\by Stop WCY messages coming out on your terminal
+
+
+
+ 1\b12\b2.\b.1\b12\b24\b4.\b. u\bun\bns\bse\bet\bt/\b/w\bww\bwv\bv
+
+ u\bun\bns\bse\bet\bt/\b/w\bww\bwv\bv Stop WWV messages coming out on your terminal
+
+
+
+ 1\b12\b2.\b.1\b12\b25\b5.\b. u\bun\bns\bse\bet\bt/\b/w\bwx\bx
+
+ u\bun\bns\bse\bet\bt/\b/w\bwx\bx Stop WX messages coming out on your terminal
+
+
+
+ 1\b12\b2.\b.1\b12\b26\b6.\b. w\bwh\bho\bo
+
+ w\bwh\bho\bo Show who is physically connected
+
+
+
+ This is a quick listing that shows which callsigns are connected and
+ what sort of connection they have
+
+ 1\b12\b2.\b.1\b12\b27\b7.\b. w\bwx\bx <\b<t\bte\bex\bxt\bt>\b>
+
+ w\bwx\bx <\b<t\bte\bex\bxt\bt>\b> Send a weather message to local users
+
+
+
+ 1\b12\b2.\b.1\b12\b28\b8.\b. w\bwx\bx f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b>
+
+ w\bwx\bx f\bfu\bul\bll\bl <\b<t\bte\bex\bxt\bt>\b> Send a weather message to all cluster users
+
+
+
projects / spider.git / blobdiff