I have been working on the wind turbine Wi-Fi repeater and communication node for several years now, and I am proud to say that the project is finalized. During 2009, the emphasis was making sure that the turbine would work reliably regardless of the weather that blew through Rochester. This was easier said than done, but by the end of the 2009 school year all aspects of the project were working correctly. In fact the turbine even charged an electric bicycle for the RIT Innovation Festival Green Vehicle challenge.

For 2010, the next phase of the project was to incorporate a power monitoring device and to improve the performance of the wind turbine. For the past year my friend David Brenner, and I have been working on an Arduino based power meter which would remotely measure the power the turbine was producing and then send the data through the Internet back to a server. Work progressed slowly since this was a side project for David and I, and we were both busy with school work and clubs. We eventually got everything working in the lab, but when we moved the power meter to the field we ran into a few software bugs. We needed to incorporate an auto reconnect function for the Arduino as occasionally the wireless link would stop working for a couple of seconds, closing the data connection. Additionally, the idle power readings would fluctuate slightly since the battery voltage would change over time. An improvement would be to use voltage regulators to power the circuitry instead of running it directly off the batteries. Luckily we came up with some software solutions and everything worked correctly. Once everything was up and running it was really cool to remotely see the power output of the wind turbine.

Earlier in the year, a bearing in the first motor died and I just replace the motor with a smaller Ametek 30v motor that I had lying around. The Ametek performed fine, but it didn’t produce as much power as the first motor. When spring came around and the wind died down, the batteries started to lose their charge. To fix this issue I upgraded to a much larger motor, which practically doubled the power output during windy days. Additionally, I added a 30W solar panel to help produce power during the summer when there is little wind in Rochester. The wind turbine and solar panel complement each other great in Rochester, as it is cloudy and windy in the winter while the summers are sunny with little wind. With the new motor and solar panel, the battery issue was totally resolved.

This past May, David and I entered the Wind and Solar Powered Communication Node into the annual RIT IEEE Design Contest. There were many impressive student projects and David and I were fortunate to win the award for “Most Innovative Project.” We were extremely pleased with the award, especially since we had devoted so much of our free time working on the project, most of it outside in the freezing cold. Sadly, a week after David and I won our award, RIT notified us that we would have to relocate the wind turbine as a parking lot was going to be built where the turbine stood. Since I was graduating and no longer would live in Rochester, I decided to dismantle the project and focus on some other priorities. While the wind turbine project is no longer standing at RIT, no all is lost. Dave and I documented all aspects of the project and created a great website: www.turbinehotspot.com which explains the project and contains numerous pictures and videos.

Every night at RIT I would walk by closed computers labs, but to my amazement the computer and monitors remained powered on. As an institution that promoted its sustainable practices, not turning the computers off when the labs were closed seemed hypocritical. Every year students would complain about this issue, but nothing was ever done. My roommate, Ian Mikutel, and I decided that we would do something about RIT not having a computer power policy.

Ian and I met with the Chief Technology Officer of RIT, and she agreed that the idea of either turning computers off or having them sleep when they were not utilized was a great idea. We pursued the idea further and started meeting with ITS, the organization that managed a majority of the RIT computer labs and FMS, which was responsible for providing electricity to the buildings. Ian and I decided to implement an actually computer lab trial to demonstrate that a computer power policy could be successfully implemented and to measure the power savings. After many meetings we decided that putting the computers into S3 sleep mode after 20 minutes was the best way to maximize student productivity while minimizing power consumption. Having the computers sleep instead of turning them off ensured that computers would still receive security updates and patches in the middle of the night.

FMS installed a power meter to monitor the power consumption of the 16 Dell desktop computers in the lab. This allowed us to quantize the power savings of having the computers automatically sleep after 20 minutes. After modifying some files and fixing a couple configuration issues the computers automatically went to sleep and automatically awoke in the middle of the night to install security updates. We monitored the power consumption for around 10 weeks, and discovered that having the computers sleep reduced the labs power consumption by 66%! Everyone working on the project was amazed at the results, and when we extrapolated this to the thousands of computers at RIT, the environmental and monetary impacts are massive. Ian and I presented to the RIT’s Committee on Sustainable Practices which was very impressed with our presentation and decided to begin implementing computer sleep mode across campus. Ian and I have both recently graduated so we will not see the end results of our work, but we are both extremely proud to have made such a difference in reducing the power consumption across RIT.

