DXSpider manuaali.

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 

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 

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 

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 

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 

HELP is available for a number of commands. The syntax is:-   HELP <cmd> Where <cmd> is the name of the command you want help on. 

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

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

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 

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 

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 

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

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

on <band> - eg 160m 20m 2m 23cm 6mm on <region> - eg hf vhf uhf shf (see SHOW/BANDS) 

<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 

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 

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:- nbsp;  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. 

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. 

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 

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. 

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. 

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.