ESP-Micro Is A Tiny Development Board

The ESP-8266 packs a lot of networking power into a small package. Some would say too small, which is why they often come on a slightly larger carrier PCB. The PCB is usually little more than a breakout with an optional 3.3V regulator. [Frazer Barnes] went one step further: he put an equally tiny USB to serial bridge, an oscillator, and some power management on an ESP-8266 breakout board.

You can program the ESP-8266 via the serial port, so having a built-in USB port is handy. Of course, you might not need it in the final product, but with the board being 25x30mm, you can probably cram it into most projects. [Frazer] posted a bit about the project on Hackaday.io, and has a GitHub project, although right now the upload of the design files is pending.

There’s no shortage of ESP-8266 projects. We saw a small Zigbee to ESP8266 board last year, and also the antidote for a tiny carrier board that includes an LCD, switches, and more. We also have tons of breakouts on Hackaday.io: here’s one with all the bells and whistles, and a similar, stripped-down version. All open-everything, and ready to go.

Weightless IoT Hardware Virtually Unavailable

It has been over 2 years since we last mentioned the Weightless SIG and their claims of an IoT open standard chip with a 10 year battery life and 10km wireless range, all at a jaw dropping price of $2 per chip. There was a planned production run of the 3rd gen chips which I would suspect went to beta testers or didn’t make it into production since we didn’t hear anything else, for years.

Recently, a company called nwave began producing dev-kits using the Weightless Technology which you can see in the banner image up top. Although the hardware exists it is a very small run and only available to members of the development team. If you happen to have been on the Weightless mailing list when the Weightless-N SDK was announced there was an offer to get a “free” development board to the first 100 development members. I use bunny ears on free because in order to become a member of the developer team you have to pay a yearly fee of £900. Don’t abrasively “pffffft” just yet, if you happened to be one first 100 there was an offer for developers that came up with a product and submitted it back for certification to get their £900 refunded to them. It’s not the best deal going, but the incentive to follow through with a product is an interesting take.

Continue reading “Weightless IoT Hardware Virtually Unavailable”

Philips Says: No Internet Of Things For You!

The 900-pound gorilla in the corner of the Internet of Things (IoT) hype that everyone is trying to ignore is interoperability. In the Internet of Internets (IoI) everything works on a few standards that are widely accepted: IP and HTML. The discrepancies are in the details and the standards wars are in the past. Websites are largely interoperable. Not so in the wild-west ethos of the IoT.

Philips makes a line of ZigBee-enabled RGB lightbulbs that took the enthusiast community by storm. And initially, Philips was very friendly to other devices — it makes a ZigBee-to-WiFi bridge that would let you control all of your ZigBee-based lights, regardless of their manufacturer, from your phone. Until now.

Philips has just rolled out a “Friends of Hue” certification process, and has since pushed out a firmware update where their Hue bridges stop interoperating with non-certified devices. You can read Philips’ version of the story here.

Philips Locks Out 3rd Party ZigBee Hardware

The hub shown on the right is what's being locked down.
The hub shown on the right is what’s being locked down.

The short version is that, ZigBee standards be damned, your future non-Philips lights won’t be allowed to associate with the Philips bridge. Your GE and Osram bulbs aren’t Friends of Hue. DIY RGB strips in your lighting mix? Not Friends of Hue. In fact, you won’t be surprised to know who the “Friends of Hue” are: other Philips products, and Apple. That’s it. If you were used to running a mixed lighting system, those days are over. If you’re not on the friends list, you are an Enemy of Hue.

Their claim is that third party products may display buggy behavior on a Philips network, and that this loads up their customer-response hotlines and makes people think that Philips is responsible. Of course, they could simply tell people to disable the “other” devices and see how it works, putting the blame where it belongs. Or they could open up a “developer mode” that made it clear that the user was doing something “innovative”. But neither of these strategies prevent consumers from buying other firms’ bulbs, which cost only 30-50% of Philips’ Hue line.

