Home / SimpleHPSDR User Guide

Troubleshooting

No radio found, audio problems, power that doesn't match, and where the logs are.

No radio found

  • Check the radio is on and on this network, and try its address under "Or by address" in the radio picker.
  • The picker's Network help… button lists what a firewall must allow: UDP, radio ports 1024 to 1044 in both directions, for the StationEngine program.
  • Windows: answer yes when asked about StationEngine. If you said no, the picker offers to add the rule again when it finds nothing.
  • Mac: allow the Local Network prompt. If you dismissed it, turn SimpleHPSDR on in System Settings > Privacy & Security > Local Network.
  • If the radio shows IN USE, another program is controlling it. Close that program, or take over. A SimpleHPSDR (0.14 or later) on another computer then lets the radio go. If the other program keeps running, the take-over is refused: stop it on the computer where it runs, then connect.

"Getting ready for first use" won't finish

It's slow, not stuck: around 8 minutes on a fast computer and longer on an older one. If you quit, it carries on from where it stopped next time (on Windows it starts again). A Raspberry Pi doesn't need this step: its package brings the tuning ready-made.

The radio engine stopped

A window offers Restart engine, which reconnects with transmit off. It's worth keeping engine.log and engine.previous.log from the app's data folder for a bug report.

Audio or mic problems

Check Config > Audio: the Speaker output and Computer mic lists, and the status line under them. If you hear crackling on ASIO, use a larger buffer.

If you chose Radio speaker jack as the output, receive audio comes from the radio, not the computer, and Mon can't play.

ASIO won't stay selected (Windows)

If a driver fails, the app goes back to System audio and the status line on the Audio page says why. Most failures come from one of these:

  • Another program has the interface. Many ASIO drivers let only one program use them at a time. Close DAWs, other radio programs and anything else using the interface, then choose ASIO again.
  • Windows is using the interface too. If it's the Windows default playback or recording device, some drivers refuse to start. In Windows Sound settings, make another device the default, then choose ASIO again.
  • The interface is unplugged, switched off or asleep. Reconnect it and choose ASIO again.
  • The driver is 32-bit only, or was left behind when the interface was removed. The status says so. Install the maker's current 64-bit driver, or remove the old one.
  • The driver can't run at 48 kHz, which the radio needs. If its own settings lock another rate, open Driver panel and change it to 48 kHz.

If ASIO is selected but you hear nothing or the radio gets no mic, the channels are probably wrong. Speaker output and Computer mic list every output and input the interface has. Pick the ones your speakers and mic are actually plugged into.

ASIO4ALL and other generic drivers work, but use the interface's own driver when it has one. When the status says "Could not instantiate the selected ASIO driver", it adds a Windows check with an error code. Include that whole line in a bug report.

Weak or distorted receive

Check RFG: too much preamp near strong signals overloads the receiver. Try attenuation, and leave Auto ATT on.

Power doesn't match another meter

PWR is the radio's own meter and can read low, and everything set from it inherits that. Compare against a meter you trust, and use External meter on the PA page. If you ran Calibrate and power is higher than shown, press Reset to stock first. Keep drive low until it's sorted out, especially with an amplifier connected.

End of transmission cut off

Raise the PTT release delay in Config > TX Audio. The engine already holds transmit for the speech still in the chain, and this adds a short extra wait.

A click or thump on each unkey

With a relay-switched amplifier, raise RX resume delay a little in Config > Amp. It keeps receive audio quiet for a moment after you unkey.

VOX keys by itself, or won't let go

Sound from the speakers is reaching the mic. Use headphones. See VOX and Mon.

PS won't go green

Run the guided setup from the PS right-click. It starts from your radio's default HW peak, which clears a setting left over from earlier tries. If it still won't lock, the line on the PS right-click says why: the sample too strong or too weak, or the wrong feedback source.

Transmit stopped with a red banner

The banner says why: SWR, the transmit timeout, the band plan or an external fault. See When transmit stops by itself.

The Ulanzi Dial stopped working after an update

On a Mac, macOS has to be asked for its permissions again. See If the dial stops working after an update.

Firmware

Click the radio's name under the panadapter, then Firmware… in the radio picker. The loader is for Protocol 2 radios.

A failed flash can leave the radio needing recovery

Use only the file made for your exact radio, on a wired network, and don't turn anything off until it finishes.

Reporting a problem

Open an issue on GitHub with:

  • your SimpleHPSDR version, your system and your radio;
  • what you did and what happened;
  • engine.log and engine.previous.log from the app's data folder.

The Help menu's update check tells you whether you're on the newest version.