Member Since: September 26, 2009

Country: United States



I was an Electrical Engineering student at Purdue University. Now I’m a software engineer at Dwyer Instruments, Inc.


Software Engineer


Dwyer Instruments, Inc.; American Scientific Affiliation

Spoken Languages


Programming Languages

ANSI C, Assembly, C#


Purdue University

  • Thanks for pointing me towards the Teensy 3.1, which looks like a great product.

    However, I’ve been looking forward to playing with the Atmel SAMD21 in an Arduino-shield compatible form-factor. Hence my enthusiasm for the Arduino Zero :)

  • Nice link! Here’s another one describing table-driven state machines:

    Writing Efficient State Machines in C

  • Does anyone know what the future (or history) is of the Arduino Zero? Is it (or Atmel) stuck somehow in a contract with Arduino SRL? Seems strange that SRL has begun selling it, while LLC has not.

    (I want to play with one, but don’t want to order from SRL.)

  • Why isn’t there a royalty for the UNO?

  • Thank you for commenting on this issue.

  • I’m also curious about this. Partially because I care about the future of Arduino. Partially because I’m curious about the state of products like Arduino Zero (only sold by Arduino SRL right now).

  • I’m sooooooo disappointed by the Arduino lawsuits. Not that I understand all the legal stuff going on, but it seems such a shame.

  • Cool use of a PID controller! If anyone is interested, there is an Arduino PID library, as well as an open-source PID controller that uses it. The controller doesn’t have many of the advanced features of a commercial controller, but it’s got all the basics, including auto-tuning.

    (I work for a company that manufactures PID controllers, so this post grabbed my attention.)

  • So I ran an experiment with a Breakout Board for FT232RL USB to Serial:

    I used FTDI’s FT_Prog utility to reprogram the PID to 0x0000. After unplugging and replugging it in, Windows could not find a driver for it. Bricked.

    Then I fired up the Windows Device Manager. After right-clicking on the bricked device, I chose “Update Driver Software” and then “Browse my computer for driver software” and then “Let me pick from a list of device drivers on my computer.” I then get a list of device types, and chose “Universal Serial Bus controllers.” Choosing “FTDI” as the manufacturer, I saw different FTDI drivers (and possibly driver versions?) to choose from. I chose “USB Serial Converter Version: [1/27/2014].” Then I agreed to a scary-sounding Windows warning.

    My computer froze after that (because of the driver install???), but after a restart, the driver was installed, and I used FT_Prog to reset the PID to 0x6001.

    Not sure if that would work with a counterfeit chip, and I also don’t appear to have the latest FTDI driver installed. But maybe this is an option for unbricking?

  • I love the “Toddler Proxy Object.” Very cool project!

Temperature Chamber

adamj537 7 items

Parts to build a really small temperature chamber for experiment…