Can we have more info on using the Ecoder?
Can the two jacks on the vertical end under the knobs be identified? They are not marked nor is there any info anywhere that I can find as to what these jacks are for!
I am looking for a jack for a foot switch as I use my SunSDR over my LAN and need a convenient way of keying the radio.
Tnx
Lloyd
VE3ERQ

Looking at the back edge, the one on the Left is for a key or keyer & the one on the Right is for as footswitch
Ray G3XLG

The E-Coder has 3 LED's. Left LED is Green and is PWR. Middle LED is Red and is obviously PTT. What is the Right LED? Anyone know?

On mine, the right LED is for RX2
Ray G3XLG

Yep, E-Coder (all HW versions) documentation is ... lets be polite ... unfinished. And yes, it is not even consistent and complete for ESDR2. Obviously, there is no documentation as yet for ESDR3 (due to its alpha state).

Also, there are few different HW finishing options even within same HW mainline. I do not think it is intentional, it is just what it is.

It is possible that your Coder has no indications (missing silk print) of back panel jacks:


then try to look at Coder's back - indication may be printed there:


As for LEDs. I believe currently those are functioning differently under ESDR2 and ESDR3 (on common reason).

Under current latest ESDR3 alpha, central LED (red) is TX; and left LED (green):

can be on by switching the following settings:


I have lodged feature request regarding E-Coder here, please feel free to add your suggestions: github.com/ExpertSDR3/ExpertSDR3-BUG-TRACKER/issues/79

My E-Coder also has no silkscreen for the rear connectors. I can take a photo but these things are quite minor if we can document these things. I would rather Roman and his team work on the software than deal with these things. Perhaps we can just have a community driven documentation for these things, either as a Wiki or some commonly editable document. Frankly, the information is not THAT hard once you know it, and it is finite. This could take a lot of pressure off the development team and let them focus on getting the main software progressing.

When I bought the SunSDR2DX, I said to myself - I can support this team of developers. I like their attitudes and dedication so I'm quite happy even with the work in progress. I do sense quite a bit of defensiveness among some of the old stalwarts here - not sure why but maybe due to some unpleasantries in the past. I think this is a great product and a fantastic team. You would never imagine being able to give ANY input to the software team at Yaesu, for example, so I count this as a great advantage. We can't always control how people react but we don't need to control how people react.

If we want to, I reckon we could write a manual for the E-Coder in two days.