Speak Your WiFi

When you create a Thing for the Internet of Things, you’ve made a little computer that does a simple job and which probably has a minimal interface. But minimal interfaces leave little room for configuration, such as entering WiFi details. Perhaps if you made the Thing yourself you’ve hard-coded your WiFi credentials in your code, but that hardly translates to multiple instances. So, how to put end-user WiFi credentials easily on more than one Thing? Perhaps [Rob Dobson] has the answer with his technique of sending them as a sequence of audible tones.

There is a piece of Javascript code in a browser into which you enter your WiFi credentials, which are then expressed through the speaker as a set of FSK tones to be picked up by a microphone on the Thing. They can then be decoded into the credentials, and the Thing can connect. All the code is available, on GitHub, should you fancy it yourself.

Of course, this is nothing new, as any owner of an 8-bit machine that had a cassette interface will tell you. And on the face of it it’s much easier than those awkward impromptu hotspots with a web interface to which you connect and pass on your credentials. But while we quite like the convenience, we can’t help wondering whether expressing the credentials in audible free space might be a bit too insecure for many readers. The technique however remains valid, and we’re sure that other less sensitive applications might be found for it. Meanwhile we hope he hasn’t inadvertently shared his WiFi password in the video below the break.

Continue reading “Speak Your WiFi”

New AVR-IOT Board Connects To Google

Readers of Hackaday are no strangers to using a microcontroller to push data to WiFi. Even before the ESP8266 there were a variety of ways to do that. Now Microchip is joining the fray with a $29 board called the AVR-IOT WG that contains an 8-bit ATmega4808, a WiFi controller, and hardware-based crypto chip for authenticating with Google Cloud.

The board has a section with a USB port for charging a battery and debugging that looks like it is made to cut away. There are a number of LEDs and buttons along with a light sensor and a temperature sensor. It feels like the goal here was to pack as many Microchip parts onto a single dev board as possible. You’ll find the ATmega4808 as the main controller, an ATWINC1510 WiFi controller (a castellated module reminiscent of the ESP8266), the ATECC608A cryptographic co-processor, MCP73871 LiPo charger, MIC33050 voltage regulator, and an MCP9808 temperature sensor. We can’t find much info about the “nEDBG Programmer/Debugger” chip. If you’ve used it on one of a handful of other dev board, let us know in the comments about off-board programming and other possible hacks.

Naturally, the board works with AVR Studio or MPLAB X IDE (Microchip bought Atmel, remember?). Of course, Atmel START or MPLAB Code Configurator can configure the devices, too. There’s also an AVR-IoT-branded website that lets you use Google cloud to connect your device for development. The headers along the top and bottom edges are compatible with MicroElektronika Click boards which will make anyone with a parts bin full of those happy.

Looks like you can pick up the Microchip boards now from the usual places. From reading what Microchip is saying, they would like to position this as the “IoT Arduino” — something someone without a lot of experience could pick up and use to pipe data into Google cloud. While that’s probably good, it isn’t that hard to use an ESP-device to do the same thing using the Arduino IDE and then you have a 32-bit processor and you can use whatever cloud vendor you want. Sure, it would be a little more work, so maybe that’s where this offering will appeal.

On the plus side, we really liked that there was a battery option with a charger already on board — it seems like that’s something we always have to add anyway. It may be buried in the documentation, but the user’s guide and the technical guide didn’t appear to have an average and maximum current draw specified, so battery life is an open question, although the video says “low power.”

Although it isn’t quite the same thing, we’ve seen ESP8266’s talk to Google servers for interfacing with Google Home. And while it is on the Amazon cloud, we’ve even seen a 6502 up there.

Continue reading “New AVR-IOT Board Connects To Google”

Portable Hacking Unit Combines Pi With WiFi Pineapple

