Well that’s not good…
And sorry to hear about the way their support has been treating you. Would make me think twice about doing business with them.
ya know thats why I posted the IRC log, then they discovered I pasted it, Prog asked me what “right” I had to post a log from a public irc channel. Just shows you their mentality over there. A quick google search shows this is not their first time that attitude has show up. I just posted to be transparent to the community here to know what they are getting when dealing with them from a “support” perspective.
Sounds like someone above prog found the post and may have ‘expressed’ something 
I would recommend staying away from AirSpy mini for ADS-B as R820T2 gives better results and is cheaper. Even after pairing Mini with LNA4ALL amp the result were disappointing even though the output looks good on SDR# but the decoder is pretty s*** !.
I think if they can resolve the ADSB rejected errors it might be a lot better, but until then. I agree with you
There’s a whole world beyond cheap dongles which works quite differently. Fixable frames are passed by our decoder to the plotting software for statistics and/or some advanced recovery, just like high end receivers like the SBS-3 and Beast. If you only need CRC validated frames, use the strict mode. It will let you believe the reception is perfect, but is sub optimal for real life decoding.
As a side note, I’d add that if you can’t get good results from proven hardware/software used successfully by thousands, including professional users like airports, and if you are unable to grasp the tech fundamentals of your hobby, you can only blame yourself - not the tools. Ironically, there are more positive reports in this same thread which shows a large disparity in this crowd at the technical level. Is learning new things that hard?
1 Like
hey look ! Its all of us that are the idiots! Wow what a treat way to treat paying customers.
I can only help with good tools. Knowledge/Skills are still required on your part. Be a gent and good luck!
Hey Dude,
It seems you’ve become ready for some overdue advice: You want to be a successful vendor in this hobby? Become a great teacher and stop being the arrogant fucktard that you are. You have the latter mastered. You might explore the former. You want to sell some inventory? Join us and guide us as we place your devices into service. Instead, you’ve alienated nearly your entire audience and customer base here. Not a great business plan. I guess Harvard wasn’t for you, huh? As you have observed, this is a hobby. We are here to learn, and most importantly, have fun. Clearly, that may be too low-level for you. Well, good luck with your professional airport accounts. I’m sure you can expect an order any day now.
You’re welcome,
Skeet!
I’ve not even read the rest of your message, but I want you to know that my time is better spent on actual projects rather than arguing with lambda joes on forums.
Want great working stuff that sets a new level of performance? Get my tools. Don’t want to learn by yourself? You can keep insulting/ranting on forums, this won’t make you look smarter.
And no, watching planes on a map is hardly a hobby if at all. Building high performance radios is where the fun is.
Now you can keep insulting.
Some people should learn when to stop digging their own grave.
Not sure anyone is knocking the hardware, although the implementation in regards to ADSB in specific is either lacking, buggy or simply misunderstood - possibly a combination of all three. What I’d suggest is a simple yet detailed step-by-step guide to get the masses (those who chose the purchase the radio) up and properly running. No matter how smart an individual is, or thinks they are, there is not a platform in existence that can be run through all it’s paces and debugged alone or with a small group - no less when plugging into and existing framework. Since I believe the source is closed, one thing that will help make things better is feedback from those willing to give things a try. Feedback from a novice is as important (if not more sometimes) than that of an expert so both sides can be addressed.
It’s more than obvious the hardware itself was not designed in specific for the ADSB crowd, but if you are going to go through the trouble of creating not only a plugin, but a “mini”, less expensive version of the radio to compete in the marketplace, you may as well suck up a little pride and take some time to listen to feedback. It is these people who can make or break a product and nobody is above that. Just an observation - do as you will. I’d hate to see what appears to be a fantastic piece of hardware fail this segment of the marketplace, one that is growing at a fantastic pace. If you are indeed aiming for the purely professional marketplace, then you need to ask yourself if the existing hardware is enough to compete.
Can you just tag those “successfully users”?Maybe they can provide some answers to novice level questions.
… just my five cent
→ blaming the airspy this way wasn’t 100% correct as a testing via splitter in my own testings was bad
→ blaming a customer this way is silly and helps nobody
→ for my testings i used two selected same antennas from jetvision parallel that produced same output within 1-3% range.
→ always did two runs for a week or so antennaX/receiverX and antennaY/receiverY then antennaX/receiverY and antennaY/receiverX
my findings were
→ habamp+nooelec dongle in combination with dump1090-mutability is nearly unbeatable for the price
→ airspy software can’t compete with dump1090 and raspis are too weak for airspy data output
→ airspy and especially radarcape are faster in detecting an aircraft for the first time but they deliver only few aircrafts more if any
→ radarcape delivers higher message rate (20%) than habamp/nooelec combo mentioned above
=> the only thing i’d find really interesting would be fpga solutions like this thread if their software would be on the same high level as dump1090 …
cheers
tom
1 Like
What I would really like to see is some concrete unbiased data for a an ADS-B dongle vs an Airspy mini on the various planforms; PC, RPi, etc. The fact that an Airspy mini may not be worth the money when compared to an ADS-B dongle is, in my opinion, not relevant. What is relevant is wether there is a significant performance advantage of one over the other and what platform is best suited for the Airspy. Armed with that data, each individual can then make their won determination of wether the Airspy is worth the extra cost.
All of the back and forth and insults in this thread is unproductive and helps no one.
Here are some reasonable comparison stats
satsignal.eu/mrtg/performance_ads-b.php
Note some are RPIs and others are Windows 10 PCs.
Here are some reasonable comparison stats
Note some are RPIs and others are Windows 10 PCs.
Thank you. That is the type of data I was looking for.
No one is blaming the hardware! It has been all about the software side of things and RasPi 2 isn’t really weak for Airspy Mini.
Edit:
Tom are you using a filtered pre-amp with AirSpy ?
[quote=“hsran”]
I think it’s more the support than the software. I had to work out most of the settings myself.
An RPI doesn’t have the USB bandwidth or CPU to cater for the airspy well. It is mostly the USB bandwidth, although the higher CPU causes MLAT to drop out on my devices(RPI3s). I ordered an Odroid XU4 as reviewers have stated that it has the grunt to cater for the airspys. I had it running but have to rebuilt it. It didn’t like a dev version of flight aware. I was told I should try the Ambian build. I’ll give it a go when I am not so busy (3 essays due this week).
Is that a Mini or a R2 ?