IXUS160/ELPH160 Porting attempt - page 21 - DryOS Development - CHDK Forum
supplierdeeply

IXUS160/ELPH160 Porting attempt

  • 497 Replies
  • 173789 Views
Re: IXUS160/ELPH160 Porting attempt
« Reply #200 on: 28 / September / 2015, 14:37:42 »
Advertisements
Hi Piere, glad you got things working. I can't explain why STICK didn't find the zip file (I assume the photo you dropped was for the right camera).
zeno : is there an issue with STICK not liking folder paths with spaces in them?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline mphx

  • ***
  • 210
Re: IXUS160/ELPH160 Porting attempt
« Reply #201 on: 01 / October / 2015, 17:16:38 »
Hey all ,

Someone sent me an ixus160 , to check if chdk works good enough so he can set up a multi camera thing with these cameras.

I managed to find a chdk file from this thread (tried hard since all links are deleted because some cameras had issues etc etc) and "worked" the camera with chdkptp.

So my questions are :

1. Do i have the latest "version" of the firmware for this camera?Can i have a link or something to test it out?
2. Are there any bugs i should know of ?Can i try to reproduce anything to help the progress here?
3. Where i tell my findings with chdkptp ?Here or to reyalp on some other thread?
4. How good is the progress overall ?What can i tell to the guy that sent me the camera? Is it a viable option or not ?

Thanks.

*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS160/ELPH160 Porting attempt
« Reply #202 on: 01 / October / 2015, 17:59:27 »
I managed to find a chdk file from this thread (tried hard since all links are deleted because some cameras had issues etc etc) and "worked" the camera with chdkptp.
Links were deleted because a user experienced hw failure on 2 cameras while trying a test build.

To a mod: we can't control that external site, but the link to it should perhaps be removed as it hosts a potentially dangerous early release: http://chdk.setepontos.com/index.php?topic=12321.msg122945#msg122945

Quote
1. Do i have the latest "version" of the firmware for this camera?
No, what you found is an old release, as described above. Don't use it.
Quote
2. Are there any bugs i should know of ?Can i try to reproduce anything to help the progress here?
The specific condition (running out of card space while saving DNG) that seemed to have induced camera failure is no longer allowed to happen in recent CHDK. We don't know whether this is enough to prevent camera failure. No-one else reported failure since then (but there may not be many users as we stopped providing public links to builds).
Quote
3. Where i tell my findings with chdkptp ?Here or to reyalp on some other thread?
Camera specific failures (things that work on your cams but not on the ixus160) should be reported here.
Quote
4. How good is the progress overall ?What can i tell to the guy that sent me the camera? Is it a viable option or not ?
I don't have this camera, but I have the impression that the port is usable. Bugs are still possible due to lack of widespread testing.
This camera is probably the only option if you need to buy a larger number of identical cameras.

Note that it might be possible that recently manufactured ixus160's have a firmware other than 100a.

*

Offline mphx

  • ***
  • 210
Re: IXUS160/ELPH160 Porting attempt
« Reply #203 on: 01 / October / 2015, 19:24:25 »
@srsa_4c

thanks for the link. installed it and everything works fine.
Some things i had issues with the previous version, now seems to work.

Btw i use a multi cam rig on my own, and i use chdkptp to manage the whole thing.So the things i "test" on ixus160 is chdkptp commands , since it is supposed that this camera will be used for the same job.

So every command (connect , disconnect , shutdown , sync , preshoot , shoot , rec mode , preview mode , download images , delete images , set focus , set zoom , etc etc) seems to work flawlessly.

The whole test was with one camera , but i dont see any reason that it wont work with more than one.

If there is some big bug or anything that needs testing or reproducing just let me know.





*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS160/ELPH160 Porting attempt
« Reply #204 on: 01 / October / 2015, 19:38:43 »
If there is some big bug or anything that needs testing or reproducing just let me know.
There is one potential issue you may want to check before someone starts buying dozens of cameras. It was reported to happen on the ixus145: http://chdk.setepontos.com/index.php?topic=12097.0

