Hi Karsten,
I am exactly in the same situation as you. Have you solved? Thanks for replying.

73 de Vic, I2GPT

With the latest SDR3 Beta Ver 1.0.4 just released, I have been able to operate my SunSDR2 Dx Remotely with full RF output on SSB and CW.
This is a big improvement from Beta Ver 1.0.3.

Tom W3FRG

Tom W3FRG wrote:
I have quite the Problem with no Power @ TX on Remote with 1.0.4.
Today I tested connection from my office.



I´m using an Raspberry 3B+ with ERS-Server-Image.
Connection working well....latency/ping is drifting between 24 an 65ms






Im using E-Coder2 (ltest firmware) with Headset.
On TX Button stays red.....No Power....SWR doesnt show up.








Settings are the same like in my home-workstation.

Is my connection too slow?

Hello Volker.
Please also provide screenshots of the selected Mic.

Hi Rome,

Settings attached, but SoundCard is disabled.....because usage with E-Coder2







Settings are ok.....these are the same like my home-Workstation.
When I switch to Mic-PC i can see the red modulation on Spectrum, but PWR/SDR doesnt change....
With E-Coder2 i have remote no TX

You always should select some driver in this menu, for example MME.

Rome wrote:
Do I have to activate it?
I thought with E-Coder2 is SoundCard specific and i do not have to activate the "headphone Symbol"

Dear Karsten

I have read your article. I am experiencing the same phenomenon in my case. My current environment is

1.ERS (Raspberry PI3 Model B V1.2.
2. SunSDR2DX (Firm 86.8) + ESDR3 V1.0.4β
3. jtdx Ver 2.2.158-32A

The phenomena occurring are

1. reception is possible only with VBAudio, not with TCI interface
2. Sending is not possible (Tune is also not possible).
*No matter what I do, there is no transmit output.　

I gave up trying with Raspberry and built the ERS on Linux (Ubuntu 22.04) and was able to transmit normally with the audio settings as TCI. So I think this problem is specific to Raspberry, and I hope it will work on Raspberry somehow, because it is hard to run Linux all the time!

Hideki

Hello everyone.

I reported a while ago about not being able to send ERS with Raspberry PI 3 Model B. Today, I replaced the hardware with PI 4 Model B (4GB) and both send and receive work with TCI interface. Please find below a comparison of the models for your reference.

Model that could not transmit
Raspberry PI 3 Model B Processor: BCM2837 CPU: 1.2GHz Momory: 1GB

Models that worked properly for both sending and receiving
Raspberry PI 4 Model B Processor : BCM2711 CPU: 1.5GHz Memory: 4GB

The SD card was used for PI3, and was installed in PI4 as it is.

by Hideki

Hello Hideki JH3DRN and Vic I2GPT,
sorry for not answering for such a long time, but there were some other things beside ham radio I had to focus on and the time spending with ham radio was contesting and that is running so far without the sun!
I will make the test with the PI4 during the next weeks, maybe it is solved. I have a PC next to my sun because I modified a HLA300 so that I can run it remotely using Node Red. So the server for Node Red is running on that PC as well. Of course this would also run on a PI4. As I said I will try it and will pst the results.
Beside that I will but a remoterig setup next to the sun, running Audio in both ways and USb for the E-Coder. So fare I am not able to get under 3s Audio delay even Ping and Latency is ok, but the audio has always a big offset. In addition to that I need the transverter function to use the sun seriously. As fare as I know is that not implemented in ERS yet. So my set up will change in running a PC at the remote station and running Expert3 on that PC, using VNC for running the sun and remoterig for audio. A little bit back to the "old" remote days!
Karsten