X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=sgml%2Fusermanual.sgml;h=1282f2e452f56f0f9e1b272ddeab9e2c80d204f6;hb=2538c30a81811749c0cdaf55b8c9f65ee7c5167d;hp=1d45a933513dce5b1c740c2b8947e929ba047cb9;hpb=e674587476599456cce169e02b0e441d985f9dd8;p=spider.git diff --git a/sgml/usermanual.sgml b/sgml/usermanual.sgml index 1d45a933..1282f2e4 100644 --- a/sgml/usermanual.sgml +++ b/sgml/usermanual.sgml @@ -4,9 +4,10 @@ -
-Because DXSpider runs under the Linux operating system, it is possible to
-make a direct telnet connection into the cluster. With telnet
-connections, the source callsign is not seen by DXSpider, so you will be
-asked to login with your callsign.
+With telnet connections, the source callsign is not seen by DXSpider, so
+you will be asked to login with your callsign.
To telnet to DXSpider, you would connect to a specific port. There is no
standard at the moment for a cluster telnet port but ask the sysop if
you are unsure.
@@ -143,11 +142,11 @@ You could also send a disconnect if you are using AX25, or a
To delete a message, you use the delete command.
You can only delete messages sent to or received by yourself.
Bulletins are dealt with automatically or by the sysop.
@@ -958,6 +962,13 @@ In the example what happens is that the reject is executed first, any non
hf/cw spot is passed to the accept line, which lets through everything
else on HF. The next filter line lets through just VHF/UHF spots from EU.
+
+There is now an excellent primer/tutorial on filtering written by Jim
+Samuels, W3BG with an introduction by Dave Hawes N3RD that I strongly
+suggest you read. You can read it here
+
-Below is a complete list of commands available from the cluster prompt.
-These are listed below in alphabetical order.
-
-
-
-
-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:-
-
-
-
-
-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:-
-
-
-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:-
-
-
-
-
-It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-
-
-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.
-
-
-
-
-It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-
-
-
-
-Send an announcement to LOCAL users only, where <text> is the text
-of the announcement you wish to broadcast
-
-
-
-
-This command will send your announcement across the whole cluster
-network.
-
-
-
-
-Search the help database for <string> (it isn't case sensitive),
-and print the names of all the commands that may be relevant.
-
-
-
-
-This will disconnect you from the cluster
-
-
-
-
-This command allows you to clear (remove) a line in a spot filter or to
-remove the whole filter.
-
-If you have a filter:-
-
-
-
-
-The title says it all really, this command lists all the databases defined
-in the system. It is also aliased to SHOW/COMMAND.
-
-
-
-
-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:
-
-
-
-
-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:-
-
-
-
-
-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.
-
-
-
-
-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.
-
-
-
-
-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).
-
-
-
-
-This is a quick listing that shows which links are connected and
-some information about them. See WHO for a list of all connections.
-
-
-
-
-You can read any messages that are sent as 'non-personal' and also any
-message either sent by or sent to your callsign.
-
-
-
-
-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:-
-
-
-
-
-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:-
-
-
-
-
-It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-
-
-
-
-It is unlikely that you will want to do this, but if you do then you can
-filter on the following fields:-
-
-
-
-
-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)
-
-
-
-
-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:-
-
-
-
-
-Literally, record your address details on the cluster.
-
-
-
-
-Allow announce messages to arrive at your terminal.
-
-
-
-
-Add a beep to DX and other terminal messages.
-
-
-
-
-You can stop DX messages with the unset/dx command
-
-
-
-
-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.
-
-
-
-
-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.
-
-
-
-
-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.
-
-
-
-
-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:-
-
-
-
-
-You can select the language that you want the cluster to use. Currently
-the languages available are en (English) sp (Spanish)
-and nl (Dutch).
-
-
-
-
-You can set your latitude and longitude manually or alternatively use the
-set/qra command which will do the conversion for you.
-
-
-
-
-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.
-
-
-
-
-Tell the cluster what your name is, eg:-
-
-
-
-
-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.
-
-
-
-
-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:-
-
-
-
-
-Tell the system where your are. For example:-
-
-
-
-
-Allow talk messages to arrive at your console. You can switch off
-talks with the unset/talk command.
-
-
-
-
-Allow WCY information to be seen at your console. You can switch off
-WCY messages with the unset/wcy command.
-
-
-
-
-Allow WWV information to be seen at your console. You can switch off
-WWV messages with the unset/wwv command.
-
-
-
-
-Allow WX information to be seen at your console. You can switch off
-WX messages with the unset/wx command.
-
-
-
-
-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.
-
-
-
-
-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:-
-
-
-
-
-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.
-
-
-
-
-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:-
-
-
-
-
-Show the contents of all the filters that are set by you. This command
-displays all the filters set - for all the various categories.
-
-
-
-
-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:-
-
-
-
-
-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:-
-
-
-
-
-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
-
-
-
-
-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:-
-
-
-
-
-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
-
-
-
-
-This command allows you to see to which node the callsigns specified are
-connected. It is a sort of inverse sh/config.
-
-
-
-
-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:-
-
-
-
-
-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:-
-
-
-
-
-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.
-
-
-
-
-Display the most recent WCY information that has been received by the system
-
-
-
-
-Display the most recent WWV information that has been received by the system
-
-
-
-
-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 :-):
-
-
-
-
-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:-
-
-
-
-
-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:-
-
-
-
-
-This is a quick listing that shows which callsigns are connected and
-what sort of connection they have
-
-
-
-
-Weather messages can sometimes be useful if you are experiencing an extreme
-that may indicate enhanced conditions
+