A800 Porting Thread - page 17 - DryOS Development - CHDK Forum
« previous next »
Pages: 1 ... 12 13 14 15 16 [17] 18 19 20 21 22 ... 28   Go Down

A800 Porting Thread

  • 277 Replies
  • 124952 Views
*

Offline Qanthelas

  • **
  • 71
Re: A800 Porting Thread
« Reply #160 on: 24 / March / 2012, 19:00:16 »
Advertisements
Quote from: waterwingz on 24 / March / 2012, 15:24:25
Built this one with a up-to-date copy from the svn (but with native Lua supported) on my Win7 box (but not with CHDK-Shell).

http://www.box.com/s/6d1c38eb8d74b33330db
Using this build here are my test results

Free Memory: 425416 bytes
CHDK size: 222736 bytes
loaded at: 0x1F5FFE0

setmode.lua stil shows 15 FAILED check log
With "mode chagne delay, ms" set to 250 it works just fine and cycles through a bunch of modes
Lowered delay to 150 and it still works just fine
Further lowered to 75 and it still works
Down to 40 ms, 3 failed but the rest worked
Upped to 50 ms, still works

setrec.lua seems to work just fine (leaving me in view image mode)

tstcallf.lua  gives "2 FAILED"

uartrtst.lua seems to work (just shows "***STARTED***" and "***FINISHED***"
« Last Edit: 24 / March / 2012, 19:02:06 by Qanthelas »
Logged
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: A800 Porting Thread
« Reply #161 on: 24 / March / 2012, 19:06:51 »
Quote from: Qanthelas on 24 / March / 2012, 19:00:16
Using this build here are my test results

Free Memory: 425416 bytes
CHDK size: 222736 bytes
loaded at: 0x1F5FFE0

setmode.lua stil shows 15 FAILED check log
With "mode chagne delay, ms" set to 250 it works just fine and cycles through a bunch of modes
Lowered delay to 150 and it still works just fine
Further lowered to 75 and it still works
Down to 40 ms, 3 failed but the rest worked
Upped to 50 ms, still works

setrec.lua seems to work just fine (leaving me in view image mode)

tstcallf.lua  gives "2 FAILED"

uartrtst.lua seems to work (just shows "***STARTED***" and "***FINISHED***"
So this is different than the same code built on my Linux partition.  Interesting.

I'll check which compiler versions I've been using and report back.
« Last Edit: 24 / March / 2012, 19:31:01 by waterwingz »
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline reyalp

  • ******
  • 14140
Re: A800 Porting Thread
« Reply #162 on: 24 / March / 2012, 19:09:00 »
I very much doubt the behavior of setmode changes between CHDK builds. The length of the delay needed might vary between runs due to other factors.
Logged
Don't forget what the H stands for.
*

Offline nifelim

  • *
  • 10
Re: A800 Porting Thread
« Reply #163 on: 26 / March / 2012, 14:16:38 »
nevertheless hope to test the port 1.00b.called today at canon.firmware 1.00c is, but to send an e-mail declined.
Logged
*

Offline Doug Cooper

  • *
  • 1
Re: A800 Porting Thread
« Reply #164 on: 30 / March / 2012, 08:07:46 »
Possibly dumb question -- is the A800 port likely to work on the A810?   I mainly need the "raw"
save feature -- trying to see if the A810 will work for book scanning.  Or are these cameras apples & oranges?

  Thanks, Doug
Logged
*

Offline waterwingz

  • ******
  • 12140
    • Waterwingz
Re: A800 Porting Thread
« Reply #165 on: 30 / March / 2012, 08:24:35 »
Quote from: Doug Cooper on 30 / March / 2012, 08:07:46
Possibly dumb question -- is the A800 port likely to work on the A810? 
Sorry - no.  You'll have to wait for somebody who owns one to port it.
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline jim0watters

  • *
  • 9
Re: A800 Porting Thread
« Reply #166 on: 03 / April / 2012, 08:14:41 »
I am doing a long time-lapse with the A800.

I have a Canon power supply. I made my own batteries connector but I soldered the joins and my connections look good.

Every once and a while, (about 5 times in the last week), I have discovered the camera is no longer working. The lens is still extended, so it did not do a standard shut down. But like the power was cut.

I am taking a picture once every 15 min and using focus lock to eliminate focusing each time. So not much power should be used.

Sometime it will go 2 hours some time 2 days.

Has anyone else had this problem with this camera or others?

Anything I can do to fix it?

Thanks Jim
Logged
*

Offline srsa_4c

  • ******
  • 4451
Re: A800 Porting Thread
« Reply #167 on: 03 / April / 2012, 08:23:47 »
Quote from: jim0watters on 03 / April / 2012, 08:14:41
Every once and a while, (about 5 times in the last week), I have discovered the camera is no longer working. The lens is still extended, so it did not do a standard shut down. But like the power was cut.
The camera may have crashed. If you are "lucky", the crash reason has been logged.
Try to make a romlog: Miscellaneous Stuff -> Debug Parameters -> Save ROM crash log
You'll get a text file, with a timestamp in one of the first lines. Check that timestamp, whether the crash happened while shooting with the script. You can attach that log here.
Logged
*

Offline foxsat

  • *
  • 1
Re: A800 Porting Thread
« Reply #168 on: 03 / April / 2012, 11:31:38 »
Hi all here.
I want to to scan some books.At google search i have found the use of manual shoot of a digital camera that a CANON can do.
I would like to ask if the A800 can asept the CHDK firm so i can use the camera as a scanner.
Thanks for your time and for any help.
Logged
*

Offline jim0watters

  • *
  • 9
Re: A800 Porting Thread
« Reply #169 on: 03 / April / 2012, 12:57:08 »
Quote from: srsa_4c on 03 / April / 2012, 08:23:47
Quote from: jim0watters on 03 / April / 2012, 08:14:41
Every once and a while, (about 5 times in the last week), I have discovered the camera is no longer working. The lens is still extended, so it did not do a standard shut down. But like the power was cut.
The camera may have crashed. If you are "lucky", the crash reason has been logged.
Try to make a romlog: Miscellaneous Stuff -> Debug Parameters -> Save ROM crash log
You'll get a text file, with a timestamp in one of the first lines. Check that timestamp, whether the crash happened while shooting with the script. You can attach that log here.
I got two log files and both show "ASSERT!! MotionVector.c Line 133" a search indicates that MotionVector is from the original firmware and the times stamps don't match the times when the camera actually stopped.

Jim
Logged
Pages: 1 ... 12 13 14 15 16 [17] 18 19 20 21 22 ... 28   Go Up
« previous next »
 

Related Topics


SimplePortal © 2008-2014, SimplePortal