=== 8^DISCONNECT <call> [<call> ...]^Disconnect a user or cluster
Disconnect any <call> connected locally
-=== 0^DX <freq> <callsign> <remarks>^Send a DX spot throughout the cluster
-<freq> is compared against the available bands set up in the cluster.
-see show/bands for more information.
+=== 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
+enter the <freq> and the <call> 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 <freq> is compared against the available bands set up in the
+cluster. See SHOW/BANDS for more information.
=== 1^FORWARD/OPERNAME <call>^Send out information on this <call> to all clusters
This command sends out any information held in the user file which can
Reload the /spider/data/prefix_data.pl file if you have changed it manually whilst
the cluster is running.
+=== 5^MERGE <node> [<no spots>/<no wwv>]^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 <cmd> <msgno> [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 <msgno> <call> - change TO callsign to <call>
+ MSG FRom <msgno> <call> - change FROM callsign to <call>
+ MSG PRrivate <msgno> - set private flag
+ MSG NOPRrivate <msgno> - unset private flag
+ MSG RR <msgno> - set RR flag
+ MSG NORR <msgno> - unset RR flag
+ MSG KEep <msgno> - set the keep flag (message won't be deleted ever)
+ MSG NOKEep <msgno> - unset the keep flag
+ MSG SUbject <msgno> <new> - change the subject to <new>
+ MSG WAittime <msgno> - 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 <msgno>
+
+This will display more information on the message than DIR does.
+
=== 8^PC <call> <text>^Send text (eg PC Protocol) to <call>
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
=== 5^KILL^
As a sysop you can kill any message on the system.
-=== 5^MERGE <node> [<no spots>/<no wwv>]^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).
-
=== 8^PC <call> <text>^Send arbitrary text to a connected callsign
Send any text you like to the callsign requested. This is used mainly to send
PC protocol to connected nodes either for testing or to unstick things.
=== 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 <msgno>^Reply to the specified message
-=== 0^REPLY PRIVATE <msgno>^Reply privately to the specified message
+=== 0^REPLY^Reply (privately) to the last message that you have read
+=== 0^REPLY <msgno>^Reply (privately) to the specified message
+=== 0^REPLY B <msgno>^Reply as a Bulletin to the specified message
+=== 0^REPLY NOPrivate <msgno>^Reply as a Bulletin to the specified message
=== 0^REPLY RR <msgno>^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 <call> [<call> ...]^Send a message to one or more callsigns
spaces - but they won't appear in the password). You can see the
result with STAT/USER.
-=== 0^SET/QRA <locator>^Set your QRA locator
=== 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
+=== 0^SET/QRA <locator>^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:-
info <text> - any spots containing <text> in the info or remarks
-spotter <call> - any spots spotted by <call>
+by <call> - any spots spotted by <call> (spotter <call> is the
+ same).
qsl - this automatically looks for any qsl info on the call
- held in the database.
+ held in the spot database.
+
+iota [<iota>] - If the iota island number is missing it will look for
+ the string iota and anything which looks like an iota
+ island number. If you specify then it will look for
+ that island.
+
+qra [<locator>] - this will look for the specific locator if you specify
+ one or else anything that looks like a locator.
e.g.
SH/DX 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 <prefix>^Interrogate the spot database by country
This command takes the <prefix> (which can be a full or partial
See also TYPE - to see the contents of a file.
+=== 0^SHOW/MUF <prefix> [<hours>]^Show the likely propagation to a prefix
+This command allow you to estimate the likelyhood 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 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 <callsign>^Interrogate the prefix database
This command takes the <callsign> (which can be a full or partial
callsign or a prefix), looks up which internal country number
projects / spider.git / blobdiff