Last November I bought two RASClock modules; one for keeping time for our Model Town Minster's chimes and one as a spare. After initial minor glitches, the chimes have kept perfect time since we switched them on around March 31st this year.
We have now moved on to another project and last weekend I borrowed the spare for use in the prototype of the new system. I have had major timekeeping problems with this and cannot work out why. The battery is new and measures 3.1 V, so I'm fairly sure it can't be that.
What is different to last time is as follows:
- We are running Raspbian Stretch and the Afterthought Setting Up Instructions only cover Wheezy and Jessie. I followed the instructions for Wheezy.
- I admit to making a mistake initially, when I set the RASClock up, in that I forgot to comment out the two lines which contain --systz. That has now been done.
- Our Pi Zero is connected via a ribbon cable to a PCB with various interfacing devices on it. The IDC connector on the end of the ribbon prevents the RASClock from being connected directly to the Pi, so I laid out six pins on the board to replicate the first six GPIO pins and wired the corresponding ends of the ribbon to these pins. The RASClock therefore sits on the PCB about 2-3 cm from the GPIO. I've checked the voltages; they are correct and hwclock works fine.
After each of the activities described above, the system was shut down and left for the periods indicated.
Can you suggest what might be wrong here?