jks
About
- Username
- jks
- Joined
- Visits
- 31,848
- Last Active
- Roles
- Member, Administrator, Moderator
- Points
- 314
Reactions
-
v1.696
-
Kiwisdr1 doesn’t boot up
This appears to mean a problem in the FPGA initializing process
No, that's not what LED #1 double-flashing every second means. That is the standard Debian/Linux heartbeat pattern, i.e. what Debian shows before the Kiwi software starts running (or fails to start). This should be clearly described in the operating info: http://kiwisdr.com/info/#id-leds
I haven't even released v1.696 yet that implements the new LED pattern that indicates FPGA initialization failure: http://kiwisdr.com/info/#id-fpga (update: v1.696 has been released).
Glad it's running again for you though.
-
Any plans to move to OpenWebRX Plus?
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.
-
SNR Measurement (timing) enhancement
-
SNR Measurement (timing) enhancement
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?
toNo
. Then refresh the page, then go to the console tab and clickConnect
. 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
-
Forum rules and etiquette
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.
-
Waterfall/Spec smearing when zoomed to WF14 on 4-channel mode [fixed in v1.695]
-
FT8 6m Autorun [fixed in v1.695]
-
v1.694 [hopefully a working version of the failed v1.691,692 update]
-
v1.694 [hopefully a working version of the failed v1.691,692 update]