<html><body>
<DIV>Thanks for all the info Larry and I will try your method. I've only always used telnet and did not notice a way to filter incoming spots from the host side. I thought it was only done through the user side. Another example is the "Bandmaster" I think it's called that you can get with DX-Atlas. It's also a stand-alone system that can be OLE'd into other programs. Has some filtering options. Problem with that is it seems like it ONLY uses DX-Summit and there's no way to choose a local DX Telnet cluster.</DIV>
<DIV> </DIV>
<DIV>Thanks again.....just another reason to use WT...the support given to individual requests is great.....even if they're not used...hihi. :)</DIV>
<DIV> </DIV>
<DIV>73</DIV>
<DIV>Greg - AB7R</DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">-------------- Original message -------------- <BR><BR>> Hi All <BR>> <BR>> We've been recently asked by Greg AB7R for a spots filtering capability <BR>> in Win-Test. <BR>> <BR>> Such an embedded filtering has advantages and drawbacks : The main <BR>> advantage (the only one ?) is that you don't need extra software to <BR>> achieve it, and you don't need to know cryptic commands to be sent to <BR>> your favorite DX cluster. But the main drawbacks are that kind of <BR>> filtering, on client side (= WT side), wastes much not-needed Internet <BR>> (or radio) bandwidth (which is not very friendly for the rest of us), <BR>> and, as the DX clusters designers never standardized the evolution of <BR>> the sent data format, it's likely impossible to achieve the same <BR>> capabilities among every DX Cluster system (DXNet, Pavillion, AR, DX <BR>> Spider,
etc...). <BR>> <BR>> To make it short, even if we're considering a filtering feature in <BR>> Win-Test, the easiest way to do it now is to use the one included in the <BR>> DX Cluster you're connected to. <BR>> <BR>> FYI, I just downloaded and tried the VE7CC AR Cluster/Dx Spider User <BR>> Program (http://www.ve7cc.net/). If offers many filtering options (even <BR>> US State or VE province spotter originating - Greg are you listening ? <BR>> ;-) ) and works flawlessly with Win-Test. Note that it only works for AR <BR>> and DX Spider clusters. Here's a short description of my setup : <BR>> <BR>> - Once installed, in configuration / Port - logging program, check the <BR>> Telnet logging program connection and, in the Data Sent to Logging <BR>> Program frame, check (at least) the "DX Spots" box. <BR>> <BR>> - I personnaly used the Telnet node connection, but you can also use a <BR>> TNC if you're connecting to an AR or DX Spid
er local DX Cluster. <BR>> <BR>> - Check if your connection is OK with the Cluster (top of the main <BR>> window). You can send usual command with the lower edit field to insure <BR>> you're connected. <BR>> <BR>> - Once everything is OK, you can play with all filterning features : Use <BR>> the Country and State tabs to adjust your filter (on spotter country, DX <BR>> country, etc...). Once set, send it to the cluster : VE7CC software will <BR>> automagically translate your clicks in a filter command and send it to <BR>> the DX Cluster. The filtering possibilities are countless... (also by <BR>> band, mode etc...) <BR>> <BR>> - Now, the interesting part : WT interfacing : [I assume AR User and <BR>> WtDxCluster to be on the same computer]. Open WtDxCluster (now packaged <BR>> with every version of WT), and configure the DXCluster properties to : <BR>> Host = 127.0.0.1 and Port = 7300. You can leave the user and password <BR>&g
t; fields blank. Then, use the DXCluster / Connect menu. You will be <BR>> connected to the DX Cluster THRU AR-User. Thus, in WtDxCluster you will <BR>> only get informations you asked for... Afterwards, you can use Win-Test <BR>> the usual way : Spots will be displayed in bandmaps and Spots window. <BR>> <BR>> 73 <BR>> <BR>> Larry - F6FVY <BR>> <BR>> <BR>> <BR>> _______________________________________________ <BR>> Support mailing list <BR>> Support@win-test.com <BR>> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support </BLOCKQUOTE></body></html>