WriteLog
[Top] [All Lists]

Re: [WriteLog] DTR On at startup keying my radio

To: Tom Georgens <tomgeorgens15@gmail.com>
Subject: Re: [WriteLog] DTR On at startup keying my radio
From: Dana Roode K6NR <dana.roode@gmail.com>
Date: Mon, 20 Sep 2021 16:03:38 -0700
List-post: <mailto:writelog@contesting.com>
Thanks Tom - I also got the following from Bob, N6TV, concurring with your
post and adding a bit more about Windows 10 FTDI Settings.

  Dana

---------- Forwarded message ---------
From: Bob Wilson, N6TV <n6tv@arrl.net>
Date: Mon, Sep 20, 2021 at 3:08 PM
Subject: Re: [WriteLog] DTR On at startup keying my radio
To: Kevin Rowett <kevin@rowett.org>
Cc: Dana Roode K6NR <dana.roode@gmail.com>


Hi Dana and Kevin,

This is a Writelog issue, and can be fixed.  But first make sure that the
FTDI Device Driver options for both K4 COM ports are set to "Disable Modem
Control at Startup" and that "Serial Enumeration" is disabled.  The Windows
defaults (which can get reset after a Windows 10 update, as they did
recently), are not good.  See slide 27 and following in this presentation:

   - Everything You Need to Know About USB and Serial Interfaces
   <https://bit.ly/USBserial2021>, updated for 2021

Here's what W0YK found some time ago:

I found the following in the WL Help file:

*The COMn_RTS_INIT and COMn_DTR_INIT settings are for the ports used for
rig control (only--not FSK or any other COM port uses) and change the
way WriteLog initializes the RTS and DTR lines **on** the rig port. Setting
the value to 0 (zero) causes WriteLog to initialize the line off. Setting
the value to 1 (one) causes WriteLog to initialize the line **on*
* (which is the default if there is no entry). Setting the value to
anything else, like -1 (minus one), causes WriteLog to not change the
port.WriteLog supports RTS/CTS flow control for some rig drivers that turn
that feature **on**, but only if you also set COMn_RTS_INIT = -2*

COM1_RTS_INIT=-2

COM1_DTR_INIT=1



Adding these two statements to writelog.ini solved that problem:



COM1_RTS_INIT=0

COM1_DTR_INIT=0

Where you would substitute the COM port number, so for COM5:) set both
COM5_RTS_INIT and COM5_DTR_INIT to 0 in writelog.ini.

73,
Bob, N6TV

On Mon, Sep 20, 2021 at 3:38 PM Tom Georgens <tomgeorgens15@gmail.com>
wrote:

> There is an entry in the ini file [Rigs]  to control this.  Here is the
> section in the help file
>
>
> >>>>>
> The COMn_RTS_INIT and COMn_DTR_INIT settings are for the ports used for rig
> control (only--not FSK or any other COM port uses) and change the way
> WriteLog initializes the RTS and DTR lines on the rig port. Setting the
> value to 0 (zero) causes WriteLog to initialize the line off. Setting the
> value to 1 (one) causes WriteLog to initialize the line on (which is the
> default if there is no entry). Setting the value to anything else, like -1
> (minus one), causes WriteLog to not change the port.
> WriteLog supports RTS/CTS flow control for some rig drivers that turn that
> feature on, but only if you also set COMn_RTS_INIT = -2
>
> COM1_RTS_INIT=-2
> COM1_DTR_INIT=1
> >>>>>
>
>
> Here is the entry in my ini file as an example.  I used the DTR lines for
> some other station automation stuff
>
> [RIGS]
> COM7_RTS_INIT=-1
> COM7_DTR_INIT=-1
> COM8_RTS_INIT=-1
> COM8_DTR_INIT=-1
>
> GL and 73, Tom W2SC
>
> -----Original Message-----
> From: WriteLog <writelog-bounces@contesting.com> On Behalf Of Dana Roode
> K6NR
> Sent: Monday, September 20, 2021 5:45 PM
> To: WriteLog@contesting.com
> Subject: [WriteLog] DTR On at startup keying my radio
>
> I am using a K4, configured for Writelog as a K3.  The same virtual port I
> use for sending radio commands is configured on the K4 for DTR as CW and
> RTS
> and PTT.  Writelog is set to PC Generates for CW.  I'm using version
> 12.60C.
>
> When I start Writelog for a new contest, the rigs keys while I am selecting
> the contest.  It stays keyed until I do an Alt-K and send a character using
> the keyboard.  After that, everything works great.  If I select a contest
> that is already setup, the radio keys while Writelog is initializing, then
> all is well even without sending a character via Alt-K.
>
> I guess Writelog has DTR on at startup?  Anyway to fix this?  For my
> principal location I use a Winkey and don't think I'll have this issue.
>
>   Dana
> _______________________________________________
> WriteLog mailing list
> WriteLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
>
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web:  http://www.writelog.com/

<Prev in Thread] Current Thread [Next in Thread>