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

IXUS160/ELPH160 Porting attempt

  • 497 Replies
  • 185607 Views
*

Online reyalp

  • ******
  • 13621
Re: IXUS160/ELPH160 Porting attempt
« Reply #460 on: 18 / July / 2016, 13:04:54 »
Advertisements
2) I also found out you shouldn't use no-brand SD cards, because they will make your life a lot worse..by triggering random errors here and there..
What sort of errors? If it's like https://chdk.setepontos.com/index.php?topic=12795.0 it might not just be due to cheap cards.
Don't forget what the H stands for.

*

Offline c10ud

  • ***
  • 245
Re: IXUS160/ELPH160 Porting attempt
« Reply #461 on: 19 / July / 2016, 12:26:42 »
2) I also found out you shouldn't use no-brand SD cards, because they will make your life a lot worse..by triggering random errors here and there..
What sort of errors? If it's like https://chdk.setepontos.com/index.php?topic=12795.0 it might not just be due to cheap cards.
the major issues were found when I was trying shoot()-save-download and the SD card was injecting random lags and/or errors during shooting and downloading, changing the card to a better one solved the trick.. I think I may have sporadically even experienced random chdk errors when booting up...however upon discovery I cut the SD in a half  :haha hence unfortunately I cannot reliably reproduce this anymore..

Re: IXUS160/ELPH160 Porting attempt
« Reply #462 on: 27 / July / 2016, 17:11:50 »
I'm a bit confused, but then I'm a noob at this..  I want to use the ELPH160 for a book scanner using a Pi.  Is this commonly done, and are people using that camera with this software now without problems, or are thereproblems?  Are there just two reports that cams were bricked without any knowledge of why?  Can someone describe where we are with this, or I do I need to look for another cam to use?

*

Online reyalp

  • ******
  • 13621
Re: IXUS160/ELPH160 Porting attempt
« Reply #463 on: 27 / July / 2016, 21:08:15 »
I'm a bit confused, but then I'm a noob at this..  I want to use the ELPH160 for a book scanner using a Pi.  Is this commonly done, and are people using that camera with this software now without problems, or are thereproblems?
I'd suggest looking on http://www.diybookscanner.org/
The 'pi-scan' project linked from there mentions using ixus160/elph160 https://github.com/Tenrec-Builders/pi-scan
Quote
Are there just two reports that cams were bricked without any knowledge of why?  Can someone describe where we are with this
The bricking happened in early test builds. The exact cause is not known for certain, but there have been no additional reports.
Don't forget what the H stands for.


Re: IXUS160/ELPH160 Porting attempt
« Reply #464 on: 09 / August / 2016, 10:45:00 »
IXUS160 zoom crash

Hello, and thanks for developing this wonderful software.

I'm in the middle of testing IXUS160, using chdkptp as client. Most of the functions seem to work and be stable. But I have problems with camera crash (power off with lens still out) when zooming. It's very easy to reproduce, just fiddle the zoom back and forth:

___> c
connected: Canon IXUS 160, max packet size 512
con> rec
con 1> luar set_zoom(60)
con 2> luar set_zoom(0)
con 3> luar set_zoom(60)
con 4> luar set_zoom(0)
ERROR: I/O error
___>


Both chdk and chdkptp are the latest one can get (built yesterday). Computer platform seems to make no difference, ubuntu+gnome behaves same as gui-less centos.

I noticed different crash probablility with different zoom values. 60 seems to stand few times, whereas 35 causes almost immediate crash.

I also tried A2500 at the end of exactly same cable. With that, no problems at all, so the problem is more likely at the camera end.

Any comments on this? Anyone else experiencing zoom crash? I would like to provide more accurate information (logs, dumps, whatever) but for that I would need a bit of assistance, what is needed and how to get it.  (Maybe there a problem reporting guide somewhere, just did not hit my eye)

esa

*

Online reyalp

  • ******
  • 13621
Re: IXUS160/ELPH160 Porting attempt
« Reply #465 on: 09 / August / 2016, 13:14:01 »
I'm in the middle of testing IXUS160, using chdkptp as client. Most of the functions seem to work and be stable. But I have problems with camera crash (power off with lens still out) when zooming. It's very easy to reproduce, just fiddle the zoom back and forth:

