Xilinx recently announced the Virtex UltraScale+ VU19P FPGA. Of course, FPGA companies announce new chips every day. The reason this one caught our attention is the size of it: nearly 9 million logic cells and 35 billion transistors on a chip! If that’s not enough there is also over 2,000 user I/Os including transceivers that can move around 4.5 Tb/s back and forth.
To put things in perspective, the previous record holder — the Virtex Ultrascale 440 — has 5.5 million logic cells and an old-fashioned Spartan 3 topped out at about 50,000 cells — the new chip has about 180 times that capacity. For the record, I’ve built entire 32-bit CPUs on smaller Spartans.
That led us to wonder? Who’s buying these things? When I first heard about it I guessed that the price would be astronomical, partly due to expense but also partly because the market for these has to be pretty small. The previous biggest Xilinx part is listed on DigKey who pegs the Ultrascale 440 (an XCVU440-2FLGA2892E) at a cost of $55,000 as a non-stocked item. Remember, that chip has just over half the logic cells of the VU19P.
It seems like hardly a day goes by that doesn’t see some news story splashed across our feeds that has something to do with Elon Musk and one or another of his myriad companies. The news is often spectacular and the coverage deservedly laudatory, as when Space X nails another double landing of its boosters after a successful trip to space. But all too often, it’s Elon’s baby Tesla that makes headlines, and usually of the kind that gives media relations people ulcers.
The PR team on the automotive side of Tesla can take a bit of a breather now, though. This time it’s Elon’s solar power venture, Tesla Energy Operations, that’s taking the heat. Literally — they’ve been sued by Walmart for rooftop solar installations that have burst into flames atop several of the retail giant’s stores. While thankfully no lives have been lost and no major injuries were reported, Walmart is understandably miffed at the turn of events, leading to the litigation.
Walmart isn’t alone in their exposure to potential Tesla solar problems, so it’s worth a look to see what exactly happened with these installations, why they failed, and what we as hackers can learn from the situation. As we’ll see, it all boils down to taking electrical work very seriously and adhering to standards designed to keep everyone safe, even when they just seem like a nuisance.
India’s Chandrayaan-2 mission to the Moon was, in a word, ambitious. Lifting off from the Satish Dhawan Space Centre on July 22nd, the mission hoped to simultaneously deliver an orbiter, lander, and rover to our nearest celestial neighbor. The launch and flight to the Moon went off without a hitch, and while there were certainly some tense moments, the spacecraft ultimately put itself into a stable lunar orbit and released the free-flying lander so it could set off on its independent mission.
Unfortunately, just seconds before the Vikram lander touched down, an anomaly occurred. At this point the Indian Space Research Organisation (ISRO) still doesn’t know exactly what happened, but based on the live telemetry stream from the lander, some have theorized the craft started tumbling or otherwise became unstable between three and four kilometers above the surface.
Telemetry indicates a suboptimal landing orientation
In fact, for a brief moment the telemetry display actually showed the Vikram lander completely inverted, with engines seemingly accelerating the spacecraft towards the surface of the Moon. It’s unclear whether this was an accurate depiction of the lander’s orientation in the final moments before impact or a glitch in the real-time display, but it’s certainly not what you want to see when your craft is just seconds away from touchdown.
But for Chandrayaan-2, the story doesn’t end here. The bulk of the mission’s scientific goals were always to be accomplished by the orbiter itself. There were of course a number of scientific payloads aboard the Vikram lander, and even the Pragyan rover that it was carrying down to the surface, but they were always secondary objectives at best. The ISRO was well aware of the difficulties involved in making a soft landing on the Moon, and planned their mission objectives accordingly.
Rather than feel sorrow over the presumed destruction of Vikram and Pragyan, let’s take a look at the scientific hardware aboard the Chandrayaan-2 orbiter, and the long mission that still lies ahead of it.
Today marks exactly 15 years since Hackaday began featuring one Hack a Day, and we’ve haven’t missed a day since. Over 5,477 days we’ve published 34,057 articles, and the Hackaday community has logged 903,114 comments. It’s an amazing body of work from our writers and editors, a humbling level of involvement from our readers, and an absolutely incredible contribution to open hardware by the project creators who have shared details of their work and given us all something to talk about and to strive for.
What began as a blog is now a global virtual hackerspace. That first 105-word article has grown far beyond project features to include spectacular long-form original content. From our community of readers has grown Hackaday.io, launched in 2014 you’ll now find over 30,000 projects published by 350,000 members. The same year the Hackaday Prize was founded as a global engineering initiative seeking to promote open hardware, offering big prizes for big ideas (and the willingness to share them). Our virtual connections were also given the chance to come alive through the Hackaday Superconference, Hackaday Belgrade, numerous Hackaday Unconferences, and meetups all over the world.
All of this melts together into a huge support structure for anyone who wants to float an interesting idea with a proof of concept where “why” is the wrong question. Together we challenge the limits of what things are meant to do, and collectively we filter through the best ideas and hold them high as building blocks for the next iteration. The Hackaday community is the common link in the collective brain, a validation point for perpetuating great ideas of old, and cataloging the ones of new.
Perhaps the most impressive thing about the last 15 years of Hackaday is how much the technological landscape has changed. Hackaday is still around because all of us have actively changed along with it — always looking for that cutting edge where the clever misuse of something becomes the base for the next transformative change. So we thought we’d take a look back 15 years in tech. Let’s dig into a time when there were no modules for electronics, you couldn’t just whip up a plastic part in an afternoon, designing your own silicon was unheard of, and your parts distributor was the horde of broken electronics in your back room.
Many of us don’t think too much about radiation levels in our area, until a nuclear disaster hits and questions are raised. Radiation monitoring is an important undertaking, both from a public health perspective and as a way to monitor things like weapon development. So why is it done, how is it done, and what role can concerned citizens play in keeping an eye on things?
Not so very long ago, orbital rockets simply didn’t get reused. After their propellants were expended on the journey to orbit, they petered out and fell back down into the ocean where they were obliterated on impact. Rockets were disposable because, as far as anyone could tell, building another one was cheaper and easier than trying to reuse them. The Space Shuttle had proved that reuse of a spacecraft and its booster was possible, but the promised benefits of reduced cost and higher launch cadence never materialized. If anything, the Space Shuttle was often considered proof that reusability made more sense on paper than it did in the real-world.
Rocket Lab CEO Peter Beck with Electron rocket
But that was before SpaceX started routinely landing and reflying the first stage of their Falcon 9 booster. Nobody outside the company really knows how much money is being saved by reuse, but there’s no denying the turn-around time from landing to reflight is getting progressively shorter. Moreover, by performing up to three flights on the same booster, SpaceX is demonstrating a launch cadence that is simply unmatched in the industry.
So it should come as no surprise to find that other launch providers are feeling the pressure to develop their own reusability programs. The latest to announce their intent to recover and eventually refly their vehicle is Rocket Lab, despite CEO Peter Beck’s admission that he was originally against the idea. He’s certainly changed his tune. With data collected over the last several flights the company now believes they have a reusability plan that’s compatible with the unique limitations of their diminutive Electron launch vehicle.
According to Beck, the goal isn’t necessarily to save money. During his presentation at the Small Satellite Conference in Utah, he explained that what they’re really going after is an increase in flight frequency. Right now they can build and fly an Electron every month, and while they eventually hope to produce a rocket a week, even a single reuse per core would have a huge impact on their annual launch capability:
If we can get these systems up on orbit quickly and reliably and frequently, we can innovate a lot more and create a lot more opportunities. So launch frequency is really the main driver for why Electron is going reusable. In time, hopefully we can obviously reduce prices as well. But the fundamental reason we’re doing this is launch frequency. Even if I can get the stage back once, I’ve effectively doubled my production ratio.
But, there’s a catch. Electron is too small to support the addition of landing legs and doesn’t have the excess propellants to use its engines during descent. Put simply, the tiny rocket is incapable of landing itself. So Rocket Lab believes the only way to recover the Electron is by snatching it out of the air before it gets to the ground.
On August 8th, an experimental nuclear device exploded at a military test facility in Nyonoksa, Russia. Thirty kilometers away, radiation levels in the city of Severodvinsk reportedly peaked at twenty times normal levels for the span of a few hours. Rumors began circulating about the severity of the event, and conflicting reports regarding forced evacuations of residents from nearby villages had some media outlets drawing comparisons with the Soviet Union’s handling of the Chernobyl disaster.
Today, there remain more questions than answers surrounding what happened at the Nyonoksa facility. It’s still unclear how many people were killed or injured in the explosion, or what the next steps are for the Russian government in terms of environmental cleanup at the coastal site. The exceptionally vague explanation given by state nuclear agency Rosatom saying that the explosion “occurred during the period of work related to the engineering and technical support of isotopic power sources in a liquid propulsion system”, has done little to assuage concerns.
The consensus of global intelligence agencies is that the test was likely part of Russia’s program to develop the 9M730 Burevestnik nuclear-powered cruise missile. Better known by its NATO designation SSC-X-9 Skyfall, the missile is said to offer virtually unlimited flight range and endurance. In theory the missile could remain airborne indefinitely, ready to divert to its intended target at a moment’s notice. An effectively unlimited range also means it could take whatever unpredictable or circuitous route necessary to best avoid the air defenses of the target nation. All while traveling at near-hypersonic speeds that make interception exceptionally difficult.
Such incredible claims might sound like saber rattling, or perhaps even something out of science fiction. But in reality, the basic technology for a nuclear-powered missile was developed and successfully tested nearly sixty years ago. Let’s take a look at this relic of the Cold War, and find out how Russia may be working to resolve some of the issues that lead to it being abandoned. Continue reading “Echos Of The Cold War: Nuclear-Powered Missiles Have Been Tried Before”→
