Maybe this is pedantic -- Did you build a radar, or did you build a wrapper around an ADS-B API?
I clicked this thinking, "Wow! Radars are hard. Building one at home would be quite the feat!", but this appears to just be a wrapper around an ADS-B data providing service? Not even reading the ADS-B data over the air on one's own at home?
Calling this a radar, vs saying "I build a nice GUI around ADS-B data", are two very different things! The latter is a fun side project at home, but it's a couple orders of magnitude easier than the former!
Listen, if you think handing a kid a cavity magnetron and the multi-kilowatt power supply to drive it ON TOP of a high-voltage CRT display is a good idea -- then I really want to know how it goes.
As someone who grew up around (literally stacks of) analogue equipment, I feel that it's worth noting that there's nothing particularly unsafe about high voltages when they're properly contained. The dielectric strength of air is sufficiently high that you effectively need to be touching the conductor before it will arc. At that point, there's not a terrible amount of different between touching a live 240V AC terminal (the standard where I live and in most of the world) and a live 2000V AC terminal. I'm definitely not suggesting that one should be cavalier about high voltages, just pointing out that electrocution wasn't a big problem in practice for most of the time when these older devices were used.
There several more pressing safety issues with analogue equipment than simple electrocution:
- Fire risk due to the much greater energy consumption of older discrete components. Even the passive losses when in standby are considerable; the need for heatsinks is a given, and ventilation is critical.
- Explosion (actually implosion) risk of vacuum tubes/thermionic valves. There are a surprising number of videos online of people deliberately destroying TVs with overvoltage, but suffice it to say that you do not want one plugged into the mains during a thunderstorm.
- Physical injury. Not really the fault of the technology per se, but it can be easy to forget just how physically light modern equipment is. You can hurt yourself by trying to move older devices. Having the equipment fall on them is probably the biggest risk to a toddler who's not actually trying to take the device apart.
Well, obviously that part would be on the roof, and you would hand the kid something that would, to them, be indistinguishable from the API approach, all as you nervously wait for authorities, from the nearby military base, to come check your intentions.
I know at least three people who are nuts, skilled and moneyed enough to actually build a legit radar system - they're all hams. Only problem I think would be getting a license to transmit on radar frequencies...
"Back in my day..."
To a toddler, it's all the same.
I don't know of any toddlers reading Hacker News.
You're right, but the thing was made for a toddler and the "radar" label was probably made for them.
Honestly, "radar" is probably the clearest label for something like this for all people who don't know what ADS-B and RTL-SDR mean (which is probably 99% of all people, period).
I wouldn't have any issue if it were worded "radar", with quotes. That implies a likeness, but denotes a lack of precision.
And I think there are more avnerds on here than you would expect!
I don't understand why you're being downvoted. You are correct.
I also don't think you are being pedantic. This is a forum where technology is often the topic of discussion, and in tech words often have very specific meanings. Like radar.
No slight whatsoever to the original author, I liked the post, and applaud their work :)
I just don't get the downvoting nature of some of the folks here. This isn't reddit.
Downvoting likely signals disagreement as well as disapproval.
But consider this: there may be an electrical engineer reading the article right now thinking "damn, apps are hard, building one at home is quite the feat!"
One of the GNU radio guys built an actual passive radar quite some years ago. I could see someone with that background looking at phone app development and scratching their head ;-)
In the aviation industry the secondary surveillance radar (SSR), as it's called, passively interrogates transmitting air traffic in ATC's airspace (1090 MHz ADS-B and 978 MHz UAT). It's not the primary radar, which is active radar and what most people think of when they hear radar. It's a terminology issue which we're stuck with now given that SSR is part of the nomenclature.
The SSR receiver is usually a long conic rotating dish, the length provides lateral isolation, as the dish itself is tilted up to match the runway glideslope (inbound and outbound track for most transmitting aircraft).
The SSR can receive information well beyond the range of the primary radar. For an air traffic controller, a commercial aircraft shows up on the SSR first, and can be directed right away. The primary radar mainly catches anomalous behaviour, foreign objects and GA aircraft that may not be equipped with UAT.
Ehh, secondary radar is still radar. Swapping the passive reflector for a preamble/header triggered gated (after header received, active for some short duration) non-passive echo, doesn't negate the way of "send radio wave, receive echo, measure latency/delay, divide by twice light speed, get distance".
FYI, discussion on part 1 here - https://news.ycombinator.com/item?id=38435908
Doing God's work!
I did think the same too as radars (active or passive) are indeed complicated, but a quick view to the article clearly it’s just a wrapper around an API, still cool and I downloaded it!
You are taking this too seriously and the answer can be found in the blog post.
It's clearly a dad-daughter fun project and the toddler is more likely calling it a "Radar" and not "Can I play with the ADS-B API Wrapper?" which is the spirit of the whole post and app.