# if the command ends in a - then that line isn't printed, but any
# subsequent lines are
#
-# $Id$
+#
#
# Comment lines are indented before printing
#
=== 0^ACCEPT/SPOTS [0-9] <pattern>^Set an 'accept' filter line for spots
+=== 0^ACCEPT/RBN [0-9] <pattern>^Set an 'accept' filter line for RBN spots
Create an 'accept this spot' line for a filter.
An accept filter line means that if the spot matches this filter it is
A sysop can clear an input or normal output filter for a user or the
node_default or user_default.
+=== 6^CLEAR/DUPEFILE^Clear out the dupefile completely
+The system maintains a list of duplicate announces and spots (amongst many
+other things). Sometimes this file gets corrupted during operation
+(although not very often). This command will remove the file and start
+again from scratch.
+
+Try this if you get several duplicate DX Spots, one after another.
+
+Please ONLY use this command if you have a problem. And then only once.
+If it does not cure your problem, then repeating the command won't help.
+Get onto the dxspider-support list and let us try to help.
+
+If you use this command frequently then you will cause other people, as
+well as yourself, a lot of problems with duplicates.
+
=== 0^CLEAR/ROUTE [1|all]^Clear a route filter line
This command allows you to clear (remove) a line in a route filter or to
remove the whole filter.
use the script in /spider/connect/<callsign> to effect the 'chat' exchange
necessary to traverse the network(s) to logon to the cluster <callsign>.
+=== 5^CREATE/USER <callsign> ...^Create this user from the User Database
+This command will create one or more new users. None of the fields
+like name, qth etc will be filled in. It is just a new entry in the user
+database to which one can add more stuff like SET/PASSWORD or by SPOOF.
+
=== 9^DELETE/USDB <callsign> ...^Delete this user from the US State Database
This command will completely remove a one or more callsigns
from the US States database.
locally.
See DBIMPORT for the importing of existing AK1A format data to databases.
+See DXEXPORT for how to export an AK1A data in a form able to be imported.
See DBSHOW for generic database enquiry
-
+
+
+=== 9^DBEXPORT <dbname> <filename>^Export an AK1A data to a file
+Sometimes one needs to export the data from an existing database file,
+maybe for a backup or to send to another node.
+
+ DBEXPORT oblast /tmp/OBLAST.FUL
+
+will export the OBLAST database to /tmp/OBLAST.FUL
+
+There is no protection, it is up to you not to overwrite a file that
+is important to you.
+
+See DBIMPORT for the importing of existing AK1A format data to databases.
+
=== 9^DBIMPORT <dbname> <filename>^Import AK1A data into a database
If you want to import or update data in bulk to a database you can use
this command. It will either create or update entries into an existing
will import the standard OBLAST database that comes with AK1A into the
oblast database held locally.
+See DBEXPORT for how to export an AK1A database
+
=== 9^DBREMOVE <dbname>^Delete a database
DBREMOVE will completely remove a database entry and also delete any data
file that is associated with it.
=== 5^DIRECTORY-^
Sysops can see all users' messages.
-=== 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
-Disconnect any <call> connected locally
+=== 8^DISCONNECT <call> [<call> ...]^Disconnect user(s) or node(s)
+Disconnect any <call> connected locally.
+
+In addition you can disconnect all users (except yourself) with
+
+ DISC users
+
+or all nodes with:
+
+ DISC nodes
+
+or everything (except yourself) with
+
+ DISC all
=== 0^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
The <freq> is compared against the available bands set up in the
cluster. See SHOW/BANDS for more information.
+=== 9^DXQSL_EXPORT <filename>^Export SH/DXSQL information to a file
+The SHOW/DXQSL command shows any QSL managers that have been extracted
+from comments on a DX spot.
+
+Use this command to export the current state of the information to
+a CSV style text file. For example:
+
+ DXQSL_EXPORT /tmp/qsl.csv
+
+NOTE: this command will overwrite any file that you have write
+permission for.
+
+See also DXQSL_IMPORT to import one of these files.
+
+=== 9^DXQSL_IMPORT <filename>^Import SH/DXSQL information from a file
+The SHOW/DXQSL command shows any QSL managers that have been extracted
+from comments on a DX spot.
+
+Use this command to restore a file created by the DXSQL_EXPORT command.
+For example:
+
+ DXQSL_IMPORT /tmp/qsl.csv
+
+The data in this file will UPDATE any information that may already be
+present. This may not be what you want. To make the data the same as
+the import file then you must:
+
+* stop the node
+* remove /spider/data/qsl.v1
+* restart the node
+* login as sysop
+* do the import
+
+Preferably before too many DX spots with qsl manager info come in.
+
=== 0^ECHO <line>^Echo the line to the output
This command is useful in scripts and so forth for printing the
line that you give to the command to the output. You can use this
be broadcast in PC41 protocol packets. This information is Name, QTH, Location
and Homenode. PC41s are only sent for the information that is available.
+=== 8^GET/KEPS^Obtain the latest AMSAT Keplarian Elements from the web
+There are various ways that one can obtain the AMSAT keps. Traditionally the
+regular method was to get on the mailing list and then arrange for the email
+to be piped into convkeps.pl and arrange from the crontab to run LOAD/KEPS.
+For various reasons, it was quite easy for one to be silently dropped
+from this mailing list.
+
+With the advent of asynchronous (web) connections in DXSpider it is now
+possible to use this command to get the latest keps direct from the
+AMSAT web site. One can do this from the command line or one can add a line
+in the local DXSpider crontab file to do periodically (say once a week).
+
+This command will clear out the existing keps and then run LOAD/KEPS
+for you (but only) after a successful download from the AMSAT website.
+
=== 0^HELP^The HELP Command
HELP is available for a number of commands. The syntax is:-
can get confused if you are doing a lot of moving commands about or
delete a command in the local_cmd tree and want to use the normal one
again. Execute this command to reset everything back to the state it
-was just after a cluster restart.
+was just after a cluster restart. To see what is in the command cache
+see SHOW/CMD_CACHE.
=== 9^LOAD/FORWARD^Reload the msg forwarding routing table
Reload the /spider/msg/forward.pl file if you have changed it
it takes is output to the console in seconds.
Any visible cluster node can be PINGed.
+=== 0^RBN^The Reverse Beacon or Skimmer System
+DXSpider now has the ability to show spots from the Reverse Beacon Network
+or "Skimmers", if your sysop has enabled the feed(s) (and has the bandwidth
+to both receive the feeds and also to pass them on to you.
+
+Currently there are two RBN/Skimmer feeds available which, at busy
+times can send up to 50,000 spots/hour EACH. Somewhere in the low
+1000s is more normal. Clearly this is not much use to the average user
+and so DXSpider "curates" them by removing duplicates and checking for
+invalid callsigns or prefixes, as well as using some algorithms to fix
+the rather variable frequencies that some skimmers produce
+(particularly for CW spots).
+
+This means that the format of the spot that you see is completely
+different to the spots that the RBN feeds supply and, as a result of
+the "curation" reduces the volume of spots to you by between 8 and 11
+times.
+
+See SET/SKIMMER (or SET/WANTRBN) for more information on enabling
+RBN/Skimmer spots and also on selecting particular categories (e.g CW
+or FT8/FT4) - which has the side benefit of reducing the volume of
+spots that you receive even more!
+
+Here are some examples of the output:
+
+DX de LZ4UX-#: 14015.5 ON7TQ CW 6dB Q:9 Z:5,14,15,40 14 0646Z 20
+DX de VE7CC-#: 3573.0 N8ADO FT8 -14dB Q:4 Z:4,5 4 0647Z 3
+DX de DM7EE-#: 14027.5 R1AC CW 9dB Q:9* Z:5,15,17,20 16 0643Z 14
+DX de WE9V-#: 7074.0 EA7ALL FT8 -9dB Q:2+ Z:5 14 0641Z 4
+
+Note that UNSET/DXGRID, UNSET/DXITU and SET/DXCQ are in operation in
+these examples. This is completely optional.
+
+The comment field has been completely changed in order provide as much
+information, in as smaller space, as possible. All the irrelevant
+information has been removed.
+
+You can use the Category (CW and FT8 in these examples) to with
+SET/SKIMMER (or SET/WANTRBN) to, rather coarsely, select which spots
+you require. You can refine this further by the use of Filtering. See
+SET/SKIMMER or SET/WANTRBN for more information. But the short answer
+is that these are spots and are filtered like any other spot, unless
+you want to filter these spots differently, in which case you can use
+REJECT/RBN and ACCEPT/RBN in exactly the same way as ACCEPT/SPOT and
+REJECT/SPOT. If you don't use RBN filters then these spots will be
+filter by any spot filters that you may have.
+
+The next field (6dB, -14dB etc) is the LOWEST reported signal that was
+heard.
+
+The Q: field is the number of skimmers that heard this spot (up to 9
+shown, but it could easily be many more). If Q: is > 1 (especially on
+CW) then you can be reasonably certain that the callsign is accurate,
+especially on CW. 'Q' stands for "Qualitee" :-)
+
+If there is a '*', it means that there was a disagreement about
+frequency. In fact, particularly for CW spots, I have see
+disagreements of 600Hz. Which is a worry. The frequency that is shown
+is the majority view of all the skimmers spotting this call. You may
+have to fossick about the airwaves to find the actual frequency :-)
+
+There are stations that are permanently on, like Beacons, and also
+others that have long sessions on the same frequency and do a lot of
+CQing. If they have been on for a certain length of time and they
+reappear before their cache entry expires (about 2 hours), then they
+are respotted. This is indicated by the '+'. NOTE - if they change
+frequency, this will generate new spots. Each callsign/frequency pair
+could respotted separately for as long as any individual
+callsign/frequency pair remain in the cache.
+
+The Z: field is present then that indicates the other CQ zones that
+heard this spot - not including the skimmer that is shown. I show as
+many as there are in whatever space is left in the comment
+field. Note: if you have any of the optional flags around the time
+then they may overwrite part of this field.
+
+If there is NO filter in operation, then the skimmer spot with the
+LOWEST signal strength will be shown. This implies that if any extra
+Z: zones are shown, then the signal will be higher in those zones.
+
+If you have a filter (for instance: ACCEPT/SPOT by_zone 14 and not
+zone 14 or zone 14 and not by_zone 14) where '14' is your QTH CQ
+zone. You will, instead be served with the lowest signal strength spot
+that satisfies that filter. Incidentally, this particular style of
+filter is quite useful for RBN spots, as it reduces the volume and is
+likely to be more relevant for casual use. If this filter is too broad
+(or narrow) for your normal spotting requirements, then you can use
+ACCEPT/RBN with the same filter specification and it will only apply
+to RBN spots. You can also replace '14' with a list like '14,15' if
+you want to broaden it out. You will still get the same Z: list (if
+any) whether you filter or not.
+
=== 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
This command allows you to send nearly any command to another DX Cluster
node that is connected to the system.
reject/ann user_default by G,M,2
=== 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
+=== 0^REJECT/RBN [0-9] <pattern>^Set a 'reject' filter line for RBN spots
Create a 'reject this spot' line for a filter.
A reject filter line means that if the spot matches this filter it is
message.
You can carry on with the message until you are ready to send it.
+
+=== 6^SEND_CONFIG^Broadcast PC92 C records
+This is the PC92 equivalent of INIT. In that it will send out a new
+PC92 C record to all interfaces. This can be used to bring other nodes
+up to date quicker after a restart.
+
=== 0^SET/ADDRESS <your address>^Record your postal address
+=== 9^SET/AGWENGINE^Enable the AGW Engine
+=== 9^UNSET/AGWENGINE^Disable the AGW Engine
+These commands assume that /spider/local/AGWConnect.pm has been setup
+correctly and you wish to do some testing or otherwise want to alter
+the default state of your connection to the AGW Engine.
+
+=== 9^SET/AGWMONITOR^Enable Monitoring on the AGW Engine
+=== 9^UNSET/AGWMONITOR^Disable Monitoring on the AGW Engine
+
=== 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
=== 0^UNSET/ANNOUNCE^Stop announce messages coming out on your terminal
=== 5^SET/ARCLUSTER <call> [<call>..]^Make the callsign an AR-Cluster node
-=== 8^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
-=== 8^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
+=== 6^SET/BADDX <call>..^Stop callsigns in a dx spot being propagated
+=== 6^UNSET/BADDX <call>..^Propagate a dx spot with this callsign again
Setting a word as 'baddx' will prevent spots with that word in the
'spotted' field (as in: DX 14001.1 FR0G)of a DX spot from going any
further. They will not be displayed and they will not be sent onto
unset/baddx VIDEO
-=== 8^SET/BADNODE <call>..^Stop spots from this node being propagated
-=== 8^UNSET/BADNODE <call>..^Allow spots from this node again
+=== 6^SET/BADNODE <call>..^Stop spots from this node being propagated
+=== 6^UNSET/BADNODE <call>..^Allow spots from this node again
Setting a callsign as a 'badnode' will prevent spots from that node
going any further. They will not be displayed and they will not be
sent onto other nodes.
Use with extreme care. This command may well be superceeded by FILTERing.
-=== 8^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
-=== 8^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
+=== 6^SET/BADSPOTTER <call>..^Stop spots from this callsign being propagated
+=== 6^UNSET/BADSPOTTER <call>..^Allow spots from this callsign again
Setting a callsign as a 'badspotter' will prevent spots from this callsign
going any further. They will not be displayed and they will not be
sent onto other nodes.
Use with extreme care. This command may well be superceded by FILTERing.
-=== 8^SET/BADWORD <word>..^Stop things with this word being propagated
-=== 8^UNSET/BADWORD <word>..^Propagate things with this word again
+This command will also stop TALK and ANNOUNCE/FULL from any user marked
+as a BADSPOTTER.
+
+=== 6^SET/BADWORD <word>..^Stop things like this word being propagated
Setting a word as a 'badword' will prevent things like spots,
announces or talks with this word in the the text part from going any
further. They will not be displayed and they will not be sent onto
other nodes.
-The word must be written in full, no wild cards are allowed eg:-
+This has changed its meaning from the master release. All words entered
+are reduced to the minimum regex that will match words starting like
+this one:
+
+ set/badword annihilate
+
+will stop anything that starts with these words in the text
+like this:
- set/badword annihilate annihilated annihilation
+ annihilate annihilated
-will stop anything with these words in the text.
+but it will also stop things like this:
- unset/badword annihilated
+ anihilate annni11ihhh ii lllattt eee
+
+A few common 'leet' substitutions are automatically matched:
+
+ b0ll0cks bo0lll0ccckks fr1iigging
+
+and so on
-will allow text with this word again.
+It will not stop some things like:
+
+ The base word FRIG will stop 'friiigging' but not 'friiig ging'
+
+=== 6^UNSET/BADWORD <word>..^Propagate things like this word again
+This is the opposite of set/badword <word>
+
+ unset/badword fred
+
+will allow text with this word again (if it has been set as a bad word.
=== 0^SET/BEEP^Add a beep to DX and other messages on your terminal
=== 0^UNSET/BEEP^Stop beeps for DX and other messages on your terminal
=== 5^SET/BBS <call> [<call>..]^Make the callsign a BBS
+=== 0^SET/BUDDY <call> [<call>..]^Add this call to my buddy list
+=== 0^UNSET/BUDDY <call> [<call>..]^Remove this call from my buddy list
+A notification message
+is sent to you automatically if anybody on your buddy list logs in or
+out of any node in this cluster.
+
=== 5^SET/CLX <call> [<call>..]^Make the callsign an CLX node
=== 9^SET/DEBUG <name>^Add a debug level to the debug set
the languages available are en (English), de (German), es (Spanish),
Czech (cz), French (fr), Portuguese (pt), Italian (it) and nl (Dutch).
+=== 5^SET/LOCAL_NODE^Add node to the local_node group
+=== 5^UNSET/LOCAL_NODE^Remove node from the local_node group
+The 'local_node' group is a group of nodes that you want a user
+to perceive as effectively one big node. At the moment, this extends
+only to announcing whenever a user is logging in or out of one of
+the nodes in the group (if those users have SET/LOGININFO).
+
+The local node group is as setup on this node. If you want the other
+nodes to also include this node and all the other nodes specified, then
+you must get those nodes to also run this command (or rcmd them to do
+so).
+
+In principle, therefore, each node determines its own local node group
+and these can overlap with other nodes' views.
+
=== 0^SET/LOCATION <lat & long>^Set your latitude and longitude
=== 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
In order to get accurate headings and such like you must tell the system
then this command will set your QRA locator for you. For example:-
SET/LOCATION 52 22 N 0 57 E
-=== 0^SET/LOGININFO^Inform when a station logs in locally
-=== 0^UNSET/LOGININFO^Inform when a station logs out locally
+=== 0^SET/LOGININFO^Inform when a station logs in/out locally
+=== 0^UNSET/LOGININFO^No longer inform when a station logs in/out locally
=== 9^SET/LOCKOUT <call>^Stop a callsign connecting to the cluster
=== 9^UNSET/LOCKOUT <call>^Allow a callsign to connect to the cluster
+=== 8^SET/MAXCONNECT <value> [<call> ..]^Set max incoming connections for user/node
+Set the maximum no of connections (parents) an incoming user or node is
+allowed to have. If this incoming connection takes it over the separate
+limits for users and nodes (defaults: 3 and 8 respectively), then the
+connection is refused (with a polite message).
+
+The idea behind this to limit the number of copies of messages that
+are sent to users (and nodes). Nodes really don't need to have more than
+5 or 6 partners and users don't need more than two connections into the
+cluster cloud.
+
+This check is only for INCOMING connections, no check is performed for
+outgoing connections.
+
=== 0^SET/NAME <your name>^Set your name
Tell the system what your name is eg:-
SET/NAME Dirk
Tell the system where you are. For example:-
SET/QTH East Dereham, Norfolk
+=== 9^SET/RBN <call> ...^Mark this call as an RBN node
+This will mark this callsign as a Reverse Beacon
+Network client. It's not a node in the normal sense of that word
+in DXSpider. But it will generate spots from the RBN/Skimmers and
+will act like a specialised node just for RBN spots.
+
+You will need to use this command to create your skimmer node
+connections. Normally one per RBN port (7000, 7001) but, in principle
+you could connect to any skimmer that uses the same spot format.
+
=== 9^SET/REGISTER <call> ...^Mark a user as registered
=== 9^UNSET/REGISTER <call> ...^Mark a user as not registered
Registration is a concept that you can switch on by executing the
Tell the system that the call(s) are to be treated as DXSpider node and
fed new style DX Protocol rather normal user commands.
+=== 5^UNSET/SPIDER <call> [<call>..]^Make the callsign a normal user
+=== 5^UNSET/ARCLUSTER <call> [<call>..]^Make the callsign a normal user
+=== 5^UNSET/NODE <call> [<call>..]^Make the callsign a normal user
+=== 5^UNSET/AK1A <call> [<call>..]^Make the callsign a normal user
+=== 5^SET/USER <call> [<call>..]^Make the callsign a normal user
+
=== 0^SET/TALK^Allow TALK messages to come out on your terminal
=== 0^UNSET/TALK^Stop TALK messages coming out on your terminal
Do a STAT/USER to see which flags you have set if you are confused.
+=== 0^SET/WANTRBN^[category ..]^Allow (some) RBN/Skimmer spots
+=== 0^SET/SKIMMER^[category ..]^Allow (some) RBN/Skimmer spotsT
+=== 0^UNSET/WANTRBN^Stop all RBN/Skimmer spots
+=== 0^UNSET/SKIMMER^Stop all RBN/Skimmer spots
+=== 9^SET/WANTRBN^<call> [category ..]^Allow (some) RBN/Skimmer spots
+=== 9^SET/SKIMMER^<call> [category ..]^Allow (some) RBN/Skimmer spots
+This command allows curated Reverse Beacon Spots to come out on your
+terminal (or not).
+
+If you want everything just type:
+
+ set/wantrbn
+or
+ set/skimmer
+
+Either command will do.
+
+If you want it all to just stop type:
+
+ unset/skimmer (or unset/wantrbn)
+or
+ set/skimmer none
+
+There five categories (or modes) of RBN/Skimmer spot available and one
+can limit the spots to one or more of these categories/modes:
+
+ CW BEACON PSK RTTY FT
+
+together with a load of synonyms
+
+ BEACON BCN DXF
+ PSK FSK MSK
+ FT FT8 FT4
+
+if you use
+
+ set/skimmer psk ft8
+
+you will get psk, fsk, msk, ft4 and ft8 spots. if you want to break
+that down, then you will need to set filters accordingly - but your
+filter will only be offered spots from the categories that you have
+selected.
+
+If you get into a muddle with this you can simply reset 'all on'
+with SET/SKIMMER or 'all off' with UNSET/SKIMMER.
+
+By default any filters that you have for "manual" spots will be
+automatically applied to your RBN/Skimmer feed. However it is possible
+to filter RBN/Skimmer spots differently by use ACCEPT/RBN and/or
+REJECT/RBN filters.
+
+The RBN filters completely override any spot filters for these
+spots. But the spot filters will continue to filter "manual" spots as
+before.
+
+NOTE: Filters and this command CAN interact with each other. If you
+don't get the results that you expect, check your filters with
+SHOW/FILTER.
+
+Please see HELP RBN for an explanation of the spot format. It is NOT
+the same as one would get directly from the RBN/Skimmers. But it is
+recommended that you SET/DXCQ and UNSET/DXITU and UNSET/DXGRID (unless
+latter in more important to you with, for example, FT4/8 spots).
+
=== 0^SET/WCY^Allow WCY messages to come out on your terminal
=== 0^UNSET/WCY^Stop WCY messages coming out on your terminal
=== 0^SET/WX^Allow WX messages to come out on your terminal
=== 0^UNSET/WX^Stop WX messages coming out on your terminal
+=== 0^SHOW/ANNOUNCE [<n>][<from>-<to>][<call>] ...^Show log of announces
+Show announcements that have come in.
+
=== 1^SHOW/BADDX^Show all the bad dx calls in the system
Display all the bad dx callsigns in the system, see SET/BADDX
for more information.
Display all the bad spotter's callsigns in the system, see SET/BADSPOTTER
for more information.
-=== 1^SHOW/BADWORD^Show all the bad words in the system
+=== 6^SHOW/BADWORD^Show all the bad words in the system
+=== 6^SHOW/BADWORD full^Show all badwords with their Regex
Display all the bad words in the system, see SET/BADWORD
for more information.
+The first form shows all the base words that are stored in a simple list.
+
+The second form show each word with its associated perl regex.
+
+=== 0^SHOW/BANDS [band|region names]^Show the list of bands and regions
+Display the bands and regions (collections of bands) known to
+the system. If you supply band or region names to SHOW/BANDS,
+the command will display just those bands or regions, e.g.:
+
+ sh/band
+ sh/band 2m hf
+
+=== 0^SHOW/BUDDY^Show your list of buddies
+See SET/BUDDY for more information about buddies.
+
=== 0^SHOW/CHAT [<group>] [<lines>]^Show any chat or conferencing
This command allows you to see any chat or conferencing that has
occurred whilst you were away. SHOW/CHAT on its own will show data for
all groups. If you use a group name then it will show only chat for
that group.
+=== 9^SHOW/CMD_CACHE [pattern]^Show the real source path of commands
+It is possible in DXSpider to define local versions of commands.
+Sometimes one forgets that one has these. This command will show you
+the source path where the node is getting each one of its commands.
+
+If you find a local command that you don't want then then simply
+delete it, run LOAD/CMD_CACHE to clear out the command cache and
+try again. You will now be using the standard version.
+
+If you are looking for information on a specific command then
+just add a string, eg:
+
+ sh/cmd dx
+
+might give you:
+
+ Command Path
+ set/dxgrid /spider/cmd/set/dxgrid.pl
+ sh/dx /spider/cmd/show/dx.pl
+
=== 0^SHOW/CONFIGURATION [<node>]^Show all the nodes and users visible
This command allows you to see all the users that can be seen
and the nodes to which they are connected.
This command shows information on all the active connections known to
the node. This command gives slightly more information than WHO.
-=== 0^SHOW/CONTEST <year and month>^Show all the contests for a month
+=== 0^SHOW/CONTEST [<year>] [<month>]^Show all the contests for a month
Show all known contests which are maintained at http://www.sk3bg.se/contest/
for a particular month or year. The format is reasonably flexible.
For example:-
- SH/CONTEST sep2003
- SH/CONTEST 03 march
+ SH/CONTEST
+ SH/CONTEST mar
+ SH/CONTEST mar 13
+ SH/CONTEST 13 march
+
+If there is no month/year then the current month's contests are shown.
+
+Note that it expects ENGLISH (jan/feb/mar/apr/may/jun/jul/aug/sep/oct/nov/dec)
+month names.
=== 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time
This is very nearly the same as SHOW/TIME, the only difference the format
<prefix> - for a spotted callsign beginning with <prefix>
*<suffix> - for a spotted callsign ending in <suffix>
*<string>* - for a spotted callsign containing <string>
+ <call> exact - for a spotted callsign *exactly* as typed.
day <number> - starting <number> days ago
day <from>-<to> - <from> days <to> days ago
by_state <list> - look for spots spotted by people in the US state
specified.
+
+ origin - the node from which this spot originated (must be an
+ exact callsign with SSID e.g. gb7tlh-4)
+
+ ip - the IP address of the spotter (either in IPV4 or IPV6)
+ format. These addresses can be partial.
e.g.
SH/DX by_zone 4,5,6
SH/DX state in,oh
SH/DX by_state in,oh
+ SH/DX hb2008g exact
+ SH/DX origin gb7tlh-4
+ SH/DX ip 82.65.128.4 (or SH/DX ip 2a00:1450:4009:800::200e)
=== 0^SHOW/DXCC <prefix>^Interrogate the spot database by country
This command takes the <prefix> (which can be a full or partial
Show the contents of all the filters that are set. This command displays
all the filters set - for all the various categories.
+=== 0^SHOW/GRAYLINE [ndays] [<prefix>|<callsign>]^Show Civil dawn/dusk times
+This command is very similar to SHOW/SUN except that it shows the
+start and end of "Official" or "Civil" Dawn and Dusk. This is defined
+as when the Sun is 6 degrees below the horizon.
+
+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 civil dawn and dusk times for
+the node that you are connected to.
+
+For example:-
+
+ SH/GRAYLINE
+ SH/GRAYLINE G1TLH W5UN
+
+You can also use this command to see into the past or the future, so
+if you want to see yesterday's times then do:-
+
+ SH/GRAYLINE -1
+
+or in three days time:-
+
+ SH/GRAYLINE +3 W9
+
+Upto 366 days can be checked both in the past and in the future.
+
+Please note that the times are given as the UT times of the requested
+UT day.
+
=== 0^SHOW/HFSTATS [days] [date]^Show the HF DX Statistics
Show the HF DX spots breakdown by band for the last <days> no of days
(default is 31), starting from a <date> (default: today).
This command shows the hop counts set up for a node. You can specify
which category you want to see. If you leave the category out then
all the categories will be listed.
-
+
+=== 0^SHOW/IK3QAR <callsign>^Obtain QSL info from IK3QAR database
+Get QSL information from the online dabase run by IK3QAR.
+
+Your sysop needs to set up this command by obtaining a password from IK3QAR.
+Instructions are available in local/Internet.pm
+
=== 1^SHOW/ISOLATE^Show list of ISOLATED nodes
=== 9^SHOW/LOCKOUT <prefix>|ALL^Show the list of locked out or excluded callsigns
Please note that the rise and set times are given as the UT times of rise and
set on the requested UT day.
+=== 0^SHOW/MOTD^Show your MOTD (the Message of the Day)
+The Message of the Day is normally printed whenever one logs on. However
+many people now login using logging programs or something other than plain
+telnet or ax25 connections. This command allows the user (or the program)
+to see what is in the MOTD.
+
+The actual MOTD that you are shown depends on what carrier you are logged
+on via, whether you are registered and some other factors that your sysop
+may have thrown in.
+
=== 0^SHOW/MUF <prefix> [<hours>][long]^Show the likely propagation to a 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
Doing a SHOW/MYDX will now only, ever, show HF spots. All the other
options on SH/DX can still be used.
-=== 0^SHOW/NEWCONFIGURATION [<node>]^Show all the nodes and users visible
-This command allows you to see all the users that can be seen
-and the nodes to which they are connected.
+=== 0^SHOW/NEWCONFIGURATION [USERS|<node call>]^Show the cluster map
+Show the map of the whole cluster.
-This command produces essentially the same information as
-SHOW/CONFIGURATION except that it shows all the duplication of
-any routes that might be present It also uses a different format
-which may not take up quite as much space if you don't have any
-loops.
+This shows the structure of the cluster that you are connected to. By
+default it will only show the nodes that are known. By adding the keyword
+USER to the command it will show all the users as well.
-BE WARNED: the list that is returned can be VERY long
+As there will be loops, you will see '...', this means that the information
+is as printed earlier and that is a looped connection from here on.
+
+BE WARNED: the list that is returned can be VERY long (particularly
+with the USER keyword)
=== 0^SHOW/NEWCONFIGURATION/NODE^Show all the nodes connected locally
Show all the nodes connected to this node in the new format.
=== 1^SHOW/NODE [<callsign> ...]^Show the type and version number of nodes
+=== 1^SHOW/NODE ALL^Show the type,version number of ALL known nodes
Show the type and version (if connected) of the nodes specified on the
command line. If no callsigns are specified then a sorted list of all
-the non-user callsigns known to the system will be displayed.
+the non-user callsigns connected to node will be displayed.
=== 0^SHOW/PREFIX <callsign>^Interrogate the prefix database
This command takes the <callsign> (which can be a full or partial
sh/route n2tly
+=== 1^SHOW/RBN [<callsign> ...]^Show which connected users want RBN spots
+=== 1^SHOW/RBN ALL^Show ALL users that want RBN spots
+Show a list of the users that want RBN spots of any the callsigns
+specified on the command line. If no callsigns are specified then a
+sorted list of all connected users wanting RBN spots will be displayed
+
+SHOW/RBN ALL
+
+will go through the user file and display ALL users that want RBN spots.
+
+=== 9^SHOW/RCMD [<n>][<from>-<to>][<call>] ...^Show log of rcmds
+Show the rcmds that have come in and their replies.
+
=== 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
Show the tracking data from your location to the satellite of your choice
from now on for the next few hours.
projects / spider.git / blobdiff