Chdk for SX130 IS ? - page 63 - CHDK Releases - CHDK Forum
« previous next »
Pages: 1 ... 58 59 60 61 62 [63] 64 65 66 67 68 ... 110   Go Down

Chdk for SX130 IS ?

  • 1095 Replies
  • 370552 Views
*

Offline backlash4u

  • *
  • 10
Re: Chdk for SX130 IS ?
« Reply #620 on: 12 / June / 2011, 22:54:31 »
Advertisements
hey... i cant find the firmware version number.. i did the process involving ver.req. but the file doesnt contain anything even after doin the whole process. my cam is canon sx130is. 4 gb card... pls help
Logged
*

Offline reyalp

  • ******
  • 13878
Re: Chdk for SX130 IS ?
« Reply #621 on: 12 / June / 2011, 23:01:49 »
The firmware information is not written to the ver.req (or vers.req) file. The file just tells the camera to unlock the key combination that shows the information. The key combination is func+disp on most cameras, including the SX130 if the information on the wiki is correct.

You can also try http://chdk.wikia.com/wiki/CameraVersion
Logged
Don't forget what the H stands for.
*

Offline ppkgzz

  • *
  • 4
Re: Chdk for SX130 IS ?
« Reply #622 on: 13 / June / 2011, 05:01:30 »
Quote from: outslider on 12 / June / 2011, 16:43:07
And now some greetings:) I like to thank to all of people that made CHDK possible thing;) They saved this nise sunset:

Amazing...
I'm learning now to use this camera and I would like to know how could I take a similar picture. I think that I'm not taking all advantage of this camera and CHDK
Logged
*

Offline jfanning

  • *
  • 4
Re: Chdk for SX130 IS ?
« Reply #623 on: 13 / June / 2011, 15:03:44 »
Logged
*

Offline reyalp

  • ******
  • 13878
Re: Chdk for SX130 IS ?
« Reply #624 on: 13 / June / 2011, 16:31:44 »
Welcome, and thanks for your detailed report. I assume you've read previous posts in this thread about the possible connection between crash and lens error ?
Quote from: jfanning on 13 / June / 2011, 15:03:44
I could hear several faint clicks while the camera tried to start, making me suspect that something was wrong with the shutter.
Could also be lens, if something moves briefly and is stopped by software or mechanical limit.
Quote
  If anyone else gets the lens error, I would suggest removing both the main AA batteries and the CR1220 battery for an hour and so to try a reset.  I tried removing just the AAs for a while with no luck.  I don't recommend taking the camera apart unless you don't have a warranty anymore.
Camera RAM will be cleared as soon as the normal battery is removed. Most other camera non-volatile data is stored in onboard flash (the same "ROM" as the firwmare), which doesn't need any power at all. I don't think the CR1220 does much more than the clock, but I could be wrong. Certainly worth trying if anyone else gets this error.

Quote
If the lens error is CHDK related, removing the batteries must have fixed it.  The lens apparently still worked after the camera crashed, the camera just didn't want to extend it.
Some other thoughts:
- I assume your camera was already disassembled once, to remove the IR filter ? So in your case, there could be issues related to this (ribbon cabled not making good contact etc)
As an aside, if you want to post details of this process in http://chdk.setepontos.com/index.php?board=36.0 I'm sure other members would be interested.
- I wonder if the retract after a crash can leave the lens hardware in an unusual state, that isn't really broken but fools the software. There must limit switches, position sensors and so on. An unexpected combination of these might trigger the lens error without anything really being wrong. Or maybe there's a position where the actuators can stall or hit a current limit.  In this kind of situation, just taking it apart and moving things around might clear it. The next logical step might be trying to gently manipulate the lens without taking it apart.
Logged
Don't forget what the H stands for.
*

Offline jfanning

  • *
  • 4
