The forum is read-only currently.



Last Active
  • first fan died... how long do these things last- what other cooling alternatives ?

    @la6lu that made me smile...
    I too had problems with the factory fan and replaced several with Clint's suggestion

    I've now replaced four fans with this alternative but have just recently had to replace one of the alternatives when it too started to get noisy at the remote, poorly climate-conditioned site. It gets both hot and cold at that remote site so maybe this is to be expected. If someone finds an even better substitute or can identify a good maintenance plan for these (change oil every 20k km?) I'd be interested. Maybe this is just going to be part of the cost of keeping a Kiwi running continuously...
  • KPH Kiwis down?

    Actually, I think the power has been on the whole time. The issue seems to be a poor quality router that loses its way and no one having access to help it out. There may be plans for a replacement but there is perhaps a little politics in that one. Perhaps Rob may be able to elaborate.
  • Running more than one instance ----audio management?

    I just run multiple tabs in a single browser, one tab/kiwi-receiver. That allows separate audio, squelch ... for each of the receivers.

    It's sometimes useful to do this on kiwis that differently located and experience varying and different propagation. One can pick the best, even run squelch and let the best one win. There can be a differential delay problem but that can be dealt with.

  • Rounded Frequency Set

    I'm finding that "it works sometimes". I managed to get it not work, QSYed to a ham band where it worked, fussed around after which it quit. Maybe someone else can figure out the conditions for (non)working.
  • KiwiSDR unable to login with SDR.HU [caused by new Comcast/Xfinity "advanced security" feature]

    FWIW, I had very similar symptoms when Comcast/Xfinity (US cable ISP) changed to a new on-line administration tool for my router. They 'kindly' added something that must be akin to an iptables entry at their gateway which flagged all the kiwi traffic as 'malicious' or a threat and blocked it. I got the same error as you. This seemed to come and go, per some algorithm that I couldn't discern. After several hours on the phone (with someone in the Phillipines) I found the sub-menu on the web site which let me revert the security settings to avoid them shutting down access.

    I don't know if this is related to your cause or not, but I thought it might be helpful.

    Glenn n6gn
  • Kiwi phase/frequency stability & Ebnaut decoding

    I haven't documented the kiwiSDR onboard GPS performance but I have examined it, particularly in comparison to use of the Kiwi with an external clock. You can do the same by comparing two of my kiwis, one with a Bodnar GPSDO which generally appears to be better than 1 ppb and to not limit the phase noise performance of the kiwi with another using the on-board GPS reference.
    Bodnar referenced Kiwi
    on-board kiwi GPS
    are both looking at US NIST LOS/"groundwave" signals transmitted from less than 20 km distant.
    This may not be entirely satisfactory since the on-board kiwi's GPS antenna is outdoors but not very well located.
  • Suggestion, a change to the auto scaling in waterfall, to add 5 to the min result

    I think many of us find the low end not dark enough and routinely adjust it to dark blue. jks has mentioned this too, I think.
  • W/F and SND Bad Params

    In a kiwi itself rather than my router, after trying it with FORWARD, I ran:
    iptables -I INPUT -s -j DROP
    iptables -I INPUT -s -j DROP
    since I'm trying to stop packets from two different offenders at the kiwi rather than from being forwarded by the router. This I followed with:


    so that it will (I hope) get restored upon reboot. Examining the results I get:

    root@kiwisdr:~# iptables -L
    Chain INPUT (policy ACCEPT)
    target prot opt source destination
    DROP all -- anywhere
    DROP all -- anywhere

    Chain FORWARD (policy ACCEPT)
    target prot opt source destination
    DROP all -- anywhere
    DROP all -- anywhere

    Chain OUTPUT (policy ACCEPT)
    target prot opt source destination

    I'm not familiar enough with iptables yet to know if this will be sufficient, perhaps only the INPUT rule is needed. Maybe someone who knows can suggest whether this is correct or whether there's a better way.
  • W/F and SND Bad Params

    The steps I gave before seem to have fixed the problem for me. I am not an expert in this area either but no one has yet commented that there is a better way. To accomplish the block I first logged into my kiwi as root. I did this using secure shell, ssh, on a Linux host but this is also possible from a Windows machine via PuTTy or similar. Using PuTTy, simply enter the address, port 22, and it should then ask you to OK the connection. After you do, it will ask you who you want to log in as. Answer 'root'. That should get you a command line prompt from the kiwi. Once logged in I executed three lines:

    iptables -I INPUT -s -j DROP
    iptables -I INPUT -s -j DROP

    There may be even easier ways but that's all I did and it seems to have worked, the log is no longer reporting these hits. Presumably these could start again from a different IP address and I would need to repeat one of the above first two commands with that address in place of the one shown.

    Glenn n6gn
  • Combining/Diplexing Antennas to Single Kiwi

    I have been working on exactly this for some time. I started with a variety of broadband approaches several years ago. A prototype was published by W6SFH in QST a couple of years ago. I've visited both short dipoles and loops as well as various FET/BJT approaches such as several iterations on the Trask design.
    My target has been to get to or very close to the "quiet rural" ITU noise floor with an antenna (system) that can cover the range of the kiwi. It turns out that with small antennas the limiting point is the same as that of the kiwi - upper HF. Although 'radiation resistance' and the associated signal&noise levels are dropping with increasing wavelength, the noise floor at these long wavelengths is rising faster so that allows a very small antenna to work well from LF-midHF. The problem is that to get to the ITU limit above ~14 MHz (or so) one needs to get rather close to KTB. This is not presently possible with available devices. For a dipole, the device that can provide the input Z (low capacity, high R) to avoid mismatch loss can not simultaneously handle the broadband onslaught of highlevel signals and very low noise floor. I have been able to achieve this with an OpAmp design but only VLF up to midHF.

    Lately I've been working on a hybrid passive/active approach just as you suggest. But to make this system work with a passive over an [octave] requires some complexity. The Q of a single dipole (around 7) is too high to avoid mismatch loss (see paper by Fano) that raises the effective noise floor. But there are techniques that can do this. For example, a biconical or modified-biconical can be built from wire and give only ~2 dB mismatch loss from 14-30 MHz (and above). It also appears to be possible to couple an active dipole with a passive one to get partial-hybrid, though not over an octave. With a suitable diplexer at, say, 12 MHz, one can combine the best of the active antenna performance with that of the passive and get to a suitably low noise floor.

    Presently I'm trying to understand the effects of ground/earth proximity and polarization better. I have kiwis outfitted with both active antennas and multiple V/H passive dipoles (with LNA) available should you like to investigate. The active dipoles are on N6GN/K3 and N6GN/K2 (a remote site) while orthogonal 21 MHz dipoles are at N6GN/K. All three have antenna switches so you can play around, though be cautioned that I'm always messing with things so there's no guarantee what you'll find. I try to keep the Antenna labels current but don't always succeed.
    Write me if interested in any particular part of this.

    Glenn n6gn