[Great-River-DX] packet and DX Cluster info

[Danny Pease]

I was on W9ZRX earlier today. I did see K4VX on it eqrlier this week, 
can't remember which day. I have seen K0CA logged onto W9ZRX in the past 
as well. I did not see NA9Q logged onto W9ZRX this week though, which 
makes me wonder if the W9AWE node is getting feeds form W9ZRX or not 
right now.

Danny


Jay Hainline wrote:
> To change your mail delivery options or to unsubscribe from this list go to:
>  http://mailman.qth.net/mailman/listinfo/great-river-dx
> ________________________________________________________
> 
> Just connected to W9ZRX cluster. I use VE7CC software which is very good at
> filtering. I cannot see Mike's cluster over 2 meters from this QTH. I don't
> see any familiar calls on ZRX right now... 
> 
> 
> Jay Hainline  KA9CFD  EN40om
> Colchester, IL
> 
> -----Original Message-----
> From: great-river-dx-bounces at mailman.qth.net
> [mailto:great-river-dx-bounces at mailman.qth.net] On Behalf Of BenEm
> Sent: Friday, May 02, 2008 00:46
> To: Great-River-DX at mailman.qth.net
> Subject: RE: [Great-River-DX] packet and DX Cluster info
> 
> To change your mail delivery options or to unsubscribe from this list go to:
>  http://mailman.qth.net/mailman/listinfo/great-river-dx
> ________________________________________________________
> 
> Danny,
> 
> Thanks for the good info....
> I have updated my VE7CC Node to W9ZRX and will monitor other local stations
> when I am connected.  Form my home station, I am unable to hear the packet
> W9AWE from NA9Q's QTH so will need to connect thru the ILQDX digipeater.
> Ben WM9DX
> 
> -----Original Message-----
> From: great-river-dx-bounces at mailman.qth.net
> [mailto:great-river-dx-bounces at mailman.qth.net] On Behalf Of Danny Pease
> Sent: Thursday, May 01, 2008 3:48 PM
> To: Great-River-DX at mailman.qth.net
> Subject: [Great-River-DX] packet and DX Cluster info
> 
> To change your mail delivery options or to unsubscribe from this list go to:
>  http://mailman.qth.net/mailman/listinfo/great-river-dx
> ________________________________________________________
> 
> At out meeting last Sunday, K0CA asked about connecting to the local DX
> node, W9AWE via packet and also discussed telnet connections. There are a
> multitude of programs that allow both but it appears we are all not using
> the same node on telnet. Also, most of the logging software that supports
> telnet connections will also allow you to set your own filters for only what
> you are looking for and not have to sort through hundreds of un-needed
> spots. If you want to use a standalone program for either packet or telnet,
> I highly recommend the free package by VE7CC, AR-User.
> 
> It was suggested all those that use telnet via internet to use W9ZRX, if for
> no other reason than we can all "see" each other on the node when we are
> logged on. That makes it easy for us to pass messages to each other.
> 
> Cliff also suggested that I post how to connect to the local DX node via
> packet. The local node, W9AWE, is located the QTH of NA9Q and operates on
> 144.910. Since Mike's antenna system is capable of hearing everyone in the
> area that might want to log in, it is best to use the ILQDX digipeater. To
> connect via packet, simply connect to ILQDX first and after you get a
> response back that you are connected to ILQDX, connect to W9AWE. The
> commands are simply, c ILQDX (wait for response) and the c W9AWE. You will
> shortly get the welcome message from the packet cluster node and are ready
> to watch for DX spots.
> 
> Those that connect via packet can only "see" other stations connected to
> W9AWE at that time, they will not be able to see those connected to W9ZRX
> via telnet. The same goes the other way, those connected to W9ZRX can see
> each other but they cannot see who is connected to W9AWE. IF you are
> connected to W9AWE and you send a spot, it will be sent to all those
> connected to W9AWE but that is all. If you are connected to W9ZRX and spot a
> DX station, it will be seen by those connected to W9AWE. Also, any messages
> sent to all on W9ZRX will be seen by those connected to W9AWE, but the
> reverse is not true. The connection form W9ZRX to W9AWE is one way, W9AWE
> receives spots form W9ZRX but cannot send any spots back to W9ZRX.
> 
> Eventually we hope to replace the current cluster software at W9AWE with
> software that will let us telnet into W9AWE as well as connect via packet,
> but it will take some time to set up the hardware and learn the new
> software. If any of you are experienced Linux users, you may be able to help
> with that.
> 
> NG9R
> 
> No virus found in this outgoing message.
> Checked by AVG. 
> Version: 7.5.524 / Virus Database: 269.23.7/1408 - Release Date: 4/30/2008
> 6:10 PM
>  
> 
> ______________________________________________________________
> Great-River-DX mailing list
> Home: http://mailman.qth.net/mailman/listinfo/great-river-dx
> Help: http://mailman.qth.net/mmmain.htm
> Post: mailto:Great-River-DX at mailman.qth.net
> administrator is dpease at adams.net
> 
> ______________________________________________________________
> Great-River-DX mailing list
> Home: http://mailman.qth.net/mailman/listinfo/great-river-dx
> Help: http://mailman.qth.net/mmmain.htm
> Post: mailto:Great-River-DX at mailman.qth.net
> administrator is dpease at adams.net
> 
> 
> 
> ______________________________________________________________
> Great-River-DX mailing list
> Home: http://mailman.qth.net/mailman/listinfo/great-river-dx
> Help: http://mailman.qth.net/mmmain.htm
> Post: mailto:Great-River-DX at mailman.qth.net
> administrator is dpease at adams.net
> 
> 
>