KiwiSDR designer here. Thanks Massdrop for offering people a great price. Always nice to see a little capitalism in action (although everyone seems to be making money except me, lol). Happy to answer any questions. Also, please check the "wall of text" at kiwisdr.com and forum at http://valentfx.com/forums/#/categories/kiwisdr-discussion
Regards,
John, ZL/KF6VO
RavenIIYeah, I probably shouldn't have said that. Everything is fine. R&D costs are covered. Open source contributors are being compensated. There's money for the placement program. Seeed seems happy and is putting real effort into expanding the marketing. I'm happy to give a good chunk of the profits to them so I don't have to worry about manufacturing, logistics, distribution, ... I can spend my time fixing the software, adding features, doing support. Stuff I should be doing.
shaneshortI don't know much about ADS-B, but doesn't it operate at 1090 MHz or something? The Kiwi is a "shortwave" SDR with a top frequency of 30 MHz (32 with degraded performance). You could use a downconverter I suppose. But aren't there already complete solutions using an inexpensive RTL-SDR plus a Beagle or R-Pi? I'm not sure what advantage a Kiwi would have for ADS-B.
[edit] I should add that there have been requests for high-resolution tagging of the mono audio stream data and (future) IQ output stream with GPS timestamps. Presumably for use by downstream applications. Applications typically use a program that listens to the audio output of the browser via a "virtual audio cable" adapter of some sort. It is also possible to write "extensions" for KiwiSDR where you can load a small program into the server and/or browser to do custom processing (existing ones are under the "extensions" menu in the user interface). The complete list of all Kiwi bugs and wishes is here: http://kiwisdr.com/bugs/
Regards, John, ZL/KF6VO