[WriteLog] VE7CC packet spot problem solved

Jim Reisert AD1C jjreisert at alum.mit.edu
Sat Aug 22 10:16:54 PDT 2009


K2MK is correct.  The USER program runs on port 7300 (that is the port 
that WriteLog connects to).  The connection FROM the user program to 
VE7CC node is on port 23.

73 - Jim AD1C

On 8/22/2009 10:43 AM, Gary AL9A wrote:
> Mike,
>
> Please reread Ron's last paragraph.  Lee recommends using port 23 instead of
> 7300.  If this is done and something happens to Lee's server, which has
> happened before due to his ISP or the local power going out, you are
> automatically reconnected to Ron's CC cluster - truly a seamless operation.
> Glade you like VE7CC User - it's a great interface.
>
> 73,
> Gary AL9A
>
>
> ----- Original Message -----
> From: "K2MK"<k2mk at comcast.net>
> To: "Ron Stordahl"<ron_n5in at yahoo.com>; "WriteLog Reflector"
> <WriteLog at CONTESTING.COM>
> Sent: August 22, 2009 4:20 AM
> Subject: Re: [WriteLog] VE7CC packet spot problem solved
>
>
>> Thanks Ron:
>>
>> I decided to try your suggestion of using the VE7CC User Program as an
>> intermediary. I searched the archive as you suggested and found out how to
>> do it.
>>
>> Open VE7CC User Program
>> Open WriteLog
>> On the WriteLog Telnet window, use an IP ADDRESS of 127.0.0.1 and a PORT
>> setting of 7300.
>>
>> Bingo, it works perfectly and it hasn't disconnected once in the 12 hours
>> I've been running it. It automatically feeds the packet information to
>> WriteLog. You just have to keep the VE7CC User Program running in the
>> background.

-- 
Jim Reisert AD1C, <jjreisert at alum.mit.edu>, http://www.ad1c.us


More information about the WriteLog mailing list