Reload the /spider/msg/forward.pl file if you have changed it
manually whilst the cluster is running.
+=== 5^LOAD/KEPS^Load new keps data
+=== 5^LOAD/KEPS [nn]^Load new keps data from message
+If there is no message number then reload the current Keps data from
+the Keps.pm data file. You create this file by running
+
+ /spider/perl/convkeps.pl <filename>
+
+on a file containing NASA 2 line keps as a message issued by AMSAT.
+
+If there is a message number, then it will take the message, run
+convkeps.pl on it and then load the data, all in one step.
+
+These messages are sent to ALL by GB7DJK (and others) from time to time.
+
=== 9^LOAD/MESSAGES^Reload the system messages file
If you change the /spider/perl/Messages file (usually whilst
fiddling/writing new commands) you can have them take effect during a
=== 0^SET/DX^Allow DX messages to come out on your terminal
=== 0^UNSET/DX^Stop DX messages coming out on your terminal
-=== 0^SET/DXGRID^Allow Grid Squares on the end of DX announcements
-=== 0^UNSET/DXGRID^Stop Grid Squares on the end of DX announcements
+=== 0^SET/DXGRID^Allow QRA Grid Squares on the end of DX announcements
+=== 0^UNSET/DXGRID^Stop QRA Grid Squares on the end of DX announcements
A standard feature which is enabled in version 1.43 and above is
that if the spotter's grid square is known it is output on the end
of a DX announcement (there is just enough room). Some user programs
SET/HOMENODE gb7djk
=== 8^SET/HOPS <call> ann|spots|route|wwv|wcy <n>^Set hop count
+=== 8^UNSET/HOPS <call> ann|spots|route|wwv|wcy^Unset hop count
Set the hop count for a particular type of broadcast for a node.
This command allows you to set up special hop counts for a node
Set SHOW/HOPS for information on what is already set. This command
creates a filter and works in conjunction with the filter system.
+You can unset the hops with command UNSET/HOPS. For example:-
+
+ unset/hops gb7djk ann
+ unset/hops gb7mbc spots
+
+
=== 9^SET/ISOLATE^Isolate a node from the rest of the network
Connect a node to your system in such a way that you are a full protocol
member of its network and can see all spots on it, but nothing either leaks
=== 0^SET/LANGUAGE <lang>^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).
+the languages available are en (English), de (German), es (Spanish)
+and nl (Dutch).
=== 0^SET/LOCATION <lat & long>^Set your latitude and longitude
=== 9^SET/SYS_LOCATION <lat & long>^Set your cluster latitude and longitude
Tell the system that the call(s) are to be treated as DXSpider node and
fed new style DX Protocol rather normal user commands.
-=== 9^SET/SYS_QRA <locator>^Set your cluster QRA locator
-=== 0^SET/QRA <locator>^Set your QRA locator
+=== 9^SET/SYS_QRA <locator>^Set your cluster QRA Grid locator
+=== 0^SET/QRA <locator>^Set your QRA Grid 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:-
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/QRA <locator> [<locator>]^Show distance between locators
-=== 0^SHOW/QRA <lat> <long>^Convert latitude and longitude to a locator
+=== 0^SHOW/QRA <locator> [<locator>]^Show distance between QRA Grid locators
+=== 0^SHOW/QRA <lat> <long>^Convert lat/long to a QRA Grid locator
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
projects / spider.git / blobdiff