the sx10 porting thread

originalstarlite

A while back I saw a couple of jpeg's of the battery icon done in 3D. They sure did look great and I have been hoping that someone would add these to the build.

https://chdk.setepontos.com/d/3443

jlly

Nimrod, thank you for your efforts. my 101b version need RAW and remote control 😀 although not very technically inclined i am prepared to assist where possible.

Sunflower

fe50

- power your cam on, half-press the shutter to go to record mode
- press PRINT, then press FUNC/SET
- select "Load script from file", go 2 steps down to the TEST/ folder, press FUNC/SET
- select "BADPIXEL.LUA", press FUNC/SET
- start the script with the SHUTTER !
- wait until you see "press SET to save....."
- press FUNC/SET to store the badpixel.bin automatically in the right place

I can't seem to get the "press SET to save" message. I run the script as instructed, and the camera clearly is doing something, then some text flashes too fast to be read.

When I press PRINT, the display reads "Create badpixel.bin" in the bottom left corner, with ALT in the center at the bottom.

Can anyone tell me what I'm missing?

an0n

Hi Sunflower,

Have you waited a while for message to appear, if so, check with File Browser to see if BADPIXEL.BIN is there, it should have 50kb - 60kb approx size. (Main Menu>Miscellaneous stuff>File Browser). If not then run through instructions again carefully, if it's there then DNG should be available.

fe50

@Sunflower

Often the script output on the console get's overwriten (cleared) by the Canon OSD...

After the badpixel.lua script is started, it takes a first picture and calculates the bad pixels for ~ 10-15 seconds, then the blue print LED lits for ~ 3-5s; now a 2nd image is captured and calculated, takes 10-15s + 3-5s again...

