Next Previous Contents

12. The DXSpider command reference

Below is a complete list of commands available from the cluster prompt. These are listed below in alphabetical order.

12.1 accept/announce

accept/announce [0-9] <pattern> Set an accept filter line for announce

Create an 'accept this announce' line for a filter.

An accept filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERS for more info. Please read this to understand how filters work - it will save a lot of grief later on.

You can use any of the following things in this line:-

  info <string>            eg: iota or qsl
  by <prefixes>            eg: G,M,2         
  origin <prefixes>
  origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
  origin_itu <numbers>
  origin_zone <numbers>
  by_dxcc <numbers>
  by_itu <numbers>
  by_zone <numbers>
  channel <prefixes>
  wx 1                     filter WX announces
  dest <prefixes>          eg: 6MUK,WDX      (distros)

some examples:-

  acc/ann dest 6MUK
  acc/ann 2 by_zone 14,15,16
  (this could be all on one line: acc/ann dest 6MUK or by_zone 14,15,16)

or

  acc/ann by G,M,2 

This filter would only allow announces that were posted buy UK stations. You can use the tag 'all' to accept everything eg:

  acc/ann all

but this probably for advanced users...

12.2 accept/spots

accept/announce [0-9] <pattern> Set an accept filter line for spots

Create an 'accept this spot' line for a filter.

An accept filter line means that if the spot matches this filter it is passed onto the user. See HELP FILTERS for more info. Please read this to understand how filters work - it will save a lot of grief later on.

You can use any of the following things in this line:-

  freq <range>           eg: 0/30000 or hf or hf/cw or 6m,4m,2m
  on <range>             same as 'freq'
  call <prefixes>        eg: G,PA,HB9
  info <string>          eg: iota or qsl
  by <prefixes>            
  call_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
  call_itu <numbers>
  call_zone <numbers>
  by_dxcc <numbers>
  by_itu <numbers>
  by_zone <numbers>
  origin <prefixes>
  channel <prefixes>

For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb - thus: hf/ssb. You can also just have a simple range like: 0/30000 - this is more efficient than saying simply: freq HF (but don't get too hung up about that)

some examples:-

  acc/spot 1 on hf/cw
  acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)

You can use the tag 'all' to accept everything, eg:

  acc/spot 3 all

but this probably for advanced users...

12.3 accept/wcy

accept/wcy [0-9] <pattern> set an accept WCY filter

It is unlikely that you will want to do this, but if you do then you can filter on the following fields:-

  by <prefixes>            eg: G,M,2         
  origin <prefixes>
  origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
  origin_itu <numbers>
  origin_zone <numbers>
  by_dxcc <numbers>
  by_itu <numbers>
  by_zone <numbers>
  channel <prefixes>

There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them).

This command is really provided for future use.

See HELP FILTER for information.

12.4 accept/wwv

accept/wwv [0-9] <pattern> Set an accept WWV filter

It is unlikely that you will want to do this, but if you do then you can filter on the following fields:-

  by <prefixes>            eg: G,M,2         
  origin <prefixes>
  origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
  origin_itu <numbers>
  origin_zone <numbers>
  by_dxcc <numbers>
  by_itu <numbers>
  by_zone <numbers>
  channel <prefixes>

for example

  accept/wwv by_zone 4

is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US).

See HELP FILTER for information.

12.5 announce

announce <text> Send an announcement to local users

Send an announcement to LOCAL users only, where <text> is the text of the announcement you wish to broadcast

12.6 announce full

announce full <text> Send an announcement cluster wide

This command will send your announcement across the whole cluster network.

12.7 apropos

apropos <string> Search the help database

Search the help database for <string> (it isn't case sensitive), and print the names of all the commands that may be relevant.

12.8 bye

bye Exit from the cluster

This will disconnect you from the cluster

12.9 clear/spots

clear/spots [1|all] Clear a spot filter line

This command allows you to clear (remove) a line in a spot filter or to remove the whole filter.

If you have a filter:-

  acc/spot 1 on hf/cw
  acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)

and you say:-

  clear/spot 1

you will be left with:-

  acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)

If you do:

  clear/spot all

the filter will be completely removed.

12.10 dbavail

dbavail Show a list of all the databases in the system

The title says it all really, this command lists all the databases defined in the system. It is also aliased to SHOW/COMMAND.

12.11 dbshow

dbshow <dbname> <key> Display an entry, if it exists, in a database

