CHDK firmware hack discussion (11)

Started Jun 9, 2007 | Discussions
donmorris Regular Member • Posts: 155
CHDK firmware hack discussion (11)

This is a sequel to the old threads discussing the CHDK firmware.
The CHDK fw is a hacked firmware for DIGIC II cameras. Currently
supported cams are A610, A620, A630, A640, A710 IS, S2 IS and S3 IS
(see the FAQ for a complete list).
The CHDK fw implements new features like RAW, battery indicator,
live histogram (RGB/luminance), zebra mode (blinking areas of
over- underexposure), DOF calculator, scripts (intervalometer,
exposure/focus
... bracketing etc.), text reader, file browser,
calendar, games and much more. New features get implemented
frequently, so check the timeline for the latest changes, or the
FAQ for a complete list.
The CHDK firmware does not touch the original firmware of your
camera. It is an additional program which gets loaded into the
memory of the cam. If you have a problem, just turn your cam off or
remove the batteries, and the CHDK fw is gone.

For further information, a guide, download links and FAQ see the
english WIKI:
http://scratchpad.wikia.com/wiki/CHDK

Timeline:
http://tools.assembla.com/chdk/timeline
Dear Vitalyb, GrAnd and all the others: Thank you so much for
creating this wonderful piece of software!
Some screenshots:

Main menu

Histogram (Blended) and Zebra overexposure indicator

Script menu

Link to the previous thread:
http://forums.dpreview.com/forums/readflat.asp?forum=1010&thread=23461906

harvester Contributing Member • Posts: 693
Re: CHDK firmware hack discussion (11)

imatom wrote:

PS-ReC SDK can control USB

http://www.usa.canon.com/consumer/controller?act=SDKHomePageAct&keycode=Sdk_Lic&fcategoryid=314&modelid=9808&id=3464

Quote:
"---

PS-ReC SDK 1.1.0b (Windows only) supports remote control including video out with the PowerShot G7, S3 IS, S80, A640 and A620 models exclusively.

CD-SDK 7.3 (Windows only) supports downloading with all USB PowerShots released before 6/30/2005. Remote control and video out are supported with some of these models. Please see the SDK Compatibility Charts for more information on this topic.
---"

