ixus140 elph130 porting thread - page 2 - DryOS Development - CHDK Forum

ixus140 elph130 porting thread

  • 29 Replies
  • 8139 Views
*

Offline srsa_4c

  • ******
  • 3904
Re: ixus140 elph130 porting thread
« Reply #10 on: 27 / October / 2013, 16:03:28 »
Advertisements
Not any more, the current CHDK code has checks to prevent loading on the wrong firmware
The checks are not yet in place. I'm still expecting feedback, I'd like to have "green light" before continuing. To be on-topic, I don't recommend trying the official release on differing firmware either.

*

Online reyalp

  • ******
  • 11896
Re: ixus140 elph130 porting thread
« Reply #11 on: 03 / November / 2013, 14:58:06 »
FWIW, the file counter on this port seems to still have issues. I had one raw in a timelapse series overwrite the previous one because the counter wasn't incremented.
« Last Edit: 30 / December / 2013, 21:52:43 by reyalp »
Don't forget what the H stands for.

Re: ixus140 elph130 porting thread
« Reply #12 on: 30 / December / 2013, 20:45:14 »
I also have firmware 100b I have added a dump to the wiki page, I installed the 100a version and the menus appear. Not sure what else I should be checking.

*

Online reyalp

  • ******
  • 11896
Re: ixus140 elph130 porting thread
« Reply #13 on: 30 / December / 2013, 21:48:40 »
I also have firmware 100b I have added a dump to the wiki page, I installed the 100a version and the menus appear. Not sure what else I should be checking.
Thanks!

If it runs at all, the 100a version is probably fine for 100b camera, but I'll take a look at the dump when I get a chance.

A couple of known issues with the port:
- The file counter issue mentioned in my previous post. Basically, this means if you save raw, there's a possibility a few will go missing or have the wrong number.
- The subject distance override functions will crash if you don't have AF lock enabled.
Don't forget what the H stands for.


*

Offline srsa_4c

  • ******
  • 3904
Re: ixus140 elph130 porting thread
« Reply #14 on: 31 / December / 2013, 08:53:44 »
- The file counter issue mentioned in my previous post. Basically, this means if you save raw, there's a possibility a few will go missing or have the wrong number.
How about storing the last saved raw's file number or filename and comparing it with the current one before saving the file? Or, stat() the current filename?

*

Online reyalp

  • ******
  • 11896
Re: ixus140 elph130 porting thread
« Reply #15 on: 31 / December / 2013, 14:07:16 »
How about storing the last saved raw's file number or filename and comparing it with the current one before saving the file? Or, stat() the current filename?
I was going to just re-enable PAUSE_FOR_FILE_COUNTER but what bugs me about that is that >90% of the time, it doesn't need to pause.

One thought was to record the last known image number later in the raw hook, and then only pause if the numbers are equal. It seems like that should always be safe for any cam that uses pause for file counter, though it would pause for the first shot.

edit:
Mostly it hadn't bugged me enough to do anything about it, but now that this camera has another user... :P
« Last Edit: 31 / December / 2013, 14:10:33 by reyalp »
Don't forget what the H stands for.

*

Online reyalp

  • ******
  • 11896
Re: ixus140 elph130 porting thread
« Reply #16 on: 31 / December / 2013, 19:07:25 »
I verified that 100b stubs are exactly the same as 100a, and updated the autobuild to make 100b builds as a copy.

I also added PAUSE_FOR_FILE_COUNTER and adjusted the SD override defines, so the two issues I mentioned earlier should be addressed.
Don't forget what the H stands for.

Re: ixus140 elph130 porting thread
« Reply #17 on: 03 / January / 2014, 09:34:03 »
hi every one, and 1000 thanks for helping us enjoying our toys camera.

I'm about to purchase a small/light Canon camera to be loaded with CHDK, and attached to a small QuadCopter.

my needs: RAW file, Timelipse pretty stable in AF SERVO mode.

I'm hesitating between the ELPH130 and the ELPH110 (light enough to get on board)

they both run a different version of CHDK, but since it's being develop as we write,

what model would you recommend me to purchase ?

cheers & happy new year


Re: ixus140 elph130 porting thread
« Reply #18 on: 03 / January / 2014, 09:56:06 »
I'm hesitating between the ELPH130 and the ELPH110 (light enough to get on board)
they both run a different version of CHDK, but since it's being develop as we write,
what model would you recommend me to purchase ?
There is only one version of CHDK so I'm not sure why you think there are more than one. 

Okay,  technically there are a couple of versions,  the stable and unstable branch  (currently v 1.2.0 & 1.3.0 respectively).   But both are available for either camera.

And I guess there are the old archived 1.1.0 and 1.0.0 versions.  Not recommended but again,  available for either camera.

However,  there is a separate load file for each camera as these are uniquely created on a per camera basis to accomdate the different firmware builds in the camera.  The CHDK feature and functions will be essentially the same (unless there is some hardware difference between cameras - like a touchscreen or different buttons).

So chose the model to purchase based on your needs, budget and desires.  CHDK feature & functions are the same for either model.
« Last Edit: 03 / January / 2014, 10:00:05 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

Re: ixus140 elph130 porting thread
« Reply #19 on: 03 / January / 2014, 10:44:26 »
yes, I was referring in bad terms, to the ALPHA & BeTA versions, one camera running under ALPHA et the other BETA both 1.2

 

Related Topics