Let’s be honest. Paying electricity bills sucks. The amount paid is always too much, and the temperatures in the building are rarely set at a comfortable level. But now, with the help of this DIY Climate Control system, power-users can finally rejoice knowing that the heating and cooling process of their home (or commercial space) can be easily controlled through the utilization of an XBee Remote Kit and a process called zoning.
The team behind the project is [Doug], [Benjamin] and [Lucas]. They hope to solve the inconsistent temperature problems, which are caused by a moving sun, by open-sourcing their work into the community.
Their XBee system runs on a mesh network making it a perfect tool for sensing and communicating which areas in the house are too hot or too cold. Once the data is collected, XBee modules route the information wirelessly to each other until it reaches a central Arduino gatekeeper; which then decides if it wants to heat, ventilate, or air condition the room.
Not to mention all the added benefits posted below:
Continue reading “THP Entry: Cut Energy Consumption by 30 percent with this WiFi XBee Setup”
With the lessons learned from the Egyptian, Libyan, and Syrian revolutions, a few hardware and software hackers over at Lulzlabs have taken it upon themselves to create a free-as-in-beer and free-as-in-speech digital communications protocol that doesn’t deal with expensive, highly-surveilled commercial and government controlled infrastructure. They call it Airchat, and it’s an impressive piece of work if you don’t care about silly things like ‘laws’.
Before going any further, we have to say yes, this does use amateur radio bands, and yes, they’re using (optional) encryption, and no, the team behind Airchat isn’t complying with all FCC and other amateur radio rules and regulations. Officially, we have to say the FCC (and similar agencies in other countries) have been granted the power – by the people – to regulate the radio spectrum, and you really shouldn’t disobey them. Notice the phrasing in that last sentence, and draw your own philosophical conclusions.
Airchat uses an off the shelf amateur transmitter, a Yaesu 897D in the example video below although a $30 Chinese handheld radio will do, to create a mesh network between other Airchat users running the same software. The protocol is based on the Lulzpacket, a few bits of information that give the message error correction and a random code to identify the packet. Each node in this mesh network is defined by it’s ability to decrypt messages. There’s no hardware ID, and no plain text transmitter identification. It’s the mesh network you want if you’re under the thumb of an oppressive government.
Airchat has already been used to play chess with people 180 miles away, controlled a 3D printer over 80 miles, and has been used to share pictures and voice chats. It’s still a proof of concept, and the example use cases – NGOs working in Africa, disaster response, and expedition base camps – are noble enough to not dismiss this entirely.
Continue reading “Airchat, The Wireless Mesh Network From Lulzlabs”
[Andrew] just finished his write-up describing electronic conference badges that he built for a free South African security conference (part1, part2). The end platform shown above is based on an ATMega328, a Nokia 5110 LCD, a 433MHz AM/OOK TX/RX module, a few LEDs and buttons.
The badges form a mesh network to send messages. This allows conversations between different attendees to be tracked. Final cost was the main constraint during this adventure, which is why these particular components were chosen and bought from eBay & Alibaba.
The first PCB prototypes were CNC milled. Once the PCB milling was complete there was a whole lot of soldering to be done. Luckily enough [Andrew]’s friends joined in to solder the 77 final boards. He also did a great job at documenting the protocol he setup, which was verified using the
open source tool Maltego. Click past the break to see two videos of the system in action.
Continue reading “Building a Mesh Networked Conference Badge”
[Pinoccio] is currently an Indeigogo crowd-sourced project that aims use the real-world programmability of the Arduino through the internet using a wifi connection. One could rightly point out that this can already be done through the use of a wifi shield. Before ruling this device out, just “shush your shussins” and consider that it’s designed specifically for interfacing with “things” over the internet. This can replace several components (see 1:10 in the video after the break) and should be less of a hassle.
Additionally, with a shield on one of these devices, several other [Pinoccio] boards can communicate with the Internet using this as a hub in a mesh network. This is similar to how the many “smart” electrical meters work, with a grid router being a central hub for communications. Additionally, this board has a built in temperature sensor and a RGB (instead of a single-color) LED, so you can do some interesting stuff with it right out of the box. Assuming this project gets funded, which seems likely at this point, we’re excited to see the projects that get built using it! Continue reading “Pinoccio – An Ecosystem for the Internet of Things”
Since he’s got several Raspberry Pi boards on hand [Eric Erfanian] decided to see what he could pull off using the robust networking tools present in every Linux installation. His four-part series takes you from loading an image on the SD cards to building a mesh network from RPi boards and WiFi dongles. He didn’t include a list of links to each article in his post. If you’re interested in all four parts we’ve listed them after the break.
He says that getting the mesh network up and running is easiest if none of the boards are using an Ethernet connection. He used the Babel package to handle the adhoc routing since no device is really in charge of the network. Each of the boards has a unique IP manually assigned to it before joining. All of this work is done in part 3 of the guide. The link above takes you to part 4 in which [Eric] adds an Internet bridge using one of the RPi boards which shares the connection with the rest of the mesh network.
If the power of this type of networking is of interest you should check out this home automation system that takes advantage of it.
Continue reading “Mesh networking with multiple Raspberry Pi boards”
[Ian Harris] designed a bunch of home automation for his parents using X10 hardware. He was a bit disappointed by the failure rate of the modules and the overall performance of the system so he set out to replace it with his own hardware. Lucky for use he’s documented the journey in a four-part series about mesh networks.
The hardware seen above is his test rig. He’s using a couple of Sparkfun breakout boards to develop for nrf2401a RF transceiver chips. These could be used as slave modules, with a central command device, but due to the home’s architecture wireless signals don’t propagate well from one end of the house to the other. The solution is to build a mesh network that will allow each module to act as a network node, receiving and passing on messages until they arrive at the target device. He’s trying to do this with cheap hardware, selecting the PIC 16F88 which boasts 7 KB or program memory and 368 bytes of ram. In the end it doesn’t take much code to get this running, it’s the concepts that take some time and research before you’ll be comfortable working with them.