It's all about the Software

KA1GJU wrote: ↑Tue Jan 26, 2021 6:09 pm So you will need a bank of 4K monitors to actually see something of value with 10, 20, 30 MHz bandwidth?

For my purposes, Kriss, 32-inch 1920x1080 is great for FM BC. It's the overall band status I need first, then activity in the "holes", then any abnormalities that suggest interesting propagation.

I would use 4k at that size. I've seen Console running on 60" 8k monitors...

Is anyone running a CloudSDR with SDR Console? I cannot connect to mine and assume I have a setup problem.

WReeve wrote: ↑Wed Jan 18, 2023 5:40 am Is anyone running a CloudSDR with SDR Console? I cannot connect to mine and assume I have a setup problem.

Post the logfile as an attachment.

Sorry for the delay.

I've attached the logfile for a single attempt at connecting to a CloudSDR at 10.0.0.120:50112.

Logfile attached for one connection attempt to a CloudSDR at 10.0.0.12:50112.

OK, what about firewalls? I assume your local net is 10.0.0.x?

Are you sure port 50112 is correct?

Yes, the application is allowed in the Windows Defender Firewall and, yes, the local net is 10.0.0.x, and, yes, the port 50112 is correct.

I use IP 10.0.0.120:50112 to connect to the radio using SpectraVue without problems.

Okay, problem solved. First, my router was handing out 10.0.0.120 to a Macbook Air, so I deleted that and reserved a new address 10.0.0.112 for the CloudSDR on port 50112.

Next, I had manually added the CloudSDR in SDR Console but that didn't work. I used the SDR Console Search function for RFSpace and it found both of my CloudSDR. I saved those and now can connect okay.

Good news