This is the generic user interface to the database to the database system. It is expected that the sysop will add an entry to the local Aliases file so that users can use the more familiar AK1A style of enquiry such as:

  SH/BUCK G1TLH

but if he hasn't and the database really does exist (use DBAVAIL or SHOW/COMMAND to find out) you can do the same thing with:

  DBSHOW buck G1TLH

12.12 directory

directory List messages
directory all List all messages
directory own List your own messages
directory new List all new messages
directory to <call> List all messages to <call>
directory from <call> List all messages from <call>
directory subject <string> List all messages with <string> in subject
directory <nn> List last <nn> messages
directory <from>-<to> List messages <from> message <to> message

List the messages in the messages directory.

If there is a 'p' one space after the message number then it is a personal message. If there is a '-' between the message number and the 'p' then this indicates that the message has been read.

You can use shell escape characters such as '*' and '?' in the <call> fields.

You can combine some of the various directory commands together eg:-

   DIR TO G1TLH 5
or 
   DIR SUBJECT IOTA 200-250

You can abbreviate all the commands to one letter and use ak1a syntax:-

   DIR/T G1* 10
   DIR/S QSL 10-100 5

12.13 dx

dx [by <call>] <freq> <call> <remarks> Send a DX spot

This is how you send a DX Spot to other users. You can, in fact, now enter the <freq> and the <call> either way round.

   DX FR0G 144.600
   DX 144.600 FR0G
   DX 144600 FR0G 

will all give the same result. You can add some remarks to the end of the command and they will be added to the spot.

   DX FR0G 144600 this is a test

You can credit someone else by saying:-

   DX by G1TLH FR0G 144.600 he isn't on the cluster

The <freq> is compared against the available bands set up in the cluster. See SHOW/BANDS for more information.

12.14 help

help <cmd> Get help on a command

All commands can be abbreviated, so SHOW/DX can be abbreviated to SH/DX, ANNOUNCE can be shortened to AN and so on.

Look at the APROPOS <string> command which will search the help database for the <string> you specify and give you a list of likely commands to look at with HELP.

12.15 kill

kill <msgno> [<msgno> ..] Delete a message from the local system

Delete a message from the local system. You will only be able to delete messages that you have originated or been sent (unless you are the sysop).

12.16 links

links Show which nodes are physically connected

This is a quick listing that shows which links are connected and some information about them. See WHO for a list of all connections.

12.17 read

read Read the next unread personal message addressed to you
read <msgno> Read the specified message

You can read any messages that are sent as 'non-personal' and also any message either sent by or sent to your callsign.

12.18 reject/announce

reject/announce [0-9] <pattern> Set a reject filter for announce

Create an 'reject this announce' line for a filter.

An reject filter line means that if the announce matches this filter it is passed onto the user. See HELP FILTERS for more info. Please read this to understand how filters work - it will save a lot of grief later on.

You can use any of the following things in this line:-

  info <string>            eg: iota or qsl
  by <prefixes>            eg: G,M,2         
  origin <prefixes>
  origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
  origin_itu <numbers>
  origin_zone <numbers>
  by_dxcc <numbers>
  by_itu <numbers>
  by_zone <numbers>
  channel <prefixes>
  wx 1                     filter WX announces
  dest <prefixes>          eg: 6MUK,WDX      (distros)

some examples:-

  rej/ann by_zone 14,15,16 and not by G,M,2

You can use the tag 'all' to reject everything eg:

  rej/ann all

but this probably for advanced users...

12.19 reject/spots

reject/spots [0-9] <pattern> Set a reject filter line for spots

Create a 'reject this spot' line for a filter.

A reject filter line means that if the spot matches this filter it is dumped (not passed on). See HELP FILTERS for more info. Please read this to understand how filters work - it will save a lot of grief later on.

You can use any of the following things in this line:-

  freq <range>           eg: 0/30000 or hf or hf/cw or 6m,4m,2m
  on <range>             same as 'freq'
  call <prefixes>        eg: G,PA,HB9
  info <string>          eg: iota or qsl
  by <prefixes>            
  call_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
  call_itu <numbers>
  call_zone <numbers>
  by_dxcc <numbers>
  by_itu <numbers>
  by_zone <numbers>
  origin <prefixes>
  channel <prefixes>

For frequencies, you can use any of the band names defined in SHOW/BANDS and you can use a subband name like: cw, rtty, data, ssb - thus: hf/ssb. You can also just have a simple range like: 0/30000 - this is more efficient than saying simply: on HF (but don't get too hung up about that)

some examples:-

  rej/spot 1 on hf
  rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)

