PowerShot SX230 HS - Porting Thread

  • 671 Replies
  • 112127 Views
  • Publish
    Re: PowerShot SX230 HS - Porting Thread
    « Reply #490 on: 12 / February / 2012, 15:17:54 »
    Advertisements
    I'll start running through the test scripts that are posted in the link. From the little playing I have done so far the only issue I have is raw mode gets turned off every time I turn the camera off. Probably a setting I have to change somewhere.

  • Publish
    Re: PowerShot SX230 HS - Porting Thread
    « Reply #491 on: 12 / February / 2012, 15:38:47 »
    Here are the results from testing
    llibtst.lua - no errors
    setmode.lua - 3 tests first 3 errors second 19 errors third test 23 errors. Not sure whats going on here.
    ubtest.lua - all buttons print correctly, no errors reported.

    How should I proceed with the setmode errors?

    *

    Offline reyalp

    • ******
    • 9954
  • Publish
    Re: PowerShot SX230 HS - Porting Thread
    « Reply #492 on: 12 / February / 2012, 15:54:53 »
    setmode.lua - 3 tests first 3 errors second 19 errors third test 23 errors. Not sure whats going on here.
    Can you post a log here as an attachment ?

    It seems like newer cameras may have problems with this test, also reported for a800 http://chdk.setepontos.com/index.php?topic=7409.msg81178#msg81178

    Maybe they need a little delay between switches, when I wrote that I was surprised you could just spam mode changes like that.
    Don't forget what the H stands for.

  • Publish
    Re: PowerShot SX230 HS - Porting Thread
    « Reply #493 on: 12 / February / 2012, 16:07:58 »
    I deleted the setmode.log file and reran the test, just to make sure I wasn't adding to the log. This time I got 6 errors. Maybe it is just that it runs so fast.

    http://www.box.com/s/2l9rxui14tvziqam76hb


    *

    Offline reyalp

    • ******
    • 9954
  • Publish
    Re: PowerShot SX230 HS - Porting Thread
    « Reply #494 on: 12 / February / 2012, 17:46:54 »
    Try the following version of setmode.lua

    It has a configurable delay between mode switches, default 200ms (try that first)
    Don't forget what the H stands for.

  • Publish
    Re: PowerShot SX230 HS - Porting Thread
    « Reply #495 on: 12 / February / 2012, 18:16:55 »
    That version worked perfectly, 200ms and no errors at all. looks like the 101b can be extended again to the 101e firmware. Now I just need to get a couple scripts to work correctly and I'll be happy.

    Thanks for the help everyone.

    *

    Offline reyalp

    • ******
    • 9954
  • Publish
    Re: PowerShot SX230 HS - Porting Thread
    « Reply #496 on: 12 / February / 2012, 18:36:55 »
    That version worked perfectly, 200ms and no errors at all. looks like the 101b can be extended again to the 101e firmware.
    Great. Can you check smaller values ? I'd start with 10, if that fails, maybe 50 or 100 ?

    This will help us correctly document the behavior of the mode switching functions.
    Don't forget what the H stands for.

  • Publish
    Re: PowerShot SX230 HS - Porting Thread
    « Reply #497 on: 12 / February / 2012, 18:49:13 »
    Sure, here are the numbers of errors reported along with the ms speed used;
    200 - 0 errors
    150 - 0 errors
    100 - 0 errors
    50 - 0 errors
    25 - 0 errors
    15 - 0 errors
    10 - 0 errors
    5 - 0 errors
    1 - 0 errors
    1 - 0 errors
    0 - 7 errors
    0 - 5 errors

    I ran the 1ms and the 0ms delayed tests twice each as listed above. All tests run using the setmode you posted above. Any other tests I can run for you?


    *

    Offline reyalp

    • ******
    • 9954
  • Publish
    Re: PowerShot SX230 HS - Porting Thread
    « Reply #498 on: 12 / February / 2012, 20:36:26 »
    Great, thanks. FWIW, the camera only sleeps in 10 ms increments (and script actually starts at 30, but that's a bug)

    I've checked in the updated version of setmode.lua und updated the wiki.
    Don't forget what the H stands for.

  • Publish
    Re: PowerShot SX230 HS - Porting Thread
    « Reply #499 on: 13 / February / 2012, 15:48:38 »
    I have tried everything I can, but I cannot get scripts that use overrides to work correctly. The 2 scripts I am trying to mainly use are "HDR Assist script" and the "Universal Intervalometer". The motion detect fast burst works perfectly (I believe). I get an average of 150-180ms, everytime with a few 210's (not sure if that is good, bad, or ugly, but that's how it is).

    In the hdr script it went from taking all pictures the same with no bracketing to taking all black pictures, starting this morning. Tried a fresh install of chdk and wiped the cameras setting to stock and still getting only black pictures.

    On the Intervalometer script, I am trying to use the override shutter length. it just takes it's pictures as normal one after the other, with no mods to the shutter length.

    I have read the user guide and have been able to change the over rides. Bracketing in continuous mode does do the over/under exposures correctly. And I can do extremely long exposures in manual mode as well, so all the over rides work, just not when used in scripts.

    I have also tried multiple hdr and Intervalometer scripts to make sure it wasn't just 1 script that isn't compatible. The only hdr script that works is the one that comes with chdk that has the over/under ev hardcoded.

    All attempts have been made in P or M mode, and as stated above the camera passes all tests so chdk can control the camera.

    Can anyone help me troubleshoot the issue so I can get the scripting to work?

     

    Related Topics