1 The DXSpider User Manual
2 Ian Maude, G0VGS, (ianmaude@btinternet.com)
3 Version 1.0, March 2001
5 A complete reference for users of the DXSpider DXCluster program.
6 ______________________________________________________________________
69 1.1 What is a DX Cluster?
70 1.2 So what is DXSpider?
72 2. Logins and logouts.
79 3. Setting your personal details.
81 4. Getting and posting DX.
86 5. Headings and propagation
94 6.1 Making announcements.
95 6.2 Listing announcements.
103 9.1 The "directory" command.
106 9.4 Replying to mail.
109 10. Filtering (From version 1.45)
111 10.1 General filter rules
114 10.4 Advanced filtering
116 11. Hints, tips and common questions.
118 12. The DXSpider command reference
137 12.18 reject/announce
185 ______________________________________________________________________
187 1
\b1.
\b. I
\bIn
\bnt
\btr
\bro
\bod
\bdu
\buc
\bct
\bti
\bio
\bon
\bn
189 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?
191 A DX Cluster is a packet node where DX chasers on any band or mode can
192 post rare or interesting stations that they have worked or heard. Of
193 course other people are doing the same thing too, so you can find new
194 DX as well as telling others about the stations you have worked.
195 Clusters tend to be linked to each other so that the amount of people
196 using them is increased, thereby increasing the amount of posted DX.
197 Other information can be found on clusters such as on-line call books,
198 mail etc. You can talk to other stations connected to the cluster
199 network too, in real time, whether at the node you are logged into or
200 on another node connected to the network. You can also use converse
201 mode, where several stations can talk to each other in the same way.
202 Of course, the DX is still posted to you all the while!
205 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?
207 PacketCluster nodes have been around since roughly 1985. The original
208 PacketCluster idea came from Dick Newell, AK1A, and ran under DOS. In
209 about 1992 Dick stopped the development of the PacketCluster software
210 for amateur radio. Many systems are still using this relatively old
213 There are several new compatible cluster programs around now,
214 including DXSpider. DXSpider is a clone of PacketCluster software
215 that runs under the Linux operating system. Linux is fast becoming
216 the choice for amateur radio stations because of it's flexibility,
217 reliability and the lack of the memory limitations of DOS. Linux
218 supports multitasking and is also multiuser. It has support for AX25,
219 ROSE, NetROM and TCPIP built in, making it the ideal choice for
220 amateur radio. It is also totally free!
222 DXSpider was conceived and begun in 1998 by Dirk Koopman, G1TLH as an
223 exercise in perl programming. It has developed rapidly and today is a
224 very powerful cluster program. It was designed to be totally
225 compatible with the AK1A program, although several commands have been
226 extended to try and improve functionality.
228 This manual is designed to help you become familiar with the commands
229 that DXSpider supports and to help you get the best from the program
230 so you can enjoy working that rare DX! As DXSpider is being improved
231 all the time, commands will be added as time goes by, so make sure you
232 have the most upto date version of this manual. The latest version
233 will always be included with the cluster program so if you are unsure,
234 simply ask your sysop. The manual will also be available on the
239 2
\b2.
\b. L
\bLo
\bog
\bgi
\bin
\bns
\bs a
\ban
\bnd
\bd l
\blo
\bog
\bgo
\bou
\but
\bts
\bs.
\b.
241 You might not think that there is a lot of point of including a
242 section on how to log in and out of DXSpider. However, you would be
243 suprised at the difficulties some people have in simply getting in and
246 There are several ways a login might be achieved, dependant on how the
247 sysop has DXSpider configured. It is impossible for me to cover all
248 variations but here are the basic ones.
251 2
\b2.
\b.1
\b1.
\b. A
\bAX
\bX2
\b25
\b5 l
\blo
\bog
\bgi
\bin
\bns
\bs.
\b.
253 Simplicity itself. The usual C
\bCO
\bON
\bNN
\bNE
\bEC
\bCT
\bT command will log you straight
254 into the cluster and you will not have to do anything else.
255 Obviously, you will have to connect to the correct callsign. Some
256 nodes use an SSID with their call so you would have to add that.
258 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
265 2
\b2.
\b.2
\b2.
\b. N
\bNe
\bet
\btr
\bro
\bom
\bm l
\blo
\bog
\bgi
\bin
\bns
\bs.
\b.
267 There are several possibilities here, dependant on how the sysop has
268 configured his system. If you are connecting via netrom then you are
269 most probably connecting from another station. Listing the nodes in
270 that station with the N
\bNO
\bOD
\bDE
\bES
\bS command will tell you what callsign or
271 netrom alias to connect to. Then just issue the connect command from
272 there. It is possible that the netrom alias may connect you to a node
273 with an alias for the cluster, such as DXC. Just type this and you
276 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
285 2
\b2.
\b.3
\b3.
\b. T
\bTe
\bel
\bln
\bne
\bet
\bt l
\blo
\bog
\bgi
\bin
\bns
\bs.
\b.
287 Because DXSpider runs under the Linux operating system, it is possible
288 to make a direct telnet connection into the cluster. With telnet
289 connections, the source callsign is not seen by DXSpider, so you will
290 be asked to login with your callsign. To telnet to DXSpider, you
291 would connect to a specific port. There is no standard at the moment
292 for a cluster telnet port but ask the sysop if you are unsure.
294 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
303 All the above are possible ways of connecting to a DXSpider cluster.
304 You may have some or all of these available to you. There may be one
305 or two additional ways to connect dependant on the network local to
306 you. However I am sure you get the idea.
309 2
\b2.
\b.4
\b4.
\b. L
\bLo
\bog
\bgo
\bou
\but
\bts
\bs.
\b.
311 Logging out can be done by simply issuing the standard B
\bBY
\bYE
\bE command.
313 You could also send a disconnect if you are using AX25, or a C
\bCL
\bLO
\bOS
\bSE
\bE
314 command if you are connected via telnet. If you do not log out
315 gracefully using one of the above commands, you may find you are
316 unable to get a full connect next time. This may also happen if a
317 NETRom connection drops. You may get connected, but nothing else will
318 happen because the program thinks you are still connected and will not
319 let you connect twice under the same call. However you could
320 reconnect by adding a number to the end of your call, for example
321 G0YLM2. This can be done by either altering your MYCALL setting in
322 the TNC or by altering your program configuration.
326 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.
328 Once logged in to the cluster, you should set your details so that
329 anybody who wishes to contact you can find out who and where you are.
330 There are four items to set, your name, qth, location and home node.
331 Setting these details also allows the use of the SHOW/HEADING and
332 SHOW/SUN commands from within the cluster. Unless you set your QTH
333 and location, these commands cannot function. Once you have set your
334 name, DXSpider will greet you with it next time you login. Your QTH
335 setting is where you live and it is a good idea to add your locator to
336 this as the location setting is converted to latitude and longitude
337 once inputted. You can actually set your location in
338 latitude/longitude or as a locator. Setting your home node will tell
339 the program where you wish mail to be sent to you.
341 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
346 set/qth Morecambe, Lancashire IO84NB
347 set/location 48 34 n 12 12 e
355 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.
357 When all is said and done, this is the main function of a DX cluster.
358 In its simplest form you can just connect to the node and you will
359 start to receive DX spots almost immediately! You can check on recent
360 postings in either a general manner or on a particular band or mode.
361 You can even check DX by callsign or a fragment of a callsign. Of
362 course, once you get the hang of things, it is expected that you start
363 posting some yourself! After all, there would be no clusters if
364 people did not post DX and you get the added thrill of the hunt!
367 4
\b4.
\b.1
\b1.
\b. R
\bRe
\bec
\bce
\bei
\biv
\bvi
\bin
\bng
\bg D
\bDX
\bX.
\b.
369 As we have already said, it is possible just to connect to the cluster
370 and you will receive spots automatically. However, you may wish to
371 check on spots just posted. Maybe you wish to see if a particular
372 band is open or if a certain callsign is active, perhaps a DXpedition.
373 The command to do this is S
\bSH
\bHO
\bOW
\bW/
\b/D
\bDX
\bX. Without any other arguments, this
374 command will output the last 10 spots posted. It is possible to look
375 at more than this, for example the last 20 or 50 spots, by adding the
376 number to the command. You can make it even more specific by adding a
377 band in either wavelength or frequency, and/or any additional
378 information such as QSL details.
380 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
391 will show the last 10, 5 and 20 spots received by the cluster
394 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs
404 will show the last 5, 10 or 20 spots on 20 metres only.
406 It is also possible to check for certain callsigns, or fragments of
407 callsigns in the same way.
409 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
419 would show the last 5 or 10 dx spots containing the callsign g0vgs.
422 You can check for DX by offset and also by specifying a comment to
425 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
436 would show the spots that arrived between 30 and 40 spots ago and any
437 spots with the word _
\bi_
\bo_
\bt_
\ba in the comment field. The case of the
438 comment is not important.
440 Checking DX posted on a certain day is possible too. All you have to
441 do here is to specify how many days ago it was like this ...
443 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
452 It is of course possible to specify multiple arguments.
454 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
458 show/dx 20 prefix 9a on vhf day 30
463 This would show the last 20 spots posted by or about calls with the
464 prefix 9a on vhf 30 days ago.
466 As you can see the S
\bSH
\bHO
\bOW
\bW/
\b/D
\bDX
\bX command is very flexible, so if you are not
467 sure whether something will work or not, try it and see! More
468 information can be found in the Command Set section.
471 4
\b4.
\b.2
\b2.
\b. P
\bPo
\bos
\bst
\bti
\bin
\bng
\bg D
\bDX
\bX.
\b.
473 To post DX you use the D
\bDX
\bX command. The syntax is shown below.
475 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
479 dx (frequency) (callsign) (remarks)
484 Where frequency is in kilohertz and the callsign is the callsign of
485 the station you have worked or heard, (ie not your own callsign!).
486 The remarks section allows you to add information like the operators
487 name or perhaps a location. Actually DXSpider will allow the
488 frequency and callsign fields to be entered in any order.
490 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
494 dx 14004 pa3ezl OP Aurelio 599
499 In fact, all the following will give the same result...
503 dx 14004 pa3ezl OP Aurelio 599
504 dx pa3ezl 14004 OP Aurelio 599
505 dx pa3ezl 14.004 OP Aurelio 599
510 This posting, or callout as it is known, will be forwarded to all
511 other connected stations both at the cluster you are connected to and
512 other active clusters in the network. The callout will also be sent
513 to you as proof of receipt.
516 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
518 There are three commands in DXSpider to help you get the best DX
519 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
520 commands will only work for you if you have entered your personal
521 details. They use your entered location as a reference, so if you
522 have not entered it or have entered it incorrectly they will not
523 return the correct information.
529 5
\b5.
\b.1
\b1.
\b. S
\bSu
\bun
\bn
531 The S
\bSH
\bHO
\bOW
\bW/
\b/S
\bSU
\bUN
\bN command can be used in three different ways. It can be
532 used to show sunrise and sunset times for your own station, a
533 particular callsign or a prefix.
535 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
544 The output from this would look something like this ..
548 sh/sun Location Rise Set Azim Elev
549 G0VGS Morecambe, Lancashire 07:08Z 17:39Z 205.3 24.1
561 would look like this ...
565 sh/sun 5b4 Location Rise Set Azim Elev 5B Cyprus-5B 04:23Z 15:40Z 244.0 18.8
570 You can also specify multiple arguments like this ...
574 sh/sun gw4veq 5b4ab zs
579 and then the output would look like this ...
583 sh/sun gw4veq 5b4ab zs
584 Location Rise Set Azim Elev
585 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
586 ZS So-Africa-ZS1-ZS 04:31Z 17:28Z 289.9 41.3
587 ZS So-Africa-ZS5-ZS 03:44Z 16:34Z 278.5 32.0
588 ZS So-Africa-ZS6-ZS 03:59Z 16:42Z 277.6 35.0
595 5
\b5.
\b.2
\b2.
\b. M
\bMo
\boo
\bon
\bn
597 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.
598 This program however, calculates the rise and set times of the moon
599 for a prefix or callsign, together with the current azimuth and
600 elevation of the sun at these locations.
602 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
611 The output from this command would look like this ..
616 Location Rise Set Azim Elev RGain dB
617 EA Spain-EA 08:15Z 20:09Z 257.2 9.5 -0.6
622 You can see that the output is similar to the S
\bSH
\bHO
\bOW
\bW/
\b/S
\bSU
\bUN
\bN command, with
623 slightly different fields.
626 5
\b5.
\b.3
\b3.
\b. H
\bHe
\bea
\bad
\bdi
\bin
\bng
\bg
628 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
629 S
\bSH
\bHO
\bOW
\bW/
\b/M
\bMO
\bOO
\bON
\bN commands but outputs beam headings for a specified callsign
630 or prefix. Reciprocal beam headings are also calculated.
632 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be
641 The output from this command would look like this ..
646 ZL New-Zealand-ZL1-ZL: 7 degs - dist: 11238 mi, 18087 km Reciprocal heading: 355 degs
647 ZL New-Zealand-ZL2-ZL: 9 degs - dist: 11540 mi, 18574 km Reciprocal heading: 353 degs
648 ZL New-Zealand-ZL3-ZL: 19 degs - dist: 11634 mi, 18724 km Reciprocal heading: 345 degs
649 ZL New-Zealand-ZL4-ZL: 34 degs - dist: 11783 mi, 18963 km Reciprocal heading: 332 degs
655 6
\b6.
\b. A
\bAn
\bnn
\bno
\bou
\bun
\bnc
\bce
\bem
\bme
\ben
\bnt
\bts
\bs.
\b.
657 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.
659 Occasionally, you may wish to post something that does not fall into
660 the normal parameters for a DX callout. You may wish to tell
661 everybody connected that 10 FM is open for example, or ask if anyone
662 knows the QSL manager for a certain callsign etc. You can do this
663 using the A
\bAN
\bNN
\bNO
\bOU
\bUN
\bNC
\bCE
\bE command.
665 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
669 announce 10 FM is open in IO84NB to europe.
674 That would let everyone know locally that this was the case, however
675 it would not be forwarded to other nodes connected. To send
676 announcements to other connected nodes as well, you would use the F
\bFU
\bUL
\bLL
\bL
679 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
683 announce full Anyone seen EA7WA today?
688 Be cautious in your use of announce full. There are many other tools
689 available to get the information you require and the judicious use of
690 this command is frowned upon as it creates a great deal of traffic
694 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.
696 You can list previous announcements in the standard format with the
697 S
\bSH
\bHO
\bOW
\bW command. As before you can list just the last 5 or as many as
700 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
705 show/announcements 10
711 7
\b7.
\b. N
\bNo
\bod
\bde
\bes
\bs a
\ban
\bnd
\bd u
\bus
\bse
\ber
\brs
\bs.
\b.
713 You can check which nodes are connected in the network, who is logged
714 on locally, who is logged on at all the nodes or even just one node in
715 particular. This is handy if you wish to see whether a friend is
716 connected at the node they use. To see who is connected to the nodes,
717 the S
\bSH
\bHO
\bOW
\bW/
\b/C
\bCO
\bON
\bNF
\bFI
\bIG
\bGU
\bUR
\bRA
\bAT
\bTI
\bIO
\bON
\bN command is used.
719 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
728 show/configuration/nodes
729 show/configuration (node_call)
730 show/configuration (prefix)
735 The first of our three examples would output something like this,
743 GB7BIG (GD0TEP) GD3UMW
744 GB7BPQ (G0INA) G0RCI G3AKU G3OCA
746 GB7DJK G0FYD G0REK G1TLH G4PEL G4SOZ
747 G4TVR G7SQW K8AZ M0CTQ-1 MM1CXE-10
750 GB7DXC (G0HDB) G0WFK (G1FYC) G3KWK G3LME
751 G3OIL G4BGW G4FUJ (G4PDQ) GW7SMV
753 (GB7DXG) GU6EFB GU7DHI
754 GB7DXK G1NTW G3IBI G3NSM G3XAQ G4CUS
756 GB7DXM G1EUC G3GAF G3LAS G4ZTR G8WXU
761 You will notice that EI5TCR is showing only that it has 7 users and
762 not giving the actual callsigns. This means that this node is on a
763 limited protocol of some kind, probably because of a contest situation
764 where slow radio links can block up and fail if too much information
765 is sent between nodes.
767 The second example would just show the nodes connected in the network,
773 GB7BAA GB7BAA GB7BPQ (GB7CDX) GB7DJK GB7DXA
774 GB7DXC GB7DXE (GB7DXG) GB7DXK GB7DXL
775 GB7DXM GB7DXS GB7IPT GB7MRS GB7UJS
776 GB7YDX KL7G N2TLY (ON0DXK)
777 GB7BIG EI5TCR GB7ADX GB7BIG GB7UDX
784 If we insert the node_call pi4tue-8 into the third example, then this
794 PI4TUE-8 9A1CMA-6 DF6PW DL4FAY DL4KAK DL4WF-2
795 F5NOD-2 F5PAC IZ0CSR N6CR OH2BLD
796 ON1LVL-13 ON4CBT ON4CJP ON5DXL-14 ON7NQ
797 PA0RCT PA3DYS PA3FDO PA5KW-4 PI4TUE-9
802 As you can see, only the users of the requested node are shown.
804 You can also use a prefix to show only a group of nodes. For example
805 you may only wish to see who is connected to the nodes in the UK. To
806 do this simply use a prefix like this ...
809 show/configuration gb7
813 To show the locally connected users, the S
\bSH
\bHO
\bOW
\bW/
\b/U
\bUS
\bSE
\bER
\bRS
\bS command is used
815 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
824 The output of this command would look like this,
827 Callsigns connected to GB7MBC
828 G0JHC G0NEI G0VGS G0VGS-2 G0YLM
834 8
\b8.
\b. T
\bTa
\bal
\blk
\bk m
\bmo
\bod
\bde
\be.
\b.
836 You can send a single comment or start a dedicated talk session to
837 another user by using the T
\bTA
\bAL
\bLK
\bK command.
840 Talk mode is used to send a one line comment or greeting to a specific
841 user connected either at your node or another in the network. You can
842 also enter into a dedicated talk session with another user. Talks
843 will be automatically forwarded to other nodes if the station you are
844 talking to is not connected locally. You can find out who is
845 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
848 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
853 talk g0rdi Having a good day Iain?
859 This example would send the line "Having a good day Iain?" to the user
860 g0rdi but would leave you in normal mode.
865 Entering Talkmode, /EX to end, /<cmd> to run a command
871 As you can see, you can still run commands whilst in talk mode.
872 Simply prefix the command with a / like /sh/dx and you will get the
873 expected output. If the user is connected to another node, you may
874 have to use a slightly extended version of the T
\bTA
\bAL
\bLK
\bK command.
883 To exit talk mode, you issue the command /
\b/e
\bex
\bx.
885 Whilst in talk mode you will still receive DX spots. This means that
886 you can chat to a friend whilst working DX.
889 9
\b9.
\b. M
\bMa
\bai
\bil
\bl.
\b.
891 You can send and receive both personal mail and bulletins with
892 DXSpider quite easily.
895 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.
897 To list mail you would use the D
\bDI
\bIR
\bRE
\bEC
\bCT
\bTO
\bOR
\bRY
\bY command. On its own, this
898 command will output the last ten messages received by the node, either
899 to or from yourself or bulletins such as "DX" and "ALL". As with
900 other commands you can display more by specifying a number with the
901 command. You should be aware that Spider will accept these commands
902 by separating with either a slash or a space, so _
\bd_
\bi_
\br _
\bn_
\be_
\bw and _
\bd_
\bi_
\br_
\b/_
\bn_
\be_
\bw
903 work in the same way.
905 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
916 Of course most of the time you will only want to list new mail sent to
917 you personally since your last login. However you might also like to
918 check for general mail received by the node. In fact if there is new
919 mail for you, the cluster will tell you when you login. You will also
920 be informed if new mail arrives for you during the time you are logged
921 in. Mail is not only sent to callsigns though. Mail can also be sent
922 to subjects like "all" or "local" or "dx" etc. You can treat these
923 bulletins in the same way as personal mail with the directory command.
925 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\bes
\bs:
\b:
933 directory/from <call>
939 The last option will only show mail from a callsign if it was sent to
940 you personally or was sent as a bulletin. There are some additional
941 commands and these can be found in the DXSpider Command Reference
945 9
\b9.
\b.2
\b2.
\b. R
\bRe
\bea
\bad
\bdi
\bin
\bng
\bg m
\bma
\bai
\bil
\bl.
\b.
947 The output of the D
\bDI
\bIR
\bRE
\bEC
\bCT
\bTO
\bOR
\bRY
\bY command could be something like this.
952 20735 2 ALL GW7SMV 21-Feb 1204Z REC 9E1S QSL TDY 50Mhz....
953 20823 308 UK G0HDB 22-Feb 2334Z Help - which district code?
954 20824 105 ALL W9AE 23-Feb 0349Z S0NY QSL address?
955 20825 2 UK G0LRJ 23-Feb 0806Z QSL REC LZ2CJ/1.CARD NO-750.
956 20858 2 ALL GW7SMV 24-Feb 0905Z REC S92DX QSL CARD TDY 50Mhz
957 20921 200 ALL GM4FDM 27-Feb 2203Z Trip to VP8
958 20949 375 ALL K0MN 27-Feb 0428Z ST0P cards are gd @ ARRL
959 20950 2 UK G0LRJ 28-Feb 0835Z QSL REC SV9/IZ0CKJ/P EU-187.
960 20987 569 ALL GD0TEP 1-Mar 1733Z Portable contests
961 21076 2 ALL G4AFJ 3-Mar 1743Z kh6nd/kh5 qsl received
962 21184-p 599 GW4HAT G0VGS 4-Mar 1518Z Re: Time
967 The first column is the actual message number. If the message is a
968 personal one to you, you will see a letter 'p' after this number. If
969 the message has been read, there will be a '-' between the message
970 number and the 'p'. This only works for personal messages. The next
971 column shows the file size of the message. The third column shows the
972 address the message was sent to and the next column shows who sent it.
973 The rest is fairly self-explanatory.
975 Reading a message is as simple as typing read, followed by the message
976 number that you wish to read.
978 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
987 will read message number 25. However the mail will be displayed in
988 it's entirety unless you specify a page length. You can set your page
989 length to any number you like and when the message reaches that number
990 of lines you will get a prompt giving you options.
991 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
1002 9
\b9.
\b.3
\b3.
\b. S
\bSe
\ben
\bnd
\bdi
\bin
\bng
\bg m
\bma
\bai
\bil
\bl.
\b.
1004 Sending mail is done in the time honoured way. First you specify a
1005 recipient for the message, then you will be prompted for a subject.
1006 Once you have done this you will be asked to type your message.
1007 Please remember that there is no automatic word wrap, so unless you
1008 are using a client that wraps lines automatically, remember to hit
1009 return at the end of each line.
1011 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
1016 Enter Subject (30 characters):
1018 Enter Message /EX to send or /ABORT to exit
1020 Just a quick note to say that I can make Thursday after all. The
1021 appointment I had has cancelled so we are go!
1028 At this point you can either hit return and enter /ex to send the
1029 message or use /abort at any time to abort it. You can now display
1030 the message in the normal way. There are several send options and
1031 these are listed in the Command Set section. These include sending
1032 mail to several recipients and asking for a return receipt.
1036 9
\b9.
\b.4
\b4.
\b. R
\bRe
\bep
\bpl
\bly
\byi
\bin
\bng
\bg t
\bto
\bo m
\bma
\bai
\bil
\bl.
\b.
1038 If mail is addressed to you or to a bulletin address, you can use the
1039 R
\bRE
\bEP
\bPL
\bLY
\bY command to reply to it. Using this command, the subject will be
1040 automatically set for you as "Re: subject", whatever the subject was.
1042 E
\bEx
\bxa
\bam
\bmp
\bpl
\ble
\be:
\b:
1052 9
\b9.
\b.5
\b5.
\b. D
\bDe
\bel
\ble
\bet
\bti
\bin
\bng
\bg m
\bma
\bai
\bil
\bl
1054 To delete a message, you use the _
\bd_
\be_
\bl_
\be_
\bt_
\be command. You can only delete
1055 messages sent to or received by yourself. Bulletins are dealt with
1056 automatically or by the sysop.
1057 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)
1059 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
1061 Upto v1.44 it was not possible for the user to set their own filters.
1062 From v1.45 though that has all changed. It is now possible to set
1063 filters for just about anything you wish. If you have just updated
1064 from an older version of DXSpider you will need to update your new
1065 filters. You do not need to do anything with your old filters, they
1066 will be renamed as you update.
1069 There are 3 basic commands involved in setting and manipulating
1070 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
1071 generally at filtering. There are a number of things you can filter in
1072 the DXSpider system. They all use the same general mechanism.
1075 In general terms you can create a 'reject' or an 'accept' filter which
1076 can have up to 10 lines in it. You do this using, for example ...
1087 where ..... are the specific commands for that type of filter. There
1088 are filters for spots, wwv, announce, wcy and (for sysops) connects.
1089 See each different accept or reject command reference for more
1092 There is also a command to clear out one or more lines in a filter.
1103 There is clear/xxxx command for each type of filter.
1106 and you can check that your filters have worked by the command ...
1117 For now we are going to use spots for the examples, but you can apply
1118 the same principles to all types of filter.
1123 1
\b10
\b0.
\b.2
\b2.
\b. T
\bTy
\byp
\bpe
\bes
\bs o
\bof
\bf f
\bfi
\bil
\blt
\bte
\ber
\br
1125 There are two main types of filter, _
\ba_
\bc_
\bc_
\be_
\bp_
\bt or _
\br_
\be_
\bj_
\be_
\bc_
\bt. You can use
1126 either to achieve the result you want dependent on your own preference
1127 and which is more simple to do. It is pointless writing 8 lines of
1128 reject filters when 1 accept filter would do the same thing! Each
1129 filter has 10 lines (of any length) which are tried in order. If a
1130 line matches then the action you have specified is taken (ie reject
1131 means ignore it and accept means take it)
1134 If you specify reject filters, then any lines that arrive that match
1135 the filter will be dumped but all else will be accepted. If you use
1136 an accept filter, then ONLY the lines in the filter will be accepted
1137 and all else will be dumped. For example if you have a single line
1138 _
\ba_
\bc_
\bc_
\be_
\bp_
\bt filter ...
1142 accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1147 then you will _
\bO_
\bN_
\bL_
\bY get VHF spots _
\bf_
\br_
\bo_
\bm or _
\bt_
\bo CQ zones 14, 15 and 16.
1150 If you set a reject filter like this ...
1154 reject/spots on hf/cw
1159 Then you will get everything _
\bE_
\bX_
\bC_
\bE_
\bP_
\bT HF CW spots. You could make this
1160 single filter even more flexible. For example, if you are interested
1161 in IOTA and will work it even on CW even though normally you are not
1162 interested in CW, then you could say ...
1166 reject/spots on hf/cw and not info iota
1171 But in that case you might only be interested in iota and say:-
1175 accept/spots not on hf/cw or info iota
1180 which achieves exactly the same thing. You should choose one or the
1181 other until you are comfortable with the way it works. You can mix
1182 them if you wish (actually you can have an accept AND a reject on the
1183 same line) but don't attempt this until you are sure you know what you
1187 You can arrange your filter lines into logical units, either for your
1188 own understanding or simply convenience. Here is an example ...
1189 reject/spots 1 on hf/cw
1190 reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
1195 What this does is to ignore all HF CW spots and also rejects any spots
1196 on VHF which don't either originate or spot someone in Europe.
1199 This is an example where you would use a line number (1 and 2 in this
1200 case), if you leave the digit out, the system assumes '1'. Digits
1201 '0'-'9' are available. This make it easier to see just what filters
1202 you have set. It also makes it more simple to remove individual
1203 filters, during a contest for example.
1206 You will notice in the above example that the second line has
1207 brackets. Look at the line logically. You can see there are 2
1208 separate sections to it. We are saying reject spots that are VHF or
1209 above _
\bA_
\bP_
\bA_
\bR_
\bT from those in zones 14, 15 and 16 (either spotted there or
1210 originated there). If you did not have the brackets to separate the 2
1211 sections, then Spider would read it logically from the front and see a
1212 different expression entirely ...
1216 (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
1221 The simple way to remember this is, if you use OR - use brackets.
1222 Whilst we are here CASE is not important. 'And BY_Zone' is just the
1223 same as 'and by_zone'.
1225 As mentioned earlier, setting several filters can be more flexible
1226 than simply setting one complex one. Doing it in this way means that
1227 if you want to alter your filter you can just redefine or remove one
1228 or more lines of it or one line. For example ...
1232 reject/spots 1 on hf/ssb
1237 would redefine our earlier example, or
1246 To remove all the filter lines in the spot filter ...
1255 1
\b10
\b0.
\b.3
\b3.
\b. F
\bFi
\bil
\blt
\bte
\ber
\br o
\bop
\bpt
\bti
\bio
\bon
\bns
\bs
1257 You can filter in several different ways. The options are listed in
1258 the various helpfiles for accept, reject and filter.
1261 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
1263 Once you are happy with the results you get, you may like to
1267 The previous example that filters hf/cw spots and accepts vhf/uhf
1268 spots from EU can be written with a mixed filter, for example ...
1274 acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
1279 Note that the first filter has not been specified with a number. This
1280 will automatically be assumed to be number 1. In this case, we have
1281 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
1282 _
\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
1283 _
\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
1284 'reject' slot and an 'accept' slot. The reject slot is executed BEFORE
1288 It was mentioned earlier that after a reject test that doesn't match,
1289 the default for following tests is 'accept', the reverse is true for
1290 'accept'. In the example what happens is that the reject is executed
1291 first, any non hf/cw spot is passed to the accept line, which lets
1292 through everything else on HF. The next filter line lets through just
1293 VHF/UHF spots from EU.
1297 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.
1299 Q
\bQ.
\b.These commands seem very long! Can I shorten them?
1301 A
\bA.
\b.Of course you can and the usual abbreviations work. If you are
1304 Q
\bQ.
\b.I am not sure if this command is correct. Can I cause any harm if I
1307 A
\bA.
\b.Do not be afraid to try a command to see if it will work, at the
1308 worst you will get an error message. If you require any help on a
1309 command, just type help followed by the command you want help on.
1310 Look at the "DXSpider Command Reference" section to see what help can
1313 Q
\bQ.
\b.How should I use the announce command?
1315 A
\bA.
\b.With respect. Use the command by all means, but please only use the
1316 "full" extension if absolutely necessary. It can create a LOT of
1317 messages passing between clusters.
1319 Q
\bQ.
\b.I like to be working in the shack while logged into the cluster but
1320 I can't be looking at the screen all the time. How can I be alerted
1321 when anything happens?
1323 A
\bA.
\b.Use the S
\bSE
\bET
\bT/
\b/B
\bBE
\bEE
\bEP
\bP command. You can find information on this in the
1324 "DXSpider Command Reference" section.
1326 Q
\bQ.
\b.I keep getting disconnected from the cluster, what is happening and
1329 Q
\bQ.
\b.I got disconnected from the cluster and now I can't log back in
1330 again. What is wrong?
1332 A
\bA.
\b.Probably the cluster thinks you are still logged on and will not let
1333 you reconnect using the same call to prevent loops. Try logging on
1334 again adding an ssid to your callsign as DXSpider treats G0YLM and
1335 G0YLM-1 as different users.
1337 Q
\bQ.
\b.I notice that all the commands are shown in lower case in the main
1338 section of this manual, but in upper case in the "DXSpider Command
1339 Reference" section. Why is that?
1341 Q
\bQ.
\b.How do I know if I have got the latest version of this user manual?
1343 A
\bA.
\b.The latest and greatest will always be on the Website. It will also
1344 be included with every release of DXSpider. As always, if unsure, ask
1345 your sysop what version number is the latest.
1348 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
1350 Below is a complete list of commands available from the cluster
1351 prompt. These are listed below in alphabetical order.
1354 1
\b12
\b2.
\b.1
\b1.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be
1356 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
1359 Create an 'accept this announce' line for a filter.
1361 An accept filter line means that if the announce matches this filter
1362 it is passed onto the user. See HELP FILTERS for more info. Please
1363 read this to understand how filters work - it will save a lot of grief
1366 You can use any of the following things in this line:-
1370 info <string> eg: iota or qsl
1371 by <prefixes> eg: G,M,2
1373 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1374 origin_itu <numbers>
1375 origin_zone <numbers>
1380 wx 1 filter WX announces
1381 dest <prefixes> eg: 6MUK,WDX (distros)
1392 acc/ann 2 by_zone 14,15,16
1393 (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)
1407 This filter would only allow announces that were posted buy UK
1408 stations. You can use the tag 'all' to accept everything eg:
1417 but this probably for advanced users...
1420 1
\b12
\b2.
\b.2
\b2.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs
1422 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 spots
1425 Create an 'accept this spot' line for a filter.
1428 An accept filter line means that if the spot matches this filter it is
1429 passed onto the user. See HELP FILTERS for more info. Please read this
1430 to understand how filters work - it will save a lot of grief later on.
1432 You can use any of the following things in this line:-
1436 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1437 on <range> same as 'freq'
1438 call <prefixes> eg: G,PA,HB9
1439 info <string> eg: iota or qsl
1441 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1453 For frequencies, you can use any of the band names defined in
1454 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1455 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1456 this is more efficient than saying simply: freq HF (but don't get too
1464 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1469 You can use the tag 'all' to accept everything, eg:
1478 but this probably for advanced users...
1481 1
\b12
\b2.
\b.3
\b3.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bwc
\bcy
\by
1483 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
1486 It is unlikely that you will want to do this, but if you do then you
1487 can filter on the following fields:-
1491 by <prefixes> eg: G,M,2
1493 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1494 origin_itu <numbers>
1495 origin_zone <numbers>
1505 There are no examples because WCY Broadcasts only come from one place
1506 and you either want them or not (see UNSET/WCY if you don't want
1509 This command is really provided for future use.
1511 See HELP FILTER for information.
1514 1
\b12
\b2.
\b.4
\b4.
\b. a
\bac
\bcc
\bce
\bep
\bpt
\bt/
\b/w
\bww
\bwv
\bv
1516 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
1519 It is unlikely that you will want to do this, but if you do then you
1520 can filter on the following fields:-
1524 by <prefixes> eg: G,M,2
1526 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1527 origin_itu <numbers>
1528 origin_zone <numbers>
1541 accept/wwv by_zone 4
1546 is probably the only useful thing to do (which will only show WWV
1547 broadcasts by stations in the US).
1549 See HELP FILTER for information.
1552 1
\b12
\b2.
\b.5
\b5.
\b. a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be
1554 a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send an announcement to local users
1557 Send an announcement to LOCAL users only, where <text> is the text of
1558 the announcement you wish to broadcast
1561 1
\b12
\b2.
\b.6
\b6.
\b. a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be f
\bfu
\bul
\bll
\bl
1563 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
1566 This command will send your announcement across the whole cluster
1570 1
\b12
\b2.
\b.7
\b7.
\b. a
\bap
\bpr
\bro
\bop
\bpo
\bos
\bs
1572 a
\bap
\bpr
\bro
\bop
\bpo
\bos
\bs <
\b<s
\bst
\btr
\bri
\bin
\bng
\bg>
\b> Search the help database
1575 Search the help database for <string> (it isn't case sensitive), and
1576 print the names of all the commands that may be relevant.
1579 1
\b12
\b2.
\b.8
\b8.
\b. b
\bby
\bye
\be
1581 b
\bby
\bye
\be Exit from the cluster
1585 This will disconnect you from the cluster
1588 1
\b12
\b2.
\b.9
\b9.
\b. c
\bcl
\ble
\bea
\bar
\br/
\b/s
\bsp
\bpo
\bot
\bts
\bs
1590 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
1593 This command allows you to clear (remove) a line in a spot filter or
1594 to remove the whole filter.
1596 If you have a filter:-
1601 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1615 you will be left with:-
1619 acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
1633 the filter will be completely removed.
1636 1
\b12
\b2.
\b.1
\b10
\b0.
\b. d
\bdb
\bba
\bav
\bva
\bai
\bil
\bl
1638 d
\bdb
\bba
\bav
\bva
\bai
\bil
\bl Show a list of all the databases in the system
1641 The title says it all really, this command lists all the databases
1642 defined in the system. It is also aliased to SHOW/COMMAND.
1645 1
\b12
\b2.
\b.1
\b11
\b1.
\b. d
\bdb
\bbs
\bsh
\bho
\bow
\bw
1647 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
1651 This is the generic user interface to the database to the database
1652 system. It is expected that the sysop will add an entry to the local
1653 Aliases file so that users can use the more familiar AK1A style of
1663 but if he hasn't and the database really does exist (use DBAVAIL or
1664 SHOW/COMMAND to find out) you can do the same thing with:
1674 1
\b12
\b2.
\b.1
\b12
\b2.
\b. d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by
1676 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by List messages
1677 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by o
\bow
\bwn
\bn List your own messages
1678 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by n
\bne
\bew
\bw List all new messages
1679 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>
1680 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>
1681 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
1682 d
\bdi
\bir
\bre
\bec
\bct
\bto
\bor
\bry
\by <
\b<n
\bnn
\bn>
\b> List last <nn> messages
1683 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
1686 List the messages in the messages directory.
1688 If there is a 'p' one space after the message number then it is a
1689 personal message. If there is a '-' between the message number and the
1691 You can use shell escape characters such as '*' and '?' in the <call>
1694 You can combine some of the various directory commands together eg:-
1700 DIR SUBJECT IOTA 200-250
1705 You can abbreviate all the commands to one letter and use ak1a
1717 1
\b12
\b2.
\b.1
\b13
\b3.
\b. d
\bdx
\bx
1719 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
1722 This is how you send a DX Spot to other users. You can, in fact, now
1723 enter the <freq> and the <call> either way round.
1734 will all give the same result. You can add some remarks to the end of
1735 the command and they will be added to the spot.
1739 DX FR0G 144600 this is a test
1744 You can credit someone else by saying:-
1748 DX by G1TLH FR0G 144.600 he isn't on the cluster
1753 The <freq> is compared against the available bands set up in the
1754 cluster. See SHOW/BANDS for more information.
1757 1
\b12
\b2.
\b.1
\b14
\b4.
\b. h
\bhe
\bel
\blp
\bp
1759 h
\bhe
\bel
\blp
\bp <
\b<c
\bcm
\bmd
\bd>
\b> Get help on a command
1762 All commands can be abbreviated, so SHOW/DX can be abbreviated to
1763 SH/DX, ANNOUNCE can be shortened to AN and so on.
1765 Look at the APROPOS <string> command which will search the help
1766 database for the <string> you specify and give you a list of likely
1767 commands to look at with HELP.
1770 1
\b12
\b2.
\b.1
\b15
\b5.
\b. k
\bki
\bil
\bll
\bl
1772 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
1775 Delete a message from the local system. You will only be able to
1776 delete messages that you have originated or been sent (unless you are
1783 1
\b12
\b2.
\b.1
\b16
\b6.
\b. l
\bli
\bin
\bnk
\bks
\bs
1785 l
\bli
\bin
\bnk
\bks
\bs Show which nodes are physically connected
1788 This is a quick listing that shows which links are connected and some
1789 information about them. See WHO for a list of all connections.
1792 1
\b12
\b2.
\b.1
\b17
\b7.
\b. r
\bre
\bea
\bad
\bd
1794 r
\bre
\bea
\bad
\bd Read the next unread personal message addressed to you
1795 r
\bre
\bea
\bad
\bd <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Read the specified message
1798 You can read any messages that are sent as 'non-personal' and also any
1799 message either sent by or sent to your callsign.
1802 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
1804 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
1807 Create an 'reject this announce' line for a filter.
1809 An reject filter line means that if the announce matches this filter
1810 it is passed onto the user. See HELP FILTERS for more info. Please
1811 read this to understand how filters work - it will save a lot of grief
1814 You can use any of the following things in this line:-
1818 info <string> eg: iota or qsl
1819 by <prefixes> eg: G,M,2
1821 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1822 origin_itu <numbers>
1823 origin_zone <numbers>
1828 wx 1 filter WX announces
1829 dest <prefixes> eg: 6MUK,WDX (distros)
1838 rej/ann by_zone 14,15,16 and not by G,M,2
1843 You can use the tag 'all' to reject everything eg:
1849 but this probably for advanced users...
1852 1
\b12
\b2.
\b.1
\b19
\b9.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/s
\bsp
\bpo
\bot
\bts
\bs
1854 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
1857 Create a 'reject this spot' line for a filter.
1859 A reject filter line means that if the spot matches this filter it is
1860 dumped (not passed on). See HELP FILTERS for more info. Please read
1861 this to understand how filters work - it will save a lot of grief
1864 You can use any of the following things in this line:-
1868 freq <range> eg: 0/30000 or hf or hf/cw or 6m,4m,2m
1869 on <range> same as 'freq'
1870 call <prefixes> eg: G,PA,HB9
1871 info <string> eg: iota or qsl
1873 call_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1885 For frequencies, you can use any of the band names defined in
1886 SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb -
1887 thus: hf/ssb. You can also just have a simple range like: 0/30000 -
1888 this is more efficient than saying simply: on HF (but don't get too
1896 rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
1901 You can use the tag 'all' to reject everything eg:
1910 but this probably for advanced users...
1915 1
\b12
\b2.
\b.2
\b20
\b0.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bwc
\bcy
\by
1917 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
1920 It is unlikely that you will want to do this, but if you do then you
1921 can filter on the following fields:-
1925 by <prefixes> eg: G,M,2
1927 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1928 origin_itu <numbers>
1929 origin_zone <numbers>
1938 There are no examples because WCY Broadcasts only come from one place
1939 and you either want them or not (see UNSET/WCY if you don't want
1942 This command is really provided for future use.
1944 See HELP FILTER for information.
1947 1
\b12
\b2.
\b.2
\b21
\b1.
\b. r
\bre
\bej
\bje
\bec
\bct
\bt/
\b/w
\bww
\bwv
\bv
1949 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
1952 It is unlikely that you will want to do this, but if you do then you
1953 can filter on the following fields:-
1957 by <prefixes> eg: G,M,2
1959 origin_dxcc <numbers> eg: 61,62 (from eg: sh/pre G)
1960 origin_itu <numbers>
1961 origin_zone <numbers>
1974 reject/wwv by_zone 14,15,16
1979 is probably the only useful thing to do (which will only show WWV
1980 broadcasts by stations in the US).
1981 See HELP FILTER for information.
1984 1
\b12
\b2.
\b.2
\b22
\b2.
\b. r
\bre
\bep
\bpl
\bly
\by
1986 r
\bre
\bep
\bpl
\bly
\by Reply (privately) to the last message that you have read
1987 r
\bre
\bep
\bpl
\bly
\by <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Reply (privately) to the specified message
1988 r
\bre
\bep
\bpl
\bly
\by B
\bB <
\b<m
\bms
\bsg
\bgn
\bno
\bo>
\b> Reply as a Bulletin to the specified message
1989 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
1990 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
1993 You can reply to a message and the subject will automatically have
1994 "Re:" inserted in front of it, if it isn't already present.
1996 You can also use all the extra qualifiers such as RR, PRIVATE,
1997 NOPRIVATE, B that you can use with the SEND command (see SEND for
2001 1
\b12
\b2.
\b.2
\b23
\b3.
\b. s
\bse
\ben
\bnd
\bd
2003 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
2004 s
\bse
\ben
\bnd
\bd R
\bRR
\bR <
\b<c
\bca
\bal
\bll
\bl>
\b> Send a message and ask for a read receipt
2005 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
2006 s
\bse
\ben
\bnd
\bd P
\bPR
\bRI
\bIV
\bVA
\bAT
\bTE
\bE <
\b<c
\bca
\bal
\bll
\bl>
\b> Send a personal message
2007 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
2010 All the SEND commands will create a message which will be sent either
2011 to an individual callsign or to one of the 'bulletin' addresses.
2013 SEND <call> on its own acts as though you had typed SEND PRIVATE, that
2014 is it will mark the message as personal and send it to the cluster
2015 node that that callsign is connected to.
2017 You can have more than one callsign in all of the SEND commands.
2019 You can have multiple qualifiers so that you can have for example:-
2023 SEND RR COPY 123 PRIVATE G1TLH G0RDI
2028 which should send a copy of message 123 to G1TLH and G0RDI and you
2029 will receive a read receipt when they have read the message.
2031 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP
2032 is an alias for SEND PRIVATE
2035 1
\b12
\b2.
\b.2
\b24
\b4.
\b. s
\bse
\bet
\bt/
\b/a
\bad
\bdd
\bdr
\bre
\bes
\bss
\bs
2037 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
2040 Literally, record your address details on the cluster.
2043 1
\b12
\b2.
\b.2
\b25
\b5.
\b. s
\bse
\bet
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be
2045 s
\bse
\bet
\bt/
\b/a
\ban
\bnn
\bno
\bou
\bun
\bnc
\bce
\be Allow announce messages
2047 Allow announce messages to arrive at your terminal.
2050 1
\b12
\b2.
\b.2
\b26
\b6.
\b. s
\bse
\bet
\bt/
\b/b
\bbe
\bee
\bep
\bp
2052 s
\bse
\bet
\bt/
\b/b
\bbe
\bee
\bep
\bp Add beeps to terminal messages
2055 Add a beep to DX and other terminal messages.
2058 1
\b12
\b2.
\b.2
\b27
\b7.
\b. s
\bse
\bet
\bt/
\b/d
\bdx
\bx
2060 s
\bse
\bet
\bt/
\b/d
\bdx
\bxAllow DX messages to arrive at your terminal
2063 You can stop DX messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bd_
\bx command
2066 1
\b12
\b2.
\b.2
\b28
\b8.
\b. s
\bse
\bet
\bt/
\b/d
\bdx
\bxg
\bgr
\bri
\bid
\bd
2068 s
\bse
\bet
\bt/
\b/d
\bdx
\bxg
\bgr
\bri
\bid
\bdAllow grid squares on the end of DX messages
2071 Some logging programs do not like the additional information at the
2072 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
2073 to remove the grid squares.
2076 1
\b12
\b2.
\b.2
\b29
\b9.
\b. s
\bse
\bet
\bt/
\b/e
\bec
\bch
\bho
\bo
2078 s
\bse
\bet
\bt/
\b/e
\bec
\bch
\bho
\bo Make the cluster echo your input
2081 If you are connected via a telnet session, different implimentations
2082 of telnet handle echo differently depending on whether you are
2083 connected via port 23 or some other port. You can use this command to
2084 change the setting appropriately.
2086 You can remove the echo with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\be_
\bc_
\bh_
\bo command
2088 The setting is stored in your user profile.
2090 YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.
2093 1
\b12
\b2.
\b.3
\b30
\b0.
\b. s
\bse
\bet
\bt/
\b/h
\bhe
\ber
\bre
\be
2095 s
\bse
\bet
\bt/
\b/h
\bhe
\ber
\bre
\be Set the here flag
2098 Let others on the cluster know you are here by only displaying your
2099 callsign. If you are away from your terminal you can use the
2100 _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bh_
\be_
\br_
\be command to let people know you are away. This simply puts
2101 brackets around your callsign to indicate you are not available.
2104 1
\b12
\b2.
\b.3
\b31
\b1.
\b. s
\bse
\bet
\bt/
\b/h
\bho
\bom
\bme
\ben
\bno
\bod
\bde
\be
2106 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
2109 Tell the cluster system where you normally connect to. Any Messages
2110 sent to you will normally find their way there should you not be
2119 1
\b12
\b2.
\b.3
\b32
\b2.
\b. s
\bse
\bet
\bt/
\b/l
\bla
\ban
\bng
\bgu
\bua
\bag
\bge
\be
2121 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
2124 You can select the language that you want the cluster to use.
2125 Currently the languages available are _
\be_
\bn (English) _
\bs_
\bp (Spanish) and _
\bn_
\bl
2129 1
\b12
\b2.
\b.3
\b33
\b3.
\b. s
\bse
\bet
\bt/
\b/l
\blo
\boc
\bca
\bat
\bti
\bio
\bon
\bn
2131 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
2134 You can set your latitude and longitude manually or alternatively use
2135 the _
\bs_
\be_
\bt_
\b/_
\bq_
\br_
\ba command which will do the conversion for you.
2139 set/location 54 04 N 2 02 E
2145 1
\b12
\b2.
\b.3
\b34
\b4.
\b. s
\bse
\bet
\bt/
\b/l
\blo
\bog
\bgi
\bin
\bni
\bin
\bnf
\bfo
\bo
2147 s
\bse
\bet
\bt/
\b/l
\blo
\bog
\bgi
\bin
\bni
\bin
\bnf
\bfo
\bo Show logins and logouts of nodes and users
2150 Show users and nodes when they log in and out of the local cluster.
2151 You can stop these messages by using the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bl_
\bo_
\bg_
\bi_
\bn_
\bi_
\bn_
\bf_
\bo command.
2154 1
\b12
\b2.
\b.3
\b35
\b5.
\b. s
\bse
\bet
\bt/
\b/n
\bna
\bam
\bme
\be
2156 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
2159 Tell the cluster what your name is, eg:-
2169 1
\b12
\b2.
\b.3
\b36
\b6.
\b. s
\bse
\bet
\bt/
\b/p
\bpa
\bag
\bge
\be
2171 s
\bse
\bet
\bt/
\b/p
\bpa
\bag
\bge
\be <
\b<n
\bn>
\b> Set the number of lines per page
2174 Tell the system how many lines you wish on a page when the number of
2175 lines of output from a command is more than this. The default is 20.
2176 Setting it explicitly to 0 will disable paging.
2185 The setting is stored in your user profile.
2188 1
\b12
\b2.
\b.3
\b37
\b7.
\b. s
\bse
\bet
\bt/
\b/q
\bqr
\bra
\ba
2190 s
\bse
\bet
\bt/
\b/q
\bqr
\bra
\ba <
\b<l
\blo
\boc
\bca
\bat
\bto
\bor
\br>
\b> Set your QRA locator
2193 Tell the system what your QRA (or Maidenhead) locator is. If you have
2194 not done a SET/LOCATION then your latitude and longitude will be set
2195 roughly correctly (assuming your locator is correct ;-). For example:-
2205 1
\b12
\b2.
\b.3
\b38
\b8.
\b. s
\bse
\bet
\bt/
\b/q
\bqt
\bth
\bh
2207 s
\bse
\bet
\bt/
\b/q
\bqt
\bth
\bh <
\b<y
\byo
\bou
\bur
\br Q
\bQT
\bTH
\bH>
\b> Set your QTH
2210 Tell the system where your are. For example:-
2214 set/qth East Dereham, Norfolk
2220 1
\b12
\b2.
\b.3
\b39
\b9.
\b. s
\bse
\bet
\bt/
\b/t
\bta
\bal
\blk
\bk
2222 s
\bse
\bet
\bt/
\b/t
\bta
\bal
\blk
\bk Allow talk messages to be seen at your console
2225 Allow talk messages to arrive at your console. You can switch off
2226 talks with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bt_
\ba_
\bl_
\bk command.
2229 1
\b12
\b2.
\b.4
\b40
\b0.
\b. s
\bse
\bet
\bt/
\b/w
\bwc
\bcy
\by
2231 s
\bse
\bet
\bt/
\b/w
\bwc
\bcy
\by Allow WCY messages to be seen at your console
2234 Allow WCY information to be seen at your console. You can switch off
2235 WCY messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bc_
\by command.
2238 1
\b12
\b2.
\b.4
\b41
\b1.
\b. s
\bse
\bet
\bt/
\b/w
\bww
\bwv
\bv
2240 s
\bse
\bet
\bt/
\b/w
\bww
\bwv
\bv Allow WWV messages to be seen at your console
2243 Allow WWV information to be seen at your console. You can switch off
2244 WWV messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bw_
\bv command.
2245 1
\b12
\b2.
\b.4
\b42
\b2.
\b. s
\bse
\bet
\bt/
\b/w
\bwx
\bx
2247 s
\bse
\bet
\bt/
\b/w
\bwx
\bx Allow WX messages to be seen at your console
2250 Allow WX information to be seen at your console. You can switch off
2251 WX messages with the _
\bu_
\bn_
\bs_
\be_
\bt_
\b/_
\bw_
\bx command.
2254 1
\b12
\b2.
\b.4
\b43
\b3.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bda
\bat
\bte
\be
2256 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
2259 This is very nearly the same as SHOW/TIME, the only difference the
2260 format of the date string if no arguments are given.
2262 If no prefixes or callsigns are given then this command returns the
2263 local time and UTC as the computer has it right now. If you give some
2264 prefixes then it will show UTC and UTC + the local offset (not
2265 including DST) at the prefixes or callsigns that you specify.
2268 1
\b12
\b2.
\b.4
\b44
\b4.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bx
2270 s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bx [
\b[o
\bop
\bpt
\bti
\bio
\bon
\bns
\bs]
\b] interrogate the spot database
2273 If you just type SHOW/DX you will get the last so many spots (sysop
2274 configurable, but usually 10).
2276 In addition you can add any number of these options in very nearly any
2277 order to the basic SHOW/DX command, they are:-
2311 on <band> - eg 160m 20m 2m 23cm 6mm
2312 on <region> - eg hf vhf uhf shf (see SHOW/BANDS)
2314 <number> - the number of spots you want
2315 <from>-<to> - <from> spot no <to> spot no in
2318 <prefix> - for a spotted callsign beginning with <prefix>
2319 *<suffix> - for a spotted callsign ending in <suffix>
2320 *<string>* - for a spotted callsign containing <string>
2322 day <number> - starting <number> days ago
2323 day <from>-<to> - <from> days <to> days ago
2325 info <text> - any spots containing <text> in the info or remarks
2327 by <call> - any spots spotted by <call> (spotter <call>
2330 qsl - this automatically looks for any qsl info on the call
2331 held in the spot database.
2333 iota [<iota>] - If the iota island number is missing it will
2334 look for the string iota and anything which looks like
2335 an iota island number. If you specify then it will look
2338 qra [<locator>] - this will look for the specific locator if
2339 you specify one or else anything that looks like a locator.
2350 SH/DX on 20m info iota
2351 SH/DX 9a on vhf day 30
2361 1
\b12
\b2.
\b.4
\b45
\b5.
\b. s
\bsh
\bho
\bow
\bw/
\b/d
\bdx
\bxc
\bcc
\bc
2363 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
2366 This command takes the <prefix> (which can be a full or partial
2367 callsign if desired), looks up which internal country number it is and
2368 then displays all the spots as per SH/DX for that country.
2370 The options for SHOW/DX also apply to this command. e.g.
2378 SH/DXCC W on 20m info iota
2384 1
\b12
\b2.
\b.4
\b46
\b6.
\b. s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\ble
\bes
\bs
2386 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
2389 SHOW/FILES on its own will show you a list of the various fileareas
2390 available on the system. To see the contents of a particular file area
2400 where <filearea> is the name of the filearea you want to see the
2403 You can also use shell globbing characters like '*' and '?' in a
2404 string to see a selection of files in a filearea eg:-
2408 SH/FILES bulletins arld*
2413 See also TYPE - to see the contents of a file.
2416 1
\b12
\b2.
\b.4
\b47
\b7.
\b. s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\blt
\bte
\ber
\br
2418 s
\bsh
\bho
\bow
\bw/
\b/f
\bfi
\bil
\blt
\bte
\ber
\br Show the filters you have set
2421 Show the contents of all the filters that are set by you. This command
2422 displays all the filters set - for all the various categories.
2425 1
\b12
\b2.
\b.4
\b48
\b8.
\b. s
\bsh
\bho
\bow
\bw/
\b/m
\bmo
\boo
\bon
\bn
2427 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
2430 Show the Moon rise and set times for a (list of) prefixes or
2431 callsigns, together with the azimuth and elevation of the sun
2432 currently at those locations.
2434 If you don't specify any prefixes or callsigns, it will show the times
2435 for your QTH (assuming you have set it with either SET/LOCATION or
2436 SET/QRA), together with the current azimuth and elevation.
2438 In addition, it will show the gain or loss dB relative to the nominal
2439 distance of 385,000Km due to the ellipsoidal nature of the orbit.
2441 If all else fails it will show the Moonrise and set times for the node
2442 that you are connected to.
2454 1
\b12
\b2.
\b.4
\b49
\b9.
\b. s
\bsh
\bho
\bow
\bw/
\b/m
\bmu
\buf
\bf
2456 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
2460 This command allow you to estimate the likelihood of you contacting a
2461 station with the prefix you have specified. The output assumes a
2462 modest power of 20dBW and receiver sensitivity of -123dBm (about
2465 The result predicts the most likely operating frequencies and signal
2466 levels for high frequency (shortwave) radio propagation paths on
2467 specified days of the year and hours of the day. It is most useful for
2468 paths between 250 km and 6000 km, but can be used with reduced
2469 accuracy for paths shorter or longer than this.
2471 The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and
2472 used to predict the MUF given the predicted flux, day of the year,
2473 hour of the day and geographic coordinates of the transmitter and
2474 receiver. This routine is reasonably accurate for the purposes here,
2475 with a claimed RMS error of 3.8 MHz, but much smaller and less complex
2476 than the programs used by major shortwave broadcasting organizations,
2477 such as the Voice of America.
2479 The command will display some header information detailing its
2480 assumptions, together with the locations, latitude and longitudes and
2481 bearings. It will then show UTC (UT), local time at the other end
2482 (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path
2483 (Zen) and the likely signal strengths. Then for each frequency for
2484 which the system thinks there is a likelihood of a circuit it prints a
2487 The value is currently a likely S meter reading based on the
2488 conventional 6dB / S point scale. If the value has a '+' appended it
2489 means that it is 1/2 an S point stronger. If the value is preceeded by
2490 an 'm' it means that there is likely to be much fading and by an 's'
2491 that the signal is likely to be noisy.
2493 By default SHOW/MUF will show the next two hours worth of data. You
2494 can specify anything up to 24 hours worth of data by appending the no
2495 of hours required after the prefix. For example:-
2509 RxSens: -123 dBM SFI: 159 R: 193 Month: 10 Day: 21
2510 Power : 20 dBW Distance: 6283 km Delay: 22.4 ms
2511 Location Lat / Long Azim
2512 East Dereham, Norfolk 52 41 N 0 57 E 47
2513 United-States-W 43 0 N 87 54 W 299
2514 UT LT MUF Zen 1.8 3.5 7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
2515 18 23 11.5 -35 mS0+ mS2 S3
2516 19 0 11.2 -41 mS0+ mS2 S3
2521 indicating that you will have weak, fading circuits on top band and
2522 80m but usable signals on 40m (about S3).
2533 will get you the above display, but with the next 24 hours worth of
2544 Gives you an estimate of the long path propagation characterics. It
2545 should be noted that the figures will probably not be very useful, nor
2546 terrible accurate, but it is included for completeness.
2549 1
\b12
\b2.
\b.5
\b50
\b0.
\b. s
\bsh
\bho
\bow
\bw/
\b/p
\bpr
\bre
\bef
\bfi
\bix
\bx
2551 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
2554 This command takes the <callsign> (which can be a full or partial
2555 callsign or a prefix), looks up which internal country number it is
2556 and then displays all the relevant prefixes for that country together
2557 with the internal country no, the CQ and ITU regions.
2562 1
\b12
\b2.
\b.5
\b51
\b1.
\b. s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\bra
\ba
2564 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
2565 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
2568 This is a multipurpose command that allows you either to calculate the
2569 distance and bearing between two locators or (if only one locator is
2570 given on the command line) the distance and beraing from your station
2571 to the locator. For example:-
2581 The first example will show the distance and bearing to the locator
2582 from yourself, the second example will calculate the distance and
2583 bearing from the first locator to the second. You can use 4 or 6
2586 It is also possible to convert a latitude and longitude to a locator
2587 by using this command with a latitude and longitude as an argument,
2592 SH/QRA 52 41 N 0 58 E
2598 1
\b12
\b2.
\b.5
\b52
\b2.
\b. s
\bsh
\bho
\bow
\bw/
\b/q
\bqr
\brz
\bz
2600 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
2603 This command queries the QRZ callbook server on the internet and
2604 returns any information available for that callsign. This service is
2605 provided for users of this software by http://www.qrz.com
2608 1
\b12
\b2.
\b.5
\b53
\b3.
\b. s
\bsh
\bho
\bow
\bw/
\b/r
\bro
\bou
\but
\bte
\be
2610 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>
2613 This command allows you to see to which node the callsigns specified
2614 are connected. It is a sort of inverse sh/config.
2624 1
\b12
\b2.
\b.5
\b54
\b4.
\b. s
\bsh
\bho
\bow
\bw/
\b/s
\bsa
\bat
\bte
\bel
\bll
\bli
\bit
\bte
\be
2626 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
2630 Show the tracking data from your location to the satellite of your
2631 choice from now on for the next few hours.
2633 If you use this command without a satellite name it will display a
2634 list of all the satellites known currently to the system.
2636 If you give a name then you can obtain tracking data of all the passes
2637 that start and finish 5 degrees below the horizon. As default it will
2638 give information for the next three hours for every five minute
2641 You can alter the number of hours and the step size, within certain
2644 Each pass in a period is separated with a row of '-----' characters
2651 SH/SAT FENGYUN1 12 2
2657 1
\b12
\b2.
\b.5
\b55
\b5.
\b. s
\bsh
\bho
\bow
\bw/
\b/s
\bsu
\bun
\bn
2659 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
2662 Show the sun rise and set times for a (list of) prefixes or callsigns,
2663 together with the azimuth and elevation of the sun currently at those
2666 If you don't specify any prefixes or callsigns, it will show the times
2667 for your QTH (assuming you have set it with either SET/LOCATION or
2668 SET/QRA), together with the current azimuth and elevation.
2670 If all else fails it will show the sunrise and set times for the node
2671 that you are connected to.
2678 SH/SUN G1TLH K9CW ZS
2684 1
\b12
\b2.
\b.5
\b56
\b6.
\b. s
\bsh
\bho
\bow
\bw/
\b/t
\bti
\bim
\bme
\be
2686 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
2689 If no prefixes or callsigns are given then this command returns the
2690 local time and UTC as the computer has it right now. If you give some
2691 prefixes then it will show UTC and UTC + the local offset (not
2692 including DST) at the prefixes or callsigns that you specify.
2695 1
\b12
\b2.
\b.5
\b57
\b7.
\b. s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by
2697 s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by Show the last 10 WCY broadcasts
2698 s
\bsh
\bho
\bow
\bw/
\b/w
\bwc
\bcy
\by <
\b<n
\bn>
\b> Show the last <n> WCY broadcasts
2701 Display the most recent WCY information that has been received by the
2707 1
\b12
\b2.
\b.5
\b58
\b8.
\b. s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv
2709 s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv Show the last 10 WWV broadcasts
2710 s
\bsh
\bho
\bow
\bw/
\b/w
\bww
\bwv
\bv <
\b<n
\bn>
\b> Show the last <n> WWV broadcasts
2713 Display the most recent WWV information that has been received by the
2717 1
\b12
\b2.
\b.5
\b59
\b9.
\b. s
\bsy
\bys
\bso
\bop
\bp
2719 s
\bsy
\bys
\bso
\bop
\bp Regain your privileges if you login remotely
2722 The system automatically reduces your privilege level to that of a
2723 normal user if you login in remotely. This command allows you to
2724 regain your normal privilege level. It uses the normal system: five
2725 numbers are returned that are indexes into the character array that is
2726 your assigned password (see SET/PASSWORD). The indexes start from
2729 You are expected to return a string which contains the characters
2730 required in the correct order. You may intersperse those characters
2731 with others to obscure your reply for any watchers. For example (and
2732 these values are for explanation :-):
2736 password = 012345678901234567890123456789
2747 aa2bbbb0ccc5ddd7xxx3n
2754 They will all match. If there is no password you will still be offered
2755 numbers but nothing will happen when you input a string. Any match is
2759 1
\b12
\b2.
\b.6
\b60
\b0.
\b. t
\bta
\bal
\blk
\bk
2761 t
\bta
\bal
\blk
\bk <
\b<c
\bca
\bal
\bll
\bls
\bsi
\big
\bgn
\bn>
\b> Enter talk mode with <callsign>
2762 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>
2763 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
2764 <callsign> via <node_call>
2767 Send a short message to any other station that is visible on the
2768 cluster system. You can send it to anyone you can see with a
2769 SHOW/CONFIGURATION command, they don't have to be connected locally.
2771 The second form of TALK is used when other cluster nodes are connected
2772 with restricted information. This usually means that they don't send
2773 the user information usually associated with logging on and off the
2776 If you know that G3JNB is likely to be present on GB7TLH, but you can
2777 only see GB7TLH in the SH/C list but with no users, then you would use
2778 the second form of the talk message.
2780 If you want to have a ragchew with someone you can leave the text
2781 message out and the system will go into 'Talk' mode. What this means
2782 is that a short message is sent to the recipient telling them that you
2783 are in a 'Talking' frame of mind and then you just type - everything
2784 you send will go to the station that you asked for.
2786 All the usual announcements, spots and so on will still come out on
2789 If you want to do something (such as send a spot) you precede the
2790 normal command with a '/' character, eg:-
2794 /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
2800 To leave talk mode type:
2810 1
\b12
\b2.
\b.6
\b61
\b1.
\b. t
\bty
\byp
\bpe
\be
2812 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
2815 Type out the contents of a file in a filearea. So, for example, in
2816 filearea 'bulletins' you want to look at file 'arld051' you would
2821 TYPE bulletins/arld051
2826 See also SHOW/FILES to see what fileareas are available and a list of
2830 1
\b12
\b2.
\b.6
\b62
\b2.
\b. w
\bwh
\bho
\bo
2832 w
\bwh
\bho
\bo Show who is physically connected locally
2835 This is a quick listing that shows which callsigns are connected and
2836 what sort of connection they have
2839 1
\b12
\b2.
\b.6
\b63
\b3.
\b. w
\bwx
\bx
2841 w
\bwx
\bx <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a weather message to local users
2842 w
\bwx
\bx f
\bfu
\bul
\bll
\bl <
\b<t
\bte
\bex
\bxt
\bt>
\b> Send a weather message to all cluster users
2845 Weather messages can sometimes be useful if you are experiencing an
2846 extreme that may indicate enhanced conditions