Day 1 NOV 24 00:20:00:2017 V: 2.733 T: 32 <no shot>
I found the 'debug' mode which seems to put ultimate into a repetitive loop and lots of shots were saved to the card.
I then set it up to run all night expecting a card full of shots this morning. Instead I get 3 shots saved and the log showing no shot each time there should have been?
I think for CCTV alarm triggered still shots I need to learn some lua script writing because Ultimate has different concepts.
Will CHDK external trigger still work when a script is running,
does a running script take priority over normal CHDK functions and every button and camera setting has to be defined in the script?
I will spend a little more time with Ultimate, but I think it is too heavyweight to unpick and give me something more suited to CCTV.
Again it did far more than I need, but it can bypass the timer to accept remote USB trigger and fire single shots. Unfortunately, it doesn't handle the Canon maximum file number limit, won't overwrite old files and stops at 'Card Full', something I think all intervalometer scripts should include to avoid the 'time bomb'.
One issue to cope with is stick formats all cards 4Gb and below as single partition FAT 16 and cards >4Gb as 2 partitions FAT16 for boot and FAT32 for CHDK and shots. I am not sure yet how a script will manage deleting old files if the camera firmware (or CHDK?) is automatically generating new folders with each containing <2000 files if I understand correctly.
but I can see me wearing out the card slot.
Hi, can somebody please help me understand and confirm the 'hierarchy' and priority of camera setting options and settings when using CHDK and scripts?
1. There are the normal Canon firmware options which can be accessed when the card write protect tab is off and the camera doesn't boot to CHDK. When the camera then auto boots to CHDK does it use the Canon settings or replace/overide them in its own menus?
2. Mode options can be set using the Canon function wheel - AUTO, MAN, etc. Can I assume CHDK doesn't interfere with these pre-sets?
3. Many new options can be set with CHDK, but do the Canon settings have priority if set before CHDK loads?
4. If a script is loaded and running, does the script replace CHDK settings? i.e is the CHDK base firmware still running and a script interacts with it or does a script replace CHDK. When I'm switching back and forth between a script menu and the CHDK menu, I'm not sure what is running or what has priority?
I'm trying to get my head around these three ways of changing camera 'variables': Canon firmware settings, CHDK, and Scripts and how each interacts. At a very basic level I need to know if scripts just change what CHDK does as default by reading the status of settings then changing them, or scripts have to initialise settings from scratch?
Incidentally, I've finally found out why these Canon Powershot 'A' series cameras give so much trouble with low battery warnings after testing my A560 on a bench power supply: The Canon firmware does more than just measure battery voltage. At power on it measures battery internal resistance by measuring the peak current against some reference value. The A560 takes about 350mA with the lcd lit and 80mA unlit so it must be calculating a peak value which will support flash recharging. I think the flaw is in the Canon firmware, because many low battery situations will support loads more shots. It's a shame the Canon algorithm appears to be responsible for dumping loads of re-chargeable batteries. Even a 2.5Amp bench supply can max out their internal resistance algorithm and put up occasional low battery warnings. The warnings remain persistent until the camera is re powered. I can stop this behaviour by adding a large capacitor to the supply wiring. I now test all my niMh batteries for internal resistance and the variation between brands is surprising. I also re-test after a few charge discharge cycles because some do not stay good. My battery of choice for consistent performance is the non-rechargeable Lithium AA. When I find Canons current sense resistor on my camera I will change its value. When people try to fix this problem by cleaning battery terminals, they are just trying to lower the battery internal resistance which the camera measures at power on. I think the real problem is with Canons measurement algorithm? The low battery voltage threshold set by Canon was for 1.5V cells like high capacity Duracells. There is a greater voltage margin for these cells than NiMh which start at 1.35V fully charged.
Incidentally, if you scroll down through the script parameters to the one that says Action if card full and set it to [ Delete ] , you should be able to watch it shoot one shot, delete it, shoot another shot, delete it, over & over with your SD card configuration.
Started by Brandon00151
General Discussion and Assistance
Started by hph@
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by geordienz
General Discussion and Assistance
Started by tileboy1
General Help and Assistance on using CHDK stable releases
Started by Intheswamp