IXUS 240/ELPH 320 HS Porting thread - page 27 - DryOS Development - CHDK Forum

IXUS 240/ELPH 320 HS Porting thread

  • 286 Replies
  • 68783 Views
*

Offline reyalp

  • ******
  • 12649
Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #260 on: 05 / June / 2015, 21:03:56 »
Advertisements
While the Ixus 125 is very well tested and has a minor PtP problem regarding
the Vertical PtP Resolution.
Are there details of this problem posted somewhere?

Quote
Also the Ixus 265 and Sx600 are capable of Wi-Fi Remote Shoot and Wi-Fi Live View
on IOS and Android smart Devices, they are also are Discounted.

And the Ixus 275 and Sx610 are capable of Wi-Fi Remote Shoot and Wi-Fi Live View
on IOS and Android smart Devices, they are the current canon models
Just so it's clear, none of these cameras are currently supported by CHDK.
Don't forget what the H stands for.

Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #261 on: 06 / June / 2015, 00:32:51 »
While the Ixus 125 is very well tested and has a minor PtP problem regarding
the Vertical PtP Resolution.
Are there details of this problem posted somewhere?
Reply #157 on: 31/October/2013
http://chdk.setepontos.com/index.php?topic=8085.msg106723#msg106723

When I recently tested a Ixus 125 I noticed that the PtP resolution is about half
what is in the cameras viewfinder i.e. the top half only is displayed.

I also recently tested a Ixus 240-101a using test build #3 and there was several
problems, I will re test and post the results in more detail.

Is the Ixus 240-1xxx Source Code for the test build #3 available somewhere ?

Also is it possible that the  Ixus 240 capt_seq.c file has some or multiple
errors, as capt_seq.c seems to be the most difficult part of any CHDK port.

H-H
« Last Edit: 06 / June / 2015, 00:55:26 by Hardware_Hacker »

Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #262 on: 06 / June / 2015, 07:14:45 »
Hi HH and reyalp.

Thank you for detailed description.

Probably, Ixus 265/275 will not be good solution for me, because I need camera for archive papers scanning, some old books, i.e. some case of book scanning. That means, RAW format is critical for me because JPEG has some compression artifacts around text. Also, looks like API for these camera is closed, and I can't use it with my own software.

And Ixus 125 costs almost twice than Ixus 240 :( Probably, I will need to buy even 4 cameras for two scanners in this summer, i.e. cost will be important thing. I see fast answers in this thread and good support. Sometimes, it's more important than stable work.

I can use very limited functionality for first time, even without much ptp control. I just need:
1) ability to save RAW files(CR2 or DNG - not important) additionally to jpeg on the memory card
2) live preview with any quality via PTP - aspect ratio issues is not important at all
3) send 'shoot' command by PTP, i.e. ability to shoot and save jpeg and cr2 to memory card
4) ability to call get_image_dir() and get_exp_count() Lua script commands via PTP
5) download jpeg and cr2 files by PTP to computer and remove they from memory card

Could anybody please to check it on Ixus 240 ?

Re: IXUS 240/ELPH 320 HS Porting thread (slightly off topic response)
« Reply #263 on: 06 / June / 2015, 08:32:13 »
Probably, Ixus 265/275 will not be good solution for me, because I need camera for archive papers scanning, some old books, i.e. some case of book scanning. That means, RAW format is critical for me because JPEG has some compression artifacts around text. Also, looks like API for these camera is closed, and I can't use it with my own software.