As I said some threads before, some guy claimed that he got remote shooting capability on his A610 by using an old PC software (was it the G3 software? Can't remember), so I think it may be a limitation of the PC software, not the camera firmware.

Other people answered that there are 3rd party tools available which also don't give the A610, A630 etc. remote shooting, so that the limitation must be camera firmware related, not the PC software.

I think perhaps the 3rd party software relies on the Canon SDKs and therefore is not able to adress the A610 etc.

If that is true, maybe if you still have remote shooting software from one of your old Canon cams, you should give it a try with your A610, A630, A710.

On the other hand: maybe this guy lied, or maybe he had a very early firmware version where remote shooting was still activated (if it is a firmware limitation).

Marty Too Senior Member • Posts: 1,219
Clash/lightning script?

Is there any chance the scripts for lightning posted on the Wiki will work for A series cameras or just for the S3 and similar?

http://scratchpad.wikia.com/wiki/CHDK/uBASIC/Scripts_02

GrAnd Regular Member • Posts: 325
Re: Clash/lightning script?

Marty Too wrote:

Is there any chance the scripts for lightning posted on the Wiki
will work for A series cameras or just for the S3 and similar?
http://scratchpad.wikia.com/wiki/CHDK/uBASIC/Scripts_02

I do not see any reasons why that script will not work in A-series.

Lilien Regular Member • Posts: 140
"Dead/Stuck Pixel Remapping"?

First of all let me thank you very much for programming this hack!

I think one last shortcoming is the lack of "Dead/Stuck Pixel Remapping"
under user control (You have to go to the Canon service).
E.g. the Olympus 'Automatic Pixel Mapping' algorithm is much more
elegant and user friendly.

Is it known, how DIGIC II cameras handle the (bad) pixel mapping
and where the bad pixel information is stored?

Do you think it is possible to add a "Dead/Stuck Pixel Remapping"
function to the CHDK firmware hack, so that we can remap those
pixel out ourselves?

Thanks for reading and thinking about my idea!

Russel_Sprouts Regular Member • Posts: 300
stonewalled

I desperately want to circumvent the 1/500sec minimum shutter speed imposed when flash is enabled, but it seems this won't be possible.

The CHDK scripts emulate keypresses, but the cam refuses to accept Av or Tv etc adjustments when in the half-pressed state.

From reading the wiki, I understand this is a known limitation, and that a scripted sequence like this won't work:
lines of code...
press "half_shoot"
set_tv
...more code

but I'm still hoping someone will discover a workaround.
If you do, please post the solution here!

Russel_Sprouts Regular Member • Posts: 300
Re: "Dead/Stuck Pixel Remapping"?

Is it known, how DIGIC II cameras handle the (bad) pixel mapping
and where the bad pixel information is stored?

Which models have you seen/read that offer the user an ability to "map out bad pixels"? (I haven't seen any)

Is it even "known" that the cams "handle bad pixel mapping" in-camera?

If Canon support can, in fact, run a utility apply a patch... would it amount to a customized rewrite of the firmware, or writing some additional .DAT mapfile to the camera?

harvester Contributing Member • Posts: 693
Re: stonewalled

Russel_Sprouts wrote:

I desperately want to circumvent the 1/500sec minimum shutter speed
imposed when flash is enabled, but it seems this won't be possible.

Are you sure you want that? I think if you would be able to choose a shutter speed faster than the flash sync speed, you would only expose a part of the picture. (The sync speed is the fastest speed at which the entire CCD can be open to light. At speeds faster than the sync speed the slit between the first and second curtain that travels across the CCD narrows.)
Perhaps you might want a ND filter instead.

Vit40 Regular Member • Posts: 269
Re: stonewalled

There are no curtains on A series. Shutter is combination of mechanical shutter in lens and electronic shutter in CCD, an 1/500s is certainly achieved with electronic shutter, as mechanical one isn't so fast

Lilien Regular Member • Posts: 140
Re: "Dead/Stuck Pixel Remapping"?

Russel_Sprouts wrote:

Which models have you seen/read that offer the user an ability to
"map out bad pixels"? (I haven't seen any)

Olympus named this feature Automatic Pixel Mapping (APM), it was
developed to keep the camera operational over an extended period
of time, reducing the need to send the camera in for service.
The Kodak Easyshare P880 offers a pixel remapping program to
remove any malfunctioning pixels. And last but not least there is a
russian hack/program, that can remap bad pixels on some (now older)
Nikon (e.g. Coolpix 2500) and Olympus cameras. (For this russian program
see here: http://e2500.narod.ru/ccd_defect_e.htm ).

What is your point?
Is this not a nice feature to have in a camera?

harvester Contributing Member • Posts: 693
Re: stonewalled

Vit40 wrote:

There are no curtains on A series. Shutter is combination of
mechanical shutter in lens and electronic shutter in CCD, an 1/500s
is certainly achieved with electronic shutter, as mechanical one
isn't so fast

Interesting. Do you know how the mechanical shutter works?

OP donmorris Regular Member • Posts: 155
Re: stonewalled

harvester wrote:

Vit40 wrote:

There are no curtains on A series. Shutter is combination of
mechanical shutter in lens and electronic shutter in CCD, an 1/500s
is certainly achieved with electronic shutter, as mechanical one
isn't so fast

Interesting. Do you know how the mechanical shutter works?

Hi,
I took apart my brothers broken camera. A80?

It seems like a very small motor would cause 2 vanes to close from opposite sides. I still have some of the more interesting pieces, like that 1.
lol
Don

Russel_Sprouts Regular Member • Posts: 300
Re: stonewalled

harvester wrote:

Russel_Sprouts wrote:

I desperately want to circumvent the 1/500sec minimum shutter speed
imposed when flash is enabled, but it seems this won't be possible.

Are you sure you want that? I think if you would be able to choose
a shutter speed faster than the flash sync speed, you would only
expose a part of the picture. (The sync speed is the fastest speed
at which the entire CCD can be open to light. At speeds faster than
the sync speed the slit between the first and second curtain that
travels across the CCD narrows.)
Perhaps you might want a ND filter instead.

My primary concern is toward reducing motion blur. If the flash sync "misses" and I don't get the peak flash output, that's okay by me.

Russel_Sprouts Regular Member • Posts: 300
Re:

Lilien wrote:

Russel_Sprouts wrote:

Which models have you seen/read that offer the user an ability to
"map out bad pixels"? (I haven't seen any)

Olympus named this feature Automatic Pixel Mapping (APM)...

{snip}

What is your point?
Is this not a nice feature to have in a camera?

point:

If it's not native to the DIGIC II cameras, it's not available for the CHDK to "hack", eh?

moretoys Contributing Member • Posts: 543
SD version?

Is anyone working on getting this to work on the SD cameras. I have an SD600 that I would love to have RAW ability
--
----Steve----
Canon SD600
Sony H2
Sony P73

 moretoys's gear list:moretoys's gear list
Olympus XZ-2 iHS Olympus PEN E-PM2 Olympus E-M1 II Olympus M.Zuiko Digital ED 40-150mm F4-5.6 R Olympus M.Zuiko Digital ED 14-42mm F3.5-5.6 EZ +2 more
harvester Contributing Member • Posts: 693
Re: SD version?

moretoys wrote:

Is anyone working on getting this to work on the SD cameras.

AFAIK no.

moretoys Contributing Member • Posts: 543
Re: SD version?

harvester wrote:

moretoys wrote:

Is anyone working on getting this to work on the SD cameras.

AFAIK no.

Thanks
--
----Steve----
Sony H2
Sony P73

 moretoys's gear list:moretoys's gear list
Olympus XZ-2 iHS Olympus PEN E-PM2 Olympus E-M1 II Olympus M.Zuiko Digital ED 40-150mm F4-5.6 R Olympus M.Zuiko Digital ED 14-42mm F3.5-5.6 EZ +2 more
GrAnd Regular Member • Posts: 325
Build #119

Build #119

  • uBasic: Corrected constants for "set_av", "set_tv" commands

+ uBasic: Added "get_zoom", "set_zoom", "set_zoom_rel" commands

  • uBasic: Increased maximum script size from 2K to 8K

Regarding " zoom" commands...
There ate a lot of restrictions/issues with them:

  • Camera does not refocus automatically after the end of zooming

  • The "sleep" command is needed after the "set_zoom*" command. Otherwise, camera will shutdown if other command is executed duiring zoomming process.

  • S-series: The speed of zooming depends on previous manual zooming speed.

Russel_Sprouts Regular Member • Posts: 300
where is my cursor?

When simulating the MENU button press (click "menu"), you have the benefit of knowing "where you are, relatively speaking" -- in other words, immediatly after the press, your cursor will ALWAYS be on the "Column1 camera icon" within the menu screen.

Unfortunately, when scripting access to the FUNCTION menu (click "set") this isn't the case. Instead, if you have previously accessed the function menu during the current shooting session, you're presented with a screen based on whichever setting (i.e. ISO or WB or DriveMode etc) you last accessed. This presents a problem, in that you can't foresee the effect a "click down", "click right" simulated keypress will have, because when the script is replayed you can't be certain "where your cursor is", relatively speaking.

Although we probably can't count on jumping to a "known" navigation point within the function menu, due to differences in available settings per camera model as well as availability per shooting mode (P/Av/Tv/M)...

...I've noted (true for the A620, at least) that the function menu "cursor position" gets reset each time you jog the Mode Dial on the camera. I have also noted (I'm not sure what "side-effects" might result, though) that if a script is currently running, jogging the ModeDial does not interrupt the script's execution.

What can we do?
How best to handle FUNCTION menu navigation with certainty?

I can't trust that I'll develop an unwavering habit of jogging the Mode Dial prior to executing any script which simulates FUNCTION menu keypresses. Until the devs arrive at a solution (or until someone suggests a better interim measure), the only workaround I've found is:

For scripts which will simulate keypresses the FUNCTION menu, begin with a print statement advising the user to jog the ModeDial, followed by a sleep XXX line.

harvester Contributing Member • Posts: 693
focus distance in EXIF?

Does somebody know if the camera saves the focus distance in the EXIF info?

Keyboard shortcuts:
FForum MMy threads