Use a battery dummy and an external power supply to power the camera and check whether you can shoot (by hand and over PTP). Perhaps try different SD cards too.

*

Offline mphx

  • ***
  • 210
Re: IXUS160/ELPH160 Porting attempt
« Reply #205 on: 01 / October / 2015, 20:19:59 »
Gonna test it when i will be at studio (the next days) where the rig is.
I see that ixus160 uses the same battery with A2500 i am using , so the dummies/external power must suit to ixus160 too.

I will post results when i will test it.

Re: IXUS160/ELPH160 Porting attempt
« Reply #206 on: 03 / October / 2015, 00:54:52 »
I tried to brick my camera to verify that the capture-DNG-with-no-space-bricking bug was fixed. Alas, the experiment was inconclusive. My camera is still healthy.

There are no obvious malfunctions when trying to reproduce on a build which post-dates the fix.
But there are also no obvious malfunctions when reproducing on a build which I think pre-dates the fix.

So I'm not sure what else can be done for now to show that there is no longer a risk of camera bricking. If any of you have ideas, let me know. I'm still willing to use my camera as a sacrificial lamb if necessary.

-D

Re: IXUS160/ELPH160 Porting attempt
« Reply #207 on: 03 / October / 2015, 01:15:15 »
But there are also no obvious malfunctions when reproducing on a build which I think pre-dates the fix.
Yes - disproving this conclusively  will be tough.

Did you actually run your SD card down to "empty" prior to trying the test ?

Edit : I've always been very amazed / thankful that I never bricked any of the cameras I ported from scratch.  Although no doubt I came close many times.
« Last Edit: 03 / October / 2015, 01:17:09 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


Re: IXUS160/ELPH160 Porting attempt
« Reply #208 on: 05 / October / 2015, 12:14:04 »
For my test, I created a bootable SD card with CHDK on it. I filled up most of the card with other files, leaving about 300 MB free. Then I put the card into the camera, enabled DNG/RAW photographs, and started taking pictures. When there wasn't enough space left for the DNG file, the camera reverted to taking JPEGs only. And when there wasn't enough space for even a JPEG, the camera started beeping at me plaintively whenever I pressed the shutter button.

I'm happy to change my procedure in some way and try again if it will increase the odds of tracking this bug down.

In the mean time, I think I will move forward in the assumption that (a) it is likely fixed and (b) the things I am doing with the camera will be unlikely to trigger this bug in any case. But my peace of mind would be greatly enhanced if I was sure it was fixed.

-D

*

Offline srsa_4c

  • ******
  • 4426
Re: IXUS160/ELPH160 Porting attempt
« Reply #209 on: 05 / October / 2015, 19:52:43 »
For my test, I created a bootable SD card with CHDK on it. I filled up most of the card with other files, leaving about 300 MB free. Then I put the card into the camera, enabled DNG/RAW photographs, and started taking pictures. When there wasn't enough space left for the DNG file, the camera reverted to taking JPEGs only. And when there wasn't enough space for even a JPEG, the camera started beeping at me plaintively whenever I pressed the shutter button.
Current CHDK source no longer attempts to save RAW/DNG when free space is low. This was not the case at the time the incidents happened. Aside from this change, no other source change attempted to address the "bug" in question.
Quote
my peace of mind would be greatly enhanced if I was sure it was fixed.
I could say the same. However, this isn't likely to happen (unless someone from the Canon engineering team gives us hints where to look  :P).

Similar incidents also happened with other models: http://chdk.wikia.com/wiki/Camera_failures_suspected_to_be_caused_by_CHDK .

Here are Scannerall's posts, that's all we know.
And here are some guesses from me.

Should we vote on enabling autobuild for this port?

 

Related Topics