SX130 => http://forum.chdk-treff.de/download/file.php?id=2605S110 => http://forum.chdk-treff.de/download/file.php?id=2607
Quote from: JohnW on 03 / January / 2014, 10:07:25I can, but little point I think, both CSV's have no file size and no data contained within - presumably because the camera crashes and powers itself off?True. Usually I open & close log files each time write to them in my scripts. For some reason unknown, I chose to not do that in this script - bad decision. I'll add that to the update list. Don't worry about it for now.Meanwhile, we've learned that with CHDK as it is today, you need to enable Lua native calls, and put thisCode: [Select] call_event_proc("SS.Create") call_event_proc("SS.MFOn")at the start of your script and this Code: [Select] call_event_proc("SS.Create") call_event_proc("SS.MFOff")at the end if you want to use the set_focus() function on the G15.
I can, but little point I think, both CSV's have no file size and no data contained within - presumably because the camera crashes and powers itself off?
Is it necessary to call SS.Create each time?
Here's a version that calls the variants of MFOn / MFOff and registration functions that I know of. If all variants return -1 it will be logged.
After a couple of IRC discussions with reyalp, the consensus is to add a Lua scripting function that disables the various #defined interlocks that decide if set_focus() actually gets issued or not. With all of your help, this will then be used to collect as much information as possible about what works and doesn't for each camera directly at the Canon firmware level. I've attached a patch file that implements this. My preference would have been to put #defines around the changes so that they are only a build option for people doing new ports once these set_focus() tests are complete. However, luascript.c is a module and conditional compilation in modules is strongly discouraged by the CHDK devs.I've also attached a reworked script that captures more information than the previous script. It can run without actually taking any pictures ( shoot_half only ) although there is an option to enable full shots. It also lets you run with interlocks disabled or enabled. And logging opens and closes with each write to preserve as much of the log as possible during testing if there is a crash.The plan now is to update the unstable branch with some variation of this patch and then ask all the testers to load the new version and run the new test script. Be warned that with interlocks disable, some test steps will cause the camera to shutdown. Once that is done, a final determination can be made about how to finally fix CHDK's SD override functions so that they work consistently for all cameras.I'd appreciate feedback on the script changes - for now you can run with the interlocks enabled and any current CHDK build. Post any MF_test.csv and comments here? TIA
My cameras all have SS.Create + PT_MFOn.Version 2.6 attached which adds the PT_MFOn test to the SS.Create block.
Hi,i hav patched my Code and now i get that message:Set Focus Tester v2.5 SX230HS:126 attempt to call global 'set_focus_interlock_bypass' (a nil value)***ABGEBROCHEN***What I have done wrong?By
Started by kwf
General Discussion and Assistance
Started by dzsemx
Started by kmboise
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by Sdack
« 1 2 3 »
General Discussion and Assistance
Started by pigeonhill
« 1 2 »
General Help and Assistance on using CHDK stable releases