Here’s a new chip from FTDI which brings a nice little feature to the USB-to-serial converter family: charging detection. That means that it is capable of detecting when a battery charger is connected. What does that actually mean? The top of the datasheet gives you the short version, but let’s look at the investigation [Baoshi] undertook to test the full extent of this particular feature. We agree with him that the listed capability leaves those in the know with a lot of questions:
USB Battery Charger Detection. Allows for USB peripheral devices to detect the presence of a higher power source to enable improved charging.
Obviously the chip will be able to tell when a charger is connected, alerting the device when it’s time to start lapping up the extra milliamps. But what type of chargers will actually trigger the detection circuit? After rigging up the test circuit shown above he ran through several scenarios: connected directly to the PC USB port, via externally powered and non-powered USB hubs, and with multiple wall wart chargers. Full results of the tests are included in the post linked above.
[via Dangerous Prototypes]
Although it’s still a prototype, [Russell] tipped us off to his battery-powered device for storing your contacts list: ContactKey. (Warning: Loud sound @ beginning). Sure, paper can back up your contact information, but paper isn’t nearly as cool to show off, nor can it receive updates directly from your Android. The ContactKey displays a contact’s information on an OLED screen, which you can pluck through by pressing a few buttons: either ‘Up,’ ‘Down,’ or ‘Reset’. Although the up/down button can advance one contact at a time, holding one down will fly through the list at lightning speed. A few seconds of inactivity causes a timeout and puts the ContactKey to sleep to conserve battery life.
This build uses an ATMega328 microcontroller and an external EEPROM to store the actual list. [Russell] wrote an Android app that will sync your contact list to the ContactKey over USB via an FTDI chip. The microcontroller uses I2C to talk to the EEPROM, while an OLED display interfaces to the ATMega through SPI. We’re looking forward to seeing how compact [Russell] can make the ContactKey once it’s off the breadboard; the battery life for most smartphones isn’t particularly stellar. Phones of the future will eventually live longer, but we bet it won’t be this one.
Continue reading “ContactKey: A portable, battery-powered phonebook”
[Hans Peter] wanted to move away from using full Arduino boards in his projects. One of the components he rarely used after the development stage is the USB hardware. Once the firmware is flashed to the chip he didn’t need it any longer. So he tried his hand with some really small SMD parts by building this USB to serial Arduino programmer.
The chip he went with isn’t the FTDI part we’re used to. Instead of using an FT232RL, he opted for its smaller cousin the FT230x. This chip doesn’t fully implement the communications protocol of the 232, but it does work with AVRdude and that’s all that really matters. Above you can see [Hans’] creation next to the official Arduino USB-to-serial programmer. He used the same connection scheme, but went with an edge connector for the USB instead of using a mini-B jack.
It’s pretty impressive to see his prototyping work with the 16-pin QFN package. He soldered it dead-bug style to a couple of SIL pin headers in order to test it on a breadboard. The first board he assembled was too loose in the USB port, but he added some tape to the back to make it thicker, and coated the edge connector traces with a bit of solder and that did the trick.
It should come as no surprise the Hackaday tip line is regularly flooded with press releases. Everything from an infographic comparing Call of Duty 3 to Battlefield 3 (yes, totally serious), announcements that a company we’ve never heard of is getting a new CFO, to the business proposals from hat box manufacturers that wind up in our inbox on a nearly weekly basis.
With the Hackaday crew sifting though hundreds of these emails a month, you’d figure the PR people would hit gold once in a while, right? Apparently not. The coolest stuff we get in our email is usually from an engineer working on a project and doing a PR rep’s job for them. We thank them for that, so here’s two really cool pieces of hardware that showed up in the tip line recently.
Continue reading “Cool new hardware spectacular”
This is a simple iOS debugging tool that will take no time to solder together. There’s even a chance that you already have everything you need on hand. The hack simply connects an RS232-to-USB converter to a breakout board for an iPod connector.
The hardware is aimed not at stock iOS systems, but as an aid to those who wish to run alternative operating systems on them. When the OpeniBoot package is run on an iPod Touch or iPhone it enables a serial terminal on pins 12 and 13. The FTDI breakout board takes these as RX and TX and makes them available to your terminal program of choice via USB. Speaking of USB, you may already have noticed the black cable leaving the right side of the image. Using the terminal doesn’t limit your ability to use the device’s USB functions.
Even though the Roland MDX-20 CNC mill fetched a pretty penny when it was first made available 12 years ago, there were a few features that made any builder lucky enough to own one scratch their head. The only way for a computer to communicate with this mill was through an RS-232 connection, and instead of a normal control protocol such as GCode, the Roland mill uses a very proprietary software package.
[Johan] fixed these problems and at the same time turned this wonderful machine into a tool for the 21st century. Now, instead of running a very long serial cable to his mill with a serial to USB converter at the end, he can just plug a USB cable into his mill with the addition of an FTDI USB to serial chip wired directly to the mill’s circuit board.
Stock, the Roland mill used a very strange proprietary communications protocol. [Johan] was able to reverse engineer this protocol by tracing out a few simple shapes and curves and taking a highlighter to the printout of the resulting file. Instead of the outdated software package that shipped with his mill, [Johan] can now export tool paths directly from his CAD program and send them over a USB cable.
It really is a shame such a nice machine like [Johan]’s mill suffered from the glaring shortsightedness of Roland executives 12 years ago, but at least now [Johan] has a machine that should easily last another decade.
Over at the Albuquerque, NM hackerspace Quelab, [Alfred] needed to test a bunch of surface mount LEDs. He ended up building a pair of 3D printed tweezers with a pair of needles attached to the end and a space for a coin cell battery. It works and Quelab got a new tool.
Woo Raspberry Pi
[tech2077] added an FTDI chip to his Raspberry Pi to do a little single cable development. We’ve seen a few similar builds, but surprisingly nothing related to the on board display serial interface. This wiki page suggests
it’s possible to connect an iPhone 3G or iPhone 4 display directly to the Raspi. Does anyone want to try that out? Nevermind, but it would be cool to get a picture from a display plugged into that display port on the Raspi.
I like to ride my bicycle, I like to ride my bike
Over at the 23b hackerspace a few people were having trouble finding a good bike cargo rack that wasn’t overpriced. They built their own with $30 in materials and a salvaged milk crate. It looks great and is most likely a lot more durable than the Walmart model.
If that cargo rack fell off, it would look like this
Apparently you can get ‘spark cartridges’ to attach to the underside of a skateboard. [Jim] saw these would look really cool attached to his bike so he did the next best thing
. He attached them to his sandals. It does
Less heat, less noise
[YO2LDK] picked up a TV tuner dongle for software radio and found it overheated and stopped working after about 15 minutes (Romanian, Google Translate). He hacked up a heat sink from an old video card to solve this problem. Bonus: the noise was reduced by a few tenths of a dB.