SX260 HS Porting Thread - page 59 - DryOS Development - CHDK Forum

SX260 HS Porting Thread

  • 642 Replies
  • 151798 Views
Re: SX260 HS Porting Thread
« Reply #580 on: 24 / March / 2013, 20:04:29 »
Advertisements
I'm still thinking its the delay that's screwing up the rest of the capt_seq task timing. 

replace the get_usb_bit() loop with msleep(10);

Re: SX260 HS Porting Thread
« Reply #581 on: 24 / March / 2013, 20:11:12 »
As quick look at the wiki for the sx260 show that the LED address I quoted above is definitely wrong.

Here's version with that line commented out :

sx260hs-101a-1.2.0-mod4


Note - that bad address is used in the debug_led() function too ...


replace the get_usb_bit() loop with msleep(10);
Good idea - I'll try that next if fixing the LED does not do it.  I guess your theory is to yield while waiting for the remote to release ?
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SX260 HS Porting Thread
« Reply #582 on: 24 / March / 2013, 20:37:48 »
Good news and bad news. Still doesn't crash, but now it fires the focus light, waits a second or so, fires the preflash, then about 10 seconds later, takes a picture on its own.  Nothing happens when I remove the cord.

Re: SX260 HS Porting Thread
« Reply #583 on: 24 / March / 2013, 20:39:34 »
Oh yes, the same thing happens whether or not delay is enabled.


Re: SX260 HS Porting Thread
« Reply #584 on: 24 / March / 2013, 20:43:09 »

I guess your theory is to yield while waiting for the remote to release ?


In my own tests the quickest possible click of the remote (which you would not do) is at least 130 msec, so I guess you can yield for 100 msec.

Re: SX260 HS Porting Thread
« Reply #585 on: 24 / March / 2013, 20:46:24 »
Good news and bad news. Still doesn't crash, but now it fires the focus light, waits a second or so, fires the preflash, then about 10 seconds later, takes a picture on its own.  Nothing happens when I remove the cord.
EXCELLENT!   It was the stinking LED definition all along!!  The worst part is that I looked at it much earlier today and when I saw the same address used in the debug_led() routine I assume it must be correct.   DOH!!!!

The "10 seconds later" part is normal - the USB sync code will only wait 10 seconds for the USB voltage to go away.  Its kind of a safety thing to assure the camera doesn't hang for too long.  We've talked of removing or lenthening it but I have not got around to testing longer delays.

To prove this,  plug in the USB cable for a couple of seconds (to let the camera focus & preflash etc) and then pull the cable out.  It should take a picture right away.


Ported :   A1200    SD940   G10    Powershot N    G16

Re: SX260 HS Porting Thread
« Reply #586 on: 24 / March / 2013, 20:58:11 »
Attached, is the ROMLog and the camera does take a picture right away, when the cord is removed right away after the first sequence is finished.

Re: SX260 HS Porting Thread
« Reply #587 on: 24 / March / 2013, 21:00:04 »
Attached, is the ROMLog and the camera does take a picture right away, when the cord is removed right away after the first sequence is finished.
I think we are done.  I'll clean up the code for the 1.00b to match the 1.00c & 1.01a and submit for update to the autobuild.   Thanks for hanging in while I chased this.
Ported :   A1200    SD940   G10    Powershot N    G16


Re: SX260 HS Porting Thread
« Reply #588 on: 24 / March / 2013, 21:12:27 »
No problem, it might prove useful for me, down the line and I appreciate all the work everyone does, writing the code and debugging it.  I'm really glad to help.

Re: SX260 HS Porting Thread
« Reply #589 on: 26 / March / 2013, 09:54:21 »
Waterwingz,

I believe you were working from the code from ptpcam gui, but I could be mistaken, at any rate, I tried that program with my SX260 and the program would not recognize it, no matter what I did.  Just as I had given up, I decided to try it with my SD790 and it worked perfectly, every function, even to the point of turning the camera off.

Just thought you might like to know.

 

Related Topics