A Rebel Alliance For Internet Of Things Standards

November 21, 2016 by Alasdair Allan 41 Comments

Back when the original Internet, the digital one, was being brought together there was a vicious standards war. The fallout from the war fundamentally underpins how we use the Internet today, and what’s surprising is that things didn’t work out how everyone expected. The rebel alliance won, and when it comes to standards, it turns out that’s a lot more common than you might think.

Looking back the history of the Internet could have been very different. In the mid eighties the OSI standards were the obvious choice. In 1988 the Department of Commerce issued a mandate that all computers purchased by government agencies should be OSI compatible starting from the middle of 1990, and yet two years later the battle was already over, and the OSI standards had already lost.

In fact by the early nineties the dominance of TCP/IP was almost complete. In January of 1991 the British academic backbone network, called JANET (which was based around X.25 colored book protocols), established a pilot project to host IP traffic on the network. Within ten months the IP traffic had exceeded the levels of X.25 traffic, and IP support became official in November.

“Twenty five years ago a much smaller crowd was fighting about open versus proprietary, and Internet versus OSI. In the end, ‘rough consensus and running code’ decided the matter: open won and Internet won,”

—Marshall Rose, chair of several IETF Working Groups during the period

This of course wasn’t the first standards battle, history is littered with innumerable standards that have won or lost. It also wasn’t the last the Internet was to see. By the mid noughties SOAP and XML were seen as the obvious way to build out the distributed services we all, at that point, already saw coming. Yet by the end of the decade SOAP and XML were in heavy retreat. RESTful services and JSON, far more lightweight and developer friendly than their heavyweight counterparts, had won.

“JSON appeared at a time when developers felt drowned by misguided overcomplicated XML-based web services, and JSON let them just get the job done,”

“Because it came from JavaScript, and pretty much anybody could do it, JSON was free of XML’s fondness for design by committee. It also looked more familiar to programmers.”

—Simon St. Laurent, content manager at LinkedIn and O’Reilly author

Yet, depending on which standards body you want to listen to, ECMA or the IETF, JSON only became a standard in 2013, or 2014, respectively and while the IETF RFC talks about semantics and security, the ECMA standard covers only the syntax. Despite that it’s unlikely many people have actually read the standards, and this includes the developers using the standard and even those implementing the libraries those developers depend on.

We have reached the point where standardization bodies no longer create standards, they formalize them, and the way we build the Internet of Things is going to be fundamentally influenced by that new reality.

Continue reading “A Rebel Alliance For Internet Of Things Standards” →

Sinclair I/O Board Completed Over 30 Years Later

November 21, 2016 by Jenny List 15 Comments

In the early 1980s when the 8-bit microcomputer boom was well under way, [Alan Faulds] was a student, and an owner of a Sinclair ZX81. He had ambitions to use it, in his words, “to control the world“, but since the Sinclair lacked an I/O port he was thwarted. He bought an expander board and a couple of I/O card PCBs from the British electronic supplier Maplin in the days when they were a mail order parts stockist rather than a chain of stores chasing Radio Shack’s vacated retail position.

Sadly for [Alan], he didn’t have the cash to buy all the parts to populate the boards, then the pressures of a final year at university intervened, and he never built those Maplin kits. They sat forgotten in their padded envelope for over three decades until a chance conversation with a friend reminded him of his unfinished student project. He sought it out, and set about recreating the board.

The ZX81 had a single port: a PCB edge connector at its rear that exposed all the Z80 processor’s lines. It was notorious for unreliability, as the tiniest vibration when a peripheral was connected would crash the machine. Maplin’s expansion system featured a backplane with a series of edge connector sockets, and cards with bare PCB edge connectors. Back in the 1980s it was easy to find edge connectors of the right size with the appropriate key installed, but not these days. [Alan] had to make one himself for his build.

The I/O card with its 8255 and brace of 74 series chips was a double-sided affair with vias made through the use of little snap-off hand-soldered pins. [Alan] put his ICs in sockets, a sensible choice given that when he powered it up he found he’d put a couple of the 74 chips in the wrong positions. With that error rectified the board worked exactly as it should, giving the little ZX three I/O ports, albeit with one of them a buffered output.

We haven’t featured the little Sinclair micro as often as we should have here at Hackaday, it seems to have been overshadowed by its ZX Spectrum successor. We did show you a VGA ZX81 emulated on an mbed though, and a rather neat color video hack for its Brazilian cousin.

Five-Watt SDR Transceiver For Hams

November 20, 2016 by Elliot Williams 50 Comments

The availability of cheap SDR hardware created a flourishing ecosystem for SDR software, but a lot of the hardware driving the revolution was still “cheap”. In the last few years, we’ve seen quality gear replacing the TV dongles in many setups, and down-converters designed for them to allow them to work on the ham bands.

But something that’s purpose-built might be a better option if ham radio, particularly the shortwave portion thereof, is your goal. First off, you might want to transmit, which none of the TV dongles allow. Then, you might want a bit of power. Finally, if you’re serious about short-wave, you care more about the audio quality than you do immense bandwidth, so you’re going to want some good filters on the receiving end to help you pull the signal out of all the noise.

The RS-HFIQ 5 W SDR transceiver might be for you. It’s up on Kickstarter right now, and it’s worth looking at if you want a fully open source (schematics, firmware, and software) shortwave SDR rig. It’s also compatible with various open frontends.

