X-Git-Url: http://dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=015bc790118bb77f0342c10dee9fcd055949b62d;hb=bd14b9e29dbd64a441cc7b65f6b6b92717f8a01b;hp=b78e29db376dd5f651a12395e90b08dc30e0505f;hpb=324bd80ed4aef7e2636f5a03288788ce11ab2663;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index b78e29db..015bc790 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -34,6 +34,25 @@ DX cluster . This process creates a new 'client' process which will use the script in /spider/connect/ to effect the 'chat' exchange necessary to traverse the network(s) to logon to the cluster . +=== 9^CATCH All|[ ...]^Mark a message as sent +=== 9^UNCATCH All|[msgno> ...]^Unmark a message as sent +When you send messages the fact that you have forwarded it to another node +is remembered so that it isn't sent again. When you have a new partner +node and you add their callsign to your /spider/msg/forward.pl file, all +outstanding non-private messages will be forwarded to them. This may well +be ALL the non-private messages. You can prevent this by using these +commmands:- + + catch GB7DJK all + catch GB7DJK 300 301 302 303 + +and to undo what you have just done:- + + uncatch GB7DJK all + uncatch GB7DJK 300 301 302 303 + +which will arrange for them to be forward candidates again. + === 9^DEBUG^Set the cluster program into debug mode Executing this command will only have an effect if you are running the cluster in debug mode i.e. @@ -44,14 +63,31 @@ It will interrupt the cluster just after the debug command has finished. === 0^DIRECTORY^List messages === 0^DIRECTORY ALL^List all messages === 0^DIRECTORY OWN^List your own messages -=== 0^DIRECTORY NEW^List your own new messages -List the messages in the messages directory. +=== 0^DIRECTORY NEW^List all new messages +=== 0^DIRECTORY TO ^List all messages to +=== 0^DIRECTORY FROM ^List all messages from +=== 0^DIRECTORY SUBJECT ^List all messages with in subject +=== 0^DIRECTORY ^List last messages +=== 0^DIRECTORY -^List messages message 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. +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 +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:- -If there is a - after the message number then this indicates that the -message has been read. + DIR/T G1* 10 + DIR/S QSL 10-100 5 === 5^DIRECTORY-^ Sysops can see all users' messages. @@ -59,9 +95,25 @@ Sysops can see all users' messages. === 8^DISCONNECT [ ...]^Disconnect a user or cluster Disconnect any connected locally -=== 0^DX ^Send a DX spot throughout the cluster - is compared against the available bands set up in the cluster. -see show/bands for more information. +=== 0^DX [BY ] ^Send a DX spot +This is how you send a DX Spot to other users. You can, in fact, now +enter the and the either way round. + + DX FR0G 144.600 + DX 144.600 FR0G + DX 144600 FR0G + +will all give the same result. You can add some remarks to the end +of the command and they will be added to the spot. + + DX FR0G 144600 this is a test + +You can credit someone else by saying:- + + DX by G1TLH FR0G 144.600 he isn't on the cluster + +The is compared against the available bands set up in the +cluster. See SHOW/BANDS for more information. === 1^FORWARD/OPERNAME ^Send out information on this to all clusters This command sends out any information held in the user file which can @@ -119,6 +171,39 @@ unknown message 'xxxx' in lang 'en' Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst the cluster is running. +=== 5^MERGE [/]^Ask for the latest spots and WWV +MERGE allows you to bring your spot and wwv database up to date. By default +it will request the last 10 spots and 5 WWVs from the node you select. The +node must be connected locally. + +You can request any number of spots or wwv and although they will be appended +to your databases they will not duplicate any that have recently been added +(the last 2 days for spots and last month for WWV data). + +=== 9^MSG [data ... ]^Alter various message parameters +Alter message parameters like To, From, Subject, whether private or bulletin +or return receipt (RR) is required or whether to keep this message from timing +out. + + MSG TO - change TO callsign to + MSG FRom - change FROM callsign to + MSG PRrivate - set private flag + MSG NOPRrivate - unset private flag + MSG RR - set RR flag + MSG NORR - unset RR flag + MSG KEep - set the keep flag (message won't be deleted ever) + MSG NOKEep - unset the keep flag + MSG SUbject - change the subject to + MSG WAittime - remove any waitting time for this message + MSG QUeue - queue any outstanding bulletins + MSG QUeue 1 - queue any outstanding private messages + +You can look at the status of a message by using:- + + STAT/MSG + +This will display more information on the message than DIR does. + === 8^PC ^Send text (eg PC Protocol) to Send some arbitrary text to a locally connected callsign. No processing is done on the text. This command allows you to send PC Protocol to unstick things if problems @@ -136,17 +221,14 @@ cluster and be returned. You can get rid of any message to or originating from your callsign using this command. You can remove more than one message at a time. -=== 5^KILL-^ -As a sysop you can kill any message on the system. +=== 5^KILL -^Remove a range of messages from the system +=== 5^KILL FROM ^Remove all messages from a callsign +=== 5^KILL TO ^Remove all messages to a callsign +=== 5^KILL FULL [ [/]^Ask for the latest spots and WWV -MERGE allows you to bring your spot and wwv database up to date. By default -it will request the last 10 spots and 5 WWVs from the node you select. The -node must be connected locally. - -You can request any number of spots or wwv and although they will be appended -to your databases they will not duplicate any that have recently been added -(the last 2 days for spots and last month for WWV data). +=== 5^KILL^ +As a sysop you can kill any message on the system. === 8^PC ^Send arbitrary text to a connected callsign Send any text you like to the callsign requested. This is used mainly to send @@ -178,15 +260,16 @@ message either sent by or sent to your callsign. === 5^READ-^ As a sysop you may read any message on the system -=== 0^REPLY^Reply to the last message that you have read -=== 0^REPLY ^Reply to the specified message -=== 0^REPLY PRIVATE ^Reply privately to the specified message +=== 0^REPLY^Reply (privately) to the last message that you have read +=== 0^REPLY ^Reply (privately) to the specified message +=== 0^REPLY B ^Reply as a Bulletin to the specified message +=== 0^REPLY NOPrivate ^Reply as a Bulletin to the specified message === 0^REPLY RR ^Reply to the specified message with read receipt You can reply to a message and the subject will automatically have "Re:" inserted in front of it, if it isn't already present. You can also use all the extra qualifiers such as RR, PRIVATE, -NOPRIVATE that you can use with the SEND command (see SEND +NOPRIVATE, B that you can use with the SEND command (see SEND for further details) === 0^SEND [ ...]^Send a message to one or more callsigns @@ -246,6 +329,10 @@ You can potentially connect several nodes in this way. === 9^UNSET/ISOLATE^Stop Isolation of a node from the rest of the network Remove isolation from a node - SET/ISOLATE +=== 0^SET/LANGUAGE ^Set the language you want to use +You can select the language that you want the cluster to use. Currently +the languages available are en (english) and nl (dutch). + === 0^SET/LOCATION ^Set your latitude and longitude === 9^SET/SYS_LOCATION ^Set your cluster latitude and longitude In order to get accurate headings and such like you must tell the system @@ -270,10 +357,6 @@ of output from a command is more than this. The default is 20. Setting it explicitly to 0 will disable paging. SET/PAGE 30 SET/PAGE 0 - -=== 0^SHOW/PROGRAM^Show the locations of all the included program modules -Show the name and location where every program module was load from. This -is useful for checking where you think you have loaded a .pm file from. === 9^SET/PRIVILEGE [^Set your QRA locator +=== 9^SET/PASSWORD ^Set a users password +The password for a user can only be set by a full sysop. The string +can contain any characters but any spaces are removed (you can type in +spaces - but they won't appear in the password). You can see the +result with STAT/USER. + === 9^SET/SYS_QRA ^Set your cluster QRA locator +=== 0^SET/QRA ^Set your QRA locator Tell the system what your QRA (or Maidenhead) locator is. If you have not done a SET/LOCATION then your latitude and longitude will be set roughly correctly (assuming your locator is correct ;-). For example:- @@ -330,13 +419,29 @@ day - - days days ago info - any spots containing in the info or remarks -spotter - any spots spotted by +by - any spots spotted by (spotter is the + same). + +qsl - this automatically looks for any qsl info on the call + held in the spot database. + +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 [] - 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 === 0^SHOW/DXCC ^Interrogate the spot database by country This command takes the (which can be a full or partial @@ -349,6 +454,79 @@ e.g. SH/DXCC G SH/DXCC W on 20m info iota +=== 0^SHOW/FILES [ []]^List the contents of a filearea +SHOW/FILES on its own will show you a list of the various fileareas +available on the system. To see the contents of a particular file +area type:- + SH/FILES +where 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. + +=== 0^SHOW/MUF []^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 +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. + === 0^SHOW/PREFIX ^Interrogate the prefix database This command takes the (which can be a full or partial callsign or a prefix), looks up which internal country number @@ -357,6 +535,10 @@ together with the internal country no, the CQ and ITU regions. See also SHOW/DXCC +=== 0^SHOW/PROGRAM^Show the locations of all the included program modules +Show the name and location where every program module was load from. This +is useful for checking where you think you have loaded a .pm file from. + === 0^SHOW/WWV^Show last 10 WWV broadcasts === 0^SHOW/WWV ^Show last WWV broadcasts Display the most recent WWV information that has been received by the system @@ -376,6 +558,31 @@ and stuff. Only the fields that are defined (in perl term) will be displayed. +=== 0^SYSOP^Regain your privileges if you login remotely +The system automatically reduces your privilege level to that of a +normal user if you login in remotely. This command allows you to +regain your normal privilege level. It uses the normal system: five +numbers are returned that are indexes into the character array that is +your assigned password (see SET/PASSWORD). The indexes start from +zero. + +You are expected to return a string which contains the characters +required in the correct order. You may intersperse those characters +with others to obscure your reply for any watchers. For example (and +these values are for explanation :-): + +password = 012345678901234567890123456789 + > sysop +22 10 15 17 3 +you type:- +aa2bbbb0ccc5ddd7xxx3n +or 2 0 5 7 3 +or 20573 + +They will all match. If there is no password you will still be offered +numbers but nothing will happen when you input a string. Any match is +case sensitive. + === 0^TALK ^Send a text message to another station === 0^TALK > ^Send a text message to another station via a node Send a short message to any other station that is visible on the cluster @@ -390,6 +597,19 @@ 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. +=== 0^TYPE /^Look at the contents of a file in one of the fileareas +Type out the contents of a file in a filearea. So, for example, in +filearea 'bulletins' you want to look at file 'arld051' you would +enter:- + TYPE bulletins/arld051 + +See also SHOW/FILES to see what fileareas are available and a +list of content. + +=== 0^WHO^Show who is physically connected +This is a quick listing that shows which callsigns are connected and +what sort of connection they have + === 0^WX ^Send a weather message to local users === 0^WX FULL ^Send a weather message to all cluster users === 5^WX SYSOP ^Send a weather message to other clusters only