Adding USB-C To The TS100

The TS100 is a popular entry into the new breed of small temperature-controlled soldering irons that, at least for some of us, have started to replace the bulky soldering stations of old. Unfortunately, one downside of this particular model is the need to plug it into a fairly ungainly laptop-style power supply, which certainly hinders its otherwise portable nature. But [Dennis Schneider] has come up with a very slick solution to that problem by adding a USB-PD module to his TS100.

The idea here is very simple: just remove the original DC barrel connector, and in its place install a USB-PD trigger module. In practice it took more than a little fiddling, cutting, persuasion, and creative soldering (ironically, with a soldering station), but the end result does look quite professional.

It helps that the USB-PD module [Dennis] used was almost the exact same width as the TS100 PCB, meaning that the modified iron could go back into its original case. Though as we saw not so long ago, there’s a growing community of 3D printed replacement cases should you select a trigger module that doesn’t so neatly fit the footprint of the original board. Or if you didn’t want to modify the iron at all, you could always just make an external adapter.

Those that have some experience with these irons might be wondering what the point of modifying the TS100 to take USB-C is when we already have the TS80. As it turns out, while the TS80 is using a USB-C connector it doesn’t actually use USB-PD, so its not taking advantage of the enhanced power delivery capabilities. We know, it’s all kind of confusing.

Announcing The “Take Flight With Feather” Contest

The Adafruit Feather is the latest platform for microcontroller development, and companies like Particle, Sparkfun, Seeed Studios, and of course Adafruit are producing Feather-compatible devices for development and prototyping. Now it’s your turn! The Take Flight With Feather contest challenges you to design a board to fit in the Feather ecosystem, with the grand prize of having your boards manufactured for you and listed for sale on Digi-Key.

To get started, take a look at the current Feather ecosystem and get acquainted with this list of examples. From there, get to work designing a cool, useful, insane, or practical Feather. But keep in mind that we’re looking for manufacturability. Electron savant Lady Ada will be judging each board on the basis of manufacturability.

What’s a good design? We’re looking for submissions in the following categories:

  • The Weirdest Feather — What’s the most ridiculous expansion board you can come up with?
  • You’ll Cut Yourself On That Edge — We’re surrounded with bleeding-edge tech, what’s the coolest use of new technology?
  • Retro Feather — Old tech lives on, but can you design a Feather to interact with it? Is it even possible to build a vampire Ethernet tap or an old acoustically-coupled modem?
  • Assistive Tech — Build a Feather to help others. Use technology to improve lives.
  • Wireless Feather — Add a new wireless technology to the Feather ecosystem

In addition to the grand prize winner, five other entries (one in each of the 5 categories above) will receive $100 Tindie gift certificates. The contest begins now and runs through December 31st. To get started, start a project on Hackaday.io and use the “Submit Project To” dropdown box on the left sidebar of your project page to enter it in the contest.

FBus: An Extensible And Easily Configurable FPGA Based DAQ

[flow] is a little disillusioned with commercial Data Acquisition Systems (DAQs) and channeled his frustration into his own, very cool, FPGA based solution.

The project takes form as a back plane into which various cards can be slotted. The the interface is just a PCI-e connector. If you need analog input, simply insert the card for it. Ethernet output? Same process. Modularity and expandability are the themes here.

[flow] already has projects in mind for his new DAQ. He’s using it to build an inverted pendulum. However, his planned cards really show the possibilities, anything from a logic analyzer card to an HDMI Output card allow for a wide array of configurations. There is also a small suite of tools which makes this process relatively easy to manage.

We can definitely see this evolving into a useful tool on our bench for prototyping.

DSP Spreadsheet: Frequency Mixing

Circuit simulation and software workbooks like Matlab and Jupyter are great for being able to build things without a lot of overhead. But these all have some learning curve and often use clever tricks, abstractions, or library calls to obscure what’s really happening. Sometimes it is clearer to build math models in a spreadsheet.

You might think that spreadsheets aren’t built for doing frequency calculation and visualization but you’re wrong. That’s exactly what they’re made for — performing simple but repetative math and helping make sense of the results.

In this installment of the DSP Spreadsheet series, I’m going to talk about two simple yet fundamental things you’ll need to create mathematical models of signals: generating signals and mixing them. Since it is ubiquitous, I’ll use Google Sheets. Most of these examples will work on any spreadsheet, but at least everyone can share a Google Sheets document. Along the way, we’ll see a neat spreadsheet trick I should probably use more often.

Continue reading “DSP Spreadsheet: Frequency Mixing”

Hackaday Podcast 042: Capacitive Earthquakes, GRBL On ESP32, Solenoid Engines, And The TI-99 Space Program

Hackaday Editors Elliot Williams and Mike Szczys talk turkey on the latest hacks. Random numbers, art, and electronic geekery combine into an entropic masterpiece. We saw Bart Dring bring new life to a cool little multi-pen plotter from the Atari age. Researchers at UCSD built a very very very slow soft robot, and a broken retrocomputer got a good dose of the space age. A 555 is sensing earthquakes, there’s an electric motor that wants to drop into any vehicle, and did you know someone used to have to read the current time into the telephone ad nauseam?

Take a look at the links below if you want to follow along, and as always tell us what you think about this episode in the comments!

Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Direct download (60 MB or so.)

Continue reading “Hackaday Podcast 042: Capacitive Earthquakes, GRBL On ESP32, Solenoid Engines, And The TI-99 Space Program”

Ploopy Open Source Trackball Keeps Rolling Along

We’ll be honest. When we first heard about a mouse, we weren’t convinced. The argument was that business people weren’t familiar with computers. That didn’t ring true since every business person in the last century had at least seen a typewriter keyboard, but most of them had never seen a mouse before the 1980s. The mouse has since become totally ubiquitous, so presumably, it was the right choice. However, if you are a serious touch typer, it is annoying to have to move your hands off the keyboard to a different location each time. There are several solutions for that, but the oldest one is probably the trackball. Ploopy is an open source trackball you can build yourself and it looks pretty capable.

While we aren’t wild about the name, Ploopy looks pretty good and is one of those projects that would have been very difficult ten years ago. It requires two PC boards. Those used to be hard to get. It also requires some very customized plastic parts. Getting a handful of plastic parts made used to be hard, too. But now you probably have a 3D printer that is just begging for something to do.

Continue reading “Ploopy Open Source Trackball Keeps Rolling Along”

This Week In Security: Project Zero’s IPhone, BBC The Onion, Rooting Androids, And More

The always interesting Project Zero has a pair of stories revolving around security research itself. The first, from this week, is all about one man’s quest to build a debug iPhone for research. [Brandon Azad] wanted iOS debugging features like single-stepping, turning off certain mitigations, and using the LLDB debugger. While Apple makes debug iPhones, those are rare devices and apparently difficult to get access to.

[Brandon] started looking at the iBoot bootloader, but quickly turned his attention to the debugging facilities baked into the Arm chipset. Between the available XNU source and public Arm documentation, he managed to find and access the CoreSight debug registers, giving him single-step control over a core at a time. By triggering a core halt and then interrupting that core during reset, he was able to disable the code execution protections, giving him essentially everything he was looking for. Accessing this debug interface still requires a kernel level vulnerability, so don’t worry about this research being used maliciously.

The second Google Zero story that caught my eye was published earlier in the month, and is all about finding useful information in unexpected places. Namely, finding debugging symbols in old versions of Adobe Reader. Trying to understand what’s happening under the hood of a running application is challenging when all you have is a decompiler output. Adobe doesn’t ship debug builds of Reader, and has never shipped debug information on Windows. Reader has been around for a long time, and has supported quite a few architectures over the years, and surprisingly quite a few debug builds have been shipped as a result.

How useful could ancient debugging data be? Keep in mind that Adobe changes as little as possible between releases. Some code paradigms, like enums, tend to be rather static as well. Additional elements might be added to the end of the enum, but the existing values are unlikely to change. [Mateusz Jurczyk], the article’s author, then walks us through an example of how to take that data and apply it to figuring out what’s going on with a crash. Continue reading “This Week In Security: Project Zero’s IPhone, BBC The Onion, Rooting Androids, And More”