I have spent the last six months working on my RIT Graduate Project involving Femtocells.  After a great deal of research and writing over 80 pages, I have come to the conclusion that femtocells will not be the magical solution to capacity and coverage issues for wireless carriers.  This was a very surprising conclusion as numerous experts and companies supporting the technology have a much different viewpoint.  In my paper I discuss how I came to my conclusion and outlined that femtocells are a temporary solution until Wi-Fi chipsets are universal to all cell phones.   In the current market place, wireless carriers don’t seem to be pushing femtocells, but instead Wi-Fi based solutions which not only offer greater capacity but are also cheaper to deploy.  AT&T Wireless has had great success with offloading data usage by deploying Wi-Fi access point, something that femtocells have yet to deliver.  I could be completely wrong in my analysis, but I believe that Wi-Fi will be the perfect companion to 4G networks.    Until 4G coverage is widespread femtocells will be play an important role in expanding coverage, but I believe their deployments will be limited.

Click Here to Download my Femtocell Paper

I have been working on an independent study to revamp the telecom lab here at RIT.  The telecom labs has lots of cool equipment such as Cisco ONS optical transport gear, Fiber to the home PON equipment, T1/T3 multiplexers, hybrid fiber coax equipment, and class 5 central office switches.  Most of the lab hardware is time division multiplexed (TDM) based, but in today telecom environment everything is going IP.  The lab’s TDM based hardware does a great job of emulation a central office network, but the IP network in the lab is more like a home network than an ISP.  For my independent study I am changing this by re-designing the lab IP network to implement BGP and MPLS.

A great tool for working with Cisco IP based networks is GSN3.  GNS3 is a GUI based Cisco router emulation tool.  Designing and building networks in emulation is far easier and a massive time saver.  Instead of ripping the lab apart and running new cables all over the place, all I have to do is build a virtual lab.  Once I build a virtual lab and configure all the routers successfully, I can copy the configurations over to the real routers in the lab and know that the network will work correctly.  There is minimal downtime since I can keep the existing network up and only deploy the new network once I have verified everything is working.  GNS3 is also great for studying for Cisco certifications since you can configure and setup a network in a fraction compared with the actual hardware.  To learn more about GNS3 visit the official website: http://www.gns3.net/

In the past month my friend David Brenner and I have made a great deal of progress with the wind turbine remote Arduino power meter.  The idea behind the project is to log the amount of power generated from the wind turbine and have the data automatically be uploaded online where it can graphed.  There are similar products on the market, but they are designed for much larger turbine and solar arrays, and thus are expensive.  We wanted to utilize the Arduino micro-controller as it versatile and inexpensive.  With all the parts the costs is around $80, which is a fraction of the cost of other solutions.

The power meter works by reading the current flowing from the turbine.  We are using a Hall Effect current sensor as it is very efficient and can handle up 30 Amps.  Based on the amount of current, the sensor outputs a voltage which can then be read by the Arduino’s analog to digital input.  An issue with the Arduino’s ADC is that it is limited to only 1024 values ranging from 0-5 volts.  This means that the Arduino is not very accurate and can only sense a 4.8mV change.  The issue we had was that the current sensor’s output voltage changes by a very small amount and the change couldn’t be read by the Arduino.  To correct this, we fed the current sensor into an amplifier stage to increase the output voltage so the Arduino could read smaller current changes.  The current sensor outputs 1.5v with no current, so to ensure that we weren’t amplifying the voltage when there was no current we needed to implement a 1.5v offset.

The Arduino microcontroller reads the data from the ADC input and then sends the data through the Internet to a server.  We are utilizing the wireless repeater portion of the wind turbine to transport the data through the Internet.  The server then reads the data and stores it in a mysql data base so graphs can be created.  The Arduino sends a new power reading every one second, so the graphs can be extremely accurate if we wish.  The remote power meter is currently in field trials to ensure the basic functionally works correctly.