Forum Replies Created
-
Posts
-
Yes, but I’m trying to figure out exactly which segments don’t work. Only you can tell me that by cycling through the numbers and paying attention to which segments you expect to illuminate compared to what actually does illuminate.
Based on a few images, I can see that the B segment (upper right segment) does not seem to work. Correct? Are there any others that never turn on? Or do all other 6 turn on with no problem?
To fix the B segment, look at these connections: http://nootropicdesign.com/defusableclock/support/board_segmentB.jpg
What happens when you change the time with the MIN and HOUR buttons? I need a better indication as to which segments are not functioning. If a particular segment does not work on any digit then I can tell you which connections to check. Is there any consistency between the digits?
The schematic and board design are here: http://nootropicdesign.com/defusableclock/design.html
Sounds like you are asking for a simpler layout? I’m not sure how it could be simpler.The Video Experimenter cannot manipulate the video image.
It can overlay pixels, do rudimentary capture, and other things on the projects page, but it cannot affect the original signal.Initialize with:
pinMode(pinNumber, INPUT_PULLUP);
This will tie the pin to 5V with a pullup resistor. To activate ground the pin and it will read LOW.
read with:
if (digitalRead(pinNumber) == HIGH) {
tv.print(50, 50, "text");
} else {
tv.print(50, 50, "something else");
}A really long wire would be easy! Just solder one of the button pins that is not ground, and one that is, to your new remote button.
No, SD cards are too slow for realtime recording/playback. I used SRAM so that audio could be recorded while it’s being played back at the same time, like for echo effects and such. You can’t do that with SD cards.
Servo motors require timer interrupts, and that won’t be compatible with using the Video Experimenter, which requires very precise timing in order to generate the video signal. Anything requiring interrupts is not going to work well with the Video Experimenter, I’m afraid.
I don’t think the ATmega328 chip is damaged because it’s running.
I would check the connections on the resistors and diodes. Feel free to send a picture, too.Definitely not a software issue. Look for shorts, and feel free to send a clear picture of the back of the board to support@nootropicdesign.com.
That’s strange behavior. Is there anything causing connections on the back of the board to short out? Are you touching the back of the board, especially near the crystal?
Feel free to send pictures of the back of the board so I can have a look.
