[Michael]

oh, so you are using code from this project? http://nootropicdesign.com/projectlab/2011/03/20/arduino-computer-vision/

Yes, you could easily limit the area you are interested in. Just change the bounds in the program. It currently searches the whole width and height of the screen with these loops:

for(int y=0;y
for(int x=0;x
...

}

} 

[Michael]

Yes, you can mix it onto the incoming signal. There is an example project showing how to mix signals:
https://nootropicdesign.com/projectlab/2013/07/05/3-track-looper/

Study this project and you’ll see how to mix together. There is a description in the project writeup.

[Michael]

Ok, best of luck. I still don’t see how you can change the brightness. Analog pins are analog input, not analog output.

[Michael]

You can’t change the brightness in software. The LEDs are not driven by PWM. They are driven by a 7-segment driver chip.

You can make them dimmer by changing the 8 150 ohm resistors under the display to larger values. For example, 220 ohms, or higher. Just try some things, I think.

You can power the clock from 12V, but the regulator will get warmer. Not too warm, just warmer. Any regulator that takes in 12V input and ouputs 5V needs to dissipate the power as heat, so all regulators should output the same amount of heat.

[Michael]

I guess it’s not possible. Sorry, I’m not working on or supporting the Layers library any longer. The Processing team told me they removed it from processing.org, but it seems to still be there. It does not work with the newest version of Processing.

[Michael]

not sure what you are asking. Which project are you doing? What does your code do?

[Michael]

Thanks much for the feedback. Glad you had a successful build!

[Michael]

It’s not as easy as copy/paste — you do need to understand it. If you understand how to use the chip select pins, and which address ranges go to which chips, then you can do it. If you have no micorcontroller programming experience, then this is definitely diving into the deep end of the pool.

[Michael]

You would need to use an additional Arduino pin as the chip select pin for each new chip you add. For example, if you add 2 more chips, you could use digital pins 3 and 4 for the chip select pins.

Do you have experience with SPI? You would have to make changes to the Audio Hacker library to support more chips. Have you studied the library code?

[Michael]

No. This question is answered in the FAQ: http://nootropicdesign.com/audiohacker/faq.html

[Michael]

Bon chance, my friend!

[Michael]

Thanks for the videos.

Ok, did you ever change WIRE_3 to OUTPUT and set it HIGH while it was connected to ground? If so, you will destroy the I/O pin on the microcontroller.

I think you may have done that accidentally as you were making code changes.

[Michael]

Are you saying that the clock worked correctly when you received it?

I think your wires are not connected well. Make sure each terminal on the right side is connected to ground. All four terminals on the left side are at ground. Use a multimeter to ensure that all terminal blocks are at ground when all wires are attached.

[Michael]

WIRE_3 is an INPUT pin, not an OUTPUT pin. You can’t “write” the value to LOW. The purpose of an input pin is to read its value to see if it is shorted to ground or not. If WIRE_3 is connected to ground (by a wire), then digitalRead(WIRE_3) returns LOW. If not, digitalRead(WIRE_3) returns HIGH.

if you are trying to use WIRE_3 as an output, then you need to set pinMode(WIRE_3, OUTPUT).

[Michael]

Yes, you can certainly use sockets if you’d like.

[Author]

Posts