Fail of the Week: WinCE is a Noun and a Verb

A few years ago, [localroger] found some incredible hardware on sale: a very tiny laptop with a seven-inch screen, full keyboard, trackpad, Ethernet, WiFi, USB (with support for a lot of HID devices), and a battery that would last hours. They were on sale for $30 USD, and [localroger] bought four of them. A great deal, you say? These machines ran Windows CE. No, owning a WinCE device is not the Fail of the Week.

Figuring he should do something with these machines, [roger] thought, ‘a clock will do’, and began to figure out how to program or write an app for these things. These tiny netbooks did come with a programming language, JavaScript, in the form of the built-in IE6 web browser. This was actually a really, really good solution – WinCE apps formatted for portrait displays just didn’t work with the ‘widescreen’ laptop, and a hand-coded HTML table is probably the best solution anyone could have hoped for.

These machines – [roger] used three of them over the years as alarm clocks – did their job well, even if NTP had been left out of the OS image. The real fail here comes from buying a $30 WinCE netbook, and using it for something as mission critical as an alarm clock. The displays burned in, the batteries began puffing up, one unit somehow wouldn’t allow IE to run (probably a bad Flash chip), and the trackpad in another one sent the cursor on a random walk. You get what you pay for.

These WinCE netbooks have finally been put out to pasture, hopefully the same one laser printers go to. It’s all for the best, though; [roger] made a much better alarm clock with Nixies.


2013-09-05-Hackaday-Fail-tips-tileFail of the Week is a Hackaday column which runs every now and again. Help keep the fun rolling by writing about your past failures and sending us a link to the story — or sending in links to fail write ups you find in your Internet travels.

Fail of the Week: Cat6 != Coax

With a new Kenwood 5.1 receiver acquired from questionable sources, [PodeCoet] had no way to buy the necessary coax. He did have leftover Cat6 though. He knew that digital requires shielded cable, but figured hacking a solution was worth a try.

HAD - Coaxfail4To give hacking credit where credit is due, [PodeCoet] spent over a decade enjoying home theatre courtesy of a car amp rigged to his bench supply. Not all that ghetto of a choice for an EE student, it at least worked. To hook up its replacement he pondered if Cat6 would suffice, “Something-something twisted pair, single-sideband standing wave black magic.” Clearly hovering at that most dangerous level of knowledge where one knows just enough to get further into trouble, he selected the “twistiest” (orange) pair of wires in the cables. Reasonable logic, one must select the strongest of available shoelaces for towing a car.

Continue reading “Fail of the Week: Cat6 != Coax”

Fail of the Week: Battery Packin’

[NeXT] got himself an IBM ThinkPad TransNote and yeah, we’re pretty jealous. For the uninitiated, the TransNote was IBM’s foray into intelligent note transcription from roughly fifteen years ago. The ThinkPad doesn’t even have to be on to capture your notes because the proprietary pen has 2MB of flash memory. It won an award and everything. Not the pen, the TransNote.

Unfortunately, the battery life is poor in [NeXT]’s machine. The TransNote was (perhaps) ahead of its time. Since it didn’t last on the market very long, there isn’t a Chinese market for replacement batteries. [NeXT] decided to rebuild the replacement battery pack himself after sending it off with no luck.

The TransNote’s battery pack uses some weird, flat Samsung 103450 cells that are both expensive and rare. [NeXT] eventually found some camera batteries that have a single cell and a charge controller. He had to rearrange the wiring because the tabs were on the same side, but ultimately, they did work. He got the cells together in the right configuration, took steps to prevent shorts, and added the TransNote’s charge controller back into the circuit.

Nothing blew up, and the ThinkPad went through POST just fine. He plugged it in to charge and waited a total of 90 minutes. The charging rate was pretty lousy, though. At 94% charge, the estimated life showed 28 minutes, which is worse than before. What are your thoughts on the outcome and if it were you, what would be the next move?


2013-09-05-Hackaday-Fail-tips-tileFail of the Week is a Hackaday column which runs every Wednesday. Help keep the fun rolling by writing about your past failures and sending us a link to the story — or sending in links to fail write ups you find in your Internet travels.

Fail of the Week: Robotic 1950 Mercury Boogies, Won’t Come Back From Dead Man’s Curve

[Dave] wanted to make an Arduino robot out of a remote-control 1950 Mercury. He removed the RC portion from the car and kept the drive and steering motors. The idea was to use three ultrasonic rangefinders in the grille real estate and move the car forward based on the longest distance detected.

He initially used a Seeed motor controller and some Grove cables soldered to his sensors to power the steering. It went forward, but only forward, and [Dave] decided the motor controller and the car’s steering motor weren’t playing well together.

