Blue Labs

Software and Hardware for the Future

David David Ford, software and electronics
Rob Rob Magee, software and electronics
Tanner Tanner Koebel, software and research

Welcome to Blue Labs.

We write a lot of random and sometimes useless bits of software mostly for ourselves. We build things that blink, beep, and move around. We put software on powerful computers and read data from microcontrollers. Sometimes it runs on a sprinkler controller, a saltwater reef aquarium, a vehicle, or your common personal computer.

Sometimes the software we write gets used by others and we make a moderate attempt to keep things updated. wink Every now and then, the software we write is used to save lives by helping first responders get ultra-fast notifications with advanced on-scene data using technology now commonly in the pocket of nearly every person ― a smartphone.

A lot of Blue Labs time and effort is folded back into the Open Source community. Patches, debugging, and code development contributions have been provided to projects such as Sendmail, PostgreSQL, Apache, Python, WAMP, and the Linux Kernel.

Blue Labs has been around for over three decades helping the world learn, achieve, produce, a little here, a little there. Blue Labs was informally established in 1987.

Of course, not everything we do goes on GitHub. Some of our projects' early life cycles evolve heavily on breadboards such as this CAN bus module being designed to control all the vehicle's fans based on thermister values, logic state of the A/C compressor, cabin environment controls; all accessory lighting based on door latch position sense and cluster switches; window positioning based on moisture detection and internal static air temperature; door lock engage and release upon signal from remote module.

Occasionally our work requires 3D modeling and printing. We are not yet at the industrial age where STL files can be expected to exist for most common objects. We do release nearly everything we model with an Apache 2 style license.