Troubleshooting live scan devices

What to check when a live scan device won’t connect or the trace looks wrong.

“Invalid IP address” / “Enter a valid IPv4 address or hostname.” The address field needs a plain IPv4 address (e.g. 192.168.1.100) or hostname — no protocol prefix, no port in the address field (the Owon and bridge options have their own port fields).

“Device not connected” / “Please connect the device before saving” The dialog can’t reach the device at that address. Confirm the analyzer is powered, on the same network as your computer, and reachable (try pinging it). For network tinySAs, confirm the unit is in its network mode and note that only one client can talk to it at a time.

“Could not connect to the MRK16 at …” Same checks as above; also confirm the MRK16’s network interface is enabled and no other controller is holding the connection.

The Live button is red and no trace appears Red while not sweeping means the device is offline. Reopen the Live Scan Data Settings dialog to reconnect, or Disconnect and select it again.

The trace is a flat line around −70 dBm and ignores settings changes (tinySA) The device’s own configuration is corrupted. On the tinySA itself, run Config → More → Clear Config (default unlock code 1234); the device restarts with factory settings. Reconnect afterwards.

A USB tinySA isn’t detected by the desktop app The USB flow is legacy — the current integration is tinySA Ultra (Network) over the network, which is more reliable. If you must use USB: start SoundBase Desktop with the tinySA disconnected, open the live scan settings, and only then connect and power the device.

The live scan stopped when I opened Plot Settings That’s by design — opening the plot settings stops the sweep. Close the settings and start the scan again.

I can’t see the live scan controls at all They’re desktop-only and require SoundBase Pro (or a zone that already has a device assigned) plus edit permission. See the requirements in Connecting a live scan device.