Inside A $30,000 8 GHz Scope

One of the best things about the Internet — especially the video part — is that you can get exposed to lots of things you might otherwise not be able to see. Take oscilloscopes, for example. If you were lucky, you might have one or two really nice instruments at work and you certainly weren’t going to be allowed to tear them open if they were working well. [The Signal Path], as a case in point, tears down a $30,000 MSO6 8 GHz oscilloscope.

Actually, the base price is not quite $30,000 but by the time you outfit one, you’ll probably break the $30K barrier. Compared to the scopes we usually get to use, these are very different. Sure, the screens are larger and denser, but looking at the circuit boards they look more like some sort of high-end computer than an oscilloscope. Of course, in a way, that’s exactly what it is.

Continue reading “Inside A $30,000 8 GHz Scope”

Smashing The Atom: A Brief History Of Particle Accelerators

When it comes to building particle accelerators the credo has always been “bigger, badder, better”. While the Large Hadron Collider (LHC) with its 27 km circumference and €7.5 billion budget is still the largest and most expensive scientific instrument ever built, it’s physics program is slowly coming to an end. In 2027, it will receive the last major upgrade, dubbed the High-Luminosity LHC, which is expected to complete operations in 2038. This may seem like a long time ahead but the scientific community is already thinking about what comes next.
Recently, CERN released an update of the future European strategy for particle physics which includes the feasibility study for a 100 km large Future Circular Collider (FCC). Let’s take a short break and look back into the history of “atom smashers” and the scientific progress they brought along. Continue reading “Smashing The Atom: A Brief History Of Particle Accelerators”

Falcon 9 Beats Shuttle’s Reflight Record, But Still Has A Long Way To Go

Put simply, the goal of any reusable booster is to reduce the cost of getting a payload into space. The comparison is often made to commercial aviation: if you had to throw away the airliner after every flight, nobody could afford the tickets. The fact that the plane can be refueled and flown again and again allows operators to amortize its high upfront cost.

In theory, the same should hold true for orbital rockets. With enough flight experience, you can figure out which parts of the vehicle will need replacement or repair, and how often. Assuming the fuel is cheap enough and the cost of refurbishment doesn’t exceed that of building a new one, eventually the booster will pay for itself. You just need a steady stream of paying customers, which is hardly a challenge given how much we rely on our space infrastructure.

But there’s a catch. For the airliner analogy to really work, whatever inspections and repairs the rocket requires between missions must be done as quickly as possible. The cost savings from reuse aren’t nearly as attractive if you can only fly a few times a year. The key to truly making space accessible isn’t just building a reusable rocket, but attaining rapid reusability.

Which is precisely where SpaceX currently finds themselves. Over the years they’ve mastered landing the Falcon 9’s first stage, and they’ve even proven that the recovered boosters can be safely reused for additional flights. But the refurbishment process is still fairly lengthy. While their latest launch officially broke the record for fastest reflight of a space vehicle that had previously been set by Space Shuttle Atlantis, there’s still a lot of work to be done if SpaceX is ever going to fly their rockets like airplanes.

Continue reading “Falcon 9 Beats Shuttle’s Reflight Record, But Still Has A Long Way To Go”

Let’s Take A Closer Look At This Robotic Airship

It’s not a balloon, however shiny its exterior may seem. This miniature indoor robotic airship created by the University of Auckland mechanical engineering research group [New Dexterity] is an asymmetric system experimenting with the possibilities of an open-source helium-based airship.

Why a helium airship, as opposed to a fixed wing aircraft? The group wanted to experiment with the advantages of lighter-than-air (LTA) travel, namely the higher mobility and looser path planning constraints. Furthermore, LTA airships have a less obstructed field of vision and fewer locomotion issues. While unmanned aerial vehicles (UAV) may be capable of hovering in one place, their lift is generated by rotor thrust, which drains their batteries quickly in the order of minutes. LTA airships can hover for longer periods of time.

The design was created for educational and research purposes, focusing on the financial feasibility of manufacturing the platform, the environmental impact of the materials, and the helium loss through the balloon-like envelope. By measuring these parameters, the researchers are able to study the effects of circumstances such as the cost of indoor commercial balloons and the mechanical properties of balloon materials.

The airship gondola was designed and 3D printed in a modular fashion, then attached to the envelope with Velcro. The placement with respect to the horizontal symmetry of the gondola was done for flight stability, with several configurations tested for the side rotor angle.

The group open-sourced their CAD files and ROS interface for controlling the airship. They primarily use off-the-shelf components such as Raspberry Pi boards, propellers, a DC single brushed motor driver carrier, and LiPo batteries for a total cost of $90 for the platform, with an addition $20 for the balloon and initial helium filling. The price is comparable to the cost of indoor blimps like the Blimpduino 2.0.

You can check out the completed airship below, where the team demonstrates its path following capabilities based on a carrot chasing path finding algorithm. And if you’re interested in learning more about the gotchas of building lighter-than-air vehicles, check out [Sophi Kravitz’s] blimp talk from Hackaday Belgrade.

Continue reading “Let’s Take A Closer Look At This Robotic Airship”

Jan Czochralski And The Silicon Revolution

If you were to travel back in time to the turn of the previous century and try to convince the average person that the grains of sand on just about any beach would be the basis of an industry worth hundreds of billions of dollars within 100 years, they’d probably have thought you were crazy. Aside from being coarse, rough, and irritating, sand is everywhere, and convincing anyone of its value would be a hard sell, unless your interlocutor was a real estate visionary with an appreciation of the future value of seaside property and a lot of patience.