Re: Chdk for SX130 IS ?
« Reply #625 on: 13 / June / 2011, 17:54:54 »
I have read through most of the thread, but it has been a while.  I guess I should re-read it at some point.
Quote
Could also be lens, if something moves briefly and is stopped by software or mechanical limit.
That could be, but I was in manual focus, and I wasn't using a zoom script.  Nothing was supposed to move at least.  I wasn't watching the camera whenever it happened, so I don't know if anything moved.  Unfortunately, I had the lens zoomed near 60mm, so if it went any farther I wouldn't notice it.  It was still zoomed near the far limit when I found it.  Whatever was clicking was extremely quiet.  It was hard to hear over the static noise of the IS mechanism.
Quote
Camera RAM will be cleared as soon as the normal battery is removed. Most other camera non-volatile data is stored in onboard flash (the same "ROM" as the firwmare), which doesn't need any power at all. I don't think the CR1220 does much more than the clock, but I could be wrong. Certainly worth trying if anyone else gets this error.
That's what I would expect as well.  I forgot about the CR1220 until I took the camera apart, otherwise I would have removed it for a while just as a test.  I didn't notice anything being reset besides the clock.  The file numbering sequence was pushed back a few hundred, but that probably has to do with the crash itself.
Quote
Some other thoughts:
- I assume your camera was already disassembled once, to remove the IR filter ? So in your case, there could be issues related to this (ribbon cabled not making good contact etc)
As an aside, if you want to post details of this process in http://chdk.setepontos.com/index.php?board=36.0 I'm sure other members would be interested.
I actually took the camera apart twice.  I started out using a piece of a Lee 87 filter, then I switched to a Kodak Wratten 89B.  I tried to be careful, but the parts are tiny so I certainly could have damaged something or had some dirt sneak in.  I took pictures of the whole process with the intent of doing a writeup, I just haven't found time to do it yet.  It is actually pretty simple.
The stock IR cut filter is a piece of glass 0.4mm thick.  I couldn't find a source of filter glass that thin without ordering a truck load, so I just used gel.  A small piece of gel filter cut to size fits fine.  The stock filter is so thin that replacing it with gel doesn't change the optical system much.  The manual focus scale is still close enough to correct that I would have to actually measure it to see any error.
Quote
- I wonder if the retract after a crash can leave the lens hardware in an unusual state, that isn't really broken but fools the software. There must limit switches, position sensors and so on. An unexpected combination of these might trigger the lens error without anything really being wrong. Or maybe there's a position where the actuators can stall or hit a current limit.  In this kind of situation, just taking it apart and moving things around might clear it. The next logical step might be trying to gently manipulate the lens without taking it apart.
The weird thing is that the lens seemed to retract fine after the crash, then it refused to extend again.  I sort of wonder if the code that handles startup after a crash has a bug and the camera hits some sort of double fault that isn't handled.  I tried to force the lens in every direction while turning it on.  I wasn't very gentle.  I didn't expect to be able to fix the camera anyway, so I put quite a bit of force on it to see if I got lucky.  Most of the times that I read about trying to force the lens it was after the camera had been dropped or some dirt got into it.  My SX130 was never dropped and it is pretty clean except for some dust.  My SX200 has had a much rougher life, and it still works fine.
I almost hope that the camera crashes again with the lens error.  That way I can try things one at a time next time and maybe figure out the fix.  Every time I have seen someone disassemble a compact camera lens, it never goes back together.  I fully expected to be buying another camera later that night, so I wasn't very scientific.
« Last Edit: 13 / June / 2011, 17:57:29 by jfanning »
Logged
*

Offline jfanning

  • *
  • 4
Re: Chdk for SX130 IS ?
« Reply #626 on: 13 / June / 2011, 19:12:38 »
I just did a quick re-read of the thread.  Obviously, I missed a lot of stuff about other people getting lens errors.  It looks like it is most common when the camera crashes with the lens zoomed most of the way out.  The lens will retract, but then the camera gives the lens error.  A few other people also think that the problem may be in the code that handles recovering from a crash.  I guess I should have re-read the thread before posting.  Oh well.  The thread at http://chdk.clan.su/forum/22-608-6 also seems to have a lot of good information, but I will have to go through the whole thing later with Google translate.  In page 6 of that thread, Ryabchik also mentions the possibility of the Canon error handler messing up.

As far as I can tell, almost everyone who gets the lens error just gets a replacement camera from Canon.  Does Canon ever give any indication of what exactly is broken?  I would guess that these cameras are cheap enough to not be worth fixing, but I would assume that the camera has a more detailed error internally that Canon could read.  I would assume that Canon can tell the difference between a true hardware failure, and the software just freaking out.  "Lens error" covers a whole lot of possible problems.

