Minimal Blinky Project Makes The Chip The Circuit Board

We’ve got a thing for projects that have no real practical value but instead seek to answer a simple yet fundamental question: I wonder if I can do that? This dead-bug style 555 blinky light is one of those projects, undertaken just to see how small a circuit can be. Pretty small, as it turns out, and we bet it can get even smaller.

[Danko]’s minimal circuit is about as small as possible for the DIP version of the venerable 555 chip. The BOM is stripped to the bone: just the chip, three resistors, a capacitor, and an LED. All the discrete components are SMDs in 0805. The chip’s leads are bent around the package to form connections, and the SMDs bridge those “traces” to complete the circuit. [Danko] shows the build in step-by-step detail in the video below. There’s some fairly fine work here, but we can’t help wondering just how far down the scale this could be pushed. We know someone’s made a smaller blinky using a tiny microcontroller, but we’d love to see this tried with the BGA version of the chip which is only 1.4 mm on a side.

Cheers to [Danko] for trying this out and having some fun with an old chip. He seems to have a bit of a thing for the 555; check out this cute robot sculpture that’s built around the chip.

Continue reading “Minimal Blinky Project Makes The Chip The Circuit Board”

DIY Puff-Suck Interface Aims For Faster Text Input

Puff and Suck (or Sip and Puff) systems allow people with little to no arm mobility to more easily interact with computers by using a straw-like unit as an input device. [Ana] tells us that the usual way these devices are used to input text involves a screen-based keyboard; a cursor is moved to a letter using some method (joystick, mouse emulator, buttons, or eye tracking) and that letter is selected with a sip or puff into a tube.

[Ana] saw such systems as effective and intuitive to use, but also limited in speed because there’s only so fast that one can select letters one at a time. That led to trying a new method; one that requires a bit more work on the user’s part, but the reward is faster text entry. The Puff-Suck Interface for Fast Text Input turns a hollow plastic disk and a rubber diaphragm into bipolar pressure switch, able to detect three states: suck, puff, and idle. The unit works by having an IR emitter and receiver pair on each side of a diaphragm (one half of which is shown in the image above). When air is blown into or sucked out of the unit, the diaphragm moves and physically blocks one or the other emitter-receiver pair. The resulting signals are interpreted by an attached Arduino.

How does this enable faster text input? By throwing out the usual “screen keyboard” interface and using Morse code, with puffs as dots and sucks as dashes. The project then acts as a kind of Morse code keyboard. It does require skill on the user’s part, but the reward is much faster text entry. The idea got selected as a finalist in the Human-Computer Interface Challenge portion of the 2018 Hackaday Prize!

Morse code may seem like a strange throwback to some, but not only does the bipolar nature of [Ana]’s puff-suck switch closely resemble that of Morse code input paddles, it’s also easy to learn. Morse code is far from dead; we have pages of projects and news showing its involvement in everything from whimsical projects to solving serious communication needs.

Maker Faire NY: Where Robots Come Out To Play

There was an unbelievable amount of stuff on display at the 2018 World Maker Faire in New York. Seriously, an unreal amount of fantastically cool creations from all corners of the hacker and maker world: from purely artistic creations to the sort of cutting edge hardware that won’t even be on the rest of the world’s radar for a year or so, and everything in between. If you’ve got a creative bone in your body, this is the place for you.

But if there was one type of creation that stood out amongst all others, a general “theme” of Maker Faire if you will, it was robotics. Little robots, big robots, flying robots, battling robots, even musical robots. Robots to delight children of all ages, and robots to stalk the darkest corners of their nightmares. There were robots for all occasions. Probably not overly surprising for an event that has a big red robot as its mascot, but still.

There were far too many robots to cover them all, but the following is a collection of a few of the more interesting robotic creations we saw on display at the event. If you’re the creator of one of the robots we didn’t get a chance to get up close and personal with in our whirlwind tour through the Flushing Meadows Corona Park, we only ask that you please don’t send it here to exact your revenge. We’re very sorry. (Just kidding, if you have a robot to show off drop a link in the comments!)

Continue reading “Maker Faire NY: Where Robots Come Out To Play”

Join Hackaday And Tindie This Thursday At Open Hardware Summit

This weekend Hackaday and Tindie will be trekking out to beautiful Cambridge, Massachusetts, for the greatest congregation of Open Source hardware enthusiasts on the planet. This is the Open Hardware Summit. It’s every year, most of the time in different places, and this year it’s back in the hallowed halls of MIT. Somebody put a car on the roof before we do.

The schedule for this year’s Open Hardware Summit is stuffed to the gills with interesting presentations sure to satiate every hardware nerd. We’ve got talks on Open Source Software Defined Radio, and the people behind the Hackaday Prize entry Programmable Air will be there talking about controlling soft robotics.

