[Elecraft] Remote K2

[Jack Brindle]

The only way to avoid TCP/IP would be to set up a dedicated twisted  
pair between your place and the remote location. This is a very  
expensive solution, and I'd bet you really don't want to spring for it.  
The reason that you really need to use TCP/IP is that it is the only  
protocol suite that is commonly passed among the internet. Pretty much  
all other protocols are blocked.

The only alternative realistically would be to set up at least one  
phone line at the radio site to carry the control and data information  
to and from the radio. The device would have to answer the phone,  
connect to the radio and start controlling things. There would need to  
be a separate path for the voice or CW data so that rig controls data  
would not interfere with it - thus you would really need two lines. Of  
course, this could also be a phone line which carries DSL. One function  
of the box would be to make sure that only you can operate the rig, and  
that the rig does NOT transmit when you are not controlling it live.

Somehow I suspect that the other TCP/IP networked solutions might  
actually provide what you need. There are some pretty cool ones as you  
are now learning...

On Oct 11, 2004, at 5:56 AM, John Huffman wrote:

> Richard -
>
> Thanks for the info.  I'd like to avoid tcp/ip if I could because of  
> what I assume is the latency involved.  I want to operate a remote  
> radio and yet still want to have QSK CW.  Does your set-up allow QSK?
>
> I don't have an internet connection faster than dial-up and doubt I  
> could get anything better at a remote site.
>
> The latency may be an incorrect assumption on my part and I'd  
> appreciate being corrected.
>
> Thanks again,
>
> 73 de NA8M
> John

- Jack Brindle, WA4FIB
------------------------------------------------------------------------ 
---------------------