29
September
2022
17:00

DxSpider Cluster DX Commands

,
29 September 2022 17:00

The article presents commands for managing the DxSpider DX cluster.

DXspidercluster commands

command Action
accept ... Set a filter to allow something
accept/announce [0-9] ‹pattern› Set a permissive filter for advertisements numbered from 0 to 9. The pattern string can be one of the following:

info search_string. Example: info iota
origin prefixes or numbers
Filters "origin..." used by admins. Example: origin G,F
origin_dxcc prefixes. Example: orignin_dxcc G,GM,GW
origin_itu prefixes. Example: origin_itu K,N,W
origin_zone zone_numbers
origin_state states. Example: origin_state VA,NH,RI,NH
by_dxcc prefixes - for filtering by country prefixes.
by_itu prefixes
by_zone prefixes or numbers. Example: by_zone 14,15,16
by_state states
channel prefixes
wx 1 filter for weather announcements WX
dest prefixes Example: dest** WDX (distributors)
accept/route [0-9] ‹sample› Set a filter for transmission through the interface between nodes (command for admins - for sending DX spots)
by callsign - spots from the callsign
by_dxcc prefix - L'indicatif d'appel de l'auteur du pays DXCC appartient à
call prefix - call sign
call_itu**prefixes

Example:
acc/route gb7djk call_itu 27**
accept/spots [0-9] ‹sample› Set the DX spot resolution filter numbered from 0 to 9. String sample may be one of the following:

freq frequency range. Examples: freq 7000-7060 or frequency HF/CW or frequency 2m
call can include callsign_prefixes. Example: call G,PA,HB9 on 14000-14100/. The frequency range can be specified as a fraction: on 0/30000 Example: call ja on hf/cw or on 10m/6m.
mode Where mode is cw, ssb or rtty. Examples: mode hf/cw or mode ssb, mode/rtty.
info string Can be used with negation: not. Example: info not iota
by prefixes - from prefixes. Example: by JA
call_dxcc countries Example: call_dxcc VA
call_itu**prefixes or numbers. Example: call_itu G,GM,GW
by_zone number_of_zones. Example: by_zone 14,15,16
bystate**states\USA. Example: by_state VA,NH,RI,ME

node_default all (For administrators - accept all spots by default)
user_default by G,M (For administrators - allow spots from G, M)

origin prefixes - used by admins
channel prefixes - used by admins
wx 1 filter for weather announcements WX
dest prefixes Example: dest WDX (distributor)
---------
Key words of amateur radio frequency bands:
160m, 80m, 60m, 40m, 30m, 20m, 17m, 15m, 12m, 10m, 2m, 70cm, 23cm, 13cm, 9cm, 6cm, 3cm,12mm, 6mm
Bands for competitions (contests) on HF: contesthf 160m 80m 40m 20m 15m 10m
WARC bands:warc 60m 30m 17m 12m
All bands -all, HF bands -hf, VHF bands -uhf, microwave -shf.
Example: accept/spots hf, vhf, uhf
Keywords of frequency bands for types of transmission: cw, rtty, data, ssb, sstv.
Example: accept/spots hf/ssb.
-----
Filter combinations - using logical operators and- \"and\" or- \"or\". Example: accept/spots (2m/cw or 2m/rtty) and call_dxcc OH


Prefix "call" refers to DX radio station
Prefix "by" - the author of the DX spot, the one who sent the DX spot to the cluster.
accept/WCY [0-9] ‹sample› It is unlikely that you will want to use this filter because all WCY broadcast messages are issued by one source.
You can enable or disable WCY messages with the commands:
SET/WCY or UNSET/WCY
accept/WWV [0-9] ‹sample› It is unlikely that you will want to use this filter since all WWV ionospheric index broadcast messages are issued by one source.
You can enable or disable WWY messages with the commands:
SET/WWY or UNSET/WWY
Announce ‹text› Send an ad to local users, where text is an ad for local users only
Annouce Full ‹text› Send an announcement to all users of the cluster, where text is an announcement to all users of the cluster
Apropos ‹text› Search the reference database (string is a case-insensitive search string) and display the names of DX cluster commands that are relevant to string
Blank Prints an empty line
Bye Disconnect from server
Chat ‹group› ‹text› Send a message "text" to the group "group". It is now possible to join a global group and receive messages from that group. The DXspider system does not use the AK1A conferencing system, instead it uses the normal announcement notification mechanism (ANN system)
Clear/Announce[1/all] Remove one or all ad filters
Clear/Spots This command allows you to delete a DX spot filter line or all filters. For example, if you have two filters
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 remove the first filter with the command clear/spot 1, after which the user's filter list will look like this:
acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
Clear/WCY This command allows you to delete a specific WCY broadcast message filter or delete all WCY message filters
Clear/WWV This command allows you to delete a specific WWV geomagnetic index message filter or delete all WWV message filters
dbavail Display a list of available databases. This command is aliased: SHOW/COMMAND
dbshow dbname ‹key› This is the standard interface to the Aliases database (for the administrator).
DIRectory Display a list of personal messages
DIRectory #from - #to List private messages from ... to. Example: directory 1 - 10

