SD 4000 IS / IXUS 300 HS / IXY 30S porting thread - page 31 - DryOS Development - CHDK Forum

SD 4000 IS / IXUS 300 HS / IXY 30S porting thread

  • 322 Replies
  • 160905 Views
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #300 on: 07 / February / 2012, 16:15:36 »
Advertisements
Hi,

I tried to use the focus bracketing with beta11, but it doesn't work. All scripting and or inbuild feature, which try to access the focus resulting in a shut down of the camera.

Is focus bracketing not yet implemented or is it my misunderstanding of tutorials and scripts.

I would love to do focus bracketing. It would be the key feature for digiscoping  :xmas

best regards
Sven

P.S: What are the prerequisite to support a porting (e.g. Assembler-Programmer)

Hi pixeldoc2000,

I have installed the c environment for the CHDK development and I'm willing to do some coding, as long as it is not ASM.
Could you give me a jump start, where to look for, if I want to get focus bracketing working on the SD4000.
Or is there a golden rule, if the camera does not offer manual focus, you can set the focus by chdk?

Every idea, where to look is appreciated!

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #301 on: 09 / February / 2012, 15:25:28 »
Anyone using Exmem on this model?
Well i did a little bit of testing with exmem some time ago, but not much. I could compile a build with enabled exmem i you want to give it a try.
« Last Edit: 09 / February / 2012, 15:57:27 by pixeldoc2000 »

*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #302 on: 09 / February / 2012, 15:58:37 »
I have installed the c environment for the CHDK development and I'm willing to do some coding, as long as it is not ASM.
Could you give me a jump start, where to look for, if I want to get focus bracketing working on the SD4000.
Or is there a golden rule, if the camera does not offer manual focus, you can set the focus by chdk?
Well what you can do is the compare the disassemble firmware (ASM) from simular cameras (same dryos version, simular hardware, etc.) and their relevant platform code with SD4000.

*

Offline reyalp

  • ******
  • 13717
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #303 on: 14 / June / 2017, 00:23:38 »
Following a report in https://chdk.setepontos.com/index.php?topic=13160.0 I checked in some changes for this in trunk 4828 / stable 4829. These aren't thoroughly tested, but the keymask and "usb over dng" code were clearly wrong, so it's unlikely to be much worse.

* add play button to key mask
* remove KEY_PRINT alias
* remove UP+LEFT alt key option
* remove invalid DNG over USB code

Any reports from owners of this camera would be appreciated.
 
Don't forget what the H stands for.


Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #304 on: 08 / July / 2017, 23:30:14 »
Any reports from owners of this camera would be appreciated.

A number of possible issues with the ixus300_sd400 port have been kindly reported over the past few weeks by Robert1975. He did not have much time to assist in debugging the issues but did offer a number of theories about the possible root causes. 

So I recently borrowed one of these fine cameras, fixed the issues identified, and where there was actually no issue I was able to demonstrate that as well.  I've just posted a patch for inclusion in the autobuild so these fixes should propagate shortly. Here's a more detailed list of the problem description and result for the record.

Keymap Wrong
It appears that mixing Jog wheel and buttons on SD4000 required some "weird" key mapping system in Canon's original firmware which makes CHDK a bit more difficult to run on this model.
Fixed in June by reyalp.  There is nothing unusual about the operation of the keys or jog dial on this camera - they now all work as expected.  I've spent a couple of weeks using the latest code - it just works.

Note that the original <ALT> key function of "UP+LEFT" on the jog dial (315 deg) did not actually activate <ALT> - you could do that whenever the LEFT position in the jog dial (270 deg) was pressed.

"Touch Wheel" Feather Touch Feature
Yes, looking at the code and manual, this camera appears to have both a jog dial and "touch wheel".
For reference, this touch wheel is purely mechanical - there is no capacitive touch functionality.  When you press at any position on the jog dial, it's like a two position mechanical switch. Canon uses light presses to trigger On Screen descriptions of what the otherwise unlabelled jog dial does when you press at any position.  When you press a little harder, those functions activate. 

CHDK correctly ignores the light touches completely in <ALT> mode - could be a fun project some day to figure out something to do with those touches.

