> Gerry, we realize that. I indicated that cooperation from Microbit is > necessary. The most efficient integration would require a redesign of their > board as well as Electaft's boards. > > There are any number of ideas that would result in better cable management > between RemoteRig and the K3. > > Paul, W9AC >
> Sent from my iPhone6 > >> On Jul 19, 2015, at 6:15 PM, Gerry Hull <ge...@w1ve.com> wrote: >> >> 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 >> >> >> >>> 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 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 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