You can also precede the message number with the recipient's call sign TO or the subject SUBJECT. Examples:
dir TO GE1BP
dir SUBJECT iota 1-5
For a more compact notation, TO can be shortened to /T, Subject to /S:
dir/s QSL 15-20
DIRectory ‹nn› Display the last nn personal messages
DIRectory all Display all private messages
DIRectory FROM callsign Display messages from the callsign. Example: DIR FROM K1FD
DIRectory NEW Display new messages
DIRectory SUBJECT ‹topic› Display a message with the line "subject" in the title
DIRectory TO ‹callsign› Display messages for a callsign. Example: DIR TO F6LD
DX [‹from_callsign›] ‹frequency› ‹callsign› ‹comment› The main command for sending DX spots to other users. Where ‹from_callsign› used when a radio amateur has several call signs.
In fact, to send a DX spot it is enough to enter the command
DX frequency callsign

Examples:
DX 14203 OK7LP/P

You can add notes to the information after the DX callsign:
DX 14207 OK7LP/P QRV from park /P

You can also fulfill another user's request by sending a DX spot on their behalf: DX BY
DX BY RV1BF OK7LP/P 14212 OK7LP/P He is not on the cluster

Frequencies in the command must be entered in kHz. For a detailed list of bands, see the command output. SHOW/BANDS
Echo ‹string› Output a string of characters. The characters can include tabs \t, beeps \a, and newlines \n.
Example:
echo Test
reject ... Reject something (filters). See also command description accept- but the command reject has the ability to reject something.
reject announce Creates a filter string to reject a specific ad. If the ad matches the filter, "reject announce", the announcement is rejected. Options for the "reject announce" command:

info ‹string› Example: info iota or qsl
by ‹prefixes› Example: by G,M
origin the ‹prefix› of the "origin ..." command is used by admins
origin_dxcc ‹prefixes/numbers› For example: 61,62 (from output: sh/pre G)origin_itu ‹prefixes/numbers› For example: G,GM,GW
origin_zone ‹prefixes/numbers›
origin_state ‹states› For example: VA,NH,RI,ME
by_dxcc ‹prefixes/numbers› Filter the list of DXCC countries, for example: G,F
by_itu ‹prefixes/numbers› - filter by ITU zones, for example. 19
by_zone ‹prefixes/numbers›
by_state ‹states› Example: VA,NH,RI,ME
channel ‹prefixes› Used by admins
wx 1 weather announcement filter
dest ‹prefixes› List of distributors, for example: 6MUK,WDX
reject spots Creates a filter drain to reject a specific DX spot. The 'reject' filter line means that if a spot matches this filter, it is discarded (not passed down the filter list).
Options for the "reject spots" command:
reject/spots [0-9] ‹sample› , where ‹sample› is one of the following options:
freq ‹frequency range›
on ‹frequency range›
info ‹line›
call ‹prefixes›
call_dxcc ‹prefixes›
call_itu ‹numbers›
call_zone ‹numbers›
call_state ‹2-character US state abbreviation›
by ‹prefixes›
by_dxcc ‹numbers›
by_itu ‹numbers›
by_zone ‹numbers›
by_state ‹2-character US state abbreviation›
origin ‹prefixes› Used by admins, not users.
channel ‹prefixes› Used by administrators, not users.


Prefix "call" refers to DX radio station
Prefix "by" - the author of the DX spot, the one who sent the DX spot to the cluster.
USING FILTERS DXspider allows users to apply filters to limit the display of a list of DX spots. Filters are specified by keywords accept/spots - accept spots and reject/spots- reject spots. You can create a complex custom filter consisting of several, up to 10 lines.
accept/spots ... Allow spots... (see the description of the ACCEPT/SPOTS command at the beginning of the table)

