ELPH 110 HS (IXUS 125 HS) Porting Thread - page 12 - DryOS Development - CHDK Forum

ELPH 110 HS (IXUS 125 HS) Porting Thread

  • 246 Replies
  • 101649 Views
Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #110 on: 03 / May / 2013, 19:40:32 »
Advertisements
Hi, brand new to the CHDK Boards but not to CHDK. Hopefully I can help out as much as possible here.

I have two IXUS125's that I plan to use for balloon and kite aerial photography and I'd like to get CHDK running smoothly on them.

Thank you nafraf and others for all of the work that has been done thus far. I've downloaded your latest patched version for my 101a and will give it a shot. I'll post anything that may be useful for future development. Let me know if there is anything else I can do on my end.

*

Offline nafraf

  • *****
  • 1308
Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #111 on: 03 / May / 2013, 19:59:13 »
Thank you nafraf and others for all of the work that has been done thus far. I've downloaded your latest patched version for my 101a and will give it a shot. I'll post anything that may be useful for future development. Let me know if there is anything else I can do on my end.
Hi, please test Dark frame subtraction on and off.

Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #112 on: 03 / May / 2013, 22:02:13 »
So I'm having an interesting problem. I downloaded the patched zip. Extracted it to SD card and when I start the camera (via the play button of course) I do not actually have the option of updating the firmware using the Canon menus. I formatted the card and installed the alpha version of CHDK instead and was able to flash it and make the card bootable. So I formatted the card again and tried the zip from your previous post and still no firmware update option.

Any suggestions? Is the Alpha version different from your upload?

Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #113 on: 03 / May / 2013, 22:09:31 »
So I'm having an interesting problem. I downloaded the patched zip. Extracted it to SD card and when I start the camera (via the play button of course) I do not actually have the option of updating the firmware using the Canon menus. I formatted the card and installed the alpha version of CHDK instead and was able to flash it and make the card bootable. So I formatted the card again and tried the zip from your previous post and still no firmware update option.

Any suggestions? Is the Alpha version different from your upload?
Typically,  CHDK versions posted on the forum don't have the ability to boot via the "firmware update method".  Its an extra step in the build requiring an encryption file that most devs just skip (as autobooting is so much easier to use in the first place).

If there is no ps.fi2 file in the root of the SD card then you will not be able to use the "firmware update method".
Ported :   A1200    SD940   G10    Powershot N    G16


Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #114 on: 07 / May / 2013, 23:53:16 »
Ok, so after my momentary lapse in common sense with respect to loading CHDK I have it loaded. I have one issue that may be problematic for testing.
1. Prior to taking RAW images and testing removal of dark frame removal on/off I tried creating the badpixel.bin file. I could not get it to work after trying 6 or 7 times. I also could not get badpixel.bin to work on the alpha version of CHDK so I'm not sure where to go with this issue. I'm also not sure whether this will influence dark frame removal on/off testing.
2. Despite issue #1, I tried dark frame removal on and off and both "worked" that is there was no crash when I took the pictures. But again I do not know whether issue #1 has influenced this test.

Please advise with respect to issue #1. What other information can I provide to help.

Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #115 on: 08 / May / 2013, 08:49:20 »
1. Prior to taking RAW images and testing removal of dark frame removal on/off I tried creating the badpixel.bin file. I could not get it to work after trying 6 or 7 times. I also could not get badpixel.bin to work on the alpha version of CHDK so I'm not sure where to go with this issue. I'm also not sure whether this will influence dark frame removal on/off testing.
Some people have reported better results getting badpixel.bin to work if they hold the camera very still while pointing at a dark area (i.e. in a darkened room). It might also help if you let the camera run for 5 minutes so that internal temperatures stablize prior to running the bad pixel create menu option.

Otherwise,  you can use DNG in 1.3 mode - which doesn't require the file (or do bad pixel correction for you).