[Dave] had the idea to use relays instead to both power the motor and determine polarity. Now, the Merc was turning and avoid obstacles about half the time, but it was also getting dinged up from hitting walls. He figured out that his sensor arrangement was making the car turn immediately and decided to give the program information from the wheels with a reed switch and a rare earth magnet. The only problem is that the caliber of magnet required to trip the reed switch is too heavy and strong. [Dave] and has concluded that he simply can’t exercise the kind of control over the car that he needs. and will build his own robot chassis.

Update: Check out a video of [Dave]’s car after the break.


2013-09-05-Hackaday-Fail-tips-tileFail of the Week is a Hackaday column which runs every Wednesday. Help keep the fun rolling by writing about your past failures and sending us a link to the story — or sending in links to fail write ups you find in your Internet travels.

Continue reading “Fail of the Week: Robotic 1950 Mercury Boogies, Won’t Come Back From Dead Man’s Curve”

Fail of the Week: This Inanimate Titanium Rod

You saw [Chris] cast aluminium on the cheap using Kinetic Sand a few weeks ago, didn’t you? He recently got his meaty hands on some titanium through the magic of modern transactional methods and was bowled over by its strength, hardness, and poor heat transfer.

He thought he would cast it into a nice, strong bottle opener. As you can probably guess, that didn’t go so well. First off, it wasn’t easy to saw through the thin rod. Once he did get it split in twain, it was surprisingly cool to the touch except at the tip. This is nasty foreshadowing, no?

[Chris] takes a moment to help us absorb the gravity of what he’s about to do, which of course is to send several hundred amps through that poor rod using a DC arc welder. Special precautions are necessary due to the reaction between oxygen and heated titanium. His trusty graphite crucible is grounded to the bottom of a big aluminium tub, and a cozy blanket of argon from a TIG welder will shield the titanium from burnination.

Well . . . the titanium didn’t melt. Furthermore, the crucible is toast. On the up side, vise-enabled cross-sectional examination of the crucible proved that there was still gold in them there walls.

Do you have any (constructive, on-topic) suggestions for [Chris]? Let him know below.

Continue reading “Fail of the Week: This Inanimate Titanium Rod”

Sparkfun Ships 2000 MicroViews Without Bootloaders

microview-fail

Everyone has a bad day right? Monday was a particularly bad day for the folks at Sparkfun. Customer support tickets started piling up, leading to the discovery that they had shipped out as many as 1,934 MicroViews without bootloaders.

MicroView is the tiny OLED enabled, Arduino based, microcontroller system which had a wildly successful Kickstarter campaign earlier this year. [Marcus Schappi], the project creator, partnered up with SparkFun to get the MicroViews manufactured and shipped out to backers. This wasn’t a decision made on a whim, Sparkfun had proven themselves by fulfilling over 11,000 Makey Makey boards to backers of that campaign.

Rather than downplay the issue, Sparkfun CEO [Nathan Seidle] has taken to the company blog to explain what happened, how it happened, and what they’re going to do to make it right for their customers. This positions them as the subject of our Fail of the Week column where we commiserate instead of criticize.

First things first, anyone who receives an affected MicroView is getting a second working unit shipped out by the beginning of November. Furthermore, the bootloaderless units can be brought to life relatively easily. [Nate] provided a hex file with the correct bootloader. Anyone with an Atmel AVR In-System Programming (ISP) programmer and a steady hand can bring their MicroView to life. Several users have already done just that. The bootloader only has to be flashed via ISP once. After that, the MicroView will communicate via USB to a host PC. Sparkfun will publish a full tutorial in a few weeks.

Click past the break to read the rest of the story.

Continue reading “Sparkfun Ships 2000 MicroViews Without Bootloaders”

Fail of the Week: Blown Light Bulb Controllers

fotw-nyc-resistor-chandelier-driver

We’ve been meaning to get around to this one for many weeks now. It’s been hard to find good fail write-ups… it’s as if hackers are afraid to admit that sometimes projects fail. We hope you’ll shake off that opinion as failure is the fastest path for learning and true understanding!

[xymax] was working on a control system for a chandelier with 150 bulbs which use 5 Watts each. This project was being readied for the NYC Resistor Interactive Party which [Adam Fabio] attended last month. As deadline for the show approached, the last piece was put in place late into the night… but it was connected backwards. In a tale worthy of a slapstick movie, the reverse polarity caused a chip on all seven controller boards for this module to blow like the one seen above. But that’s not all, the laptop being used during prototyping was connected by USB and started smoking!

All of us feel the pain of this type of equipment failure. Luckily [xymax] looked for lessons to learn instead of dwelling on the mistake itself. Use protection diodes, keyed connectors, and write about your failures. Hopefully reading this will help others avoid a similar equipment-destroying mistake.


2013-09-05-Hackaday-Fail-tips-tileFail of the Week is a Hackaday column which runs every Thursday. Help keep the fun rolling by writing about your past failures and sending us a link to the story — or sending in links to fail write ups you find in your Internet travels.