[[WriteLog] thanks - PCI3000 squelch]

GilBaronW0MN gbaron@charter.net
Fri, 1 Feb 2002 14:14:47 -0600


MMTTY interface is much better and has squelch too.


> -----Original Message-----
> From: writelog-admin@contesting.com
> [mailto:writelog-admin@contesting.com]On Behalf Of Duane Calvin
> Sent: Friday, February 01, 2002 13:43
> To: DJ3IW Goetz; writelog@contesting.com
> Subject: Re: [[WriteLog] thanks - PCI3000 squelch]
> 
> 
> I'd like to know the answer too - same problem with the DXP38 
> TNC.  Usually my
> noise level is high enough that the squelch is opened anyway, but 
> would like
> to be able to turn off the rig and have the squelch take over.  Somehow
> WriteLog bypasses this function.
> 
>    73, Duane 
> 
> 
> "DJ3IW Goetz" <k0869565@tiscalinet.de> wrote:
> Hello
> and thanks to all, who answered my previous plea for help.
> Having the WriteLog window active and hitting the F-keys
> produces nice, clean Baudot - I always tried to transmit out of
> the Rttyrite window.
> Now I have another, PCI-3000 specific question:
> When I activate the Rttyrite window and have the RX on, endless garbage
> is printed in the receive screen. The PCI-3000 has a print squelch
> function that needs to be activated and set properly. WF1B RTTY provides
> a "talk to TNC/TU" function for this purpose (and some other PCI-3000
> specific parameters). Where and how can I do this in WriteLog/Rttyrite?
> My guess is the WriteLog.INI - but how? Please answer direct to my email
> address.
>  
> 73 de Goetz, DJ3IW
> k0869565@tiscalinet.de
> 
> 
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> 
> 
> Duane Calvin, AC5AA
> Austin, Texas
> 
> ____________________________________________________________________
> Get free e-mail and a permanent address at http://www.amexmail.com/?A=1
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
>