> Finally, I finished that propellor clock.
>
> ...
>
> http://www.bubblesoftonline.com/prop4.gif

Nice job, Tony.  So that's what you meant by a propellor clock!

I have done something similar (rotating LEDs to make pixels), and I'm
curious how close the implementations are.  I used a 16C66.  It receives a
timing pulse from an opto interrupter once per revolution.  This is captured
by a CCP module, and the instructions per pixel calculated from that.  Timer
0 is then used to cause an interrupt when it's time to update the LEDs twice
each pixel.  Twice because the display looked stupid if the LEDs were on for
the whole pixels.  I had to match the dots caused by the discrete LEDs in
the sweep direction by having the LEDs completely off every 1/2 pixel.  The
message is stored as ASCII characters, and conversion to pixels is done on
the fly using a font table that takes up most of the program memory.  You
can see a small picture of it at
http://www.embedinc.com/ourportfolio.shtml#eyeball.

If you're willing to tell, how did you do it?  I'm mostly curious whether
convergent evolution drives these kinds of designs mostly in the same
direction, or whether there are fundametally different ways of doing this.
The way I did it seemed obvious to me, but I have no way of knowing what I
didn't think of.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics