All About USB-C: Connector Mechanics

There’s two cases when hackers have to think about USB-C connector mechanics. The first is when a USB-C connector physically breaks, and the second is when we need to put a connector on our own board. Let’s go through both of them.

Clean That Connector

What if a socket on your phone or laptop fails? First off, it could be due to dust or debris. There’s swabs you can buy to clean a USB-C connector; perhaps adding some isopropyl alcohol or other cleaning-suitable liquids, you can get to a “good enough” state. You can also reflow pins on your connector, equipped with hot air or a sharp soldering iron tip, as well as some flux – when it comes to mechanical failures, this tends to remedy them, even for a short period of time.

How could a connector fail, exactly? Well, one of the pins could break off inside the plastic, or just get too dirty to make contact. Consider a device with a USB-C charging and data socket, with USB 2.0 but without high-speed pairs – which is to say, sadly, the majority of the phones out there. Try plugging it into a USB-A charger using a USB-A to USB-C cable. Does it charge, even if slowly? Then, your VBUS pins are okay.

Plug it into a Type-C charger using a Type-C cable, and now the CC pins are involved. Does it charge in both orientations? Then both of your CC pins are okay. Does it charge in only one orientation? One of the CC pins has to be busted. Then, you can check USB 2.0 pins, used for data transfer and legacy charging. Plug the phone into a computer using a USB-A to USB-C cable. Does it enumerate as a device? Does it enumerate in both orientations? If not, you might want to clean D- and D+ pins specifically, maybe even both sets. Continue reading “All About USB-C: Connector Mechanics”

Seriously, Don’t Buy This Mopping Robot

The original Roomba robotic vacuum cleaner led to loads of clones and lookalikes over the years, and one of them is the ALEE mopping “robot”. [Raymond] tears it down and reveals what’s inside. Turns out it contains mostly regret! Although it does host some design cleverness in its own way.

Technically the ALEE, which cost [Raymond] a cool $85 USD, is not a robot since it has no sensors. And unless a dragging a wet cloth pad kept moist by a crude drip reservoir counts as “mopping”, it’s not much of a mop, either.

This one-motor unit (and tiny battery) is responsible for both motion and direction control. There are no sensors.

There is one interesting aspect to this thing, and it’s to do with the drive system and direction control. The whole thing is driven by a single motor, and not a very powerful one. The center of the robot has a pair of wheels that are both driven at the same rate and speed, and the wheel assembly can pivot around its axis. That’s about it. There are not even any bump sensors of any kind.

So how does this thing move, let alone change direction to (poorly) emulate an original Roomba-like crisscross pattern? The control board appears to have one job: if the motor stalls, reverse direction. That, combined with the fact that the drive unit can pivot and the enclosure is dragging a wet rag, appears to be all the chaos that’s needed to turn bonking into a wall into an undefined direction change.

It’s not great performance, but it sure is some impressive cost-cutting. You can see it bonk around unimpressively in a short video, embedded below the page break.

Just to be clear, [Raymond] knows perfectly well what he’s in for when he obtains cheap tech items from overseas retailers for teardowns. The ALEE does have some mildly interesting secrets to share, but overall, it really wasn’t worth it. Sometimes cheap tech has hacker potential, but there’s no such potential here. Seriously, don’t buy this thing.

Continue reading “Seriously, Don’t Buy This Mopping Robot”

A Love Letter To My Lost Amiga

My first love was a black wedge. It was 1982, and I had saved up to buy a Sinclair ZX81. That little computer remains the only one of the huge number that I have owned over the years about which I can truly say that I understood its workings completely; while I know how the i7 laptop on which this is being written works I can only say so in a loose way as it is an immensely complex device.

Computing allegiance is fickle, and while I never lost an affection for the little Sinclair I would meet my true electronic soulmate around eight years later as an electronic engineering student. It no longer graces my bench, but this was the computer against which all subsequent machines I have owned would be measured, the one which I wish had not been taken from me before its time, and with which I wish I could have grown old together. That machine was a Commodore Amiga, and this is part love letter, part wistful musing about what could have been, and part rant about what went wrong for the best desktop computer platform ever made. Continue reading “A Love Letter To My Lost Amiga”

The Physics Behind The Collapse Of A Huge Aquarium

At the end of last week Aquadom, the world’s largest cylindrical aquarium, unexpectedly shattered and caused an emergency as it flooded both the Berlin hotel that housed it and the surrounding streets. From an engineering perspective it’s a fascinating story, because its construction was such that this shouldn’t have happened. We have an analysis of what might have gone wrong from [Luis Batalha] (Nitter), and from it we can learn a little about the properties of the plastic used.

The aquarium was made of an acrylic polymer which has an interesting property — at a certain temperature it transitions between a glass-like state and a rubber-like one. Even at room temperature the acrylic is well below the transition temperature, but as the temperature drops the acrylic becomes exponentially more brittle. When the outside temperature dropped to well below zero the temperature also dropped in the foyer, and the high water pressure became enough to shatter the acrylic.

