Warning for developers: properties can be tricky
Alex
knowing what you are doing can be dangerous, because they are stored
in non-volatile RAM.
For example, I've just changed PROP_PIC_QUALITY(0x80000031) to
FFFFFFFF by mistake, and this resulted in error 70. Took battery out,
rebooted => error 70 right from the beginning. The error was present
even in video mode, so I didn't have access to Canon menu to reset the
settings.
Fortunately, ML was still loading (and displaying shutter count and
cmos temperature), so I've been able to revert the property to a valid
value, and now my camera seems alive again :)
It might be also possible to solve cases like this via EOS utility (didn't try).
Fernando Freire
We are going to get nightmares with Err70 monsters :-)
Alex
Actually, 500D developers like those screens :)
"
i got mad last night and i change the code to start dumping from 0x0
(ya' i know!) and the camera crashed with error 70 or something like
this. a very interesting error message where the camera tells you
something is screwed up, displays total shutter releases and a bunch
of other thing and then reboots.
"
source: http://chdk.setepontos.com/index.php?topic=5971.msg61298;topicseen#msg61298
On Sat, Feb 26, 2011 at 9:00 AM, Fernando Freire <nang...@gmail.com> wrote:
> Thanks, I'm collecting also a few scares ...
>
> We are going to get nightmares with Err70 monsters :-)
>
>
> --
> http://magiclantern.wikia.com/
>
> To post to this group, send email to ml-d...@googlegroups.com
> To unsubscribe from this group, send email to
> ml-devel+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/ml-devel?hl=en