Arrow’s $30 FPGA Board Reviewed

We like cheap FPGA boards. It isn’t just that we’re cheap — although that’s probably true, too — but cheap boards are a good way to get people started on FPGAs and we think more people should be using FPGAs more often. One inexpensive board is the Max-1000 from Trenz and Arrow. At $29, it is practically an impulse buy. [ZipCPU] did a great write up on his experience using the board. He found that some of it was good, some was bad, and some was just plain ugly. Still, for $30, it seems like this might be a nice board for some applications or for getting started.

Billed an IoT Maker Board, the tiny board sports a Intel (formerly Altera) MAX10 device with 8,000 logic elements, a USB programming interface onboard, 8 MB of SDRAM, and both PMOD and Arduino MKR headers. The MAX10 has an analog to digital conversion block (with an analog mux for up to nine channels) and the ability to host a 32-bit soft controller onboard, too.

Continue reading “Arrow’s $30 FPGA Board Reviewed”

Students Hack An Unusual Violin

[Sean Riley] is a violinist who had a problem. He wanted to play one particular piece, but he couldn’t. It wasn’t that he lacked the skill — he a doctoral student at the University of Texas and has two degrees in violin performance from The Julliard School. The problem was that “The Dharma at Big Sur” by [John Adams] is made for an instrument with six strings, while most violins only have four. So he did what any of us would do. He stopped by the local hackerspace and fabricated one. You can hear (and see) [Sean] performing with the instrument in the video, below.

The University of Texas operates “The Foundry” which is a hackerspace with all the usual items: laser cutters, 3D printers, and the like. It is open to all their students and staff. [Sean] needed some help with the engineering, and was lucky to find a mechanical engineering senior, [Daniel Goodwin], working at The Foundry.

Continue reading “Students Hack An Unusual Violin”

Search For Military Satellite Finds One NASA Lost Instead

[Scott Tilley] was searching for radio signals from the Air Force’s top-secret ZUMA satellite. He found something that is — we think — much more interesting. He found NASA’s lost satellite called IMAGE. You are probably wondering why it is interesting that someone listening for one satellite found another one. You see, NASA declared IMAGE dead in 2005. It went silent unexpectedly and did not complete its mission to image the magnetosphere.

NASA did a failure review and concluded that in all likelihood a single event upset caused a power controller to trip. A single event upset, or SEU, is a radiation event and should have been automatically recovered. However, there was a design flaw that failed to report certain types of power controller failures, including this one.

The report mentioned that it might be possible to reset the controller at a specific time in 2007, but given that NASA thought the satellite was out of commission that either never occurred or didn’t work. However, something apparently woke the satellite up from its sleep.

[Scott] did a lot of number crunching to determine that the satellite’s spin rate had only decreased a little from its operational value and that the doppler data matched what he expected. [Scott] can’t read or command the telemetry, so he doesn’t know how healthy the satellite is, but it is at least operational to some degree. It’s really neat to see members of the team that worked on IMAGE leaving comments congratulating [Scott] on the find. They are working to get him data formatting information to see if more sense can be made of the incoming transmissions.

Who knew listening to satellites could be so exciting? If you want to build your own ground station, you might be interested in this antenna mount. If you need to know what’s overhead, this can help.

Quantum Weirdness In Your Browser

I’ll be brutally honest. When I set out to write this post, I was going to talk about IBM’s Q Experience — the website where you can run real code on some older IBM quantum computing hardware. I am going to get to that — I promise — but that’s going to have to wait for another time. It turns out that quantum computing is mindbending and — to make matters worse — there are a lot of oversimplifications floating around that make it even harder to understand than it ought to be. Because the IBM system matches up with real hardware, it is has a lot more limitations than a simulator — think of programming a microcontroller with on debugging versus using a software emulator. You can zoom into any level of detail with the emulator but with the bare micro you can toggle a line, use a scope, and hope things don’t go too far wrong.

So before we get to the real quantum hardware, I am going to show you a simulator written by [Craig Gidney]. He wrote it and promptly got a job with Google, who took over the project. Sort of. Even if you don’t like working in a browser, [Craig’s] simulator is easy enough, you don’t need an account, and a bookmark will save your work.

It isn’t the only available simulator, but as [Craig] immodestly (but correctly) points out, his simulator is much better than IBM’s. Starting with the simulator avoids tripping on the hardware limitations. For example, IBM’s devices are not fully connected, like a CPU where only some registers can get to other registers. In addition, real devices have to deal with noise and the quantum states not lasting very long. If your algorithm is too slow, your program will collapse and invalidate your results. These aren’t issues on a simulator. You can find a list of other simulators, but I’m focusing on Quirk.

What Quantum Computing Is

As I mentioned, there is a lot of misinformation about quantum computing (QC) floating around. I think part of it revolves around the word computing. If you are old enough to remember analog computers, QC is much more like that. You build “circuits” to create results. There’s also a lot of difficult math — mostly linear algebra — that I’m going to try to avoid as much as possible. However, if you can dig into the math, it is worth your time to do so. However, just like you can design a resonant circuit without solving differential equations about inductors, I think you can do QC without some of the bigger math by just using results. We’ll see how well that holds up in practice.

Continue reading “Quantum Weirdness In Your Browser”

Firing Up 750 Raspberry Pis

Creating Raspberry Pi clusters is a popular hacker activity. Bitscope has been commercializing these clusters for a bit now and last year they created a cluster of 750 Pis for Los Alamos National Labs. You might wonder what an institution know for supercomputers wants with a cluster of Raspberry Pis. Turns out it is tough to justify taking a real high-speed cluster down just to test software. Now developers can run small test programs with a large number of CPU cores without requiring time on the big iron.

On the face of it, this doesn’t sound too hard, but hooking up 750 of anything is going to have its challenges. You have to provide power and carry away heat. They all have to communicate, and you aren’t going to want to house the thing in a few hundred square feet which makes heat and power even more difficult.

Continue reading “Firing Up 750 Raspberry Pis”

DIY Graphene Putty Makes Super Sensitive Sensor

It is sort of an electronics rule 34 that if something occurs, someone needs to sense it. [Bblorgggg], for reasons that aren’t immediately obvious, needs to sense ants moving over trees. No kidding. How are you going to do that? His answer was to use graphene.

Actually, his super sensitive sensors mix graphene in Silly Putty, an unlikely combination that he tried after reading (on Hackaday, no less) about similar experiments at Trinity College resulting in Gputty. The Gputty was highly sensitive to pressure, and so it appears is his DIY version called Goophene. At Trinity they claimed to be able to record the footsteps of a spider, so detecting ant stomping didn’t seem too far-fetched. You can see a video of the result, below.

Continue reading “DIY Graphene Putty Makes Super Sensitive Sensor”

Tiny Programming Language In 25 Lines Of Code

There are certain kinds of programs that fascinate certain kinds of software hackers. Maybe you are into number crunching, chess programs, operating systems, or artificial intelligence. However, on any significant machine, most of the time those activities will require some sort of language. Sure, we all have some processor we can write hex code for in our head, but you really want at least an assembler if not something sturdier. Writing languages can be addictive, but jumping right into a big system like gcc and trying to make changes is daunting for anyone. If you want a gentle introduction, check out [mgechev’s] language that resides in 25 lines of Javascript.

The GitHub page bills it as a tiny compiler, although that is a bit misleading and even the README says it is a transpiler. Actually, the code reads a simple language, uses recursive descent parsing to build a tree, and then uses a “compiler” to convert the tree to JavaScript (which can then be executed, of course). It can also just interpret the tree and produce a numerical answer.

Continue reading “Tiny Programming Language In 25 Lines Of Code”