While Philips is very careful to not couch it as such, the Friends of Hue program really looks like an attempt to shut out their competitors; Philips got an early lead in the RGB LED game and has a large share of the market. As they say themselves in their own press release “Today these 3rd party bulbs represent a minimal fraction of the total product connected to our bridges so the percentage of our users affected is minimal.” And they’d like to keep it that way, even though the people they’re hurting are probably their most vocal and dedicated customers.

Who owns the IoT?

This Techdirt response to the situation is positively apoplectic, and there’s been the predictable flood of tirades in the comments on Slashdot. [Joel Ward], who in January was celebrating the ability to afford enough colored lights to appease his son is not so happy anymore.

And while we, with our manual light switches, laugh comfortably at the first-world problems of Hue consumers, we have to ask ourselves whether we’re next. Today they come for our RGB lightbulbs, but tomorrow it might be our networked toasters. A chilling thought!

Snark aside, the IoT brings two of the saddest realities of the software world into your home appliances: Where there’s code, there’s vulnerabilities, and when you can’t control the code yourself you aren’t really in control. You may own the lightbulb, but you’re merely licensing the firmware that runs it. The manufacturer can change the rules of the game, or go out of the product line entirely, and you’re high and dry. What can you do? Pull out your JTAG debugger.

Of course it’s insane to suggest that everyone needs to become an embedded-device firmware hacker just to keep their fridge running. As we’ve written before, we need to come up with some solution that puts a little more control in the hands of the ostensible owners of the devices, while at the same time keeping the baddies out. We suggest a press-to-revert-firmware button, for instance. When Philips pushes a non-consumer-friendly upgrade, you could vote with your fingertips — but then you’d miss out on bug fixes as well. Maybe it’s better to just give in an learn to love Windows 10.

There are no easy solutions and no perfect software. The industry is still young and we’ll see a lot of companies staking out their turf as with any new technology. It seems to us that IoT devices leave consumers with even less choice and control than in the past, because they are driven by firmware that’s supposed to be invisible. It’s just a lightbulb, right?

What do you think? Any ideas about how to put the power back in the hands of the “owner” of the device without everyone’s refrigerators becoming botnet zombies? Let us know in the comments.

Thanks [djxfade] for the tip!

Edit: Shortly after we ran this piece, Philips backed down:

“We underestimated the impact this would have upon the small number of our customers who currently use uncertified lights from other brands in the Philips Hue system. We have decided to continue to enable our customers who wish to integrate these uncertified products within their Philips Hue system.”

Every PCB Has Its Place

Everyone has their favorite process for PCB fabrication, as long as you’re a happy hacker I don’t think it really matters. But in this post I thought it might be interesting to describe my personal process, and some of the options available.

Making your own at home

The Dirty Electronics Skull Etching Synth a great looking maskless board.

Etching is the classic PCB fabrication option for the home hacker. It’s been many, many years since I etched a PCBs but it can produce interesting results. Some people don’t like it, and I’d personally tend to avoid it as a messy and finicky process. But, if you only need 1 or 2 layer boards with large features (through-hole components are best of course) it can be a viable option. In some cases, I think etched boards look awesome and are a great fit. One example is the skull etching shown to the right. The oxidation and discoloration of the boards adds to the design aesthetic in this case.

Sample1
A simple design milled on an Accurate CNC

For those with a bigger budget a professional milling machine might be a viable choice. I’ve used an Accurate CNC in the past (LPKF and others make mills too), but this is an expensive option (no online pricing, but if $10,000 USD is a lot for you don’t bother). The accurate mill is pretty awesome, it can be fitted with a vacuum bed, automatic tool changer and vision system for alignment. The mill can produce high quality two layer boards with all the holes and vias drilled out. The final step of filling the vias is however manual, but compared to etched boards the results are pretty professional (the mill itself uses milled PCBs!). They claim a 0.1mm (4 mil) track size, I’ve never tried tracks this small but surface mount components were not a problem.

