Ambient Orb Setup
Posted: June 1, 2009 Filed under: Hardware, Software Leave a commentThis page describes the process of hooking an Ambient Orb up to show a real-time information using the Ambient Hardware Developer’s Kit.
Previous Work
The Orb provides a great, at-a-glance indication of build status for a continuously integrated software project. The subjects of Continuous Integration and its benefits are discussed in a number of other places, so I won’t cover them here. Likewise, the use of an Orb using the Ambient Web API is covered admirably by Michael Swanson, so you can read that there.
Problems
The two problems I found were:
-
Update lag
The Ambient pager network does not change the color of an orb for 10 – 30 minutes. I can break a build in seconds. An ideal system would indicate the status of software builds in real time with no lag.
-
Integration of multiple software projects
I work in a shop that produces a lot of different projects at a time. We currently have eleven builds managed by CruiseControl.NET. Using NAnt events as described elsewhere did not provide an easy way to measure how many builds were successful moment-by-moment.
Solution
Lucky for me, the first problem can be solved with hardware. As a software guy, I love when that happens. Ambient produces a Hardware Developer’s Kit. You put an Orb on one end and a serial port on the other, and you’re in business: you can update the orb instantly to any color you like.
Unfortunately, the cable is only 3 feet long, making the orb’s location a bit constrained. This was easily solved with a cheap 50-foot serial cable. As a bonus, the $45 (with shipping) HDK frees me from the $80/year subscription to Ambient’s developer channel, so the hardware investment will pay for itself within the first year.
To have the Orb reflect the status of multiple software projects all at once, I polled the CruiseControl.NET server. For now, I’m using a screen scrape of the CruiseControl dashboard. With a little gumption, I could probably poll the same port that CCTray uses.
Keeping in mind that I might not always use CruiseControl as my CI solution, and that I might change the way I poll it for build status, I thought it would be nice to keep those changes insulated from the core orb updating service.
I’m a native speaker of Perl, so that’s the language all of this is in. I used Win32::Daemon by Dave Roth to create a Windows service in Perl. The service talks on the serial port using Bill Birthisel’s Win32::SerialPort package and updates the colors using my Win32::AmbientOrb package.
How to Do It Yourself
This Walkthrough describes how to set up the whole system.
Lazy Part 4
Posted: April 28, 2006 Filed under: Build, Software Leave a commentPart 4: Talking to Yahoo! Music Engine
So the remote has been programmed to impersonate a CD player remote, and the computer can detect when it’s sending commands. Now I just need to actually do something with the commands.
Good News
When I installed Girder, I found out that it’s already got a Yahoo! Music Engine plugin configured. It can handle Play, Pause, Stop, Skip, etc., so my initial goal of skipping Nickelback songs looks to be within easy reach. As a bonus, Girder also has plugins for WinAmp, Windows Media Player, and just about any other software you could be using to control your playlist.
To actually make use of Girder, you will need to visit each event in the included Yahoo! Music Engine GML and make usre it’s listening for its events from the remote you just set up. Just visit the event you want to define:
and double-click it to set its properties. When you get there, set the Event Device to the remote you just created: 
Budget
After my initial investigation, I expected to spend just under $150 and 20 hours to get this done. I spent $143.44, so for once I was under budget. If you already have a universal remote that you like, you really could do this with just the UIRT and Girder ($103.60 with shipping). As far as time, there were two parts of this that went surprisingly smooth: Girder’s YME plugin saved me hours of capturing commands, and the IrToWav software made it super easy to program the remote with exactly the right codes for all of my devices. I actually spent only 9 hours on this, and since I already found the parts and vendors, you could get through this exercise in even less time.
Next Steps
At this point, I have achieved my initial goal of being able to control my playlist using the same infrared remote I use for the rest of my stereo equipment. Along the way, some other interesting questions and challenges presented themselves. If I’m feeling particularly ambitious in the future I might plan to pursue one of these:
Changing Stations
I might decide after skipping ten tracks in a row that maybe I’m just listening to the wrong station. It would be cool if I could set up a list of favorite channels or playlists and change to them with the remote.
RF Remote Control
This setup works great in my living room where I’m already holding an infrared remote control (unless Blake has stolen it). But I have speakers on my back porch too and the IR remote doesn’t really cope well with the sliding glass door. I live in Phoenix, so infrared opacity is important, and I’m not willing to change glass. An RF remote would solve this problem and free me from the line-of-sight requirement.
Breakeven Analysis
I know how much time and money I spent on this. I’m willing to ignore the money for now. A vanity website baron such as myself has little time for such material concerns anyway. The real scarce resource is time. I had my faithful assistant clock me while I made round trips to the computer and back to my seat skipping crappy music tracks. 13 seconds per trip, average. Then he clocked me using the remote: 2 seconds. That’s a net time savings of 11 seconds per crappy music track.
I don’t have data concerning the ratio of music I’ll tolerate to music I won’t, so we will work from a model. If each song is 3½ minutes long and 3% of them are crappy enough to be skipped, my 11 second advantage breaks down to .001571429 seconds saved per second that I listen to music, or about 5.7 seconds per hour. To look at it another way, I’ll be hearing about 17 songs per hour, with a little more than one crappy song every two hours, but the song will only waste 2 seconds of my life, not 13.
If I listen to music for an average 30 minutes a day, it will only take me 191 listening days to break even on my 9 hour investment. I drove the golden spike uniting Yahoo! Music Engine and my remote on March 20, 2006. That means that on September 27, 2006, I will have regained all of the time spent putting this together. This is considerably more favorable than if it had taken 20 hours as I predicted at the beginning. That would have put my breakeven point at May 18, 2007. Still acceptable.
Summary in 10 Words or Less
Not as hard as I expected and totally worth it.
Final Budget: $143.44, 9 hours
Lazy Part 3
Posted: March 31, 2006 Filed under: Build, Hardware, Software Leave a commentPart 3: Talking to the Computer
For my next trick, I’ll need an assistant: the USB-UIRT. This is that gadget that’s going to receive infrared signals from the remote. I’ll also need the Girder software to learn the codes my remote is sending and actually do something with them. For now, I’m just going to be satisfied with proving that my PC is hearing what the remote is saying. Making the software do anything about it is a matter for another day.
I’ll only be needing a handful of buttons here. They’re all standard play controls and appear on just about any remote.
- Power (to open or bring focus to the application)
- Play/Pause
- Stop
- Previous Track
- Next Track
- Shuffle
- Repeat
Hardware Installation
Dude. That couldn’t have gone much easier. Plug in the UIRT and the Plug and Play dialog finds it. You download the drivers from the USBUIRT site and tell the PnP wizard where to find them. Done.
Software Installation
This was also a cakewalk. Come to think of it, it was much easier than a cakewalk. I’ve participated in several of those and never walked away with a thing. Here there is no cake, but at least I have something to show for my effort.
Telling Girder About It
Go to File -> Settings, select “Plug-in settings,” and check the box next to “USB-UIRT.” Restart Girder and you’re off & running.
Setting Up Your Remote
Go to Tools -> Add Remote Wizard. Click Next, name the remote, then start programming. It asks you to press any button to make sure it detects a remote at all, then it asks you to press each button that you want to use on the remote. After you finish this, Girder will be able to get signals from your remote. 
All of this only took me an hour, and most of that was poking around trying to figure out what else Girder could be used for. I went ahead and picked buttons to use for song rating too. If everything goes smooth, I’ll not only be able to skip sucky tracks, but ban them for good measure. Next, I’m going to make Girder listen for the signals from my remote.
Budget update: $143.44, 8 hours.
PowerfulMojo 
