The SX1 IS Porting Thread - page 25 - General Discussion and Assistance - CHDK Forum  

The SX1 IS Porting Thread

  • 381 Replies
  • 183238 Views
*

Offline reyalp

  • ******
  • 14119
Re: The SX1 IS Porting Thread
« Reply #240 on: 10 / May / 2009, 21:53:24 »
Advertisements
4GB card formatted completely to FAT16, copied all CHDK files plus bootdisk.bin and locked the card.  Loaded it into the camera and switched on, the CHDK logo came up (hoot hoot!!). 
Went into the Canon menus and found "Firmware Update...", selected that and it said "update firmware 2.0.0 --> 1.1.0.
Selected "yes" and the camera seemed to lock up.
Firm update and diskboot are alternative methods of loading CHDK.  You only need one or the other.

Firm update is known broken for the SX1, as mentioned multiple times in this thread.

For the histogram issue, it sounds like CHDK is using the wrong part of memory in halfshoot.
Don't forget what the H stands for.

Re: The SX1 IS Porting Thread
« Reply #241 on: 11 / May / 2009, 02:23:22 »
reyalp,
Yeah thanks - as I said - this is my first time to use CHDK so I'm learning by trying.

More information on the histogram....

About an hour after my earlier tests I happened to be taking some pics when I noticed that the static waveform that develops had completely changed shape.  It was still wrong and static but a new form.

Then about 30 minutes later it had changed again.  I tried switching off, back on and even removing the batteries but this didn't change the wave form.

Then I ran off a few random shots and the waveform had changed.  Seems to fill up in the middle after having just taken a burst of photos.  I used high speed continuous (not AF because I had read of the crashes), and immediately afterward the waveform was looking plump (like me)

It seems to be related to the temperature of some part of the camera because after leaving it for a few minutes, the static waveform returns to the left side again.

*

Offline fe50

  • ******
  • 3152
  • IXUS50 & 860, SX10 Star WARs-Star RAWs
    • fe50
Re: The SX1 IS Porting Thread
« Reply #242 on: 11 / May / 2009, 08:04:24 »
One annoyance that remains is that in manual (M) exposure mode the shutter speed is still limited to 1 sec unless you use the override (which is much less convenient) -- any possibility that that will get lifted?

Isn't the Canon lower limit on the SX1 15 s in M mode, as on the SX10 ?  ???

*

Offline pev69

  • **
  • 55
Re: The SX1 IS Porting Thread
« Reply #243 on: 11 / May / 2009, 08:34:12 »
If I remember correctly (still at work), longer than 1 s (and upto 15 s) is only available in the special "long shutter" scene mode.
« Last Edit: 11 / May / 2009, 08:51:36 by pev69 »


*

Offline yvesson

  • ***
  • 209
  • A540 SX10IS
    • poll about some pics (not much serious) ^^
Re: The SX1 IS Porting Thread
« Reply #244 on: 11 / May / 2009, 09:22:55 »
Hej,
Yes, amazingly it's limited more than the SX10, I read that in a review lately, and I'm very happy I have the SX10, cause I would be extremely pissed if that was limited to 1s in manual modes. :/
That has to be on purpose, but just to annoy people ? I don't get it.

Re: The SX1 IS Porting Thread
« Reply #245 on: 11 / May / 2009, 17:45:02 »
Possible bug...  Connecting to the video out with my tv, most of the CHDK OSD stuff runs off the screen...  Any one else experience this?
« Last Edit: 16 / May / 2009, 09:35:59 by miahill9 »

Re: The SX1 IS Porting Thread
« Reply #246 on: 11 / May / 2009, 19:41:12 »
Earlier I reported this...

3) Enable OSD Symbols
Just a minor point but if these are turned on in the menu, the option reverts to off again after switching off and restarting the camera.


However, something changed last night and the symbols are now staying in place after a power down.  I'm not sure but I think it was after I experimented with selecting the symbol fonts in Visual Settings.  First I tried ICON_10.RBF but they show nothing on screen, then I selected ICON_16.RBF and the symbols have remained on the menu ever since.

However, I seem to have found a new problem with the AF assist beam.  With CHDK loaded, it flickers twice at boot-up but seems to be disabled thereafter even though I confirmed it as ON in the Canon menu.  With CHDK not loaded, it works normally.

So in summary, up to now I have seen,

1) Histogram problem at half shoot.
2) User Menu not editable
3) AF assist beam not functioning

I can confirm that I also experienced the AF Continuous Shooting Crash reported by others earlier.

I hope this helps someone who know how to program  :D

-----------------------------------
Comments for those above discussing the lack of long shutter times.