Quote
2. Despite issue #1, I tried dark frame removal on and off and both "worked" that is there was no crash when I took the pictures. But again I do not know whether issue #1 has influenced this test.
Issue #1 would not matter - I assume you ran the test in DNG 1.3 mode or just used RAW without DNG enabled?   If the "test" worked,  and you used a long exposure time >2 seconds (like 15 seconds), then with Dark Frame Subtraction enabled you should have noticed a "Busy" message that persisted after the 15 second exposure completed for an additional length of time equal to the original exposure time (eg 15 seconds).   With Dard Frame Subtraction "off" that extra "Busy" delay should not have happened.
« Last Edit: 08 / May / 2013, 08:59:07 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #116 on: 08 / May / 2013, 10:15:50 »
Thanks for the clarifications waterwingz. See below:

1. Prior to taking RAW images and testing removal of dark frame removal on/off I tried creating the badpixel.bin file. I could not get it to work after trying 6 or 7 times. I also could not get badpixel.bin to work on the alpha version of CHDK so I'm not sure where to go with this issue. I'm also not sure whether this will influence dark frame removal on/off testing.
Some people have reported better results getting badpixel.bin to work if they hold the camera very still while pointing at a dark area (i.e. in a darkened room). It might also help if you let the camera run for 5 minutes so that internal temperatures stablize prior to running the bad pixel create menu option.

Otherwise,  you can use DNG in 1.3 mode - which doesn't require the file (or do bad pixel correction for you).

Ok, so I did have the camera stable in a dark-ish room, lit poorly at least and flash off. However DNG was in mode 1.3. However I did not know that I did not need to worry about the badpixel.bin with DNG in 1.3 mode. I've read a tremendous amount of material on the CHDK site but must have missed that nugget of information. Thanks.

Quote
2. Despite issue #1, I tried dark frame removal on and off and both "worked" that is there was no crash when I took the pictures. But again I do not know whether issue #1 has influenced this test.
Issue #1 would not matter - I assume you ran the test in DNG 1.3 mode or just used RAW without DNG enabled?   If the "test" worked,  and you used a long exposure time >2 seconds (like 15 seconds), then with Dark Frame Subtraction enabled you should have noticed a "Busy" message that persisted after the 15 second exposure completed for an additional length of time equal to the original exposure time (eg 15 seconds).   With Dard Frame Subtraction "off" that extra "Busy" delay should not have happened.


I did run the test in DNG mode. I believe that I did not run a long enough exposure time since it was only about 2 seconds however the "busy" message did persist for about 2 seconds after. I will rerun the tests with a much longer time to confirm that this feature is working.

Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #117 on: 08 / May / 2013, 10:39:25 »
I did run the test in DNG mode. I believe that I did not run a long enough exposure time since it was only about 2 seconds however the "busy" message did persist for about 2 seconds after. I will rerun the tests with a much longer time to confirm that this feature is working.
What you are trying to confirm is that CHDK can turn Dark Frame Subtraction OFF on your camera during long exposures.  The Canon firmware has it ON by default for those long exposures. 

So if you set the CHDK Dark Frame Subtraction menu item to AUTO or ON with a 15 second exposure,  you should see the complete shot take 30 seconds ( 15 for the shot and 15 for the dark frame ).  If you set it to OFF in the CHDK menu,  the same shot should only take 15 seconds to complete.

The test is to confirm that CHDK actually tricks the camera into not taking the extra dark frame with every long exposure.
Ported :   A1200    SD940   G10    Powershot N    G16


Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #118 on: 09 / May / 2013, 07:55:59 »
I have completed several tests of the Darkframe subtraction both on and off and it is functioning as it should as far as I can tell. Darkframe subtraction off with 5, 10 and 15 second exposures only took the length of the exposure while Darkframe subtraction on with the same time exposures took 10, 20 and 30 seconds to complete respectively. No crashes of CHDK during my testing.

My general experience thusfar with both the forum version of CHDK and the Alpha version of CHDK have been positive.

Anything else need testing?

Re: ELPH 110 HS (IXUS 125 HS) Porting Thread
« Reply #119 on: 11 / May / 2013, 04:02:34 »
Thank you very much for your great work!

 

Related Topics