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

S100 porting thread

  • 286 Replies
  • 104201 Views
Re: S100 porting thread
« Reply #110 on: 19 / May / 2012, 20:07:26 »
Advertisements
I am using the normal motion script.  I dont think it is the sensitivity.
sometimes I also get this on the screen when trying to end the loop:

":23: attempt to compare number with nil"

here is a video and a picture of the error if it helps:

http://youtu.be/tCIBezuJ828


« Last Edit: 19 / May / 2012, 20:15:21 by colon247 »

Re: S100 porting thread
« Reply #111 on: 19 / May / 2012, 22:04:28 »
I am using the normal motion script.
If by "normal" you mean the one that's packed into the CHDK distribution then you need to know that script is  a simple "throw away" included just to demonstrate how to call the MD function.    The parameters it uses were quite frankly pulled out of air and will need to be tuned for each camera and shooting situation.  Some of the more sophisticated shooting scripts (expecially those specifically for lightening) might be a better starting point.

 
Ported :   A1200    SD940   G10    Powershot N    G16

Re: S100 porting thread
« Reply #112 on: 19 / May / 2012, 23:14:51 »
My head is about to explode.....hahahaha :lol

I have been at this for a couple hours now.....and I am talking about:

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

Phil.

and

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 ....

I go uncomment these... build... and then have no idea what I am supposed to do after that....or if I am even doing it right  :(

am I missing something?
Can you guys explain a little more?
« Last Edit: 19 / May / 2012, 23:25:59 by colon247 »

Re: S100 porting thread
« Reply #113 on: 20 / May / 2012, 13:24:32 »
On the first script issue I had with the script causing fisheye.  I tried shooting in raw (canon raw) and got no fish-eye distortion.

Could the camera be correcting this even in Raw?
« Last Edit: 20 / May / 2012, 13:36:28 by colon247 »


*

Offline reyalp

  • ******
  • 13621
Re: S100 porting thread
« Reply #114 on: 20 / May / 2012, 17:51:34 »
On the first script issue I had with the script causing fisheye.  I tried shooting in raw (canon raw) and got no fish-eye distortion.

Could the camera be correcting this even in Raw?
If you mean canon native raw, I'd guess the canon software knows how to correct it.
Don't forget what the H stands for.

Re: S100 porting thread
« Reply #115 on: 20 / May / 2012, 21:27:26 »
I go uncomment these... build... and then have no idea what I am supposed to do after that....or if I am even doing it right  :(
am I missing something?
Can you guys explain a little more?
In both cases, what you get is the ability to "dump" information from the cameras memory to the screen.  You use that to look for values that change when the ring dial is activated.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline schnurrhahn

  • *
  • 6
  • Canon S100, Firmware 101A
Re: S100 porting thread
« Reply #116 on: 29 / May / 2012, 17:11:03 »
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.


Please disable the "SafetY-MF".
Then the Motion Detection will work fine in MF-Mode !
Canon S100, Firmware 101A

Re: S100 porting thread
« Reply #117 on: 02 / June / 2012, 13:28:15 »
Hi guys, I have been using CHDK on my SD900 & SD990, just got the S100 and loaded it today.  I will be testing the port based on my other cameras usage.  So far the loading and card setup is much easier,  Thanks for all your efforts.

Hans
It is better to burn a roll of film than curse the darkness Equip, S100 w/CHDK, SD900 w/CHDK, SD990 w/CHDK & Pentax K2000, Pentax Kr
Flickr:


Re: S100 porting thread
« Reply #118 on: 02 / June / 2012, 17:34:45 »
I did have some time to play today and checked out most over rides SS, Aperture, ISO, Focus, Quality (SF), and additional display info, DOF Calc, Time, Battery, and Remote control.  and many menu functions, DNG, and Raw save incl.  the resulting images in PS Elements.  All works like my SD990.  I did notice the battery voltages were not the same as my SD900 or SD990 that use the same battery???  both my SD's use 3975 - 3425  the S100 has 4050 - 3200

I didn't read the entire thread so I assume all the functionality has already been checked.

I am running firmware 1.01a

Hans

update after running several battery cycles is seems the 4025 and 3425 works for me on my S100 and the SD's using the same type battery
« Last Edit: 03 / June / 2012, 16:59:45 by hnikesch »
It is better to burn a roll of film than curse the darkness Equip, S100 w/CHDK, SD900 w/CHDK, SD990 w/CHDK & Pentax K2000, Pentax Kr
Flickr:

Re: S100 porting thread
« Reply #119 on: 03 / June / 2012, 19:42:29 »
Hnikesch

I noticed that after a while that the battery percent voltages were not the same among all my batteries.   Perhaps it is not such a perfect system.  I have gotten used to it though. I tested my number using the factory battery.  Maybe it is just different on every camera.  The ebay battery never worked well the battery percent I have now.

Hnikesch are you a programmer?

 

Related Topics