[WT-support] DX Spots filtering

[ab7r at comcast.net]

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.

Thanks again.....just another reason to use WT...the support given to individual requests is great.....even if they're not used...hihi. :)

73
Greg - AB7R


-------------- Original message -------------- 

> Hi All 
> 
> We've been recently asked by Greg AB7R for a spots filtering capability 
> in Win-Test. 
> 
> Such an embedded filtering has advantages and drawbacks : The main 
> advantage (the only one ?) is that you don't need extra software to 
> achieve it, and you don't need to know cryptic commands to be sent to 
> your favorite DX cluster. But the main drawbacks are that kind of 
> filtering, on client side (= WT side), wastes much not-needed Internet 
> (or radio) bandwidth (which is not very friendly for the rest of us), 
> and, as the DX clusters designers never standardized the evolution of 
> the sent data format, it's likely impossible to achieve the same 
> capabilities among every DX Cluster system (DXNet, Pavillion, AR, DX 
> Spider, etc...). 
> 
> To make it short, even if we're considering a filtering feature in 
> Win-Test, the easiest way to do it now is to use the one included in the 
> DX Cluster you're connected to. 
> 
> FYI, I just downloaded and tried the VE7CC AR Cluster/Dx Spider User 
> Program (http://www.ve7cc.net/). If offers many filtering options (even 
> US State or VE province spotter originating - Greg are you listening ? 
> ;-) ) and works flawlessly with Win-Test. Note that it only works for AR 
> and DX Spider clusters. Here's a short description of my setup : 
> 
> - Once installed, in configuration / Port - logging program, check the 
> Telnet logging program connection and, in the Data Sent to Logging 
> Program frame, check (at least) the "DX Spots" box. 
> 
> - I personnaly used the Telnet node connection, but you can also use a 
> TNC if you're connecting to an AR or DX Spider local DX Cluster. 
> 
> - Check if your connection is OK with the Cluster (top of the main 
> window). You can send usual command with the lower edit field to insure 
> you're connected. 
> 
> - Once everything is OK, you can play with all filterning features : Use 
> the Country and State tabs to adjust your filter (on spotter country, DX 
> country, etc...). Once set, send it to the cluster : VE7CC software will 
> automagically translate your clicks in a filter command and send it to 
> the DX Cluster. The filtering possibilities are countless... (also by 
> band, mode etc...) 
> 
> - Now, the interesting part : WT interfacing : [I assume AR User and 
> WtDxCluster to be on the same computer]. Open WtDxCluster (now packaged 
> with every version of WT), and configure the DXCluster properties to : 
> Host = 127.0.0.1 and Port = 7300. You can leave the user and password 
> fields blank. Then, use the DXCluster / Connect menu. You will be 
> connected to the DX Cluster THRU AR-User. Thus, in WtDxCluster you will 
> only get informations you asked for... Afterwards, you can use Win-Test 
> the usual way : Spots will be displayed in bandmaps and Spots window. 
> 
> 73 
> 
> Larry - F6FVY 
> 
> 
> 
> _______________________________________________ 
> Support mailing list 
> Support at win-test.com 
> http://www.f5mzn.org/cgi-bin/mailman/listinfo/support 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://numerobis.f5mzn.org/pipermail/support/attachments/20041217/2a8e7a97/attachment-0070.htm