Memory Issues
There is no "DNG issue", it's a general memory/CPU issue which affects all kinds of shots at slower shutter speeds as the camera needs more power to process images. Fixing this would require rewriting both Canon's original memory management and CHDK, as well as replacing RAM/CPU chips with better ones.
This turned out to be completely untrue. The reported "crashes" were apparently just the user not waiting for dark frame subtraction to complete after each shot.  Turning off dark frame subtraction "fixed" the non-existant memory issue without any need to rewrite Canon's memory management.

Dual Partition Cards
Partitioned cards are not recognized by this cam.
That was a legitimate bug.  Fixed now.

Manual Focus
We also established that all focus commands end in failure, and manual focusing (S.D.O.) is not possible.
True - but it's fixed now.
I knew it was pointless to try anything about manual focusing on this cam.
Well, not pointless at all.  It works fine now with a little debugging and testing. Demo script for using MF attached.  You can also invoke AFL manually (per one of your posts) and use the CHDK menu SD override option.

is_key
I can now definitely confirm is_key does NOT work with SD4000 due to the reasons I explained in previous post.
There are no issues with is_key.  However, there are a lot of issues with the script you posted - I finally got it working after major editing and fixing things you did not anticipate.  PM me if you want a copy?

Bugs in uBASIC
And the script, well, there are bugs and issues within the language itself. Check out this document http://images2.wikia.nocookie.net/__cb20100806022158/chdk/images/e/e5/UBASIC_User_Guide_D0_5.pdf Page 21, NESTED IF. This applies to my problem. I was very close to the solution with the first version of the loop, even with the "wrong syntax" (the script was actually running without errors reported), but the machine definitely has some issues with keys and buttons.
A very old reference to an obsure obsolete branch of CHDK.  There have been a lot of changes, bug fixes, and updates in the subsequent years.  Having now tested with the camera, I can state that there are no issues with keys and buttons on the ixus300_sd400.  Your script was another issue however.  8)
Ported :   A1200    SD940   G10    Powershot N    G16

Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #305 on: 09 / July / 2017, 17:19:28 »
But for example, turning the wheel in CHDK in Beta I tested today affects the aperture - quite annoying, shouldn't happen...
Yep, Av value changes while turning the wheel in CHDK menu.

Update : While the keys & buttons are very stable now, I can confirm this still happens in one use case.  If you rotate the jog dial while you are in <ALT> mode, you will get one jog dial "click" in whatever direction you used when you exit <ALT>.   So if you are in Av or Tv priority shooting mode, that value will change.

No magic here - the jog dial code is incomplete.  I'll fix that in my next update - I've now almost fixed zebra, histogram, edge overlay and live view so I'll roll all the fixes into one update.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline hwntw

  • ***
  • 159
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #306 on: 11 / July / 2017, 07:36:55 »
Thanks for this: I love my Ixus 300, it is very stylish and fun to use
Ixus 300HS S100


Windows 10

Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #307 on: 11 / July / 2017, 07:58:00 »
Thanks for this: I love my Ixus 300, it is very stylish and fun to use
Thanks. I've learned to like the camera too. It's half way between my ixus120 and my G10.

I now have the jog dial problem fixed and I hope to nail down the final common issue with zebra, edge overly, histogram, motion detect, and live view shortly.
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline pixeldoc2000

  • ****
  • 356
  • IXUS900Ti 1.00C, IXUS300HS 1.00D
    • pixel::doc homebase
Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #308 on: 11 / July / 2017, 17:40:52 »
Glad someone is still trying to finish my port. Thx!

It still bugs me today that i was not able to finish it.  :-[

Maybe i can assist with some testing.
 

Re: SD 4000 IS / IXUS 300 HS / IXY 30S porting thread
« Reply #309 on: 11 / July / 2017, 20:41:33 »
Glad someone is still trying to finish my port. Thx! It still bugs me today that i was not able to finish it.  :-[
I just posted another patch file that hopefully kills the last of the really big issues. But you did all of the really hard work and "heavy lifting" for this port!  I'm just doing a little cleanup based on having done five other ports already.

Quote
Maybe i can assist with some testing.
You did a really nice job of flagging "ToDo" items in your source code.  Once the updates hits the autobuild server (hopefully tomorrow) I could use some help reviewing the "ToDo"'s, deleting the ones that no longer apply, and then putting together a list of bugs that still need fixing.
Ported :   A1200    SD940   G10    Powershot N    G16

 

Related Topics