jks

About

Username
jks
Joined
Visits
29,909
Last Active
Roles
Member, Administrator, Moderator
Points
207
Location
Tauranga, New Zealand RF82ci
Callsign
ZL4VO/KF6VO
Additional information
KiwiSDR support email: support@kiwisdr.com
  • Problem with massive RFI after changing router

    Changing the external SMPS is fine. But there is another issue that is more difficult to deal with. The use of internal DC-to-DC converters (that are also SMPS) directly on the PCB of the device.

    These days it seems a lot more devices, including PC motherboards, are powered with higher voltage from the primary supply. Then high-efficiency "point of load" DC-to-DC converters are used right at the consuming load. In the case of your router the external SMPS is now 12V instead of 5V and there is almost certainly a 12V-to-3.3V (or even less) converter internally (chips don't run on 5V these days and in many cases don't run on 3.3V either except maybe for I/O).
    ka9qjohnk5mo
  • wifi connection and local time

    The "-s" in "curl -s" (silent mode) is preventing us from seeing any error message if the connection is failing.
    What happens if you do:
    ping 50.116.2.70
    versus
    ping kiwisdr.com

    I'll bet this is a problem with DNS not working with WiFi for some reason (router configuration problem?)
    f6bir
  • KiwiSDR production status and availability

    The build count has stabilized at 204. So Seeed seems to have built the promised 200 units plus a few spares.
    wb8cxo
  • KiwiSDR production status and availability

    I'm only guessing here, and I don't mean to show favoritism towards particular distributors, but my bet would be ML&S (UK) and WiMo (DE). I wouldn't order from Mouser (USA) until they show units in stock (they had an issue earlier in the year with not filling a large backorder in the correct queue order).

    As of this morning the total count of Kiwis that have been through factory final test since Aug 19 is 186. So depending on the delay shipping to the distributors we shouldn't have to wait much longer now.
    disco1954
  • AGC control

    Currently, when you connect with a browser, the default AGC threshold is -130 dB. In the past this default was -100 dB and there was disagreement about this choice and discussion about whether it needed to be automatically adjusted depending on passband etc. Remember that certain values in the UI (including the AGC values) are saved across connections via browser cookies. So what you see in the AGC tab of the control panel may not be the true default.

    Kiwiclient (kiwirecorder et al) allows you to turn AGC on and use a fixed set of parameter values (set in the Python code) or turn AGC off and set a manual gain, all via the --agc-gain (or -g) [gain] argument. The fixed values as defined in the file kiwiclient/kiwi/client.py are:
        def set_agc(self, on=False, hang=False, thresh=-100, slope=6, decay=1000, gain=50):
            self._send_message('SET agc=%d hang=%d thresh=%d slope=%d decay=%d manGain=%d' % (on, hang, thresh, slope, decay, gain))
    
    So Kiwiclient is using -100 dB as the threshold which is at odds with the current browser default. Although not with what some people may have it set to. There is for example no Kiwiclient --agc-threshold argument, but it would be trivial to add. If you peruse the code you will see other references to "thresholds" but those are for NBFM squelch and RSSI thresholds.
    HB9TMC