CHDK for IXUS 135. - page 2 - CHDK Releases - CHDK Forum supplierdeeply

CHDK for IXUS 135.

  • 17 Replies
  • 7457 Views
*

Offline srsa_4c

  • ******
  • 4416
Re: CHDK for IXUS 135.
« Reply #10 on: 18 / September / 2014, 13:14:57 »
Advertisements
If it is true that the Ixus 132 build works fine on the Ixus 135 (and it seems to be) then it's very easy for me to make STICK and ACID work and download the right build when presented with a photo taken with an Ixus 135.

Anyone see a problem with this?
Yes. The included PS.FI2 will only work on the ixus132 :(
The CHDK build environment currently requires a separate port for every model.

Quote
PS In fact it seems that ACID and STICK should work without any modification since the ID in the EXIF that they use to identify the camera turns out to be the same in both cameras, so ACID and STICK will think an Ixus 135 is an Ixus 132 and will thus download the 'right' build.
This will result in the same mess as with the two N models...

*

Offline zeno

  • *****
  • 889
Re: CHDK for IXUS 135.
« Reply #11 on: 18 / September / 2014, 15:19:08 »
Are you sure? I had thought that the differences between the two were not related to firmware, but just to purely external 'hardware' features (the case, etc). If the diskboot.bin is the same for both, why not the ps.fi2?

By the way, based on sample images on the web, there appears to be a 100a firmware version for both cameras.
« Last Edit: 18 / September / 2014, 15:23:06 by zeno »
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit

*

Offline srsa_4c

  • ******
  • 4416
Re: CHDK for IXUS 135.
« Reply #12 on: 18 / September / 2014, 16:38:53 »
Are you sure? I had thought that the differences between the two were not related to firmware, but just to purely external 'hardware' features (the case, etc).
The 135 also has Wi-Fi.
Quote
If the diskboot.bin is the same for both, why not the ps.fi2?
The .fi2 file was meant to be used for firmware upgrades. The upgrade file includes the camera's P-ID, which is checked by the camera. If there's P-ID mismatch, the camera will refuse to do the upgrade. The P-ID is not part of the firmware, it's located in the configuration area of the flash ROM - that enables them to make a single firmware for models that only differ in optional hw.

*

Offline zeno

  • *****
  • 889
Re: CHDK for IXUS 135.
« Reply #13 on: 18 / September / 2014, 18:12:32 »
Does the P-ID appear in the EXIF of a photo? If it does, then ACID and STICK could use that info to distinguish between the two cameras.

I know that photos from the N and N Facebook cameras have identical EXIF, so it's not possible to distinguish them using photos.
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit


*

Offline srsa_4c

  • ******
  • 4416
Re: CHDK for IXUS 135.
« Reply #14 on: 18 / September / 2014, 18:24:21 »
Does the P-ID appear in the EXIF of a photo? If it does, then ACID and STICK could use that info to distinguish between the two cameras.

I know that photos from the N and N Facebook cameras have identical EXIF, so it's not possible to distinguish them using photos.
The N and N Facebook also have different P-ID, so I guess the answer is that it isn't recorded in the exif.
Does the "Camera Model Name" field of the exif not help distinguishing them (or the ixus132/135)?

*

Offline zeno

  • *****
  • 889
Re: CHDK for IXUS 135.
« Reply #15 on: 19 / September / 2014, 05:45:01 »
Does the "Camera Model Name" field of the exif not help distinguishing them (or the ixus132/135)?
It does, but:
1. that name field can vary from country to country - the Ixus 132 is also called the Elph115 - which is why ACID and STICK report it but don't use it to distinguish cameras, relying instead on a Model ID in the Canon MakerNote EXIF fields (not P-ID)
2. I'm unhappy adding lots of special case logic to ACID and STICK to deal with this sort of problem in a piecemeal fashion. Who knows how many more cameras this might apply to
A570, S100, Ixus 127
Author of ASSIST, STICK, WASP, ACID, SDMInst, LICKS, WICKS, MacBoot, UBDB, CFGEdit

*

Offline srsa_4c

  • ******
  • 4416
Re: CHDK for IXUS 135.
« Reply #16 on: 21 / September / 2014, 17:36:10 »
I have created a port for this model as a copy of the ixus132_elph115 port with modified PLATFORMID. Since the two cameras are identical (except for the Wi-Fi), any changes and corrections should be applied to both ports. Porting thread is http://chdk.setepontos.com/index.php?topic=10457.0

Re: CHDK for IXUS 135.
« Reply #17 on: 04 / May / 2017, 10:13:22 »
Does the "Camera Model Name" field of the exif not help distinguishing them (or the ixus132/135)?

I'm sorry for reviving this topic, but I just wanted to let you know that CHIMP does just that.

This obviously won't work for IXUS 133 (an obscure variant of 132).
« Last Edit: 31 / May / 2017, 18:47:21 by dmitrys »
Author of CHIMP, Canon Hack Installation and Management Platform


 

Related Topics