screenshow showing the supposed AllSpice interface. It resembles the GitHub interface, and shows a pull request open to add some ESD protection to a device.

AllSpice Building A Hardware Development Ecosystem For Companies

February 27, 2022 by Arya Voronova 7 Comments

In our “hardware development gets serious” news, we’ve recently learned about AllSpice, a startup building hardware development collaboration infrastructure for companies. Hardware developers are great at building hardware tools for themselves, but perhaps not always so when it comes to software, and AllSpice aims to fill that gap at the “hardware company” level. Nowadays, what commonly happens is that software development tools and integrations are repurposed for hardware needs, and the results aren’t always as stellar as they get in the software world. In other words, AllSpice is learning from the positive outcomes of software industry and building a platform that takes the best parts from these tools, aiming to get to similarly positive outcomes in areas where currently hardware team experiences are lacking.

What AllSpice is building seems to be an umbrella platform designed to augment, integrate and hook into a slew of different already-developed platforms like GitHub, GitLab, Jira (and some other ones), and add much-needed features that large-scale hardware developers can’t afford to maintain and develop themselves. “Design review by screenshot” isn’t unheard of in hardware circles, and likely a thing that everyone of us with hardware collaboration experience has partaken in. On a company scale, there’s a myriad of hardware-related problems like that to solve and polish over.

Continue reading “AllSpice Building A Hardware Development Ecosystem For Companies” →

Pick Up The Ball And Run With It

September 11, 2021 by Mike Szczys 2 Comments

Once in a while we get to glimpse how people build on each other’s work in unexpected and interesting ways. So it is with the GateBoy project, a gate-level emulator built from die shots of the original Game Boy processor. The thing is, [Austin Appleby] didn’t have to start by decapping and taking photos of the chip. He didn’t even have to make his own schematics by reverse engineering those structures. Someone else had already done that and made it available for others to use. A couple of years back, [Furrtek] started manually tracing out the DMG chip and posted schematics to the DMG-CPU-Inside repo, kindly licensing it as CC-BY-SA 4.0 to let people know how they can use the info.

But playing Game Boy games isn’t actually the end game of [Austin’s] meticulous gate-level recreation. He’s using it to build “a set of programming tools that can bridge between the C/C++ universe used by software and the Verilog/VHDL universe used by hardware.” A new tool has been born, not for gaming, but for converting a meta language that assigns four-letter codes to gate structures (somewhat reminiscent of DNA sequences) and will eventually convert them to your choice of C++ or a Hardware Description Language for use with FPGAs.

The open source community is playing four-dimensional football. Each project moves the ball downfield, but some of them add an additional goal in an alternate hardware universe — advancing the aims of both (like finding and fixing some errors in [Furrtek’s] original schematics).

Of course the real challenge is getting the word out that these projects exist and can be useful for something you’re working on. For instance, [Neumi’s] depth sounding rowboat allows an individual to make detailed depth maps of lakes, rivers, and the like. It was in the comments that the OpenSeaMap project was brought up — a site working to create crowd sourced waterway charts. It’s the perfect place for [Neumi] to get inspiration, and help move that ball toward a set of goals.

How do we get the word out so more of these connections happen? We’ll do our part here at Hackaday. But it’s the well-document and thoughtfully-licensed projects that set the up playing field in the first place.

99% Inspiration, 99% Perspiration, And 99% Collaboration

March 6, 2021 by Elliot Williams 52 Comments

I was watching an oldish TEDx talk with Rodney Mullen, probably the most innovative street skater ever, but that’s not the point, and it’s not his best talk either. Along the way, he makes a claim that ideas — in particular the idea that a particular skateboard trick is even possible — are the most important thing.

His experience, travelling around the world on skateboard tours, is that there are millions of kids who are talented enough that when they see a video demonstrating that a particular trick idea is possible, they can replicate it in short order. Not because the video showed them how, but because it expanded their mind’s-eye view of what is possible. They were primed, and so what pushed them over the edge was the inspiration.

