If you plan to purchase a camera with the intention of using it without the lens, please ask before in this forum thread.
- 1 Operating the camera with faulty / missing lens or IS hardware
Operating the camera with faulty / missing lens or IS hardware
Missing or malfunctioning optical image stabilizer
How to recognize?
- The camera stops with an E32 error, usually one minute after switching it on or switching it to rec mode.
- The IS hardware is deliberately disconnected
Cameras released in and after end of 2009 (DryOS r39 or later) have special event procedures dealing with IS errors in their firmware. They are called EnableISDriveError and (the one that's actually useful) DisableISDriveError. To use the latter, one could run a Lua script which invokes it correctly, or a modified CHDK could take care of the invocation.
To make sure your camera has these event procedures, please ask in this forum thread.
There are two kinds of cameras with IS
- IS is disabled in play mode: DisableISDriveError needs to be invoked after each play -> rec mode transition
- some parts of the IS unit are always in use, even in play mode: DisableISDriveError needs to be invoked after any play -> rec or rec -> play transition (* needs proof)
call_event_proc("Mecha.Create") call_event_proc("StartImStEventProc") call_event_proc("DisableISDriveError")
Missing, broken or malfunctioning lens hardware
How to recognize?
- The camera stops with one of the lens related error messages
Partial software solution
This is of no use to most of the camera owners, except when the lens hardware is not needed (astronomical, microscopy applications)
Cameras released in 2011 or later have special event procedures named EnableLensError, DisableLensError. It is assumed that using DisableLensError could prevent camera shutdown in presence of certain (but not all!) lens related error conditions. For example, lens error still appears when the whole lens unit is disconnected, see these forum posts.
Possible hardware solution
Check out the following forum threads