On 4/9/2016 9:03 PM, Cliff Frescura wrote:
> Yes, the signal has to travel ~22,300 miles x 2 (up and down).
In the early days of satellite telephone circuits (late 1960s - early
1970s before they used echo suppressors) the audible echo was about 3
seconds. Very disconcerting.
73 de K2ASP
[mailto:elecraft-boun...@mailman.qth.net] On
Behalf Of David Gilbert
Sent: Saturday, April 09, 2016 11:53 PM
To: elecraft@mailman.qth.net
Subject: Re: [Elecraft] Operating remotely via
Direct TV satellite provider
Not sure about the audio, but I think latency
would be the bigger issue. I had satellite
remotely via Direct TV satellite provider
Not sure about the audio, but I think latency would be the bigger issue. I
had satellite internet (essentially Hughes. net) for about three years
before a wireless ISP opened shop in our area. My typical pings were on the
order of 1300-1500 msec. I don't
Not sure about the audio, but I think latency would be the bigger
issue. I had satellite internet (essentially Hughes. net) for about
three years before a wireless ISP opened shop in our area. My typical
pings were on the order of 1300-1500 msec. I don't think you'd want to
live with that
The main problem is latency. It can affect audio spending on how it is
buffered.
Doug -- K0DXV
On 4/9/2016 8:23 PM, Don Strom wrote:
Is anyone operating their K3 remotely using a satellite provider.
I believe I heard that is not possible with satellite internet at the remote
site?
Is anyone operating their K3 remotely using a satellite provider.
I believe I heard that is not possible with satellite internet at the remote
site?
Something to do with the way the audio is passed via the internet connection.
Don W0EAR
Sent from Mail for Windows 10
6 matches
Mail list logo
