Bill Gross On Why Your Startup Will Succeed

Bill Gross is one of the great heros when it comes to technology incubators. Twenty years ago, he founded Idealab, a business whose business plan is to create more businesses. This started out with just a handful of companies in 1996, and has since gone on to found 150 companies, that have collectively raised three and a half billion dollars. Out of these companies, more than half have either gone through successful IPOs and acquisitions, or are currently operating. That investment has generated a 13.5x return, and created more than 10,000 jobs.

Obviously, when you want to talk about what goes into a successful startup, Bill Gross is the person you want to talk to. We were happy to have him Keynote the Hackaday Superconference this year, and the lessons he shared might surprise you, especially if you’re interested in starting your own business.

Continue reading “Bill Gross On Why Your Startup Will Succeed” →

Designing Space-Rated PCBs

We’ve reduced printed circuit board design to practice so much that we hardly give a thought to the details anymore. It’s so easy to bang out a design, send it to a fab house, and have ten boards in your hands in no time at all. All the design complexities are largely hidden from us, abstracted down to a few checkboxes on the vendor’s website.

There’s no doubt that making professional PCB design tools available to the hobbyist has been a net benefit, but there a downside. Not every PCB design can be boiled down to the “one from column A, one from column B” approach. There are plenty of applications where stock materials and manufacturing techniques just won’t cut it. PCBs designed to operate in space is one such application, and while few of us will ever be lucky enough to have a widget blasted to infinity and beyond, learning what’s behind space-rated PCBs is pretty interesting.

Continue reading “Designing Space-Rated PCBs” →

Hackaday Links Column Banner

Hackaday Links: November 25, 2018

Bad Obsession Motorsport have been stuffing the engine and suspension from a 4WD Celica into an old Mini since forever. It is a wonderful homage to Police Squad and some of the best machining and fabrication you’ll see on YouTube. The latest episode tackled the electrical system and how to drive an alternator in an extremely cramped engine bay. The solution was a strange flex-shaft confabulation, and now the Bad Obsession Motorsport guys have a video on how they attached an alternator to a car where no alternator should go. It’s forty minutes of machining, go watch it.

Last Friday was Black Friday, and that means it’s time to CONSUME CONSUME CONSUME. Tindie’s having a sale right now, so check that out.

I’m the future of autonomous flight! This week, I got a market research survey in my email from Uber, wanting me to give my thoughts on autonomous ridesharing VTOL aircraft. Uber’s current plan for ridesharing small aircraft involves buying whatever Embraer comes up with (Uber is not developing their own aircraft), not having pilots (this will never get past the FAA), and turning a random parking lot in LA into the busiest airport in the world (by aircraft movements, which again is something that will never get past the FAA). Needless to say, this is criminally dumb, and I’m more than happy to give my thoughts. Below are the relevant screencaps of the survey:

The crux of this survey is basic market research; how much would I pay for a VTOL ride sharing service versus buying a new (autonomous) car versus using an autonomous Uber. You’ve also got a Likert scale thingy asking me if I’m comfortable flying in a battery-powered aircraft. Protip: I highly doubt anyone given this survey has flown in a battery-powered aircraft. Proprotip: the easiest way to screw up the scoring for a Likert scale is to answer ‘1’ for the first question, ‘2’ for the second, etc., and wrap back around to ‘1’ for the sixth question.

Don’t worry, though: I answered all the questions truthfully, but Uber Air will never happen. The FAA won’t let this one fly, and no company will ever carry passengers without a licensed pilot on board.

Fail Of The Week: Did My Laser Cutter Tube Really Burn Out?

All the cool kids are doing it these days, or more like for many years now: you can get a laser cutter for a song if you don’t mind doing your own repairs and upgrades — you know, being a hacker. The downside is that some failures can really ruin your day. This is what [Erich Styger] encountered with his cutter that is just a bit more than a year old. This Fail of the Week looks at the mysterious death of a CO2 laser tube.

This is the infamous K40 laser cutter. Our own [Adam Fabio] just took one on a couple of months back and [Erich] even references Hackaday coverage of the K40 Whisperer project as what pushed him over the edge to make the purchase. We’ve followed his blog as he acquired the cutter and made upgrades along the way, but after an estimated 500 hours of use, a horrible teeth-gnashing screech sprung forth from the machine. [Erich’s] reaction was to hit the e-stop; that’s certainly why it’s there.

Chasing down the problem is a story well-told, but as is often the case with these FotW articles, in the end what caused the failure is not entirely known. We’d love to hear what you think about it in the comments below.

The investigation began at the power supply for the laser, but that didn’t yield any answers. Next he moved to the tube itself, noticing that the wire connection to the tube’s anode wasn’t soldered. The anode is an unknown material he suspects to be graphite and he found a video showing the “soldering” process for connecting a wire. (We added quotes to that as the video he linked doesn’t actually solder anything but the wrapped wire strands themselves.) The solution he found is a great tip to take away from the story. It’s a socket by TE Connectivity to which he soldered the wire. Assuming it’s power rated for the task, and won’t fall off during normal operation, this is a great way to do it.

