Motion Detection too slow?

[anonymous]

RAM dumping:

CHDK debug menu: enable RAM dump

Then press (display) to get ram dump in 100CANON.

It is the 32 MB file, that includes the frame buffers (LCD/EVF).

Make a dump with a dark frame (LCD/EVF), just put cap on lens,
and a dump with a normal frame.
There is no need to take a picture.

[fudgey]

I tried fiddling with the RAM dumps according to mx3's directions. This is from an a570is 1.00e:

wine find_diffs crw_0004.jpg crw_0005.jpg 10 6400

The last 3 lines of find_diffs output are the ones with the highest "bytes" values:

(0x00656100 + 0x1900 = 0x00657A00) bytes: 3CA50
(0x006D4A00 + 0x1900 = 0x006D6300) bytes: 3CA50
(0x00753300 + 0x1900 = 0x00754C00) bytes: 3CA50

So, if I'm not mistaken, the addresses are 0x00657A00 0x006D6300 0x00754C00 or 0x00656100 0x006D4A00 0x00753300 without the 0x1900 offset.

zzz.bat puzzles me a bit, since find_u32s.exe says
usage: find_diffs <input file 1 name> <offset> <hex1> <hex2> <hex3>
but zzz.bat has 3 extra argument addresses for the 610.refs output, with 0x10000000 offset to the other 3 args.

So after half a dozen failed attempts to form a proper command line, I ran

wine find_u32s crw_0004.jpg 0x00657A00 0x006D6300 0x00754C00 0x10657A00 0x106D6300 0x10754C00

and finally got some output 

[0x0065C6CC] : 10657A00
[0x0065C6D0] : 106D6300
[0x0065C6D4] : 10754C00
[0x0065C73C] : 10657A00
[0x0065DC00] : 10754C00
[0x0065DC04] : 10754C00
[0x0065DC88] : 10657A00
[0x006A9A30] : 10754C00
[0x0070C57C] : 10657A00
[0x0071DFD4] : 10657A00
[0x0095A108] : 10657A00
[0x0096A1E0] : 106D6300
[0x0096A1E4] : 106D6300

Will this be of any use?

[mx3]

Jucifer, I'm probably wrong, but I think they are trying to find ways to improve the response time with the md_detect's own built-in command for "immediate shoot".

we are talking about using all three available buffers instead of one used by CHDK
we are trying to reduce 100msecs to 30 msecs

this dont have anything to do with immediate shot option

[mx3]

wine find_u32s crw_0004.jpg 0x00657A00 0x006D6300 0x00754C00 0x10657A00 0x106D6300 0x10754C00

and finally got some output 

[0x0065C6CC] : 10657A00
[0x0065C6D0] : 106D6300
[0x0065C6D4] : 10754C00
[0x0065C73C] : 10657A00
[0x0065DC00] : 10754C00
[0x0065DC04] : 10754C00
[0x0065DC88] : 10657A00
[0x006A9A30] : 10754C00
[0x0070C57C] : 10657A00
[0x0071DFD4] : 10657A00
[0x0095A108] : 10657A00
[0x0096A1E0] : 106D6300
[0x0096A1E4] : 106D6300

Will this be of any use?

yes. it is usefull. but I would recommend you to add  1900 after file name
i'm drunk right now. i think i can use 0x0065C6CC - 0x00657A00 +0x1900 as a base address

[fudgey]

yes. it is usefull. but I would recommend you to add  1900 after file name
i'm drunk right now. i think i can use 0x0065C6CC - 0x00657A00 +0x1900 as a base address

Ok,

Code: [Select]

wine find_u32s crw_0004.jpg 1900 0x00657A00 0x006D6300 0x00754C00 0x10657A00 0x106D6300 0x10754C00

[0x000065CC] : 10657A00
[0x000065D0] : 106D6300
[0x000065D4] : 10754C00
[0x0000663C] : 10657A00
[0x00007B00] : 10754C00
[0x00007B04] : 10754C00
[0x00007B88] : 10657A00
[0x00053930] : 10754C00
[0x000B647C] : 10657A00
[0x000C7ED4] : 10657A00
[0x00304008] : 10657A00
[0x003140E0] : 106D6300
[0x003140E4] : 106D6300



[Barney Fife]

Deleted

[jonnythe]

Hey guys, the motion detection works with lightning in the day. We just had a huge thunderstorm. Unfortunately batteries were going flat but I just had to check if it would work just by hand-holding the camera. Missed every great flash due to getting sore arms and the lightning moving all round. But this fairly average strike succeeded.

[Barney Fife]

Deleted

[yeyoungpup]

Great shot jonnythe.

And thanks anonymous for the dump guide. Now I can activate it in the menu on my G7 but the display, and or +/- buttons don't seem to do the dump. I'll keep working on it.

 

[jonnythe]

Well I don't really agree that is a great shot. Yeah I just put the A610 on manual, f8 and for some reason dialed in a 1/100 shutter speed trying to get a proper exposure. So I think this was a bit of a fluke. Most of the "leader" flashes were just too dim in the daylight to set it off and I couldn't lower the threshold since I was hand holding the camera. But that shot was definitely triggered by the motion detection. As usual though every time I pointed the camera to a different part of the sky, there'd be a good strike where I was looking previously. Always the way isn't it.

I tell you though, just as I put my arms down for a rest the last time, there was a beautiful bright forked strike right where I had the camera pointed, not much more than 1km away going by the thunder delay. And with an easily discernible delay between the pre-flash, just like with the successful capture. If I had have got that, I think we all would have peed our pants.

[GrAnd]

Just FYI...
I've just made an experiment. I measured time delay of 'shoot' command which is used for internal shooting in md command. It is about 650ms for all preparations (from calling to virtual pressing of "shoot_full"). Then I applied my suggestions regarding -10ms, etc. And this time is reduced to 230ms.

[Barney Fife]

Deleted

[jonnythe]

Does this mean then, that no matter how the internal shoot command might be "tweaked" that it might never get faster than using the script "click shoot_full" method? (I find that hard to believe, but it's possible I suppose.) Given that, then could the external script shoot method be sped-up by removing all code from CHDK for the internal method? (Just wondering out-loud here.)

This still doesn't make sense to me. Obviously internal code should be faster than a script?
What I attempted to do was work out exactly what happens when "shoot_full" is called from the script and hard code the process into the MD routine. Then compare the timing with the script method. I can get the source I downloaded to compile and it seems to run ok, but the internal shoot function will not run. I'm stuck.

[rjoe]

Hi all,

While searching for settings for the Motion Detection Scripts I found that there are good suggestions, but widely scattered.  In an attempt to streamline some of the excellent results people are getting I set up a single Wiki page at

http://chdk.wikia.com/wiki/Motion_detection_settings#Motion_Detection_Settings

It is my hope that this page will serve as a repository for finalized help on settings.

Best,

R. Joe

[GrAnd]

Does this mean then, that no matter how the internal shoot command might be "tweaked" that it might never get faster than using the script "click shoot_full" method?

Right now - yes. Because  the internal shoot command uses "shoot" command, not "click 'shoot_full'". The "shoot" command does a lot of others actions before it clicks 'shoot_full'.