OK, I see the difference. David uses a timed system to display the arcs, while I would use a counter system. I would let the amount of displayed objects (arcs) determine the screen refresh rate rather than a pre-defined (timed) rate. For example, the smallest circle I would display exactly 1 time while the largest circle could be 20 times to make it appear with the same brightness. This way I would sequence a list of all the arcs to be displayed, and once at the bottom go immediately to the top. The refresh rate could then well be 200Hz for very few objects or 20Hz for many objects. If you want to make some games for your clock, this method would lead to a larger amount of arcs you can display on the screen, but you would need to hookup Q9 to an external interrupt and re-write the software a bit. You might also have to run the MCU at a higher frequency so that you can still update the D/A converters at the new rate.
Michel On Sep 6, 9:51 am, Oscilloclock <[email protected]> wrote: > You have it, Michel! > > I have several posts on theory in Draft state so be sure to subscribe or > check back once in a while. Until then, (and very likely even AFTER then!), > the best circuit theory explanation is on David's site: > > http://cathodecorner.com/sc200theory.html > > My circuit has not veered greatly from his design. > > Aaron -- You received this message because you are subscribed to the Google Groups "neonixie-l" group. To post to this group, send an email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
