some examples:-
- acc/spot 1 freq hf/cw
- acc/spot 2 freq vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
You can use the tag 'all' to accept everything, eg:
- ann/spot 3 all
+ acc/spot 3 all
but this probably for advanced users...
If you have a filter:-
- acc/spot 1 freq hf/cw
- acc/spot 2 freq vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+ acc/spot 1 on hf/cw
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
and you say:-
you will be left with:-
- acc/spot 2 freq vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+ acc/spot 2 on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
If you do:
it BUT if you specify an 'accept' filter then any spots that don't
match are dumped. For example if I have a one line accept filter:-
- accept/spots freq vhf and (by_zone 14,15,16 or call_zone 14,15,16)
+ accept/spots on vhf and (by_zone 14,15,16 or call_zone 14,15,16)
then automatically you will ONLY get VHF spots from or to CQ zones 14
15 and 16. If you set a reject filter like:
- reject/spots freq hf/cw
+ reject/spots on hf/cw
Then you will get everything EXCEPT HF CW spots, If you am interested in IOTA
and will work it even on CW then you could say:-
- reject/spots freq hf/cw and not info iota
+ reject/spots on hf/cw and not info iota
But in that case you might only be interested in iota and say:-
- accept/spots not freq hf/cw or info iota
+ accept/spots not on hf/cw or info iota
which is exactly the same. You should choose one or the other until
you are confortable with the way it works. Yes, you can mix them
You can arrange your filter lines into logical units, either for your
own understanding or simply convenience. I have one set frequently:-
- reject/spots 1 freq/cw
- reject/spots 2 freq 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
+ reject/spots 1 on hf/cw
+ reject/spots 2 on 50000/1400000 not (by_zone 14,15,16 or call_zone 14,15,16)
What this does is to ignore all HF CW spots (being a class B I can't
read any CW and couldn't possibly be interested in HF :-) and also
that you will NEED brackets in a situation like line 2 because,
without it, will assume:-
- (freq 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
+ (on 50000/1400000 and by_zone 14,15,16) or call_zone 14,15,16
annoying, but that is the way it is. If you use OR - use
brackets. Whilst we are here CASE is not important. 'And BY_Zone' is
If you want to alter your filter you can just redefine one or more
lines of it or clear out one line. For example:-
- reject/spots 1 freq/ssb
+ reject/spots 1 on hf/ssb
or
my example that filters hf/cw spots and accepts vhf/uhf spots from EU
can be written with a mixed filter, eg:
- rej/spot freq hf/cw
- acc/spot freq 0/30000
- acc/spot 2 freq 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+ rej/spot on hf/cw
+ acc/spot on 0/30000
+ acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
each filter slot actually has a 'reject' slot and an 'accept'
slot. The reject slot is executed BEFORE the accept slot.
The next filter line lets through just VHF/UHF spots from EU.
+=== 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
+This command sends all the latitude and longitude information that your
+cluster is holding against callsigns. One advantage of recieving this
+information is that more locator information is held by you. This
+means that more locators are given on the DX line assuming you have
+SET/DXGRID enabled. This could be a LOT of information though, so
+it is not recommended on slow links.
+
=== 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
This command sends out any information held in the user file which can
be broadcast in PC41 protocol packets. This information is Name, QTH, Location
or
pc G1TLH Try doing that properly!!!
-=== 1^PING <node>^Send a ping command to another cluster
-This command is used to estimate the quality of the link to another cluster.
-The time returned is the length of time taken for a PC51 to go to another
-cluster and be returned.
-
=== 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
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.
You can also use in the same way as a talk command to a connected user but
without any processing, added of "from <blah> to <blah" or whatever.
-=== 1^PING <node call>^Find out the delays an a circuit to another node
-This command will enable sysops to determine the speed of an inter-cluster
-node.
-
+=== 1^PING <node call>^Check the link quality between nodes
+This command allows you to send a frame to another cluster node on
+the network and get a return frame. The time it takes to do this
+is a good indication of the quality of the link. The actual time
+it takes is output to the console in seconds.
Any visible cluster node can be PINGed.
=== 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
=== 5^READ-^
As a sysop you may read any message on the system
-=== 0^REJECT/ANNOUNCE [0-9] <pattern>^Set an 'reject' filter line for announce
+=== 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
Create an 'reject this announce' line for a filter.
-An reject filter line means that if the announce matches this filter it is
+A 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.
reject/ann input node_default by G,M,2
reject/ann user_default by G,M,2
-=== 0^REJECT/SPOTS [0-9] <pattern>^Set an 'reject' filter line for spots
-Create an 'reject this spot' line for a filter.
+=== 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
+Create a 'reject this spot' line for a filter.
-An reject filter line means that if the spot matches this filter it is
+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.
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
+this is more efficient than saying simply: on HF (but don't get
too hung up about that)
some examples:-
- rej/spot 1 freq hf
- rej/spot 2 freq vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
+ rej/spot 1 on hf
+ rej/spot 2 on vhf and not (by_zone 14,15,16 or call_zone 14,15,16)
You can use the tag 'all' to reject everything eg:
reject/spot user_default by G,M,2
-=== 0^REJECT/WCY [0-9] <pattern>^set an 'reject' WCY filter
+=== 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
reject/wcy gb7djk all
-=== 0^REJECT/WWV [0-9] <pattern>^set an 'reject' WWV filter
+=== 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
and returns any information available for that callsign. This service
is provided for users of this software by http://www.qrz.com
+=== 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
+This command allows you to see to which node the callsigns specified are
+connected. It is a sort of inverse sh/config.
+
+sh/route n2tly
+
=== 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.