1 The DXSpider User Manual v1.50
2 Ian Maude, G0VGS, (g0vgs@gb7mbc.net)
3 September 2002 revision 0.1
5 A complete reference for users of the DXSpider DXCluster program.
6 ______________________________________________________________________
13 1.1 What is a DX Cluster?
14 1.2 So what is DXSpider?
16 2. Logins and logouts.
22 3. Setting your personal details.
23 4. Getting and posting DX.
27 5. Headings and propagation
33 6.1 Making announcements.
34 6.2 Listing announcements.
39 9.1 The "directory" command.
45 10. Filtering (From version 1.45)
46 10.1 General filter rules
49 10.4 Advanced filtering
51 11. Hints, tips and common questions.
52 12. The DXSpider command reference
95 12.43 show/configuration
96 12.44 show/configuration/node
120 ______________________________________________________________________
122 1
\b1.
\b. I
\bIn
\bnt
\btr
\bro
\bod
\bdu
\buc
\bct
\bti
\bio
\bon
\bn
124 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?
126 A DX Cluster is a packet node where DX chasers on any band or mode can
127 post rare or interesting stations that they have worked or heard. Of
128 course other people are doing the same thing too, so you can find new
129 DX as well as telling others about the stations you have worked.
130 Clusters tend to be linked to each other so that the amount of people
131 using them is increased, thereby increasing the amount of posted DX.
132 Other information can be found on clusters such as on-line call books,
133 mail etc. You can talk to other stations connected to the cluster
134 network too, in real time, whether at the node you are logged into or
135 on another node connected to the network. You can also use converse
136 mode, where several stations can talk to each other in the same way.
137 Of course, the DX is still posted to you all the while!
140 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?
142 PacketCluster nodes have been around since roughly 1985. The original
143 PacketCluster idea came from Dick Newell, AK1A, and ran under DOS. In
144 about 1992 Dick stopped the development of the PacketCluster software
145 for amateur radio. Many systems are still using this relatively old
148 There are several new compatible cluster programs around now,
149 including DXSpider. DXSpider is a clone of PacketCluster software
150 that runs under several operating systems including Linux and Windows.
151 Linux is fast becoming the choice for amateur radio stations because
152 of it's flexibility, reliability and the lack of the memory
153 limitations of DOS. Linux supports multitasking and is also
154 multiuser. It has support for AX25, ROSE, NetROM and TCPIP built in,
155 making it the ideal choice for amateur radio. It is also totally
158 DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
159 exercise in perl programming. It has developed rapidly and today is a
160 very powerful cluster program. It was designed to be totally
161 compatible with the AK1A program, although several commands have been
162 extended to improve functionality.
164 This manual is designed to help you become familiar with the commands
165 that DXSpider supports and to help you get the best from the program
166 so you can enjoy working that rare DX! As DXSpider is being improved
167 all the time, commands will be added as time goes by, so make sure you
168 have the most upto date version of this manual. The latest version
169 will always be included with the cluster program so if you are unsure,
170 simply ask your sysop. The manual will also be available on the
175 2
\b2.
\b. L
\bLo
\bog
\bgi
\bin
\bns
\bs a
\ban
\bnd
\bd l
\blo
\bog
\bgo
\bou
\but
\bts
\bs.
\b.
177 You might not think that there is a lot of point of including a
178 section on how to log in and out of DXSpider. However, you would be
179 suprised at the difficulties some people have in simply getting in and
182 There are several ways a login might be achieved, dependant on how the
183 sysop has DXSpider configured. It is impossible for me to cover all
184 variations but here are the basic ones.
187 2
\b2.
\b.1
\b1.
\b. A
\bAX
\bX2
\b25
\b5 l
\blo
\bog
\bgi
\bin
\bns
\bs.
\b.
189 Simplicity itself. The usual C
\bCO
\bON
\bNN
\bNE
\bEC
\bCT
\bT command will log you straight
190 into the cluster and you will not have to do anything else.
191 Obviously, you will have to connect to the correct callsign. Some
192 nodes use an SSID with their call so you would have to add that.
194 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
203 2
\b2.
\b.2
\b2.
\b. N
\bNe
\bet
\btr
\bro
\bom
\bm l
\blo
\bog
\bgi
\bin
\bns
\bs.
\b.
205 There are several possibilities here, dependant on how the sysop has
206 configured his system. If you are connecting via netrom then you are
207 most probably connecting from another station. Listing the nodes in
208 that station with the N
\bNO
\bOD
\bDE
\bES
\bS command will tell you what callsign or
209 netrom alias to connect to. Then just issue the connect command from
210 there. It is possible that the netrom alias may connect you to a node
211 with an alias for the cluster, such as DXC. Just type this and you
214 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
221 2
\b2.
\b.3
\b3.
\b. T
\bTe
\bel
\bln
\bne
\bet
\bt l
\blo
\bog
\bgi
\bin
\bns
\bs.
\b.
223 With telnet connections, the source callsign is not seen by DXSpider,
224 so you will be asked to login with your callsign. To telnet to
225 DXSpider, you would connect to a specific port. There is no standard
226 at the moment for a cluster telnet port but ask the sysop if you are
229 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
237 All the above are possible ways of connecting to a DXSpider cluster.
238 You may have some or all of these available to you. There may be one
239 or two additional ways to connect dependant on the network local to
240 you. However I am sure you get the idea.
243 2
\b2.
\b.4
\b4.
\b. L
\bLo
\bog
\bgo
\bou
\but
\bts
\bs.
\b.
245 Logging out can be done by simply issuing the standard B
\bBY
\bYE
\bE command.
247 You could also send a disconnect if you are using AX25, or a C
\bCL
\bLO
\bOS
\bSE
\bE
248 command if you are connected via telnet. If you do not log out
249 gracefully using one of the above commands, you may find you are
250 unable to get a full connect next time. This may also happen if a
251 netrom connection drops. You may get connected, but nothing else will
252 happen because the program thinks you are still connected and will not
253 let you connect twice under the same call. However you could
254 reconnect by adding a number to the end of your call, for example
255 G0YLM-2. This can be done by either altering your MYCALL setting in
256 the TNC or by altering your program configuration.
260 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.
262 Once logged in to the cluster, you should set your details so that
263 anybody who wishes to contact you can find out who and where you are.
264 There are four items to set, your name, qth, location and home node.
265 Setting these details also allows the use of the SHOW/HEADING and
266 SHOW/SUN commands from within the cluster. Unless you set your QTH
267 and location, these commands cannot function. Once you have set your
268 name, DXSpider will greet you with it next time you login. Your QTH
269 setting is where you live and it is a good idea to add your locator to
270 this as the location setting is converted to latitude and longitude
271 once inputted. You can actually set your location in
272 latitude/longitude or as a locator. Setting your home node will tell
273 the program where you wish mail to be sent to you.
275 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
280 set/qth Morecambe, Lancashire IO84NB
281 set/location 48 34 n 12 12 e
287 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.
289 When all is said and done, this is the main function of a DX cluster.
290 In its simplest form you can just connect to the node and you will
291 start to receive DX spots almost immediately! You can check on recent
292 postings in either a general manner or on a particular band or mode.
293 You can even check DX by callsign or a fragment of a callsign. Of
294 course, once you get the hang of things, it is expected that you start
295 posting some yourself! After all, there would be no clusters if
296 people did not post DX and you get the added thrill of the hunt!
299 4
\b4.
\b.1
\b1.
\b. R
\bRe
\bec
\bce
\bei
\biv
\bvi
\bin
\bng
\bg D
\bDX
\bX.
\b.
301 As we have already said, it is possible just to connect to the cluster
302 and you will receive spots automatically. However, you may wish to
303 check on spots just posted. Maybe you wish to see if a particular
304 band is open or if a certain callsign is active, perhaps a DXpedition.
305 The command to do this is S
\bSH
\bHO
\bOW
\bW/
\b/D
\bDX
\bX. Without any other arguments, this
306 command will output the last 10 spots posted. It is possible to look
307 at more than this, for example the last 20 or 50 spots, by adding the
308 number to the command. You can make it even more specific by adding a
309 band in either wavelength or frequency, and/or any additional
310 information such as QSL details.
312 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
322 will show the last 10, 5 and 20 spots received by the cluster
325 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs
334 will show the last 5, 10 or 20 spots on 20 metres only.
336 It is also possible to check for certain callsigns, or fragments of
337 callsigns in the same way.
339 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
348 would show the last 5 or 10 dx spots containing the callsign g0vgs.
351 You can check for DX by offset and also by specifying a comment to
354 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
364 would show the spots that arrived between 30 and 40 spots ago and any
365 spots with the word _
\bi_
\bo_
\bt_
\ba in the comment field. The case of the
366 comment is not important.
368 Checking DX posted on a certain day is possible too. All you have to
369 do here is to specify how many days ago it was like this ...
371 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
379 It is of course possible to specify multiple arguments.
381 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
385 show/dx 20 prefix 9a on vhf day 30
389 This would show the last 20 spots posted by or about calls with the
390 prefix 9a on vhf 30 days ago.
392 As you can see the S
\bSH
\bHO
\bOW
\bW/
\b/D
\bDX
\bX command is very flexible, so if you are not
393 sure whether something will work or not, try it and see! More
394 information can be found in the Command Set section.
396 4
\b4.
\b.2
\b2.
\b. P
\bPo
\bos
\bst
\bti
\bin
\bng
\bg D
\bDX
\bX.
\b.
398 To post DX you use the D
\bDX
\bX command. The syntax is shown below.
400 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
404 dx (frequency) (callsign) (remarks)
408 Where frequency is in kilohertz and the callsign is the callsign of
409 the station you have worked or heard, (ie not your own callsign!).
410 The remarks section allows you to add information like the operators
411 name or perhaps a location. Actually DXSpider will allow the
412 frequency and callsign fields to be entered in any order.
414 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
418 dx 14004 pa3ezl OP Aurelio 599
422 In fact, all the following will give the same result...
426 dx 14004 pa3ezl OP Aurelio 599
427 dx pa3ezl 14004 OP Aurelio 599
428 dx pa3ezl 14.004 OP Aurelio 599
432 This posting, or callout as it is known, will be forwarded to all
433 other connected stations both at the cluster you are connected to and
434 other active clusters in the network. The callout will also be sent
435 to you as proof of receipt.
438 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
440 There are three commands in DXSpider to help you get the best DX
441 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
442 commands will only work for you if you have entered your personal
443 details. They use your entered location as a reference, so if you
444 have not entered it or have entered it incorrectly they will not
445 return the correct information.
448 5
\b5.
\b.1
\b1.
\b. S
\bSu
\bun
\bn
450 The S
\bSH
\bHO
\bOW
\bW/
\b/S
\bSU
\bUN
\bN command can be used in three different ways. It can be
451 used to show sunrise and sunset times for your own station, a
452 particular callsign or a prefix.
454 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
462 The output from this would look something like this ..
467 Location Rise Set Azim Elev
468 G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
476 would look like this ...
481 Location Rise Set Azim Elev
482 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
486 You can also specify multiple arguments like this ...
490 sh/sun gw4veq 5b4ab zs
494 and then the output would look like this ...
498 sh/sun gw4veq 5b4ab zs
499 Location Rise Set Azim Elev
500 GW4VEQ Brungwran, Isle of Anglesey IO 07:14Z 17:48Z 204.9 24.9
501 5B Cyprus-5B 04:23Z 15:40Z 244.5 18.3
502 ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
503 ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
504 ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
508 5
\b5.
\b.2
\b2.
\b. M
\bMo
\boo
\bon
\bn
510 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.
511 This program however, calculates the rise and set times of the moon
512 for a prefix or callsign, together with the current azimuth and
513 elevation of the sun at these locations.
515 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
523 The output from this command would look like this ..
528 Location Rise Set Azim Elev RGain dB
529 EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
533 You can see that the output is similar to the S
\bSH
\bHO
\bOW
\bW/
\b/S
\bSU
\bUN
\bN command, with
534 slightly different fields.
537 5
\b5.
\b.3
\b3.
\b. H
\bHe
\bea
\bad
\bdi
\bin
\bng
\bg
539 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
540 S
\bSH
\bHO
\bOW
\bW/
\b/M
\bMO
\bOO
\bON
\bN commands but outputs beam headings for a specified callsign
541 or prefix. Reciprocal beam headings are also calculated.
543 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be
551 The output from this command would look like this ..
556 ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
557 ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
558 ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
559 ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
563 6
\b6.
\b. A
\bAn
\bnn
\bno
\bou
\bun
\bnc
\bce
\bem
\bme
\ben
\bnt
\bts
\bs.
\b.
565 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.
567 Occasionally, you may wish to post something that does not fall into
568 the normal parameters for a DX callout. You may wish to tell
569 everybody connected that 10 FM is open for example, or ask if anyone
570 knows the QSL manager for a certain callsign etc. You can do this
571 using the A
\bAN
\bNN
\bNO
\bOU
\bUN
\bNC
\bCE
\bE command.
573 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
576 announce 10 FM is open in IO84NB to europe.
580 That would let everyone know locally that this was the case, however
581 it would not be forwarded to other nodes connected. To send
582 announcements to other connected nodes as well, you would use the F
\bFU
\bUL
\bLL
\bL
585 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
589 announce full Anyone seen EA7WA today?
593 Be cautious in your use of announce full. There are many other tools
594 available to get the information you require and the judicious use of
595 this command is frowned upon as it creates a great deal of traffic
599 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.
601 You can list previous announcements in the standard format with the
602 S
\bSH
\bHO
\bOW
\bW command. As before you can list just the last 5 or as many as
605 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
610 show/announcements 10
614 7
\b7.
\b. N
\bNo
\bod
\bde
\bes
\bs a
\ban
\bnd
\bd u
\bus
\bse
\ber
\brs
\bs.
\b.
616 You can check which nodes are connected in the network, who is logged
617 on locally, who is logged on at all the nodes or even just one node in
618 particular. This is handy if you wish to see whether a friend is
619 connected at the node they use. To see who is connected to the nodes,
620 the S
\bSH
\bHO
\bOW
\bW/
\b/C
\bCO
\bON
\bNF
\bFI
\bIG
\bGU
\bUR
\bRA
\bAT
\bTI
\bIO
\bON
\bN command is used.
622 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
627 show/configuration/nodes
628 show/configuration (node_call)
629 show/configuration (prefix)
633 The first of our three examples would output something like this,
642 GB7BIG (GD0TEP) GD3UMW
643 GB7BPQ (G0INA) G0RCI G3AKU G3OCA
645 GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
646 G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
649 GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
650 G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
652 (GB7DXG) GU6EFB GU7DHI
653 GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
655 GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
660 You will notice that EI5TCR is showing only that it has 7 users and
661 not giving the actual callsigns. This means that this node is on a
662 limited protocol of some kind, probably because of a contest situation
663 where slow radio links can block up and fail if too much information
664 is sent between nodes.
666 The second example would just show the nodes connected in the network,
673 GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
674 GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
675 GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
676 GB7YDX KL7G N2TLY (ON0DXK)
677 GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
684 If we insert the node_call pi4tue-8 into the third example, then this
690 PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
691 F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
692 ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
693 PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
698 As you can see, only the users of the requested node are shown.
700 You can also use a prefix to show only a group of nodes. For example
701 you may only wish to see who is connected to the nodes in the UK. To
702 do this simply use a prefix like this ...
705 show/configuration gb7
709 To show the locally connected users, the S
\bSH
\bHO
\bOW
\bW/
\b/U
\bUS
\bSE
\bER
\bRS
\bS command is used
711 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
719 The output of this command would look like this,
723 Callsigns connected to GB7MBC
724 G0JHC G0NEI G0VGS G0VGS-2 G0YLM
729 8
\b8.
\b. T
\bTa
\bal
\blk
\bk m
\bmo
\bod
\bde
\be.
\b.
731 You can send a single comment or start a dedicated talk session to
732 another user by using the T
\bTA
\bAL
\bLK
\bK command.
735 Talk mode is used to send a one line comment or greeting to a specific
736 user connected either at your node or another in the network. You can
737 also enter into a dedicated talk session with another user. Talks
738 will be automatically forwarded to other nodes if the station you are
739 talking to is not connected locally. You can find out who is
740 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
743 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
747 talk g0rdi Having a good day Iain?
751 This example would send the line "Having a good day Iain?" to the user
752 g0rdi but would leave you in normal mode.
757 Entering Talkmode, /EX to end, /<cmd> to run a command
761 As you can see, you can still run commands whilst in talk mode.
762 Simply prefix the command with a / like /sh/dx and you will get the
763 expected output. If the user is connected to another node, you may
764 have to use a slightly extended version of the T
\bTA
\bAL
\bLK
\bK command.
772 To exit talk mode, you issue the command /
\b/e
\bex
\bx.
774 Whilst in talk mode you will still receive DX spots. This means that
775 you can chat to a friend whilst working DX.
778 9
\b9.
\b. M
\bMa
\bai
\bil
\bl.
\b.
780 You can send and receive both personal mail and bulletins with
781 DXSpider quite easily.
784 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.
786 To list mail you would use the D
\bDI
\bIR
\bRE
\bEC
\bCT
\bTO
\bOR
\bRY
\bY command. On its own, this
787 command will output the last ten messages received by the node, either
788 to or from yourself or bulletins such as "DX" and "ALL". As with
789 other commands you can display more by specifying a number with the
790 command. You should be aware that Spider will accept these commands
791 by separating with either a slash or a space, so _
\bd_
\bi_
\br _
\bn_
\be_
\bw and _
\bd_
\bi_
\br_
\b/_
\bn_
\be_
\bw
792 work in the same way.
794 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
804 Of course most of the time you will only want to list new mail sent to
805 you personally since your last login. However you might also like to
806 check for general mail received by the node. In fact if there is new
807 mail for you, the cluster will tell you when you login. You will also
808 be informed if new mail arrives for you during the time you are logged
809 in. Mail is not only sent to callsigns though. Mail can also be sent
810 to subjects like "all" or "local" or "dx" etc. You can treat these
811 bulletins in the same way as personal mail with the directory command.
813 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
821 directory/from <call>
825 The last option will only show mail from a callsign if it was sent to
826 you personally or was sent as a bulletin. There are some additional
827 commands and these can be found in the DXSpider Command Reference
831 9
\b9.
\b.2
\b2.
\b. R
\bRe
\bea
\bad
\bdi
\bin
\bng
\bg m
\bma
\bai
\bil
\bl.
\b.
833 The output of the D
\bDI
\bIR
\bRE
\bEC
\bCT
\bTO
\bOR
\bRY
\bY command could be something like this.
838 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
839 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
840 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
841 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
842 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
843 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
844 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
845 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
846 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
847 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
848 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
852 The first column is the actual message number. If the message is a
853 personal one to you, you will see a letter 'p' after this number. If
854 the message has been read, there will be a '-' between the message
855 number and the 'p'. This only works for personal messages. The next
856 column shows the file size of the message. The third column shows the
857 address the message was sent to and the next column shows who sent it.
858 The rest is fairly self-explanatory.
860 Reading a message is as simple as typing read, followed by the message
861 number that you wish to read.
863 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
871 will read message number 25. However the mail will be displayed in
872 it's entirety unless you specify a page length. You can set your page
873 length to any number you like and when the message reaches that number
874 of lines you will get a prompt giving you options.
876 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
884 9
\b9.
\b.3
\b3.
\b. S
\bSe
\ben
\bnd
\bdi
\bin
\bng
\bg m
\bma
\bai
\bil
\bl.
\b.
886 Sending mail is done in the time honoured way. First you specify a
887 recipient for the message, then you will be prompted for a subject.
888 Once you have done this you will be asked to type your message.
889 Please remember that there is no automatic word wrap, so unless you
890 are using a client that wraps lines automatically, remember to hit
891 return at the end of each line.
893 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
898 Enter Subject (30 characters):
900 Enter Message /EX to send or /ABORT to exit
902 Just a quick note to say that I can make Thursday after all. The
903 appointment I had has cancelled so we are go!
909 At this point you can either hit return and enter /ex to send the
910 message or use /abort at any time to abort it. You can now display
911 the message in the normal way. There are several send options and
912 these are listed in the Command Set section. These include sending
913 mail to several recipients and asking for a return receipt.
917 9
\b9.
\b.4
\b4.
\b. R
\bRe
\bep
\bpl
\bly
\byi
\bin
\bng
\bg t
\bto
\bo m
\bma
\bai
\bil
\bl.
\b.
919 If mail is addressed to you or to a bulletin address, you can use the
920 R
\bRE
\bEP
\bPL
\bLY
\bY command to reply to it. Using this command, the subject will be
921 automatically set for you as "Re: subject", whatever the subject was.
923 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
931 9
\b9.
\b.5
\b5.
\b. D
\bDe
\bel
\ble
\bet
\bti
\bin
\bng
\bg m
\bma
\bai
\bil
\bl
933 To delete a message, you use the _
\bd_
\be_
\bl_
\be_
\bt_
\be command. You can only delete
934 messages sent to or received by yourself. Bulletins are dealt with
935 automatically or by the sysop.
938 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)
940 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
942 Upto v1.44 it was not possible for the user to set their own filters.
943 From v1.45 though that has all changed. It is now possible to set
944 filters for just about anything you wish. If you have just updated
945 from an older version of DXSpider you will need to update your new
946 filters. You do not need to do anything with your old filters, they
947 will be renamed as you update.
950 There are 3 basic commands involved in setting and manipulating
951 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
952 generally at filtering. There are a number of things you can filter in
953 the DXSpider system. They all use the same general mechanism.
956 In general terms you can create a 'reject' or an 'accept' filter which
957 can have up to 10 lines in it. You do this using, for example ...
966 where ..... are the specific commands for that type of filter. There
967 are filters for spots, wwv, announce, wcy and (for sysops) connects.
968 See each different accept or reject command reference for more
971 There is also a command to clear out one or more lines in a filter.
981 There is clear/xxxx command for each type of filter.
984 and you can check that your filters have worked by the command ...
992 For now we are going to use spots for the examples, but you can apply
993 the same principles to all types of filter.
996 1
\b10
\b0.
\b.2
\b2.
\b. T
\bTy
\byp
\bpe
\bes
\bs o
\bof
\bf f
\bfi
\bil
\blt
\bte
\ber
\br
998 There are two main types of filter, _
\ba_
\bc_
\bc_
\be_
\bp_
\bt or _
\br_
\be_
\bj_
\be_
\bc_
\bt. You can use
999 either to achieve the result you want dependent on your own preference
1000 and which is more simple to do. It is pointless writing 8 lines of
1001 reject filters when 1 accept filter would do the same thing! Each
1002 filter has 10 lines (of any length) which are tried in order. If a
1003 line matches then the action you have specified is taken (ie reject
1004 means ignore it and accept means take it)
1007 If you specify reject filters, then any lines that arrive that match
1008 the filter will be dumped but all else will be accepted. If you use
1009 an accept filter, then ONLY the lines in the filter will be accepted
1010 and all else will be dumped. For example if you have a single line
1011 _
\ba_
\bc_
\bc_
\be_
\bp_
\bt filter ...
1015 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1019 then you will _
\bO_
\bN_
\bL_
\bY get VHF spots _
\bf_
\br_
\bo_
\bm or _
\bt_
\bo CQ zones 14, 15 and 16.
1022 If you set a reject filter like this ...
1026 reject/spots on hf/cw
1030 Then you will get everything _
\bE_
\bX_
\bC_
\bE_
\bP_
\bT HF CW spots. You could make this
1031 single filter even more flexible. For example, if you are interested
1032 in IOTA and will work it even on CW even though normally you are not
1033 interested in CW, then you could say ...
1037 reject/spots on hf/cw and not info iota
1041 But in that case you might only be interested in iota and say:-
1045 accept/spots not on hf/cw or info iota
1049 which achieves exactly the same thing. You should choose one or the
1050 other until you are comfortable with the way it works. You can mix
1051 them if you wish (actually you can have an accept AND a reject on the
1052 same line) but don't attempt this until you are sure you know what you
1056 You can arrange your filter lines into logical units, either for your
1057 own understanding or simply convenience. Here is an example ...
1061 reject/spots 1 on hf/cw
1062 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
1066 What this does is to ignore all HF CW spots and also rejects any spots
1067 on VHF which don't either originate or spot someone in Europe.
1068 This is an example where you would use a line number (1 and 2 in this
1069 case), if you leave the digit out, the system assumes '1'. Digits
1070 '0'-'9' are available. This make it easier to see just what filters
1071 you have set. It also makes it more simple to remove individual
1072 filters, during a contest for example.
1075 You will notice in the above example that the second line has
1076 brackets. Look at the line logically. You can see there are 2
1077 separate sections to it. We are saying reject spots that are VHF or
1078 above _
\bA_
\bP_
\bA_
\bR_
\bT from those in zones 14, 15 and 16 (either spotted there or
1079 originated there). If you did not have the brackets to separate the 2
1080 sections, then Spider would read it logically from the front and see a
1081 different expression entirely ...
1085 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
1089 The simple way to remember this is, if you use OR - use brackets.
1090 Whilst we are here CASE is not important. 'And BY_Zone' is just the
1091 same as 'and by_zone'.
1093 As mentioned earlier, setting several filters can be more flexible
1094 than simply setting one complex one. Doing it in this way means that
1095 if you want to alter your filter you can just redefine or remove one
1096 or more lines of it or one line. For example ...
1100 reject/spots 1 on hf/ssb
1104 would redefine our earlier example, or
1112 To remove all the filter lines in the spot filter ...
1120 1
\b10
\b0.
\b.3
\b3.
\b. F
\bFi
\bil
\blt
\bte
\ber
\br o
\bop
\bpt
\bti
\bio
\bon
\bns
\bs
1122 You can filter in several different ways. The options are listed in
1123 the various helpfiles for accept, reject and filter.
1127 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
1129 Once you are happy with the results you get, you may like to
1133 The previous example that filters hf/cw spots and accepts vhf/uhf
1134 spots from EU can be written with a mixed filter, for example ...
1140 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
1144 Note that the first filter has not been specified with a number. This
1145 will automatically be assumed to be number 1. In this case, we have
1146 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
1147 _
\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
1148 _
\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
1149 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
1153 It was mentioned earlier that after a reject test that doesn't match,
1154 the default for following tests is 'accept', the reverse is true for
1155 'accept'. In the example what happens is that the reject is executed
1156 first, any non hf/cw spot is passed to the accept line, which lets
1157 through everything else on HF. The next filter line lets through just
1158 VHF/UHF spots from EU.
1162 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.
1164 Q
\bQ.
\b.These commands seem very long! Can I shorten them?
1166 A
\bA.
\b.Of course you can and the usual abbreviations work. If you are
1169 Q
\bQ.
\b.I am not sure if this command is correct. Can I cause any harm if I
1172 A
\bA.
\b.Do not be afraid to try a command to see if it will work, at the
1173 worst you will get an error message. If you require any help on a
1174 command, just type help followed by the command you want help on.
1175 Look at the "DXSpider Command Reference" section to see what help can
1178 Q
\bQ.
\b.How should I use the announce command?
1180 A
\bA.
\b.With respect. Use the command by all means, but please only use the
1181 "full" extension if absolutely necessary. It can create a LOT of
1182 messages passing between clusters.
1184 Q
\bQ.
\b.I like to be working in the shack while logged into the cluster but
1185 I can't be looking at the screen all the time. How can I be alerted
1186 when anything happens?
1188 A
\bA.
\b.Use the S
\bSE
\bET
\bT/
\b/B
\bBE
\bEE
\bEP
\bP command. You can find information on this in the
1189 "DXSpider Command Reference" section.
1192 Q
\bQ.
\b.I got disconnected from the cluster and now I can't log back in
1193 again. What is wrong?
1195 A
\bA.
\b.Probably the cluster thinks you are still logged on and will not let
1196 you reconnect using the same call to prevent loops. Try logging on
1197 again adding an ssid to your callsign as DXSpider treats G0YLM and
1198 G0YLM-1 as different users.
1200 Q
\bQ.
\b.How do I know if I have got the latest version of this user manual?
1202 A
\bA.
\b.The latest and greatest will always be on the Website. It will also
1203 be included with every release of DXSpider. As always, if unsure, ask
1204 your sysop what version number is the latest.
1207 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
1209 Below is a complete list of commands available from the cluster
1210 prompt. These are listed below in alphabetical order.
1213 1
\b12
\b2.
\b.1
\b1.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be
1215 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
1218 Create an 'accept this announce' line for a filter.
1220 An accept filter line means that if the announce matches this filter
1221 it is passed onto the user. See HELP FILTERS for more info. Please
1222 read this to understand how filters work - it will save a lot of grief
1225 You can use any of the following things in this line:-
1229 info <string> eg: iota or qsl
1230 by <prefixes> eg: G,M,2
1232 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1233 origin_itu <numbers>
1234 origin_zone <numbers>
1239 wx 1 filter WX announces
1240 dest <prefixes> eg: 6MUK,WDX (distros)
1249 acc/ann 2 by_zone 14,15,16
1250 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1260 This filter would only allow announces that were posted buy UK
1261 stations. You can use the tag 'all' to accept everything eg:
1269 but this probably for advanced users...
1272 1
\b12
\b2.
\b.2
\b2.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs
1274 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
1277 Create an 'accept this spot' line for a filter.
1280 An accept filter line means that if the spot matches this filter it is
1281 passed onto the user. See HELP FILTERS for more info. Please read this
1282 to understand how filters work - it will save a lot of grief later on.
1284 You can use any of the following things in this line:-
1288 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1289 on <range> same as 'freq'
1290 call <prefixes> eg: G,PA,HB9
1291 info <string> eg: iota or qsl
1293 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1304 For frequencies, you can use any of the band names defined in
1305 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1306 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1307 this is more efficient than saying simply: freq HF (but don't get too
1315 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1318 You can use the tag 'all' to accept everything, eg:
1326 but this probably for advanced users...
1329 1
\b12
\b2.
\b.3
\b3.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bwc
\bcy
\by
1331 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
1334 It is unlikely that you will want to do this, but if you do then you
1335 can filter on the following fields:-
1339 by <prefixes> eg: G,M,2
1341 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1342 origin_itu <numbers>
1343 origin_zone <numbers>
1351 There are no examples because WCY Broadcasts only come from one place
1352 and you either want them or not (see UNSET/WCY if you don't want
1355 This command is really provided for future use.
1357 See HELP FILTER for information.
1360 1
\b12
\b2.
\b.4
\b4.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv
1362 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
1365 It is unlikely that you will want to do this, but if you do then you
1366 can filter on the following fields:-
1370 by <prefixes> eg: G,M,2
1372 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1373 origin_itu <numbers>
1374 origin_zone <numbers>
1385 accept/wwv by_zone 4
1389 is probably the only useful thing to do (which will only show WWV
1390 broadcasts by stations in the US).
1392 See HELP FILTER for information.
1395 1
\b12
\b2.
\b.5
\b5.
\b. a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be
1397 a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send an announcement to local users
1400 Send an announcement to LOCAL users only, where <text> is the text of
1401 the announcement you wish to broadcast
1404 1
\b12
\b2.
\b.6
\b6.
\b. a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be f
\bfu
\bul
\bll
\bl
1406 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
1409 This command will send your announcement across the whole cluster
1413 1
\b12
\b2.
\b.7
\b7.
\b. a
\bap
\bpr
\bro
\bop
\bpo
\bos
\bs
1415 a
\bap
\bpr
\bro
\bop
\bpo
\bos
\bs <
\b<s
\bst
\btr
\bri
\bin
\bng
\bg>
\b> Search the help database
1418 Search the help database for <string> (it isn't case sensitive), and
1419 print the names of all the commands that may be relevant.
1422 1
\b12
\b2.
\b.8
\b8.
\b. b
\bby
\bye
\be
1424 b
\bby
\bye
\be Exit from the cluster
1427 This will disconnect you from the cluster
1430 1
\b12
\b2.
\b.9
\b9.
\b. c
\bcl
\ble
\bea
\bar
\br/
\b/s
\bsp
\bpo
\bot
\bts
\bs
1432 c
\bcl
\ble
\bea
\bar
\br/
\b/s
\bsp
\bpo
\bot
\bts
\bs [
\b[1
\b1|
\b|a
\bal
\bll
\bl]
\b] Clear a spot filter line
1435 This command allows you to clear (remove) a line in a spot filter or
1436 to remove the whole filter.
1438 If you have a filter:-
1443 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1454 you will be left with:-
1458 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1470 the filter will be completely removed.
1473 1
\b12
\b2.
\b.1
\b10
\b0.
\b. d
\bdb
\bba
\bav
\bva
\bai
\bil
\bl
1475 d
\bdb
\bba
\bav
\bva
\bai
\bil
\bl Show a list of all the databases in the system
1478 The title says it all really, this command lists all the databases
1479 defined in the system. It is also aliased to SHOW/COMMAND.
1482 1
\b12
\b2.
\b.1
\b11
\b1.
\b. d
\bdb
\bbs
\bsh
\bho
\bow
\bw
1484 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
1487 This is the generic user interface to the database to the database
1488 system. It is expected that the sysop will add an entry to the local
1489 Aliases file so that users can use the more familiar AK1A style of
1498 but if he hasn't and the database really does exist (use DBAVAIL or
1499 SHOW/COMMAND to find out) you can do the same thing with:
1507 1
\b12
\b2.
\b.1
\b12
\b2.
\b. d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by
1509 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by List messages
1510 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by o
\bow
\bwn
\bn List your own messages
1511 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by n
\bne
\bew
\bw List all new messages
1512 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>
1513 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>
1514 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
1515 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by <
\b<n
\bnn
\bn>
\b> List last <nn> messages
1516 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
1519 List the messages in the messages directory.
1521 If there is a 'p' one space after the message number then it is a
1522 personal message. If there is a '-' between the message number and the
1524 You can use shell escape characters such as '*' and '?' in the <call>
1527 You can combine some of the various directory commands together eg:-
1533 DIR SUBJECT IOTA 200-250
1537 You can abbreviate all the commands to one letter and use ak1a
1547 1
\b12
\b2.
\b.1
\b13
\b3.
\b. d
\bdx
\bx
1549 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
1552 This is how you send a DX Spot to other users. You can, in fact, now
1553 enter the <freq> and the <call> either way round.
1563 will all give the same result. You can add some remarks to the end of
1564 the command and they will be added to the spot.
1568 DX FR0G 144600 this is a test
1572 You can credit someone else by saying:-
1576 DX by G1TLH FR0G 144.600 he isn't on the cluster
1580 The <freq> is compared against the available bands set up in the
1581 cluster. See SHOW/BANDS for more information.
1584 1
\b12
\b2.
\b.1
\b14
\b4.
\b. h
\bhe
\bel
\blp
\bp
1586 h
\bhe
\bel
\blp
\bp <
\b<c
\bcm
\bmd
\bd>
\b> Get help on a command
1589 All commands can be abbreviated, so SHOW/DX can be abbreviated to
1590 SH/DX, ANNOUNCE can be shortened to AN and so on.
1592 Look at the APROPOS <string> command which will search the help
1593 database for the <string> you specify and give you a list of likely
1594 commands to look at with HELP.
1597 1
\b12
\b2.
\b.1
\b15
\b5.
\b. k
\bki
\bil
\bll
\bl
1599 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] Delete a message from the local system
1602 Delete a message from the local system. You will only be able to
1603 delete messages that you have originated or been sent (unless you are
1607 1
\b12
\b2.
\b.1
\b16
\b6.
\b. l
\bli
\bin
\bnk
\bks
\bs
1609 l
\bli
\bin
\bnk
\bks
\bs Show which nodes are physically connected
1612 This is a quick listing that shows which links are connected and some
1613 information about them. See WHO for a list of all connections.
1616 1
\b12
\b2.
\b.1
\b17
\b7.
\b. r
\bre
\bea
\bad
\bd
1618 r
\bre
\bea
\bad
\bd Read the next unread personal message addressed to you
1619 r
\bre
\bea
\bad
\bd <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Read the specified message
1622 You can read any messages that are sent as 'non-personal' and also any
1623 message either sent by or sent to your callsign.
1626 1
\b12
\b2.
\b.1
\b18
\b8.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be
1628 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 for announce
1632 Create an 'reject this announce' line for a filter.
1634 An reject filter line means that if the announce matches this filter
1635 it is passed onto the user. See HELP FILTERS for more info. Please
1636 read this to understand how filters work - it will save a lot of grief
1639 You can use any of the following things in this line:-
1643 info <string> eg: iota or qsl
1644 by <prefixes> eg: G,M,2
1646 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1647 origin_itu <numbers>
1648 origin_zone <numbers>
1653 wx 1 filter WX announces
1654 dest <prefixes> eg: 6MUK,WDX (distros)
1662 rej/ann by_zone 14,15,16 and not by G,M,2
1666 You can use the tag 'all' to reject everything eg:
1674 but this probably for advanced users...
1677 1
\b12
\b2.
\b.1
\b19
\b9.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs
1679 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
1682 Create a 'reject this spot' line for a filter.
1684 A reject filter line means that if the spot matches this filter it is
1685 dumped (not passed on). See HELP FILTERS for more info. Please read
1686 this to understand how filters work - it will save a lot of grief
1689 You can use any of the following things in this line:-
1693 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1694 on <range> same as 'freq'
1695 call <prefixes> eg: G,PA,HB9
1696 info <string> eg: iota or qsl
1698 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1709 For frequencies, you can use any of the band names defined in
1710 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1711 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1712 this is more efficient than saying simply: on HF (but don't get too
1720 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1724 You can use the tag 'all' to reject everything eg:
1732 but this probably for advanced users...
1735 1
\b12
\b2.
\b.2
\b20
\b0.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bwc
\bcy
\by
1737 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
1740 It is unlikely that you will want to do this, but if you do then you
1741 can filter on the following fields:-
1745 by <prefixes> eg: G,M,2
1747 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1748 origin_itu <numbers>
1749 origin_zone <numbers>
1756 There are no examples because WCY Broadcasts only come from one place
1757 and you either want them or not (see UNSET/WCY if you don't want
1760 This command is really provided for future use.
1762 See HELP FILTER for information.
1765 1
\b12
\b2.
\b.2
\b21
\b1.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bww
\bwv
\bv
1767 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
1770 It is unlikely that you will want to do this, but if you do then you
1771 can filter on the following fields:-
1775 by <prefixes> eg: G,M,2
1777 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1778 origin_itu <numbers>
1779 origin_zone <numbers>
1791 reject/wwv by_zone 14,15,16
1795 is probably the only useful thing to do (which will only show WWV
1796 broadcasts by stations in the US).
1798 See HELP FILTER for information.
1801 1
\b12
\b2.
\b.2
\b22
\b2.
\b. r
\bre
\bep
\bpl
\bly
\by
1803 r
\bre
\bep
\bpl
\bly
\by Reply (privately) to the last message that you have read
1804 r
\bre
\bep
\bpl
\bly
\by <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Reply (privately) to the specified message
1805 r
\bre
\bep
\bpl
\bly
\by B
\bB <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Reply as a Bulletin to the specified message
1806 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
1807 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
1810 You can reply to a message and the subject will automatically have
1811 "Re:" inserted in front of it, if it isn't already present.
1813 You can also use all the extra qualifiers such as RR, PRIVATE,
1814 NOPRIVATE, B that you can use with the SEND command (see SEND for
1819 1
\b12
\b2.
\b.2
\b23
\b3.
\b. s
\bse
\ben
\bnd
\bd
1821 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
1822 s
\bse
\ben
\bnd
\bd R
\bRR
\bR <
\b<c
\bca
\bal
\bll
\bl>
\b> Send a message and ask for a read receipt
1823 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
1824 s
\bse
\ben
\bnd
\bd P
\bPR
\bRI
\bIV
\bVA
\bAT
\bTE
\bE <
\b<c
\bca
\bal
\bll
\bl>
\b> Send a personal message
1825 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
1828 All the SEND commands will create a message which will be sent either
1829 to an individual callsign or to one of the 'bulletin' addresses.
1831 SEND <call> on its own acts as though you had typed SEND PRIVATE, that
1832 is it will mark the message as personal and send it to the cluster
1833 node that that callsign is connected to.
1835 You can have more than one callsign in all of the SEND commands.
1837 You can have multiple qualifiers so that you can have for example:-
1841 SEND RR COPY 123 PRIVATE G1TLH G0RDI
1845 which should send a copy of message 123 to G1TLH and G0RDI and you
1846 will receive a read receipt when they have read the message.
1848 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
1849 is an alias for SEND PRIVATE
1852 1
\b12
\b2.
\b.2
\b24
\b4.
\b. s
\bse
\bet
\bt/
\b/a
\bad
\bdd
\bdr
\bre
\bes
\bss
\bs
1854 s
\bse
\bet
\bt/
\b/a
\bad
\bdd
\bdr
\bre
\bes
\bss
\bs <
\b<y
\byo
\bou
\bur
\br_
\b_a
\bad
\bdd
\bdr
\bre
\bes
\bss
\bs>
\b> Record your postal address
1857 Literally, record your address details on the cluster.
1860 1
\b12
\b2.
\b.2
\b25
\b5.
\b. s
\bse
\bet
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be
1862 s
\bse
\bet
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be Allow announce messages
1865 Allow announce messages to arrive at your terminal.
1868 1
\b12
\b2.
\b.2
\b26
\b6.
\b. s
\bse
\bet
\bt/
\b/b
\bbe
\bee
\bep
\bp
1870 s
\bse
\bet
\bt/
\b/b
\bbe
\bee
\bep
\bp Add beeps to terminal messages
1873 Add a beep to DX and other terminal messages.
1876 1
\b12
\b2.
\b.2
\b27
\b7.
\b. s
\bse
\bet
\bt/
\b/d
\bdx
\bx
1878 s
\bse
\bet
\bt/
\b/d
\bdx
\bxAllow DX messages to arrive at your terminal
1881 You can stop DX messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bd_
\bx command
1884 1
\b12
\b2.
\b.2
\b28
\b8.
\b. s
\bse
\bet
\bt/
\b/d
\bdx
\bxg
\bgr
\bri
\bid
\bd
1886 s
\bse
\bet
\bt/
\b/d
\bdx
\bxg
\bgr
\bri
\bid
\bdAllow grid squares on the end of DX messages
1889 Some logging programs do not like the additional information at the
1890 end of a DX spot. If this is the case, use the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bd_
\bx_
\bg_
\br_
\bi_
\bd command
1891 to remove the grid squares.
1894 1
\b12
\b2.
\b.2
\b29
\b9.
\b. s
\bse
\bet
\bt/
\b/e
\bec
\bch
\bho
\bo
1896 s
\bse
\bet
\bt/
\b/e
\bec
\bch
\bho
\bo Make the cluster echo your input
1899 If you are connected via a telnet session, different implimentations
1900 of telnet handle echo differently depending on whether you are
1901 connected via port 23 or some other port. You can use this command to
1902 change the setting appropriately.
1904 You can remove the echo with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\be_
\bc_
\bh_
\bo command
1906 The setting is stored in your user profile.
1908 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
1911 1
\b12
\b2.
\b.3
\b30
\b0.
\b. s
\bse
\bet
\bt/
\b/h
\bhe
\ber
\bre
\be
1913 s
\bse
\bet
\bt/
\b/h
\bhe
\ber
\bre
\be Set the here flag
1916 Let others on the cluster know you are here by only displaying your
1917 callsign. If you are away from your terminal you can use the
1918 _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bh_
\be_
\br_
\be command to let people know you are away. This simply puts
1919 brackets around your callsign to indicate you are not available.
1922 1
\b12
\b2.
\b.3
\b31
\b1.
\b. s
\bse
\bet
\bt/
\b/h
\bho
\bom
\bme
\ben
\bno
\bod
\bde
\be
1924 s
\bse
\bet
\bt/
\b/h
\bho
\bom
\bme
\ben
\bno
\bod
\bde
\be <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> Set your home cluster
1927 Tell the cluster system where you normally connect to. Any Messages
1928 sent to you will normally find their way there should you not be
1937 1
\b12
\b2.
\b.3
\b32
\b2.
\b. s
\bse
\bet
\bt/
\b/l
\bla
\ban
\bng
\bgu
\bua
\bag
\bge
\be
1939 s
\bse
\bet
\bt/
\b/l
\bla
\ban
\bng
\bgu
\bua
\bag
\bge
\be <
\b<l
\bla
\ban
\bng
\bgu
\bua
\bag
\bge
\be>
\b> Set the language you wish to use
1942 You can select the language that you want the cluster to use.
1943 Currently the languages available are _
\be_
\bn (English) _
\bs_
\bp (Spanish) and _
\bn_
\bl
1948 1
\b12
\b2.
\b.3
\b33
\b3.
\b. s
\bse
\bet
\bt/
\b/l
\blo
\boc
\bca
\bat
\bti
\bio
\bon
\bn
1950 s
\bse
\bet
\bt/
\b/l
\blo
\boc
\bca
\bat
\bti
\bio
\bon
\bn <
\b<l
\bla
\bat
\bt a
\ban
\bnd
\bd l
\blo
\bon
\bng
\bg>
\b> Set your latitude and longitude
1953 You can set your latitude and longitude manually or alternatively use
1954 the _
\bs_
\be_
\bt_
\b/_
\bq_
\br_
\ba command which will do the conversion for you.
1958 set/location 54 04 N 2 02 E
1962 1
\b12
\b2.
\b.3
\b34
\b4.
\b. s
\bse
\bet
\bt/
\b/l
\blo
\bog
\bgi
\bin
\bni
\bin
\bnf
\bfo
\bo
1964 s
\bse
\bet
\bt/
\b/l
\blo
\bog
\bgi
\bin
\bni
\bin
\bnf
\bfo
\bo Show logins and logouts of nodes and users
1967 Show users and nodes when they log in and out of the local cluster.
1968 You can stop these messages by using the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bl_
\bo_
\bg_
\bi_
\bn_
\bi_
\bn_
\bf_
\bo command.
1971 1
\b12
\b2.
\b.3
\b35
\b5.
\b. s
\bse
\bet
\bt/
\b/n
\bna
\bam
\bme
\be
1973 s
\bse
\bet
\bt/
\b/n
\bna
\bam
\bme
\be <
\b<y
\byo
\bou
\bur
\br_
\b_n
\bna
\bam
\bme
\be>
\b> Set your name
1976 Tell the cluster what your name is, eg:-
1984 1
\b12
\b2.
\b.3
\b36
\b6.
\b. s
\bse
\bet
\bt/
\b/p
\bpa
\bag
\bge
\be
1986 s
\bse
\bet
\bt/
\b/p
\bpa
\bag
\bge
\be <
\b<n
\bn>
\b> Set the number of lines per page
1989 Tell the system how many lines you wish on a page when the number of
1990 lines of output from a command is more than this. The default is 20.
1991 Setting it explicitly to 0 will disable paging.
2000 The setting is stored in your user profile.
2003 1
\b12
\b2.
\b.3
\b37
\b7.
\b. s
\bse
\bet
\bt/
\b/q
\bqr
\bra
\ba
2005 s
\bse
\bet
\bt/
\b/q
\bqr
\bra
\ba <
\b<l
\blo
\boc
\bca
\bat
\bto
\bor
\br>
\b> Set your QRA locator
2009 Tell the system what your QRA (or Maidenhead) locator is. If you have
2010 not done a SET/LOCATION then your latitude and longitude will be set
2011 roughly correctly (assuming your locator is correct ;-). For example:-
2019 1
\b12
\b2.
\b.3
\b38
\b8.
\b. s
\bse
\bet
\bt/
\b/q
\bqt
\bth
\bh
2021 s
\bse
\bet
\bt/
\b/q
\bqt
\bth
\bh <
\b<y
\byo
\bou
\bur
\br Q
\bQT
\bTH
\bH>
\b> Set your QTH
2024 Tell the system where your are. For example:-
2028 set/qth East Dereham, Norfolk
2032 1
\b12
\b2.
\b.3
\b39
\b9.
\b. s
\bse
\bet
\bt/
\b/t
\bta
\bal
\blk
\bk
2034 s
\bse
\bet
\bt/
\b/t
\bta
\bal
\blk
\bk Allow talk messages to be seen at your console
2037 Allow talk messages to arrive at your console. You can switch off
2038 talks with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bt_
\ba_
\bl_
\bk command.
2041 1
\b12
\b2.
\b.4
\b40
\b0.
\b. s
\bse
\bet
\bt/
\b/w
\bwc
\bcy
\by
2043 s
\bse
\bet
\bt/
\b/w
\bwc
\bcy
\by Allow WCY messages to be seen at your console
2046 Allow WCY information to be seen at your console. You can switch off
2047 WCY messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bc_
\by command.
2050 1
\b12
\b2.
\b.4
\b41
\b1.
\b. s
\bse
\bet
\bt/
\b/w
\bww
\bwv
\bv
2052 s
\bse
\bet
\bt/
\b/w
\bww
\bwv
\bv Allow WWV messages to be seen at your console
2055 Allow WWV information to be seen at your console. You can switch off
2056 WWV messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bw_
\bv command.
2059 1
\b12
\b2.
\b.4
\b42
\b2.
\b. s
\bse
\bet
\bt/
\b/w
\bwx
\bx
2061 s
\bse
\bet
\bt/
\b/w
\bwx
\bx Allow WX messages to be seen at your console
2064 Allow WX information to be seen at your console. You can switch off
2065 WX messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bx command.
2069 1
\b12
\b2.
\b.4
\b43
\b3.
\b. s
\bsh
\bho
\bow
\bw/
\b/c
\bco
\bon
\bnf
\bfi
\big
\bgu
\bur
\bra
\bat
\bti
\bio
\bon
\bn
2071 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 visible nodes and their users
2074 This command allows you to see all the users that can be seen and the
2075 nodes to which they are connected. With the optional _
\bn_
\bo_
\bd_
\be, you can
2076 specify a particular node to look at.
2078 This command is normally abbreviated to: sh/c
2080 BE WARNED: the list that is returned can be VERY long
2083 1
\b12
\b2.
\b.4
\b44
\b4.
\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
2085 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
2088 Show all the nodes connected locally and the nodes they have
2093 1
\b12
\b2.
\b.4
\b45
\b5.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bda
\bat
\bte
\be
2095 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
2098 This is very nearly the same as SHOW/TIME, the only difference the
2099 format of the date string if no arguments are given.
2101 If no prefixes or callsigns are given then this command returns the
2102 local time and UTC as the computer has it right now. If you give some
2103 prefixes then it will show UTC and UTC + the local offset (not
2104 including DST) at the prefixes or callsigns that you specify.
2107 1
\b12
\b2.
\b.4
\b46
\b6.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bx
2109 s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bx [
\b[o
\bop
\bpt
\bti
\bio
\bon
\bns
\bs]
\b] interrogate the spot database
2112 If you just type SHOW/DX you will get the last so many spots (sysop
2113 configurable, but usually 10).
2115 In addition you can add any number of these options in very nearly any
2116 order to the basic SHOW/DX command, they are:-
2120 on <band> - eg 160m 20m 2m 23cm 6mm
2121 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2123 <number> - the number of spots you want
2124 <from>-<to> - <from> spot no <to> spot no in
2127 <prefix> - for a spotted callsign beginning with <prefix>
2128 *<suffix> - for a spotted callsign ending in <suffix>
2129 *<string>* - for a spotted callsign containing <string>
2131 day <number> - starting <number> days ago
2132 day <from>-<to> - <from> days <to> days ago
2134 info <text> - any spots containing <text> in the info or remarks
2136 by <call> - any spots spotted by <call> (spotter <call>
2139 qsl - this automatically looks for any qsl info on the call
2140 held in the spot database.
2142 iota [<iota>] - If the iota island number is missing it will
2143 look for the string iota and anything which looks like
2144 an iota island number. If you specify then it will look
2147 qra [<locator>] - this will look for the specific locator if
2148 you specify one or else anything that looks like a locator.
2157 SH/DX on 20m info iota
2158 SH/DX 9a on vhf day 30
2166 1
\b12
\b2.
\b.4
\b47
\b7.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bxc
\bcc
\bc
2168 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
2171 This command takes the <prefix> (which can be a full or partial
2172 callsign if desired), looks up which internal country number it is and
2173 then displays all the spots as per SH/DX for that country.
2175 The options for SHOW/DX also apply to this command. e.g.
2180 SH/DXCC W on 20m info iota
2184 1
\b12
\b2.
\b.4
\b48
\b8.
\b. s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\ble
\bes
\bs
2186 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
2189 SHOW/FILES on its own will show you a list of the various fileareas
2190 available on the system. To see the contents of a particular file area
2199 where <filearea> is the name of the filearea you want to see the
2202 You can also use shell globbing characters like '*' and '?' in a
2203 string to see a selection of files in a filearea eg:-
2207 SH/FILES bulletins arld*
2211 See also TYPE - to see the contents of a file.
2214 1
\b12
\b2.
\b.4
\b49
\b9.
\b. s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\blt
\bte
\ber
\br
2216 s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\blt
\bte
\ber
\br Show the filters you have set
2219 Show the contents of all the filters that are set by you. This command
2220 displays all the filters set - for all the various categories.
2223 1
\b12
\b2.
\b.5
\b50
\b0.
\b. s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn
2225 s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn [
\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
2228 Show the Moon rise and set times for a (list of) prefixes or
2229 callsigns, together with the azimuth and elevation of the sun
2230 currently at those locations.
2232 If you don't specify any prefixes or callsigns, it will show the times
2233 for your QTH (assuming you have set it with either SET/LOCATION or
2234 SET/QRA), together with the current azimuth and elevation.
2236 In addition, it will show the gain or loss dB relative to the nominal
2237 distance of 385,000Km due to the ellipsoidal nature of the orbit.
2239 If all else fails it will show the Moonrise and set times for the node
2240 that you are connected to.
2250 1
\b12
\b2.
\b.5
\b51
\b1.
\b. s
\bsh
\bho
\bow
\bw/
\b/m
\bmu
\buf
\bf
2252 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
2256 This command allow you to estimate the likelihood of you contacting a
2257 station with the prefix you have specified. The output assumes a
2258 modest power of 20dBW and receiver sensitivity of -123dBm (about
2261 The result predicts the most likely operating frequencies and signal
2262 levels for high frequency (shortwave) radio propagation paths on
2263 specified days of the year and hours of the day. It is most useful for
2264 paths between 250 km and 6000 km, but can be used with reduced
2265 accuracy for paths shorter or longer than this.
2267 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2268 used to predict the MUF given the predicted flux, day of the year,
2269 hour of the day and geographic coordinates of the transmitter and
2270 receiver. This routine is reasonably accurate for the purposes here,
2271 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2272 than the programs used by major shortwave broadcasting organizations,
2273 such as the Voice of America.
2275 The command will display some header information detailing its
2276 assumptions, together with the locations, latitude and longitudes and
2277 bearings. It will then show UTC (UT), local time at the other end
2278 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2279 (Zen) and the likely signal strengths. Then for each frequency for
2280 which the system thinks there is a likelihood of a circuit it prints a
2283 The value is currently a likely S meter reading based on the
2284 conventional 6dB / S point scale. If the value has a '+' appended it
2285 means that it is 1/2 an S point stronger. If the value is preceeded by
2286 an 'm' it means that there is likely to be much fading and by an 's'
2287 that the signal is likely to be noisy.
2289 By default SHOW/MUF will show the next two hours worth of data. You
2290 can specify anything up to 24 hours worth of data by appending the no
2291 of hours required after the prefix. For example:-
2303 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2304 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2305 Location Lat / Long Azim
2306 East Dereham, Norfolk 52 41 N 0 57 E 47
2307 United-States-W 43 0 N 87 54 W 299
2308 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2309 18 23 11.5 -35 mS0+ mS2 S3
2310 19 0 11.2 -41 mS0+ mS2 S3
2314 indicating that you will have weak, fading circuits on top band and
2315 80m but usable signals on 40m (about S3).
2325 will get you the above display, but with the next 24 hours worth of
2335 Gives you an estimate of the long path propagation characterics. It
2336 should be noted that the figures will probably not be very useful, nor
2337 terrible accurate, but it is included for completeness.
2340 1
\b12
\b2.
\b.5
\b52
\b2.
\b. s
\bsh
\bho
\bow
\bw/
\b/p
\bpr
\bre
\bef
\bfi
\bix
\bx
2342 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
2345 This command takes the <callsign> (which can be a full or partial
2346 callsign or a prefix), looks up which internal country number it is
2347 and then displays all the relevant prefixes for that country together
2348 with the internal country no, the CQ and ITU regions.
2353 1
\b12
\b2.
\b.5
\b53
\b3.
\b. s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\bra
\ba
2355 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 the distance between locators
2356 s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\bra
\ba <
\b<l
\bla
\bat
\bt>
\b> <
\b<l
\blo
\bon
\bng
\bg>
\b> Convert latitude and longitude to a locator
2359 This is a multipurpose command that allows you either to calculate the
2360 distance and bearing between two locators or (if only one locator is
2361 given on the command line) the distance and beraing from your station
2362 to the locator. For example:-
2371 The first example will show the distance and bearing to the locator
2372 from yourself, the second example will calculate the distance and
2373 bearing from the first locator to the second. You can use 4 or 6
2376 It is also possible to convert a latitude and longitude to a locator
2377 by using this command with a latitude and longitude as an argument,
2382 SH/QRA 52 41 N 0 58 E
2386 1
\b12
\b2.
\b.5
\b54
\b4.
\b. s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\brz
\bz
2388 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
2391 This command queries the QRZ callbook server on the internet and
2392 returns any information available for that callsign. This service is
2393 provided for users of this software by http://www.qrz.com
2396 1
\b12
\b2.
\b.5
\b55
\b5.
\b. s
\bsh
\bho
\bow
\bw/
\b/r
\bro
\bou
\but
\bte
\be
2398 s
\bsh
\bho
\bow
\bw/
\b/r
\bro
\bou
\but
\bte
\be <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Show the route to <callsign>
2401 This command allows you to see to which node the callsigns specified
2402 are connected. It is a sort of inverse sh/config.
2410 1
\b12
\b2.
\b.5
\b56
\b6.
\b. s
\bsh
\bho
\bow
\bw/
\b/s
\bsa
\bat
\bte
\bel
\bll
\bli
\bit
\bte
\be
2412 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 satellite tracking
2416 Show the tracking data from your location to the satellite of your
2417 choice from now on for the next few hours.
2419 If you use this command without a satellite name it will display a
2420 list of all the satellites known currently to the system.
2422 If you give a name then you can obtain tracking data of all the passes
2423 that start and finish 5 degrees below the horizon. As default it will
2424 give information for the next three hours for every five minute
2427 You can alter the number of hours and the step size, within certain
2430 Each pass in a period is separated with a row of '-----' characters
2437 SH/SAT FENGYUN1 12 2
2441 1
\b12
\b2.
\b.5
\b57
\b7.
\b. s
\bsh
\bho
\bow
\bw/
\b/s
\bsu
\bun
\bn
2443 s
\bsh
\bho
\bow
\bw/
\b/s
\bsu
\bun
\bn [
\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
2446 Show the sun rise and set times for a (list of) prefixes or callsigns,
2447 together with the azimuth and elevation of the sun currently at those
2450 If you don't specify any prefixes or callsigns, it will show the times
2451 for your QTH (assuming you have set it with either SET/LOCATION or
2452 SET/QRA), together with the current azimuth and elevation.
2454 If all else fails it will show the sunrise and set times for the node
2455 that you are connected to.
2462 SH/SUN G1TLH K9CW ZS
2466 1
\b12
\b2.
\b.5
\b58
\b8.
\b. s
\bsh
\bho
\bow
\bw/
\b/t
\bti
\bim
\bme
\be
2468 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
2471 If no prefixes or callsigns are given then this command returns the
2472 local time and UTC as the computer has it right now. If you give some
2473 prefixes then it will show UTC and UTC + the local offset (not
2474 including DST) at the prefixes or callsigns that you specify.
2477 1
\b12
\b2.
\b.5
\b59
\b9.
\b. s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by
2479 s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by Show the last 10 WCY broadcasts
2480 s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by <
\b<n
\bn>
\b> Show the last <n> WCY broadcasts
2483 Display the most recent WCY information that has been received by the
2488 1
\b12
\b2.
\b.6
\b60
\b0.
\b. s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv
2490 s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv Show the last 10 WWV broadcasts
2491 s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv <
\b<n
\bn>
\b> Show the last <n> WWV broadcasts
2494 Display the most recent WWV information that has been received by the
2498 1
\b12
\b2.
\b.6
\b61
\b1.
\b. s
\bsy
\bys
\bso
\bop
\bp
2500 s
\bsy
\bys
\bso
\bop
\bp Regain your privileges if you login remotely
2503 The system automatically reduces your privilege level to that of a
2504 normal user if you login in remotely. This command allows you to
2505 regain your normal privilege level. It uses the normal system: five
2506 numbers are returned that are indexes into the character array that is
2507 your assigned password (see SET/PASSWORD). The indexes start from
2510 You are expected to return a string which contains the characters
2511 required in the correct order. You may intersperse those characters
2512 with others to obscure your reply for any watchers. For example (and
2513 these values are for explanation :-):
2517 password = 012345678901234567890123456789
2527 aa2bbbb0ccc5ddd7xxx3n
2533 They will all match. If there is no password you will still be offered
2534 numbers but nothing will happen when you input a string. Any match is
2538 1
\b12
\b2.
\b.6
\b62
\b2.
\b. t
\bta
\bal
\blk
\bk
2540 t
\bta
\bal
\blk
\bk <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Enter talk mode with <callsign>
2541 t
\bta
\bal
\blk
\bk <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a text message to <callsign>
2542 t
\bta
\bal
\blk
\bk <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> >
\b> <
\b<n
\bno
\bod
\bde
\be_
\b_c
\bca
\bal
\bll
\bl>
\b> [
\b[<
\b<t
\bte
\bex
\bxt
\bt>
\b>]
\b] Send a text message to
2543 <callsign> via <node_call>
2546 Send a short message to any other station that is visible on the
2547 cluster system. You can send it to anyone you can see with a
2548 SHOW/CONFIGURATION command, they don't have to be connected locally.
2550 The second form of TALK is used when other cluster nodes are connected
2551 with restricted information. This usually means that they don't send
2552 the user information usually associated with logging on and off the
2555 If you know that G3JNB is likely to be present on GB7TLH, but you can
2556 only see GB7TLH in the SH/C list but with no users, then you would use
2557 the second form of the talk message.
2559 If you want to have a ragchew with someone you can leave the text
2560 message out and the system will go into 'Talk' mode. What this means
2561 is that a short message is sent to the recipient telling them that you
2562 are in a 'Talking' frame of mind and then you just type - everything
2563 you send will go to the station that you asked for.
2565 All the usual announcements, spots and so on will still come out on
2568 If you want to do something (such as send a spot) you precede the
2569 normal command with a '/' character, eg:-
2573 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2578 To leave talk mode type:
2586 1
\b12
\b2.
\b.6
\b63
\b3.
\b. t
\bty
\byp
\bpe
\be
2588 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 a file in one of the fileareas
2591 Type out the contents of a file in a filearea. So, for example, in
2592 filearea 'bulletins' you want to look at file 'arld051' you would
2597 TYPE bulletins/arld051
2601 See also SHOW/FILES to see what fileareas are available and a list of
2605 1
\b12
\b2.
\b.6
\b64
\b4.
\b. w
\bwh
\bho
\bo
2607 w
\bwh
\bho
\bo Show who is physically connected locally
2610 This is a quick listing that shows which callsigns are connected and
2611 what sort of connection they have
2614 1
\b12
\b2.
\b.6
\b65
\b5.
\b. w
\bwx
\bx
2616 w
\bwx
\bx <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a weather message to local users
2617 w
\bwx
\bx f
\bfu
\bul
\bll
\bl <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a weather message to all cluster users
2620 Weather messages can sometimes be useful if you are experiencing an
2621 extreme that may indicate enhanced conditions