But we digress. Even with the connection made, the old tube had to be replaced with a new one. It’s also notable that the portion of that anode inside the bad tube is orange in color when a new tube would be black like the part on the outside. Does this hint at why that tube died, and could this have been avoided? If you have insight, help us learn from this failure by leaving a comment below.

The Linux Throwie: A Non-Spacefaring Satellite

Throwies occupy a special place in hardware culture — a coin cell battery, LED, and a magnet that can be thrown into an inaccessible place and stick there as a little beacon of colored light. Many of us will fondly remember this as a first project. Alas, time marches inevitably on, and launching cheerful lights no longer teaches me new skills. With a nod to those simpler times, I’ve been working on the unusual idea of building a fully functional server that can be left in remote places and remain functional, like a throwie (please don’t actually throw it). It’s a little kooky, yet should still deliver a few years of occasional remote access if you leave it somewhere with sunlight.

A short while ago, I described the power stages for this solar-powered, cloud accessible Linux server. It only activates on demand, so a small solar cell and modest battery are sufficient to keep the whole show running.

Where we left off, I had a solar cell that could charge a battery, and provide regulated 12 V and 5 V output. For it to be a functional device, there are three high level problems to solve:

  1. It must be possible to set up the device without direct physical access
  2. You must be able to remotely turn it on and off as needed.
  3. It needs to be accessible from the Internet.

The funny thing is, this hardware reminds me of a satellite. Of course it’s not meant to go into space, but I do plan to put it somewhere not easy to get to again, it runs off of solar power, and there’s a special subsystem (ESP8266) to tend the power, check for remote activation, and turn the main computer (Raspberry Pi 3) on and off as necessary. This sounds a lot like space race tech, right?

As I have a bit more code than usual to share with you today, I’ll discuss the most interesting parts, and provide links to the full firmware files at the end of the article.

Continue reading “The Linux Throwie: A Non-Spacefaring Satellite” →

Of Roach Killer And Rust Remover: Sam Zeloof’s Garage-Made Chips

A normal life in hacking, if there is such a thing, seems to follow a predictable trajectory, at least in terms of the physical space it occupies. We generally start small, working on a few simple projects on the kitchen table, or if we start young enough, perhaps on a desk in our childhood bedroom. Time passes, our skills increase, and with them the need for space. Soon we’re claiming an unused room or a corner of the basement. Skills build on skills, gear accumulates, and before you know it, the garage is no longer a place for cars but a place for pushing back the darkness of our own ignorance and expanding our horizons into parts unknown.

It appears that Sam Zeloof’s annexation of the family garage occurred fairly early in life, and to a level that’s hard to comprehend. Sam seems to have caught the hacking bug early, and by the time high school rolled around, he was building out a remarkably well-equipped semiconductor fabrication lab at home. Sam has been posting his progress regularly on his own blog and on Twitter, and he dropped by the 2018 Superconference to give everyone a lesson on semiconductor physics and how he became the first hobbyist to produce an integrated circuit using lithographic processes.

Continue reading “Of Roach Killer And Rust Remover: Sam Zeloof’s Garage-Made Chips” →

Fail Of The Week: When The Epoxy-Coated Chip Is Conductive

Every once in a while, you’ll find some weirdness that will send your head spinning. Most of the time you’ll chalk it up to a bad solder joint, some bad code, or just your own failings. This time it’s different. This is a story of weirdness that’s due entirely to a pin that shouldn’t be there. This is a package for an integrated circuit that has a pin zero.

The story begins with [Erich] building a few development boards for the Freescale Kinetis K20 FPGA. This is a USB-enabled microcontroller, and by all accounts, a worthwhile effort. So far, so good. The problem with the prototype boards was soon apparent. On some of the boards, the external 32 kHz oscillator was not starting. Resoldering the oscillator or microcontroller sometimes solved the problem, but not always. This is troubling, because that means the issue isn’t code, and it’s not the PCB. This is going to take a deep dive and a good inspection microscope.

One of [Erich]’s friends, [Christian B] somehow found the problem. When the Freescale K40 is manufactured, the die is carefully laid in a chip carrier and coated with epoxy, putting it in a small QFN package. The problem is, there’s an extra connection sticking out of one corner of this chip. This is just an artifact of the chip carrier, but if you leave exposed metal connected to ground, something is eventually going to go wrong.

The best guess [Erich] has is that this additional connection is from the manufacturing and packaging process, with the exposed metal pad in this application being bridged to an adjacent pad. Now, if there’s one failure to [Erich]’s design, it’s that the trace comes out of the pin on the adjacent pad at 90 degrees; this isn’t a best practice, but most of the time you can get away with it. This time, though, somebody got burned.

We don’t know how [Christian] ever found this issue. When you look at a tiny QFN package, you don’t expect there to be an extra pin attached to ground that can be easily bridged with a bit of solder paste. It’s either a lot of luck or skill to find this problem, but it’s a great example of the weird things you have to look out for.