Forum Replies Created
-
Posts
-
setting the wires to be fixed instead of random is simple. Just change the assignment in the function countdown().
For example, if you want the defuse wire to be wire 2:
defuseWire = WIRE_2;
Arduino 1.6.x deals with PROGMEM data differently because of changes in GCC. Try the attached sketch. All the bitmaps are included in the .ino file now, so there is only one file in this new version.
Note that this is for the v2 version of the board. If you have a v1 version (e.g. sold by Adafruit) let me know.Thanks for those links, IChop. Yes with some cleverness and additional components, it could be possible.
That’s great to hear. Embedded programming is much more challenging than writing software on a computer that has enormous resources. Working in a constrained environment is what brings out creativity and cleverness. It will make you a better coder.
Fantastic build, Jason! That looks awesome.
Is it ok if we post this picture to the gallery?
https://nootropicdesign.com/defusableclock/gallery.htmlHow about some details on the code that won’t compile? I can help if you actually show me the error.
Unfortunately, you need a LOT of pins to read a keypad.
http://nootropicdesign.com/projectlab/2010/04/03/keypad-tutorial/The Defusable clock uses the standard pinout: RTS, RX, TX, 5V, NC, GND
RTS and DTR are compatible. NC means “not connected”. RTS is on side marked “GRN” and ground is on side marked “BLK”. Green and black are the standard colors on FTDI cables.Some resources:
https://www.sparkfun.com/products/9717
https://learn.adafruit.com/introducing-pro-trinket/using-ftdiYou only need a driver for the FTDI device. Nothing else. Looks like a permissions problem of some kind.
Hmm, that looks like some kind of Windows permissions problem with the serial port. Never heard of that before. Try looking in the arduino.cc forums http://forum.arduino.cc/
