Re: [Elecraft] K3/K3s Ethernet Interface
Special driver. Sigh, more Windows-only ham software. A Telnet connection could be used by hamlib. wunder K6WRU CM87wj http://observer.wunderwood.org/ (my blog) On Jul 20, 2015, at 1:53 AM, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: Yes you can use it one of two ways... in TCP mode, there is a small driver loaded on your PC that creates a pseudo RS232 port on the computer that all your existing software connects to. Your software thinks it's talking to your radio via RS232... but really that is an emulation that gets ported over the Ethernet to the radio (where the Ethernet to RS232 server is) and deconstructed into RS232 (RXD and TXD) with DTR and RTS for keying. Your computer can be right next to your radio or half way around the world and the radio will never know the difference. Latency is not a problem. Second mode is WEB server where the radio is emulated in web pages in the onboard web server (eg web page looks like the radio). You can change any parameter in the setup or knob on the radio that you could via RS232. No security is provided. Nor is there with the FLEX, Ten-tec, or any other radio that has an Ethernet connection currently. I just use a Netgear firewall and VPN through it securely. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton – J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Pierfrancesco Caci [mailto:p...@tippete.net] Sent: Monday, July 20, 2015 12:35 AM To: b...@wjschmidt.com; 'Paul Christensen'; elecraft@mailman.qth.net Subject: Re: [Elecraft] K3/K3s Ethernet Interface On 19 July 2015 23:40:51 CEST, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: I have a prototype Ethernet interface running inside my K3 right now... simple replacement for the KIO3 board. I posted a couple of times suggesting it but was completely ignored so I build my own. It's just a pic with Ethernet capabilities and replaces the functions of the KIO3 completely and more. It will be available commercially soon... Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch - K9ZC Staunton, Illinois Owner - Operator Villa Grand Piton - J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Paul Christensen Sent: Sunday, July 19, 2015 2:24 PM To: elecraft@mailman.qth.net Subject: [Elecraft] K3/K3s Ethernet Interface This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all of it. The Holy Grail is an Ethernet interface that includes (optional) integrated RemoteRig hardware - just one interface board [e.g., KIO3E(thernet) board] that manages K3 Ethernet connectivity with or without RemoteRig attributes. Don't need Ethernet
Re: [Elecraft] K3/K3s Ethernet Interface
Or for those who own a Navigator or similar interface, do not need the new KXV3A interface board. They may already have a single USB connection to the radio. Using the setup I have now, It took less than 30 minutes to remote control my K-Line via my iPhone 6 plus yesterday, now if someone just comes up with a iWatch app. 73s Jim, W4ATK On 7/20/2015 6:55 AM, Walter Underwood wrote: Special driver. Sigh, more Windows-only ham software. A Telnet connection could be used by hamlib. wunder K6WRU CM87wj http://observer.wunderwood.org/ (my blog) On Jul 20, 2015, at 1:53 AM, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: Yes you can use it one of two ways... in TCP mode, there is a small driver loaded on your PC that creates a pseudo RS232 port on the computer that all your existing software connects to. Your software thinks it's talking to your radio via RS232... but really that is an emulation that gets ported over the Ethernet to the radio (where the Ethernet to RS232 server is) and deconstructed into RS232 (RXD and TXD) with DTR and RTS for keying. Your computer can be right next to your radio or half way around the world and the radio will never know the difference. Latency is not a problem. Second mode is WEB server where the radio is emulated in web pages in the onboard web server (eg web page looks like the radio). You can change any parameter in the setup or knob on the radio that you could via RS232. No security is provided. Nor is there with the FLEX, Ten-tec, or any other radio that has an Ethernet connection currently. I just use a Netgear firewall and VPN through it securely. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton – J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Pierfrancesco Caci [mailto:p...@tippete.net] Sent: Monday, July 20, 2015 12:35 AM To: b...@wjschmidt.com; 'Paul Christensen'; elecraft@mailman.qth.net Subject: Re: [Elecraft] K3/K3s Ethernet Interface On 19 July 2015 23:40:51 CEST, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: I have a prototype Ethernet interface running inside my K3 right now... simple replacement for the KIO3 board. I posted a couple of times suggesting it but was completely ignored so I build my own. It's just a pic with Ethernet capabilities and replaces the functions of the KIO3 completely and more. It will be available commercially soon... Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch - K9ZC Staunton, Illinois Owner - Operator Villa Grand Piton - J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Paul Christensen Sent: Sunday, July 19, 2015 2:24 PM To: elecraft@mailman.qth.net Subject: [Elecraft] K3/K3s Ethernet Interface This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all
Re: [Elecraft] K3/K3s Ethernet Interface
On 20 July 2015 07:53:04 CEST, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: Yes you can use it one of two ways... in TCP mode, there is a small driver loaded on your PC that creates a pseudo RS232 port on the computer that all your existing software connects to. Your software thinks it's talking to your radio via RS232... but really that is an emulation that gets ported over the Ethernet to the radio (where the Ethernet to RS232 server is) and deconstructed into RS232 (RXD and TXD) with DTR and RTS for keying. Your computer can be right next to your radio or half way around the world and the radio will never know the difference. Latency is not a problem. Second mode is WEB server where the radio is emulated in web pages in the onboard web server (eg web page looks like the radio). You can change any parameter in the setup or knob on the radio that you could via RS232. No security is provided. Nor is there with the FLEX, Ten-tec, or any other radio that has an Ethernet connection currently. I just use a Netgear firewall and VPN through it securely. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton – J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com William, The fact that you mention a driver makes me think this will be limited to a certain OS. Please correct me if I'm wrong. You didn't answer my question about firmware updates to the K3. Will it be possible to use k3util in the normal way, for doing upgrades, saving and restoring config, doing the calibration? How will network latency and packet loss affect critical operations like firmware uploads? Pf ik5pvx -- Pierfrancesco Caci __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3/K3s Ethernet Interface
Not really. The drivers are available for windows, mac, and flavors of unix. They are standard drivers. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton - J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com On Jul 20, 2015, at 6:55 AM, Walter Underwood wun...@wunderwood.org wrote: Special driver. Sigh, more Windows-only ham software. A Telnet connection could be used by hamlib. wunder K6WRU CM87wj http://observer.wunderwood.org/ (my blog) On Jul 20, 2015, at 1:53 AM, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: Yes you can use it one of two ways... in TCP mode, there is a small driver loaded on your PC that creates a pseudo RS232 port on the computer that all your existing software connects to. Your software thinks it's talking to your radio via RS232... but really that is an emulation that gets ported over the Ethernet to the radio (where the Ethernet to RS232 server is) and deconstructed into RS232 (RXD and TXD) with DTR and RTS for keying. Your computer can be right next to your radio or half way around the world and the radio will never know the difference. Latency is not a problem. Second mode is WEB server where the radio is emulated in web pages in the onboard web server (eg web page looks like the radio). You can change any parameter in the setup or knob on the radio that you could via RS232. No security is provided. Nor is there with the FLEX, Ten-tec, or any other radio that has an Ethernet connection currently. I just use a Netgear firewall and VPN through it securely. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton – J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Pierfrancesco Caci [mailto:p...@tippete.net] Sent: Monday, July 20, 2015 12:35 AM To: b...@wjschmidt.com; 'Paul Christensen'; elecraft@mailman.qth.net Subject: Re: [Elecraft] K3/K3s Ethernet Interface On 19 July 2015 23:40:51 CEST, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: I have a prototype Ethernet interface running inside my K3 right now... simple replacement for the KIO3 board. I posted a couple of times suggesting it but was completely ignored so I build my own. It's just a pic with Ethernet capabilities and replaces the functions of the KIO3 completely and more. It will be available commercially soon... Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch - K9ZC Staunton, Illinois Owner - Operator Villa Grand Piton - J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Paul Christensen Sent: Sunday, July 19, 2015 2:24 PM To: elecraft@mailman.qth.net Subject: [Elecraft] K3/K3s Ethernet Interface This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3
Re: [Elecraft] K3/K3s Ethernet Interface
Yes that is where i started. With one of those outboard boxes a couple of years ago. I found it easy to condense the whole thing into the K3. The part I'm working in now is the VOIP integration so that with just a single connection, you can be completely remote. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton - J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com On Jul 20, 2015, at 11:00 AM, Gerry Hull ge...@w1ve.com wrote: There is plenty of Ethernet-to-RS-232 hardware around if you want to roll your own. http://www.ebay.com/itm/RS232-RS485-to-TCP-IP-Ethernet-Serial-Device-Server-NEW-/301230345289?pt=LH_DefaultDomain_0hash=item4622ba4c49 $19, connect via TCP, TCP Server, or UDP, UDP server. I find surplux Moxa Serial servers on ebay. I got a 24-port 1U RS232 box for $50... Drivers are available for Windows or Linux. 73, Gerry W1VE Gerry Hull, W1VE | Hancock, NH USA | +1-603-499-7373 AKA: VE1RM | VY2CDX | VO1CDX | 6Y6C | 8P9RM On Mon, Jul 20, 2015 at 8:53 AM, Pierfrancesco Caci p...@tippete.net wrote: On 20 July 2015 07:53:04 CEST, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: Yes you can use it one of two ways... in TCP mode, there is a small driver loaded on your PC that creates a pseudo RS232 port on the computer that all your existing software connects to. Your software thinks it's talking to your radio via RS232... but really that is an emulation that gets ported over the Ethernet to the radio (where the Ethernet to RS232 server is) and deconstructed into RS232 (RXD and TXD) with DTR and RTS for keying. Your computer can be right next to your radio or half way around the world and the radio will never know the difference. Latency is not a problem. Second mode is WEB server where the radio is emulated in web pages in the onboard web server (eg web page looks like the radio). You can change any parameter in the setup or knob on the radio that you could via RS232. No security is provided. Nor is there with the FLEX, Ten-tec, or any other radio that has an Ethernet connection currently. I just use a Netgear firewall and VPN through it securely. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton – J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com William, The fact that you mention a driver makes me think this will be limited to a certain OS. Please correct me if I'm wrong. You didn't answer my question about firmware updates to the K3. Will it be possible to use k3util in the normal way, for doing upgrades, saving and restoring config, doing the calibration? How will network latency and packet loss affect critical operations like firmware uploads? Pf ik5pvx -- Pierfrancesco Caci __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to ge...@w1ve.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3/K3s Ethernet Interface
There is plenty of Ethernet-to-RS-232 hardware around if you want to roll your own. http://www.ebay.com/itm/RS232-RS485-to-TCP-IP-Ethernet-Serial-Device-Server-NEW-/301230345289?pt=LH_DefaultDomain_0hash=item4622ba4c49 $19, connect via TCP, TCP Server, or UDP, UDP server. I find surplux Moxa Serial servers on ebay. I got a 24-port 1U RS232 box for $50... Drivers are available for Windows or Linux. 73, Gerry W1VE Gerry Hull, W1VE | Hancock, NH USA | +1-603-499-7373 AKA: VE1RM | VY2CDX | VO1CDX | 6Y6C | 8P9RM http://www.yccc.org http://www.yccc.org/ http://www.facebook.com/gerryhull https://plus.google.com/+GerryHull/posts http://www.twitter.com/w1ve On Mon, Jul 20, 2015 at 8:53 AM, Pierfrancesco Caci p...@tippete.net wrote: On 20 July 2015 07:53:04 CEST, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: Yes you can use it one of two ways... in TCP mode, there is a small driver loaded on your PC that creates a pseudo RS232 port on the computer that all your existing software connects to. Your software thinks it's talking to your radio via RS232... but really that is an emulation that gets ported over the Ethernet to the radio (where the Ethernet to RS232 server is) and deconstructed into RS232 (RXD and TXD) with DTR and RTS for keying. Your computer can be right next to your radio or half way around the world and the radio will never know the difference. Latency is not a problem. Second mode is WEB server where the radio is emulated in web pages in the onboard web server (eg web page looks like the radio). You can change any parameter in the setup or knob on the radio that you could via RS232. No security is provided. Nor is there with the FLEX, Ten-tec, or any other radio that has an Ethernet connection currently. I just use a Netgear firewall and VPN through it securely. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton – J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com William, The fact that you mention a driver makes me think this will be limited to a certain OS. Please correct me if I'm wrong. You didn't answer my question about firmware updates to the K3. Will it be possible to use k3util in the normal way, for doing upgrades, saving and restoring config, doing the calibration? How will network latency and packet loss affect critical operations like firmware uploads? Pf ik5pvx -- Pierfrancesco Caci __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to ge...@w1ve.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3/K3s Ethernet Interface
FB Bill, Yes, I have a couple of the boards. My career is in telecom/VoIP... software, rather than hardware. What microprocessor you using? Are you using open source software? I'd be interested to know which one. Essentially, you are doing RemoteRig over, in a different form factor. This is awesome -- giving choice in the marketplace. If you ever need a beta tester, let me know! 73, Gerry W1VE Gerry Hull, W1VE | Hancock, NH USA | +1-603-499-7373 AKA: VE1RM | VY2CDX | VO1CDX | 6Y6C | 8P9RM http://www.yccc.org http://www.yccc.org/ http://www.facebook.com/gerryhull https://plus.google.com/+GerryHull/posts http://www.twitter.com/w1ve On Mon, Jul 20, 2015 at 1:07 PM, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: Yes that is where i started. With one of those outboard boxes a couple of years ago. I found it easy to condense the whole thing into the K3. The part I'm working in now is the VOIP integration so that with just a single connection, you can be completely remote. *Dr. **William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ* Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton - J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com On Jul 20, 2015, at 11:00 AM, Gerry Hull ge...@w1ve.com wrote: There is plenty of Ethernet-to-RS-232 hardware around if you want to roll your own. http://www.ebay.com/itm/RS232-RS485-to-TCP-IP-Ethernet-Serial-Device-Server-NEW-/301230345289?pt=LH_DefaultDomain_0hash=item4622ba4c49 $19, connect via TCP, TCP Server, or UDP, UDP server. I find surplux Moxa Serial servers on ebay. I got a 24-port 1U RS232 box for $50... Drivers are available for Windows or Linux. 73, Gerry W1VE Gerry Hull, W1VE | Hancock, NH USA | +1-603-499-7373 AKA: VE1RM | VY2CDX | VO1CDX | 6Y6C | 8P9RM http://www.yccc.org http://www.yccc.org/ http://www.facebook.com/gerryhull https://plus.google.com/+GerryHull/posts http://www.twitter.com/w1ve On Mon, Jul 20, 2015 at 8:53 AM, Pierfrancesco Caci p...@tippete.net wrote: On 20 July 2015 07:53:04 CEST, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: Yes you can use it one of two ways... in TCP mode, there is a small driver loaded on your PC that creates a pseudo RS232 port on the computer that all your existing software connects to. Your software thinks it's talking to your radio via RS232... but really that is an emulation that gets ported over the Ethernet to the radio (where the Ethernet to RS232 server is) and deconstructed into RS232 (RXD and TXD) with DTR and RTS for keying. Your computer can be right next to your radio or half way around the world and the radio will never know the difference. Latency is not a problem. Second mode is WEB server where the radio is emulated in web pages in the onboard web server (eg web page looks like the radio). You can change any parameter in the setup or knob on the radio that you could via RS232. No security is provided. Nor is there with the FLEX, Ten-tec, or any other radio that has an Ethernet connection currently. I just use a Netgear firewall and VPN through it securely. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton – J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com William, The fact that you mention a driver makes me think this will be limited to a certain OS. Please correct me if I'm wrong. You didn't answer my question about firmware updates to the K3. Will it be possible to use k3util in the normal way, for doing upgrades, saving and restoring config, doing the calibration? How will network latency and packet loss affect critical operations like firmware uploads? Pf ik5pvx -- Pierfrancesco Caci __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to ge...@w1ve.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3/K3s Ethernet Interface
Jack, All valid points but take note of K9HZ's work as a start. Nevertheless, let's say native Ethernet control isn't worth the engineering effort. That should not preclude the integration of RemoteRig as an option into a K3/K3s. If I didn't care about the resale value of my K3 or RemoteRig, I could easily turn this into a weekend construction project and be up and running on Monday morning with an Ethernet cable hanging from the back of the K3. The RemoteRig board would come out of its enclosure then mount in the K3. It's just a matter of adding an RJ45 port, tapping +12V, internal audio, RS-232, PTT, key line, and ACC. The tapping of RS232 and audio is not trivial but it is completely manageable. While this adds little additional operational utility than it does now, it significantly cleans up K3 cabling with RemoteRig. No change is needed at the client end for use with the K3 mini. For K3 clients, a similar integration could accomplished or kept as it is now with external cabling. Of course, there must be enough demand from remote users to make it worthwhile as well as cooperation from Microbit. Paul, W9AC Sent from my iPhone6 On Jul 19, 2015, at 4:56 PM, Jack Brindle jackbrin...@me.com wrote: Paul; What is your proposal for the host-side interface? Pretty much all host programs these days use a serial interface. We usually use this through a USB-Serial adapter or through built-in serial ports, which are rapidly disappearing. To make this viable we would need drivers for all major platforms that implement a serial port driver interface to ethernet. Or, the host programs will need to be modified. There is a lot of work needed to make this suggestion viable, both on the host and radio sides. This is the fact same reason we still use serial interfaces for our rigs instead of true USB interface. Put forth a good proposal and let it be considered. Without that work (whoever does it), ethernet hardware isn’t very useful. - Jack, W6FB p.s., no, this isn’t a flame, but a challenge. Let’s get the whole thing viable, then we will take a good look at implementing it on all sides. On Jul 19, 2015, at 12:24 PM, Paul Christensen w...@arrl.net wrote: This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all of it. The Holy Grail is an Ethernet interface that includes (optional) integrated RemoteRig hardware - just one interface board [e.g., KIO3E(thernet) board] that manages K3 Ethernet connectivity with or without RemoteRig attributes. Don't need Ethernet? Then don't get the board. Since the RemoteRig hardware is mature and consumes little circuit board space and DC current, perhaps it would be worth opening up a discussion with RemoteRig's designer since Elecraft already has a close relationship with Microbit.I know rear panel real estate is a concern, so it won't be easy to add yet another connector without adversely affecting other connectivity. Thoughts? Paul, W9AC __ Elecraft
Re: [Elecraft] K3/K3s Ethernet Interface
What you all fail to realize is that RemoteRig is a Microbit product, not an Elecraft product. It's designed to be used with a number of radios. What I'd like to see is RemoteRig in another form factor, with some type of high-density connector that has all the important signals. For example, why couldn't the Remoterig board be re-worked to fit on the back of a K3/0 Mini? That would be great. Perhaps Elecraft can work a deal with Microbit. From the RF site, a box redesign with a single high-density connector and one ethernet would be great. 73, Gerry, W1VE Remoting happily from Many K3/RemoteRig combos. Gerry Hull, W1VE | Hancock, NH USA | +1-603-499-7373 AKA: VE1RM | VY2CDX | VO1CDX | 6Y6C | 8P9RM http://www.yccc.org http://www.yccc.org/ http://www.facebook.com/gerryhull https://plus.google.com/+GerryHull/posts http://www.twitter.com/w1ve On Sun, Jul 19, 2015 at 6:00 PM, Paul Christensen w...@arrl.net wrote: Jack, All valid points but take note of K9HZ's work as a start. Nevertheless, let's say native Ethernet control isn't worth the engineering effort. That should not preclude the integration of RemoteRig as an option into a K3/K3s. If I didn't care about the resale value of my K3 or RemoteRig, I could easily turn this into a weekend construction project and be up and running on Monday morning with an Ethernet cable hanging from the back of the K3. The RemoteRig board would come out of its enclosure then mount in the K3. It's just a matter of adding an RJ45 port, tapping +12V, internal audio, RS-232, PTT, key line, and ACC. The tapping of RS232 and audio is not trivial but it is completely manageable. While this adds little additional operational utility than it does now, it significantly cleans up K3 cabling with RemoteRig. No change is needed at the client end for use with the K3 mini. For K3 clients, a similar integration could accomplished or kept as it is now with external cabling. Of course, there must be enough demand from remote users to make it worthwhile as well as cooperation from Microbit. Paul, W9AC Sent from my iPhone6 On Jul 19, 2015, at 4:56 PM, Jack Brindle jackbrin...@me.com wrote: Paul; What is your proposal for the host-side interface? Pretty much all host programs these days use a serial interface. We usually use this through a USB-Serial adapter or through built-in serial ports, which are rapidly disappearing. To make this viable we would need drivers for all major platforms that implement a serial port driver interface to ethernet. Or, the host programs will need to be modified. There is a lot of work needed to make this suggestion viable, both on the host and radio sides. This is the fact same reason we still use serial interfaces for our rigs instead of true USB interface. Put forth a good proposal and let it be considered. Without that work (whoever does it), ethernet hardware isn’t very useful. - Jack, W6FB p.s., no, this isn’t a flame, but a challenge. Let’s get the whole thing viable, then we will take a good look at implementing it on all sides. On Jul 19, 2015, at 12:24 PM, Paul Christensen w...@arrl.net wrote: This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B
Re: [Elecraft] K3/K3s Ethernet Interface
I have a prototype Ethernet interface running inside my K3 right now... simple replacement for the KIO3 board. I posted a couple of times suggesting it but was completely ignored so I build my own. It's just a pic with Ethernet capabilities and replaces the functions of the KIO3 completely and more. It will be available commercially soon... Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch - K9ZC Staunton, Illinois Owner - Operator Villa Grand Piton - J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Paul Christensen Sent: Sunday, July 19, 2015 2:24 PM To: elecraft@mailman.qth.net Subject: [Elecraft] K3/K3s Ethernet Interface This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all of it. The Holy Grail is an Ethernet interface that includes (optional) integrated RemoteRig hardware - just one interface board [e.g., KIO3E(thernet) board] that manages K3 Ethernet connectivity with or without RemoteRig attributes. Don't need Ethernet? Then don't get the board. Since the RemoteRig hardware is mature and consumes little circuit board space and DC current, perhaps it would be worth opening up a discussion with RemoteRig's designer since Elecraft already has a close relationship with Microbit.I know rear panel real estate is a concern, so it won't be easy to add yet another connector without adversely affecting other connectivity. Thoughts? Paul, W9AC __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to b...@wjschmidt.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3/K3s Ethernet Interface
Cool! Please publish the specs. How secure it it? SSL? TLS 1.2 (or better)? Will there be accommodations for upgrades as security problems are found? Does it do ipv6 (which is rapidly becoming a requirement)? My concern is this - we are putting a rather powerful transceiver on the internet. With Telnet or any other non-secure format/protocol there is a lot of potential for someone to take over the data stream and use the transceiver for their use. Even with secure protocols there has been a very poor record of vulnerabilities and other problems taking over computers, breaking in for information or other problems. Exposing a ham transceiver to this endangers your license and our spectrum. Anything that is not secure should not come close to a radio. Today that means TLS 1.2 and full security. And updates to fix bugs as they are exposed. We are at the beginning of the age of IOT, the Internet Of Things. There are many very good manufacturers working on chips and interfaces for embedded devices - refrigerators, lights, cars, and even ham transceivers. These will be secure and will accommodate the requirements I describe above and many more in a way that allows us to simply expand the radios we have now with new cards. This stuff is starting to come to market now - I would suggest we are a year to two off from adding them to our devices. Then we need to convince the ham software developers to start adding support for them in all the flavors that already exist. I suspect that won’t be very difficult when they find a willing market. Good luck with your venture. I’d love to see it when it becomes available. We need to see things like this to interest hams, show them (and us) what is possible, advance the state of the art and even to expose vulnerabilities with current schemes so we can all do (and demand) better. - Jack, W6FB p.s. Yeah, security is THAT important. On Jul 19, 2015, at 2:40 PM, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: I have a prototype Ethernet interface running inside my K3 right now... simple replacement for the KIO3 board. I posted a couple of times suggesting it but was completely ignored so I build my own. It's just a pic with Ethernet capabilities and replaces the functions of the KIO3 completely and more. It will be available commercially soon... Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch - K9ZC Staunton, Illinois Owner - Operator Villa Grand Piton - J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Paul Christensen Sent: Sunday, July 19, 2015 2:24 PM To: elecraft@mailman.qth.net Subject: [Elecraft] K3/K3s Ethernet Interface This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all of it. The Holy Grail is an Ethernet interface that includes (optional) integrated RemoteRig hardware - just one interface board [e.g., KIO3E(thernet) board] that manages K3
Re: [Elecraft] K3/K3s Ethernet Interface
As a long time remote user I'll second that idea completely! 73, Olli Contest, DX radio projects: http://www.dh8bqa.de Am 20.07.2015 um 00:00 schrieb Paul Christensen: Jack, All valid points but take note of K9HZ's work as a start. Nevertheless, let's say native Ethernet control isn't worth the engineering effort. That should not preclude the integration of RemoteRig as an option into a K3/K3s. If I didn't care about the resale value of my K3 or RemoteRig, I could easily turn this into a weekend construction project and be up and running on Monday morning with an Ethernet cable hanging from the back of the K3. The RemoteRig board would come out of its enclosure then mount in the K3. It's just a matter of adding an RJ45 port, tapping +12V, internal audio, RS-232, PTT, key line, and ACC. The tapping of RS232 and audio is not trivial but it is completely manageable. While this adds little additional operational utility than it does now, it significantly cleans up K3 cabling with RemoteRig. No change is needed at the client end for use with the K3 mini. For K3 clients, a similar integration could accomplished or kept as it is now with external cabling. Of course, there must be enough demand from remote users to make it worthwhile as well as cooperation from Microbit. Paul, W9AC Sent from my iPhone6 On Jul 19, 2015, at 4:56 PM, Jack Brindle jackbrin...@me.com wrote: Paul; What is your proposal for the host-side interface? Pretty much all host programs these days use a serial interface. We usually use this through a USB-Serial adapter or through built-in serial ports, which are rapidly disappearing. To make this viable we would need drivers for all major platforms that implement a serial port driver interface to ethernet. Or, the host programs will need to be modified. There is a lot of work needed to make this suggestion viable, both on the host and radio sides. This is the fact same reason we still use serial interfaces for our rigs instead of true USB interface. Put forth a good proposal and let it be considered. Without that work (whoever does it), ethernet hardware isn’t very useful. - Jack, W6FB p.s., no, this isn’t a flame, but a challenge. Let’s get the whole thing viable, then we will take a good look at implementing it on all sides. On Jul 19, 2015, at 12:24 PM, Paul Christensen w...@arrl.net wrote: This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all of it. The Holy Grail is an Ethernet interface that includes (optional) integrated RemoteRig hardware - just one interface board [e.g., KIO3E(thernet) board] that manages K3 Ethernet connectivity with or without RemoteRig attributes. Don't need Ethernet? Then don't get the board. Since the RemoteRig hardware is mature and consumes little circuit board space and DC current, perhaps it would be worth opening up a discussion with RemoteRig's designer since Elecraft already has a close relationship with Microbit.I know rear panel real estate is a concern, so it won't be easy to add yet another connector without adversely affecting other connectivity. Thoughts? Paul, W9AC
Re: [Elecraft] K3/K3s Ethernet Interface
Radio protocols are bi-directional ASCII connections. They are usually implemented over serial ports, but there is no reason why they wouldn’t work over Telnet or ssh. Outside of amateur radio, I’ve only used a serial connection once in the past 20 years. That was hooking a console to an HP-UX server to get the networking set up. wunder K6WRU CM87wj http://observer.wunderwood.org/ (my blog) On Jul 19, 2015, at 4:56 PM, Jack Brindle jackbrin...@me.com wrote: Paul; What is your proposal for the host-side interface? Pretty much all host programs these days use a serial interface. We usually use this through a USB-Serial adapter or through built-in serial ports, which are rapidly disappearing. To make this viable we would need drivers for all major platforms that implement a serial port driver interface to ethernet. Or, the host programs will need to be modified. There is a lot of work needed to make this suggestion viable, both on the host and radio sides. This is the fact same reason we still use serial interfaces for our rigs instead of true USB interface. Put forth a good proposal and let it be considered. Without that work (whoever does it), ethernet hardware isn’t very useful. - Jack, W6FB p.s., no, this isn’t a flame, but a challenge. Let’s get the whole thing viable, then we will take a good look at implementing it on all sides. On Jul 19, 2015, at 12:24 PM, Paul Christensen w...@arrl.net wrote: This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all of it. The Holy Grail is an Ethernet interface that includes (optional) integrated RemoteRig hardware - just one interface board [e.g., KIO3E(thernet) board] that manages K3 Ethernet connectivity with or without RemoteRig attributes. Don't need Ethernet? Then don't get the board. Since the RemoteRig hardware is mature and consumes little circuit board space and DC current, perhaps it would be worth opening up a discussion with RemoteRig's designer since Elecraft already has a close relationship with Microbit.I know rear panel real estate is a concern, so it won't be easy to add yet another connector without adversely affecting other connectivity. Thoughts? Paul, W9AC __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to jackbrin...@me.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to wun...@wunderwood.org __ Elecraft mailing list Home:
Re: [Elecraft] K3/K3s Ethernet Interface
Paul; What is your proposal for the host-side interface? Pretty much all host programs these days use a serial interface. We usually use this through a USB-Serial adapter or through built-in serial ports, which are rapidly disappearing. To make this viable we would need drivers for all major platforms that implement a serial port driver interface to ethernet. Or, the host programs will need to be modified. There is a lot of work needed to make this suggestion viable, both on the host and radio sides. This is the fact same reason we still use serial interfaces for our rigs instead of true USB interface. Put forth a good proposal and let it be considered. Without that work (whoever does it), ethernet hardware isn’t very useful. - Jack, W6FB p.s., no, this isn’t a flame, but a challenge. Let’s get the whole thing viable, then we will take a good look at implementing it on all sides. On Jul 19, 2015, at 12:24 PM, Paul Christensen w...@arrl.net wrote: This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all of it. The Holy Grail is an Ethernet interface that includes (optional) integrated RemoteRig hardware - just one interface board [e.g., KIO3E(thernet) board] that manages K3 Ethernet connectivity with or without RemoteRig attributes. Don't need Ethernet? Then don't get the board. Since the RemoteRig hardware is mature and consumes little circuit board space and DC current, perhaps it would be worth opening up a discussion with RemoteRig's designer since Elecraft already has a close relationship with Microbit.I know rear panel real estate is a concern, so it won't be easy to add yet another connector without adversely affecting other connectivity. Thoughts? Paul, W9AC __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to jackbrin...@me.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3/K3s Ethernet Interface
Indeed, and yet it's called wireless. A non-ham visitor once asked me, How do you keep track of all the wires? I replied, It works right now, I don't ever touch it. 73, Fred K6DGW - Northern California Contest Club - CU in the 50th Running of the Cal QSO Party 3-4 Oct 2015 - www.cqp.org On 7/19/2015 12:24 PM, Paul Christensen wrote: Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3/K3s Ethernet Interface
I ordered the K3S to replace my K3, partially for the cable clean up. I've stopped using the Y cables as they contribute to the tangle. I prefer to run over to a breakout panel with modules on DIN rails from www.winford.com. 73 jim ab3cv __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
[Elecraft] K3/K3s Ethernet Interface
This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all of it. The Holy Grail is an Ethernet interface that includes (optional) integrated RemoteRig hardware - just one interface board [e.g., KIO3E(thernet) board] that manages K3 Ethernet connectivity with or without RemoteRig attributes. Don't need Ethernet? Then don't get the board. Since the RemoteRig hardware is mature and consumes little circuit board space and DC current, perhaps it would be worth opening up a discussion with RemoteRig's designer since Elecraft already has a close relationship with Microbit.I know rear panel real estate is a concern, so it won't be easy to add yet another connector without adversely affecting other connectivity. Thoughts? Paul, W9AC __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3/K3s Ethernet Interface
On 19 July 2015 23:40:51 CEST, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: I have a prototype Ethernet interface running inside my K3 right now... simple replacement for the KIO3 board. I posted a couple of times suggesting it but was completely ignored so I build my own. It's just a pic with Ethernet capabilities and replaces the functions of the KIO3 completely and more. It will be available commercially soon... Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch - K9ZC Staunton, Illinois Owner - Operator Villa Grand Piton - J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Paul Christensen Sent: Sunday, July 19, 2015 2:24 PM To: elecraft@mailman.qth.net Subject: [Elecraft] K3/K3s Ethernet Interface This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all of it. The Holy Grail is an Ethernet interface that includes (optional) integrated RemoteRig hardware - just one interface board [e.g., KIO3E(thernet) board] that manages K3 Ethernet connectivity with or without RemoteRig attributes. Don't need Ethernet? Then don't get the board. Since the RemoteRig hardware is mature and consumes little circuit board space and DC current, perhaps it would be worth opening up a discussion with RemoteRig's designer since Elecraft already has a close relationship with Microbit.I know rear panel real estate is a concern, so it won't be easy to add yet another connector without adversely affecting other connectivity. Thoughts? Paul, W9AC __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to b...@wjschmidt.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to p...@tippete.net William, What does it need on the control computer side? Will it be totally transparent to existing applications, k3util, fldigi, hamlib and so on? Does it require a specific operating system? Does it supports firmware uploads to the radio? Pf -- Pierfrancesco Caci __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] K3/K3s Ethernet Interface
Yes you can use it one of two ways... in TCP mode, there is a small driver loaded on your PC that creates a pseudo RS232 port on the computer that all your existing software connects to. Your software thinks it's talking to your radio via RS232... but really that is an emulation that gets ported over the Ethernet to the radio (where the Ethernet to RS232 server is) and deconstructed into RS232 (RXD and TXD) with DTR and RTS for keying. Your computer can be right next to your radio or half way around the world and the radio will never know the difference. Latency is not a problem. Second mode is WEB server where the radio is emulated in web pages in the onboard web server (eg web page looks like the radio). You can change any parameter in the setup or knob on the radio that you could via RS232. No security is provided. Nor is there with the FLEX, Ten-tec, or any other radio that has an Ethernet connection currently. I just use a Netgear firewall and VPN through it securely. Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch – K9ZC Staunton, Illinois Owner – Operator Villa Grand Piton – J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Pierfrancesco Caci [mailto:p...@tippete.net] Sent: Monday, July 20, 2015 12:35 AM To: b...@wjschmidt.com; 'Paul Christensen'; elecraft@mailman.qth.net Subject: Re: [Elecraft] K3/K3s Ethernet Interface On 19 July 2015 23:40:51 CEST, Dr. William J. Schmidt, II b...@wjschmidt.com wrote: I have a prototype Ethernet interface running inside my K3 right now... simple replacement for the KIO3 board. I posted a couple of times suggesting it but was completely ignored so I build my own. It's just a pic with Ethernet capabilities and replaces the functions of the KIO3 completely and more. It will be available commercially soon... Dr. William J. Schmidt - K9HZ J68HZ 8P6HK ZF2HZ PJ4/K9HZ VP5/K9HZ PJ2/K9HZ Owner - Operator Big Signal Ranch - K9ZC Staunton, Illinois Owner - Operator Villa Grand Piton - J68HZ Soufriere, St. Lucia W.I. Rent it: www.VillaGrandPiton.com email: b...@wjschmidt.com -Original Message- From: Elecraft [mailto:elecraft-boun...@mailman.qth.net] On Behalf Of Paul Christensen Sent: Sunday, July 19, 2015 2:24 PM To: elecraft@mailman.qth.net Subject: [Elecraft] K3/K3s Ethernet Interface This inquiry is directed to both the Elecraft leadership team as well as K3/K3s owners who may have an interest in native Ethernet connectivity. In searching through the list archives, I noted that some K3 owners had previously expressed an interest in an Ethernet option - and some owners have been disappointed that the new K3s and KIO3B board does not include Ethernet connectivity. A bit of background: for the past few months, N4CC and I have been operating a remote Internet station that's located near the FL/GA state line. Our setup includes a K3 and RemoteRig at the remote site and either a K3 or K3-mini at the control locations. Since the installation, we've experienced almost no operating trouble and any issues that have developed are managed remotely though direct and back-door network access points. Last week, I made some internal changes to the K3 and also added an external USB data interface device for RTTY. What's apparent is that cable management is getting way out of control. To gain inside access to the K3 almost requires a meditation exercise before going in. Consider that a PR6 is mounted to the back of the K3. The rear of the K3 is an absolute rat's nest of cabling. With the RemoteRig and PR6, It was bad enough before the inclusion of the external USB sound car/interface, but now it's bordering on ridiculous. Moreover, RemoteRig does not allow clean access to the K3's ACC DB-15 connector for other purposes such as FSK keying. Sure, the connector can be opened to access pins, but it requires a wiring break-out, leading to yet a further rat's nest of cabling. To help deal with the cabling issues, I am replacing the external PR6 with the new KXVB3 board. Next, a KIO3B board will be added when it's available to existing K3 owners. That should eliminate the external sound card interface and clear up much of the cabling mess, but not all of it. The Holy Grail is an Ethernet interface that includes (optional) integrated RemoteRig hardware - just one interface board [e.g., KIO3E(thernet) board] that manages K3 Ethernet connectivity with or without RemoteRig attributes. Don't need Ethernet? Then don't get the board. Since the RemoteRig hardware is mature and consumes little circuit board space and DC current, perhaps it would be worth opening up a discussion with RemoteRig's designer since Elecraft already has a close relationship with Microbit.I know rear panel real estate is a concern, so it won't be easy to add yet another connector without adversely