In the mean time, I will keep running my SX130 hard.  I had it running for about 10 hours today playing with motion detection.  I totally discharged 2 sets of Eneloops until the camera shut down, and I mostly killed 2 more sets.  I haven't had any more trouble.  If I break it again, I will try and see if I can figure out exactly how to fix it, assuming I can fix it again.  It may have just been dumb luck.  If anyone else has one break, I would be curious if just removing both the main AAs and the CR1220 for a while manages to get the camera going again.
Logged
*

Offline reyalp

  • ******
  • 13878
Re: Chdk for SX130 IS ?
« Reply #627 on: 13 / June / 2011, 21:47:29 »
Quote from: jfanning on 13 / June / 2011, 19:12:38
I just did a quick re-read of the thread.  Obviously, I missed a lot of stuff about other people getting lens errors.  It looks like it is most common when the camera crashes with the lens zoomed most of the way out.  The lens will retract, but then the camera gives the lens error.
It's hard to tell how strong the connection is. If these cameras just have a failure prone lens mechanism, it would be pretty hard to tell the difference.
Quote
 In page 6 of that thread, Ryabchik also mentions the possibility of the Canon error handler messing up.
If it is a pure software problem, one might expect Canon to fix it in one of their firmware revs, even if they didn't make a public update. AFAIK, 101c is the only known version though. edit: No, there's 101d as well, a closer look a the differences might be in order.
Quote
I would assume that Canon can tell the difference between a true hardware failure, and the software just freaking out.  "Lens error" covers a whole lot of possible problems.
If Canon has a more detailed error, then we should be able to get it as well. Some digging through the code that generates this might be worth while (also interesting because people would like to override this error so they can replace the optics with their own)

Actually, dumping the console log from a camera in this condition might tell us a lot. This can be done in an eventproc enabled build with a lua script like
Code: [Select]
uartr=require("uartr")

-- redirect UART to specific file
uartr.start("A/CONDUMP.LOG", 1)
sleep(100)
call_event_proc("ShowCameraLog")
If the error only appears when you attempt to switch to record, you'd want to do that immediately before running the script, or use a set_record(1) in the script and wait a second before dumping the log.

There is also "mecha condition" displayed in the detail version info pages (from vers.req), which might be related. Some of the mecha eventprocs (http://chdk.wikia.com/wiki/User:ReyalP/EventProcNotes#MechaRegisterEventProcedure - note these are from a much older camera, might not exist or have different names on yours ) might also provide more information or even get it unstuck I suppose.

Quote
In the mean time, I will keep running my SX130 hard.
Excellent, please do keep us posted.
« Last Edit: 14 / June / 2011, 00:24:35 by reyalp »
Logged
Don't forget what the H stands for.
*

Offline backlash4u

  • *
  • 10
Re: Chdk for SX130 IS ?
« Reply #628 on: 13 / June / 2011, 22:57:50 »
my firmware version as it turns out is 1.01d.. so can u direct me to the correct version of chdk... also pls tell  me if it is stable or still in early stages.. tried reading the whole thread... but it is too lengthy...
Logged
*

Offline waterwingz

  • ******
  • 12132
    • Waterwingz
Re: Chdk for SX130 IS ?
« Reply #629 on: 14 / June / 2011, 00:11:34 »
Quote from: backlash4u on 13 / June / 2011, 22:57:50
my firmware version as it turns out is 1.01d.. so can u direct me to the correct version of chdk...
Link to test version of CHDK for the SX130 fw 1.01D

Quote
also pls tell  me if it is stable or still in early stages..
Probably safest to refer to it as early stages.. if you had taken the time to scan through this thread you would have seen the concerns about possible lens errors.

Quote
tried reading the whole thread... but it is too lengthy...
Based on your words above, experimenting with CHDK might not a good idea if you don't have time to understand what you are getting into.  Sorry.

Logged
Ported :   A1200    SD940   G10    Powershot N    G16
Pages: 1 ... 58 59 60 61 62 [63] 64 65 66 67 68 ... 110   Go Up
« previous next »
 

Related Topics