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

2»

Comments

  • You are correct that on a mobile client there is no real use for an IQ mode button. However the SAM, SAU, SAL, SAS and QAM modes should be considered. Perhaps just SAM since the others are less frequently used. There is a real advantage to using synchronous AM decoding for weak AM signals.

    Just my opinion, but I think using red to outline active buttons has too little contrast. Maybe something like yellow would be better?

    F5AFY
  • edited September 8

    I consider replacing IQ with SAM then.

    Will see what I can change to make keys more visible, but want to keep the interface stylish, not cluttered with different colors.

    Another question: is there a method or socket to decode cw (similar to drm ext socket)? Any other suggestions are welcome.

    another question: my signal meter is now a value from 0 to 100. I found this formula on one of the kiwi demo files:

      smeter, = struct.unpack('>H', buffer(body[5:7]))

      rssi  = 0.1*smeter - 127

    My question: is this a calibrated value and is there a formula to convert it to a calibrated S-meter signal: S1-3-5-7-9+!0+20+40+60 ?

  • jksjks
    edited September 8

    The EXT socket you used to open DRM can be used to open any of the extensions. You just change ext_switch_to_client=X where X is the name of the extension as it appears in the extension menu on the Kiwi UI. As mentioned before, you can very easily use the browser debug window "network" tab to see exactly what socket command are being sent by the Kiwi Javascript client code -- commands that you will have to send yourself. This is much easier than reading the code to see what it's doing. Select the EXT socket and HTTP response tab.

    A lot extensions can run without any parameters needing to be set. E.g. the cw_decoder, cw_skimmer and FT8 extensions because their default parameters will just work. All you have to do is somehow display their decoding output. In the case of the cw decoders that means processing the cw_chars=... message. And ignoring messages like cw_plot and bar_pct if test mode is active. For FT8 just process the chars=... message.

    Send a close or stop and blur messages when done (varies by extension for historical reasons).

    You can use the test mode message to debug with to get a strong pre-recorded CW signal that will decode 100%. Similarly for FT8 mode. No tuning to an active CW/FT8 frequency required.

  • Thank you, I will have a close look at it to understand it first.

    The problem with the s-meter is solved, I will implement a standardized S-value. S1-3-5-7-9+10+20+40+60 (values above 9 will have to be read as S9+value), so S20 means S9 + 20 dB.

    Standardized S-meter will be ready in next release.

Sign In or Register to comment.