From the looks of it this clock is a couple of months ahead of its time. [Oscar] built the clock (translated) taking time to add a lot of goodies into the mix. First up, the parts you see include six large 7-segment displays for hours, minutes, and seconds as well as an LED marquee which can scroll messages. Inside there’s a temperature and humidity sensor for environmental feedback, and an Xbee module which allows for wireless computer control. Time is kept by a DS1307 real-time clock, which is read by an Arduino Uno, then pushed to the display by the pair of I2C addressable SAA1064 drivers. The whole thing was enclosed in four sheets of granite for the box, and a pane of glass for the front. We sure hope it’s well anchored to that wall. You can see it ticking away after the break.
[JP Carrascal] hacked his guitar by adding motion control while removing the need for wires. He’s using a dual-Arduino system with an Mini Pro inside the guitar and a Duemilanova for the receiver connected to a computer. Wireless is provided by the XBee module seen above and a gutted Wii remote accelerometer is in there for motion sensing. Check out the artfully blurry demonstration of the motion effects after the break.
While he added some potentiometer-based controls there is also an automatic power-down feature. [JP] replaced the mono pickup with a stereo one and used the extra conductor as a switch to activate the additional electronics. We wonder if he also winds his own pickups or builds his own effects pedals.
NYC Resistor hosted a wearable wireless workshop today. It was taught by [Rob Faludi] and [Kate Hartman]. They brought along their recently released LilyPad XBee breakout boards. The goal of the class was to use the digital radios to build wireless communication gloves. Above, you can see the conductive thread sewn into the fingertips to key the device. The signal is transmitted to the other glove, which flashes an indicator LED so you can communicate using Morse code.
“The great thing about standards is that there are so many to choose from.” Truer words were never spoken, and this goes double for the hobbyist world of hardware hacking. It seems that every module, every company, and every individual hacker has a favorite way of putting the same pins in a row.
We have an entire drawer full of adapters that just go from one pinout to another, or one programmer to many different target boards. We’ll be the first to admit that it’s often our own darn fault — we decided to swap the reset and ground lines because it was convenient for one design, and now we have two adapters. But imagine a world where there was only a handful of distinct pinouts — that drawer would be only half full and many projects would simply snap together. “You may say I’m a dreamer…”
This article is about connectors and standards. We’ll try not to whine and complain, although we will editorialize. We’re going to work through some of the design tradeoffs and requirements, and maybe you’ll even find that there’s already a standard pinout that’s “close enough” for your next project. And if you’ve got a frequently used pinout or use case that we’ve missed, we encourage you to share the connector pinouts in the comments, along with its pros and cons. Let’s see if we can’t make sense of this mess.
Researchers at Tufts University are experimenting with smart thread sutures that could provide electronic feedback to recovering patients. The paper, entitled “A toolkit of thread-based microfluidics, sensors, and electronics for 3D tissue embedding for medical diagnosis”, is fairly academic, but does describe how threads can work as pH sensors, strain gauges, blood sugar monitors, temperature monitors, and more.
Conductive thread is nothing new but usually thought of as part of a smart garment. In this case, the threads close up wounds and are thus directly in the patient’s body. In many cases, the threads talked to an XBee LilyPad or a Bluetooth Low Energy module so that an ordinary cell phone can collect the data.
The Maker movement is a wildly popular thing, even if we can’t define what it is. The push towards STEM education is absolutely, without a doubt, completely unlike a generation of brogrammers getting a CS degree because of the money. This means there’s a market for kits to get kids interested in electronics, and there are certainly a lot of options. Most of these ‘electronic learning platforms’ don’t actually look that good, and the pedagogical usefulness is very questionable. Evive is not one of these toolkits. It looks good, and might be actually useful.
The heart of the Evive is basically an Arduino Mega, with the handy dandy Arduino shield compatibility that comes with that. Not all of the Mega pins are available for plugging in Dupont cables, though – a lot of the logic is taken up by breakouts, displays, buttons, and analog inputs. There’s a 1.8″ TFT display in the Evive, an SD card socket, connectors for an XBee, Bluetooth, or WiFi module, motor drivers, a fast DAC, analog inputs, and a plethora of buttons, knobs, and switches. All of this is packed into a compact and seemingly sturdy plastic case, making the Evive a little more durable than a breadboard and pile of jumper wires.
You can check out a remarkably well produced video for the Evive below.
Sometimes the journey is as interesting as the destination, and that’s certainly the case with [Marc]’s pursuit of measuring his sleep apnea (PDF, talk slides. Video embedded below.). Sleep apnea involves periods of time when you don’t breathe or breathe shallowly for as long as a few minutes and affects 5-10% of middle-aged men (half that for women.) [Marc]’s efforts are still a work-in-progress but along the way he’s tried a multitude of things, all involving different technology and bugs to work out. It’s surprising how many ways there are to monitor breathing.
His attempts started out using a MobSenDat Kit, which includes an Arduino compatible board, and an accelerometer to see just what his sleeping positions were. That was followed by measuring blood O2 saturation using a cheap SPO2 sensor that didn’t work out, and one with Bluetooth that did work but gave results as a graph and not raw data.
Next came measuring breathing by detecting airflow from his nose using a Wind Sensor, but the tubes for getting the “wind” from his nose to the sensor were problematic, though the approach was workable. In parallel with the Wind Sensor he also tried the Zeo bedside sleep manager which involves wearing a headband that uses electrical signals from your brain to tell you what sleep state you’re in. He particularly liked this one as it gave access to the data and even offered some code.
And his last approach we know of was to monitor breathing by putting some form of band around his chest/belly to measure expansion and contraction. He tried a few bands and an Eeonyx conductive textile/yarn turned out to be the best. He did run into noise issues with the Xbee, as well as voltage regulator problems, and a diode that had to be bypassed.