With the overrides ON and Dark Frame Subtraction, it should be easy to get good images at crazy shutter times.  Last night I was experimenting with 40 seconds in a nearly dark room.  Haven't had a chance to analyze the results yet - as I said, I am still learning my way around CHDK.

I don't see any inconvenience in setting up and using the overrides, it is not as if you are going to be selecting those settings for a quick snapshot.  The only thing I can see at the moment is that the EXIF data seems to report a maximum of 15 seconds in the recorded image.

*

Offline pev69

  • **
  • 55
Re: The SX1 IS Porting Thread
« Reply #247 on: 12 / May / 2009, 05:06:21 »
However, I seem to have found a new problem with the AF assist beam.  With CHDK loaded, it flickers twice at boot-up but seems to be disabled thereafter even though I confirmed it as ON in the Canon menu.  With CHDK not loaded, it works normally.

See reply #212:
http://chdk.setepontos.com/index.php/topic,3410.msg33101.html#msg33101

Hey reyalp, or other devs, perhaps the debug_led should be permanently disbled for the SX1 for now?! Because no direct address has been found for other than the AF assist lamp. Actually it should be fixed from the core code, something stupid is going on that turns the debug LED off repeatedly.

Quote
2) User Menu not editable

I have used the user menu successfully. You have to use the single erase button (not +/-) to add a menu item to user menu when user menu is in edit mode.


alife and back
« Reply #248 on: 12 / May / 2009, 19:43:34 »
Hi all!

I was really "quiet" (no substantial updates) for the last two weeks because: First my PC had to get a decent "upgrade" after some HW issues (including to be offline for about 4 days), then last week I was on holidays (where I enjoyed distance to PC's and stuff). Holidays were nice, because I had my SX1 with me and could take some nice shots (+ experiment with CHDK). At least for myself: I think the SX1 CHDK Port is "usable" in wide parts (or at least, what I myself expect from it).

(@all: I'm the one who started together with the help of pev69, the "Port" of the SX1 up to current status)

I confirm pev69 summary of the current status of the CHDK Port for the SX1 on Page "16" of this thread and if time allows: I'm working on the "manual load method" (with PS.FI2) as well to find the issues of crashes while "continuous AF". Please understand that what my part is concerned - I'm not a developer! ...so I do compare firmware codes (of SX1 with different Cam's and within "firmware releases" and I try to understand the "binary/assembler sequences" and checkout if there are some "calls" to subroutines, which causes the SX1 to crash. If such routines are found, they need to be checked if not something substantial is not working later. This is a quite cumbersome work, because most of the code is not documented in any manner...

So as pev69 mentioned earlier: I see my further work more related to find/fix the "manual load" method (if possible) and potentially the "continous AF crashes". Also to find the other LED Adresses, because in the SX1 code only the AF-Beam LED is "known" (for now). The other LED values (Print Button, PowerOn etc) seem to be "calculated" whereas I do not have the formula right now.

I'm very glad that pev69 helped to fix the "Zebra-Mode"/MotionDetection thingy until now (he is definately more "developer" than me).

I think you folks do not always need to check this "thread" if you are interested into latest development. Due to the fact, that the SX1 CHDK is on the AutoBuild Server, the best thing is to get it from there.

Tip: To see if on the most recent CHDK Release there has been a major change to SX1 Code, please check out this link to see if there has been a specific change added to the SX1 CHDK Codebase: http://tools.assembla.com/chdk/log/trunk?action=stop_on_copy&rev=head&stop_rev=&mode=stop_on_copy&verbose=on --> Last change happened on Release @752


If nothing is mentioned, then nothing new to be reported.

(first Picture from Island Sylt (Germany), with 52mm C-Pol Filter)
(second Pictures from the moon (handshoot, 80x Zoom, 1/125)
(third Pictures from the night sky (on trypod, 32sec)
« Last Edit: 12 / May / 2009, 19:52:35 by fboesch »

*

Offline pev69

  • **
  • 55
Re: The SX1 IS Porting Thread
« Reply #249 on: 13 / May / 2009, 07:06:22 »
Hi fboesch, welcome back, good to hear from you after a while!

I have also been quiet regarding modifications to CHDK. I have studied the code somewhat, but just have not gotten myself to properly start any changes. I still have big plans for it :)

Regarding the LED addresses, perhaps they are only needed for some debugging, because in "normal operation" (mostly I mean not during the boot-up sequence) you can use the LEDs with the "set_led" command in scripts, and the "ubasic_set_led(led, state, 0);" function call in the code, see my reply #215:
http://chdk.setepontos.com/index.php/topic,3410.msg33238.html#msg33238
As you can see, the LEDs can do nice things on their own, heh.
« Last Edit: 13 / May / 2009, 07:29:32 by pev69 »

 

Related Topics


SimplePortal 2.3.6 © 2008-2014, SimplePortal