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.
studentkra I just found a free slot and the stream continues. Can you check the log for a frequency of 198kHz and check if you get a "API: decided connection is OKAY" (or something) at around 13:10 UTC?
I can't say for sure this wasn't like this on previous versions, but I noticed the AGC action seemed quite slow (I couldn't find a place to adjust that) and it made the first syllable of strong signals to sound somewhat over driven. This was on some LSB amateur signals on 80m. I also noticed, perhaps related to the AGC action, that the peaks of stronger signals seemed to be driven into some distortion. I had none of the noise or compression features enabled.
"I'd also like to have the ability to edit the 24 band buttons, to have them go to frequencies of my choosing and have the labels reflect that."
I have been thinking how to integrate this, but I do not find an easy way.
As alternative solution I would suggest you to add your frequency as preset (via MEM) and name them something like "BAND x". This allows you to search on BAND and select it. The name will appear below.
If you click MEM again, your last search result will be shown, so you see all your "custom" BANDs.
Even more: your mode (like LSB, USB, ...) will be saved and selected too.
I listened again, ready to compare - but the app performed fine. Tried multiple things, all sounded well so have to put it down to some strange one time internet connection issue I guess.
Love the look and feel of this app, pretty cool Running on a Pixel 8a.
I am finding that any SDR that is using a proxy - such as my own 21263.proxy.kiwisdr.com does not connect. Although I can connect using the internal IP. My ISP (Starlink) does port block so using the proxy is a must. Yet any that are using an IP or ddns (for example) do work. User/config problem on my end or something I am missing? I am still doing the demo version, trying it out before we enjoy the coffee :)
@va3xa I will have a look at your server 21263.proxy.kiwisdr.com:8073
Update: your statement that QiwiQ cannot open ...proxy.kiwisdr.com servers seems not correct.
I tested several servers and they work, including your server: 21263.proxy.kiwisdr.com:8073
ps. perhaps you forgot to add the port number 8073
Update: you seem to be right: the server directory has recently changed and the proxy.kiwisdr.com addresses now seem to miss the port number (see comment of @jks later).
I will try to fix this as soon as possible in the next release. In the meanwhile, you can circumvent this by adding the server address manually as a custom server and add :8073 to the address.
@XPloRR ahhhh, that's it! I was using the search feature when gives us the proxy address but does not add the 8073. Good one for users to be aware of, by default it is not added in the kiwisdr proxy addresses in the database.
Thanks, I figured it was at least part user problem :)
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.
Comments
@XPloRR Hi. Perhaps this is because access is denied to non-Kiwi applications.
Number of simultaneous channels available for connection by non-Kiwi apps ==> none
Ok sounds plausible, but how should QiwiQ present itself then as a Kiwi app (since basically that is the purpose of QiwiQ)?
I don't know how this happens. Perhaps the server receives information from the client using JS navigator.userAgent.
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.
Update: I found the solution to be accepted as real Kiwi-app ...
[jks: Edited to remove explanation of how to bypass some of the bot countermeasures. We don't know who's reading here do we?]
Hi All
I am an app challenged KIWI owner !
I downloaded your cool app and I like the interface for my phone.
I accessed a few kiwis and got the hang of it.
But when I logged into my Kiwi here on the island....I cannot get into the radio No audio,lights are on but no one is home.
OK,UPDATE...I HAD TWO RCV CHANNELS with users .I only allowed 2 public non password.
I logged out of my PC on the kiwi.
Got in ok this time with the app..but no audio .Waterfall is active,and squelch at 0 and volume at 52%.
So,I guess I'm still missing something?
Ron
Flores island,Azores
You can find out kiwi with a search FLORES
Thanks for any help🙂
@jks you are right to correct me. Excuse me, It was my mistake. I understand the purpose.
@NU6F can you send me your server address so I will have a (debugging) look at it.
ps. I am currently testing a new version to support legacy servers (version <= 1.690). Could be the reason. Let me have a look.
Update: if this is your server: http://22561.proxy.kiwisdr.com:8073/?f=10Mamnz10
I found your version is 1.822 and I have no problem receiving audio on your server.
@XPloRR , I temporarily allowed Non-Kiwi devices connections a few hours ago. You can check it. Software version 1.633.
@studentkra thank you. But I was testing with a new version that should present QiwiQ as a "real Kiwi app". Could you disable it again so I can test?
Yes. One moment.
Done.
studentkra I just found a free slot and the stream continues. Can you check the log for a frequency of 198kHz and check if you get a "API: decided connection is OKAY" (or something) at around 13:10 UTC?
I can not see any connections betwen 13:07 ~ 13:14 UTC
Can you give me your server address again, to make sure we talk the same server?
http://std.swl.su:8073
Sorry my mistake, was testing with another server.
Can you check the log for a frequency of 198kHz and check if you get a "API: decided connection is OKAY" (or something) at around 14:22 UTC?
Yes. API OKEY. Three connections. Two of them are two minutes long, one is about a minute long
My new version seems ok (will release soon after some more testing).
New version of QiwiQ released: 2.05.52
• Support for legacy servers (version <= 1.690)
• Fix while switching servers
• Fix offset bug on legacy servers
• Bug fixes + ui-improvements
Download at: https://bit.ly/3I49LfD
Feedback/bugs welcome!
comments on version.52
I can't say for sure this wasn't like this on previous versions, but I noticed the AGC action seemed quite slow (I couldn't find a place to adjust that) and it made the first syllable of strong signals to sound somewhat over driven. This was on some LSB amateur signals on 80m. I also noticed, perhaps related to the AGC action, that the peaks of stronger signals seemed to be driven into some distortion. I had none of the noise or compression features enabled.
Any ideas? Have others noticed this at all?
AGC has not been changed in the latest 5 versions.
The AGC parameters used are:
SET agc=1 hang=0 thresh=-100 slope=6 decay=1000 manGain=50
Perhaps @jks could advise to use other default AGC settings.
Those AGC settings are correct.
Please do direct side-by-side comparisons between QiwiQ and a browser-based Kiwi connection before making any subjective comments about AGC.
@ve6jy I come back to your earlier request:
"I'd also like to have the ability to edit the 24 band buttons, to have them go to frequencies of my choosing and have the labels reflect that."
I have been thinking how to integrate this, but I do not find an easy way.
As alternative solution I would suggest you to add your frequency as preset (via MEM) and name them something like "BAND x". This allows you to search on BAND and select it. The name will appear below.
If you click MEM again, your last search result will be shown, so you see all your "custom" BANDs.
Even more: your mode (like LSB, USB, ...) will be saved and selected too.
I listened again, ready to compare - but the app performed fine. Tried multiple things, all sounded well so have to put it down to some strange one time internet connection issue I guess.
Love the look and feel of this app, pretty cool Running on a Pixel 8a.
I am finding that any SDR that is using a proxy - such as my own 21263.proxy.kiwisdr.com does not connect. Although I can connect using the internal IP. My ISP (Starlink) does port block so using the proxy is a must. Yet any that are using an IP or ddns (for example) do work. User/config problem on my end or something I am missing? I am still doing the demo version, trying it out before we enjoy the coffee :)
Scott
curve ball time - iOS app :-)
@va3xa I will have a look at your server 21263.proxy.kiwisdr.com:8073
Update: your statement that QiwiQ cannot open ...proxy.kiwisdr.com servers seems not correct.
I tested several servers and they work, including your server: 21263.proxy.kiwisdr.com:8073
ps. perhaps you forgot to add the port number 8073
Update: you seem to be right: the server directory has recently changed and the proxy.kiwisdr.com addresses now seem to miss the port number (see comment of @jks later).
I will try to fix this as soon as possible in the next release. In the meanwhile, you can circumvent this by adding the server address manually as a custom server and add :8073 to the address.
@jks meta-question:
Since I do not have this thread constantly open, I have set e-mail notifications,
but I do not receive notifications via e-mail. What is the problem?
Below are my settings:
@XPloRR ahhhh, that's it! I was using the search feature when gives us the proxy address but does not add the 8073. Good one for users to be aware of, by default it is not added in the kiwisdr proxy addresses in the database.
Thanks, I figured it was at least part user problem :)
Scott
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.