Really, though, this is an extravaganza filled with the people who make things, and here you’re not going to find a better crew. At every Open Hardware Summit we’ve attended, you can’t turn your head without locking eyes with someone with an interesting story of hardware heroics to tell.

This is, without a doubt, the greatest gathering of the people behind all your favorite hardware designs. The greats of 3D printing will be there, we’re going to get an update on the now two-year-old Open Hardware Certification program (hint: great success!), and there’s an awesome badge, as always. There will be some extra-special Hackaday swag in the goodie bags, sure to be a collectable. We’re going to be there with boots on the ground, but it’s still not too late to get tickets if you’re in the Boston area.

Buy A Baofeng While You Still Can? FCC Scowls At Unauthorized Frequency Transmitters

There was a time when a handheld radio transceiver was an object of wonder, and a significant item for any radio amateur to own. A few hundred dollars secured you an FM walkie-talkie through which you could chat on your local repeater, and mobile radio was a big draw for new hams. Thirty years later FM mobile operation may be a bit less popular, but thanks to Chinese manufacturing the barrier to entry is lower than it has ever been. With extremely basic handheld radios starting at around ten dollars and a capable dual-bander being yours for somewhere over twice that, most licencees will now own a Baofeng UV5 or similar radio.

The FCC though are not entirely happy with these radios, and QRZ Now are reporting that the FCC has issued an advisory prohibiting the import or sale of devices that do not comply with their rules. In particular they are talking about devices that can transmit on unauthorised frequencies, and ones that are capable of transmission bandwidths greater than 12.5 kHz.

We’ve reported before on the shortcomings of some of these radios, but strangely this news doesn’t concern itself with their spurious emissions. We’re guessing that radio amateurs are not the problem here, and the availability of cheap transceivers has meant that the general public are using them for personal communication without a full appreciation of what frequencies they may be using. It’s traditional and normal for radio amateurs to use devices capable of transmitting out-of-band, but with a licence to lose should they do that they are also a lot more careful about their RF emissions.

Read the FCC statement and you’ll learn they are not trying to restrict the sale of ham gear. However, they are insisting that imported radios that can transmit on other frequencies must be certified. Apparently, opponents of these radios claim about 1 million units a year show up in the US, so this is a big business. The Bureau warns that fines can be as high as $19,639 per day for continued marketing and up to $147,290 — we have no idea how they arrive at those odd numbers.

So if you’re an American who hasn’t already got a Baofeng or similar, you might be well advised to pick one up while you still can.

UV5-R image via PE1RQM

Productivity, Unfinished Projects, And Letting Go

Most of us have been there, some projects just don’t get finished. Everyone shelves an in-progress build from time to time, and some hackers drop almost every project for fully finishing it. Why does it happen? What can we do about it? Or does it even matter? My own most memorable one is the wine glass rack I was making for my sister’s birthday, still sitting incomplete on a shelf eleven years later.

The answer may lie in what you consider to be a “done” project. Is it a fully completed build with every possible feature implemented and polished? With that rubric you could be counting all of your completed projects on one hand. What are you really getting out of your personal projects? It’s an interesting topic to consider as pivoting your mindset can end up boosting your productivity. So let’s dig in!

Continue reading “Productivity, Unfinished Projects, And Letting Go”

Trials And Tribulations In Sending Data With Wires

When working on a project that needs to send data from place to place the distances involved often dictate the method of sending. Are the two chunks of the system on one PCB? A “vanilla” communication protocol like i2c or SPI is probably fine unless there are more exotic requirements. Are the two components mechanically separated? Do they move around? Do they need to be far apart? Reconfigurable? A trendy answer might be to add Bluetooth Low Energy or WiFi to everything but that obviously comes with a set of costs and drawbacks. What about just using really long wires? [Pat] needed to connect six boards to a central node over distances of several feet and learned a few tricks in the process.

When connecting two nodes together via wires it seems like choosing a protocol and plugging everything in is all that’s required, right? [Pat]’s first set of learnings is about the problems that happen when you try that. It turns out that “long wire” is another way to spell “antenna”, and if you happen to be unlucky enough to catch a passing wave that particular property can fry pins on your micro.

Plus it turns out wires have resistance proportional to their length (who would have though!) so those sharp square clock signals turn into gently rolling hills. Even getting to the point where those rolling hills travel between the two devices requires driving drive the lines harder than the average micro can manage. The solution? A differential pair. Check out the post to learn about one way to do that.

It looks like [Pat] needed to add USB to this witches brew and ended up choosing a pretty strange part from FTDI, the Vinculum II. The VNC2 seemed like a great choice with a rich set of peripherals and two configurable USB Host/Peripheral controllers but it turned out to be a nightmare for development. [Pat]’s writeup of the related troubles is a fun and familiar read. The workaround for an incredible set of undocumented bad behaviors in the SPI peripheral was to add a thick layer of reliability related messaging on top of the physical communication layer. Check out the state machine for a taste, and the original post for a detailed description.