Best Recent Content
-
QiwiQ a KiwiSDR client for Android: looking for feedback, testers and comments
-
EibiSpace B25 Stored DX Labels CSV file
-
EibiSpace B25 Stored DX Labels CSV file
Well, no.
First, this file is filled with dozens of illegal UTF-8 sequences. You can see the decoding failures in the browser's javascript console. They are mostly of the form e1 byte1 byte2, where the trailing two bytes are not valid UTF-8 continuation bytes beginning with the high-order bits 11. This is a symptom of improperly downloading files from eibispace.de. I had to learn this the hard way many years ago. You can't download files from there with the browser download function. You have to use wget plus some additional magic.
Second, I don't understand why you'd want to do this. We already have an integrated EiBi database. Yes, it's A25. I've been waiting for B25 to be released. I don't think this csv file is the official B25 release as eibispace.de only shows a 27 Sept update to A25 as being current.
The integrated EiBi database has a special filtering control panel that you don't get by uploading EiBi entries into the stored database. You lose that functionality which is important given that there are so many overlapping labels (more than 10 thousand).
But whatever I suppose..
-
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.
-
QiwiQ a KiwiSDR client for Android: looking for feedback, testers and comments
-
QiwiQ a KiwiSDR client for Android: looking for feedback, testers and comments
-
Help needed: DSP, SSB, Hilbert transforms, Octave language
-
MF WSPR
-
QiwiQ a KiwiSDR client for Android: looking for feedback, testers and comments
I should also mention, re your earlier query about VHF/UHF Kiwi, that a reason to detect and respond to dynamic changes in the offset is because it is possible for this to be set in the antenna switch configuration. So that a user connection could select an antenna that also switches a downconverter in/out-of-line. On the Kiwi UI this causes a page reload to correct the frequency scale and all the other places the new offset needs to be taken into account.
But in practice I don't think many Kiwi are setup this way. VHF/UHF operation seems to be a static setup rather than associated with an antenna configuration.
-
QiwiQ a KiwiSDR client for Android: looking for feedback, testers and comments
First of all I did not write the squelch code, so I can't say exactly how it works. But it was originally designed for the NBFM modes. So using it outside that context is perhaps a bit problematic. I think it tries to compare energy at and above typical voice frequencies and use that as a basis for squelching. So it probably isn't going to work at all on AM BCB signals where there are very few periods of silence.
It works well however on things like the digital bursts in the UK on e.g. 4037.5 kHz. In either USB or AM modes.