Examples:
accept/spots vhf - receive spots only from VHF bands
accept/spots hf/cw and by_zone 14,15,16 - display only spots on HF in telegraph, from ITU zones 14, 15, 16
accept/spots by_dxcc UA - accept spots only from Russia
accept/spots by_state VA,NH,RI,ME - accept spots from US states
reject/spots ... Ban spots ...
reject/spots on hf/cw - reject spots in the telegraph on HF
reject/spots on hf/cw and not info iota - disable spots in the HF telegraph that have a mark "iota".

It's important to remember that if you specify the "reject" filter (or multiple "reject/spots" rows), you'll receive anything that doesn't match any of the filter rows. BUT IF you specify the "accept" filter, all records that don't match the "accept" filter will be discarded.

For example, if you have a filter for receiving spots: accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16) then you will automatically receive VHF spots from CQ zones 14,15,16, and the remaining DX spots will be discarded.
COMBINING SEVERAL FILTERS You can combine several accept and reject rules (up to 10 in total) into a complex combined filter. To do this, each rule must be assigned a number when added. For example:
reject/spots 1 on hf/cw
reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
This filter turns off all CW spots on short waves and rejects spots on VHF 50 - 144 MHz not from Europe.

If you omit the digit of the filter number in the command, the system assumes 1. The available filter line numbers are from 0 to 9. In expressions, you can omit the keyword "and", combine several conditions using parentheses. Because "AND" takes precedence over "OR", in conditions where "AND" and "OR" are used in the same expression, use parentheses to specify the precedence of the operations. Example:
(on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
EDITING AND REMOVING FILTERS If you want to fix the filter, redefine it by specifying the line number. Example of filter replacement:

reject/spots 1 on hf/ssb
reject/spots 1 on hf

Or, delete the filter and create it again:
clear/spots 1

To delete all filters, enter the command
clear/spots all

You can CLEAR other filters in the same way:
clear/announce
clear/wcy
clear/wwv
USING 10 FILTER SLOTS DXSpider has ten available filter slots for 'accept' and ten for 'reject'. Each slot contains one reject rule and one accept rule. Thus, each filter type can contain up to ten rows of rules contained in these ten slots. The filter rules must be numbered sequentially, i.e. 0-9 lines of 'reject' filter rules and 0-9 lines of 'accept' filter rules, to correspond to their position in the slot. If a number is not used, each row is assumed to be in slot 1, and adding a second filter row of the same type without a number will simply overwrite the first one that was previously written to slot 1. (Why not slot 0? That's how it works.) Important: The filter rules are applied sequentially, i.e., from 0 to 9. The rules are applied on each row in that order. They act on the 'reject' filter in each slot, before acting on the 'accept' filter contained in that slot. If a slot is completely empty, or if there is no filter string 'reject' or 'accept' in that slot, it moves directly to the next filter rule in sequence from 0 to 9.

Example sequence:
1) slot 0 reject
2) slot 0 accept
3) slot 1 reject
4) slot 1 accept
5) slot 2 reject
6) slot 2 accept
...
19) slot 9 reject
20) slot 9 accept
As a rule, the 'reject' filter rules in a slot are always executed before the 'accept' filter rules. There is a very good reason for this. If a spot does not match the 'reject' filter, the spot is checked against the next filter line in the set.However, if the spot matches the 'accept' filter, it is immediately sent to the user.
help ‹command› Show help for command "command". Commands can be abbreviated, for example, "show/dx" to "sh/dx". Example:
help sh/dx
join ‹group› Join a chat, i.e. a discussion group (global)
See also commands CHAT, LEAVE, SHOW/CHAT
kill ... Commands for deleting private messages. Examples:
kill 1-4 - delete messages №№ from 1 to 4
kill 7 - delete message №7
kill from regular_expression_callsign
kill to regular_expression_callsign
leave ‹group› Leave chat with name ‹group›
links Display information about which links are connected to this node and some information about them. See the command WHO to display a complete list of connections.
read Read the following personal message addressed to me
read ‹No._message› Read personal message with number ‹message#›
reply Reply to personal message
reply ‹No._message› Reply to a personal message with the number ‹message#›
reply b ‹No._message› Reply to a permanent announcement (bulletin) with the number ‹message#›
reply noprivate ‹No._message› Reply to a permanent bulletin with a new bulletin
reply rr ‹No._message› Send a reply receipt to message number ...
send ‹call signs› Create and send a message for one or more call signs
send copy ‹Message No.› ‹call sign› Send a copy of the message to any call sign
reply noprivate ‹call sign› Create and send a message to callsign ‹callsign›

