Member Since: December 19, 2006

Country: United States

  • Sounds like SparkFun is so excited that they're starting early! Arduino Day is planned for April 2nd:

  • It should work, using the files here:

  • One correction to the jumpers discussion on the "Board Overview" page: the VCC jumper only effects the VCC pin on the unmounted 6-pin (2x3) ISP header. The ATtiny always receives power from the board's USB connection, regardless of whether the VCC solder jumper is open or closed.

    Or, at least, that's the situation on the version of the board that's currently for sale. It looks like this tutorial is written for a newer, still un-released version, which may have a different behavior for the VCC solder jumper.

  • One thing that might be interesting to try is automatically generated image files (e.g. PNGs) each time you commit a hardware design file (e.g. Eagle file, SketchUp). GitHub has some reasonably good tools for comparing different versions of image files, so having an image for each version of, say, an Eagle schematic could go a long way towards being able to see the changes between versions. I think it might be possible with some combination of a Git commit hook and an Eagle script.

  • This programmer doesn't work in place of an FTDI cable or breakout board, i.e. you can't use it to program an Pro Mini (or similar) over serial on the 6-pin header. You could use it to reburn the bootloader onto a Pro Mini (although this shouldn't be necessary in normal use), but you'd have to connect to the MISO, MOSI, SCK, and RESET pins of the Pro Mini.

  • Interesting. The programmer shouldn't need much power itself. Do you have anything connected to it (besides the ATtiny)?

  • Weird. It sounds like an intermittent communication issue. Maybe the ATtiny is loose in the socket? Alternatively, I wonder if there's a program on your computer that's occasionally scanning / using the attached USB devices and disrupting the communication (e.g. something that's looking for connected cellphones or printers or something like that)? What operating system are you on?

  • This sounds awesome!

    I would suggest that whatever format you settle on as the default, you also collect and make available files in the native format for the CAD program that they were created in. For example, SolidWorks or Rhino or whatever in addition to the STL. That way, others who have the same software will be able to update or adapt the model.

  • Hmmm, you shouldn't need any drivers on OS X. What error message or behavior did you see when you tried to use it?

  • Weird, I haven't seen that problem before with these. Does it always happen in the same location (byte 0x0100)? Does it happen with all of the chips?

No public wish lists :(