[Elecraft] [K3] - Data mode TX problem from VK7JB

[Don Wilhelm]

Tony,

I do not disagree with your statements, but as you have alluded to, many 
ham applications are not written to deal with the requirements of later 
OS versions - you cited some examples.  User be aware!  Yes, a properly 
written application will "ride around" those interruptions caused by 
virus checkers and other things going on with the computer maintenance, 
but others do not, they expect to have full control of the computer if 
their window is open - unfortunately, that is not within the realm of 
reality with today's OS - background applications must exist and do 
their function, whether that be virus checking or the ethernet 
connection or any of the other computer services that run in the 
background and we take for granted as "just being there".

User awareness of this situation is essential - the K3 is probably not 
to blame for the clicks and pops, it is most likely that the computer 
that is causing them.  If the K3 creates the clicks and pops with no 
input from the computer, then it is a K3 problem, but it the K3 output 
is clean with no computer input and there is clicks and pops when the 
computer is introduced, the clicks and pops are being generated in the 
computer audio stream - nothing that the K3 (or any other transceiver) 
can do about it..

73,
Don W3FPR

On 9/13/2011 8:14 PM, Tony Estep wrote:
> Sure, but DPCs may be caused by anything that is running on your 
> machine. The most common offender is a WiFi driver, which has nothing 
> to do with ham software. The issue of weak coding standards in ham 
> software is a different topic, one that I've bemoaned before on this 
> forum. To write real-time software with a GUI requires coding skills 
> that are beyond most hobbyist programmers. Even among the pros there 
> are those who have the requisite advanced knowledge and skills, and 
> those who don't. To experience this firsthand, just plunge yourself 
> into the whirlpool of PSDRs and their associated virtual serial ports 
> and virtual audio cables. Most of it works most of the time, but it's 
> a long way from being consumer-friendly. However, as I said, ham 
> software probably is not related to the pops and clicks that were 
> reported in earlier posts. If they are being caused by DPCs, it's most 
> likely due to something like the virus-checker, the safe-site monitor, 
> the WiFi driver, or other unexpected source.