I'm having intermittent problems with pops in the audio stream from my remote 
K3 to my control site. They sound like brief, sub-second audio stream outages. 
When it's bad, it's several pops per second for 10-30 seconds, then clean 
operation for a minute or three. I've had some reports of interruptions on the 
transmit side, too. This is unacceptable. When it's "good," I hear only the 
occasional pop, quite survivable, but doing almost anything on the remote 
network, especially something with Chrome Remote Desktop, causes a flurry of 
pops.

I'm also seeing frequent delays in LCD updates, especially at initial 
connection time. I also see frequent UI artifacts, such as bogus RIT LEDs on 
the panel and incorrect LCD segments that come and go.

The remote side is nominally a fast, TV cable network, recently refurbished 
with new RG11 cable on the long run from the street. It shows ping times from 
15 to 40 msec, download 25-32 Mbps and upload (the critical parameter) 1.5-2 
Mbps. All these numbers "should be" acceptable. The client side speeds are even 
better, especially upload, but that's probably not relevant.

I've tried RRC jitter and packet size parameters in many combinations and the 
only noticeable impact is lengthening or shortening the duration of the 
individual pops, not their frequency of occurrence.

I'm using Linksys EA4500 routers at both the remote and client side networks, 
albeit with totally different user interfaces. Both claim to be "up to date" 
when I check for software revisions. Streaming audio and video work OK on both 
sides using various Web browsers and media players. Of course, they all have 
the luxury of being able to do deep buffering, something the RRC doesn't want 
to do.

I've had another K3 Remote user connect to my remote site from his control site 
with inconclusive results. One time he heard no pops for a few minutes, leading 
me to suspect my client side, but he didn't listen long enough to rule out just 
being there at a quiet time. Another time he heard badly distorted audio (which 
I've never heard at my place) and decided his home network must be saturated, 
so that test was invalid. I think he's out of time or patience for further 
testing.

The RRC tells me to open both UDP and TCP ports. Does anyone know which they 
use for audio? If it's UDP, then lost packets might sound like this. Lost 
packets would also explain the LCD and panel update problems. If that's the 
problem, what do I do about it? Does anyone have any other advice on how to 
further characterize and possibly solve this problem?

Thanks & 73,

/Rick N6XI
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]

This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html

Reply via email to