Automate Git and Upgrade Your Battle Station With a Custom Peripheral

[mfaust] wakes up in the morning like a regular person, goes to work like a regular person, types in tedious commands for his software versioning utilities like a regular person, and then, as a reward, gets his coffee, just like rest of us. However, what if there was a way to shorten the steps, bringing us all closer to the wonderful coffee step, without all those inconvenient delays? Well, global industry is trying its best to blot out the sun, so mornings are covered there. [Elon Musk’s] thinktank proposed the hyperloop, which should help with the second step. [mfaust] built a control station for his versioning software. Raise your cup of joe high for this man’s innovative spirit.

He first laid out all the buttons, LED lights, and knobs he’d like on a panel to automate away his daily tasks. Using photoshop he ended up with a nice template. He laminated it to the top of a regular project box and did his best to drill holes in the right places without a workshop at his command. It’s pretty good looking!

Since this is the sort of thing an Arduino is best at he, in a mere two tries, wired everything up in such a way that it would all cram into the box. With everything blinking satisfactorily and all the buttons showing up on the serial out, he was ready for the final step.

Being a proficient and prolific enough developer to need a control panel in the first place, like a sort of software DJ, he wrote a nice interface for it all. The Arduino sits and waits for serial input while occasionally spitting out a packet of data describing its switch status. A Java daemon runs in the background of his computer. When the right bits are witnessed, a very nicely executed on screen display reports on the progress of his various scripts.

Now he can arrive at the hyperloop terminal during the appropriate work time slot in Earth’s perpetual night. After which he simply walks up to his computer, flips a few switches, glances quickly at the display for verification, and goes to drink some nice, hydroponically grown, coffee. Just like the rest of us.

Simple Clock from Tiny Chip

If you haven’t jumped on the ESP8266 bandwagon yet, it might be a good time to get started. If you can program an Arduino you have pretty much all of the skills you’ll need to get an ESP8266 up and running. And, if you need a good idea for a project to build with one of these WiFi miracle chips, look no further than [Ben Buxton]’s dated, but awesome, NTP clock.

Continue reading “Simple Clock from Tiny Chip”

Bring Doping, Microfluidics, Photovoltaics, and More Into the Home

Can you make a spectrometer for your home lab all from materials you have sitting around? We might not believe it from a less credible source, but this MIT course does indeed build a spectrometer from foam board using two razor blades as the silt cover and a writable CD as the diffraction grating. The coolest part is removing the metal backing of the CD.

mit_experiments_thumbHackaday reader [gratian] tipped us off about the course available from MIT courseware called Nanomaker. It boils down some fairly complicated experiments to the kind one can do in the home lab without involving thousands of dollars of lab equipment. The whole point is to demystify what we think of as complicated devices and topics surrounding photovoltaics, organic photovoltaics, piezoelectricity and thermoelectricity.


Spectrometers are used to analyze the wavelengths of a light source. Now that you have a measurement tool in hand it’s time to build and experiment with some light sources of your own. Here you can see an LED that is the topic of one of the course labs.

If you have a bit of background in chemistry this is a good step-by-step guide for getting into these types of experiments at home. It reminds us of some of the really cool stuff [Jeri Ellsworth] was doing in her garage lab, like making her own EL panels.

Continue reading “Bring Doping, Microfluidics, Photovoltaics, and More Into the Home”

Arduino vs. Phidgets vs. Gadgeteer

A few days ago, we saw a dev time trial between the Arduino and Phidgets, a somewhat proprietary dev board that is many times more expensive than an Arduino. The time trial was a simple experiment to see which platform was faster to prototype simple circuits. As always in Hackaday comments, there was a ton of comments questioning the validity and bias of the test. Not wanting to let a good controversy go to waste, [Ian Lee] tossed his hat into the ring with the same dev trial with the Gadgeteer.

The Gadgeteer has the same design philosophy as Phidgets: modular components and a unique software system -the Gadgeteer is based on .NET Micro Framework – that allows you to get up and running quickly. Unlike Phidgets, the Gadgeteer is priced competitively with the Arduino, and the mainboard is priced within an order of magnitude of a single ATMega chip.

[Ian] pulled off three projects with the three development platforms: blinking a LED, moving a servo, and building a pedometer with an accelerometer. For each trial, the time taken and the price of all components were added up. Here’s the relevant graph:

