X-Git-Url: http://www.dxcluster.org/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=b5c10c19255ce7c6e87176c4072e3c1e194d2472;hb=51fc2b9134d2e3bf91daf970c36bb8a80590e34f;hp=c6cac236d2bcc8dada517ceeeec9e14bd246a2cd;hpb=ed64ea9b9a101013cebeafaf76da0fc1a17722bf;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index c6cac236..b5c10c19 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -378,6 +378,7 @@ in the system. It is also aliased to SHOW/COMMAND. === 9^DBCREATE ^Create a database entry === 9^DBCREATE chain [..]^Create a chained database entry === 9^DBCREATE remote ^Create a remote database entry +=== 9^DBCREATE cmd ^make a local command available as a DB DBCREATE allows you to define a database in the system. It doesn't actually create anything, just defines it. @@ -430,6 +431,16 @@ to allow to work as they may be used to. +You can also make local commands available as 'pseudo' databases. You +can therefore make spider special commands available as a database. I +imagine that this will be primarily useful for remote access from +legacy nodes. For example:- + + DBCREATE dxqsl cmd show/dxqsl + +You also use one of these databases in a chain. This may be useful +locally. + See DBIMPORT for the importing of existing AK1A format data to databases. See DBSHOW for generic database enquiry @@ -1403,6 +1414,28 @@ You can show what levels you are logging with SHOW/DEBUG === 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/DXCQ^Show CQ Zones on the end of DX announcements +=== 0^UNSET/DXCQ^Stop CQ Zones on the end of DX announcements +Display both the Spotter's and the Spotted's CQ Zone on the end +of a DX announcement (there is just enough room). Some user programs +cannot cope with this. The Spotter's CQ is on the RHS of the +time, the Spotted's CQ is on the LHS. + +Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE + +Do a STAT/USER to see which flags you have set if you are confused. + +=== 0^SET/DXITU^Show ITU Zones on the end of DX announcements +=== 0^UNSET/DXITU^Stop ITU Zones on the end of DX announcements +Display both the Spotter's and the Spotted's ITU Zone on the end +of a DX announcement (there is just enough room). Some user programs +cannot cope with this. The Spotter's ITU is on the RHS of the +time, the Spotted's ITU is on the LHS. + +Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE + +Do a STAT/USER to see which flags you have set if you are confused. + === 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 @@ -1411,6 +1444,10 @@ of a DX announcement (there is just enough room). Some user programs cannot cope with this. You can use this command to reset (or set) this feature. +Conflicts with: SET/DXCQ, SET/DXITU + +Do a STAT/USER to see which flags you have set if you are confused. + === 5^SET/DXNET [..]^Make the callsign an DXNet node === 0^SET/ECHO^Make the cluster echo your input @@ -1668,8 +1705,8 @@ overwritten by any weekly updates that affect this callsign see also DELETE/USDB -=== 0^SET/DXSTATE^Allow US State info on the end of DX announcements -=== 0^UNSET/DXSTATE^Stop US State info on the end of DX announcements +=== 0^SET/USSTATE^Allow US State info on the end of DX announcements +=== 0^UNSET/USSTATE^Stop US State info on the end of DX announcements If the spotter's or spotted's US State is known it is output on the end of a DX announcement (there is just enough room). @@ -1681,6 +1718,10 @@ information from SET/DXGRID. Some user programs cannot cope with this. You can use this command to reset (or set) this feature. +Conflicts with: SET/DXCQ, SET/DXITU + +Do a STAT/USER to see which flags you have set if you are confused. + === 0^SET/WCY^Allow WCY messages to come out on your terminal === 0^UNSET/WCY^Stop WCY messages coming out on your terminal @@ -1736,6 +1777,14 @@ Show all the nodes connected to this node. This command shows information on all the active connections known to the node. This command gives slightly more information than WHO. +=== 0^SHOW/CONTEST ^Show all the contests for a month +Show all known contests which are maintained at http://www.sk3bg.se/contest/ +for a particular month or year. The format is reasonably flexible. +For example:- + + SH/CONTEST sep2003 + SH/CONTEST 03 march + === 0^SHOW/DATE [|]^Show the local time This is very nearly the same as SHOW/TIME, the only difference the format of the date string if no arguments are given. @@ -2065,6 +2114,25 @@ is provided for users of this software by http://www.qrz.com See also SHOW/WM7D for an alternative. +=== 0^SHOW/DXQSL ^Show any QSL info gathered from spots +The node collects information from the comment fields in spots (things +like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database. + +This command allows you to interrogate that database and if the callsign +is found will display the manager(s) that people have spotted. This +information is NOT reliable, but it is normally reasonably accurate if +it is spotted enough times. + +For example:- + + sh/dxqsl 4k9w + +You can check the raw input spots yourself with:- + + sh/dx 4k9w qsl + +This gives you more background information. + === 9^SHOW/REGISTERED []^Show the registered users === 0^SHOW/ROUTE ...^Show the route to the callsign