With a script. If you are using ptp, you can do something likeCode: [Select]=set_led(0,1)=set_led(0,0)=set_led(1,1)=set_led(1,0)
=set_led(0,1)=set_led(0,0)=set_led(1,1)=set_led(1,0)
=set_led(2,1)=set_led(2,0)
Post screenshots of the record and playback mode palettes and I'll see if it can be easily fixed (or improved). This port does not have custom colors implemented so it won't be ideal.
For reference:If the CHDK option is set to "Auto", the canon firmware should take a dark frame if the shutter speed is set >= 1.3 seconds in the Canon UI. The display will probably show "busy" for roughly the same time as the exposure time.
If the CHDK option is set to "Off", no dark frame should be taken.
If the CHDK option is set to "On" the dark frame should be taken with a Canon UI shutter speed < 1.3 seconds.
Hope these help?Record:Playback:
Here's a test build with Phils palette patch applied
Here's a test build with Phils palette patch applied and the AF led updated for the MD test.
Just to confirm, were the dark frame tests you did using my earlier test build?
Also, which LEDs (if any) did the other two set_led options control?
lua set_led(5,1)lua set_led(5,0)lua set_led(8,1)lua set_led(8,0)
MD_tune.bas results: 100 triggers -> min 40 max 1030 Av 228 (darkish room pointed at a phone 10cm distance)
Quote from: reyalp on 02 / February / 2015, 16:16:34Also, which LEDs (if any) did the other two set_led options control?nothing.For the record - the cam was connected to chdkptp via a 7 port hub - I had an SD card reader in another port. These:Code: [Select]lua set_led(5,1)lua set_led(5,0)lua set_led(8,1)lua set_led(8,0)turned the led on/off within the SD card reader as though an SD card had been inserted/removed
=return call_event_proc('System.Create')=return call_event_proc('Driver.Create')
=return call_event_proc('LEDDrive',0,0)=return call_event_proc('LEDDrive',0,1)
You don't need a huge number of triggers, 10-20 should be fine. A very dark environment might cause problems because the camera may reduce the live view frame rate. This usually only happens for night shooting, normal indoor lighting should be fine.
If 0 and 1 actually don't do anything, this is another bug. If you want, you can find the actual numbers using the LEDDrive eventproc. With native called enabled, use the following in chdkptpCode: [Select]=return call_event_proc('System.Create')=return call_event_proc('Driver.Create')These should both return zero. Then for every LED you want to tryCode: [Select]=return call_event_proc('LEDDrive',0,0)=return call_event_proc('LEDDrive',0,1)The first number is the LED number. This is NOT the same as the numbers used by CHDK, but will probably range from 0 to 9 or something like that, possibly with multiple values triggering the same LED.The second value turns the LED on or off. 0 turns the LED on, 1 turns it off.The function will probably return nonzero if the LED number is not valid.Looking at the SX150 the activity LED on the back and the AF LED are probably the only ones.
> =return call_event_proc('System.Create')3:return:0> =return call_event_proc('Driver.Create')4:return:0---> =return call_event_proc('LEDDrive',7,1) ---> does nothing14:return:0> =return call_event_proc('LEDDrive',7,0) ---> turns back led ON !15:return:0> =return call_event_proc('LEDDrive',7,1) ---> turns back led OFF !16:return:0---> =return call_event_proc('LEDDrive',9,1) ---> does nothing19:return:0> =return call_event_proc('LEDDrive',9,0) ---> turns AF assist ON !20:return:0> =return call_event_proc('LEDDrive',9,1) ---> turns AF assist OFF !21:return:0
retest -> 20 triggers min 40 max 70 Av 62 (normal lighting - pointed at a white paint wall)
> =return call_event_proc('LEDDrive',7,0) ---> turns back led ON !15:return:0> =return call_event_proc('LEDDrive',7,1) ---> turns back led OFF !16:return:0
Yes, as I said "The second value turns the LED on or off. 0 turns the LED on, 1 turns it off."
I've updated the set_led function so no set_led(0) is the green status LED, and set_led(1) is the AF led.
> =set_led(0,1) -> status led ON> =set_led(0,0) -> status led OFF> =set_led(1,1) ->AF assist led ON> =set_led(1,0) ->AF assist led OFF
check the if the Canon and CHDK OSD looks reasonably correct in chdkptp live view with UI overlay enabled.
If you can post the output of =return get_meminfo(),get_meminfo('system'),get_meminfo('aram'),get_meminfo('exmem')
> =return get_meminfo(),get_meminfo('system'),get_meminfo('aram'),get_meminfo('exmem')10:return:table:{chdk_start=63589344,free_size=719952,chdk_size=135120,allocated_size=1347480,free_block_count=9,name="combined",allocated_count=1805,chdk_malloc=true,free_block_max_size=373752,allocated_peak=1412760,total_size=2067576,}10:return:table:{start_address=1531112,chdk_start=63589344,free_size=373752,chdk_size=135120,allocated_size=1165392,free_block_count=1,allocated_count=860,name="system",end_address=3070256,chdk_malloc=true,free_block_max_size=373752,allocated_peak=1191312,total_size=1539144,}10:return:table:{start_address=3530752,chdk_start=63589344,free_size=24,chdk_size=135120,allocated_size=139192,free_block_count=1,allocated_count=349,name="aram",end_address=3670016,chdk_malloc=true,free_block_max_size=24,allocated_peak=139200,total_size=139264,}10:return:table:{start_address=63724464,chdk_start=63589344,free_size=344520,chdk_size=135120,allocated_size=44568,free_block_count=5,allocated_count=616,name="exmem",end_address=64113632,chdk_malloc=true,free_block_max_size=344456,allocated_peak=82248,total_size=389168,}
and verify that it runs and is able to shoot correctly
Started by pizzicat Firmware Dumping
Started by hiker_jon General Discussion and Assistance
Started by slyth999 General Discussion and Assistance
Started by gtoonstra « 1 2 ... 5 6 » General Discussion and Assistance
Started by rdx1968 General Help and Assistance on using CHDK stable releases
