toggle quoted messageShow quoted text
A year or so ago I sent a message to this newsgroup with exactly same problem: ATEN USB-Serial converter, Prolific chip and choppy CW. Changing USB/Serial converter to true PCI COM port (that was a desktop PC) solved problem.
Beside that, updating driver from Prolific site was not possible. Only ATEN driver was applicable. And it was faulty.
---In N1MMLoggerplus@..., <w2cdo@...> wrote :
I’ve done a bit of sleuthing and found some interesting things: first, I’ve been using an ATEN USB-Serial device and a *Prolific* driver since the beginning. This is something I didn’t know. The WinKeyer USB uses the FTDI driver and chipset on COM4 and I must have been looking at that instead of the USB-Serial device on COM6 connected to the Mark V CAT. That said and contrary to the experience of many, the Prolific driver has worked for me (HP 500-205t i3-4350 CUP @ 3.60 GHz, 8 GB RAM, Win 10/64) so far. (Yes, I know I’m jinxing myself by saying this out loud.) Testing with only the Mark V at ~ 30 Watts I had no problem going between F keys and the manual keying. Kicking in the Alpha brought on the symptoms so the answer seems to be that RFI is affecting the device. I’ll wrap the stuff in tinfoil and install toroids to protect the connection. And replace most of my interconnect coax for good measure. Just in case it all stops working, can you remind me which USB-Serial adapters use the FTDI chipset?
p.s., Out of curiosity, can you tell me what this means: “Device USB\VID_0557&PID_2008\6&ba9edbb&0&1 requires further installation”? It shows up in the Information window under the Port’s Events tab and the Event Viewer provides the following: “Driver Management concluded the process to install driver ser2at.inf_amd64_2208228bed2dedb3\ser2at.inf for Device Instance ID USB\VID_0557&PID_2008\6&BA9EDBB&0&1 with the following status: 0x0.” The Event Log Online Help link goes to a “Page Not Found” on MS TechNet.
Sent from Mail for Windows 10
N1MM tfwagner@... [N1MMLoggerplus]Sent:
Monday, November 9, 2015 3:33 PMTo:
Re: [N1MMLoggerplus] Re: Macros and Choppy CW
Please report your results, good or bad.
This article used to be linked in the doc and the link got broken.
Tom - N1MM
On 11/9/2015 3:29 PM, Peter Alterman w2cdo@... [N1MMLoggerplus] wrote:
> Will do, Tom. Thanks.
> Sent from Mail <http://go.microsoft.com/fwlink/?LinkId=550986> for
> Windows 10
> *From: *N1MM tfwagner@... [N1MMLoggerplus]
> *Sent: *Monday, November 9, 2015 3:08 PM
> *To: *N1MMLoggerplus@...
> *Subject: *Re: [N1MMLoggerplus] Re: Macros and Choppy CW
> Try fiddling with the advanced settings in the FTDI driver for that
> "serial" port.
> Try very low receive/transmit bytes and 1 msec for the latency timer. I
> doubt timeout or the checkbox options will help.
> If you don't see any change, reset to defaults.
> Tom - N1MM
> On 11/9/2015 2:52 PM, Peter Alterman w2cdo@... [N1MMLoggerplus]
> > I’m one of those having trouble with choppy CW the first few
> > characters I send. Then it settles down after that. I use the FTDI
> > chip and current driver and Winkeyer. Have had this problem from the
> > very beginning of use of +. I figure it’s got to be a setting on the
> > virtual com port.
> > Peter W2CDO
> > Sent from Mail <http://go.microsoft.com/fwlink/?LinkId=550986> for
> > Windows 10
> > *From: *drew.vonadasmith@... [N1MMLoggerplus]
> > *Sent: *Monday, November 9, 2015 1:50 PM
> > *To: *N1MMLoggerplus@...
> > *Subject: *RE: [N1MMLoggerplus] Re: Macros and Choppy CW
> > Audio might be the most obvious preemptive Windows event, but it isn't
> > the only one. Serial CW generation works fine for you, and probably
> > works for most people, but it does not work for everyone, audio or
> > otherwise.
> > Winkey is the gold standard for good reasons.
> > 73,
> > Drew K3PA
> > ---In N1MMLoggerplus@..., <aldermant@...> wrote :
> > Being very polite --- That is total hogwash Rick!!
> > For years, I have run 100 + wpm QSO's using Windows 95 to the current
> > Windows 10 and I never have problems with NL+ macros nor with choppy
> > CW, no matter what CW generation application I use.
> > Understand how a computer works! The reason the serial port (or any PC
> > I/O port) will cause CW generation to be 'choppy' or to 'stutter' is
> > simply because when a CPU generates audio, it shuts all I/O ports
> > (meaning serial/parallel ports) OFF, generates the audio, and then
> > turns the I/O port ON again. The simple solution is to go into Windows
> > set-up and turn OFF the PC's internally generated audio.
> > The under informed will spend their nickel's to 'go buy a solution'; I
> > prefer to save my nickel to buy another bottle of wine. YMMV!!
> > 73,
> > Tom - W4BQF
> > -----Original Message-----
> > From: N1MMLoggerplus@...
> > <mailto:N1MMLoggerplus@...>
> > [mailto:N1MMLoggerplus@...
> > <mailto:N1MMLoggerplus@...>]
> > Sent: Monday, November 9, 2015 11:56 AM
> > To: k4ie_tom@... <mailto:k4ie_tom@...>
> > Cc: N1MMLoggerplus@...
> > Subject: [N1MMLoggerplus] Re: Macros and Choppy CW
> > Sending CW through any serial port - real or USB-adapted - is hit or
> > miss. Some versions of some logging programs will work with some ports
> > on some releases of some operating systems at some maximum system load
> > that depends on the CPU type, the nature of other programs running at
> > the same time, and the amount of I/O they are performing. (Most
> > notable here is Telnet spotting in a contest like SS in which many
> > operators spot every S&P QSO they make! The load is huge.)
> > Please, bite the bullet and get an external keyer that accepts ASCII
> > characters from the logger and forms dots and dashes outside the
> > computer CPU. Generating Morse Code is a real-time computing activity.
> > Windows was never intended to do real-time computing and, when asked,
> > doesn't do it very well. MM is one of the best at taming the beast but
> > some combinations of the factors listed above will confound even MM.
> > External keyers are nearly timing-independent. A Winkeyer USB is cheap
> > and reliable and will save you hours of frustration. There are many
> > alternative external keyers as well. I use a YCCC SO2R Box Plus.
> > Microham and other keyers and SO2R boxes work fine, too.
> > GL & 73,
> > /Rick N6XI
> > --
> > Rick Tavan N6XI
> > Truckee, CA