S100 porting thread

colon247

waterwingz thanks again 😁 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?

waterwingz

colon247
waterwingz thanks again 😁 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.

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.

Also I have been testing scripts and I have a question: What would cause image fish-eye when using zoom script?

RAW or jpg ?

philmoz

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

colon247

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.

waterwingz

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

philmoz

waterwingz

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

waterwingz

philmoz

waterwingz

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

mv3830

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.

colon247

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.

reyalp

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

colon247

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

waterwingz

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

colon247

My head is about to explode.....hahahaha :lol

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

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

Phil.

and

waterwingzso 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?

colon247

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?

reyalp

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

waterwingz

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

schnurrhahn

mv3830
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 !

hnikesch

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

hnikesch

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

colon247

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?

« Previous Page Next Page »