I would like to provide more accurate information (logs, dumps, whatever) but for that I would need a bit of assistance, what is needed and how to get it.  (Maybe there a problem reporting guide somewhere, just did not hit my eye)
If you can post a romlog (http://chdk.wikia.com/wiki/Debugging#Camera_crash_logs_.28romlog.29) that might be helpful.

If you can build CHDK yourself, try increasing CAM_NEED_SET_ZOOM_DELAY in platform/ixus160_elph160/platform_camera.h

IIRC, 300 is largest value we use in other ports.
Don't forget what the H stands for.

Re: IXUS160/ELPH160 Porting attempt
« Reply #466 on: 09 / August / 2016, 14:38:24 »
ok, thanks

below is romlog from this short session:

con 5> rec
con 6> luar set_zoom(35)
ERROR: I/O error


ASSERT!! FocusLensController.c Line 1064
Occured Time  2016:08:09 19:28:08
Task ID: 14614561
Task name: PhySw
SP: 0x0059DB0C
StackDump:
0x00000000
0x00000000
0xFF98C9AC
0x00000428
0x00001CE8
0x00000001
0x00001CE8
0x00000001
0x19980218
0x19980218
0x19980218
0x19980218
0xFF98D50C
0x00000BB4
0x0000EF74
0x00001CE8
0xFFB7E858
0x00000000
0x00000BB4
0x0000EF74
0x00040100
0x00286AD0
0xFFB7E8B0
0x00000BB4
0x001A6D48
0x00040100
0x00199A5C
0x00000BB4
0x00000BB4
0x00000200
0x0018FF5B
0x00000023
0x00000B91
0x00040100
0x0018FF99
0x0018FF71
0x00286AD0
0x00286DE0
0x00612CED
0x00612CE1
0x006173D3
0x00288620
0x00000010
0x00000000
0x00288628
0x006107E0
0x00000000
0x00286DE0
0x00040100
0x00286AD0
0x0061C143
0x00000000
0x00286AD0
0x00286DE0
0x00288870
0x002885C8
0x0028886C
0x00288578
0x00000001
0x00000000
0x00000000
0x006107E0
0x00000005
0x006170CD
0x00286AD0
0x00000000
0x00627534
0x001A6868
0x0061743D
0x00286AD0
0x00616EBB
0x00286AD0
0x006173ED
0x00286DE0
0x00000000
0x00286AD0
0x00000000
0x00286AD0
0x00000000
0x00627534
0x001A6868
0x19980218
0x19980218
0x19980218
0x19980218
0x0018BB21
0x0059DC28
0x00616EAF
0x00629650
0x00000000
0x0060E000
0x00629650
0x00000020
0x00286AD0
0x00189D69
0x001A5C64
0x00189E53
0x0062728C
0x00000000
0x00627534
0x00000000
0x0003FCB4
0x006174E9
0x00000000
0x0062728C
0x00000000
0x006139F9
0x006139CD
0x001A6868
0x00000001
0xA32F1C9E
0x001A6868
0x0019628D
0xA32F1C9E
0x00195CF5
0x00610838
0x0059DD04
0x00629650
0x00000000
0x00000020
0x0060FDD0
0x0060FDD0
0x00286AD0
0x0059DD30
0x0061608B
0x00000002
0xFFFFFFFF
0x00610446
ShootConDump:
0f 0f 0f 0f 0f 0f 0f 0f 0f 0f
CameraConDump:
07 0a 02 0d 09 01 0f 0f 0f 0f
00239840: UI:DispSwCon_MuteOffPhysicalScreen
00239840: UI:LogicalEvent:0x00003110:adr:0,Para:0
00239840: UI:DispSwCon_TurnOnDisplayDevice
00239840: UI:UI_StrobeCon_Start
00239840: UI:LogicalEvent:0x00003136:adr:0,Para:0
00239840: UI:_ManagePTMProperty
00239850: UI:LogicalEvent:0x0000301c:adr:0,Para:0
00239850: SS:ModChg
00239850: SS:   Evf=1
00239850: SS:   0069->8005
00239850: SS:   Asp 0000->0000
00239860: SS:ModChg*
00239860: UI:_DecideCaptureMode
00239860: UI:_StartStill
00239860: UI:_ContiCount->0(5632)
00239860: UI:DSIC:42,6
00239860: UI:DSIC:1b,0
00239890: UI:VTMUnLock
00239900: UI:TerminateDeliverToZoomController
00239900: UI:OPTICAL_ZOOM_POS
00239900: UI:DispSwCon_TurnOnDisplayDevice
00239900: UI:LogicalEvent:0x0000313e:adr:0,Para:0
00239900: UI:_EnrySRec
00239900: UI:DCIC:1,0
00239900: UI:CaptModeChanger_CheckRTCRrepared
00239900: UI:DispSwCon_MuteOffPhysicalScreen
00239900: UI:_ChangeDisplayOut
00239900: UI:Window MuteOff
00239900: UI:MuteOffPhysicalScreen
00239900: UI:UnpressZoomLever
00239900: UI:DSIC:e9,0
00239900: UI:_DecideModeDial
00239900: UI:No Change Capture Mode
00239900: UI:DSIC:d4,0
00239900: UI:VTMLock
00239900: UI:VTMReduuce
00239910: UI:LogiEvnt_NotPowerType:0x000009a4:adr:0,Para:0
00239910: UI:LogiEvnt_NotPowerType:0x000009a2:adr:0,Para:0
00239920: UI:DSIC:6a,0
00239920: UI:VTM SW
00239920: UI:VTMUnLock
00240000: UI:VTMLock
00240010: UI:VTMUnLock
00241250: SS:ChargeComplete
00241370: UI:VTMLock
00241380: UI:DSIC:a9,1
00241380: UI:DSIC:55,0
00241380: UI:VTMUnLock
00243390: UI:VTMLock
00243390: UI:VTMUnLock
00245870: UI:VTMLock
00245880: UI:VTMUnLock
00249950: UI:DSIC:13,0
00249950: UI:DispSwCon_MuteOnPhysicalScreen
00249950: UI:Window MuteOn
00249950: UI:MuteOnPhysicalScreen
00249950: UI:DispSwCon_TurnOffBackLight
00249950: UI:TurnOffBackLight
00249950: UI:DCIC:10,0
00249950: UI:VTMLock
00249950: UI:VTMUnLock
00249950: UI:LogicalEvent:0x00003136:adr:0,Para:0
00249950: UI:VTMLock
00249950: UI:VTMReduuce
00249950: UI:VTMLock
00249960: UI:VTMUnLock
00249960: UI:DSIC:16,0
00249960: UI:VTMLock
00249960: UI:VTMReduuce
00249960: UI:VTMLock
00249970: UI:VTMReduuce
00249970: UI:VTMLock
00249970: UI:VTMReduuce
00249970: SS:StopFdr 1
00250420: UI:DispSwCon_TurnOffDisplayDevice
00250420: UI:DispSwCon_TurnOffBackLight
00250420: UI:TurnOffDisplay
00250470: UI:DispSwCon_TurnOffDisplayDevice
00250470: UI:DispSwCon_TurnOffBackLight
00250470: UI:VTM SW
00250470: UI:VTMUnLock
00261290: UI:DSIC:21a,0
00261300: SS:OptAt=35 3
00261350: UI:VTMLock
00261350: UI:VTMUnLock
00261440: UI:VTMLock
00261440: UI:VTMUnLock




*

Online reyalp

  • ******
  • 13621
Re: IXUS160/ELPH160 Porting attempt
« Reply #467 on: 09 / August / 2016, 17:09:37 »
ok, thanks

below is romlog from this short session:

con 5> rec
con 6> luar set_zoom(35)
ERROR: I/O error


ASSERT!! FocusLensController.c Line 1064
Occured Time  2016:08:09 19:28:08
Task ID: 14614561
Task name: PhySw
SP: 0x0059DB0C
This looks a lot like the problem that increasing CAM_NEED_SET_ZOOM_DELAY would address. Did you try that? I thought from your earlier post that you were set up to build CHDK, but if not I can post a test build.

Don't forget what the H stands for.


Re: IXUS160/ELPH160 Porting attempt
« Reply #468 on: 09 / August / 2016, 17:21:28 »

This looks a lot like the problem that increasing CAM_NEED_SET_ZOOM_DELAY would address. Did you try that? I thought from your earlier post that you were set up to build CHDK, but if not I can post a test build.
[/quote]

I built chdkptp and downloaded autobuilt chdk. It might take considerable time to learn to build chdk so I would appreciate if you could post a test build.

*

Online reyalp

  • ******
  • 13621
Re: IXUS160/ELPH160 Porting attempt
« Reply #469 on: 09 / August / 2016, 21:01:20 »
No problem. Here's a test build with zoom delay 300
Don't forget what the H stands for.

 

Related Topics