jks

About

Username
jks
Joined
Visits
36,719
Last Active
Roles
Member, Administrator, Moderator
Points
670
  • QiwiQ a KiwiSDR client for Android: looking for feedback, testers and comments

    Leaving off the ":8073" will only work if the client (web browser or QiwiQ) responds to an HTTP 302 or 308 redirect. That is, if a user requests xxx.proxy.kiwisdr.com it will receive a redirect to "xxx.proxy.kiwisdr.com:8073" from the proxy server on kiwisdr.com (i.e. it will be told to retry with the new URL). You might ask why I don't implement this using a URL rewrite instead of a redirect, but that's where the next paragraph comes in.

    Right now this is more of a shortcut convenience so you can leave off the ":8073". But soon I'm going to load balance the proxy service between two servers and responding to 302/308 will become mandatory. A reference to yyy.kiwisdr.com[:8073] will be redirected to yyy.proxy2.kiwisdr.com:8073 if yyy happens to be hosted on the secondary proxy server.

    You might have noticed I recently removed the ":8073" from any Kiwi proxy URLs shown on my.kiwisdr.com and rx.kiwisdr.com. And this is probably why this problem with QiwiQ is occurring now.

    Of course I don't remove the port number from any non-Kiwi-proxy URLs (e.g. zzz.ddns.net:807x) because those need to remain.

    Whatever HTTP package QiwiQ is using should have the redirect functionality someplace. This is a fundamental web standard. Might just be an issue of enabling or configuring something.

    va3xa
  • v1.823, 824

    An email I sent to the guy who requested SBAS support (which will be under development for some time). SBAS is Satellite Based Augmentation System. Geostationary satellites providing GPS location improvement data.

    So v1.824 of the Kiwi software has SBAS selection and tracking (with some problems). It's mostly so I could try it on Kiwi's in various locations and see the status of the received SBAS sats and what message types (MTs) they are receiving. So far I've only checked from here in NZ (122:SPAN/AU-NZ, 130:BDSBAS/China, 137:MSAS/Japan) and the UK (121,123,136:EGNOS/EU). There is no MT decoding other than tow/week from MT12 and almanac status info from MT17. Lots of work needed.


    To use, go to the admin GPS tab. Uncheck Navstar, QZSS, Galileo. Click SBAS "Select" button. Menu appears. Click "log msgs" entry. Re-select menu. Click "all" entry. After a while you should see SBAS entries in the channels with colors appearing in the "subframe" column if MTs are being seen. The subframe numbers don't correspond to MT numbers since there are 64 MTs. Currently the subframe number is just incremented and blinked when a new MT is detected.


    Once you know which SBAS sats you can hear you can use the "none" menu entry to clear the list and then select just the ones you want to search for (to speed up the search).


    There is a bug currently that enabling the SBAS mode breaks the regular Kiwi user connection realtime response (i.e. the audio breaks up etc). I'm trying to figure out why. No doubt related to the higher nav data rate of the SBAS sats.


    With "log msgs" selected you will see various messages in the admin log tab related to SBAS.

    Examples:

    S130 MTs seen: 0 2

    S137 MTs seen: 2 7 9 10 18 26 28 63

    S122 MTs seen: 0 1 3 4 7 9 10 12 17 18 25 26 27 62

    S137 MT17 status: #0 S137 ranging=0 corrections=1 integrity=1 service=MSAS

    S137 MT17 status: #1 S129 ranging=0 corrections=1 integrity=1 service=MSAS


    The "S" indicator in the status column of the GPS tab:

    Blue: An MT0 was seen indicating sat should not be used for high-precision safety-of-life applications (e.g. aircraft landings)

    Green: MT0 not seen (S137 MSAS/Japan is an example of this)


    Good introduction: https://sgu4823.wordpress.com/wp-content/uploads/2012/11/l4-2_sbas_signal.pdf

    HB9TMC
  • v1.823, 824

    From the CHANGE_LOG file:

    v1.823 November 16, 2025

      DX label frequency list menus:

        When click-holding on a DX label a menu will now appear if there are multiple labels that

        have the same label text. The menu allows the frequencies of these multiple labels to be

        selected directly. This works for all the label databases: stored, EiBi and community.

       

        Example: Click-hold on the 10 MHz WWVH/WWV label and a menu with all the WWV frequencies

        (2.5, 5, 10, 15, 20 MHz) appears. A menu entry "open ext" will be shown if a label has an

        associated extension. If a label only has a single frequency (e.g. WWVB, DCF77) click-holding

        will immediately open the extension (if any). Type 'h' with the cursor in the label area for

        a complete description.


      Updated to EiBi-B25 database. (thanks MeolsKopite)


      Proxy service: The proxy service client (frpc) is now managed in its own process such that it

      will better respond to timeout / restarts when the Kiwi restarts faster then the network router.

      For example after a power failure.

       

      When the current frequency is exactly between adjacent or overlapping bands the frequency step

      buttons now make more sense. Example: Current frequency is 7300 kHz when in ITU R2 (Americas)

      mode where the 40m amateur band ends, and the 41m broadcast band begins, at 7300.

      Previously the leftmost "-" step button (or 'alt-j' shortcut key) would step down -5 kHz into

      the amateur band instead of -1 kHz as it should. (thanks Steffen)

       

      Admin GPS tab:

        Checkbox "Acquire if Kiwi busy?" now defaults to checked (true) for a new Kiwi run for the

        first time. This change will not disturb any change to the setting you may have made using

        the admin interface. (thanks NU6F)

         

        Added SBAS satellites for development purposes. No SBAS corrections are currently done.

       

      TDoA: Changed timeout value so message "Timeout: excessive runtime" will appear instead of the

      more obscure "Protocol timeout" when the TDoA algorithm runs too long.

       

      Added IP address to the "denied connection" log messages triggered by bots. (thanks F5LFE)


    nitroengineHB9TMCTremolatjimjackiiF5LFEG4ZFEstudentkra
  • EibiSpace B25 Stored DX Labels CSV file

    Okay, thank you for the changes.

    I see as of this morning Eike has made an official B25 release on eibispace.de. So I will get that into the next software release.

    HolgerMeolsKopite
  • QiwiQ a KiwiSDR client for Android: looking for feedback, testers and comments

    So I was wrong about the "too_busy=N" message (I can't remember how this stuff works anymore without looking at the code). "N" in this case is a count of the number of available channels. But N is context dependent.

    In the case of a non-Kiwi app connecting @studentkra is correct that this will be count of the non-Kiwi UI channels the admin has configured. Which may be different from the actual number of free channels available to regular connections using the Kiwi UI. A lot of people clamp down on non-Kiwi apps due to the number of bot connections they see. Either allowing zero non-Kiwi channels or only a small number. Note there is bot identification/filtering on top of this restriction.

    So the question of how to flag QiwiQ as a valid connection, compared to the bots, is reasonable. I don't have a good answer currently. Probably some sort of public key identification scheme is needed. But can you imagine the hassle in implementing that. I don't have the time and a large part of the community doesn't stay updated to the latest release anyway, so wouldn't get any potential fix.

    studentkraXPloRR