Fast forward to our time, and we all know the value of the material that comes from common quartz sand: silicon, specifically the ultra-purified crystals of silicon that end up as the wafers we depend on to build the circuitry of life. The trip from beach to chip foundry is a long and non-obvious one which would not have been possible without the insights of an undistinguished Polish student and one-time druggist who discovered the process that made the Information Age possible: Jan Czochralski.

Continue reading “Jan Czochralski And The Silicon Revolution”

Hackaday Links Column Banner

Hackaday Links: July 19, 2020

Care to flex your ethical hacker muscles? The Defense Advanced Research Projects Agency, better known as DARPA, is running its first-ever bug-bounty program. The event is called “Finding Exploits to Thwart Tampering”, or FETT — get it? Bounty hunter? Fett? — and is designed to stress-test security hardware developed through DARPA’s System Security Integration Through Hardware and Firmware, or SSITH. Tortured backronyms and pop culture references aside, FETT will start this month and go through September. This is not an open challenge per se; rather, the Red Team will be coordinated by crowdsourced security research company Synack, who has called for security researchers to sign on.

The Linux kernel development team has decided to join the trend away from insensitive terminology like “master/slave” and “blacklist/whitelist” in coding style. A July 4 proposal by kernel maintainer Dan Williams goes into some detail on the logic of making the change, and it’s quite convincing stuff. It’s hard to argue with the fact that code reviewers can easily be distracted by coding style changes, so replacing terms that have become lightning rods only makes sense. Linus himself has signed off on the changes for all future code; the current terminology will only be allowed for purposes of maintaining older code.

Some stories just leap off the screen when you’re scanning headlines, and a story with the term “narco-antennas” practically begs further investigation. It turns out that the drug cartels in Mexico (and probably elsewhere, but the story focused on Mexico) are quite sophisticated in terms of communications technology. Eschewing cell phones for some of their communication needs for obvious reasons, they still apparently leverage the cell system by installing their own transceivers at cell sites. This can lead to some tense moments for the engineers who maintain legitimate gear at these sites; the story above recounts one hapless tech who powered down a site to make some repairs only to be confronted by armed men upset about the loss of their radios. It’s a fascinating look at the underworld and their technology, and we can’t help but feel for the men and women who have to face down these criminals just to do their jobs.

Way back in January — remember January? — we kicked off the 2020 Hack Chat series with a fellow named Alberto Caballero, principal investigator of the Habitable Exoplanet Hunting Project. At the time, I was blown away by the fact that the tiny changes in intensity caused by planets transiting across their star’s face were detectable on Earth with instruments an amateur astronomer could easily afford. And now, the project’s crowdsourced planet hunters have hit pay dirt, with the discovery of a Saturn-sized exoplanet in orbit within the habitable zone around star GJ 3470, also known as Gliese 3470, a red dwarf about 30 parsecs away in the constellation Cancer. Their paper is still in preprint and hasn’t been peer-reviewed yet, but it’s exciting to see this kind of citizen science being done, and we’d like to congratulate the team on their achievement and wish them continued luck in their search for “Earth 2.0”

And finally, if you can’t stand the idea that future archaeologists may someday pore over your code in an attempt to understand the digital lives of their long-dead forebears, then you might want to skip this story about how GitHub shipped 21 terabytes of open-source code to cold storage. The destination for the data, contained on reels of archive film and shipped on two pallets, is the world’s long-term memory: the Artic World Archive on the island of Svalbard. Perhaps better known for the Svalbard Seed Vault, where the genetic diversity of the world’s plants is stored, the Artic Code Vault is in a nearby abandoned coal mine and set deep within the permafrost. The rationale for making the effort to preserve code makes for some interesting reading, but we can’t help but feel that like the graffitists of Pompeii, if we’d known someone would be reading this stuff in a thousand years, we might have edited out a few things.

This 68k Board Is About As Simple As It Gets

For those of us who remember the Motorola 68000 microprocessor, it’s likely that a sizeable quantity of those memories will come in the form of a cream or grey box with a Commodore, Atari, or Apple logo on it These machines were the affordable creative workstations of their day, and under the hood were a tour de force of custom silicon and clever hardware design. We might, therefore, be excused for an association between 68000 based computers and complexity, but in reality, they are as straightforward to interface as the rest of the crop of late-1970s silicon. We can see it in [Matt Sarnoff]’s 68k-nano, about as simple a 68000-based single-board computer as it’s possible to get.

But for all its simplicity, this board is no slouch. It packs a megabyte of RAM, 64k of ROM, a 16550 UART, and an IDE interface for a CompactFlash card. There is also provision for a real-time clock module, through an interesting bit-banged SPI interface from the 16550’s control lines. There appears also to be a 50-pin expansion header.

Software-wise there is a ROM monitor that provides test and housekeeping functions, and which loads an executable from the card plugged into the IDE interface if there is one. This feature makes the board especially interesting, as it opens up the possibility of running a μClinux or similar kernel for a more fully-featured operating system.

The 68k doesn’t receive the attention here that some of its 8-bit contemporaries do, but it still appears from time to time. We’ve certainly featured at least one other 68000-based SBC in the past.

Thanks [Anton] for the tip.