You can use the tag 'all' to reject everything eg:

  rej/spot 3 all

but this probably for advanced users...

12.20 reject/wcy

reject/wcy [0-9] <pattern> Set a reject WCY filter

It is unlikely that you will want to do this, but if you do then you can filter on the following fields:-

  by <prefixes>            eg: G,M,2         
  origin <prefixes>
  origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
  origin_itu <numbers>
  origin_zone <numbers>
  by_dxcc <numbers>
  by_itu <numbers>
  by_zone <numbers>
  channel <prefixes>

There are no examples because WCY Broadcasts only come from one place and you either want them or not (see UNSET/WCY if you don't want them).

This command is really provided for future use.

See HELP FILTER for information.

12.21 reject/wwv

reject/wwv [0-9] <pattern> Set a reject WWV filter

It is unlikely that you will want to do this, but if you do then you can filter on the following fields:-

  by <prefixes>            eg: G,M,2         
  origin <prefixes>
  origin_dxcc <numbers>    eg: 61,62 (from eg: sh/pre G)
  origin_itu <numbers>
  origin_zone <numbers>
  by_dxcc <numbers>
  by_itu <numbers>
  by_zone <numbers>
  channel <prefixes>

for example

  reject/wwv by_zone 14,15,16

is probably the only useful thing to do (which will only show WWV broadcasts by stations in the US).

See HELP FILTER for information.

12.22 reply

reply Reply (privately) to the last message that you have read
reply <msgno> Reply (privately) to the specified message
reply B <msgno> Reply as a Bulletin to the specified message
reply NOPrivate <msgno> Reply as a Bulletin to the specified message
reply RR <msgno> Reply to the specified message with read receipt

You can reply to a message and the subject will automatically have "Re:" inserted in front of it, if it isn't already present.

You can also use all the extra qualifiers such as RR, PRIVATE, NOPRIVATE, B that you can use with the SEND command (see SEND for further details)

12.23 send

send <call> [<call> ...] Send a message to one or more callsigns
send RR <call> Send a message and ask for a read receipt
send COPY <msgno> <call> Send a copy of a message to someone
send PRIVATE <call> Send a personal message
send NOPRIVATE <call> Send a message to all stations

All the SEND commands will create a message which will be sent either to an individual callsign or to one of the 'bulletin' addresses.

SEND <call> on its own acts as though you had typed SEND PRIVATE, that is it will mark the message as personal and send it to the cluster node that that callsign is connected to.

You can have more than one callsign in all of the SEND commands.

You can have multiple qualifiers so that you can have for example:-

  SEND RR COPY 123 PRIVATE G1TLH G0RDI

which should send a copy of message 123 to G1TLH and G0RDI and you will receive a read receipt when they have read the message.

SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak) SP is an alias for SEND PRIVATE

12.24 set/address

set/address <your_address> Record your postal address

Literally, record your address details on the cluster.

12.25 set/announce

set/announce Allow announce messages

Allow announce messages to arrive at your terminal.

12.26 set/beep

set/beep Add beeps to terminal messages

Add a beep to DX and other terminal messages.

12.27 set/dx

set/dxAllow DX messages to arrive at your terminal

You can stop DX messages with the unset/dx command

12.28 set/dxgrid

set/dxgridAllow grid squares on the end of DX messages

Some logging programs do not like the additional information at the end of a DX spot. If this is the case, use the unset/dxgrid command to remove the grid squares.

12.29 set/echo

set/echo Make the cluster echo your input

If you are connected via a telnet session, different implimentations of telnet handle echo differently depending on whether you are connected via port 23 or some other port. You can use this command to change the setting appropriately.

You can remove the echo with the unset/echo command

The setting is stored in your user profile.

YOU DO NOT NEED TO USE THIS COMMAND IF YOU ARE CONNECTED VIA AX25.

12.30 set/here

set/here Set the here flag

Let others on the cluster know you are here by only displaying your callsign. If you are away from your terminal you can use the unset/here command to let people know you are away. This simply puts brackets around your callsign to indicate you are not available.

12.31 set/homenode

set/homenode <node_call> Set your home cluster

Tell the cluster system where you normally connect to. Any Messages sent to you will normally find their way there should you not be connected. eg:-

  SET/HOMENODE gb7djk

12.32 set/language

set/language <language> Set the language you wish to use

You can select the language that you want the cluster to use. Currently the languages available are en (English) sp (Spanish) and nl (Dutch).

