SX40HS porting thread - page 17 - DryOS Development - CHDK Forum supplierdeeply

SX40HS porting thread

  • 258 Replies
  • 115776 Views
Re: SX40HS porting thread
« Reply #160 on: 08 / July / 2012, 10:53:01 »
Advertisements
Hi,

Please let me know if there is anything else you can think of, else, I am guessing this camera is bad?

Thanks!

Justin.

Re: SX40HS porting thread
« Reply #161 on: 08 / July / 2012, 12:57:03 »
Hi,

Although this says its triggered by CHDK:
http://chdk.wikia.com/wiki/Debugging

Hmmm..!

Justin.

Re: SX40HS porting thread
« Reply #162 on: 08 / July / 2012, 13:33:43 »
I will go take a picture of the settings and post shortly.

Re: SX40HS porting thread
« Reply #163 on: 08 / July / 2012, 13:55:07 »
Hello,

1. I've now set everything as you have recommended.
2. I have formatted the card (Eye Fi X2 8GB) and put on SX40HS 100i 1957-full on fresh install.
3. Trying my motion script first (earlier) and then if any issues will try the one you recommended again.
4. Here *were* the settings before changing them per your recommendations:

http://home.comcast.net/~jpiszcz/20120708/photo1.JPG
http://home.comcast.net/~jpiszcz/20120708/photo2.JPG
http://home.comcast.net/~jpiszcz/20120708/photo3.JPG
http://home.comcast.net/~jpiszcz/20120708/photo4.JPG
http://home.comcast.net/~jpiszcz/20120708/photo5.JPG

I have it running again, we'll see how long it stays up this time.

Please advise if I should try anything else in the meantime.

Justin.



*

Offline reyalp

  • ******
  • 14121
Re: SX40HS porting thread
« Reply #164 on: 08 / July / 2012, 15:31:30 »
Although this says its triggered by CHDK:
http://chdk.wikia.com/wiki/Debugging
The "hardware defect" error *can* be trigger by CHDK. One assumes it can also be trigger by actual hardware errors. The way to distinguish is to see whether the same setup triggers the error on multiple cameras. Of course, if the error is intermittent that may not be conclusive.

Also note, if triggered by CHDK, it doesn't necessarily mean that CHDK has damaged your hardware, more likely it just confused the camera to the point where it thought the hardware was misbehaving.
Don't forget what the H stands for.

Re: SX40HS porting thread
« Reply #165 on: 08 / July / 2012, 16:50:51 »
Hi,

Ok-- is anyone running chdk+motion detect script that is working (where the camera does not shut off)?

Justin.

Re: SX40HS porting thread
« Reply #166 on: 08 / July / 2012, 17:08:00 »
Running a test record (video) w/out CHDK for 30 min 640x480 on an 8GB SDHC card, checking stability..

Re: SX40HS porting thread
« Reply #167 on: 08 / July / 2012, 17:38:09 »
Just recorded 30 minutes of video w/OUT CHDK running and it was rock solid.
Even sending it via Eye Fi X2 8GB.

So how do we debug this problem?
With either motion script that runs, the camera turns off after N minutes/hours and it leaves the lens extended.

Thoughts?


*

Offline philmoz

  • *****
  • 3450
    • Photos
Re: SX40HS porting thread
« Reply #168 on: 09 / July / 2012, 05:40:03 »
Just recorded 30 minutes of video w/OUT CHDK running and it was rock solid.
Even sending it via Eye Fi X2 8GB.

So how do we debug this problem?
With either motion script that runs, the camera turns off after N minutes/hours and it leaves the lens extended.

Thoughts?


I will run some tests on my camera when I get some time.

The error log indicates the camera is crashing in one of the camera tasks not CHDK; possibly a timing problem with CHDK changing something when the camera does not expect it.

Phil.
CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)
  g7x2 (1.01a, 1.01b, 1.10b)

Re: SX40HS porting thread
« Reply #169 on: 11 / July / 2012, 12:12:38 »
Hi,

Ok-- thanks.
Whenever you need me to test something, just let me know.

Justin.

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal