I don't use LPT port as early on I found that CW doesn't work as well as with COM port. I use COM 3 for rig control and also CW keying, COM 5 is dedicated for PTT w/PSK31 RigBlaster is commonplace with PSK31 and requires use of a separate COM port for PTT Rig control and CW keying work well on the same COM port, can't use LPT port for Rig control. Also, I don't care to re-engineer what use to work well and still works well with Writelog and other programs. That would create more problems when using other software. As I said before, It wasn't broke before and now it is. Ver 5.02/03 did this all fine by allowing a separate port selection. If you don't use a RigBlaster, or separate COM ports for CW and PTT for PSK31 that's what you are missing! If what you are doing works for you, thats great. Many others want it as it was before V.6
----- Original Message ----- From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> To: "'Roger Borowski'" <[EMAIL PROTECTED]>; "'Larry Gauthier'" <[EMAIL PROTECTED]> Cc: "'DX4Win Reflector'" <dx4win@mailman.qth.net> Sent: Sunday, March 16, 2003 8:13 PM Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > You haven't got it hooked up correctly... > > On the LPT port... > Pin 1 keys CW > Pin 16 keys PTT > > It sounds like you are using pin 1 for PTT > > I don't know anything about Rigblasters... > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Roger Borowski > Sent: March 16, 2003 4:07 PM > To: [EMAIL PROTECTED]; 'Larry Gauthier' > Cc: 'DX4Win Reflector' > Subject: Re: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > That doesn't work either, Mel. The PTT relay in the RigBlaster then keys > with every dit and dah or the radio PTT keys with every dit and dah in > the CW mode. It would likely work if you were to disconnect and > re-connect the PTT line for PSK31 but why not just allow the individual > software control for individual selection of ports for CW and PSK31 PTT > as it was in Ver 5.02/03 That wasn't broke and didn't need fixing! Now > its broke! -=Rog-K9RB=- > > ----- Original Message ----- > From: "Mel Martin (VE2DC)" <[EMAIL PROTECTED]> > To: "'Larry Gauthier'" <[EMAIL PROTECTED]> > Cc: "'DX4Win Reflector'" <dx4win@mailman.qth.net> > Sent: Sunday, March 16, 2003 3:24 PM > Subject: RE: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > > Hi Larry... You CAN use the LPT port to key both CW and PSK31/CW > > PTT... I would think this would only be a problem if you are using a > > different radio for PSK31... So work-around 1 should work... Obviously > > > workaround 2 won't unless you define a 2nd COM PTT interface for mmty > > and hook them up in parallel... > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > On Behalf Of Larry Gauthier > > Sent: March 16, 2003 1:41 PM > > To: dx4win@mailman.qth.net > > Subject: [Dx4win] PSK31 config change in DX4WIN 6.02? > > > > > > In DX4WIN 5.x, the PSK <Settings><Tx> screen allowed you to select the > > > PSK keying com port from 1-8, and either RTS or DTR as the keyed > > line. The 5.x PSK selection was completely independent of the keyed > > line for CW. In DX4WIN 6.02, it seems that your only choices for PSK > > keying are either the CW interface or VOX. What happened to the > > ability to independently choose a com port? > > > > In my 5.03 configuration, I had been using the LPT port for CW keying, > > > and the com port for keying in either PSK31 or MMTTY. As long as I did > > > not attempt to simultaneously open the PSK window and run MMTTY, this > > arrangement worked fine. > > > > Under 6.02, I attempted to work-arounds... neither which seem to work: > > > First work-around: telling DX4WIN to use the LPT CW interface for PSK > > keying. It doesn't work. PSK does not key via the LPT port... although > > > CW still works fine. > > > > Second work-around: Re-configure for CW keying via the com port. This > > allows CW and PSK to work properly, but prevents MMTTY from running. > > (DX4WIN grabs control of the CW port upon launch, and if you try to > > subsequently launch MMTTY you get a port conflict error.) > > > > > > Has anyone else encountered these problems? Does anyone have a > > suggestion on how to solve them? > > > > -larry > > K8UT > > > > --- StripMime Report -- processed MIME parts --- multipart/alternative > > text/plain (text body -- kept) > > text/html > > The reason this message is shown is because the post was in HTML or > > had an attachment. Attachments are not allowed. To learn how to post > > > in Plain-Text go to: http://www.expita.com/nomime.html --- > > _______________________________________________ > > Dx4win mailing list > > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > > > > _______________________________________________ > > Dx4win mailing list > > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > > _______________________________________________ > Dx4win mailing list > Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win > >
