@EB2: Since the main object is the psycological effect of the non-periodic tick of the clock, I expect the effect will be maximized if all of the visual effects (pendulum meter, tube base, tube "wires") are synchronized to the non-periodic tick.
I did see that work of art. Since the main object is the psycological effect of the non-periodic tick of the clock, I expect the effect will be maximized if all of the visual effects (pendulum meter, tube base, tube "wires") are synchronized to the non-periodic tick. If they are independent, it may morph into random noise, and the intended effect will be lost.
If Max doesn't want to "fire up" the tube, perhaps fake illuninated wires to these terminals. Translucent tubing with addressable multi-color LED strips inside. You could have multi-color light "chasers" showing capacitive flux flowing in and out of the tube.
It's got two longish pins coming out of the bottom -- at the moment I just have two holes drilled through the MDF -- they are just the right diameter to give a nice friction fit to the extent that you could turn the thing upside down and the tube wouldn't fall out (not that I plan on doing that, you understand :-) But it's easy to remove the tube (for transportatiion, for example) by just pulling it off.
When it comes to the real cabinet I'm not sure what I'll do -- I had thought of applying a bit of hot glue to the pins inside the cabined, but I do like the idea of being able to easily remove the tube -- but that decision is a while away yet.
@Rcurl: This may be caused by a recent windows update that included code from FTDI that bricks fake FTDI chips. Some Arduinos are known to be affected by this. Look here:
Thanks for the info.
I pretty much use a Mac to program my Arduino so unless Apple did the same thing as Microsoft I'm not sure mine has been bricked the same way. It appears in a device manager on a windows machine as an unknown device with error 43.
There are articles and other utilities for recovering the USB chip but all have failed on Mac and Windows. I have been powering the board through the USB port so I think it has at some point received a few to may millivolts thus destroyed the chip, which would be My Bad unfortunately:-(