Continue reading “Arduino vs. Phidgets vs. Gadgeteer”

Arduino vs. Phidgets – Dev Time Trials

Is developing on an Arduino too slow? Are Phidgets too expensive? When might you use one or the other? Hackaday regular [Ken] breaks down what he learned from three experimental time trials.

The main development differences between Arduino and Phidgets are a mix of flavor preferences and some hard facts. The Arduino is open source, Phidgets are proprietary. Arduino requires a mix of hard- and software where Phidgets only needs (and only allows) a connection to a full computer but enables high level languages – it is expected to get the job done sooner and easier. And finally, Arduinos are cheap, Phidgets are 3-5x the cost.

The three time trials were common tasks: 1. Blink an LED. 2. Use a pot to turn a servo. 3. Build a pedometer. For [Ken], the Phidgets won in each of the three experiments, but not significantly: 37%, 45%, and 25% respectively. The difference is only minutes. Even considering time value, for most hackers it is not worth the cost.

HAD - Phidgets3In context, the advantages of a mildly more rapid development on the simplest projects are wasted away by needing to rebuild a permanent solution. Chained to a PC, Phidgets are only useful for temporary or fixed projects. For many of our readers that puts them dead in the water. Arduinos may technically be dev kits but are cheap enough to be disposed of in the project as the permanent solution – probably the norm for most of us.

[Ken] points out that for the software crowd that abhor electronics, Phidgets plays to their preferences. Phidgets clips together their pricey peripherals and the rest is all done in code using familiar modern languages and libraries. We wonder just how large this group could still be; Phidgets might have been an interesting kit years ago when the gulf between disciplines was broader but the trend these days is towards everyone knowing a little about everything. Hackaday readers probably represent that trend more than most, but let us know if that seems off.

[Ken]’s article has much more and much better detailed explanations of the experiments and the tradeoffs between the platforms.

If you enjoy watching parallel engineering, see the time-lapse video below for a split screen of the time trials.

Continue reading “Arduino vs. Phidgets – Dev Time Trials”

Bare-metal Programming On The Teensy 3


The Teensy 3.x series of boards are amazing pieces of work, with a tiny, breadboard-friendly footprint, an improbable number of IO pins, and a powerful processor, all for under $20. [Karl Lunt] loves nearly all the features of the Teensy 3, except for one: the Arduino IDE. Yes, the most terrible, most popular IDE in existence. To fix this problem, [Karl] set up a bare-metal development environment, and lucky us, he’s chosen to share it with us.

[Karl] is using CodeBench Lite for the compiler, linker, assembler, and all that other GCC fun, but the CodeSourcery suite doesn’t have an IDE. Visual Studio 2008 Express is [Karl]’s environment of choice, but just about every other IDE out there will do the same job. Of course a make utility will be needed, and grabbing the docs for the Freescale K20 microcontroller wouldn’t be a bad idea, either.

The end result is [Karl] being able to develop for the Teensy 3.X with the IDE of his choice. He was able to quickly set up a ‘blink a LED’ program with the new toolchain, although uploading the files to the Teensy does require the Teensy Loader app.

The story behind developing the Sifteo from an engineer’s perspective


The video game industry must be one of the most secretive sectors when it comes to developing the electronic hardware used in the gaming consoles. The big guys don’t want to give anything away — to the competition or to the hackers who will try to get around their security measures. But it seems Sifteo doesn’t share those secretive values. We had a great time reading about the bumpy ride for the developers bringing the gaming system from concept to market. [Micah Elizabeth Scott] wrote the guest post for Adafruit Industries. She was brought on as an engineer for the Sifteo project just after the first version of the interactive gaming cube was released. From her narrative it seems like this was the top of the big hill on the roller coaster ride for the company.

What’s seen above is one gaming cube. The system developed in [Beth’s] story puts together multiple cubes for each game. The issue at hand when she joined the company was how to put more power in the hardware and rely less heavily on a computer to which it was tethered. She discusses cost of components versus features offered, how to deliver the games to the system, and all that the team learned from studying successful consoles that came before them like the long line of Nintendo hardware. It’s a fascinating read if you’re interesting in how the sausage is made.