Day: August 23, 2014

Being aware that oneself is in a dream can be a difficult moment to accomplish. But as [Rob] showed on his blog, monitoring the lucid experience once it happens doesn’t have to be costly. Instead, household items can be fashioned together to make a mask that senses REM sleep cycles. We were tipped off to the project by [Michael Paul Coder] who developed an algorithm to communicate inside a dream.

[Rob] cut up plastic milk cartons for this ‘DreamJacker’ project and attached a webcam to produce a simple way to detect eye movements. A standard game adapter with a triangular array of white LED’s was added to the plastic cover in order to provide the necessary illumination needed for the camera. After testing it out, he switched to red light to balance sensitivity issues. Another iteration later and [Rob] attempted to create hypnagogic imagery during the drowsiness state that occurs right before falling asleep. He did this by fitting a single tri-color LED that he scrapped from Christmas lights that were dumped on his street.

The mask is tied to the back of the head with shoelaces, and acts like an eye patch during Wake Back to Bed sessions (WBTB). The end result produces an eerie looking graph of eye twitching taken throughout the night. We would be interested confirming that this setup helps the user experience a lucid dream, so it might be time to make our own.

Since writing his post, [Rob] has since adapted a mouse for use inside the mask cup to integrate with the LucidScribe REM FIELD-mouse plugin developed by [Michael Paul Coder].

After seeing an earlier Hackaday post on old, old Unix systems loading up our retro edition, [Eugenio] decided he would play out the late 90s browser wars on a few machines of his own. Yes, it’s Internet Explorer vs. Netscape in a fight to the death. No <blink> or <marquee> tags were involved, but a Sun Ultra 5 was. We’re looking at the peak of the workstation world circa 1999 here, and only one browser would emerge victorious (it’s neither IE nor Netscape, btw).

The Solaris 9 system [Eugenio] has supports both Internet Explorer 5 and shipped with Netscape 4. Compared to the functionality of modern browsers, both IE5 and Netscape 4 are ancient and terrible. Remember kids, even the scroll wheel on a mouse is a relatively new invention.

Our retro edition doesn’t have any CSS, Javascript, or any of the new Web weirdness, so everything loaded as it should. One interesting problem [Eugenio] encountered was an inverse color desktop when the IE5 window was in focus. Bringing another window into focus returned the desktop to the right color. I guess Netscape wins the Solaris browser war.

[Eugenio] also dug out an old VT320 terminal and connected it to a Vaio x505 (the same approximate vintage as the Sun Ultra 5). This worked beautifully in both 80 and 132 column mode.

We’re always looking for new submissions of old computers loading up our retro site. We haven’t had many minicomputers loading the site, so dig out those Vaxxen and send something in.

Inspired by the detonator in the Captain America: The First Avenger movie, [Jon] modified a normal Zippo lighter to activate a relay on a receiver module. His instructables shows how to create such a device by adjusting the insert in such a way that if someone flipped it open, all they would see would be a flint wheel, flint, wick, and all that stuff; nothing would be abnormal. In order to do this, the components would have to be perfectly concealed.

To acquire a remote signal, [Jon] used the whole metal case as an antenna instead of replacing the wick with one. An antenna pin on an RF module was attached to the insert to get the necessary effect. The flint wheel was then turned into a button and a notification LED was installed. Once the code was uploaded and a receiver module was fashioned together, the end product produced a flash of sparks on the other end.

This hack was made for educational use, and is only meant for demonstration purposes.

During our trip out to Vegas for Defcon, we were lucky enough to catch up with a few of the companies that should be of interest to Hackaday readers. One of the companies based out of the area is Pololu, makers and purveyors of fine electronics and robots. In an incredible bit of lucky scheduling, LV Bots, the Las Vegas area robot builders club, was having an event the same weekend we were there. A maze challenge, no less, where builders would compete to build the best robot and write the best code to get a pile of motors and electronics through a line-following maze in the fastest amount of time.

The Bots

