The Philips Hue range is a great way to add wirelessly controllable lighting to your home, but the protocol is proprietary which makes it difficult to add our own custom hardware. [Peter] found a way to create his own Hue compatible devices based on cheap JN5168 modules that are able to connect to the Hue bridge. This means you can roll out your own lamps using cheap RGB or White LEDs, a power supply and the JN5168 Zigbee Light Link module.
He started off by trying to clone a Zigbee Light Link device to a MeshBee — Seeed studio’s open source Zigbee Pro module based on the NXP JN5168. Even though the MeshBee used the same device as a Hue lamp, it would not connect to the Hue bridge. But another clone lamp called Innr that he purchased from the local hardware store did connect quite easily. Using NXP’s open source tools, he was able to download the flash and EEPROM contents from the Innr and copy them to the MeshBee which did the trick.
After the EEPROM transfer trick, he figured out how to modify the two keys used for the ZigBee protocol — one for Home Automation and the other for the Light Link. With this final discovery he is able to take the ZigBee Light Link demo project, edit it using Beyond Studio, and then load the binaries on the MeshBee device so it can connect to the Hue bridge.
All of this work culminates in two custom firmware binaries; one for white dimmable lights and another for RGB dimmable ones. It even runs on these cheap JN5168 breakout kits he found for a few bucks. With all of the software taken care of, and having cheap ZigBee Light Link compatible modules on hand, building low cost Hue compatible lights becomes pretty straight forward.
Thanks [wind-rider] for the tip.
The LTC4316 is something special. It’s an I²C address translator that changes the address of a device that would otherwise conflict with another on the same I²C bus. Not a hack? Not so fast. Exactly how this chip does this trick is clever enough that I couldn’t resist giving it the post it rightfully deserves.
What’s so special? This chip translates the address on-the-fly, making it transparent to the I²C protocol. Up until this point, our best bet for resolving address collisions was to put the clashing chip on a separate I²C bus that could be selectively enabled or disabled. In that department, there’s the PCA9543 and PCA9547 demultiplexers which we’ve seen before. Both of these devices essentially act like one-way check valves. To address any devices downstream, we must first address the multiplexer and select the corresponding bus. While these chips resolve our address collision problems, and while there’s technically a way to address a very large number of devices if we’re not time-constrained, the control logic needed to address various bus depths can get clunky for nested demultiplexers.
What’s so classy about the LTC4316 is that is preservers simplicity by keeping all devices on the same bus. It prevents us from having to write a complicated software routine to address various sections of a demultiplexed I²C bus. In a nutshell, by being protocol-transparent, the LTC4316 keeps our I²C master’s control logic simple.
How it Works
I mocked up a quick test setup to have a go at this chip in real life. Continue reading “LTC4316 is the I2C Babelfish”
January has drawn to a close, and for many of you that means: “Oh no! Less than two weeks’ time until Valentine’s day.” But for us here at Hackaday, it means heart-themed blinky projects. Hooray!
[Dmitry Grinberg] has weighed in with his version of the classic heart-shaped LED ring. It’s hard to beat the BOM on this one: just a microcontroller, five resistors, and twenty LEDs. The rest is code, and optionally putting the name of your beloved into the copper layer. Everything is there for you to download.
Continue reading “Valentine’s Heart with Awesome Animations”
Reuters has reported that Qualcomm will purchase NXP for $38 Billion in the largest semiconductor deal ever.
This deal was rumored last month in a deal worth about $30 Billion. Qualcomm’s name should be familiar to all Hackaday readers – they have an immense portfolio of mobile processors, automotive chips, and a ton of connectivity solutions for WiFi, Bluetooth, and every other bit of the EM spectrum. NXP should also be familiar for their hundreds of ARM devices, automotive devices, and Freescale’s entire portfolio.
The deal for $38 Billion is just a bit larger than the previous largest semiconductor deal, Avago’s purchase of Broadcom for $37 Billion.
This latest acquisition has followed acquisitions of ARM Holdings by Japan’s Softbank, On and Fairchild, Avago and Broadcom, NXP and Freescale, Microchip and Atmel, Intel and Altera, and a few dozen we’re forgetting right now. The good news is this immense industry consolidation won’t result in a single gigantic chip maker; there will probably be two or three gigantic chip companies in the future. If I may dredge up an observation from a Mergers and Acquisition post from this summer, this trend didn’t go well for Hughes, Fairchild, Convair, Douglas, McDonnell Douglas, North American, Grumman, Northrop, Northrop Grumman, Bell, Cessna, Schweizer or Sikorsky. It went very well for Lockheed, Boeing, and Textron.
Remember when we talked about NXP merging with Freescale to move into the top ten semiconductor companies? Yeah, that was just eighteen months ago and just barely closed before the new year. Now it looks like Qualcomm wants to acquire NXP to the tune of $30 billion.
You’re most likely familiar with Qualcomm as a cellphone silicon company. The acquisition of NXP opens up a lot of additional markets with their portfolio of chips — automotive among them thanks to the Freescale merger. Now you should be asking yourself just how big Qualcomm is already. What’s perhaps most interesting is that, as mostly a wireless chip company, Qualcomm is ranked number three in worldwide semiconductor sales. Adding NXP — a behemoth now in the top ten — adds at least 30% to Qualcomm’s numbers.
And so here we are, one step close to a monolithic chip fab that produces all computing power for the human race. Yippie!
Buyouts, acquisitions, and mergers of semiconductor companies are not unfamiliar territory for anyone who deals with chips and components for a living. Remember Mostek? That’s STMicroelectronics now. The switches used to type this post – Cherry blues – were made by ON Semiconductor. Remember Motorola? Freescale.
Today marks another merger, this time between NXP and Freescale. The merger will result in a $40 Billion dollar company, putting it in the top ten largest semiconductor companies.
Hackaday readers should know NXP for being the only company ever to produce an ARM microcontroller in a DIP package along with thousands of other cool components. Freescale is perhaps best known for their i.MX6 series of ARM processors, but of course both companies have a portfolio that stretches back decades and is filled with tens of thousands of parts.
It’s happened. It’s finally happened. In a move that has hipsters donning their good flannel and breaking out that case of Genesee they were saving for a special occasion, the rotary cell phone is now a reality.
[Jaromir] created this astonishingly retro future device as an entry for the NXP LPC810 challenge, a contest to do the most with an ARM Cortex M0+ microcontroller in an 8-pin package. Having only six I/O pins for controlling a GSM module, display a few buttons, and the fancy rotary dial meant [Jaromir] needed to expand his I/O some way. He chose a shift register to handle the buttons and display in a somewhat impressive demonstration of using a shift register as both an input and output expander at the same time.
From the videos [Jaromir] uploaded, the rotary cell phone isn’t ready for Think Geek to do a production run quite yet. He needs to enter the PIN for the SIM card, AT commands for the GSM module, and is, of course, a horrible method of user input for the younglings who have only seen rotary phones in old movies. That being said, it’s a rotary cell phone running on an 8-pin microcontroller. What more do you want?
Videos of this awesome this truly awesome phone in action below. If you’d like to build your own – and why wouldn’t you – all the files are available on [Jaromir]’s git
Continue reading “The Rotary Cell Phone”