jks

About

Username
jks
Joined
Visits
32,331
Last Active
Roles
Member, Administrator, Moderator
Points
331
  • How do you use your SDR

    I'd also like to know how many people are reluctant to make their Kiwi public due to bandwidth consumption concerns. Either because their Internet service has a low monthly cap (several to tens of GB) or because the Kiwi doesn't yet have tools for displaying and throttling bandwidth use.

    WA2ZKD
  • 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
  • ipad iOS bandwidth adjustment [v1.67 touch events added]

    In the v1.67 release I added some touch event support. So now if you zoom in sufficiently you should be able to touch-drag on the passband edges to change the bandwidth. You can also drag across the frequency scale to move the passband smoothly. tapping anywhere will set the frequency. Dragging outside the frequency scale (waterfall, spectrum, etc.) will shift the waterfall.

    It doesn't work perfectly but it's a big improvement. Tested on iPad, iPhone, Android.

    WA2ZKDG8JNJ
  • ipad iOS bandwidth adjustment [v1.67 touch events added]

    In the v1.67 release I added some touch event support. So now if you zoom in sufficiently you should be able to touch-drag on the passband edges to change the bandwidth. You can also drag across the frequency scale to move the passband smoothly. tapping anywhere will set the frequency. Dragging outside the frequency scale (waterfall, spectrum, etc.) will shift the waterfall.

    It doesn't work perfectly but it's a big improvement. Tested on iPad, iPhone, Android.

    WA2ZKDG8JNJ
  • 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
  • Location Error when logging in [geolocation database errors]

    Oh, you mean the geo-location for your ip address that appears in the status window at the lower left. Yes, this happens on occasion. The Kiwi software has to connect to an external site to translate the ip address of the visiting user to their physical location. Occasionally the database of these external sites seem to get messed up. It should fix itself in a day or so.

    K7MT
  • 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
  • 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

    Quick comment about the GPS page.

     Bottom row:
    "acq" Acquisition state, "yes" is acquiring new sats, "paused" if active SDR connections prevent acquisition of new sats.
    "tracking" Number of sats being tracked and appearing in one of the 12 GPS channel slots.
    "good" Of the sats tracked, then number of those that are considered good enough to compute a solution from (min 4 for a solution).
    "fixes" Total number of GPS position and time fixes computed.
    "run" How long the GPS has been running (H:M:S)
    "TTFF" Time-To-First-Fix, how long it took to get the very first solution after startup.
    "ADC clock" The GPS-measured true frequency of the ADC clock (nom 66.666600 MHz) In parens after are the number of computed corrections.

    Channel display: (this is a 12-channel receiver currently)
    "acq" Shows which channel the acquisition process is working with.
    "PRN" Sat identifier.
    "SNR" Signal-to-Noise-Ratio at time of acquisition. Min 16 to begin tracking.
    "gain" Goes negative if RSSI > about 1500 and software attenuation needs to be applied.
    "hold" How many bits in the current frame, out of 300, have been decoded.
    "wdog" Watchdog that will timeout and free tracking channel if bits are not being decoded. Different timeout values depending on channel state.
    "err" U = tracking loop unlocked. P = parity error. Momentary errors are not necessarily a bad thing.
    "subframe" Colored when GPS subframe correctly received. Blinks grey when updated. Subframes 1-3 required for position solution.
    "novfl" Number of holding register overflows (a debugging aid).
    "RSSI" Relative Signal Strength Indicator. Above 250-350 means sat actually present. Above 1000 is an excellent signal.

    M0TAZ