The single-board radio isn’t really a full SDR in our mind — it demodulates the radio signal and sends a 96 kHz IQ signal across to your computer’s soundcard where it gets sampled and fully decoded. The advantage of this is that purpose-built audio rate DACs have comparatively high resolution for the money, but the disadvantage is that you’re limited to 96 kHz of spectrum into the computer. That’s great for voice and code transmissions, but won’t cut it for high-bandwidth data or frequency hopping applications. But that’s a reasonable design tradeoff for a shortwave.

Still, an SDR like this is a far cry from how simple a shortwave radio can be. But if you’re looking to build up your own SDR-based shortwave setup, and you’d like to hack on the controls more than on the radio itself, this looks like a good start.

Stairwell Lights Keep Toddler With Night-Blindness Safe

November 19, 2016 by Dan Maloney 25 Comments

A devastating diagnosis for a young child is every parent’s worst nightmare. All too often there’s nothing that can be done, but occasionally there’s a window of opportunity to make things better for the child, even if we can’t offer a cure. In that case even a simple hack, like a rapid response stairwell light to help deal with night-blindness, can make a real difference.

[Becca] isn’t yet a year old, but she and her parents carry a heavy burden. She was born with Usher Syndrome, an extremely rare genetic disease that affects hearing and vision to different degrees. In [Becca]’s case, she was born profoundly deaf and will likely lose her sight by the time she’s 10 or so. Her dad [Jake] realized that the soon-to-be-toddler was at risk due to a dark stairwell and the night-blindness that accompanies Usher, so he came up with a simple tech solution to the problem.

He chose Philips Hue LED light strips to run up the stringer of the stairs controlled by a Raspberry Pi. Originally he planned to use IFTTT for the job but the latency resulted in the light not switching on fast enough. He ended up using a simple PIR motion sensor which the Pi monitors and then uses the Hue API to control the light. This will no doubt give him a platform for future capabilities to help [Becca].

We’ve covered a few builds where parents have hacked solutions for their kids, like this custom media center for the builder’s autistic son. We suspect [Jake] has a few more tricks up his sleeve to help [Becca], and we’re looking forward to seeing how she does.

Under The (Linux) Hood

November 19, 2016 by Al Williams 53 Comments

We’ve often heard that you don’t need to know how an engine works to drive a car, but you can bet that professional race car drivers know. By analogy, you can build lots of systems with off-the-shelf boards like Raspberry Pis and program that using Python or some other high-level abstraction. The most competent hackers, though, know what’s going on inside that Pi and what Python is doing under the hood down to some low level.

If you’ve been using Linux “under the hood” often means understanding what happens inside the kernel–the heart of the Linux OS that manages and controls everything. It can be a bit daunting; the kernel is simple in concept, but has grown over the years and is now a big chunk of software to approach.

Your first embedded system project probably shouldn’t be a real time 3D gamma ray scanner. A blinking LED is a better start. If you are approaching the kernel, you need a similar entry level project. [Stephen Brennan] has just the project for you: add your own system call to a custom Linux kernel.

Continue reading “Under The (Linux) Hood” →

EM Drive Paper Published By Eagleworks Team

November 19, 2016 by Jenny List 131 Comments

There are one or two perennial scientific stories that sound just too good to be true, but if they delivered on their promise would represent a huge breakthrough and instantly obsolete entire fields. One example is so-called “cold fusion”, the idea that nuclear fusion could be sustained with a net energy release at room temperature rather than super-high temperature akin to that of the sun. We all wish it could work, but so far it has obstinately refused. As a TV actor portraying a space engineer of the future once said, one “cannae change the Laws of Physics“.
Continue reading “EM Drive Paper Published By Eagleworks Team” →

IPhone NVMe Chip Reversed With Custom Breakout Boards

November 18, 2016 by Brian Benchoff 36 Comments

Ever so slowly, the main storage in our computers has been moving from spinning disks, to SSDs over SATA, to Flash drives connected to a PCI something or other. The latest technology is NVMe — Non-Volitile Memory Express — a horribly named technology that puts a memory controller right on the chip. Intel has a PCI-based NVMe drive out, Samsung recently released an M.2 NVMe drive, and the iPhone 6S and 6S Plus are built around this storage technology.

New chips demand a reverse engineering session, and that’s exactly what [Ramtin Amin] did (Internet Archive). He took a few of these chips out of an iPhone, created a board that will read them, and managed to analyze the firmware.

Any reverse engineering will begin with desoldering the chip. This is easy enough, with the real trick being getting it working again outside whatever system it was removed from. For this, [Ramtin] built his own PCIe card with a ZIF socket. This socket was custom-made, but the good news is you can buy one from ITEAD. Yes, it is expensive — that’s what you get with a custom-made ZIF socket.

With the chip extracted, a custom PCIe card, and a bit of work with the NVMe implementation for Linux, [Ramtin] had just about everything working. Eventually, he was able to dump the entire file system on the chip, allowing anyone to theoretically back up the data on their iPhone or MacBook Air. Of course, and especially for the iPhone, this data is encrypted. It’s not possible to clone an iPhone using this method, but it is a remarkably deep dive into the hardware that makes our storage tick.