The LV Bots events are held in the same building as Pololu, and unsurprisingly there were quite a few Pololu employees making a go at taking the stuff they developed and getting it to run through a maze. At least one bot was based on the Zumo kit, and a few based on the 3pi platform. Interestingly, the Raspberry Pi Model B+ was the brains of quite a few robots; not extremely surprising, but evidence that the LV Bots people take their line-following mazes seriously and are constantly improving their builds.

Each robot and builder ‘team’ was given three runs. For each team, the first run is basically dedicated to mapping the entire maze. A carefully programmed algorithm tries to send the robot around the entire maze, storing all the intersections in memory. For the second and third runs, the bot should – ideally – make it to the end in a very short amount of time. This is the ideal situation and was only representative of one team for that weekend’s event.

In June 2014, Google revealed a low-cost Smartphone Adapter and VR SDK at their annual software developer conference in San Francisco, California. During the event, Google handed out 6,000 cardboard kits and released a tutorial online, which prompted homemade versions to surface on the web within three hours. This then sparked an iPad case manufacturer to fashion together their own cardboard VR kit that could be bought for $25. After a week, Google gained over 50,000 downloads of their cardboard Android app.

Although the popularity of this VR viewer skyrocketed extremely fast, the idea for a cheap VR solution is nothing new. Developers have been experimenting with these types of objects for years. In fact, a group of Cupertino high school sophomores debuted a similar device called ‘Face Box’ at an entertainment and technology conference at Stanford University on June 17, more than a week before Google’s I/O presentation. A few months earlier, researchers at the Mixed Reality Research Lab (MxR) at USC launched an open source DIY VR website that showed how to create virtual reality headsets with a 3D printer. The smartphone enabled head-mounted display had schematics for both Android and iPhone. The MxR lab was where [Palmer Luckey] worked at as an engineer before founding Oculus (the company that Facebook eventually acquired for approximately $2 billion). So when [Palmer] saw that Google released their cardboard kit, he vocalized his opinion by calling it a clone of his colleagues’ research on Reddit.

When [Willem] visited home last year, he stopped in at his grandparents’ house and found that his very active 93-year-old grandfather had recently gone almost completely blind and was passing the days just sitting in a chair. [Willem] suggested that he listen to audio books, but his grandfather wasn’t receptive to the idea until [Willem] convinced him that the well-narrated ones can be very gripping and entertaining. Once his grandfather was on board, [Willem] knew that he needed a much more accessible solution than a tiny device with tiny controls, so he built an RFID audio reader using a Raspberry Pi.

[Willem] has posted the build details at his personal site. Essentially, the box you see above contains a Raspi and an RFID reader. He created different ‘books’ by placing RFID cards inside of DVD boxes, which makes them more tangible and accessible. When a book is placed on the box, the RFID reader tells the Pi which mp3 files to load. The large colored buttons let the user pause, rewind 20 seconds, and control the volume.

We love to see this kind of build. It’s simple, effective, and greatly enhances the user’s quality of life. [Willem]’s grandfather loves it and uses it every day.

Some people aren’t too crazy about the rush of RFID enabled credit & debit cards, and the problem is, you don’t really have a choice what card you get if the bank sends you a new one! Well if you really don’t like this on your card for whatever reason, it’s pretty easy to disable.

[James Williamson] recently got a new debit card with RFID technology — the problem is it was messing with his access card at work, the readers would beep twice, and sometimes not work. He decided to disable it because of this and that he didn’t really use the tap to pay feature, nor was he completely convinced it was as secure as the bank said.

Since these RFID chips use antennas made of copper wire, he could have just started slicing his card with a knife to break the antenna — but, since he has access to a CT scanner, he thought he’d scan it to figure out where everything was.

Simply make a small notch in the edge of your card, or snip off one of the corners. This breaks the antenna and prevents power to the chip when held near a reader — though if you don’t have access to a CT scanner you might want to double-check next time you buy something!

Now there is another side to this — maybe you actually like the whole tap to pay thing, well, if you wanted to you could get a supplemental card, dissolve it in acetone, and then install the RFID chip into a finger ring for Jedi-like purchasing powers!