Sometimes you need to hack on the go. [Supertechguy] has put together an interesting system for hacking on the hoof called the Pineapple Pi. This combines a Raspberry Pi 3 with a seven-inch touchscreen and a Hak 5 WiFi Pineapple into a handy portable package that puts all of the latest WiFi and ethernet hacking tools to hand. The package also includes a 20,100 mAh battery, so you won’t even need a wall socket to do some testing. It’s a bit of a rough build — it is held together with velcro, for instance — but it’s a good place to start if you are looking to make a portable, standalone system for testing WiFi networks.

Continue reading “Portable Hacking Unit Combines Pi With WiFi Pineapple”

Wired Wireless Over Coax

If it’s stupid and it works, then it’s not stupid. There’s no better evidence of that than [Manawyrm]’s networking setup.

She recently had to distribute Ethernet through a building, and there are a few ways to do that. You can use regular old twisted pair, or fiber, but in this case running new cables wasn’t possible. WiFi would be the next obvious choice, but the distance was just a bit too far for ‘regular’ WiFi links. Ethernet over power lines was an option, but there are amateur radio operators in the house, and power lines put out a bunch of interference and noise. The solution was to mis-use existing 75 Ohm satellite TV coax that was just sitting around.

The correct way to do this would be to use a standard DOCSIS modem and become your own cable Internet provider. The equipment to do this is expensive, and if you’re already considering running WiFI over coax, you’re too deep down the rabbit hole to spend real money. Instead, [Manawyrm] simply made a few u.FL to F-connector adapters from u.FL to SMA, then SMA to F-connector adapters.

There are some problems with this plan. WiFi is 50 Ohms, TV coax cable is 75 Ohms. Only one MIMO channel will be available meaning the maximum theoretical bandwidth will be 433 Mbps. WiFi is also at much higher frequencies than what coax is designed for.

With two WiFi antenna to coax adapters, [Manawyrm] simply connected the coax directly to a router set up to bridge Ethernet over WiFi. The entire thing worked, although testing showed it was only getting about 60 Mbps of throughput. That’s not bad for something that was cobbled together out of old parts and unused wiring. Is it surprising that this worked? No, not really, but you’ve probably never seen anyone actually do it. Here’s the proof it does work, and if you’re ever in a bind, this is how you make WiFi wired.

Which Wireless Is Right Wireless?

Back in the early days of Arduino proliferation (and before you ask, yes we realize there was a time before that too), wireless was a strange and foreign beast. IR communication was definitely a thing. And if you had the funds there was this cool technology called ZigBee that was available, often in funny blue house-shaped XBee boards. With even more funds and a stomach for AT commands you could even bolt on a 2G cell radio for unlimited range. WiFi existed too, but connecting it to a hobbyist ecosystem of boards was a little hairier (though maybe not for our readership).

But as cell phones pushed demand for low power wireless forward and the progression of what would become the Internet of marking Terms (the IoT, of course) began, a proliferation of options appeared for wireless communication. Earlier this week we came across a great primer on some of the major wireless technologies which was put together by Digikey earlier in the year. Let’s not bury the lede. This table is the crux of the piece:

There are some neat entries here that are a little less common (and our old friend, the oft-maligned and never market-penetrating ZigBee). It’s actually even missing some entries. Let’s break it down:

  • Extremely short range: Just NFC. Very useful for transferring small amount of sensitive information slowly, or things with high location-relevance (like between phones that are touching).
  • Short range: BLE, Zigbee, Z-Wave, etc. Handy for so-called Personal Area Networks and home-scale systems.
  • Medium/long range: Wifi, Bluetooth, Zigbee, Z-Wave, LoRaWAN: Sometimes stretching for a kilometer or more in open spaces. Useful for everything from emitting tweets to stitching together a mesh network across a forrest, as long as there are enough nodes. Some of these are also useful at shorter range.
  • Very Long range/rangeless: Sigfox, NB-IoT, LTE Category-0. Connect anywhere, usually with some sort of subscription for network access. Rangeless in the sense that range is so long you use infrastructure instead of hooking a radio up to a Raspberry Pi under your desk. Though LoRa can be a fun exception to that.