While a fun toy, it’s worth considering if you really need a PCB mill. The only case where they’re really valuable is if you want to be able to iterate over a design with less than a days turn around. This can be useful in RF or low noise designs where you might want to experiment with different layouts, but for other projects the price of a good mill can pay for quick turn around (1 or 2 days from order submission to delivery) on a lot of boards.

Commercial Fabrication

Years ago commercial fabrication used to be a very expensive and finicky process. For the most part you’d need to order a full panel putting the service outside of most hobbyists reach. Generating gerbers and drill files to the fabs specification could also be a process fraught with complication.

These days services that aggregate designs onto a single panel and break them out for distribution are common. For my work I mostly stick with OSHPark and SeeedStudio whose services complement each other well. I’ve also used Itead and found them compatible with Seeed (with the added benefit that they supply free boards for open projects).

Using OSHPark gives me the warm fuzzies. A child of the hacker community, born out of DorkbotPDX, all OSHPark’s boards are fabbed in the US (check out the great amphour interview for more details). Their services are limited to either 2 or 4 layer boards (always in purple, and always coated with gold (ENIG)), in 6×6 (6 mil traces with 6 mil spacing) or 5×5. I rarely attempt BGA boards so the 2 layer service works out great for me. OSHPark’s minimum order is 3 boards, which is perfect for prototyping. The gold plating also provides a nice finish, which both protects the board from oxidation and provides a nice surface to solder to. The main reason I use OSHPark however is that they’re cheap for small boards and have a relatively fast turn around (I recently purchased 3 tiny 20x15mm boards for $2.40 including shipping which was unbeatable). From OSHPark in the US to the UK my boards take about 2 weeks to arrive. They’ve also automatically upgrade boards to their super-swift service for free when there’s spare capacity. Their service is pretty slick, and provides a rendering of the gerbers prior to ordering as a final check which comes in very handy.

oshseeed2
Zigbee to esp8266 interface fabricated by Seeed (left) and OSHPark (right) (more complex boards here)

Seeed on the other hand are much cheaper for larger size boards and volume orders. They also provide more color and finishing options. The cheapest option at Seeed is green PCBs with HASL finish (hot air solder leveling). From Seeed, my boards usually take about a month to arrive (there are a few delivery options, but in my experience this is about as fast as it gets and faster shipping services often make using Seeed less attractive).

The image to the right shows a couple of very simple boards I had manufactured at both OSHPark and Seeed. I’ve never had a fabrication issues with boards from either service (though I prefer the ENIG finish).

Partly due to the limitations imposed by using commercial fabs I pipeline my projects. I send projects out to fab early in the design process and then switch to another design. When the board comes back I bring it up, bodge as required, and iterate over the layout. This works well with a two-week turn around, so I mostly use OSHPark while prototyping.

My boards also tend to be quite small (Arduino shield size or a little bigger). With small boards like this OSHPark is usually on-par or cheaper than ordering from Seeed (whose minimum quantity is 10 boards). With boards of about 100x100mm or larger I consider Seeed as they become significantly cheaper.

As a hobbyist I also rarely need huge numbers of boards, but for workshops when I need 10 or 20 boards I order from Seeed based on the final iteration of my prototypes. This is not only much cheaper than OSHPark, but I can get boards in a variety of colors to make workshops more interesting too.

This post has described some of the available options and my personal process. I hope it’s been interesting, but I’d love to hear about your favorite fabrication techniques, services and experiences both good and bad too. Please comment below!

Stuffing Everything On A DIP32 Package

Putting an full microcontroller platform in a DIP format is nothing new – the Teensy does it, the Arduino nano does it, and a dozen other boards do it. [Alex] and [Alexey] aren’t content with just a simple microcontroller breakout board so they’re adding a radio, an OLED, an SD card reader, and even more RAM to the basic Arduino platform, all in a small, easy to use package.