After that the script is ready & shows the "press SET to save..." message...now (or better: let's say ~50 seconds after the script was started) just press FUNC/SET, regardless what you see on the LCD...

You can also press the <ALT> button twice to pause & continue the script, this refreshes the CHDK OSD and you'll see the messages on the console again...

marianoc

thanks for all, porting sx10 1.02b.

very thanks,
mariano

---------------------

Muchas gracias a todos, por agregar la compativilidad de la sx10 1.02b.

un abrazo,
mariano

Sunflower

an0n
Hi Sunflower,

Have you waited a while for message to appear, if so, check with File Browser to see if BADPIXEL.BIN is there, it should have 50kb - 60kb approx size. (Main Menu>Miscellaneous stuff>File Browser). If not then run through instructions again carefully, if it's there then DNG should be available.

It wasn't there.

fe50
@Sunflower

Often the script output on the console get's overwriten (cleared) by the Canon OSD...

After the badpixel.lua script is started, it takes a first picture and calculates the bad pixels for ~ 10-15 seconds, then the blue print LED lits for ~ 3-5s; now a 2nd image is captured and calculated, takes 10-15s + 3-5s again...

After that the script is ready & shows the "press SET to save..." message...now (or better: let's say ~50 seconds after the script was started) just press FUNC/SET, regardless what you see on the LCD...

You can also press the <ALT> button twice to pause & continue the script, this refreshes the CHDK OSD and you'll see the messages on the console again...

The script was taking the pictures, but seemed to be hanging immediately after. FUNC/SET had no effect after three-four minutes.

I pressed the ALT button twice, then hit the shutter button. The script started again, and finished correctly. The BADPIXEL.BIN file now appears where it should be.

However, now when I power on the camera, and hit the ALT button, this script is loaded and ready to run again. Is there anyway I can unload the script?

fe50

Sunflower
However, now when I power on the camera, and hit the ALT button, this script is loaded and ready to run again. Is there anyway I can unload the script?

CHDK always shows the last loaded/executet script; you can load the "default.bas" script to "unload" the script...

nimrod

Almost everyone is saying that the latest 1.01b test build is working! If you haven't tried it already, please give it a shot:

http://drop.io/nimrodfiles

If you're not yet familiar with how to get this to load, here's some information on how to create a bootable SD card:

http://chdk.wikia.com/wiki/Bootable_SD_card

Also see the FAQ:

http://chdk.wikia.com/wiki/FAQ

Q. How do I get CHDK onto my camera's SD memory card?
Q. How do I manually load CHDK so I can use it?

beez

Nimrod,

Downloaded the 1.01b and was able to load 😀

I will do some more testing tomorrow

Thanks very much

Beez

monk

nimrod,
worked for me to

just have to figure out how to take RAW in a format photoshop can open. Anyone help with that?

nimrod

monk: You just need to enable the "Save as DNG" option in the raw menu. That will save the images in adobe's portable raw format. The canon raw format on the sx10 is different from most other cameras (14 vs. 16 bits per pixel or something) so it typically won't work even on things that support the canon raw format (CRW).

I've been able to load the DNGs from the camera into lightroom with no problem

swordfish

Quick update for Firmware version 1.01B tests

Histogram - Works
RAW DNG - Works
Motion Detection - Works

Thanks again, Nimrod. Will test more and feedback.

Cheers,
Swordfish

reyalp

nimrod
The canon raw format on the sx10 is different from most other cameras (14 vs. 16 bits per pixel or something) so it typically won't work even on things that support the canon raw format (CRW).

I've been able to load the DNGs from the camera into lightroom with no problem

Just to clarify a bit:
SX10 (and most new powershots) are 12 bpp, vs 10 on the older ones. The CRW saved in by CHDK is not canon CRW format, it's just the sensor buffer written to disk. While some programs support CHDK raw, most have not yet been updated to deal with the 12bpp cameras.

Conclusion is the same, use DNG 😉

ChrisD

my camera is shootin in RAW (CRW) but I cannot convert using the latest version of dng4ps2. I have tried the DNG option in the CHDK menu. When trying to select DNG format option I get the error message "Cannot load CHDK/badpixel.bin. Please run CHDK/SCRIPTS/TEST/badpixel.lun. I just cannot locate this file in the CHDK menue. Can anyone help

swordfish

Quick update for Firmware version 1.01B tests

USB Remote - Works

Nimrod,

SDM supports script command "make_usb_connection". Is it possible here?

Cheers,

swordfish

ChrisD,

You have to copy that lua script to your SD card under the script/test directory, using a card reader on a PC. You can get the badpixel.lua script from previous SX10IS builds.

Cheers,

nimrod

I just uploaded a "full" version of the ZIP file that contains the whole CHDK directory and the boot files:

http://drop.io/nimrodfiles

If you don't have the CHDK directory (which is what you need if you want the badpixels script) then download the zip file that says "full" and copy it out of there. The stuff in CHDK hasn't changed, so if you get it from some other build (like 102b) then that's fine too.

I also removed the code that blinks the blue led since that's not needed anymore, but other than that there aren't any changes. I still need to check some stuff in stubs_min.S but the fact that nobody has encountered any major problems means that the one thing I did fix it there might be the only change needed. (I've got a nasty cold and didn't feel like doing it last night.)

I'll also upload the source for anyone who wants to look at it, but it's not ready to check in yet.

nimrod

swordfish
USB Remote - Works
SDM supports script command "make_usb_connection". Is it possible here?

I haven't tried to do anything with the USB remote or that script command yet, so I don't really know. This port is based on "trunk" (vs. SDM, etc) so whatever is in the trunk (standard) build is in this. The porting process mostly just consists of telling the rest of the code where certain functions in the firmware are (many or most of them move around every time Canon comes out with a new firmware version) and unless the one doing the porting can't figure out where some firmware function went, all the features should be the same as any other trunk port.

So basically the more general boards are better for asking about common CHDK features since there are still several that I haven't used. It's possible that some features are broken only in this port because I didn't properly update the address of some function that the feature uses, so if some feature causes the camera to crash or otherwise doesn't work when it works on other cameras then post it here and I'll track down the problem. We may have some features that don't work on any SX10 port yet, but I haven't run into any myself.

Tyler Durden

I'll be DLing and testing the 1.01b port tonight. Thanks for all the work that has been done!

May I make a small suggestion? There are a few different simultaneous discussion threads going on about 1.02b, 1.01b and other versions of the SX10 firmware/CHDK ports. I've been following the posts here for a few weeks and have found it difficult to keep track of who is talking about which port. I think it would be a good idea to put the port/firmware version being discussed in any given post in the subject line and/or somewhere in the body of the post to make it easier to follow the conversations and to search the forum for information on a specific build.

Thanks again!

TD

« Previous Page Next Page »