Sure, it’s probably a gimmick to [Jon Masters], but we absolutely love the pedal-powered server he built using a group of ARM chips. [Jon] is an engineer at Red Hat and put together the project in order to show off the potential of the low-power ARM offerings.
The platform is a quad-core Calxeda EnergyCore ARM SoC. Each chip draws only 5 Watts at full load, with eight chips weighing in at just 40 Watts. The circuit to power the server started as a solar charger, which was easy to convert just by transitioning from panels to a generator that works just like a bicycle trainer (the rear wheel presses against a spin wheel which drives the generator shaft).
So, the bicycle generator powers the solar charger, which is connected to an inverter that feeds a UPS. After reading the article and watching the video after the break we’re a bit confused on the actual setup. We would think that the inverter would feed the charger but that doesn’t seem to be the case here. If you can provide some clarity on how the system is connected please feel free to do so in the comments.
Continue reading “Pedal-powered 32-core ARM Linux server”
[Ishan Karve] works in some bizarro world where the building management demands that all servers and Uninterruptible Power Supplies be shut down at the end of each evening. While inconceivable to most systems admins, he has no recourse but to comply. This means that his employees need to turn things off before they leave for the day, and since they often work up to 15 hours a day, waiting for Windows server to shut down seems like an eternity.
Being the good manager he is, [Ishan] decided to build a device that handles the clean shutdown of their servers and UPS for them. An Arduino board serves as the brains of the device, communicating with and issuing shutdown commands to the UPS over a serial port. The Arduino is also connected to the office network, enabling it to send ARP requests to the servers in order to determine when they have completely shut down for the day. In order to protect against an accidental shutdown due to network connectivity issues, [Ishan] added an RTC module to the mix so that the Arduino does not issue shutdown commands until at least 8 pm.
Instead of waiting around for Windows to do its thing, [Ishan’s] employees can take off once they start the server shutdown process, knowing that they are totally compliant with their landlord’s crazy requests.
[Arnuschky] was looking for a network storage solution that included redundancy. He could have gone with a new NAS box, but didn’t want to shell out full price. Instead, he picked up a Dell PowerEdge 2800 and hacked it for SATA drives and quiet operation.
It’s not surprising that this hardware can be had second-hand at a low price. The backplane for it requires SCSI drives, and it’s cheaper to upgrade to new server hardware than it is to keep replacing those drives. This didn’t help out [Arnuschky’s] any, so he started out by removing the SCSI connectors. While he was at it, he soldered wires to the HDD activity light pads on the PCB. These will be connected to the RAID controller for status indication. The image above shows the server with eight SATA drives installed (but no backplane); note that all of the power connectors in each column are chained together for a total of two drive power connectors. He then applied glue to each of these connectors, then screwed the backplane in place until the glue dried. Now the device has swappable SATA drives!
His server conversion spans several posts. The link at the top is a round-up so make sure you click through to see how he did the fan speed hack in addition to the SATA conversion.
If your tolerances don’t allow you to glue the connectors like this, check out this other hack that uses shims for spacing.
Around this time last year, [Sprite_TM] took a 1980’s-era Macintosh SE and rebuilt it as a home file server. He used a Seagate Dockstar as the new motherboard, but over the past year he’s been annoyed with the fact that the Dockstar doesn’t have real SATA ports. Using USB to SATA converters on a server is a slow way of doing things, so [Sprite_TM] rebuilt his SE using an HP thin client. To do this, he had to break out the onboard SATA and PCIE; not an easy task, but that’s why [Sprite_TM] is around.
The first order of business was installing a pair of SATA ports. The stock thin client had two NAND-flash chips serving as the drive, both connected to a SATA controller. All [Sprite_tm] had to do was desolder the flash chips and wire up the new SATA connections. Easy enough.
Because the HP thin client only had 100Mbps Ethernet, [Sprite_tm] wasn’t looking forward to the order of magnitude difference between his expected rsync speeds and what he would get with a 1Gbps connection. The only problem is the thin client didn’t have a spare PCIE connection for an Ethernet card. That’s really no problem for [Sprite_tm], though: just desolder the GPU and run a few wires.
Just like last year’s work on his SE, [Sprite_tm] ended up with a functional and very cool home server. The old-school System 7 is still there, and of course he can still play Beyond Dark Castle. Awesome work, in our humble opinion.
This one must have been fun to come up with because it’s got it all. There’s hardware, firmware, networking, and server scripts all working together to create a filing, scanning document center for your business. The best part is that [Janis Jakaitis] was tasked to do this as part of his job (we’re sure there’s a bunch of IT guys shaking their heads at this statement, but it sounds like fun to us!).
The goal was to use an existing document scanner to create PDFs which are then stored in a filing system on the network. Of course it needed to be automatic. The first big issue was that the scanner was USB only, and when connected to a USB-to-LAN bridge the buttons on the device no longer functioned. [Janis] put together an Arduino circuit that added that button, as well as a display to show the status of your scan job.
The next issue is getting the filing system to recognize the document as a unique file. The solution here is to generate a unique barcode label that can be affixed to the page before scanning. Since this is a standalone setup, it was tricky to get the label printer to spit out a unique label. He already had the Arduino working with the scanner, so [Janis] decided to use it to drive this barcode job as well. It calls to a Lua script running on the server, which then pushes the next unique code to the printer.
Tie it all together and you get the demo video after the break.
Continue reading “Using your existing hardware to automate scanning and filing”
Arduino + PS2 controller + R2D2
Here’s an unbelievably real-looking R2D2 replica driven by a PS2 controller with an Arduino inside that plays sounds from the movies. Too bad we couldn’t find any more details about it. [Thanks Bill]
Server build time-lapse
[Justin] and his colleagues spent five days upgrading their server by building a 29-unit cluster. Lucky for us they set up a web-cam to capture the process.
Behold this working desktop computer, complete with monitor and mouse. We’re not sure how it was done, or what it’s for, but worth a peek just because of its size. [Thanks Harald via Dvice]
Modelling self-assembling viruses
A 3D printer and magnets were used to build this model of a self-assembling virus. Shake the jar and it falls apart. Shake a bit more and it’ll rebuild itself… it has the technology.
[Simon] is exercising his geek chic with these Tardis cuff links. The Doctor Who inspired accessories were made from a model railroad telephone booth.
What do you do when it’s time to port the most popular Linux distribution to a completely different architecture? Canonical employee [David Mandalla] works on their ARM development team and recently shared the answer to that question with his fellow Dallas Makerspace members.
Canonical needed a way to compile about 20,000+ packages for the ARM platform, however they did not want to cross-compile, which is quite time consuming. Instead, they opted to build a native solution that could handle the load while ensuring that all packages were compiled securely. To tackle this immense task, [David] and his team constructed a 4U server that runs 20 fully-independent ARM development platforms simultaneously.
The server is composed of 21 PandaBoards, small OMAP development boards featuring a dual-core ARM cortex processor with just about all the connectivity options you could possibly ask for. One board operates as the server head, keeping track of the other 20 modules. When someone requests server time to build a package, the main board checks for unused server, triggering a relay to reboot it before the server is automatically reimaged. Once the pristine, secure environment is ready to go, it’s handed off to the customer who requested it.
If you’re interested in learning more about the build process, [David] has put together a blog with additional details.