All SEND commands create messages that will be sent either to an individual callsign or to one of the "Bulletin" addresses (permanent pinned announcements).

Command SEND ‹call sign› without parameter noprivate, will do the same as if you had typed SEND private, that is, it will mark the message as personal and send it to the cluster node to which the “callsign” is connected. If you specified a "call sign", which is actually a well-known bulletin category on your node (for example: all), then the message should automatically become a bulletin (sticky message).

You can specify more than one call sign “call sign” in all send commands.

You can specify several actions in one command, for example:
SEND RR COPY 123 PRIVATE G1TLH G0RDI
This command must send a copy of message No. 123 to two call signs G1TLH and G0RDI, you also request a read receipt from each recipient in the "send" command.

Then the system will ask you to enter a message title (usually no longer than 29 characters in Latin). You will then be prompted to enter the text of the message. To finish entering a message, enter on a new line:
/ex

If you do not want the message to be saved (change your mind), enter on a new line

/abort

When you enter the body of your message, most of the normal output (eg DX announcements, etc., are suppressed and stored for the last display (up to 20 lines are stored in the new new message buffer, then the oldest lines are discarded).


In addition, you can enter regular commands (and immediately receive output) right in the middle of the message. To do this, enter a command starting with a '/' on a new line:

/DX G1TLH 144010 strong signal
The command will immediately send an advertisement to the DX cluster for the call sign G1TLH on 144100 and marked "strong signal".

Alternatively, you can add the output of the command to your message by prefixing the command with two '//' characters, thus:-

// sh/vhftable

This will show you the output of the SH/VHFTABLE command, and store it in the message You can continue typing the message until you are ready to send it
send private ‹call sign› Send personal message
send rr ‹call sign› Send Read Receipt
set/address ‹your_address› Specify the address on the cluster
set/announce Allow ads to appear in your terminal
set/anntalk Allow ads similar to talk private messages to appear in your terminal
set/beep Enable beep on DX and other messages in your terminal
set/dx Enable reception of DX spots
set/dxcq Enable DX CQ zone output at the end of DX spot lines
set/dxgrid Enable output of QTH locators at the end of lines of DX spots
set/dxitu Enable DX ITU zone output at the end of DX spot lines
set/echo Enable repeating of entered characters while typing
set/email ‹your_e-mail› Specify e-mail on the cluster
set/here Transfer the status "I'm here" to the cluster
set/homenode ‹your_home_node› Specify the DXspider home node you visit most often
set/language en Set the language for cluster message output and command results to English
set/location ‹latitude› ‹longitude› Enter latitude and longitude. where you are (for calculating distance to DX stations). For example: set/location 60 20 N 30 12 E
set/loginfo Enable display of information about user logins and logouts
set/page ‹number› Set the number of lines on screen (default 20) when outputting command results - when the output stops waiting for the Enter key to be pressed. Setting 0 disables split screens
set/password Set your personal password to log into the cluster. When you log in for the first time, the system prompts you to enter a password - this is the initial password. In the future, after logging in, you can change it to another one. You will be prompted to enter your new password twice (to ensure it is entered correctly). No characters are entered on the screen while entering a password.
set/prompt ‹line› Set the prompt text when entering commands. For example, set/prompt#
set/qra ‹locator› Set your home QTH locator (QRA). If you previously entered coordinates in the set/location command, the QRA locator will be calculated approximately based on the entered coordinates. You can specify the locator precisely. Example: set/qra ko50cj
set/qth ‹string› Set the text that will be displayed next to your callsign in the information about you on the node. Example: set/qth Smolensk
set/startup Create your own set of commands that will be executed after each login. You can add a script in one action; there is no editing option. Entering a script is similar to the SEND command - enter the script line by line. When finished, enter

at the beginning of the line /EX

To cancel the entry, i.e. exit without saving - at the beginning of the line enter:

/abort

To output empty lines in a script, use the BLANK command, which simply outputs an empty line (text break). To remove the startup script, enter the command

unset/startup
set/talk Enables the output of messages of the TALK type - messages between cluster users
set/usstate Includes in the DX spot output an indication of the 2-letter abbreviation of the state from which the radio amateur operates
set/wcy Enables output of WCY messages from DK0WY(current indices A, K, SFI ionospheric indicators)
set/wwv Includes WWV message output (WWV forecasts, geomagnetic storm warnings)
set/wx Enables weather reporting
show/chat ‹group› ‹number_lines› This command allows you to see any chat or conferences that happened while you were away. The show/cat command without parameters will show data for all groups. If you use a group name, then it will show the chat for that group only.
show/configuration ‹node› This command allows you to see all cluster users and the nodes they are connected to. This command is usually abbreviated as:
sh/c
Since hundreds of users can be connected to a cluster, this command limits the output to users in your country. However, you can list all users, from all countries, connected to all cluster nodes:
sh/c all
It is also possible to limit the output to one country, for example, sh/c EA
show/configuration/node List users of only this node (local)
show/contest ‹year› ‹month› Display all competitions known to the system that have taken place or will take place in the specified year and month. The current list of contests is maintained at http://www.sk3bg.se/contest/ The year and month query format is quite flexible. Example: sh/contest Dec2022 or sh/contest 2023 april
show/date ‹prefix or callsign› Shows the local date for the prefix or callsign. The output is very similar to show/time, differs only in the output format. If no prefix or call sign is specified, this command returns the local time, in UTC, of ​​your computer. If you give some prefixes, then it will show the UTC - and UTC + (not including DST) offset for the given prefix or call sign.
show/db0sdx ‹callsign› Displays callsign information from the QSL server db0sdx database on the Internet and displays the information available for that callsign.
See also commands SHOW/QRZ and SHOW/WM7D.
show/dx Displays the latest DX spots (usually 10).
You can specify any number of additional parameters, in almost any order, from the list below:


on ‹band› - on the frequency band. Example: on 160m 80m
on ‹region› - in the frequency region. Example: on vhf
on ‹frequency_1› - ‹frequency_2› or on ‹frequency_1› / ‹frequency_2›. Example: on 0/30000
‹number› - the desired number of DX spot lines in the command output
‹prefix› - the initial part of the callsign whose DX spots you are looking for. Example: GM
‹suffix› - the final part of the callsign whose DX spots you are looking for. Example: EK
*‹part_of_the_callsign›* - middle part of the callsign. Example: *A1A*
day ‹number_of_days› - for the specified number of days, past from today
day ‹from›-‹to› or day ‹from›/‹to› - for the specified date range
info ‹string› - search by spot note. Example: info iota
by ‹callsign› - spots sent by call sign (same as:
spotter ‹callsign› - search for DX spots by their author).
qsl - Automatic request for QSL information by callsign.
iota ‹island_number›
qra ‹locator› - search by a specific QTH locator
dxcc ‹country› - Search by DXCC country code regardless of the actual prefix. Example: DXCC OQ2
real or rt - Output DX spots in real time. The output formats of these commands are intentionally different. This is useful for some hardware loggers that use DX clusters but cannot handle the normal output of the sh /dx command. The command has an alias: sh/fdx.
filter - Filter spots before executing the command using the user's DX spot filter. Alias: sh/mysdx.
zone - list of CQ zones from which DX radio stations operate
by_zone - list of CQ zones from which people publish
itu - comma-separated list of ITU DX zones of radio stations
by_itu - list of ITU zones from which people publish
state- DX from the list of US states (2 letter state symbols)
by_state - list of US states from which people post


Examples:
SH/DX 9m0
SH/DX on 20m info iota
SH/DX 9a on vhf day 30
SH/DX rf1p qsl
SH/DX iota
SH/DX iota eu-064
SH/DX qra jn86
SH/DX dxcc oq2
SH/DX dxcc oq2 by w dxcc
SH/DX zone 4,5,6
SH/DX by_zone 4,5,6
SH/DX state in,oh
SH/DX by_state in,oh
show/dxcc ‹prefix› The command takes the country prefix ‹prefix› (if desired, you can specify the beginning or part of the call sign), queries (to the database) which country it belongs to. The command then shows all the spots for the given country to which the ‹prefix› belongs. This is now an alias for the 'SHOW/DX DXCC' command (see above). SH/DX command options can be applied to the show/dxcc command. Examples:
SH/DXCC G
SH/DXCC W on 20m iota
What can be done in another way using the commands:
SH/DX dxcc g
SH/DX dxcc w on 20m iota
show/dxqsl ‹call sign› The command collects information about QSL from the comment field of the spot and saves the collected information into the database. This command allows you to then "query" the database for the QSL manager of the callsign you are looking for, using other people's previously published spots. This information is NOT reliable, but is sometimes accurate if the DX spot call sign with manager has been sent many times. Example:
sh/dxqsl 4k9w

You can check “raw” spots with this command:
sh/dxqsl 4k9w qsl
show/dxstats ‹number_days› ‹date› Display statistics on the total number of DX spots for the last ‹number_days› days preceding the date ‹date›. By default, ‹number_days› is 31, ‹date› is today.
show/fdx Output spots in real time.
Difference from the SH/DX command in output format. You can compare both. The FDX command is more suitable for hardware logging programs that cannot handle the SH/DX format.
The command is an alias for
SHOW/DX real
show/files This command is used primarily by node administrators to display the storage areas of the file system. For example, you can find out where declarations like "bulletin":

SH/FILES bulletins

To display the contents of a file, use the command TYPE.
show/filters Display the contents (text) of all filters that you have installed. This command displays all filters in all categories.
show/hfstats ‹number_days› ‹date› Display statistics about DX spots broken down by HF bands for the last ‹number_days› days starting from date ‹date›. By default, ‹number_days› is 31, ‹date› is today.
show/hftable ‹number_days› ‹date› ‹prefixes› Display statistics on short waves: a table of DX spotters (call signs) from the specified prefixes ‹prefixes› for the last ‹number_days› days starting from the date ‹date›. By default, ‹number_days› is 31, ‹date› is today. If ‹prefixes› are not specified, statistics for your country are displayed. A detailed description of the command is given in paragraph 12.98 dXspider user manuals.
show/moon ‹number_days› ‹prefix or call sign› Show moonrise and moonset times. A detailed description of the command is given in paragraph 12.99 dXspider user manuals.
show/muf ‹prefix› [LONG] Calculate the probability of establishing radio communication from your home QTH to the specified prefix ‹prefix›, taking into account the season, indices of radio wave propagation conditions and other parameters (using the MINIMUF 3.5 subroutine developed by the US Navy). The program predicts future propagation conditions and displays a table for the HF bands. The last column shows the calculated signal strength using the S-meter. LONG option for long path calculations.
show/mydx Unlike the SHOW/DX command, which displays all spots available in the DX system, the output of the SHOW/MYDX command contains only spots that match the user's previously set filters. It filters all spots using the filters you set (see SHOW/FILTERS). However, the show/mydx command can currently only display spots on shortwave (HF). Also with the command SHOW/MYDX all options of the SHOW/DX command described above can be applied.
show/newconfiguration ‹node› This command allows you to see all the users that can be seen and the hosts they are connected to.

This command gives essentially the same information as Show/Configuration, except that it shows all duplicates of any routes that may be present. It also uses a different format that may not take up as much space if you don't have loops.

Be careful: the list returned can be very long.
show/newconfiguration/node List all nodes. connected to this cluster node, in a new format.
show/prefix ‹callsign› This command takes a callsign, finds out from the database which ITU country it belongs to, and outputs a list of all suitable prefixes that can be used in the same country, also with the country number, CQ zone, and ITU zone. See also the command SHOW/DXCC
show/qra ‹locator1› ‹locator2›
or
show/qra ‹locator›
or
show/qra ‹latitude› ‹longitude›		 This universal command can either calculate the distance and direction between two QTH locators, or the distance from your home station to a square (if only one is specified), or calculate a locator at given geographic coordinates.

Examples:
SH/QRA JN06 IN73
SH/QRA IO92QL
SH/QRA 52 41 N 0 58 E
show/qrz ‹call sign› Displaying callsign information from the QRZ.com server on the Internet.
show/route ‹callsign› This command allows you to see which node the specified callsign is connected to. The command is largely the opposite to the sh/config command.
show/satellite ‹sat_name› Show orbital calculations for the specified satellite, visible above the horizon from your home QTH (see SET/QRA) a few hours ahead (default 3 hours). You can increase the number of hours using the second command parameter.

Example:
SH/SAT SO-50
SH/SAT SO-50 8
show/startup Show the script you specified (list of commands) executed each time you start
show/sun ‹number_days› ‹prefix or call sign› Command to calculate the sunrise and sunset times for the specified call sign ‹prefix or call sign›, ‹number_days› ahead. If you specify a negative number of days (with a minus), the command performed the calculation for the specified number of days ago. For more details, see the description in the paragraph 12.112.
show/time ‹prefix or call sign› If the prefix or call sign is not specified, then this command returns your local time, in UTC - the time that your computer currently has. If you specify a prefix or call sign, the command output will show the UTC time and UTC+ or UTC- offset (not including DST - Daylight Saving Time) for the prefix or call sign you specified.
show/usdb ‹call sign› For US call signs only: retrieve call sign information from FCC database
show/vhfstats Display statistics about DX spots broken down by VHF bands for the last ‹number_days› days starting from date ‹date›. By default, ‹number_days› is 31, ‹date› is today.
show/vhftable ‹number_days› ‹date› ‹prefixes› Display statistics on short waves: a table of DX spotters (call signs) from the specified prefixes ‹prefixes› for the last ‹number_days› days starting from the date ‹date›. By default, ‹number_days› is 31, ‹date› is today. If ‹prefixes› are not specified, statistics for your country are displayed. A detailed description of the command is given in paragraph 12.98 dXspider user manuals.
show/wcy Show the latest 10 ionospheric index broadcasts from WCY
show/wcy ‹number› Show the latest ‹number› of ionospheric indices database entries from WCY
show/wm7d ‹callsign› Access the wm7d database on the Internet and retrieve callsign information from it (available for US callsigns). This information is provided by the software at http://www.wm7d.net.
See also the command SHOW/QRZ.
show/wwv Show the latest 10 ionospheric magnetic storm forecasts/warnings from WWV.
show/wwv ‹number› Display the latest ‹number› of WWV ionospheric forecasts.
sysop When a user connects to a telnet cluster, he receives the privileges of a regular user. This command allows the node administrator to elevate privileges to administrator level.
talk ‹callsign› ‹text›

or


talk ‹callsign› ‹node› ‹text›		 Send a chat message to callsign ‹callsign› on node ‹node› with text ‹text›.

You can send a short message to any other station visible in the cluster system. You can send it to everyone you can see with the command show/configuration.

If you want to chat with someone, you can leave a text message and the system will go into "conversation" mode. What this means is that a short message is sent to the recipient telling them that you are in a "talking" mood, and then you simply type - whatever you send will go to the station you asked for.

All regular announcements, DX spots and so on will still go out to your terminal.

If you want to do something (like send a DX spot) during a conversation, put a '/' symbol at the beginning of a regular command from the beginning of the line, for example:

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

Commands starting with "/" will not go into the chat of the person you are writing to.

To exit the conversation mode, enter:

/EX

A double slash ("double slash" - //) at the beginning of the line allows you to send the output of the command to the person with whom you are talking:

//sh/hftable
type/filearea View the contents of the file storage.
unset/something Disable. For example:
unset/unnounce - disable announcements
unset/anntalk - disable anntalk messages
unset/beep - disable the sound signal
unset/dx - disable DX spots - messages about DX radio stations
unset/dxcq - disable adding a CQ zone at the end of the line of DX spots
unset/dxgrid - disable the display of a square at the end of the DX line spots
unset/dxitu - disable the display of both zone numbers at the end of the DX line (spotter and DX radio station)
unset/echo - disable character repetition in the cluster terminal
unset/email - if personal messages are sent to your e-mail address, you can disable it with this command
unset/here - indicate to the terminal that you are away from the keyboard
unset/privilege - refuse administrator privileges
unset/promt - refuse a non-standard invitation. The invitation will be reset to SET/PROMPT %C de %M %D %T dxspider > , where %C is the call sign, %M is the cluster, %D is the date, %T is the time.
unset/startup - clear the startup script
unset/talk - disable receiving Talk messages (conversations)
unset/usstate - disable the display of US states at the end of the line of DX spots
unset/wcy - disable the output of messages about ionospheric indices from WCY
unset/wwv - disable the output of transit forecasts from WWV
unset/wx - disable the output of weather messages
who Displays a quick list of callsigns that are connected to a node and what type of connections they are using
wx Send weather message to local node users
wx full Send weather message to all cluster users

Source:



Related publications

Languages

Theme

RSS feeds

Atom 1.0 RSS

Popular tags

Random post

I'll be lucky!

Archive of posts

Search here

Weather forecast