Adding new cameras, applying patches into trunk (with source code prepared) - page 54 - General Discussion and Assistance - CHDK Forum
supplierdeeply

Adding new cameras, applying patches into trunk (with source code prepared)

  • 1611 Replies
  • 423451 Views
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #530 on: 21 / November / 2011, 22:37:41 »
Advertisements
Patch for all versions of IXUS120_SD940 to fix fl_tbl[] in main.c.   Entered actual values from exif data and corrected table length (now has 10 rather than 11 elements). 

Also changed stub for  SetScriptMode in all versions to reflect value recommended by new sig finder.

(Note: does not correct recent issue reported in forum thread http://chdk.setepontos.com/index.php?topic=7071 )
« Last Edit: 21 / November / 2011, 22:40:37 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 11918
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #531 on: 22 / November / 2011, 00:38:57 »
Patch for all versions of IXUS120_SD940 to fix fl_tbl[] in main.c.   Entered actual values from exif data and corrected table length (now has 10 rather than 11 elements). 

Also changed stub for  SetScriptMode in all versions to reflect value recommended by new sig finder.
Added, changeset 1421 (broken link, assembla trac seems to be messed up...)

You might want to check the ZSETP_TABLE_SIZE / nTxtbl stuff in core/kbd.c for this camera, I'd guess it should be the same as ixus870
Don't forget what the H stands for.

*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #532 on: 22 / November / 2011, 05:31:15 »
@reyalp
Quote
broken link, assembla trac seems to be messed up...

According to www.downforeveryoneorjustme.com/, tools.assembla.com is down.
Seems to have happened after the release of rev. 1420

wim





 


Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #533 on: 22 / November / 2011, 08:42:55 »
Seems like almost all project on this site disappeared. Hopefully temporary... The only 'working' site on http://tools.assembla.com/ i have found is http://tools.assembla.com/dai/ so the server is not really down but has some problems with serving sites.

I was searching for some kind of informations about this on Google but have not found anything. http://assembla.com/ works...
« Last Edit: 22 / November / 2011, 08:44:43 by outslider »
if (2*b || !2*b) {
    cout<<question
}

Compile error: poor Yorick


*

Offline whim

  • ******
  • 2013
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #534 on: 22 / November / 2011, 09:15:35 »
Andy Singleton on Mon, Nov 21, 2011 @ 12:37 PM wrote on http://blog.assembla.com/
Quote
We are planning a release tomorrow 22 November, at 07:00 UTC.  We will make some changes to the database, so the server team has asked me to tell you that there may be up to 10 minutes downtime.  I will post notes about enhancements tomorrow.
Guess something went wrong ...

wim
« Last Edit: 22 / November / 2011, 09:48:03 by whim »

*

Offline msl

  • *****
  • 1262
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #535 on: 22 / November / 2011, 09:48:20 »
This link is now ok: http://trac.assembla.com/chdk/browser/trunk

This link is wrong: http://tools.assembla.com/chdk/browser/trunk

Last checkin by reyalp: http://trac.assembla.com/chdk/changeset/1421/trunk

I don't know if this is new, but CHDK-DE has been for some time this adress structure: http://trac.assembla.com/chdkde/browser/trunk
CHDK-DE:  CHDK-DE links

Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #536 on: 22 / November / 2011, 10:08:54 »
You might want to check the ZSETP_TABLE_SIZE / nTxtbl stuff in core/kbd.c for this camera, I'd guess it should be the same as ixus870
I actually did take a look at that but decided not to change it just yet.   

I now have several hours invested in reformatting and commenting the USB remote code.  Documentation of how the code is supposed to work does not appear to exist (there is some SDM specific stuff to provide clues but its different code).   I even bought a Ricoh CA-1 online to do some testing.  Guess what - it doesn't work reliably with my cameras - but if you pound long enough on the button you can eventually get the shutter to fire.  And as several sections of that code are actually unreachable, I'm not even sure how much of  it actually works.  So  I'm going to wait until I have it figured out before changing anything related to ZSTEP_TABLE_SIZE and nTxtbl[]. 

I'd be willing to bet that most of the cameras listed in the first #ifdef of core/kbd.c were simply put there to get it to compile and are wrong.  Apparently remote zoom via USB is not a much used feature in CHDK (SDM may be different).

I plan to start a new forum thread on this shortly to discuss what the current code does,  who is using what and what we want to do with it.   So far, the best feedback I've had is from reyalp -  "Nuke it from orbit".


Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline fe50

  • ******
  • 3099
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #537 on: 22 / November / 2011, 11:10:32 »
So far, the best feedback I've had is from reyalp -  "Nuke it from orbit".
  :P

Apparently remote zoom via USB is not a much used feature in CHDK (SDM may be different).
Remote zoom and features like this can (and IMO also should) be done completely from the script side, without any special code.
With the pulse length values from get_usb_power it's easy to handle different actions in a script, a typical application is a uC based "remote" unit like this one...
There could be some pre-defined pulse schemes coded directly in the CHDK sources, but i'd prefer to publish script samples, e.g. for the Ricoh remote...

We should also make sure that all builds in CHDK & CHDKDE behaves the same way...

FWIW - i'm using the USB remote feature with the SX20, SD860 & SD400 with simple power-only remote and with some PICAXE based circuits...


Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #538 on: 22 / November / 2011, 11:25:21 »
Remote zoom and features like this can (and IMO also should) be done completely from the script side, without any special code.
I tend to agree with the exception that having a simple "press to focus, release to shoot" mechanism that does not need a script seems to make sense for many users. Also, the CA1 and sync delay features would be hard to implement in a script - the timing is too tight.

Quote
We should also make sure that all builds in CHDK & CHDKDE behaves the same way...
Agreed.  But  I'll get a separate thread for this started shortly - let's not discuss it here.


Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3107
    • Photos
Re: Adding new cameras, applying patches into trunk (with source code prepared)
« Reply #539 on: 22 / November / 2011, 15:37:10 »
Another small patch. It improve useful tool "incrementor".
We could change incrementor step using zoom (and on some camera disp) to rapid change current menu item value.

What is done:
1. Refresh on-screen correctly
2. Resolved collision with ERASE_GUARD
3. Use incrementor for enums (useful for Tv override for example + unificate chdk behaviour)

Thanks for this - I hadn't noticed the conflict with the screen erase detect.

I've added this as changeset 1422 with a small change - I moved the incrementor display into the menu title bar at the right end and moved the menu name to the left instead of centered. Also changed the displayed value for 1000 to 1K and 10000 to 10K to shorten the display.

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)

 

Related Topics