On the other side of the street, we’ve got Thomas Edison and his “1% inspiration, 99% perspiration” routine. Edison famously tried a bazillion filament recipes ~~before settling on tungsten~~, and attributes his success to “putting his time in” or “good old-fashioned hard work” or similar. So who’s right?

The inventor of Casper Slide and the phonograph are both right. Rodney is taking it for granted that these kids have put their time in; they are skaters after all, they skate. He doesn’t see the 99% perspiration because it is the natural background, while the inspiration flashes out in Eureka moments.

Similarly, Thomas E. way underestimates inspiration. He’s already fixated on this novel idea to take an arc lamp and contain it in a glass envelope — that’s what he’s spending all of his perspiration on, after all. But without that key inspiration, all he’d be is sweaty.

And they’re also both wrong! They’re both missing a third ingredient: collaboration. Certainly Mullen, who spent his life hanging out with other skaters, teaching them what he knows, and learning from them in turn, wouldn’t say the community of skaters didn’t shape him. Even in the loner’s sport of skating, nobody is alone. And Edison? His company profited greatly from broader advances in science, and the scientific literature. Menlo Park existed to take bright, well-trained minds and put them all in one place, sharing, teaching, and working together. It embodied the idea of collaborative innovation, and that’s where some of his best work was done.

So I’m with Isaac Newton, “standing on the shoulders of giants“. Success is 99% collaboration. This leaves us with one problem: the percentages don’t add up. But that’s alright by me.

Hackaday Links: December 8, 2019

December 8, 2019 by Dan Maloney 14 Comments

Now that November of 2019 has passed, it’s a shame that some of the predictions made in Blade Runner for this future haven’t yet come true. Oh sure, 109 million people living in Los Angeles would be fun and all, but until we get our flying cars, we’ll just have to console ourselves with the ability to “Enhance!” photographs. While the new service, AI Image Enlarger, can’t tease out three-dimensional information, the app is intended to sharpen enlargements of low-resolution images, improving the focus and bringing up details in the darker parts of the image. The marketing material claims that the app uses machine learning, and is looking for volunteers to upload high-resolution images to improve its training set.

We’ve been on a bit of a nano-satellite bender around here lately, with last week’s Hack Chat discussing simulators for CubeSats, and next week’s focusing on open-source thrusters for PocketQube satellites. So we appreciated the timing of a video announcing the launch of the first public LoRa relay satellite. The PocketCube-format satellite, dubbed FossaSat-1, went for a ride to space along with six other small payloads on a Rocket Lab Electron rocket launched from New Zealand. Andreas Spiess has a short video preview of the FossaSat-1 mission, which was designed to test the capabilities of a space-based IoT link that almost anyone can access with cheap and readily available parts; a ground station should only cost a couple of bucks, but you will need an amateur radio license to uplink.

We know GitHub has become the de facto standard for source control and has morphed into a collaboration and project management platform used by everybody who’s anybody in the hacking community. But have you ever wished for a collaboration platform that was a little more in tune with the needs of hardware designers? Then InventHub might be of interest to you. Currently in a limited beta – we tried to sign up for the early access program but seem to have been put on a waiting list – it seems like this will be a platform that brings versioning directly to the ECAD package of your choice. Through plugins to KiCad, Eagle, and all the major ECAD players you’ll be able to collaborate with other designers and see their changes marked up on the schematic — sort of a visual diff. It seems interesting, and we’ll be keeping an eye on developments.

Amazon is now offering a stripped-down version of their Echo smart speaker called Input, which teams up with speakers that you already own to satisfy all your privacy invasion needs on the super cheap — only $10. At that price, it’s hard to resist buying one just to pop it open, which is what Brian Dorey did with his. The teardown is pretty standard, and the innards are pretty much what you’d expect from a modern piece of surveillance apparatus, but the neat trick here involved the flash memory chip on the main board. Brian accidentally overheated it while trying to free up the metal shield over it, and the BGA chip came loose. So naturally, he looked up the pinout and soldered it to a micro-SD card adapter with fine magnet wire. He was able to slip it into a USB SD card reader and see the whole file system for the Input. It was a nice hack, and a good teardown.