Sadly few of the fish from the aquarium survived, but fortunately nobody was killed in the incident. News coverage shows how the force of the water destroyed the doors and brought wreckage into the street, and we’re guessing that it will be a while before any other hotel considers such a project as an attraction. Meanwhile we’ve gained a little bit of knowledge about the properties of acrylic, which might come in handy some day.

Header: Chrissie Sternschuppe, CC BY-SA 2.0.

See The ATARI GEM Desktop Running On A Portable Word Processor… Thing

Get ready for vintage computing aplenty in [David Given]’s project to port EmuTOS to the AlphaSmart Dana. He’s got it all on video, too. All 38 hours of it over 13 episodes!

The GEM desktop, as seen on the Atari ST line of computers.

[David]’s fork of EmuTOS is an open source version of the Atari TOS, which is itself the 68000-based OS for the Atari ST line of computers.

As for the AlphaSmart Dana, it is a roughly twenty-year-old portable word processor thing with pen input which runs a version of PalmOS. It’s a slightly oddball piece of hardware, but quite capable in its own way. A match obviously made in heaven? It is if you have [David]’s skill and drive!

To get EmuTOS working on the Dana, the first step was figuring out how to find and work with the Dana’s debug port, using it to get direct access to the CPU while bypassing the boot ROM. Turns out that the Dana’s 68000-compatible processor has a handy feature: by manipulating the right pin, one can remote-control the CPU (to a certain extent) via the UARTs. That’s the entry point for a whole lot of hacking that ultimately results in firing up the GEM desktop on the Dana, and being able to run (some) original Atari ST software. Probably the biggest issue is that the screen size isn’t a great match for what the OS expects, but it works.

Continue reading “See The ATARI GEM Desktop Running On A Portable Word Processor… Thing”

Mouse Whisperer Keeps You Working, Even When You Need A Break

When life hands you lemons, you make lemonade, right? What about when life hands you annoyingly intrusive work-from-home policies that require you to physically stay at your computer even though you really, REALLY need to go to the bathroom, but can’t be trusted to act like a responsible adult who won’t get diverted by TV or the fridge on the way back? In that case, you build something like the Mouse Whisperer — because malicious compliance is the best kind of compliance.

To be fair, [andrey.malyshenko] does list other plausible use cases for what amounts to an automatic mouse wiggler. Like many of us, [andrey] isn’t a fan of logging back in from screen locks, and recognizes that not absolutely every minute of work requires staring at one’s screen. There’s also the need for bio-breaks, of course, and the Mouse Whisperer is designed to accommodate these use cases and more.

The design is quite compact, occupying barely more space than a wireless mouse dongle. Plugged into a USB port, the ATtiny85 mostly sits idle, waiting to detect the touch of a finger on an exposed pad via a TTP223. The dongle then goes into a routine that traces lazy circles with the mouse pointer, plus flashes an RGB LEB on the board, because blinkenlights are cool. The mouse wiggling continues until you come back from your Very Important Business and touch the pad again.

Now, if anyone is actually monitoring you remotely, the circling mouse pointer is going to look a wee bit sus. Fear not, though — the code uses a *.h file to define the circle, so other patterns should be possible. Either way, the Mouse Whisperer is a nice solution, and it’s considerably more compact and integrated than some of the alternatives we’ve seen.

Snail Mail Notifier’s Simple Power Management To Maximize Battery Life

There are no weird, specialized components nor esoteric sleep mode tricks behind the long battery life of [Zak]’s WiFi mail slot watcher. Just some sensible design and clever focus on the device’s purpose: to send an HTTP request whenever it detects that the front door’s mail slot has been opened. The HTTP request is what kicks off useful notifications, but it’s the hardware design that’s really worth a peek.

The watcher’s main components are a ESP-M2 WiFi module, a reed switch, and a single lithium cell. Here’s how it works at a high level: when the mail slot is opened (detected by the reed switch), the ESP module is powered up just long enough to connect to the local WiFi network and send a single HTTP request, after which it shuts back down. The whole process takes between four and ten seconds.

As mentioned, the power control isn’t managed by any unusual components; it comes down to a NAND gate with a single inverted input, and a MIC5504 3.3 V regulator responsible for feeding the ESP board. The logic gate controls whether the voltage regulator is enabled or disabled, and therefore whether the microcontroller receives any power at all. Most of the time the regulator is disabled, but when the reed switch triggers, its input to the NAND gate is pulled low and the regulator is turned on, booting up the ESP board.

In order to stay on, the first thing the ESP board does is use a GPIO pin to drive the inverted input of the NAND gate high in order to keep the regulator enabled, and it has a window of about half a second to do this. Once the HTTP request is sent (and the battery voltage sensed), the ESP board pulls that pin low, disabling the regulator and turning itself off until the reed switch once again begins the process.

After seven months of use, the battery has dropped from 4.2 V to 3.9 V, so there’s plenty of life left. The project’s GitHub repository has the necessary code if you’d like to apply some of its ideas to your own projects. Alternately, you may wish to consider supercapacitors and solar in lieu of batteries. Even if ultra-level power savings isn’t your bag, when WiFi and networking is involved, there are software-level opportunities to be more efficient. Even a judicious 1 ms delay can save a surprising amount of power in the right circumstances.