Hello Jonathan. First of all, thank you for sharing your work. While I grew up surrounded by RS232 cables, the serial setup sounds not practical and user friendly.
In a couple of my firmwares I hardcoded DST changeovers for 100 years (eats up 100 bytes): you only need to reset the clock at a known point in time&DST when RTC battery backup is lost. Someone here mentioned a DST button, which is pretty elegant (and easily implemented if you don't care about the date). Another approach I collected on neonixie-l is to step backwards 1 when setting hours, then going forward, so you don't have to loop through. I think that automatic DST is a must if you have an alarm function, otherwise it is a programming exercise :) "Cosmetics" a friend of mine used to say. I think your setup misses a motion detector. Maybe you would add a scrolling display of date-time? Again, it's a programming exercise :) By the way, is any of the known clocks scrolling the information? I like the idea of a rotary encoder, and it should be super easy to set time with it (no more need for archaic serial). A thought more hardware-wise: how about allowing for -optional- individual anode current adjustment (I know it takes board space)? In any case, a shared project is good by default. Keep up your work. Paolo -- You received this message because you are subscribed to the Google Groups "neonixie-l" group. To unsubscribe from this group and stop receiving emails from it, send an email to neonixie-l+unsubscr...@googlegroups.com. To post to this group, send an email to neonixie-l@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/neonixie-l/CABj2Vabb9hYTojjZNMi6uO0A_Wxj%3D1jy%2Bg26d2RGBAxB6gOduA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
