|
|
XO
 |
 |
 |
 |
Wireless mesh at the beach |
 |
 |
 |
 |
 |
 |
 |
 |
Submitted by sverma on Sunday, May 4, 2008 - 10:07 |
OLPC | XO |
 |
 |
It was a great day to be at the beach in San Francisco (Apr 27, 2008). Thanks to Jason Stone and Jim Stockford for sparing their Sunday afternoon, we met up at Ocean Beach with three XO laptops. The little green machines attract a good bit of attention. Even before we got started with out little experiment, we had people stopping by to ask questions or just check out the green machine.
So, the experiment was: How far will the point-to-point mesh network on the XOs go in relatively clear RF (radio frequency) environment? At least cleaner as far as 2.4 GHz spectrum goes. We did such a run on campus and got about 600 feet max. or so across two XO units. I suspected that this was because our campus has a lot of Wi-Fi traffic, so the interference alone would decrease the hop length. We also have a lot of foliage, so that would add to the interference.
Ocean beach is right along the Pacific at the edge of San Francisco. I hoped that RF would be cleaner there. So, we got started by setting up the mesh of three laptops (me, Jim and Jason) and then got Jim firmly planted (say, position A) in the thick of beach population to answer questions. Jason and I walked south while pinging Jim's laptop all along. Well, we kept on walking...and walking...and walking. This was definitely way beyond 600 feet. Eventually, we started seeing "host unreachable" a few times, so we stopped. We saw ping times of about 25 to 30 ms. Jason became point B there. I kept walking further south and after a few steps, the pinging resumed with low latencies (3 to 5 ms). I kept walking...and walking...and walking. A quick note about walking on the beach. Walk closer to the water. Its a lot firmer and works well when measuring paces (1 pace approximately equals three feet). Eventually, I started seeing "host unreachable". I called Jim to verify. He was seeing the same. I tried holding the laptop higher up and the pings would resume. Eventually, I stopped at what I thought was the outer limit of pings, marked the spot and took the following picture.
|
 |
 |
 |
 |
 |
 |
 |
 |
Third OLPC meet at SF State - a brief, and somewhat late report |
 |
 |
 |
 |
 |
 |
 |
 |
Submitted by sverma on Wednesday, March 26, 2008 - 08:01 |
OLPC | SFSU | XO |
 |
 |
This is a brief report on the third OLPC meet that happened at SF State on March 15. Its a bit late, but I figured, better late than never. It is, after all, Spring break, so work seems like a distant memory. Ah, the joys of selective amnesia!
Coming back to the report. We met on March 15, in a conference room. Attendance was somewhere between 25 and 30 people. What continues to surprise me is that we seem to keep up that number and have different groups rotate through. Some repeat attendees, of course, but majority of the crowd was new.
|
 |
 |
 |
 |
 |
 |
 |
 |
How green is the XO, and how does it get greener? |
 |
 |
 |
 |
 |
 |
 |
 |
Submitted by sverma on Monday, February 25, 2008 - 13:26 |
XO |
 |
 |
The OLPC XO laptop is considered to be one of the most green of machines when it comes to sustainable computing. Of course, sustainable computing does not only mean green, but being green or small-environmental-footprint is a major component. How do computers run with as efficient a footprint as possible? In the following video, Dr. Mary Lou Jepson, the ex-CTO of OLPC explains how she got the XO to be a green machine. Even more important though, is that fact that engineers are currently working hard on a very aggressive suspend-and-resume regimen for the XO laptop where the laptop will be able to suspend and resume on the boundaries of human perception (100 milliseconds or so). The idea being that the computer can remain suspended while you read the contents of a web page (the display is wired separately, so it still displays when the motherboard goes to sleep). That saves power and could effectively increase the runtime to 10 hours per charge. Of course, I am speculating the 10 hour benchmark, but that is the goal; 8 1/2 to 10 hours on one charge. The better part of this scheme is that some day, in the near future, my Sony VAIO running Ubuntu will be able to benefit from this work (FOSS) and will suspend (which it does today) and resume (which it does not) so that I can actually get something like 4+ hours out of my 7 1/2 hour Sony battery.
|
 |
 |
 |
 |
|