12.33 set/location

set/location <lat and long> Set your latitude and longitude

You can set your latitude and longitude manually or alternatively use the set/qra command which will do the conversion for you.

  set/location 54 04 N 2 02 E

12.34 set/logininfo

set/logininfo Show logins and logouts of nodes and users

Show users and nodes when they log in and out of the local cluster. You can stop these messages by using the unset/logininfo command.

12.35 set/name

set/name <your_name> Set your name

Tell the cluster what your name is, eg:-

  set/name Dirk

12.36 set/page

set/page <n> Set the number of lines per page

Tell the system how many lines you wish on a page when the number of lines of output from a command is more than this. The default is 20. Setting it explicitly to 0 will disable paging.

  SET/PAGE 30
  SET/PAGE 0

The setting is stored in your user profile.

12.37 set/qra

set/qra <locator> Set your QRA locator

Tell the system what your QRA (or Maidenhead) locator is. If you have not done a SET/LOCATION then your latitude and longitude will be set roughly correctly (assuming your locator is correct ;-). For example:-

  SET/QRA JO02LQ

12.38 set/qth

set/qth <your QTH> Set your QTH

Tell the system where your are. For example:-

  set/qth East Dereham, Norfolk

12.39 set/talk

set/talk Allow talk messages to be seen at your console

Allow talk messages to arrive at your console. You can switch off talks with the unset/talk command.

12.40 set/wcy

set/wcy Allow WCY messages to be seen at your console

Allow WCY information to be seen at your console. You can switch off WCY messages with the unset/wcy command.

12.41 set/wwv

set/wwv Allow WWV messages to be seen at your console

Allow WWV information to be seen at your console. You can switch off WWV messages with the unset/wwv command.

12.42 set/wx

set/wx Allow WX messages to be seen at your console

Allow WX information to be seen at your console. You can switch off WX messages with the unset/wx command.

12.43 show/date

show/date [<prefix>|<callsign>] Show the local time

This is very nearly the same as SHOW/TIME, the only difference the format of the date string if no arguments are given.

If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes then it will show UTC and UTC + the local offset (not including DST) at the prefixes or callsigns that you specify.

12.44 show/dx

show/dx [options] interrogate the spot database

If you just type SHOW/DX you will get the last so many spots (sysop configurable, but usually 10).

In addition you can add any number of these options in very nearly any order to the basic SHOW/DX command, they are:-

   
on <band>       - eg 160m 20m 2m 23cm 6mm
on <region>     - eg hf vhf uhf shf      (see SHOW/BANDS)
   
<number>        - the number of spots you want
<from>-<to>     - <from> spot no <to> spot no in 
                  the selected list
   
<prefix>        - for a spotted callsign beginning with <prefix>
*<suffix>       - for a spotted callsign ending in <suffix>
*<string>*      - for a spotted callsign containing <string>
   
day <number>    - starting <number> days ago
day <from>-<to> - <from> days <to> days ago
   
info <text>     - any spots containing <text> in the info or remarks
   
by <call>       - any spots spotted by <call> (spotter <call> 
                        is the same).

qsl             - this automatically looks for any qsl info on the call
                  held in the spot database.

iota [<iota>]   - If the iota island number is missing it will 
                  look for the string iota and anything which looks like 
                  an iota island number. If you specify then it will look 
                  for that island.

qra [<locator>] - this will look for the specific locator if 
                  you specify one or else anything that looks like a locator.

e.g.

   
   SH/DX 9m0
   SH/DX on 20m info iota
   SH/DX 9a on vhf day 30
   SH/DX rf1p qsl
   SH/DX iota 
   SH/DX iota eu-064
   SH/DX qra jn86

12.45 show/dxcc

show/dxcc <prefix> Interrogate the spot database by country

This command takes the <prefix> (which can be a full or partial callsign if desired), looks up which internal country number it is and then displays all the spots as per SH/DX for that country.

The options for SHOW/DX also apply to this command. e.g.

   
   SH/DXCC G
   SH/DXCC W on 20m info iota

12.46 show/files

show/files [<filearea> [<string>]] List the contents of a filearea

SHOW/FILES on its own will show you a list of the various fileareas available on the system. To see the contents of a particular file area type:-

   SH/FILES <filearea>

where <filearea> is the name of the filearea you want to see the contents of.

You can also use shell globbing characters like '*' and '?' in a string to see a selection of files in a filearea eg:-

   SH/FILES bulletins arld*

See also TYPE - to see the contents of a file.

