Charlie
Yup, that is the setting I have in the .ini file. Doesn't help.
As soon as you turn on CW on any port (even one that connects to a Winkeyer),
the program asserts DTR on all COM ports, no matter what.
Oh, well.
/steve
----- Original Message ----
From: Charles Morrison <cfmorris@bellsouth.net>
To: Steve Jackson <kz1x@yahoo.com>; writelog@contesting.com
Sent: Thursday, August 21, 2008 7:26:45 PM
Subject: RE: cool new upgrade!
I see. My disconnect comes from 2 things, one, running RTTY, I always had
an interface. Since I ran Icom's I had to have com ptt, because this was
the only way to get the Icoms to key, no rig based PTT. Using the
Rigblaster Pro, one port was set for PTT/FSK and the other set for Rig
Control. Setting Writelog up to use the ALL MODE PTT ON CW PORT RTS
underneath the ports takes care of that in SSB contesting where you gotta
have the PTT.
This of course all changes with the K3, because you don't have to have the
interface. Therefore the PTT set to the interface's port doesn't key the
rigs through the mic jack. So, now I see. However, I looked at the ini
file, have you tried under the ports section in the ini file and checked the
CWPTTCONTROL=0 setting? If I understand correctly, this controls PTT signals
on the chosen port (1=com, 2=lpt, 0=none) when in CW mode. If the K3 is set
to accept ptt, and WL isn't putting it out based on the ini file setting,
then you should be able to leave the K3 like it is for other programs. You
really don't need PTT for CW contesting with Wl, because as soon as you
close the key on the k3, it's going to key the rig anyway!
So, disabling CW PTT, does that change the PTT? (I Havent tried this yet).
> -----Original Message-----
> From: Steve Jackson [mailto:kz1x@yahoo.com]
> Sent: Thursday, August 21, 2008 6:05 PM
> To: cfmorris@bellsouth.net; writelog@contesting.com
> Subject: Re: cool new upgrade!
>
> Hi Charlie
>
> The K3 is set to use the DTR pin on its COM port for PTT, for use with all
> other programs I have that do rig control.
>
> Unless I reconfigure the radio to ignore this signal ... when I run
WriteLog
> with the WK USB on COM 3, WriteLog asserts DTR on *all* ports defined,
> including COM1, where the rig is. Voila! The rig's TX is immediately
stuck
> keyed on, even though I don't want it to be.
>
> Deselecting COMM PTT for the rig has no effect.
>
> I'm not really sure what purpose is served by keying all COM ports' DTR
lines
> when only one is needed ever, and in the case of the Winkeyer, none are
> needed. But that's the way it works.
>
> So, like others who have written me on this topic, if you're not using the
> K3's ability to key PTT and CW with these lines, then simply shut them
'off'
> and you're good to go, no worries.
>
> If you use another program that uses DTR on the COM port for PTT (any of
the
> AFSK/APSK programs, and most general logging programs), then you have to
> reconfigure the rig when you want to use WriteLog. It's a minor matter,
> although it seems simple (to me) to optionally disable this "all ports DTR
> keyed" when a WK option is selected.
>
> 73 Steve KZ1X/4
>
>
>
> ----- Original Message ----
> From: Charles Morrison <cfmorris@bellsouth.net>
> To: writelog@contesting.com
> Cc: kz1x@yahoo.com
> Sent: Thursday, August 21, 2008 5:35:28 PM
> Subject: RE: cool new upgrade!
>
> Hey Steve, now I have a K3, and I have a WKUSB, and I'm using Writelog.
So
> again, refresh what the problem is with PTT being exerted on the ports?
>
> I've configured Writelog to use Comm PTT on com4, comslot 4, I've
configured
> WKUSB on Com2, comslot2 Winkeyer is selected, Windows Soundboard is
selected
> for DVK. My Yaesu G-2800DXA is on com1, and it works fine.
>
> When I'm in a CW contest, and the rig is in CW, WL keys the Wkusb, which
in
> turn keys the radio. Both Full and semi breakin work, based upon the QSK
> setting on the rig. Touching the paddle interrupts the keying being sent
> from the radio.
>
> Selecting a SSB contest, putting the radio into SSB mode and pressing
F1-F9
> plays the associated wave file, assuming its been created, as well as keys
> the rig.
>
> Bandmap seems to work fine, tracks the frequency.
>
> What other com ports are you using for what modes, and what problems are
> they having, and how is the DTR/RTS problem affecting you? Is it just for
> other peripherals beyond the 4 defined in the program, or is it because
> you're not using a computer command based PTT in other programs, therefore
> you need real mode ptt from a com port in WL?
>
> Again, I'm in the dark.
>
> Charlie
> KI5XP
>
> > From: Steve Jackson <kz1x@yahoo.com>
> > Subject: [WriteLog] cool new upgrade!
> > To: WriteLog@contesting.com
> > Message-ID: <529828.44813.qm@web34604.mail.mud.yahoo.com>
> > Content-Type: text/plain; charset=us-ascii
> >
> > It's super to have the K3 directly supported, and all the other detailed
> > enhancements. These continued upgrades are just another reason why I am
> > really happy with this program.
> >
> > I hope the "to-do" list still includes removal of the default DTR/RTS
> toggle
> > on all COM ports for CW keying, when a Winkeyer option is selected. I'd
> love
> > to be able to use the K3 *and* the Winkeyer, without having to
reconfigure
> the
> > rig every time I use Writelog.
> >
> > One way to do this without modifying Writelog would be to have the rig-
> > reconfig command sequence sent out the serial port upon starting
Writelog,
> and
> > reversing the commands sent upon exiting the application. Adding an
> optional,
> > definable-string init and exit macro set could be a great add-on, no
> matter
> > what. Just an idea ...
> >
> > Steve KZ1X/4
> >
>
>
>
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|