Quote from: waterwingz on 25 / March / 2013, 14:07:22I suppose I could risk testing with my disposable camera (A1200) - { reboot, shoot 10 shots, reboot, repeat. } and see what happens.It's probably noted somewhere, but only reboot when the lens is in retracted state. This is even more important for a camera with a more complicated lens unit (like the SX130).
I suppose I could risk testing with my disposable camera (A1200) - { reboot, shoot 10 shots, reboot, repeat. } and see what happens.
That could be a deal killer if the exposure count doesn't get updated. The picture file names could be duplicated.
I wonder what would happen if you just reset the tick count back to 0? I suspect that all reyalp would break loose!
Is there a propset for that? Simply switching to playback won't retract the lens until the Canon retract delay expires AFAIK.
Quote from: waterwingz on 25 / March / 2013, 14:16:10Is there a propset for that? Simply switching to playback won't retract the lens until the Canon retract delay expires AFAIK.There's an eventproc for that
Quote from: lapser on 25 / March / 2013, 13:41:29That could be a deal killer if the exposure count doesn't get updated. The picture file names could be duplicated. This isn't usually a problem because the camera normally scans the card to figure out the next non-conflicting number (this behavior is explained in the Canon manuals.) It should only bite you if you are deleting images but want to keep the sequence intact.
Quote from: lapser on 25 / March / 2013, 13:41:29I wonder what would happen if you just reset the tick count back to 0?How would that be different than wrapping? We don't know for sure that wrapping is a problem, but it seems unlikely to me that Canon expects uptimes long enough for it to matter.
I wonder what would happen if you just reset the tick count back to 0?
long get_tick_count(){long t;#if !CAM_DRYOS _GetSystemTime(&t); return t;#else return (int)_GetSystemTime(&t);#endif}
Looking into how to reset it to 0, I ended up in wrapper.c...I see a possible problem with this code. CHDK doesn't have "long" as I understand it. So if _GetSystemTime(&t) returns an 8 byte long to a CHDK 4 byte "long", it will overwrite 4 bytes past t. As luck would have it, it looks like those 4 bytes are empty stack.Is this correct, or am I not getting something?It seems that if Canon changed to 8 byte system time, maybe it expects its camera to stay on longer than 2 weeks.
If that 53 days uptime is uninterrupted, then the firmware can perhaps deal with the wraparound?
Unfortunately StoreLensForShutdown no longer exists (at least with this name). The last cameras supporting it are the ones from the first DryOS generation.
Quote from: reyalp on 25 / March / 2013, 16:47:25Quote from: lapser on 25 / March / 2013, 13:41:29That could be a deal killer if the exposure count doesn't get updated. The picture file names could be duplicated. This isn't usually a problem because the camera normally scans the card to figure out the next non-conflicting number (this behavior is explained in the Canon manuals.) It should only bite you if you are deleting images but want to keep the sequence intact.It's a problem, unless the images are still on the card.If I shoot, download, delete and then reboot using CHDKPTP the camera doesn't update the counter so the next images shot will have the same numbers as the previous ones.Requires a power cycle after deleting the images to properly update the image counter.
Then a better method would be to have the script switch to playback mode and then wait one minute (plus a bit) for the lens to retract normally ?
Sorry to be obtuse, but does this mean the image numbering will work correctly after a script initiated restart as long as nothing has been deleted since the most recent power-up? If so, it doesn't seem like a limitation for the OP's desired usage.
It looks like it would work, considering that there's no possibility that the files on the card will change during the reboot.
Started by BHPete General Help and Assistance on using CHDK stable releases
Started by marc.kossa General Help and Assistance on using CHDK stable releases
Started by Stuntman General Help and Assistance on using CHDK stable releases
Started by SkyWalker9 « 1 2 ... 8 9 » Completed and Working Scripts
Started by BZHades « 1 2 3 » General Chat
