Hi Jurs, odometer, stowite,
apologies for delay in replying , i have been up at the clock tower today looking at the clock that is in there , it was installed 23 years ago , i think it is a synchronous motor that is fitted , i also found a sticker of the supplier on it, a google check has shown they still exist and i am going to call them in the morning , i may be lucky and it is one with a sync wire fitted.
Regarding your posts replies are below
I think that is the basic program then as you wanted it:
- chiming at full hours, 4 seconds between single strikes
- automatically summertime switching between UTC and BST time.
- with exception: no chiming strikes during night hours
- with exception: no chiming strikes when set to "silent" by button
- with exception: 12 chiming strikes at midnight on new year
- LCD display of time and bell icon
yes that is correct
But as I understand, you would prefer, that date/time setting could be done with the device itself, no other device attached, right?
yes i would like it to be on the device setting , either by buttons or rotary encoder i dont mind if it took a reasonable amount of time to set , so either rotary or buttons whatever is easiest to be implemented.
What do you think? Would it be possible to replace the button in your application with such a rotary encoder with button and then try to adapt my menu for date/time setting from the other thread for your application?
Create the full hardware now, prepared to be used for functions that are not available yet and need to be implemented later by programming a firmware update? But for now use the sketch that you have?
use the existing sketch as a firmware, only the button function of the encoder is used
Jurs, i am more than happy to use the software as it is now , with the addition of the rotary encoder (button use only at this time)
I am concious of the input and effort you have put into this for me up to know , for which i am truly grateful, if you wish to work on it further it will totally be on your timescale with no feeling of pressure from me.
I will be spending the next couple of weeks monitoring the physical clock against this one to see how far out they may be and what correction will be needed .
Consider using MSF ( http://www.npl.co.uk/science-technology/time-frequency/products-and-services/time/msf-radio-time-signal ) to synchronize your DS3231. For my clock whenever the DS3231 is more than 2 seconds in error I update it with MSF time; this is fairly infrequent since the DS3231 is very accruate.
msf is not receivable reliably on the south west tip of Ireland so wasnt a reliable option. Nice thought though, i built a pic msf clock a 3 years ago when i was over in the uk
In my apartment is a DS3231-based clock. I set it only once or twice a month, and then only by maybe 1 or 2 seconds each time (I know, I am anal about my clocks).
As long as your chimes are within 1 minute of the correct time, I doubt that too many people would care about the difference. Especially if it's on an island.
re apartment clock setting thats serious OCD lol , I agree with you re being within 1 minute of actual clock , so long as the minute hand is pretty close to the 12 o clock position ie minute either side i dont think folks will notice ( although there will always be one that does )
There is temperature compensation built in, but I have no idea how well it works in real life. Probably more than good enough for "island time".
where the clock is located the temp rarely drops below 4 degrees in winter , and a mild frost was last seen around five years ago, i suppose time will tell and i think it will be monitored by me for at least the next six months . The main aim of the project is to bring a piece of history back to life , the last time the bell rang was 1922.