Energy Consumption - Camera Benchmark according to CIPA DC-002 - Script Writing - CHDK Forum supplierdeeply

Energy Consumption - Camera Benchmark according to CIPA DC-002

  • 3 Replies
  • 2838 Views
*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Energy Consumption - Camera Benchmark according to CIPA DC-002
« on: 17 / January / 2009, 04:19:52 »
Advertisements
i want to write (or you write it and i just give the ideas, as i am not a good script writer :D) a script or a set of scripts or anything that benchmarks the cameras in several aspects (all having to do with ENERGY, nothing else like speed or anything)


a) normal camera benchmark according to CIPA (as close as possible to THIS - should be feasible to a certain amount)
 
b) benchmark of CHDK commands (motion detect, raw average, such things)

c) benchmark of camera functions possible through CHDK (LCD backlight off for example)

d) benchmark of normal camera functions (like http://chdk.wikia.com/wiki/Camera_Power_Consumption )

e) benchmark of batteries, for this we need a vbatt command in lua/ubasic, if not already existing

having a set of standardized scripts that make use of functions present in all cameras / CHDK versions, we could then compare a lot of things (for example i can find out if my eneloops perform on my s3is much better than on the a570).

feasability:
a) should pose no problem (except the "shut off camera after 10 pictures rule") - to really be "in sync" with CIPA, we would need an external timer using USB to wake the cam after a given time which then automatically proceeds, this test is of use for batteries only of course
b) this might only be tested using a lab power unit, as it can note the subtle differences. with batteries it is possible as well, but only makes sense if you benchmark the cam according to CIPA first, so you can compare runtime
c) like b, better to check with a lab power unit, but can also be tested using batteries (think of long time lapse photography)
d) like b & c
e) no problem creating such commands. in each script you could have a param you could set like "battery set", which you use to indicate the set of batteries used in a benchmark session (like eneleloop = set 1, primary batts = set 2, and so on)

do we need for any of this more functionality in lua/ubasic? for example for CIPA you need to note the resolution, which in standard chdk would only be a number (0 being biggest resolution). using propcase 194 (on digic II) we can at least return the width of an image (and thus, through the fixed ratio, also the height, unless widescreen mode is engaged...) to the logging function, so we can easily share the benchmark logs and even automate the parsing of benchmark logs from different people and different cameras so they can be put in a graph nicely.

there is no actual work done yet, i havent given it much priority. started the topic to gather opinions, suggestions, criticism.

as a convenience, i attached the CIPA PDF here, because for example germany is blocked from accessing the japanese site...

edit: a little bit more information: http://www.i3a.org/wp-content/uploads/2008/03/digitalcamerabatterystandards.pdf
« Last Edit: 17 / January / 2009, 04:29:46 by PhyrePhoX »

*

Offline fe50

  • ******
  • 3108
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: Energy Consumption - Camera Benchmark according to CIPA DC-002
« Reply #1 on: 17 / January / 2009, 07:01:22 »
A package with the specs & other interesting CIPA documents can also be found in the chdkdev drop, see
  http://drop.io/chdkdev/asset/cipa-specs-guidelines-whitepapers-7z
(The CIPA sites sometimes are not good reachable...).

*

Offline fudgey

  • *****
  • 1705
  • a570is
Re: Energy Consumption - Camera Benchmark according to CIPA DC-002
« Reply #2 on: 18 / January / 2009, 04:06:02 »
a) Most cameras don't wake up from USB.

d) Ordinary lab psu or multimeter output current meters are unable to provide correct readings for power consumption when camera input current is changing rapidly (such as when motors are operated). You need a something capable of true RMS DC current measurement (and note that those true RMS multimeters may not be able to true RMS at DC, many of them are ment for 50/60 Hz mains frequencies AND that they present a significant series resistance which may ruin the measurement), or only measure static power consumption during idle or half shoot, as done in previous threads concerning input current.

Actually the camera input current (at least mine) has a significant ripple making readings from some instruments twitchy unless averaged.




*

Offline PhyrePhoX

  • *****
  • 2254
  • make RAW not WAR
    • PhyreWorX
Re: Energy Consumption - Camera Benchmark according to CIPA DC-002
« Reply #3 on: 21 / January / 2009, 06:21:30 »
interesting: in s2is and s3is firmware there is a function:

Quote
SetRestartTimeForCIPA

well, i guess this makes sense. the s3is being a camera that has a "deep sleep" feature built-in - namely the canon built-in intervalometer feature. when i activate it, and set the interval to like 30 minutes, the cam goes to sleep, maybe even deeper. maybe the "deep" sleep can be found for all cameras, at least the ones that support USB-WAKEUP.


also the following string can be found (in a lot more firmwares):
Quote
http://www.cipa.jp/dps/schema/


 

Related Topics