The DIPDuino, as [Alex] and [Alexy] are calling it features an ATmega1284 processor. To this, they’re adding a 128×32 pixel OLED, a micro SD slot, and 1Mbit of SRAM. The microcontroller is a variant that includes a 2.4 GHz Zigbee radio that allows for wireless connections to other DIPDuinos.

What are [Alex] and [Alexey] going to do with their cool little board? They’re planning on using the OLED for a watch, improve their software so the firmware can be updated from the SD card, and one of [Alex]’s friends wants to build a RepRap controller with one of these. There’s a lot of potential with this board, and we’re interested in seeing where the guys take the project from here.

Google’s OnHub Goes Toe To Toe With Amazon Echo

Yesterday Google announced preorders for a new device called OnHub. Their marketing, and most of the coverage I’ve seen so far, touts OnHub as a better WiFi router than you are used to including improved signal, ease of setup, and a better system to get your friends onto your AP (using the ultrasonic communication technique we’ve also seen on the Amazon Dash buttons). Why would Google care about this? I don’t think they do, at least not enough to develop and manufacture a $199.99 cylindrical monolith. Nope, this is all about the Internet of Things, as much as it pains me to use the term.

google-onhub-iot-router-thumbOnHub boasts an array of “smart antennas” connected to its various radios. It has the 2.4 and 5 Gigahertz WiFi bands in all the flavors you would expect. The specs also show an AUX Wireless for 802.11 whose purpose is not entirely clear to me but may be the network congestion sensing built into the system (leave a comment if you think otherwise). Rounding out the communications array is support for ZigBee and Bluetooth 4.0.

I have long looked at Google’s acquisition of Nest and assumed that at some point Nest would become the Router for your Internet of Things, collecting data from your exercise equipment and bathroom scale which would then be sold to your health insurance provider so they may adjust your rates. I know, that’s a juicy piece of Orwellian hyperbole but it gets the point across rather quickly. The OnHub is a much more eloquent attempt at the same thing. Some people were turned off by the Nest because it “watches” you to learn your heating preferences. The same issue has arisen with the Amazon Echo which is “always listening”.

Google has foregone those built-in futuristic features and chosen a device to which almost  everyone has already grown accustom: the WiFi router. They promise better WiFi and I’m sure it will deliver. What’s the average age of a home WiFi AP at this point anyway? Any new hardware would be an improvement. Oh, and when you start buying those smart bulbs, fridges, bathroom scales, egg trays, and whatever else it’ll work for them as well.

As far as hacking and home automation, it’s hard to beat the voice-activated commands we’ve seen with Echo lately, like forcing it to control Nest or operate your Roku. Who wants to bet that we’ll see a Google-Now based IoT standalone device quickly following the shipment of OnHub?

Continue reading “Google’s OnHub Goes Toe To Toe With Amazon Echo”

Decapping The CC2630 And CC2650

[Jelmer] got curious about the TI CC26XX wireless MCUs and did a little decapping.

TI sells four different models of their CC26XX wireless MCUs. Three support one of the following: RF4CE, Zigbee/6LoWPAN, and Bluetooth and a further model which supports all protocols. Each IC has the same baseline specification: 128Kb Flash, 20Kb RAM and 15 GPIOs. cc26xx_nitric[Jelmer] was curious to know if the price difference was all in the software. And in order to verify this decided that decapping was the only thing to do!

We’ve covered decapping using Nitric acid before, as well as lower tech techniques. Luckily [Jelmer] had access to Nitric acid and a fume hood, not the easiest items to get hold of outside of a research lab (checkout the video of the IC bubbling away below). [Jelmer] got some great die shots under an optical microscope and was able to confirm that the die markings are identical. This opens the door to future hacks, which might allow the cheaper models to be re-flashed, expanding their capabilities.

Continue reading “Decapping The CC2630 And CC2650”