12.47 show/filter

show/filter Show the filters you have set

Show the contents of all the filters that are set by you. This command displays all the filters set - for all the various categories.

12.48 show/moon

show/moon [<prefix>|<callsign>] Show moon rise and set times

Show the Moon rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations.

If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation.

In addition, it will show the gain or loss dB relative to the nominal distance of 385,000Km due to the ellipsoidal nature of the orbit.

If all else fails it will show the Moonrise and set times for the node that you are connected to.

For example:-

  SH/MOON
  SH/MOON G1TLH W5UN

12.49 show/muf

show/muf <prefix> [<hours>][long] Show the likely propagation to <prefix>

This command allow you to estimate the likelihood of you contacting a station with the prefix you have specified. The output assumes a modest power of 20dBW and receiver sensitivity of -123dBm (about 0.15muV/10dB SINAD)

The result predicts the most likely operating frequencies and signal levels for high frequency (shortwave) radio propagation paths on specified days of the year and hours of the day. It is most useful for paths between 250 km and 6000 km, but can be used with reduced accuracy for paths shorter or longer than this.

The command uses a routine MINIMUF 3.5 developed by the U.S. Navy and used to predict the MUF given the predicted flux, day of the year, hour of the day and geographic coordinates of the transmitter and receiver. This routine is reasonably accurate for the purposes here, with a claimed RMS error of 3.8 MHz, but much smaller and less complex than the programs used by major shortwave broadcasting organizations, such as the Voice of America.

The command will display some header information detailing its assumptions, together with the locations, latitude and longitudes and bearings. It will then show UTC (UT), local time at the other end (LT), calculate the MUFs, Sun zenith angle at the midpoint of the path (Zen) and the likely signal strengths. Then for each frequency for which the system thinks there is a likelihood of a circuit it prints a value.

The value is currently a likely S meter reading based on the conventional 6dB / S point scale. If the value has a '+' appended it means that it is 1/2 an S point stronger. If the value is preceeded by an 'm' it means that there is likely to be much fading and by an 's' that the signal is likely to be noisy.

By default SHOW/MUF will show the next two hours worth of data. You can specify anything up to 24 hours worth of data by appending the no of hours required after the prefix. For example:-

  SH/MUF W

produces:

  RxSens: -123 dBM SFI: 159   R: 193   Month: 10   Day: 21
  Power :   20 dBW    Distance:  6283 km    Delay: 22.4 ms
  Location                       Lat / Long           Azim
  East Dereham, Norfolk          52 41 N 0 57 E         47
  United-States-W                43 0 N 87 54 W        299
  UT LT  MUF Zen  1.8  3.5  7.0 10.1 14.0 18.1 21.0 24.9 28.0 50.0
  18 23 11.5 -35  mS0+ mS2   S3
  19  0 11.2 -41  mS0+ mS2   S3

indicating that you will have weak, fading circuits on top band and 80m but usable signals on 40m (about S3).

inputing:-

  SH/MUF W 24

will get you the above display, but with the next 24 hours worth of propagation data.

  SH/MUF W L 24
  SH/MUF W 24 Long

Gives you an estimate of the long path propagation characterics. It should be noted that the figures will probably not be very useful, nor terrible accurate, but it is included for completeness.

12.50 show/prefix

show/prefix <callsign> Interrogate the prefix database

This command takes the <callsign> (which can be a full or partial callsign or a prefix), looks up which internal country number it is and then displays all the relevant prefixes for that country together with the internal country no, the CQ and ITU regions.

See also SHOW/DXCC

12.51 show/qra

show/qra <locator> [<locator>] Show the distance between locators
show/qra <lat> <long> Convert latitude and longitude to a locator

This is a multipurpose command that allows you either to calculate the distance and bearing between two locators or (if only one locator is given on the command line) the distance and beraing from your station to the locator. For example:-

SH/QRA IO92QL 
SH/QRA JN06 IN73

The first example will show the distance and bearing to the locator from yourself, the second example will calculate the distance and bearing from the first locator to the second. You can use 4 or 6 character locators.

It is also possible to convert a latitude and longitude to a locator by using this command with a latitude and longitude as an argument, for example:-

SH/QRA 52 41 N 0 58 E

12.52 show/qrz

show/qrz <callsign> Show any callbook details on a callsign

This command queries the QRZ callbook server on the internet and returns any information available for that callsign. This service is provided for users of this software by http://www.qrz.com

12.53 show/route