Forty Four Hackers And A Hatch: Progress Egress Takes Off

July 3, 2019 by Dan Maloney 14 Comments

The 50th anniversary of the first Moon landing is rapidly approaching, and uber space-nerd Adam Savage is in the thick of the celebration of all the amazing feats of engineering that made humanity’s first steps out of the cradle possible. And in a grand and very hacker-friendly style, we might add, as his Project Egress aims to build a full-scale replica of the Apollo 11 Command Module Columbia’s hatch.

Continue reading “Forty Four Hackers And A Hatch: Progress Egress Takes Off” →

Life On Contract: Product Development Lessons Big And Small

June 5, 2019 by Bob Baddeley 7 Comments

Developing a product and getting it out there to build a business is really hard. Whether it’s a single person acting alone to push their passion to the public, or a giant corporation with vast resources, everyone has to go through the same basic steps, and everyone needs to screw those steps up in the same way.

The reality is that the whole process needs to involve lots of aspects in order to succeed; small teams fail by not considering or dedicating resources to all of those aspects, and large teams fail by not having enough communication between the teams working on those pieces. But in truth, it’s a balance of many aspects that unlock a chance at a successful product. It’s worth recognizing this balance and seeking it out in your own product development efforts, whether you’re a one-engineer juggernaut or a large, established company.

Continue reading “Life On Contract: Product Development Lessons Big And Small” →

Friday Hack Chat: How Do You Collaborate With Hardware?

February 7, 2018 by Brian Benchoff 6 Comments

The world of Open Source software is built on collaboration. In one corner of the world, someone can fix a bug in a piece of software, and push it up to the gits. In another part of the world, someone else can put that fix into the next release, and soon everyone has newer, better software. The Internet, or the ability to rapidly transmit text and binary files, has made this all possible.

Hardware is another story. There’s a financial barrier to entry. Not only do you need a meter and a good iron, you’re probably going to need oscilloscopes, logic analyzers, and a bunch of other expensive tools. You’ll need to buy your BOM. If you’re using a PIC, it might be a good idea to buy the good compiler. Hardware is hard and expensive, and all those software devs who complain don’t know what they’re talking about. Collaborating on hardware is much more difficult than pushing some code up to the cloud.

For this week’s Hack Chat, we’re going to be talking about collaborating on hardware projects. This is a deep dive on how to make collaboration with physical objects work, and this week we’re going to be learning from some of the best.

Our guests for this week’s Hack Chat are Pete Dokter and Toni Klopfenstein of SparkFun Electronics. Pete is formerly the Director of Engineering at SparkFun and now the Brand Ambassador for SparkFun Electronics. He hosts the According to Pete video series expounding on various engineering principles and seriously needs a silverburst Les Paul and a Sunn Model T. Toni is currently the product development manager at SparkFun. She’s served on the Open Source Hardware Association Board and participates in the Open Hardware Summit yearly. In her free time, she spends fifty weeks out of the year finding dust in her art and electronics projects.

During this chat, we’re going to be discussing what makes a collaborative hardware project, how to make distributed development work for your team, and the limits of what you can do with several hardware engineers separated by thousands of miles. This is a hard problem, much harder than a distributed team of software engineers, and a fantastic discussion for all.

Our Hack Chats are live community events on the Hackaday.io Hack Chat group messaging. This Hack Chat is going down Friday, February 9th at noon, Pacific time. Time Zones got you down? Here’s a handy countdown timer!

Click that speech bubble to the left, and you’ll be taken directly to the Hack Chat group on Hackaday.io.

You don’t have to wait until Friday; join whenever you want and you can see what the community is talking about.