All things considered I think it is amaizing that it survived this run,
Definitely…But maybe there is a limit (16Bit) for the maximum number of recordings that can be handled by the cam on the SD card ...
The script logs this if set_record fails. If this happened, then all subsequent shooting would likely also fail (though later attempts to shoot of half press could coincidentally switch to rec on many cameras)
Day 21 Sat Jun 1 11:50:10 2019 lens retraction waitDay 21 Sat Jun 1 11:51:22 2019 rebooting nowDay -- Sat Jun 1 11:50:57 2019 === Ultimate v4.8 : 11:50 ===Day -- Sat Jun 1 11:50:57 2019 CHDK 1.5.0 s95 100k May 6 2019
just out of curiosity, why is the 'rebooting now' time later than the startup time.
Day 21 Sat Jun 1 21:11:04 2019 IMG_0539.JPG tv: 0.6 f: 3.1 ISO: 75 bv: 14 V: 3.949Day 21 Sat Jun 1 21:11:30 2019 IMG_0539.JPG tv: 0.6 f: 3.1 ISO: 75 bv: 5 V: 3.949Day 21 Sat Jun 1 21:12:04 2019 IMG_0540.JPG tv: 0.6 f: 3.1 ISO: 75 bv: -2 V: 3.953Day 21 Sat Jun 1 21:12:34 2019 IMG_0541.JPG tv: 0.6 f: 3.1 ISO: 75 bv: -11 V: 3.94Day 21 Sat Jun 1 21:13:04 2019 IMG_0542.JPG tv: 0.6 f: 3.1 ISO: 75 bv: -19 V: 3.949Day 21 Sat Jun 1 21:13:34 2019 IMG_0543.JPG tv: 0.6 f: 3.1 ISO: 75 bv: -27 V: 3.953Day 21 Sat Jun 1 21:14:00 2019 IMG_0543.JPG tv: 0.6 f: 3.1 ISO: 75 bv: -35 V: 3.949
@waterwingz, if your explanation is right that it only reads RTC at startup, why isn't that time used after the reboot? I would suspect the reboot simulates a startup (it at least resets the tick-counter) thus shouldn't the CF reboot with that time and thus set the time in CHDK as well?
I have found another strange thing after reboot and I think this needs more attention than the time-traveling features of the cam related to this or to reyalps remark of set_record fail?
This is quite interesting. Before I dig deeper into it, it would be nice to see a much bigger piece of log file. Can you post the whole thing somewhere and sent me a link? Or at least the part of the log including the reboot message and then all the shots up until the skipped images, and then a couple hundred shots after that?
Did you find anything or thought of something that could help us track down and solve this timing issue after reboot?
I am missing some frames that i haven't tracked yet in the log, since there are only 4 double numbers in the log and i'm missing 8 on day 21.
Started by piltdown_man
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by hulland
General Help and Assistance on using CHDK stable releases
Started by SkyWalker9
« 1 2 ... 8 9 »
Completed and Working Scripts
Started by keithsok
General Discussion and Assistance
Started by vincasr
« 1 2 3 4 »