jks

About

Username
jks
Joined
Visits
22,837
Last Active
Roles
Member, Administrator, Moderator
Points
203
  • release v1.72/73: WSPR decoder improvements, control panel hide button

    Strong signals often cause weaker "images" at different frequencies in the WSPR display. The underlying cause is still not understood. But now spots with the same callsign will only have the strongest one uploaded to prevent polluting the wsprnet.org database. You'll still see multiple spots in the WSPR viewer because they are displayed incrementally as they are decoded. But at the end only the strongest non-duplicates will be uploaded.

    A multi-pass scheme has been implemented to help decode weaker signals. After the first pass any remaining signals will be rerun through the decoder with increased effort parameters (that take more decoding time) until the full two minute decoding interval is exhausted. Previously decoding was stopped after only one pass.

    The main KiwiSDR control panel at the bottom right of the window finally has a "hide" button at the top right like the other panels. This should be helpful for iPad and other mobile device users.

    KA7USergeWA2ZKD
  • Help us test new feature: "auto add router NAT rule"

    WA2ZKD/KA7U: Interesting your routers require you to enable UPnP. Security feature I guess. Kinda defeats the purpose of lessening the setup burden.

    ic8pof: If you are seeing the message "NAT port mapping in local network firewall/router created" in the log then the next time you go to the network tab after restarting the server you should get the green message that says:
    Automatic add of NAT rule on firewall / router: succeeded
    You won't see the message immediately after changing the button from "no" to "yes". You have to restart the server first.

    UR5VIB: excellent point about router reboots. I had not considered that.

    G8JNJ: I'm not sure what you mean by "separate firewall rule didn't seem to load". The Kiwi only sends a single NAT rule (port forwarding) via UPnP. No other firewall related rules if those are required by your router. You would still have to configure those manually.


    UR5VIBSerge
  • Help us test new feature: "auto add router NAT rule"

    WA2ZKD/KA7U: Interesting your routers require you to enable UPnP. Security feature I guess. Kinda defeats the purpose of lessening the setup burden.

    ic8pof: If you are seeing the message "NAT port mapping in local network firewall/router created" in the log then the next time you go to the network tab after restarting the server you should get the green message that says:
    Automatic add of NAT rule on firewall / router: succeeded
    You won't see the message immediately after changing the button from "no" to "yes". You have to restart the server first.

    UR5VIB: excellent point about router reboots. I had not considered that.

    G8JNJ: I'm not sure what you mean by "separate firewall rule didn't seem to load". The Kiwi only sends a single NAT rule (port forwarding) via UPnP. No other firewall related rules if those are required by your router. You would still have to configure those manually.


    UR5VIBSerge
  • GPS Admin screen

    v1.60, to be released tomorrow, will fix a GPS bug that I finally understood today. Apparently, since v1.38 the GPS acquisition process has not been restarting after active users disconnect like it's supposed to. That will lead to the situation where the admin GPS page says "acq yes" (instead of "acq paused"), but there is no refresh icon shown in the "acq" column next to an incrementing PRN as is typically the case. The satellites that are already acquired and being tracked will be be fine until they drift out-of-range and are dropped. So eventually the GPS page will show nothing even though new satellites should be getting acquired.

    M0TAZWA2ZKDKA7U
  • GPS Admin screen

    v1.60, to be released tomorrow, will fix a GPS bug that I finally understood today. Apparently, since v1.38 the GPS acquisition process has not been restarting after active users disconnect like it's supposed to. That will lead to the situation where the admin GPS page says "acq yes" (instead of "acq paused"), but there is no refresh icon shown in the "acq" column next to an incrementing PRN as is typically the case. The satellites that are already acquired and being tracked will be be fine until they drift out-of-range and are dropped. So eventually the GPS page will show nothing even though new satellites should be getting acquired.

    M0TAZWA2ZKDKA7U