jks

From your description it certainly sounds like an open attenuator. Especially if you're getting the self-test patterns, just attenuated by 40 dB.

Please send an email to sales@kiwisdr.nz (note ".nz") requesting a repair. We're having to figure out some sort of formal solution to this problem since a significant number of people are asking.

By request: the list is now sorted in 0-30 MHz SNR order.

There is a new menu to select the alternate 1.8-30 MHz (HF) order.

From the CHANGE_LOG file:

Yeah, just a bug. Already fixed for the next release.

Thanks

This question is simply not valid. It doesn't take into account the architectures and evolution of the current Kiwi and owrx systems and how it is not possible to "move" between them. The Kiwi started with some owrx waterfall, sound and user interface Javascript code back in 2014-2016. But things diverged quickly from there.

owrx runs on a pc. And the Kiwi's Beagle + FPGA is not a pc. That's by design and the root of the issue.

Okay, that wasn't too difficult. Fix will be in the next release (v1.696). It will be a new file called ~/kiwi.config/opt.console.local

I turns out that setting is essentially bogus. You can override it easily. I didn't think it through carefully enough when implementing it.

Even if you're connected as admin from the Internet simply go to the "security" tab and set the switch that says Restrict console connections to the local network? to No. Then refresh the page, then go to the console tab and click Connect. It should now work.

The problem is that setting can't be in the admin interface. Otherwise it can always be defeated. This feature needs a setting similar to the one that disables the console tab entirely by creating a file called ~/kiwi.config/opt.no_console

See here: http://kiwisdr.com/info/#id-opt-dot

This is a private, non-public forum for discussing technical topics related to the genuine (original) KiwiSDR product. The forum monthly operating costs are funded out of the profits from selling KiwiSDRs.

We reserve the right to edit or remove your posts or to ban your participation. If you want to criticize our work that's fine. Just do it somewhere else please. We are all very busy and don't want to spend a lot of time managing chaos on the forum.

• New participants: Take some time to understand the product, the community, the ecosystem and the limitations that have evolved since the product introduction in 2016. The project authors do not have the resources or capabilities you might think they do.
• Don't ask support questions about non-genuine KiwiSDR devices. There are other support forums specifically for those devices. If you're not going to support us by buying our stuff you shouldn't be surprised when we don't reciprocate.
• No "low effort" posts. Search the forum and website FAQ for an answer before asking your question. 
• Don't complain about well known, long-standing technical limitations such as: audio latency, lack of https/TLS, run-as-root, spotting efficiency of the WSPR extension etc. We know all about these issues and most have been discussed for many years. They are either difficult to solve, have no solution or are way down on the priority list.
• Don't violate security "zero-day" rules. Don't report security vulnerabilities here or on Twitter. Send them to the support email instead.
• Don't attempt to explain what you think "open source" means. Everyone is wrong about that. Including me.

Thank you.

Thanks for reporting this.

It seems the rx4_wf4 FPGA file was incorrectly updated when the v1.692 changes were reapplied in v1.694. But I don't understand why that would of caused this problem. I'll have to go find out.

This will be fixed as part of v1.695

Yes, I can do that. Added to my infinite list of things to do..