t=os.date('*t') -- current date / time as tableset_clock(t.year,t.month,t.day,t.hour + 1, t.min, t.sec)
t=os.date('*t', os.time() + 10)set_clock(t.year,t.month,t.day,t.hour, t.min, t.sec)
A ptp function to sync cams´ with computers´ clock could be useful, at least for rigs with cams with outdated battery.
I'm still convinced that the RTC is more accurate than OS clock. If that is true setting RTC with set_clock will not solve the floating time of OS clock...it just makes it less visible
In my experience, the RTCs are not very accurate.
So I assume that the RTC has a non-influenced, thus stable, clock (maybe not atomic clock accurate, but consistant) while the OS clock is fluctuating because of the system reaching max load/throughput.What do you think?
* A clock running 1 s per day too fast has an inaccuracy of 1/(3600*24) = 11.57 ppm* A deviation of 1 s per week means 1.65 ppm
The temperature dependence may be particularly significant for CHDK timelapse applications, because operating continuously for long periods can result in high internal temperatures that would be less common in normal usage.
The OS clock is based on a high frequency timer on the SOC which I would expect to be fairly accurate and relatively unaffected by CPU load, but I don't really know.
On cams with GPS. Is it possible to synchronize time with GPS time?
Started by Killer G.
General Help and Assistance on using CHDK stable releases
Started by Grognerd
Started by PovertyLabs
Started by mr.burns
General Discussion and Assistance
Started by alvm
« 1 2 »