S100 porting thread - page 11 - DryOS Development - CHDK Forum

S100 porting thread

  • 286 Replies
  • 104202 Views
Re: S100 porting thread
« Reply #100 on: 18 / May / 2012, 00:20:27 »
Advertisements
waterwingz  thanks again  :D   that is exactly what I wanted!

Hey is there any way to map the  ring function button on the back?

Also I have been testing scripts and I have a question:

What would cause image fish-eye when using zoom script?

Re: S100 porting thread
« Reply #101 on: 18 / May / 2012, 00:28:54 »
waterwingz  thanks again  :D   that is exactly what I wanted!
Its a little difficult to swap between the CHD-Shell environment and an svn directory tree.  There is probably an easy way to make them work together but I finally gave up and created batch files that use the CHDK-Shell environment (gcc etc) to compile svn downloaded directories in a batch file / command window.

Quote
Hey is there any way to map the  ring function button on the back?
If you can figure out which bits change in the memory mapped I/O registers then adding new functions seems easy. 

Quote
Also I have been testing scripts and I have a question: What would cause image fish-eye when using zoom script?
RAW or jpg ?
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3378
    • Photos
Re: S100 porting thread
« Reply #102 on: 18 / May / 2012, 00:30:03 »
What would cause image fish-eye when using zoom script?

My guess:

At the wide end the lens has barrel distortion that is removed in software when the JPEG is produced. As you zoom in this distortion quickly disappears.

The lens_set_zoom_point function in wrappers.c is used by scripts to zoom the lens.
On some cameras (G10 & G12) extra code is needed to tell the camera where the lens has been zoomed to.
Without this the camera still thinks it's at the wide end and applies the distortion correction even when it is not needed.

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: S100 porting thread
« Reply #103 on: 18 / May / 2012, 00:55:31 »
waterwingz
I shot it a jpg.
you have any tips on where to start looking for a new button?

philmoz
Thanks!  that makes complete sense.
Later I will try shooting in raw without a script to see if it still produces a fish-eye.


Re: S100 porting thread
« Reply #104 on: 18 / May / 2012, 01:14:43 »
you have any tips on where to start looking for a new button?
so far most of the memory mapped i/o  for buttons etc has ended up in a three word array.  It's read in platform/s100/kbd.c at the start of the routine my_kbd_read_keys().   At one point I printed the whole array to the screen from the spytask() when I was looking for something.  If you look at the bottom of the spytask code in core/main.c you can still see where I inserted the hack - its commented out now with a #ifdef DEBUG_PRINT_TO_LCD ....
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3378
    • Photos
Re: S100 porting thread
« Reply #105 on: 18 / May / 2012, 03:17:37 »
you have any tips on where to start looking for a new button?
so far most of the memory mapped i/o  for buttons etc has ended up in a three word array.  It's read in platform/s100/kbd.c at the start of the routine my_kbd_read_keys().   At one point I printed the whole array to the screen from the spytask() when I was looking for something.  If you look at the bottom of the spytask code in core/main.c you can still see where I inserted the hack - its commented out now with a #ifdef DEBUG_PRINT_TO_LCD ....

Or enable the 'debug keymap' code in the gui_draw_debug_vals_osd() function in core/gui.c.

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: S100 porting thread
« Reply #106 on: 18 / May / 2012, 08:21:33 »
you have any tips on where to start looking for a new button?
so far most of the memory mapped i/o  for buttons etc has ended up in a three word array.  It's read in platform/s100/kbd.c at the start of the routine my_kbd_read_keys().   At one point I printed the whole array to the screen from the spytask() when I was looking for something.  If you look at the bottom of the spytask code in core/main.c you can still see where I inserted the hack - its commented out now with a #ifdef DEBUG_PRINT_TO_LCD ....

Or enable the 'debug keymap' code in the gui_draw_debug_vals_osd() function in core/gui.c.

Phil.
Having said all this, I realized that the jog dial on the G10 (and I assume other cameras) is not interfaced through the keymap.  You mentioned earlier that you were looking for the "ring dial" on the back of the camera - it might not be their either.
Ported :   A1200    SD940   G10    Powershot N    G16

Re: S100 porting thread
« Reply #107 on: 19 / May / 2012, 16:29:28 »
Has anyone used the Motion Detect script on the s100?

The MD script tries to focus after detecting motion unless you have MF set up on the ring.
Even when it does not adjust focus prior to shooting it still takes a very long time to shoot (even in high lighting, Manual, quick shutter speed, JPEG, dark frame subtraction shouldn't be an issue at quick shutter speeds).
Does anyone have any ideas? Is this a delay built into the script?

Moreover, instead of taking just 1 picture or a quick burst it continuously takes pictures untill manually stopped.

Thanks in advance.


Re: S100 porting thread
« Reply #108 on: 19 / May / 2012, 17:48:12 »
I use a lightning script that takes a pictures super quick, but for some reason you have to wait like 1 or 2 seconds when you first start it before it will work right.

Mine also continues taking pictures until manually stopped as well.......so is this a script problems or chdk problem?  ???


Edit:

The normal motion scripts seem to sometimes start shooting by itself when left alone a few second and no movement.  If I set shutter speed less and make the image darker it stops sometimes.
« Last Edit: 19 / May / 2012, 18:04:04 by colon247 »

*

Offline reyalp

  • ******
  • 13621
Re: S100 porting thread
« Reply #109 on: 19 / May / 2012, 18:04:08 »
The normal motion scripts seem to start shooting by itself when left alone a few second and no movement.
This probably means either your sensitivity is set too high, or there is something wrong with the buffer addresses or dimensions which causes it to read garbage

edit:
By sensitivity I mean md threshold (low = more sensitive to changes), but higher ISO will mean more noise, which will require a high threshold.
« Last Edit: 19 / May / 2012, 18:06:24 by reyalp »
Don't forget what the H stands for.

 

Related Topics