Before you begin: Identify the failed function and the last known working configuration.
New to the terms? Open the quick explanations.
- COM port
- A Windows serial interface identified by a number such as COM5. Use the interface assigned to the intended control function.
- CAT
- Computer-assisted transceiver control: commands such as tuning and mode changes. It is separate from RF protection and digital-mode audio.
- Driver / API
- Device-support software that lets Windows and an application communicate with the receiver. Requirements depend on the device and software version.
- Virtual COM port
- A software-created serial interface. It can form part of a deliberately configured sharing arrangement; it is not required for every basic setup.
Include Receiver Protection from the Start
Start with the Symptom: No Audio, Missing SDR, CAT or USB Faults
Choose the failing function before changing settings. These links take you to existing checks; they are not another installation sequence.
| What You Notice | Start Here |
|---|---|
| SDR receiver not found, or it will not start | Receiver discovery and device access. Check the receiver’s driver/API and Windows recognition separately from radio CAT. |
| A visible signal but no usable audio in SDR Console | Reception and audio checkout, then mode, receive filter and selected receiver channel. |
| The browser receiver is silent | Browser audio and remote-receiver checks. This is separate from your local SDR installation. |
| Missing or changed radio COM port | Radio-to-Windows USB connection. |
| CAT will not connect, or frequencies do not follow | CAT, Omni-Rig and shared COM-port checks. |
| USB disconnects, especially during transmission | USB stability and RFI checks. Stop transmitting if the fault appears during transmit operation and verify receiver protection before continuing. |
| PTT switching or receiver protection is uncertain | Protection and failure-state checklist, with the PTT wiring chapter. Software muting does not establish RF isolation. |
| It worked yesterday | Windows, software and configuration changes. Compare with the last working baseline. |
Keep the test small: record what changed, test one path with one application, and return to the known working setup before adding complexity.
Further guidance: SDRplay support, SDR Console USB guidance, External Radio control, and FlexRadio’s transmit-related RFI guidance. Apply model-specific instructions.
W3UJ Troubleshooting Guide — Find the Connection That Is Failing
Choose the topic that matches your problem. Follow the easy checks in order and change only one thing at a time.
First rule: Stop changing settings for a moment. A radio, SDR or COM port may be fine while a previous program still has the connection open. Save your work and test one connection at a time.
A Simple Startup Order
- Connect and power equipment. Use known-good USB data cables; allow Windows to recognize the radio and SDR.
- Check Device Manager. Under Ports (COM & LPT), record the transceiver CAT COM number. An SDR receiver may appear elsewhere and need no COM port.
- Start VSPE if your station uses it. Establish its physical/virtual port arrangement before applications that depend on those virtual ports.
- Start the CAT control layer. Configure or verify Omni-Rig if used; some applications start Omni-Rig automatically.
- Open SDR Console, WSJT-X or other software. Start with one program, verify its connection, then add the next.
This is a typical sequence, not a rule for every installation. Follow the actual dependencies in your station.
Is the COM Port Stuck Open?
Think of a physical COM port as a doorway. Usually only one application can hold it directly at a time. A virtual-port arrangement such as VSPE can share or redirect access when configured correctly. If the next application reports Access denied, Port busy, Cannot open port or a similar message:
- Stop CAT activity and close WSJT-X, SDR Console External Radio and other applications using that port.
- Use each program's Exit or Quit command. Check the Windows system tray: closing a window may only minimize it.
- After saving work, open Task Manager (Ctrl + Shift + Esc). If a known program remains running or is unresponsive, close it there; use End task only when necessary.
- Close VSPE after the programs using its virtual ports have exited. Check whether an Omni-Rig process remains active; do not terminate unrelated Windows services.
- Restart the applications in the intended order and test one CAT connection before opening another program.
Still stuck? Restart Windows, then verify the COM number again. A restart may release a lingering application handle; it does not fix a wrong driver, wrong COM number or mismatched serial settings. If the problem persists, try another USB port or cable and check Device Manager for errors.
Three Rules That Save Time
One change at a time: Do not change the baud rate, replace a DLL, reinstall drivers and alter VSPE simultaneously. Separate device discovery from CAT: SDR Console finding an SDRplay receiver is different from Omni-Rig controlling a transceiver. Record what works: Write down the radio model, physical and virtual COM numbers, baud rate, data bits, parity, stop bits, flow control and software versions.
Using AI as a Troubleshooting Assistant
AI tools such as ChatGPT can help explain error messages, suggest a logical test sequence, and translate technical instructions into beginner-friendly steps. Treat AI as a troubleshooting assistant, not a replacement for the manufacturer's instructions or a verified wiring diagram.
Tell AI Exactly What You Have and What Is Failing
- Identify your equipment: transceiver and SDR model, Windows version, and the software you are using (for example SDR Console, Omni-Rig, VSPE or WSJT-X).
- Describe the symptom: Is the device missing from Windows, missing from SDR Console's Radio Definitions, reporting a busy COM port, or failing CAT frequency tracking? Copy the exact error message if available.
- Provide the relevant settings: physical and virtual COM numbers, CAT baud rate, data bits, parity, stop bits, flow control, and software versions. A screenshot of Device Manager or the program's setup window may help.
- Ask for one check at a time: report the result before changing another setting. Keep a record of what you changed so you can undo it.
Example question to ask AI: "I have a Yaesu FT-991A connected to a Windows 11 PC. Device Manager shows COM5, but Omni-Rig says it cannot open the port. I also use VSPE and WSJT-X. Help me check whether another program has the port open. Give me one safe step at a time and explain what each result means."
Verify Advice Before Acting
AI can make mistakes or recommend settings intended for a different radio or software version. Confirm driver downloads, CAT pinouts, serial settings and SDR Switch/PTT wiring with the equipment manufacturer's documentation. Do not install unknown DLL files, change USB drivers indiscriminately, or transmit RF to test an unverified SDR protection path. Avoid sharing passwords, license keys, personal account details or other sensitive information in screenshots and logs.
Best use: Ask AI to help determine whether the failure is in Windows recognition, the SDR driver/API, the software's device selection, or CAT communication. Then follow the appropriate W3UJ troubleshooting topic below.
1. Radio to PC — USB & Windows COM Ports
| Common Problem | Easy Next Steps |
|---|---|
| Windows does not recognize my transceiver | Use a known-good USB data cable and a direct computer USB port. Install the manufacturer’s USB driver, following its installation instructions. Open Device Manager and reconnect the radio to see whether it appears. |
| The CAT COM port is missing or has changed | In Device Manager open Ports (COM & LPT). Reconnect the radio and record the assigned COM number. Some Yaesu radios expose more than one serial interface; identify the correct CAT port from the manufacturer’s documentation. |
| The radio connects but communication fails | Check the radio’s CAT menu and the settings actually used by your software: baud rate, data bits, parity, stop bits and flow control. Windows Device Manager → COM port → Properties → Port Settings is a useful reference, but many CAT applications override those defaults. |
| The USB connection disconnects unexpectedly | Try a different cable or port. For the relevant USB hub, check Device Manager → Universal Serial Bus controllers → Properties → Power Management, if offered, and consider clearing “Allow the computer to turn off this device to save power.” |
2. SDR Switch to SDR Receivers — Connections & Protection
| Common Problem | Easy Next Steps |
|---|---|
| The SDR is connected but receives nothing through the SDR Switch | With the transmitter disabled, trace the receive RF cable from antenna to SDR Switch and from its receiver output to the intended SDR input. Verify the correct ports and antenna selection; compare with the station diagram. |
| The SDR Switch does not change state when PTT is activated | Do not transmit RF. Verify switch power, the designated PTT/control connection and the expected switch indication or relay action using a no-RF control test. Follow the SDR Switch manufacturer’s wiring instructions. |
| The SDR disconnects or behaves strangely when transmitting | Stop transmitting until the receiver-protection path is verified. Check switch timing and PTT operation first; then investigate USB resets and possible RF coupling into computer cables. CAT control alone is not SDR transmit protection. |
Is the SDR Switch Changing State Correctly?
Test Your SDR Switch — N2EME’s five-step procedure → Use the continuity checks to compare unpowered, receive and PTT-activated states before troubleshooting the wider station.
Choose the right test instrument: multimeter, SWR/power meter or antenna analyzer →
3. Software Connecting to Radio or SDR — Device Discovery
| Common Problem | Easy Next Steps |
|---|---|
| SDR Console cannot find the SDRplay RSPdx-R2 | Open Select Radio, search for the supported SDR and create a Radio Definition. If it is not discovered, check the USB cable, Windows recognition, SDRplay API installation and SDR Console compatibility. Try SDRconnect to isolate the problem. |
| SDR Console sees the SDR but cannot start it | Close other SDR applications that may have the receiver open. Reconnect the SDR and restart SDR Console; then check the required manufacturer API/driver and the software version. |
| The RX888-MKII is missing after restarting Windows | Check USB cable, USB port and driver. At W3UJ, disconnecting and reconnecting the USB cable has sometimes helped. See the existing W3UJ RX888-MKII notes for the USB, Mix 31 ferrite and SDR Console “Random” observations, which are not universal requirements. |
| The software reports a device or USB error | Check Windows device recognition and manufacturer driver/API first. Test one application at a time; do not change DLL files, CAT settings and USB drivers simultaneously. |
RX-888 MKII: Check the Cypress FX3 Driver
Open Device Manager and follow the manufacturer’s Windows driver instructions. The guide describes an RX-888 appearing as WestBridge before its Cypress FX3 driver is installed, or as Cypress FX3 once the driver is present. Use the driver linked by that guide and follow its installation procedure. Device naming is one diagnostic clue; confirm recognition and actual reception afterward.
If the driver is installed but detection still fails, check the USB 3/SuperSpeed connection, cable capability, controller bandwidth and power requirements. A blue port does not rule out a USB 2 cable or an unsuitable hub. Compare the W3UJ RX-888 troubleshooting observations; reconnecting USB or checking “Random” is installation-specific, not a substitute for installing the driver.
NESDR / RTL-SDR: Check the Zadig Installation
Use Nooelec’s Windows instructions and Zadig for the correct RTL-SDR interface. Verify the device and USB ID before replacing a driver. Zadig is the installer utility, not the SDR operating application. Do not replace a Yaesu or SDRplay driver with this RTL-SDR procedure.
Receiver Discovery Example
SDR Console documentation: a real receiver-detection error example. Original source ↗
4. PC Software Controlling the Radio — CAT, Omni-Rig & VSPE
| Common Problem | Easy Next Steps |
|---|---|
| Omni-Rig will not connect to the transceiver | Confirm the radio model and CAT COM number. Compare the radio CAT menu with the serial settings actually applied by Omni-Rig: baud rate, data bits, parity, stop bits and flow control. An 8-N-2 configuration is an example, not a universal requirement. |
| Omni-Rig works by itself but fails when VSPE is added | Confirm which application opens the physical COM port and which uses the virtual port. Check the VSPE physical-port configuration and the port selected in Omni-Rig. Test one CAT program on the physical port first, then add VSPE and other software. |
| WSJT-X Test CAT fails | Open Settings → Radio and verify the rig model, CAT connection, port and serial settings. Close other software that may hold the physical COM port, or use the configured shared-port arrangement. |
| SDR Console and the transceiver do not follow frequency changes | First confirm the SDR receiver itself starts and receives. Then check SDR Console External Radio, Omni-Rig, the selected CAT COM port and synchronization settings. CAT tracking is separate from SDR device discovery. |
| It worked yesterday but not today | Recheck COM-port assignments, radio CAT settings, software conflicts and recent driver or Windows updates before reinstalling anything. |
5. USB Connection Problems & RFI — Random Disconnects
| Common Problem | Easy Next Steps |
|---|---|
| The COM port or SDR disappears randomly | Try a known-good USB data cable and a direct PC port. Look in Device Manager for disconnect/reconnect events. Check the relevant USB hub's Power Management setting, if offered. Avoid changing several things at once. |
| Everything works on receive but fails during transmit | Stop transmitting and first verify SDR Switch protection. Once protection is confirmed, investigate RF entering USB/control cables: cable routing, grounding arrangements and suitable ferrite common-mode suppression. A transmit-only failure can resemble a driver problem. |
| A USB hub or multiple devices behave unpredictably | Test the affected device directly on the PC. Check that the port or hub supports the device's required USB speed and power; reconnect devices one at a time. |
| Windows power saving may be interrupting USB | Device Manager → Universal Serial Bus controllers → relevant hub → Properties → Power Management, if available. Consider clearing “Allow the computer to turn off this device to save power.” Not all devices expose this setting. |
6. It Worked Yesterday — Windows & Software Changes
Keep the connections separate: Windows USB/COM recognition, SDR receiver drivers/APIs, SDR Switch RF/PTT protection, and transceiver CAT control are different systems. Fix the one that is failing before moving on.
Related resources: Beginner’s Guide • Software & Drivers / RX888-MKII notes • N2EME archived setup presentations.
Windows and Software Changes: Checks and Next Steps
| Common Problem | Easy Next Steps |
|---|---|
| CAT stopped after a restart | Check whether Windows assigned a different physical COM number. Compare it with the port configured in Omni-Rig, VSPE and WSJT-X. Close any application still holding the port. |
| SDR Console no longer finds or starts the SDR | Confirm Windows sees the device, then check the SDR Console Radio Definition and required receiver driver/API. Test with the manufacturer's SDR software when available. |
| A Windows, driver or SDR Console update preceded the failure | Record what changed. Check device status in Device Manager, software version compatibility and saved definitions before reinstalling. Use the manufacturer's current instructions; avoid random DLL substitutions. |
| The problem persists after closing everything | Use the Back to Basics clean-restart procedure. If still unsuccessful, test one device and one application at a time, document the exact error message and compare with your last working configuration. |
Related Operating and Build References
Software and Driver Links
Open the Software & Drivers directory for the SDR programs, device-support packages, CAT tools, and timing utilities referenced in these instructions.
Where next: Record the recovered working setup →
Based on W3UJ station documentation. Station examples describe this installation; consult model-specific documentation for your equipment. Sources and editorial scope.