And Ixus 125 costs almost twice than Ixus 240 :( Probably, I will need to buy even 4 cameras for two scanners in this summer, i.e. cost will be important thing. I see fast answers in this thread and good support. Sometimes, it's more important than stable work.
FWIW, about two month ago, markvandenborre selected the ixus160 (elph160) as potentially a very good camera for book scanners (not too expensive and currently available in stores).   After a few discussions on the CHDK IRC channel,  adong joined the porting effort and started the ixus160_elph160 porting thread.

They have made really good progress in porting this camera,  but its a new DIGIC4+ camera and they are currently stuck on getting RAW images to save properly.  However,  one of the most experience CHDK developers & assembly language experts - srsa_4c - is now assisting them so there is a good chance it will get sorted out shortly.  (fingers crossed).   

You might want to take a look at the porting thread and maybe contact Mark/adong via PM or on IRC?

edit :   I should have also mentioned that adong bravely started the port "blind" until  amavroidis generously sent him an actual ixus160 to work with.  amavroidis is working on a multicamera 3D scanning rig AFAIK.
« Last Edit: 06 / June / 2015, 08:49:49 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #264 on: 07 / June / 2015, 05:27:59 »
Its looking like the problem is possible "multiple errors" in the
Ixus 240-101a and Ixus-102a ports and I am not at the halfway point yet.

H-H

*

Offline reyalp

  • ******
  • 12649
Re: IXUS 240/ELPH 320 HS Porting thread
« Reply #265 on: 07 / June / 2015, 13:45:38 »
Its looking like the problem is possible "multiple errors" in the
Ixus 240-101a and Ixus-102a ports and I am not at the halfway point yet.
101a and 102a are both in the autobuild. If you can describe the problems, it is possible someone may be able to help fix them.
Don't forget what the H stands for.

*

Offline JvdP

  • ***
  • 174
Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #266 on: 22 / July / 2015, 09:08:05 »
I'm experiencing manual focus (set_mf and set_aflock) problems with my v1.3.0-3274 CHDK IXUS 240HS (102A).

Let me start with saying that locally (on cam) I can do a manual focus override, by going into the CHDK > Enhanced Photo Operations > Override Subj. Dist. [on][   176]. Taking a photo confirms focus override. Also RemoteShoot via CHDKPTP confirms that focus is set and stays at 176.

"Man Focus" button (turns green) in the quick menu, also works as expected.


However, when I do the following over CHDKPTP:
Code: [Select]
con 1> luar set_aflock(1)
con 2> luar set_focus(1)
con 3> luar set_focus(65490)
con 4> rs
WARNING: capture_get_data error I/O error
WARNING: error waiting for shot script nil
ERROR: /home/pi/chdkptp/lua/cli.lua:2274: attempt to concatenate local 'err' (a table value)
stack traceback:
        [C]: in function 'xpcall'
        /home/pi/chdkptp/lua/cli.lua:244: in function 'execute'
        /home/pi/chdkptp/lua/cli.lua:351: in function </home/pi/chdkptp/lua/cli.lua:342>
        (...tail calls...)
        /home/pi/chdkptp/lua/main.lua:281: in main chunk
        [C]: in function 'require'
        [string "require('main')"]:1: in main chunk

Camera crashes. Here's the romlog:

Code: [Select]
ASSERT!! FocusLensController.c Line 829
Occured Time  2015:07:22 14:26:32
Task ID: 18153512
Task name: CaptSeqTask
SP: 0x0055FB74
StackDump:
0x00000000
0xFF1DE614
0x0000033D
0x00000DAC
0x00000001
0x00000DAC
0x00000001
0x19980218
0x19980218
0x19980218
0x19980218
0xFF1DEF2C
0x000000EA
0x000149E8
0x00000DAC
0xFF48559C
0x00000000
0x000000EA
0x000149E8
0x00000000
0x00003540
0xFF4855F4
0x000000EA
0x002A6A84
0x00000000
0x00283070
0x000000EA
0x000000EA
0x0028E7D9
0x002A6A84
0x002A6A84
0x0028F595
0x0009DDA4
0x0009DC94
0x00298818
0x00000000
0x00000045
0x20434453
0x00000020
0x0009DDA4
0x0009DC94
0x00000000
0x00003540
0x19980218
0x19980218
0x19980218
0x19980218
0x00000045
0x00285618
0x0009DCA8
0x0053FF38
0x19980218
0x19980218
0x19980218
0x19980218
0x19980218
0x0068738C
0x19980218
0x19980218
0x00000208
ShootConDump:
10 00 01 02 0f 0f 0f 0f 0f 0f
CameraConDump:
09 01 02 0d 09 01 10 0a 02 0d
00098700: UI:LogicalEvent:0x313d:adr:0,Para:0
00098700: UI:_EnrySRec
00098700: UI:CaptModeChanger_CheckRTCRrepared
00098700: UI:DispSw: Unlock
00098700: UI:DispSwCon_MuteOffPhysicalScreen
00098700: UI:Window Reduce MuteOff
00098700: UI:DSIC:f1,0
00098700: UI:DisplayPhysicalScreenCBR
00098700: UI:Re ScreenUnLock
00098700: UI:ScreenUnLock
00098710: UI:Window Re MuteOff
00098710: UI:MuteOffPhysicalScreen
00098720: UI:_DecideModeDial
00098720: UI:No Change Capture Mode
00098720: UI:DSIC:d4,0
00098760: UI:LogiEvnt_NotPowerType:0x09a4:adr:0,Para:0
00098760: UI:LogiEvnt_NotPowerType:0x09a2:adr:0,Para:0
00098760: UI:DisplayPhysicalScreenCBR
00098760: UI:DisplayPhysicalScreenCBR
00098860: UI:ScreenLock
00098860: UI:ScreenUnLock
00098900: UI:DisplayPhysicalScreenCBR
00100150: UI:ScreenLock
00100160: UI:DSIC:a9,1
00100170: UI:DSIC:58,0
00100170: UI:ScreenUnLock
00100180: UI:DisplayPhysicalScreenCBR
00102190: UI:DSIC:d8,0
00107440: SS:AFL
00107460: UI:ScreenLock
00107460: UI:ScreenUnLock
00107490: UI:DisplayPhysicalScreenCBR
00108010: SS:AFL*
00108030: UI:ScreenLock
00108030: UI:ScreenUnLock
00108060: UI:DisplayPhysicalScreenCBR
00114790: UI:ScreenLock
00114790: UI:ScreenUnLock
00114820: UI:DisplayPhysicalScreenCBR
00116940: UI:ScreenLock
00116940: UI:ScreenUnLock
00116970: UI:DisplayPhysicalScreenCBR
00124840: UI:ScreenLock
00124840: UI:ScreenUnLock
00124880: UI:DisplayPhysicalScreenCBR
00137680: SS:AFL
00137700: UI:ScreenLock
00137700: UI:ScreenUnLock
00137740: UI:DisplayPhysicalScreenCBR
00138200: SS:AFL*
00138260: UI:ScreenLock
00138260: UI:ScreenUnLock
00138290: UI:DisplayPhysicalScreenCBR
00151590: UI:ScreenLock
00151590: UI:ScreenUnLock
00151620: UI:DisplayPhysicalScreenCBR
00151700: UI:ScreenLock
00151700: UI:ScreenUnLock
00151740: UI:DisplayPhysicalScreenCBR
00156050: UI:ScreenLock
00156050: UI:ScreenUnLock
00156070: UI:DisplayPhysicalScreenCBR
00156170: UI:Button:0x000009A1:PressSwOne
00156170: UI:DSIC:25,0
00156170: SS:PreBuf
00156170: SS:BitR
00156170: UI:ShootState:0x1
00156170: UI:ShtCon_Activate
00156170: UI:DispSw: Lock
00156180: UI:ShtCon_PrepareCapture
00156180: UI:DSIC:61,0
00156180: UI:ScreenLock
00156180: UI:ScreenUnLock
00156180: UI:ScreenLock
00156180: UI:Reduce ScreenUnLock
00156180: UI:LogicalEvent:0x3135:adr:0,Para:0
00156190: SS:LoadTest:10
00156190: SS:PreCapt
00156200: UI:ShootState:0x2
00156200: UI:ClearEventComp
00156200: UI:DisplayPhysicalScreenCBR
00156200: UI:Re ScreenUnLock
00156200: UI:ScreenUnLock
00156210: UI:ShootSeqToUI:0x203b:adr:0x40,Para:64
00156210: UI:DisplayPhysicalScreenCBR
00156210: UI:DSIC:69,0
« Last Edit: 24 / July / 2015, 04:19:41 by JvdP »

Re: Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #267 on: 22 / July / 2015, 10:03:20 »
I'm experiencing manual focus (set_mf and set_aflock) problems with my v1.3.0-3274 CHDK 220HS.
According to the test results reported here : Google Docs MF Test Results your camera should allow CHDK controlled MF with and without using AFL or MF modes.

(ref : Setting focus from scripts or menus)

Quote
Let me start with saying that locally (on cam) I can do a manual focus override, by going into the CHDK > Enhanced Photo Operations > Override Subj. Dist. [on][   176]. Taking a photo confirms focus override. Also RemoteShoot via CHDKPTP confirms that focus is set and stays at 176.
Doing MF from the CHDK menus does not invoke AFL or MF modes.  It just does an MF set.   Your issue seems to happen when using AFL or MF ?
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline srsa_4c

  • ******
  • 4242
Re: Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #268 on: 22 / July / 2015, 11:21:14 »
v1.3.0-3274 CHDK 220HS.
That build is from December 2013...
I'd suggest upgrading to a current 1.3 or 1.4 release.
However, upgrading will still not solve the remote shooting issue, as the ixus220 port doesn't yet have filewritetask support.
A quick look tells me that the a3200 likely has the same fwt code, so fwt support can be added easily to this port.
Are you willing to test that? If yes, please tell us your camera's firmware version.

As for subject distance override, please re-do your testing with a recent CHDK release.

*

Offline reyalp

  • ******
  • 12649
Re: Re: ELPH300HS aka IXUS220HS - Porting Thread
« Reply #269 on: 22 / July / 2015, 16:05:10 »
Note that the screenshot looks like a touch screen camera (IXUS 240, presumably). IXUS 220 is not touch screen, AFAIK.

If it's confirmed as 240, I will move the posts.
Don't forget what the H stands for.

 

Related Topics