show/route <callsign> Show the route to <callsign>

This command allows you to see to which node the callsigns specified are connected. It is a sort of inverse sh/config.

  sh/route n2tly

12.54 show/satellite

show/satellite <name> [<hours> <interval>] Show satellite tracking data

Show the tracking data from your location to the satellite of your choice from now on for the next few hours.

If you use this command without a satellite name it will display a list of all the satellites known currently to the system.

If you give a name then you can obtain tracking data of all the passes that start and finish 5 degrees below the horizon. As default it will give information for the next three hours for every five minute period.

You can alter the number of hours and the step size, within certain limits.

Each pass in a period is separated with a row of '-----' characters

So for example:-

SH/SAT AO-10 
SH/SAT FENGYUN1 12 2

12.55 show/sun

show/sun [<prefix>|<callsign>] Show sun rise and set times

Show the sun rise and set times for a (list of) prefixes or callsigns, together with the azimuth and elevation of the sun currently at those locations.

If you don't specify any prefixes or callsigns, it will show the times for your QTH (assuming you have set it with either SET/LOCATION or SET/QRA), together with the current azimuth and elevation.

If all else fails it will show the sunrise and set times for the node that you are connected to.

For example:-

  SH/SUN
  SH/SUN G1TLH K9CW ZS

12.56 show/time

show/time [<prefix>|<callsign>] Show the local time

If no prefixes or callsigns are given then this command returns the local time and UTC as the computer has it right now. If you give some prefixes then it will show UTC and UTC + the local offset (not including DST) at the prefixes or callsigns that you specify.

12.57 show/wcy

show/wcy Show the last 10 WCY broadcasts
show/wcy <n> Show the last <n> WCY broadcasts

Display the most recent WCY information that has been received by the system

12.58 show/wwv

show/wwv Show the last 10 WWV broadcasts
show/wwv <n> Show the last <n> WWV broadcasts

Display the most recent WWV information that has been received by the system

12.59 sysop

sysop Regain your privileges if you login remotely

The system automatically reduces your privilege level to that of a normal user if you login in remotely. This command allows you to regain your normal privilege level. It uses the normal system: five numbers are returned that are indexes into the character array that is your assigned password (see SET/PASSWORD). The indexes start from zero.

You are expected to return a string which contains the characters required in the correct order. You may intersperse those characters with others to obscure your reply for any watchers. For example (and these values are for explanation :-):

  password = 012345678901234567890123456789
  > sysop
  22 10 15 17 3

you type:-

 aa2bbbb0ccc5ddd7xxx3n
 or 2 0 5 7 3
 or 20573

They will all match. If there is no password you will still be offered numbers but nothing will happen when you input a string. Any match is case sensitive.

12.60 talk

talk <callsign> Enter talk mode with <callsign>
talk <callsign> <text> Send a text message to <callsign>
talk <callsign> > <node_call> [<text>] Send a text message to <callsign> via <node_call>

Send a short message to any other station that is visible on the cluster system. You can send it to anyone you can see with a SHOW/CONFIGURATION command, they don't have to be connected locally.

The second form of TALK is used when other cluster nodes are connected with restricted information. This usually means that they don't send the user information usually associated with logging on and off the cluster.

If you know that G3JNB is likely to be present on GB7TLH, but you can only see GB7TLH in the SH/C list but with no users, then you would use the second form of the talk message.

If you want to have a ragchew with someone you can leave the text message out and the system will go into 'Talk' mode. What this means is that a short message is sent to the recipient telling them that you are in a 'Talking' frame of mind and then you just type - everything you send will go to the station that you asked for.

All the usual announcements, spots and so on will still come out on your terminal.

If you want to do something (such as send a spot) you precede the normal command with a '/' character, eg:-

   /DX 14001 G1TLH What's a B class licensee doing on 20m CW?
   /HELP talk

To leave talk mode type:

   /EX

12.61 type

type <filearea>/<name> Look at a file in one of the fileareas

Type out the contents of a file in a filearea. So, for example, in filearea 'bulletins' you want to look at file 'arld051' you would enter:-

   TYPE bulletins/arld051

See also SHOW/FILES to see what fileareas are available and a list of content.

12.62 who

who Show who is physically connected locally

This is a quick listing that shows which callsigns are connected and what sort of connection they have

12.63 wx

wx <text> Send a weather message to local users
wx full <text> Send a weather message to all cluster users

Weather messages can sometimes be useful if you are experiencing an extreme that may indicate enhanced conditions


Next Previous Contents