You’re unlikely to go from zero to custom wireless solution without getting down into the mud with the available dev boards for a few different common protocols, but which ones? The landscape has changed so rapidly over the years, it’s easy to get stuck in one comfortable technology and miss the appearance of the next big thing (like how LoRaWAN is becoming new cool kid these days). This guide is a good overview to help catch you up and help decide which dev kits are worth a further look. But of course we still want to hear from you below about your favorite wireless gems — past, present, and future — that didn’t make it into the list (we’re looking at you 433 MHz).

Seeed Air602 WiFi dev board.

Tiny WiFi-Enabled ARM MCU For Tiny Projects

Ever since the ESP8266 WiFi-enabled microcontroller came on the scene, it seemed like suddenly everyone came up with WiFi-enabled projects. But the ESP8266 is not the only game in town! Reader [PuceBaboon] notified us of a new product released by Seeed Studios: the imaginatively called Air602 WiFi Development Board.

The core of this board is the tiny WinnerMicro W600 MCU, which integrates a 32-bit ARM Cortex M3 CPU, along with dual UARTs, I2C, SPI and I2S interfaces, as well as a real-time clock (RTC). Add to this hardware crypto, seven I/O pins (five broken out on the development board) and you have a very capable WiFi-enabled MCU which can be programmed using the usual ARM development tools (e.g. Keil) using the provided SDK.

The W600 module can be bought by itself, in all its diminutive 12 mm x 10 mm glory, for a mere $1.90 as of time of writing – without antenna – as noted in [PuceBaboon]’s thoughts on this MCU and the development board.

Apple’s Best Computer Gets WiFi

The greatest computer Apple will ever make isn’t the Apple II, it isn’t the Bondi Blue iMac, it isn’t the trash can, and it certainly isn’t whatever overheating mess they’re pushing out now. The best computer Apple will ever make is the SE/30, at its time a server in a tiny portable shell, and capable of supporting 128 Megabytes of RAM thirty years ago.

Over the years, people have extended and expanded the SE/30 to absolutely ludicrous degrees, but now we have a simple way of adding WiFi to this classic computer. Over on the 68kmla forums, [ants] discovered a tiny cheap card that could easily serve as an Ethernet to WiFi bridge. After attaching this card to a Danaport Ethernet card and bending some aluminum for a bracket, they had a WiFi antenna sticking out of the back of a 30-year-old computer.

But adding a WiFi card to an old computer is nothing new — this could have been done with a Pi, or if you’re a hacker, a TP-Link router flashed with OpenWRT. To really do this right, you’ll need integration with the operating system, and that’s where this build goes off the rails. [ants] wrote a WiFi extension for System 7 (with the relevant GitHub)

The problem with the Vonets WiFi card is that configuration has to be done through a browser. Since there are no modern browsers for classic macs, this meant either pulling out a PowerBook or doing the configuration through your daily driver desktop PC. The WiFi extension gets around that by giving a classic mac the ability to configure the Vonets card almost automatically. This extension also looks like how you would configure the WiFi on a modern mac, complete with the WiFi icon in the toolbar. It’s beautiful, and one of the rare examples of modern 68k mac programming.

As for what you can do by adding WiFi to a 30-year-old computer with a 16MHz processor, the answer is a resounding, ‘not much’. Your choice of browsers is limited (iCab seems to be the best), but you can load the Google homepage slowly. HTTPS isn’t going to work, and the Internet right now is full of megabytes of Javascript cruft. If you find a nice, lightweight web page — such as the Hackaday Retro Edition, for example — you’re looking at a capable web browsing machine. Of course, the real use case for giving the SE/30 WiFi is file transfer around the home network, but still: it’s WiFi for the best computer Apple ever made.