Motion Detection - time for a second look ? - page 9 - General Discussion and Assistance - CHDK Forum  

Motion Detection - time for a second look ?

  • 81 Replies
  • 16112 Views
*

Offline msl

  • *****
  • 1266
  • A720 IS, SX220 HS 1.01a
    • CHDK-DE links
Re: Motion Detection - time for a second look ?
« Reply #80 on: 18 / February / 2013, 04:53:30 »
Advertisements
Yes, the new buffer value helps.

But there is yet another little issue. The A720 uses _PostLEDMessage() for the LED control. This function can also control the LED brightness. The third argument of camera_set_led() must be greater than 0. The maximum value is 255.

The uBASIC and Lua commands use 200. I don't know why 200 and not 255.

I have corrected this in motion_detector.c & kbd.c. And now is all fine. The average time for the A720 is 25 ms.

msl
CHDK-DE:  CHDK-DE links

*

Offline philmoz

  • *****
  • 3146
    • Photos
Re: Motion Detection - time for a second look ?
« Reply #81 on: 18 / February / 2013, 06:05:28 »
Yes, the new buffer value helps.

But there is yet another little issue. The A720 uses _PostLEDMessage() for the LED control. This function can also control the LED brightness. The third argument of camera_set_led() must be greater than 0. The maximum value is 255.

The uBASIC and Lua commands use 200. I don't know why 200 and not 255.

I have corrected this in motion_detector.c & kbd.c. And now is all fine. The average time for the A720 is 25 ms.

msl

Thanks for that, updated in revision 2582.

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)

 

Related Topics