Setting up my shack with RemoteHams and having significant latency problems with my Adalm-Pluto SDR setup. The RCForb client is connecting fine to my remote base, but I'm seeing 200-300ms delay during SSB operation which makes real-time QSOs challenging. RemoteHams server and RCForb Client software provides the capability to easily remotely control a ham radio station including an amplifier, antenna rotator, and switches. The RCForb client software integrates with popular logging programs and includes a keyboard keyer and DX cluster.

My setup: Raspberry Pi 4 running F1ATB's Remote SDR v5.0, Pluto connected via USB, 50Mbps fiber connection. Anyone else experience similar delays with this configuration?

Check your network buffer settings in the Remote SDR config. With Remote SDR, output on Ethernet or WiFi requires: 10 k samples / s * 2 bytes for the audio in reception · 10.24 k sample / s * 2 bytes for the received spectrum · 10 k sample / s * 2 bytes for transmit audio We are at less than 100 k bytes / s by adding the control data. There is therefore a reduction of approximately 100 in the communication speed required, which facilitates remote control via internet / ethernet without loss of quality through data compression. Try lowering the audio quality to reduce bandwidth requirements.

I had the same issue with my Pluto setup. The problem was my home router's QoS settings prioritizing other traffic. Make sure you configure your router to give priority to the Pi's traffic, especially UDP packets.

Are you using Chrome or Chromium browser? Chrome, Edge or Chromium web browser. Don't use Firefox. Firefox has known audio latency issues with WebRTC that can add substantial delay to your setup.