Wordclock 0.4

I did some updates to the software of the wordclock. It couldn’t really cope with interference, and since it relies on updates from the DCF77 receiver every minute it doesn’t really work as soon as something interferes. I was a little surprised how much the signal is affected by everyday things. TVs, for instance, at least the CRT kind, which is still widely used. My main problem turned out to be the lights of my aquariums, which are neon tubes. They too affect the radio signal, which I confirmed with a “normal” radio controlled clock.

To account for these issues I modified the code to display the time from the Arduinos internal clock. This internal clock is not very accurate, from what I gathered on the Internet it is off by a couple of seconds after only a day or so. For that reason I use the radio clock signal to set the internal clock when it gets a clean signal, which should be every day at night when all interfering sources are turned off. That way the RTC chip i mentioned earlier in this post is not really necessary.

I updated the main article about the clock to reflect these changes, the new software is available for download there as well.

Controlling the boats motors from Android

So, I finally managed to get the basics done and put them together. First were the ESC for the motors. I had ordered two Turnigy 30A ESC for brushed motors from HobbyKing and it took “only” six weeks for them to be delivered. I guess it was my fault, ordering right before the chinese new year, when nobody seems to work for the next two weeks. At least neither my order was processed nor my questions were answered by the support. Anyway, they arrived eventually and I connected them to the motors, the battery pack and the Arduino. Continue reading Controlling the boats motors from Android

Keep serial pins free!

This weekend I did some final troubleshooting on my first wordclock. I had the problem that every time the display was updated all LEDs flickered a little. Very annoying, especially when there is no change.

Finally it hit me: I had connected the 74HC595 chips to the pins 1, 2 and 3. I guess I just wanted to “start” somewhere. What I didn’t account for, is that Arduinos serial port is accessible via pins 0 and 1. They are even labeled with RX and TX. So, everytime I sent data to my computer over the serial line it also went out on pin 1, which is connected to the 74HC595, hence the flickering.

Long answer short: Don’t use pins 0 and 1. Except for serial connections of course.