I have recently bought an E-Coder Plus and I have programmed it for use with my SunSDR2 DX. All is working OK - except using the keying port on the E-Coder is useless. The CW is great for the first few characters and then the keying stops totally - until you change from a dash to a dot or vice versa. It seems as if the software in the E-Coder simply cannot keep up, even at a slow speed. I have a big PC with plenty of memory and that is not the limitation. It is not an RFI issue as it still does the same with no RF output. I note that the E-Coder 2 has some upgraded CW facilities and I guess that it might be related to fixing the problem I am reporting here. The problem does not arise with the paddle connected direct to the SunSDR2 DX. It seems as if I should have waited to buy an E-Coder 2. Very disappointing. On the other hand I don't really want to use the internal keyer at all. I want to use my external memory keyer but that does not work very well (first character shortening after changeover to transmit) which Roman said was going to be fixed in a firmware update in June. Just 3 days to go or is the firmware update really V3 ?
I have now changed the connection from my PC to SunSDRD2 DX to be on my network. I have also now reconnected the E-Coder plus and all seems to be well with the keying. I do not know what the previous problem was but it seemed to be related to using only the direct ethernet connection between the PC and SunSDR2 DX. Anyway I would still like to be able to use the external keyer without the character shortening.