Remote CW feature request

This appears to be a difficult problem in that latency is a killer. Do you send one dot or dash or buffer them and send several?

remoterig offers a solution today that I use, but it is pricey. It seems quite effective, however, I get good results on CW except in times of significant ISP congestion. That is when I resort to CWX. Keep in mind that while the receive side is technically easier, the "stutter" that congestion will cause on receive can be significant. There are times (only an hour or two a day, max) where I just have to give up. It mostly works very well, though, even in fierce pileups. I suspect those who prefer CW above 25 WPM will be less satsified than I am (the higher the speed, the tougher all of this gets).

I'm not sure that a really cheap solution will be satisfactory. we may require a cooperative solution with devices on the scale/cost of 50 to 100 dollars on each end (looking at raspberry pi at about 50 for a product with a case). Clearly, given what I gladly paid remoterig, there is money in a good solution (though remoterig does SSB as well as CW for that price and has a lot of configurability).

We should not expect a cheap solution here unless the latency of the 2.0 (or 1.5) solution is really unexpectedly outstanding (read: low bandwidth to the point latency takes care of it self, doubtful IMO).

In the short run, cleaning up and remotingCWX would make a lot more sense though it may not help your situation very much. A remote CWX would deal with latency better than trying to do dots and dashes individually.

Larry:  My latency is <1ms with 0 dropped packets.  The reason I decided to use a keyer is precisely to avoid latency issues and the vagaries of software keying and to solve the sidetone issue  I'm mostly interested in being able to conduct a CW QSO from my office to the 6500 in my ham shack and I'm not too worried about working CW over the internet, nor am I very worried about full QSK etc.  100-200 ms turnaround suits me fine.  I also considered using a AFSK scheme where you use the sidetone as a kind of AFSK source to drive CW from a DAX channel.  You already have VOX to turn the radio off and on.  Virtually every tablet has a MIC input but not every one has a serial input.  I expect some fancier solution will be needed to solve the internet issue.  In the mean time....

Paul  I have an old old 8 pin version of winkey serial which I was able to connect to my winkey USB using the k1el remote server, but I couldn't make it key the radio from remote.  I think there is an issue between that old chip's output code and the remote server/client instructions.  I think but it did prove the concept.  I went ahead and ordered a new USB 3 version but I suspect a pair of serial 2 versions @ $36 each would get the job done as well.  I'll check the side tome kit tnx for the hint

73 

Hello Lee,
I built a cheap solution, waiting for official remote cw key.
It seems very close to the feature you are asking for.

I am using it on my own vpn and up to 25 wpm I am not experiencing any issue.

All details are on my web pages http://iw7dmh.jimdo.com/remoting-idea...

Enzo  Very cool

why not just have a second 6000 program on the local computer decode the output from the remote 6000 program and send that data to a serial port then on to the key line of the 6300?

Just an update, I built Enzo's circuit and have installed it on my 6500 station.  It works extremely well.  I wrote a blog post regarding the experience  sdr-w9oy.blogspot.com and made a little demo video.  If you want to do some CW work with a paddle by the pool this is the way to go.  No need to even turn on the computer in the shack, its all self contained except for 5v and a ethernet connection.  I have less than $10 in the system.   Combine it with a $20 K1EL K16 keyer or whatever keyer you have laying around and you have a remote keyer that far outperforms the WinKey remote setup.  BRAVO Enzo!!

73  W9OY