The KiwiSDR 2 online store is open for orders! Please visit kiwisdr.nz

jks

About

Username
jks
Joined
Visits
29,019
Last Active
Roles
Member, Administrator, Moderator
Points
203
  • v1.387, 388, 389

    From the CHANGE_LOG file:
    v1.387  April 10, 2020
        Admin page control tab:
            By special request, added ability to limit number of simultaneous non-Kiwi API connections
                (e.g. kiwirecorder). This works in the same way (and overrides) the TDoA extension
                setting that limits the number of simultaneous TDoA connections.
        DX label edit:
            Passband frequencies can be entered using "k" and "M" suffixes for kHz and MHz.
            I.e. "2100" and "2.1k" are equivalent, as are "1200000", "1200k" and "1.2M".
            However subsequent display of the passband field is always in Hz.
            So after entering "-2.1k, 1.2M" on the next edit the field will display "-2100, 1200000" (Hz).
    
    G0LUJcathalferrisrz3dvp
  • v1.387, 388, 389

    From the CHANGE_LOG file:
    v1.387  April 10, 2020
        Admin page control tab:
            By special request, added ability to limit number of simultaneous non-Kiwi API connections
                (e.g. kiwirecorder). This works in the same way (and overrides) the TDoA extension
                setting that limits the number of simultaneous TDoA connections.
        DX label edit:
            Passband frequencies can be entered using "k" and "M" suffixes for kHz and MHz.
            I.e. "2100" and "2.1k" are equivalent, as are "1200000", "1200k" and "1.2M".
            However subsequent display of the passband field is always in Hz.
            So after entering "-2.1k, 1.2M" on the next edit the field will display "-2100, 1200000" (Hz).
    
    G0LUJcathalferrisrz3dvp
  • v1.387, 388, 389

    From the CHANGE_LOG file:
    v1.387  April 10, 2020
        Admin page control tab:
            By special request, added ability to limit number of simultaneous non-Kiwi API connections
                (e.g. kiwirecorder). This works in the same way (and overrides) the TDoA extension
                setting that limits the number of simultaneous TDoA connections.
        DX label edit:
            Passband frequencies can be entered using "k" and "M" suffixes for kHz and MHz.
            I.e. "2100" and "2.1k" are equivalent, as are "1200000", "1200k" and "1.2M".
            However subsequent display of the passband field is always in Hz.
            So after entering "-2.1k, 1.2M" on the next edit the field will display "-2100, 1200000" (Hz).
    
    G0LUJcathalferrisrz3dvp
  • 40m band European extent - not showing correctly, though the region is set? [fixed in v1.440]

    Yep. Currently the ITU region setting only has effect for defining the NDB band bar and the 80/75m band overlap (which has problems of its own). It is not used for 160m (Fstart), 40/41m, 30m (Fstop) etc.
    cathalferris
  • Problems after upgrade from 1.383 to 1.384 [fixed by restarting network equipment]

    Is this Kiwi available from the Internet so I could connect (I don't need any passwords) and take a look?
    "Being available" doesn't mean it has to be a publicly listed Kiwi. Only that port 8073 on your router is set to map to the Kiwi and that you can tell me your public ip address.

    Oh yes, and based on recent experience I guess we now have to ask you: is your ISP Comcast? :/

    Also, is there WiFi involved anywhere in the path between your Kiwi and the machine running the browser? Does the same thing happen on some other device like a tablet, cellphone etc?

    I know this sounds like entry-level tech support, but seriously, try power cycling all your network equipment. I used to have a WiFi bridge connection between my development Kiwis and my laptop due to the physical setup here. About twice a year my Internet router or the TP-Link bridge would lose its mind and the ping times randomly go to several seconds for no apparent reason. Power cycle fixed it, but only after half my hair had already been pulled out trying to find out what was wrong with my code. Needless to say I found a way to run an Ethernet cable.
    k5khk