CHDK Forum
CHDK Development => General Discussion and Assistance => DryOS Development => Topic started by: JimP on 06 / May / 2012, 15:14:31
-
Hi everybody,
I am new to CHDK development and just starting to get acquainted here. I've used CHDK a little bit on my S95, and now I would like to get it working on my new ELPH 110 HS. Seeing no prior work on this camera here, I've decided to give it my best shot. I have programming experience, mostly C and Python, no experience with disassembly, etc. but I am willing to learn. I am using Ubuntu for development, so I will have to figure out what tools are available for all this.
Here is what I've done so far:
I tried getting firmware version with ver.req/vers.req using FUNC/SET+DISP as well as every other button combination I could think of, but nothing seemed to work. Then I tried giving an image to ACID, and that gives me firmware version: 100d
Used the univeral dumper script to dump the firmware. The log file says:Started
FF000000 dry
done
The dumped PRIMARY.BIN is here: http://ubuntuone.com/13tgUTl51dOVupayl3Rxcs (http://ubuntuone.com/13tgUTl51dOVupayl3Rxcs)
Started a wiki page: http://chdk.wikia.com/wiki/ELPH110HS (http://chdk.wikia.com/wiki/ELPH110HS)
I'm kind of short on time the next few days, but hopefully will have more time later this week to work on it.
Any help is welcome. Thanks!
Jim
-
Welcome.
If you haven't already, be sure to check out http://chdk.wikia.com/wiki/For_Developers (http://chdk.wikia.com/wiki/For_Developers) especially http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera (http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera)
Assuming you don't have the appropriate version of IDA, you'll also want to look at http://chdk.wikia.com/wiki/GPL_Tools (http://chdk.wikia.com/wiki/GPL_Tools) and possibly consider running http://chdk.wikia.com/wiki/CHDK-PT (http://chdk.wikia.com/wiki/CHDK-PT) under wine.
You can sometimes get more real-time help in the irc channel, #chdk on freenode.
You will also need a properly configured ARM toolchain.
From the dump, this is a DryOS R50 cam. This new OS version has some differences from earlier versions. The sx260 is the first dryos R50 port, so you will want to follow that thread http://chdk.setepontos.com/index.php?topic=7889.0 (http://chdk.setepontos.com/index.php?topic=7889.0)
-
Added the
- IXUS 125HS / ELPH 110HS 1.00B
full 16MB dump (dumped with cBasic udumper) by JimP from this forum post (http://chdk.setepontos.com/index.php?topic=8085.msg85120#msg85120) to the box.net/chdk (http://www.box.net/chdk) repository.
-
Hi there,
has anyone gotten into CHDK development for the IXUS 125HS / ELPH 110HS yet?
My coding skills are limited to turbo pascal/delphi, prolog and huskell which only adds to general code understanding. But if someone would guide me, I might be able to contribute to the IXUS 125HS port.
cheers,
Samplidude™
-
has anyone gotten into CHDK development for the IXUS 125HS / ELPH 110HS yet?
My coding skills are limited to turbo pascal/delphi, prolog and huskell which only adds to general code understanding. But if someone would guide me, I might be able to contribute to the IXUS 125HS port.
Standard disclaimer at this point :
link> CHDK FAQ : My camera isn't ported yet (http://chdk.wikia.com/wiki/FAQ#Q._My_camera_isn.27t_ported_yet._Is_a_port_planned.C2.A0.3F_When_will_it_be_ready.C2.A0.3F_How_can_I_help.C2.A0.3F)
Other than that, the links reyalp posted above are a good place to start. First step, in addition to reading through the info above, is to setup a build environment (try CHDK-shell on Windows). If you can rebuild other versions then you have a starting point. It wasn't pretty, but there is at least one port "completed" but someone who claimed to have no coding experience. So you are off to a better start.
-
has anyone gotten into CHDK development for the IXUS 125HS / ELPH 110HS yet?
My coding skills are limited to turbo pascal/delphi, prolog and huskell which only adds to general code understanding. But if someone would guide me, I might be able to contribute to the IXUS 125HS port.
Hi, I started a blind port of this camera, fw version 100d. It is not complete, but you can use it to start. The files are available here (http://subversion.assembla.com/svn/nafraf/chdk/).
-
I'm also interested in CHDK for the IXUS 125HS / ELPH 110HS, but haven't got the programming skills to help.
But i managed to do a Firmware dump for version 100e:
Download here: https://www.box.com/s/sxou90liimubs48ute4x (https://www.box.com/s/sxou90liimubs48ute4x)
-
Hello & welcome, lakeroe !
But i managed to do a Firmware dump for version 100e:
Good start, thanks for the dump.
Added the
- IXUS 125 / ELPH110HS 1.00E
full 16MB dump (dumped with cBasic udumper) by lakeroe from this forum post (http://chdk.setepontos.com/index.php?topic=8085.msg93993#msg93993) to the CHDK P&S FW dumps (http://tinyurl.com/chdkfiles) repository.
-
I'm also interested in CHDK for the IXUS 125HS / ELPH 110HS, but haven't got the programming skills to help.
I can try to continue the port, but I need your help for tests.
-
I can try to continue the port, but I need your help for tests.
Sounds good, I'm willing to help, what can I do ?
-
@lakeroe
I'll send a PM to you with the link to the pre-alpha version. To test, you need to load chdk using the Bootable SD Card Method (http://chdk.wikia.com/wiki/Prepare_your_SD_card#Bootable_SD_Card_Method)
-
I have programming skills, but none with CHDK, and no time - too busy working. (I bought the camera to document stuff at work actually.) Fairly experienced with CHDK use though.
I can test, give workable bug reports, and maybe dive into the code if I get any free time.
-
I can test, give workable bug reports, and maybe dive into the code if I get any free time.
What is the firmware version of your ixus125?
I'm trying to port CHDK to this camera, lakeroe is testing using 100e, but we have not got CHDK booting. :-[
-
Mine is 101a. Don't see the FW here, so I dumped it.
Canon 110HS 101a PRIMARY.BIN
http://www.filedropper.com/primary_1 (http://www.filedropper.com/primary_1)
-
Thanks for the dump !
Added the
- IXUS 125 / ELPH 110 1.01A
full 16MB dump (dumped with cBasic udumper) by true from this forum post (http://chdk.setepontos.com/index.php?topic=8085.msg94400#msg94400) to the CHDK P&S FW dumps (http://tinyurl.com/chdkfiles) repository.
-
I've used CHDK on a couple of other cameras, and would like to help with tests.
-
@slonav
What is your firmware version?
-
I get what appears to be a test screen when I press FUNC/SET and the playback button at the same time (starting with the former). You can browse colors with the direction keys. It's also a nice clock if you don't have your cell phone handy. I'm not sure if that's at all helpful, but I'm posting it just in case.
edit: It shows a calendar if you rotate the camera
-
@slonav
What is your firmware version?
I've been unable to get the firmware version from the ver.req/vers.req method. ACID reports my firmware as 100d.
-
Is there anything else I can try to get my 101a to boot? Code and toolchain setup instruction (linux and windows OK)? Might have a day or two this holiday to try to get some sort of positive result on the 110HS... don't even know where to start.
-
Code and toolchain setup instruction (linux and windows OK)?
http://chdk.wikia.com/wiki/For_Developers (http://chdk.wikia.com/wiki/For_Developers)
Scroll down to the section titled "Common Articles". You probably want to start with :
http://chdk.wikia.com/wiki/Modifying_the_CHDK_Sources (http://chdk.wikia.com/wiki/Modifying_the_CHDK_Sources)
http://chdk.wikia.com/wiki/Compiling_CHDK_under_Windows (http://chdk.wikia.com/wiki/Compiling_CHDK_under_Windows)
http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version (http://chdk.wikia.com/wiki/Adding_support_of_a_new_firmware_version)
-
@true
I had not luck with boot, but the source code is available here (http://subversion.assembla.com/svn/nafraf/chdk/).
Read notes.txt (http://subversion.assembla.com/svn/nafraf/chdk/platform/ixus125_elph110hs/notes.txt) to know the porting status.
-
waterwingz and nafraf, thanks. Got a toolchain built on linux and it seems to build CHDK fine.
Of course, it won't work with 110HS. nafraf, what was the code you used for LED tests? Do you think the addresses are different in this version? Should I find them?
(Edit: Used cBasic, the LED addresses are fine...)
-
Has anyone made progress on this? I would like to contribute, but I've never gotten far with hacking away at software and hardware. I'd be happy to try out test builds unless there's some tangible risk to it.
-
I continued with this blind port for fw version 100d, 100e and 101a, source code is available here (http://subversion.assembla.com/svn/nafraf/chdk/).
Compiled version for 100d and 101a is in attachment. These are limited versions only to test boot. Firmware update method is not available. To load CHDK, it is necessary to use bootable sd card method (http://chdk.wikia.com/wiki/Prepare_your_SD_card#Bootable_SD_Card_Method).
If someone can test it, please report the results.
-
File for 100e in attachment
EDIT:Out of date files deleted, check autobuild server
-
Thanks to nafraf
for the Blind Port's
For Me Versions prior to Revision 263
Booted and then crashed.
The last version [243] I tested however, Booted, "Blinked", and then crashed.
-=-=-=-=-=-
Re:- "If someone can test it, please report the results."
ixus125_elph110hs-100e-1.2.0-boot.zip
Note #1:- SD Card Formated via a Ixus 115-100b Camera
Ixus 125-100e 1v20 Boot's ok, runs [? ok ?]
-=-=-=-=-
Re:- "Compiling" results
nafraf - Revision 263: /chdk [125-100e]
Note #2:- when downloading "USE TXT FORMAT ONLY !!!"
the Other formats will corrupt the files
-=-=-=-=-
Compiles, for me, Ok using version 263 [but a modified] trunk-2606.zip
[modified] ixus125_elph110hs-100e-1.2.2606 Compiles Ok, Boot's ok, runs [? ok ?]
-=-=-=-=-
Found lots of typo's and some other stuff.
Found, for Ixus 115 some other stuff.
-=-=-=-=-
BUT there are more test's still "To-Do" [soon...ish.]
Good WORK
Thanks to All
H-H
-
Hi, thanks for report.
Re:- "If someone can test it, please report the results."
Ixus125_elph110hs-100e-1.2.0-boot.zip
Note #1:- SD Card Formated via a Ixus 115-100b Camera
Ixus 125-100e 1v20 Boot's ok, runs [? ok ?]
-=-=-=-=-
If CHDK boots, please run the test scripts: http://chdk.wikia.com/wiki/Testing (http://chdk.wikia.com/wiki/Testing)
Use [>] to enter in ALT mode.
Re:- "Compiling" results
nafraf - Revision 263: /chdk [125-100e]
Note #2:- when downloading "USE TXT FORMAT ONLY !!!"
the Other formats will corrupt the files
You are compiling the code 8)
I did not understand your note about "TXT FORMAT", did you have problem using svn checkout?
Compiles, for me, Ok using version 263 [but a modified] trunk-2606.zip
[modified] ixus125_elph110hs-100e-1.2.2606 Compiles Ok, Boot's ok, runs [? ok ?]
If you found some bug, please tell me.
Found lots of typo's and some other stuff.
Found, for Ixus 115 some other stuff.
The version for Ixus115 in my repository is out of date. I can check it if you need it, it is there because it is a patched version to remove 10min video time limit. But it was not added to official repository because it was not tested in all firmware versions.
-
Hi All,
I can, on a sunny day, use WiFi via a high gain, but narrow band external antenna.
There is then a choise of more than 200 WiFi's, some over 2kms away but the the connections are generaly
slow and un-reliable.
The best and most reliable signal strength is from the nearest set of "Trafic Lights".
The Only "LEGAL and FREE" internet access access I have is a time limited secssion in a public libary.
via Windows Xp running Sp3 and Ie8.06.
So When downloading the [individual] files:-
"Save as Type" = "Text File [*.txt]"
Other "Save as Types" introduce additional characters and corrupts the files.
This problem could be solved just by being able to Download the files as a Zip Archive.
Re:- Ixus 115 [ total of 6 cameras]
I have not downloaded any of your 115 versions.
I will post Ixus 115 stuff, soon...ish.
Re:- Ixus 125 [ total of 2 cameras].
I have "Dissassemled" one of the Ixus 125's.
There are some "Errors?", but they may be my own fault.
I have now Up-dated my custom Windows camera driver for the Ixus 125.
PtpCamGui works very well.
ChdkPtp-r311 works exceptionaly well.
Hardly any camera chrashes at all.
H_H
-
There is then a choise of more than 200 WiFi's, some over 2kms away but the the connections are generaly
slow and un-reliable.
Not to mention illegal?
This problem could be solved just by being able to Download the files as a Zip Archive.
ZIP archive is the only format offered here : http://mighty-hoernsche.de/ (http://mighty-hoernsche.de/)
Or did I miss something in your rather long & rambling non-specific post?
-
This problem could be solved just by being able to Download the files as a Zip Archive.
ZIP archive is the only format offered here : http://mighty-hoernsche.de/ (http://mighty-hoernsche.de/)
Or did I miss something in your rather long & rambling non-specific post?
It seems that Hardware_Hacker is talking about ixus125 source code (under development), I think that he is downloading every file from my personal svn repository using web browser. That's the problem.
A svn client can solve it:
svn checkout http://subversion.assembla.com/svn/nafraf/chdk/loader/ixus125_elph110hs loader/ixus125_elph110hs
svn checkout http://subversion.assembla.com/svn/nafraf/chdk/platform/ixus125_elph110hs platform/ixus125_elph110hs
-
Hallo,
I'm very interested in having the CHDK for this camera, in fact there is some urgence in my case.
I would like to participate with the actual releases, but I do not know how.
Following th einstructions here > http://chdk.wikia.com/wiki/Prepare_your_SD_card (http://chdk.wikia.com/wiki/Prepare_your_SD_card) there is the indication, that I need a file called either ps.fi2 or ps.fir in the root directory of the card.
Where do I get these or how to generate them, if I want to test the releases shared some post above?
Thanks
Patrick
-
I got one of them to boot, but I forget which one. The other two locked the camera up in such a way that I had to remove and reinsert the battery, which reaffirmed my fear of lightly tested software.
-
@Aerorara, there is not ps.* file for this version, it is under development.
Compiled version for 100d and 101a is in attachment. These are limited versions only to test boot. Firmware update method is not available. To load CHDK, it is necessary to use bootable sd card method (http://chdk.wikia.com/wiki/Prepare_your_SD_card#Bootable_SD_Card_Method).
To start using CHDK, you need to know the firmware version of your camera. This tool can help you: http://chdk.wikia.com/wiki/ACID (http://chdk.wikia.com/wiki/ACID)
-
I got one of them to boot, but I forget which one. The other two locked the camera up in such a way that I had to remove and reinsert the battery, which reaffirmed my fear of lightly tested software.
While you are right to be wary of a new and mostly untested CHDK port, what you saw is exactly what will happen when you load the wrong version of CHDK for your camera. The CHDK version has to match your camera's firmware version or it will lock up, usually requiring a reset by pulling the battery. The version that booted is the one that matches your camera, the other two do not. You can wait for 10,000 hours of testing to be completed and that will still be what happens.
-
I got one of them to boot, but I forget which one. The other two locked the camera up in such a way that I had to remove and reinsert the battery, which reaffirmed my fear of lightly tested software.
While you are right to be wary of a new and mostly untested CHDK port, what you saw is exactly what will happen when you load the wrong version of CHDK for your camera. The CHDK version has to match your camera's firmware version or it will lock up, usually requiring a reset by pulling the battery. The version that booted is the one that matches your camera, the other two do not. You can wait for 10,000 hours of testing to be completed and that will still be what happens.
That's what I thought might be the case since it happened with my old Canon P&S too. I don't mind waiting though. This camera is proving to be more than adequate with the stock firmware. :)
-
nafraf - Revision 263: /chdk/..../ixus125_elph110hs
I have come accross this [?] error in:-
Viewport Width Table [1:1]
// viewport width table for each image size
// 0 = 4:3, 1 = 16:9, 2 = 3:2, 3 = 1:1
static long vp_w[4] = { 360, 360, 360, 360 };
~~~~~~~~~~~~~~~~~~~~
Should it be;-
Viewport Width Table [1:1] 360 * 0.75 = 270
static long vp_w[4] = { 360, 360, 360, 270 } ;// { 360, 480, 360, 272 };
H-H
-
nafraf - Revision 263: /chdk/..../ixus125_elph110hs [+ trunk-2617]
RE:- "SD_READONLY_FLAG" Porting Status
Error:- "Memory Card Locked"
In stubs_entry.S
// #define SD_READONLY_FLAG 0x02000000 // Found @0xff413814, levent 0x20a
-=-=-=-=-=-=-=-=-
Search "Locked" (2 hits in 1 file)
C:\CHDK\Ixus125_100e\Ixus125_100e_Strings.txt (2 hits)
~Line 13339:~ 00CFA314 00CFA314 0 Memory card locked
~Line 13572:~ 00CFAF9E 00CFAF9E 0 Unlocked [?]
~~~~~~~~~~~~~~~~~~~~~~~
Search "Locked" (2 hits in 1 file)
C:\CHDK\Ixus125_100d\Strings_Ixus125_100d.txt (2 hits)
~Line 13335:~ 00CFA314 00CFA314 0 Memory card locked
~Line 13568:~ 00CFAF9E 00CFAF9E 0 Unlocked [?]
~~~~~~~~~~~~~~~~~~~~~~~
Search "Locked" (2 hits in 1 file)
C:\CHDK\Ixus125_101a\Ixus-125-100a-Strings.txt (2 hits)
~Line 13337:~ 00CFA314 00CFA314 0 Memory card locked
~Line 13570:~ 00CFAF9E 00CFAF9E 0 Unlocked [?]
-=-=-=-=-=-=-=-=-=-=-=-
Is the "Memory Card Locked" Error something I am do wrong.
or a porting error.
H-H
-
I have come accross this [?] error in:
Viewport Width Table [1:1]
// viewport width table for each image size
// 0 = 4:3, 1 = 16:9, 2 = 3:2, 3 = 1:1
static long vp_w[4] = { 360, 360, 360, 360 };Should it be;-
Viewport Width Table [1:1] 360 * 0.75 = 270
static long vp_w[4] = { 360, 360, 360, 270 } ;// { 360, 480, 360, 272 };
It a pretty normal cut & paste version used in many cameras. Some seem to need the value to change - others don't. I found a bug in the A1200 where the index used in that function (pulled from a propset value) is occasionally out of range resulting in a crash. Didn't track down why - just clamped the value. I could have tested the range instead but the A1200 always uses 360. I guess you just have to test and see what works for your camera.
-
nafraf - Revision 263: /chdk/..../ixus125_elph110hs [+ trunk-2617]
RE:- "SD_READONLY_FLAG" Porting Status
Error:- "Memory Card Locked"
It is a porting error, my guess is that SD_READONLY_FLAG is detected corrected, but there is a bug in ixus125_elph110hs/kbd.c Please test with "nafraf - Revision 265".
-
nafraf - Revision 263: /chdk/..../ixus125_elph110hs [+ trunk-2617]
RE:- "SD_READONLY_FLAG" Porting Status
Error:- "Memory Card Locked"
It is a porting error, my guess is that SD_READONLY_FLAG is detected corrected, but there is a bug in ixus125_elph110hs/kbd.c Please test with "nafraf - Revision 265".
You will also get that error if CHDK fails to load and the camera just proceeds with the normal firmware boot.
-
You will also get that error if CHDK fails to load and the camera just proceeds with the normal firmware boot.
I'm assuming that CHDK boots, because Hardware_Hacker reported it in a previous post. Another tester report (via PM) that he could navigate through CHDK menu but he could not take photos due to "Memory Card Locked" message. It's weird, I have not seen that error before, I'd like to have more details of the bug.
-
There have been occasional reports (IIRC) of some i/o bits using inverted logic. Perhaps the SD_READONLY_FLAG is corrrect but runs inverted from other cameras ?
-
I did get the message about the memory card being locked, but I assumed that was normal due to needing to lock the memory card to make it boot.
-
I did get the message about the memory card being locked, but I assumed that was normal due to needing to lock the memory card to make it boot.
Is CHDK running? Is it possible to navigate through CHDK menu?
-
I was able to navigate through, but it seemed like a lot of things were missing. For example, I didn't see the raw parameters menu. I'll see about running through the three CHDKs again to see which booted and see if I can find out something more.
-
Booted with the a version. The play button brings up the <ALT> thing at the bottom, and FUNC. SET brings me straight to the scripts menu. I can't use the Back option to move up--it just closes the menu. I get a CHDK key cheatsheet if I let it sit long enough.
edit: The menu button brings up the root CHDK menu I expected to see
-
Booted with the a version. The play button brings up the <ALT> thing at the bottom, and FUNC. SET brings me straight to the scripts menu. I can't use the Back option to move up--it just closes the menu.
I'll send you the link to a new version. Lakeroe reported that "Read only" issue was solved with nafraf - Rev 265 :).
What is the firmware version of your camera?
-
Booted with the a version. The play button brings up the <ALT> thing at the bottom, and FUNC. SET brings me straight to the scripts menu. I can't use the Back option to move up--it just closes the menu.
I'll send you the link to a new version. Lakeroe reported that "Read only" issue was solved with nafraf - Rev 265 :).
What is the firmware version of your camera?
101a
-
For example, I didn't see the raw parameters menu. I'll see about running through the three CHDKs again to see which booted and see if I can find out something more.
Booted with the a version. The play button brings up the <ALT> thing at the bottom, and FUNC. SET brings me straight to the scripts menu. I can't use the Back option to move up--it just closes the menu.
Pretty much exactly what you would expect to see & have happen. Much of the CHDK documentation still describes how things worked with the old 1.0.0 version.
-
For example, I didn't see the raw parameters menu. I'll see about running through the three CHDKs again to see which booted and see if I can find out something more.
Booted with the a version. The play button brings up the <ALT> thing at the bottom, and FUNC. SET brings me straight to the scripts menu. I can't use the Back option to move up--it just closes the menu.
Pretty much exactly what you would expect to see & have happen.
I haven't used CHDK since getting the new camera, so I forgot what was normal. :)
-
"SD_READONLY_FLAG" Porting Status
nafraf - Revision 268: /chdk/..../ixus125-100e_elph110hs [compiled with trunk-2619]
BUILD_NUMBER:- 1.2.2619
There is now NO Error for the "Memory Card Locked" problem.
"SD_READONLY"
"physw_status[SD_READONLY_IDX] = physw_status[SD_READONLY_IDX] & ~SD_READONLY_FLAG;"
A Quick test with B:\ChdkPtp-r311 [B:\Win.Xp] and B:\PtpCamGui 2v134 [B:\Win.Xp].
Both Ixus 125-100e's work very well, with my custom drivers, in 95meg Ram-Drive "B:\".
I tried very hard, but failed, to make the cameras crash.
Thanks
H-H
Attached Camera logs
Camera #1 .... Ixus 125_100e ROMLOG-LOG #1
Camera #2 .... Ixus 125_100e ROMLOG-LOG #2
-
nafraf - Revision 268: /chdk/..../ixus125-100e_elph110hs [compiled with trunk-2619]
BUILD_NUMBER:- 1.2.2619
Not sure about these, see Attached #1 & #2
H-H
-
nafraf - Revision 268: /chdk/..../ixus125-100e_elph110hs [compiled with trunk-2619]
BUILD_NUMBER:- 1.2.2619
Not sure about this, see Attached #3
H-H
-
Not sure about these, see Attached #1 & #2
#1 fixed in nafraf-Rev 276.
#2 is a difference in "style", same behavior. Fixed.
Not sure about this, see Attached #3
#3 commented line with error. Fixed.
Thanks, update to nafraf-Rev 276.
Please check the power-up button behavior:
A short tap -> camera turns on in PLAY mode.
Long press -> camera turns on in REC mode.
Some known issues:
* Colors are wrong. If you post a image of palette in REC and PLAY mode would be possible to use LOAD_CUSTOM_COLORS.
* RAW is not working, please test it with Rev 276
-
Hi all,
nafraf - Revision 268: /chdk/..../ixus125-100e_elph110hs [compiled with 1-1-2619]
Ixus125_elph110hs-100e (dryos, #12865): MEMISOSIZE used: 0x3c03e
A little bit more "Quick" testing, see attached.
With this version the two cameras were very hard to crash.
H-H
-
nafraf - Revision 268: /chdk/..../ixus125-100e_elph110hs [compiled with 1-1-2619]
Ixus125_elph110hs-100e (dryos, #12865): MEMISOSIZE used: 0x3c03e
Test of B:\PtpCamGui 2v134, see attached log.
H-H
-
@Hardware_Hacker
Modemap table is not complete, I don't have access to ixus125 to test it.
You find instructions of how to fill modemap table here: http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera (http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera) section platform/<camera>/shooting.c
Another alternative is to use set_capture_mode_canon (http://chdk.wikia.com/wiki/Script_commands) script command to identify the modes.
-
Hi All,
@nafraf - Revision 278: /chdk/..../ixus125-100e_elph110hs [Re-compiled, OK, with 1-2-2619-278]
I Noted, but ignored, a Long list of warnings.
Should I be using a newer version of Gcc ?.
-=+ Ixus125_elph110hs-100e +=-
Please check the power-up button behavior:-
A short tap -> camera turns on in PLAY mode. [A Quick Test = Ok]
Long press -> camera turns on in REC mode. [A Quick Test = Ok]
Some known issues:-
* Colors are wrong. CHDK Logo Orange [But, Not yet Tested]
If you post a image of palette in REC and PLAY mode would be possible to use LOAD_CUSTOM_COLORS.
= ToDo next post.
* RAW is not working, please test it with Rev 276 [A Quick-Quick, Test = "May Be but not Sure"]
~~~~~~~~~~ ? ~~~~~~~~~~~~~
Attached:- Ixus 125-100e & Digi-5 #4
Someting I previously noted, so It may have been changed, Should the The "125-xxx" Reference:-
#1/ Digi5 Property's [?]
#2/ DryOS Rel 47 [?]
#3/ DryOS Rel 50 [?]
Thanks
H-H
-
Not to intrude here, but a bit of attention to the posting conventions of this forum when quoting text would help many of us follow this thread and maybe contribute?
-
Not to intrude here, but a bit of attention to the posting conventions of this forum when quoting text would help many of us follow this thread and maybe contribute?
I agree. To follow Hardware-Hacker's post is not easy.
I Noted, but ignored, a Long list of warnings.
Should I be using a newer version of Gcc ?.
What kind of warnings? Could you post a log?
Please check the power-up button behavior:-
A short tap -> camera turns on in PLAY mode. [A Quick Test = Ok]
Long press -> camera turns on in REC mode. [A Quick Test = Ok]
OK, power-up button tested.
Some known issues:-
* Colors are wrong. CHDK Logo Orange [But, Not yet Tested]
If you post a image of palette in REC and PLAY mode would be possible to use LOAD_CUSTOM_COLORS.
Lakeroe send LCD screen photos to me, please test colors with nafraf- Rev 280
* RAW is not working, please test it with Rev 276 [A Quick-Quick, Test = "May Be but not Sure"]
Please try to create badpixel.com
Attached:- Ixus 125-100e & Digi-5 #4
Someting I previously noted, so It may have been changed, Should the The "125-xxx" Reference:-
#1/ Digi5 Property's [?]
#2/ DryOS Rel 47 [?]
#3/ DryOS Rel 50 [?]
Could you explain this better?
thanks
-
Hi All,
Re: ELPH 110 HS (IXUS 125 HS) Porting Thread & Post #60
Attached Files:-
# 60 Response
IXUS125-100e Testing the Blind Port
thanks
H-H
-
Hi all,
Ixus 125-100e Build N.... TRUNK-1.2.2621.281 ok
Boots ok
Runs ok
TRUNK-1.2.2621.281, Mods, But only to try to find these:-
Ixus 125-xxx Mode Map porting progress -=+ NEWS +=-
Found up to 10 Additional Modes [with Working Icons]
But not yet fully tested
1/ Tv = Icon Ok
2/ Av = Icon Ok
3/ M = "Invisible" Icon Ok
4/ Video Std = Icon Ok
5/ Hi S Burst = Icon Ok
6/ "ToDo" = Icon Ok
7/ U. Water = Icon Ok
8/ Colour A. = Icon Ok
9/ Night.... = Icon Ok
10/ "ToDo" = Icon Ok
-=-=-=-=-
A/ More testing is required for these.
B/ ToDo Cross check Modes against "icons" in Ixus 125 users Manual.pdf
C/ Badpixel.bin, Ran, .... Messages, .... etc. But I did not fully test this.
Logs Attached:-
#1 Ixus 125-281 errors #1
H-H
-
Hi all,
Ixus 125-100e Build N.... TRUNK-1.2.2621.281 ok
More Logs Attached:-
#2 log-Ixus125_elph110hs-100e-281 #1
H-H
-
Hello.
I haven't visit this forum for some time now since my last post here (http://chdk.setepontos.com/index.php?topic=8085.msg97420#msg97420)
Again: I'm willing to help with testing. So please tell me what I have to do.
The firmware of my camera is 101a.
Cheers
-
@HardwareHacker
In your logfile (http://chdk.setepontos.com/index.php?action=dlattach;topic=8085.0;attach=7946) I found three messages, but they don't seem to be problem.
-> signatures_vxworks.h
CAUTION! Signature generation is turned off!
If you check tools/Makefile, you will see the cause of warnings.
It depends on OPT_GEN_SIGS value, defined in buildconf.inc. But you are compiling for dryos camera, I don't see problem.
-> signatures_dryos.h
CAUTION! Signature generation is turned off!
If you want to remove this.. OPT_GEN_SIGS=1 should solve it.
-> stubs_entry.S
CAUTION! 'stubs_entry.S' is not updated due to target firmware binary not found!
It seems that you don't have platform/ixus125_elph110hs/sub/100e/PRIMARY.BIN
Then, stubs_entry.S can't be updated
-
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FRRiJpMy.png&hash=0b0528ae6167da42a4d8f1d499ccd511)
This black bar appears in all DNG files. The camera crops it out when producing the JPG file, so I'm assuming the engineers at Canon omitted a handful of pixels in the sensor on purpose. It appears in UFRaw and RawTherapee, so I don't think it's the software. Does anyone have insights on this?
edit: I found a thread on an identical phenomenon with another camera: http://forums.dpreview.com/forums/thread/2878810 (http://forums.dpreview.com/forums/thread/2878810)
-
Again: I'm willing to help with testing. So please tell me what I have to do.
I sent you a PM with the link to CHDK for IXUS125 101a.
To load it, it is necessary to use bootable sd card method (http://chdk.wikia.com/wiki/Prepare_your_SD_card#Bootable_SD_Card_Method).
That version has been tested by MKR, something to do/to test:
- Test Video quality override
- Test Long Exposure
- Complete Modemap table
- Detect led_table[] indexes.
Thanks
Please test and report.
-
Hello,
I managed now to boot.
I will try the first two points in the next fours or tomorrow.
However I do not know what the last two point are... Some hint please?
Cheers
-
However I do not know what the last two point are... Some hint please?
In source code, we have these warnings related to modemap table:
// Check of modemap from 'platform/CAMERA/shooting.c':
// Firmware modemap table found @ff0841bc -> ff080a6c -> ff1ca4f0 -> ff333640 -> ff5e8cf0
// Mode 33329 in firmware but not in current modemap
// Mode 33332 in firmware but not in current modemap
// Mode 33313 in firmware but not in current modemap
// Mode 33298 in firmware but not in current modemap
// Mode 32796 in firmware but not in current modemap
// Mode 32776 in firmware but not in current modemap
There are two option to detect those values:
* Follow instructions here: http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera (http://chdk.wikia.com/wiki/Adding_support_for_a_new_camera) section modemap[] in platform/<camera>/shooting.c.
*Use set_capture_mode_canon (http://chdk.wikia.com/wiki/Script_commands) script command to identify the modes. You can use script running in your camera, or execute command from using chdkptp and see what happens :)
Something like this:
$chdkptp -i -c
connected: Canon PowerShot xxxxxxx
con> rec
con 1> =set_capture_mode_canon(32796)
32796 is the mode to test.
-
Hi all,
Ixus 125-100e Build N.... TRUNK-1.2.2621.281 ok
Boots ok
Runs ok
Camera #1 NO CRASHES, untill the Battery died.
Camera #2 NO CRASHES, untill the Battery died.
TRUNK-1.2.2621.281, Mods, But only to test these:-
Ixus 125-100e Porting Progress News UpDate Produced: 3/13/2013 3:17:15 PM [Au]
ParamDmp - Cam#2.log
RomLog - Cam#2.log
By H-H
-
Hi all,
Ixus 125-100e Build N.... TRUNK-1.2.2621.281 ok
Boots ok
Runs ok
Camera #1 NO CRASHES, untill the Battery died.
Camera #2 NO CRASHES, untill the Battery died.
TRUNK-1.2.2621.281, Mods, But only to test these:-
Ixus 125-100e Porting Progress News UpDate Produced: 3/13/2013 3:17:15 PM [Au]
UartRTST - Cam#2.log >> 71
ChdkPtP-0 Cam #1.png >> 71
H-H
-
Hi all,
Ixus 125-100e Build N.... TRUNK-1.2.2621.281 ok
Boots ok
Runs ok
Camera #1 NO CRASHES, untill the Battery died.
Camera #2 NO CRASHES, untill the Battery died.
TRUNK-1.2.2621.281, Mods, But only to test these:-
Ixus 125-100e Porting Progress News UpDate Produced: 3/13/2013 3:17:15 PM [Au]
ChdkPtP-Auto Cam #1.png >> 72
ChdkPtP-Av Cam #1.png >> 72
H-H
-
Continued:-
ChdkPtP-"M" Cam #1.png >> 73
ChdkPtP-S_FE Cam #1.png >> 73
H-H
-
Continued:-
ChdkPtP-S_S_V Cam #1.png >> 74
ChdkPtP-Tv Cam #1.png >> 74
H-H
-
# 70 continued:-
ChdkPtP-V_S Cam #1.png >> 75
Desk Top for UbCd4Win Ixus 125-100e Cam#2 ChdkPtp #0.png >> 75
H-H
-
# 70 Continued:-
Desk Top for UbCd4Win Ixus 125-100e Cam#2 ChdkPtp #1.png >> 76
Desk Top for UbCd4Win Ixus 125-100e Cam#2 Hardware Test.png >> 76
H-H
-
# 70 continued;-
Hklm_Ccs_Serv1 LibUsb1 Cam #2.png >> 77
ToDo # 6.png >> 77
H-H
-
# 70 continued;-
ToDo # 9.png >> 78
Auto_FlatBatt_+_Close_Up.png >> 78
By H-H [end]
-
Hi All,
Ixus 125-100e Build N.... TRUNK-1.2.2621.288 compile ok
Boots ok
Runs ok
Demo Shoots, most Ok
Will have to try to find new MM values for a few of these that are wrong.
Found a few new things. [ToDo]
Camera #1 NO CRASHES, untill the Battery died.
Summary and Test results are below
#70 to #78 and Mode Map testing Continued:-
Mode Map Demos #2 Produced: 3/14/2013 5:22:49 PM [Au]
G:\I148
A Simple...Ixus 125...trunk...Trunk-2621...camera_list.csv
A Simple - Ixus 125 Camera_List-csv.png
H-H
-
#70 to #78 and Mode Map testing Continued:-
ChdkPtP-S_F Cam #0.png
ChdkPtP-S_S_V Cam #0.png
H-H
-
#70 to #78 and Mode Map testing Continued:-
ChdkPtP-Shoot_Av_Demo Cam #0.png
ChdkPtP-Shoot_FireWork_Demo Cam #0.png
H-H
-
#70 to #78 and Mode Map testing Continued:-
ChdkPtP-Shoot_H_S_B_Demo 2 Cam #0.png
ChdkPtP-Shoot_H_S_B_Demo Cam #0.png
H-H
-
#70 to #78 and Mode Map testing Continued:-
ChdkPtP-Shoot_LandScape_Demo Cam #0.png
ChdkPtP-Shoot_''M''_Demo Cam #0.png
-
#70 to #78 and Mode Map testing Continued:-
ChdkPtP-Shoot_MonoChrome_Demo Cam #0.png
ChdkPtP-Shoot_P_Demo Cam #0.png
H-H
-
#70 to #78 and Mode Map testing Continued:-
ChdkPtP-Shoot_S_B_I_Demo Cam #0.png
ChdkPtP-Shoot_S_FE_Demo Cam #0.png
H-H
-
#70 to #78 and Mode Map testing Continued:-
ChdkPtP-Shoot_S_S_V_Demo Cam #0.png
ChdkPtP-Shoot_S_SF_Demo Cam #0.png
-
#70 to #78 and Mode Map testing Continued:-
ChdkPtP-Shoot_S_T_C_Demo Cam #0.png
ChdkPtP-Shoot_Tv_Demo Cam #0.png
H-H
-
#70 to #78 and Mode Map testing Continued:-
ChdkPtP-Shoot_V_M_D_Demo Cam #0.png
ChdkPtP-Shoot_V_S_S_Demo Cam #0.png
H-H
-
#70 to #78 and Mode Map testing Continued:-
PlayBack Button.txt
---+= End of Testing =+----
Mode Map testing is more complicated than I originaly Thought.
Now I understand why most camera's M_Maps seem to be a work in progress !!
Next "Demo" series, if any, will be in a different format. [more compact maybe]
Coments Anybody ?
H-H
-
Next "Demo" series, if any, will be in a different format. [more compact maybe]
Coments Anybody ?
More compact report please...
setmode.lua script test modes from modemap table, running it interactively you can confirm each of them.
Modemap table has not been finished, you can find missing values using chdkptp. Read Reply 69 (http://chdk.setepontos.com/index.php?topic=8085.msg97809#msg97809) of this thread.
You suggested some changes to camera_list.csv. That file is the list of supported cameras. Ixus125 should be added, but you can't delete existing entries.
-
Hi All,
Ixus 125-100e Build N.... TRUNK-1.2.2621.291a-full compile ok
Boots ok
Runs ok
Will try to test AF led next. [Wip ...&... ToDo]
Will have to try to find new MM values for a few of these that are wrong.
Found a few new things. [Wip ...&... ToDo]
A short test only but Camera #1 NO CRASHES.
Attached:-
ROMLOG #1.LOG
ROMLOG #2.LOG
Continued:- SetMode.log
H-H
-
Hi All,
@Ixus 125-100e Build N.... TRUNK-1.2.2621.291-d compile ok
@17/03/2013, TRUNK-1.2.2621.291-d; shooting.c:-
Note:- "Up to 32 Sceens"
const CapturemodeMap modemap[] = {
{ MODE_AUTO, 32768 }, //
{ MODE_P, 32772 }, //
{ MODE_DIGITAL_IS, 33338 }, // H-H Test Only [NEW]
// { MODE_NIGHT_SCENE, 33326 }, //
{ MODE_LANDSCAPE, 16399 }, // H-H Test Only [W.i.p.]
// { MODE_EASY, 33314 }, //
{ MODE_TV, 32771 }, // H-H Test Ok
{ MODE_AV, 32770 }, // H-H Test Ok
{ MODE_M, 32769 }, // H-H Test Ok
// { MODE_LIVE, 33336 }, // H-H Test Failed
{ MODE_DISCREET, 32821 }, // H-H Test Ok [NEW]
// SCN Modes [Max=32]
{ MODE_SCN_HIGHSPEED_BURST, 33288 }, // H-H Test Only
// { MODE_SCN_SNOW, 32793 }, //
{ MODE_SCN_LOWLIGHT, 32805 }, //
{ MODE_SCN_LONG_SHUTTER, 32774 }, // H-H Test Only
{ MODE_SCN_PORTRAIT, 32785 }, // H-H Test Only
{ MODE_SCN_BEST_IMAGE, 33289 }, // H-H Test Only
// { MODE_SCN_STITCH, 33293 }, //
// { MODE_SCN_FACE_SELF_TIMER, 33295 }, //
// { MODE_SCN_SUPER_VIVID, 33322 }, //
{ MODE_SCN_SMART_SHUTTER, 16938 }, // H-H Test Only
{ MODE_SCN_FACE_SELF_TIMER, 16937 }, // H-H Test Only
{ MODE_SCN_WINK_SELF_TIMER, 16939 }, // H-H Test Only
// { MODE_SCN_POSTER_EFFECT, 33323 }, //
// { MODE_SCN_FACE_SELF_TIMER, 33324 }, //
{ MODE_SCN_FOLIAGE, 16406 }, // H-H Test Only
{ MODE_SCN_COLOR_ACCENT, 8734 }, // H-H Test Only
{ MODE_SCN_COLOR_SWAP, 8735 }, //
// { MODE_SCN_NIGHT_SNAPSHOT, 33325 }, //
// { MODE_SCN_FISHEYE, 33327 }, //
// { MODE_SCN_MINIATURE, 33328 }, //
// { MODE_xxxx, 33329 }, //
// { MODE_SCN_TOY_CAMERA, 33329 }, // H-H Test Only
{ MODE_SCN_SOFTFOCUS, 8756 }, // H-H Test Only
// { MODE_SCN_MONOCHROME, 33332 }, // H-H Test Only
// { MODE_VIDEO_MOVIE_DIGEST, 33313 }, // H-H Test Only
// { MODE_SCN_SUPER_VIVID, 33298 }, // H-H Test Only
// { MODE_SCN_FISHEYE, 32796 }, // H-H Test Only
// { MODE_SCN_FIREWORK, 32776 }, // H-H Test Only
// { MODE_SCN_FIREWORK, 32795 }, // H-H Test Only
// { MODE_SCN_TOY_CAMERA, 33331 }, //
// { MODE_SCN_MONOCHROME, 33334 }, //
// VIDEO Modes
// { MODE_VIDEO_SPEED, 2626 }, // Time Lapse in Sx230hs
{ MODE_VIDEO_SUPER_SLOW, 2631 }, //
// { MODE_VIDEO_IFRAME_MOVIE, 2633 }, //
// { MODE_VIDEO_STD, 2622 }, // H-H Test Ok
// { MODE_VIDEO_MOVIE_DIGEST, 33337 }, //
{ MODE_VIDEO_SUPER_SLOW, 2627 }, // H-H Test Only
Boots ok
Runs ok
"Will try to test AF led next. [Wip ...&... ToDo]"
Testing:- "¦Autofocus LED [on] 0xC0220164" ... enabled for 1.2.2621.291-d.
"My_Blinker..." .... compile errors, ... disabled for 1.2.2621.291-d.
Af Led Flashes, If turned on in Canon's menu. Test Method CHDK PtP.
NO Af Led Flashes, If turned off in Canon's menu. Test Method CHDK PtP.
Will have to try to find new MM values for a few of these that are wrong.
Mode_Map News 2 New modes now working but untested:-
#1 { MODE_DIGITAL_IS, 33338 }, // H-H Test Only [NEW]
#2 { MODE_DISCREET, 32821 }, // H-H Test Ok [NEW]
#3 { MODE_TV, 32771 }, // H-H Test Ok [ N.D. Filter, f8, "Click Sound"]
#4 { MODE_SCN_SOFTFOCUS, 8756 }, // H-H Test Only [?, no Icon]
Found a few new things. [Wip ...&... ToDo]
A short test only but Camera #1 One CRASH.
Attached:-
ROMLOG #291d.LOG
H-H
-
Hello Hardware_Hacker,
I found modemap entries with duplicated names in your report:
{ MODE_SCN_TOY_CAMERA, 33329 }, // H-H Test Only
{ MODE_SCN_TOY_CAMERA, 33331 }, //
{ MODE_SCN_MONOCHROME, 33332 }, // H-H Test Only
{ MODE_SCN_MONOCHROME, 33334 }, //
{ MODE_VIDEO_MOVIE_DIGEST, 33313 }, // H-H Test Only
{ MODE_VIDEO_MOVIE_DIGEST, 33337 }, //
{ MODE_SCN_SUPER_VIVID, 33298 }, // H-H Test Only
{ MODE_SCN_SUPER_VIVID, 33322 }, //
{ MODE_SCN_FISHEYE, 32796 }, // H-H Test Only
{ MODE_SCN_FISHEYE, 33327 }, //
Are you using chdkptp for test? I think it is the easiest method to check missing modemap entries.
-
Hi Nafraf,
Are you using chdkptp for test?
I think it is the easiest method to check missing modemap entries.
Yes.
"ChdkPtp-r311" =set_capture_mode_canon(xxxxx)
I also tried a few random entrys.
I Found a new Mode:-
// "Crash Mode"
see attached
H-H
-
Hello Hardware-Hacker
I also tried a few random entrys.
I Found a new Mode:-
// "Crash Mode"
Modemap numbers are extracted from camera firmware, if you test with other numbers, camera crash.
Modemap table is almost complete with your tests. I updated table.
Is this right?
{ MODE_SCN_SMART_SHUTTER, 33324 },
{ MODE_SMART_SHUTTER, 33325 },
entry 33326 remains commented because it crashes during your tests.
-
Hi All,
Ixus 125-100e Build N.... TRUNK-1.2.2641.291 c compile ok
Produced: 3/19/2013
Boots ok
Runs ok
Next I will try to test AF led. [Wip ...&... ToDo]
Mode-Map Demos & Logs Attached :-
Ixus 125-100e ROMLOG T2641.291c.log
DEMO-Shooting.c
[continued]
H-H
-
[ Post #96 ;Continued] Attached :-
Mode Map - Demo #1.png
H-H
-
[ Post #96 ;Continued] Attached :-
Mode Map - Demo #2.png
H-H
-
[ Post #96; Continued] Attached :-
Mode Map - Demo #3.png
-=+ End of Demos +=-
(Next time I will trim the files so as not to exceed the 1.5m limit)
H-H
-
Hi all,
Source Code @ Trunk2650+ N...Svn305, was added about 30 hours ago, Ixus 125 Ports from nafraf and philmoz.
The "Alpha Ixus 125_100e" version boots Ok.
and runs Ok,
BUT, no other testing was done.
CHDK-SVN AutoBuild Download has now also added the Alpha Ixus 125 Ports.
This is the development version of CHDK which is considered "Unstable"
Complete zips contain additional files like scipts, grids, language files, RBF fonts and curves
Small zips contain the bare DISKBOOT.bin and PS.FIR/PS.FI2
@ http://mighty-hoernsche.de/trunk/ (http://mighty-hoernsche.de/trunk/)
This version boots Ok for "Alpha Ixus 125_100e"
and runs Ok,
The PS.FI2 version also boots Ok for "Alpha Ixus 125_100e"
and runs Ok,
BUT, no other testing was done.
H-H
-
Compiled version for IXUS125 100d is in attachment, to load it, it is necessary to use bootable sd card method (http://chdk.wikia.com/wiki/Prepare_your_SD_card#Bootable_SD_Card_Method).
This is a version under development, Firmware update method does not work
Please test it and report.
First test: http://chdk.wikia.com/wiki/Testing (http://chdk.wikia.com/wiki/Testing)
-
Compiled version for IXUS125 100d is in attachment, to load it, it is necessary to use bootable sd card method (http://chdk.wikia.com/wiki/Prepare_your_SD_card#Bootable_SD_Card_Method).
This is a version under development, Firmware update method does not work
Please test it and report.
First test: http://chdk.wikia.com/wiki/Testing (http://chdk.wikia.com/wiki/Testing)
llibtst.lua was successful, setmode.lua had three errors. Log files attached.
-
Trying log files again - think I ejected the card before posting message.
-
llibtst.lua was successful, setmode.lua had three errors. Log files attached.
Thanks for testing. modemap table has not been fully ported for this camera model.
Please try to use chdkptp to run set_capture_mode_canon and see what happens with modes that failed running set_mode.lua
check reply 69 (http://chdk.setepontos.com/index.php?topic=8085.msg97809#msg97809) of this thread.
-
Hi all,
I'd like to help with this port for FW 101a. I have very little coding skills (matlab,arduino/processing). I'm trying to get set up like H-H so that I can give good feedback to help this along. I'll be receiving an AC power supply in a few days so I won't be time-limited to battery life for testing purposes. I've run ACID and WICK and have gotten the recommended, auto-downloaded "ixus125_elph110hs-101a" stable (alpha?) to run on the camera. It boots past the intro/version screen very fast. The normal OSD is overlapped by the chdk osd and the menu's bug out a little with the AF box wandering around the screen. I haven't tried any scripts yet and I just got chdkptp to show the camera display but can't really make it do anything (picture attached (if I can upload yet)). I've looked at the "adding support for a new camera" page and the testing page but this is all new to me.
nafraf, I hope you and the others are still willing to work on this with me (and guide me a little along the way).
-DGT
-
Hi, welcome to forum.
I've run ACID and WICK and have gotten the recommended, auto-downloaded "ixus125_elph110hs-101a" stable (alpha?) to run on the camera. It boots past the intro/version screen very fast. The normal OSD is overlapped by the chdk osd and the menu's bug out a little with the AF box wandering around the screen.
Some comments about OSD and AF box here: http://chdk.setepontos.com/index.php?topic=8450.msg96390#msg96390 (http://chdk.setepontos.com/index.php?topic=8450.msg96390#msg96390)
Basic tests were done to the port, if you want to run them again: chdk.wikia.com/wiki/Testing
LED indexes for led_table are not verified. Comments about LED tests are available here (http://chdk.setepontos.com/index.php?topic=9443.msg97577#msg97577)
I haven't tried any scripts yet and I just got chdkptp to show the camera display but can't really make it do anything (picture attached (if I can upload yet)). I've looked at the "adding support for a new camera" page and the testing page but this is all new to me.
Using chdkptp, you press on REC button to go to shoot mode, after that you can use shoot button to take photos.
-
Hi all, I'm babybug, a newbie !
I've been followed this thread for somtimes, waiting for the CHDK 100d for my Elph 110 HS, but it's been nearly a year without completion! I've tried other version (100e and 101a) on my camera. But after click OK on the Firmware Update screen, the camera just goes black, no CHDK logo appears, so I guess they won't work!
Any advice on what I should do will be greatly appreciated. Thanks!
By the way, is the ALT key for Elph 110 HS is the DISP button?
UPDATE: Please disregard my above request, I've found nafraf's compiled version 100d (on the previous page) and run it successfully on my camera. Thank you nafraf.
Also, the ALT key is the PLAY button, not the DISP
-
@nafraf : did you see this : http://chdk.setepontos.com/index.php?topic=9257.msg100043#msg100043 (http://chdk.setepontos.com/index.php?topic=9257.msg100043#msg100043) ??
-
@nafraf : did you see this : http://chdk.setepontos.com/index.php?topic=9257.msg100043#msg100043 (http://chdk.setepontos.com/index.php?topic=9257.msg100043#msg100043) ??
I checked, only 101a is affected as philmoz noted. Patch and patched version is attached. But, is there any volunteer to test it? :-[
-
Hi, brand new to the CHDK Boards but not to CHDK. Hopefully I can help out as much as possible here.
I have two IXUS125's that I plan to use for balloon and kite aerial photography and I'd like to get CHDK running smoothly on them.
Thank you nafraf and others for all of the work that has been done thus far. I've downloaded your latest patched version for my 101a and will give it a shot. I'll post anything that may be useful for future development. Let me know if there is anything else I can do on my end.
-
Thank you nafraf and others for all of the work that has been done thus far. I've downloaded your latest patched version for my 101a and will give it a shot. I'll post anything that may be useful for future development. Let me know if there is anything else I can do on my end.
Hi, please test Dark frame subtraction on and off.
-
So I'm having an interesting problem. I downloaded the patched zip. Extracted it to SD card and when I start the camera (via the play button of course) I do not actually have the option of updating the firmware using the Canon menus. I formatted the card and installed the alpha version of CHDK instead and was able to flash it and make the card bootable. So I formatted the card again and tried the zip from your previous post and still no firmware update option.
Any suggestions? Is the Alpha version different from your upload?
-
So I'm having an interesting problem. I downloaded the patched zip. Extracted it to SD card and when I start the camera (via the play button of course) I do not actually have the option of updating the firmware using the Canon menus. I formatted the card and installed the alpha version of CHDK instead and was able to flash it and make the card bootable. So I formatted the card again and tried the zip from your previous post and still no firmware update option.
Any suggestions? Is the Alpha version different from your upload?
Typically, CHDK versions posted on the forum don't have the ability to boot via the "firmware update method". Its an extra step in the build requiring an encryption file that most devs just skip (as autobooting is so much easier to use in the first place).
If there is no ps.fi2 file in the root of the SD card then you will not be able to use the "firmware update method".
-
Ok, so after my momentary lapse in common sense with respect to loading CHDK I have it loaded. I have one issue that may be problematic for testing.
1. Prior to taking RAW images and testing removal of dark frame removal on/off I tried creating the badpixel.bin file. I could not get it to work after trying 6 or 7 times. I also could not get badpixel.bin to work on the alpha version of CHDK so I'm not sure where to go with this issue. I'm also not sure whether this will influence dark frame removal on/off testing.
2. Despite issue #1, I tried dark frame removal on and off and both "worked" that is there was no crash when I took the pictures. But again I do not know whether issue #1 has influenced this test.
Please advise with respect to issue #1. What other information can I provide to help.
-
1. Prior to taking RAW images and testing removal of dark frame removal on/off I tried creating the badpixel.bin file. I could not get it to work after trying 6 or 7 times. I also could not get badpixel.bin to work on the alpha version of CHDK so I'm not sure where to go with this issue. I'm also not sure whether this will influence dark frame removal on/off testing.
Some people have reported better results getting badpixel.bin to work if they hold the camera very still while pointing at a dark area (i.e. in a darkened room). It might also help if you let the camera run for 5 minutes so that internal temperatures stablize prior to running the bad pixel create menu option.
Otherwise, you can use DNG in 1.3 mode - which doesn't require the file (or do bad pixel correction for you).
2. Despite issue #1, I tried dark frame removal on and off and both "worked" that is there was no crash when I took the pictures. But again I do not know whether issue #1 has influenced this test.
Issue #1 would not matter - I assume you ran the test in DNG 1.3 mode or just used RAW without DNG enabled? If the "test" worked, and you used a long exposure time >2 seconds (like 15 seconds), then with Dark Frame Subtraction enabled you should have noticed a "Busy" message that persisted after the 15 second exposure completed for an additional length of time equal to the original exposure time (eg 15 seconds). With Dard Frame Subtraction "off" that extra "Busy" delay should not have happened.
-
Thanks for the clarifications waterwingz. See below:
1. Prior to taking RAW images and testing removal of dark frame removal on/off I tried creating the badpixel.bin file. I could not get it to work after trying 6 or 7 times. I also could not get badpixel.bin to work on the alpha version of CHDK so I'm not sure where to go with this issue. I'm also not sure whether this will influence dark frame removal on/off testing.
Some people have reported better results getting badpixel.bin to work if they hold the camera very still while pointing at a dark area (i.e. in a darkened room). It might also help if you let the camera run for 5 minutes so that internal temperatures stablize prior to running the bad pixel create menu option.
Otherwise, you can use DNG in 1.3 mode - which doesn't require the file (or do bad pixel correction for you).
Ok, so I did have the camera stable in a dark-ish room, lit poorly at least and flash off. However DNG was in mode 1.3. However I did not know that I did not need to worry about the badpixel.bin with DNG in 1.3 mode. I've read a tremendous amount of material on the CHDK site but must have missed that nugget of information. Thanks.
2. Despite issue #1, I tried dark frame removal on and off and both "worked" that is there was no crash when I took the pictures. But again I do not know whether issue #1 has influenced this test.
Issue #1 would not matter - I assume you ran the test in DNG 1.3 mode or just used RAW without DNG enabled? If the "test" worked, and you used a long exposure time >2 seconds (like 15 seconds), then with Dark Frame Subtraction enabled you should have noticed a "Busy" message that persisted after the 15 second exposure completed for an additional length of time equal to the original exposure time (eg 15 seconds). With Dard Frame Subtraction "off" that extra "Busy" delay should not have happened.
I did run the test in DNG mode. I believe that I did not run a long enough exposure time since it was only about 2 seconds however the "busy" message did persist for about 2 seconds after. I will rerun the tests with a much longer time to confirm that this feature is working.
-
I did run the test in DNG mode. I believe that I did not run a long enough exposure time since it was only about 2 seconds however the "busy" message did persist for about 2 seconds after. I will rerun the tests with a much longer time to confirm that this feature is working.
What you are trying to confirm is that CHDK can turn Dark Frame Subtraction OFF on your camera during long exposures. The Canon firmware has it ON by default for those long exposures.
So if you set the CHDK Dark Frame Subtraction menu item to AUTO or ON with a 15 second exposure, you should see the complete shot take 30 seconds ( 15 for the shot and 15 for the dark frame ). If you set it to OFF in the CHDK menu, the same shot should only take 15 seconds to complete.
The test is to confirm that CHDK actually tricks the camera into not taking the extra dark frame with every long exposure.
-
I have completed several tests of the Darkframe subtraction both on and off and it is functioning as it should as far as I can tell. Darkframe subtraction off with 5, 10 and 15 second exposures only took the length of the exposure while Darkframe subtraction on with the same time exposures took 10, 20 and 30 seconds to complete respectively. No crashes of CHDK during my testing.
My general experience thusfar with both the forum version of CHDK and the Alpha version of CHDK have been positive.
Anything else need testing?
-
Thank you very much for your great work!
-
Hi, i'm new to this forum, i'd like to know the current development state for this camera, and more specifically for the 100d firmware (wich my camera has), i saw some posts behind a build for it, apparently it needs testing, i'm willing to test, what are the tools needed for that? to make useful error logs and stuff? whats working? what exactly needs testing? thank you for your answers and excuse my noobishness
-
Hi, i'm new to this forum, i'd like to know the current development state for this camera, and more specifically for the 100d firmware (wich my camera has), i saw some posts behind a build for it, apparently it needs testing, i'm willing to test, what are the tools needed for that? to make useful error logs and stuff? whats working? what exactly needs testing? thank you for your answers and excuse my noobishness
Source code is ready for test, I can send you a compiled version if you want to test it and report.
If you have programming experience and want to compile the code by yourself, check and fix the code, you can start here: http://chdk.wikia.com/wiki/For_Developers (http://chdk.wikia.com/wiki/For_Developers)
If you want to test it as user, you can start reading CHDK manual:
http://chdk.wikia.com/wiki/CHDK_User_Manual (http://chdk.wikia.com/wiki/CHDK_User_Manual)
Some basic scripts for test: http://chdk.wikia.com/wiki/Testing (http://chdk.wikia.com/wiki/Testing)
Photo overrides, video overrides, remote control, scripts should be working. Some things in to do list, taken from notes.txt (http://tools.assembla.com/svn/chdk/trunk/platform/ixus125_elph110hs/notes.txt):
- EXT_VIDEO_TIME not implemented
- Modemap table is not complete
- CAM_ACTIVE_AREA_?? not calibrated
- camera_set_led(): led_table[] indexes not found.
- Tables in shooting.c were not verified
-
i'd like a compiled version, i do have some programing experience, when i come at home i can read those links you send me, it would be great to have this software in a more stable state, i guess you're the one who ports this version but don't own the 100d firmware camera right? tnx for your answer
-
i'd like a compiled version, i do have some programing experience
OK. I sent you a PM with the link for download.
i guess you're the one who ports this version but don't own the 100d firmware camera right? tnx for your answer
I don't have any IXUS 125, it was a blind port.
-
Finally got the time to get it running, seems to run fine, tested some raw shooting and auto bracketing, soon i'l get to test the stuff from the notes and report back.
-
Can anyone provide me with a CHDK compiled version for ELPH 110HS V100d?
I Know it is a test version.
Thanks,
Carlos
-
Can anyone provide me with a CHDK compiled version for ELPH 110HS V100d?
Ixus 125HS 100d 1.2.0-r2856
-
Thank you Blackhole, worked fine!
carlos
-
Hi, I'm new to this forum. I got to know CHDK when I was googling how to remotely control a compact camera and see the liveview using a pc. I know DSLR does this, but sometimes it's not convenient to bring a DSLR, so I'm looking for a compact camera solution.
After research, I think ixus 125hs is a decent one, because many other cameras supported by CHDK are already discontinued. From one of the attached photos I can see that remote display in chdkptp works with firmware 100e. However, I don't know whether it works on firmware 101a, which is probably the current version on market. Can anyone test if it works? If not, I think I can help because I'm a computer science student. Thanks.
-
However, I don't know whether it works on firmware 101a, which is probably the current version on market. Can anyone test if it works? If not, I think I can help because I'm a computer science student. Thanks.
In general, if live view works correctly on one firmware version it should work on the others. If it doesn't, the bug will probably be something that we can fix relatively easily.
Live view should work to some degree on all CHDK supported cameras. The things that are most likely to be broken are
1) colors when displaying the canon UI may be wrong.
2) live view may not be the full frame buffer, or may not adjust for modes that change the viewport dimensions. In some cases it might be totally garbled, but this should be pretty rare.
In both cases, fixing is usually a matter of implementing some fairly simple functions and possibly finding some addresses in the firmware.
-
Hi,
I used the 100d Version posted some posts ago but this wouldn't work on my 16GB card so I tried it with the partitioning trick. So I moved the DISKBOOT.bin to the FAT16 partition (3,5GB) and the rest to the bigger FAT32 partition. I locked the sdcard as described in the wiki and CHDK loads. The problem is that in the smaller partition a CHDK folder is created but no scripts are copied and all new pictures are saved on this partition. But that's not how it's supposed to be. Does anyone know a workaround or a fix for this?
kind regards
-
I used the 100d Version posted some posts ago but this wouldn't work on my 16GB card so I tried it with the partitioning trick.
The ixus 125 is a DrOS r50 camera, so it supports booting from a FAT32. If you couldn't get it to boot on FAT32, your card was not set up correctly.
CHDK does not support multiple partitions on cameras that are able to boot directly from FAT32.
-
However, I don't know whether it works on firmware 101a, which is probably the current version on market. Can anyone test if it works? If not, I think I can help because I'm a computer science student. Thanks.
In general, if live view works correctly on one firmware version it should work on the others. If it doesn't, the bug will probably be something that we can fix relatively easily.
Live view should work to some degree on all CHDK supported cameras. The things that are most likely to be broken are
1) colors when displaying the canon UI may be wrong.
2) live view may not be the full frame buffer, or may not adjust for modes that change the viewport dimensions. In some cases it might be totally garbled, but this should be pretty rare.
In both cases, fixing is usually a matter of implementing some fairly simple functions and possibly finding some addresses in the firmware.
So fixing such bugs is just looking for correct function addresses and image offsets. Then I don't need to worry about potential problems with liveview. Thanks.
-
It worked fine after formatting again to one partition FAT32, copied all data to it and made it bootable with eoscard.exe
Worked flawlessly!
Thank you guys for the port!
-
anyone have a full size iso 100 dng / jpeg online from the alpha chdk for the 125hs?
Thanks in advance
-
Hello,
first of all many thanks for porting to the IXUS 125. I'm using CHDK since three weeks and with one exception everything seems to work properly.
The issue I have is the dng images. Here I have in the left area of the image a 80 pixel width black area. In addition there is
- a ~ 10 pixel width red line inside the black area
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fs18.postimg.org%2Fyg0o9gfc9%2FCRW_0041.jpg&hash=501191c649573973e7a6309dd153abbd) - or I have a shadow in the upper left and lower left corner of the image
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fs24.postimg.org%2Fdn5gwoo1h%2FCRW_0061.jpg&hash=f17197718f88931771784e492753eba0)
Both images are showing 800x600 pixel copied from the lower left corner of the total DNG image, which has a resolution of 4624x3460.
The corresponding JPEG images are fine, but have a slightly different resolution of 4608x3456. Also it seems like there is an offset of the DNG image somehow compared to the JPEG.
My version details:
- CHDK-Ver: CHDK-DE 1.2.0
- Revision: 2999
- Date: Aug 2 2013
- Camera: ixus125_elph110hs
- FW-Vers: 101a
- Compiler: GCC 4.7.0
- DNG-Versionen: 1.1 or 1.3 (both are affected)
- Raw-Buffer active or not (both are affected)
People at the German board (http://forum.chdk-treff.de/viewtopic.php?f=6&t=3169) proposed to post the issue here. Maybe you have a clue. I'm happy to support any investigation.
Thanks and Regards,
Daniel
-
Looks like the active area is not defined correctly. If you can upload a full DNG somewhere, we can fix it.
The image in the dng doesn't matter much, but it should be a fairly bright exposure so we can tell where the actual image data ends.
-
Hi,
thanks for your feedback. I uploaded a DNG.
Please find it here:
http://www.file-upload.net/download-7969481/20130803-CRW_0041.DNG.html (http://www.file-upload.net/download-7969481/20130803-CRW_0041.DNG.html)
Thanks and Regards,
Daniel
-
Here's a test build for 101a.
-
Hello,
I bought the ELPH 110 HS recently. I previously used CHDK on an older Canon to good effect.
This time around I cannot get the ELPH 110 HS to even boot CHDK.
I tried all the various versions of the CHDK firmware. None of them work.
I do not know precisely which Canon firmware I have. I cannot find a menu item for learning that.
However the photo files themselves contain a string indicating firmware 1.01.
Can anyone assist me in getting CHDK to boot on the camera?
The EXIF says:
IMG:PowerShot ELPH 110 HS JPEG
Firmware Version 1.01
Thanks.
-
Hello,
I bought the ELPH 110 HS recently. I previously used CHDK on an older Canon to good effect.
This time around I cannot get the ELPH 110 HS to even boot CHDK.
I tried all the various versions of the CHDK firmware. None of them work.
I do not know precisely which Canon firmware I have. I cannot find a menu item for learning that.
However the photo files themselves contain a string indicating firmware 1.01.
Can anyone assist me in getting CHDK to boot on the camera?
The EXIF says:
IMG:PowerShot ELPH 110 HS JPEG
Firmware Version 1.01
Thanks.
You might want to start by reading and understanding this page : http://chdk.wikia.com/wiki/Prepare_your_SD_card (http://chdk.wikia.com/wiki/Prepare_your_SD_card)
Lots of tips there on finding your firmware version. Hint : look for the ACID and STICK utilities.
-
You might want to start by reading and understanding this page : http://chdk.wikia.com/wiki/Prepare_your_SD_card (http://chdk.wikia.com/wiki/Prepare_your_SD_card)
That helped, thanks. It appears the vers files was necessary for the Firmware Update menu item to appear.
Finally I hope I will be able to make real use of this camera.
-
It appears the vers files was necessary for the Firmware Update menu item to appear.
I don't think that's correct. You most likely did something else different. Whatever it is, keep doing it that way and enjoy.
-
Hi All,
".....I tried all the various versions of the CHDK firmware. None of them work....."
".....Can anyone assist me in getting CHDK to boot on the camera?...."
I had a similar problem with my Ixus 125's, [-100e, -101a] with the inital ports.
I used my Ixus 115 to make the SD card bootable then replaced Ixus 115
software with the Ixus 125 software.
But as I haven't reformated any SD card's recently I am not sure about most recent "125" versions.
H-H
-
Here's a test build for 101a.
Hi reyalp,
many thanks for providing this test build. Unfortunately I have been not able to test it before today but I can confirm the border on the left has disappeared. Thanks a lot!
The resolution of the image has been increased from 4624x3460 to 4680x3498 and it shows in all directions now more image conent then the related JPEG image. Nice.
Thanks and Regards,
Daniel
-
many thanks for providing this test build. Unfortunately I have been not able to test it before today but I can confirm the border on the left has disappeared. Thanks a lot!
Thanks for confirming. The change will be included in autobuild 3055 and later.
-
Hi,
I'm new here. I own a IXUS 125 HS and mainly want to get around the 10mins recording limit, someone in this thread did mention its doable.
So I just have some basic questions, excuse my lack of knowledge.
How high is the risk of bricking my camera? if having put a CHDK firewire on my sd-card and then have it write protected. If the firmware doesn't work or locks up the camera, will wiping the sd-card set the camera back to its normal settings? or is there still a risk of bricking the camera?
I have got as far as downloading and running Acid to determine firmware version and selected Download Stable Full Version, however looking in the directory path (C:\Windows\system32\) for the download I cannot find the Chdk folder which is indicated in the extracting process after downloading the correct firmware for my camera.
I was hoping to find a readme file telling me what features I can expect with the custom firmware.
I have downloaded Wicks to help install it on my SD card but haven't gone that far yet because I want to make sure I am doing it correctly and worrying about bricking my camera in the process. Is there many different versions of firmware with scripts? or will all of them have the same basic features in terms of unlocking hidden features or making tweaks, including removing the 10 min recording time limit on my camera- which is the main feature one I want.
Its seems a straight forward process, using the utility programs I mentioned, but reluctant to risk stuffing up my camera. On the other hand I really want to remove this stupid 10 minute limit on recording.
Thanks for any advice,
Daza99
-
How high is the risk of bricking my camera?
link > http://chdk.wikia.com/wiki/FAQ#Q._Can_CHDK_damage_your_camera.C2.A0.3F (http://chdk.wikia.com/wiki/FAQ#Q._Can_CHDK_damage_your_camera.C2.A0.3F)
if having put a CHDK firewire on my sd-card and then have it write protected. If the firmware doesn't work or locks up the camera, will wiping the sd-card set the camera back to its normal settings?
yes
or is there still a risk of bricking the camera?
yes
I have got as far as downloading and running Acid to determine firmware version and selected Download Stable Full Version, however looking in the directory path (C:\Windows\system32\) for the download I cannot find the Chdk folder which is indicated in the extracting process after downloading the correct firmware for my camera.
Its not actually firmware - its never permanently installed in NVRAM. CHDK runs only in regular RAM and goes away each time the power is removed.
I was hoping to find a readme file telling me what features I can expect with the custom firmware.
There is a wealth of CHDK knowledge here : http://chdk.wikia.com/wiki/CHDK (http://chdk.wikia.com/wiki/CHDK) including a list of features.
I have downloaded Wicks to help install it on my SD card but haven't gone that far yet because I want to make sure I am doing it correctly and worrying about bricking my camera in the process. Is there many different versions of firmware with scripts? or will all of them have the same basic features in terms of unlocking hidden features or making tweaks, including removing the 10 min recording time limit on my camera- which is the main feature one I want.
As I said, this is not firmware. The CHDK program is the same for every camera. Additional features can be implemented with user written scripts, and there are hundreds of them available in various places.
http://chdk.wikia.com/wiki/User_Written_Scripts (http://chdk.wikia.com/wiki/User_Written_Scripts)
Its seems a straight forward process, using the utility programs I mentioned, but reluctant to risk stuffing up my camera. On the other hand I really want to remove this stupid 10 minute limit on recording.
You might actually want to read this : http://chdk.wikia.com/wiki/Prepare_your_SD_card (http://chdk.wikia.com/wiki/Prepare_your_SD_card)
The part at the top points to a utility called STICK, which might be better for your purposes.
There is risk in using CHDK - just not a very big one. You risk dropping your camera each time you pick it up. Does that stop you?
Update : took a quick look at the platform_camera.h file for the ixus125 and it shows that CAM_CHDK_HAS_EXT_VIDEO_TIME is not enabled. So it appears CHDK for your camera does not support extended video time. If you are willing to test, you might find someone here to help you with that.
-
Update : took a quick look at the platform_camera.h file for the ixus125 and it shows that CAM_CHDK_HAS_EXT_VIDEO_TIME is not enabled. So it appears CHDK for your camera does not support extended video time. If you are willing to test, you might find someone here to help you with that.
@Daza99
If you are willing to test, and report the results, I can sent you a patched version with CAM_CHDK_HAS_EXT_VIDEO_TIME support, please tell me the fw version of your camera.
-
Hi all,
I now have a Ixus 125-100d, an ebay Cheapie, it appears to me to have some porting problems , probably due to incomplete camera CHDK porting and/or camera testing.
EDIT #1:-
Now working see here ... http://chdk.setepontos.com/index.php?topic=6231.msg106509#msg106509 (http://chdk.setepontos.com/index.php?topic=6231.msg106509#msg106509)
My Ixus 125-100e and Ixus 125-101a seem to work very well but they also have some problems.
Edit #2:- http://chdk.setepontos.com/index.php?action=dlattach;topic=6231.0;attach=9185 (http://chdk.setepontos.com/index.php?action=dlattach;topic=6231.0;attach=9185)
More complete details and some logs soon.
Edit #3:-
In "Play" there is a problem with 1 to 1 Aspect ratio, may be due to Ixus 115/125 cameras :-
see attached Ixus 125 ....... 125-101a_Play_&_Aspect 1-1
http://chdk.setepontos.com/index.php?action=dlattach;topic=6231.0;attach=9185 (http://chdk.setepontos.com/index.php?action=dlattach;topic=6231.0;attach=9185)
Ixus 125-100e works Ok
H-H
continued post #150
-
continued from post 149
Ixus 125-101a .... works OK.
Also see Edits, post 149, #1, #2, & #3:-
http://chdk.setepontos.com/index.php?topic=8085.msg106401#msg106401 (http://chdk.setepontos.com/index.php?topic=8085.msg106401#msg106401)
H-H
-
Hi guys!
I have a question for you: do you know if the CHDK works even on the Ixus 127HS? I thought that the only difference from the 125HS was the colour (satin black), but after I tried to use the CHDK firmware on it, it didn't work!! :(
Thank you all!
edit: I found the right firmware for my camera and now it works, but even if is the 1.2.0 (the stable one), I have some screen problems: the OSD and the grid blink! Is that normal?
-
do you know if the CHDK works even on the Ixus 127HS? I thought that the only difference from the 125HS was the colour (satin black), but after I tried to use the CHDK firmware on it, it didn't work!!
Try installing CHDK using the STICK (http://zenoshrdlu.com/stick/stick.html) application. If it can't find a download for your camera, please dump the camera's firmware: http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper (http://chdk.wikia.com/wiki/Canon_Basic/Scripts/Dumper)
-
I have some screen problems: the OSD and the grid blink! Is that normal?
Unfortunately that's normal for record mode. Try disabling the Canon OSD as much as you can. Features like face detection, servo AF, continuous AF, etc make this worse.
-
Thanks a lot!! :)
-
Hi all,
I now have a Ixus 125-100d, an ebay Cheapie, it appears to me to have some porting problems , probably due to incomplete camera CHDK porting and/or camera testing.
Edit #4:- Also see posts 149 & 50 above for Edits #1,#2. & #3.
continued from post #150
Ixus 125-100d Logs Now Attached
H-H
-
Ixus 100d, 100e and 101a:- SD Card Bootable are all working Ok
see attached
H-H
-
Hi all,
Some more Ixus 125 testing,
Continued from:- http://chdk.setepontos.com/index.php?topic=6231.msg106509#msg106509 (http://chdk.setepontos.com/index.php?topic=6231.msg106509#msg106509)
Ixus125-101a_Aspects_Test ..... Failed
see also here http://chdk.setepontos.com/index.php?topic=9005.msg106722#msg106722 (http://chdk.setepontos.com/index.php?topic=9005.msg106722#msg106722)
and http://chdk.setepontos.com/index.php?action=dlattach;topic=9005.0;attach=9217 (http://chdk.setepontos.com/index.php?action=dlattach;topic=9005.0;attach=9217)
H-H
-
Does anyone have a working Adobe Lens Profile (.lcp) for the Ixus125, this would be really great !
Greets
-
Is there any way to control the F stop value? I have shutter speed and ISO locked while shooting on bright and sunny days, but every 6th picture or so the F goes from 2.7 to 8 and the picture is very, very dark.
I can't find any Av control, but is there maybe some trick to stop this from happening all together? Maybe drop my ISO even lower or something?
Thanks,
-Colin
-
Is there any way to control the F stop value? I have shutter speed and ISO locked while shooting on bright and sunny days, but every 6th picture or so the F goes from 2.7 to 8 and the picture is very, very dark.
I can't find any Av control, but is there maybe some trick to stop this from happening all together? Maybe drop my ISO even lower or something?
Use the CHDK menus to disable the ND filter. The Canon firmware is engaging it in bright situations.
-
Use the CHDK menus to disable the ND filter. The Canon firmware is engaging it in bright situations.
Hmm... I see "off," "In," and "Out." It was in "off," so you're suggesting I move it to "out?"
Thanks! And sorry about the double post. I'm used to other threads where stuff gets lost/missed regularly so double posts are the norm (and things still go unseen!). I'll delete the other one right away.
-Colin
-
Hmm... I see "off," "In," and "Out." It was in "off," so you're suggesting I move it to "out?"
Yes.
Judging by your post, you might also be interested in this : http://chdk.wikia.com/wiki/KAP_UAV_Exposure_Control_Script (http://chdk.wikia.com/wiki/KAP_UAV_Exposure_Control_Script)
-
Hm.... no change. I'm running two ELPH 110 hs with CHDK. One with my old config and one with the ND filter out. All of the pictures get taken at the same settings, including when both cameras hop to f 8.0 and get dark.
I've seen that script before and honestly didn't get why it was any different than the normal CHDK controls... Ranges and values and ND control. Then again, I can't seem to control the photos the way I want so I should try that script!
I'll update with my results, thanks!
-
Uh oh! The KAP-UAV lua told me I didn't have a recent enough version of CHDK so I went to update it (stupidly).
I deleted my CHDK stuff, loaded up stickx and it can't copy. Log file says
Command 'xcopy CHDK E:\CHDK /e /i /y' issued
return code was 4
Output: '0 File(s) copied'
Installation failed - see log for details
Can't get Stick or stickx to work. I tried the old fashioned method and can't get either the ver.req/vers.req trick to show me the camera firmware NOR can I find the "update firmware" in the camera settings after unpacking the freshly downloaded CHDK package directly onto the card, as per the instructions.
Lastly, I tried just copy pasting my CHDK from my first camera SD card to the second one (which I'm pretty sure is how I did it originally for this second camera) and that didn't work either.
Help! Is there a trick I'm missing specific to this camera? Has Stick changed so it no longer works? I've tried all of these things multiple times as per the instructions, but no luck. What am I missing here?
Thanks a bunch for the help,
-Colin
-
I can't seem to get anything working other than just copying my old CHDK to my new SD card. Problem is, the KAP UAV 2.3 seems to require build 3276 or higher. I'm on 3216.
Anyone have an update procedure? I looked through this thread and see talks of how programmers don't build stuff for the firmware method anymore since "autoboots" are so easy to do. I can't find how/where to do those though. Stick isn't working and Wicks isn't working either. When I download 101a I the .bin is called PRIMARY instead of BOOTLOAD, dunno if that is something...
Can anyone point me in the direction of some more current reading for this camera and CHDK builds?
MANY THANKS!
-Colin
-
Can anyone point me in the direction of some more current reading for this camera and CHDK builds?
This link will take you to the only complete and current guide to setting up CHDK on your camera : Prepare your SD card (http://chdk.wikia.com/wiki/Prepare_your_SD_card)
It's not pretty and it contains a lot of information, only some of which is relevant to any particular camera. It also contains a lot of historical information. But it does have it all.
Still, over the last couple of years, many people new to CHDK have read it and suggested they could do a better page. A few have even tried to do so - I can post a few links to their attempts if you have time to kill but it's really not worth it. Meanwhile, I'm still waiting hopefully
-
When I download 101a I the .bin is called PRIMARY instead of BOOTLOAD, dunno if that is something...
That sounds like a rom dump rather than a CHDK build. There is no file called "BOOTLOAD", CHDK binaries would be called DISKBOOT.BIN or PS.FI2, but you need the rest of the files that go with the build too.
You should get CHDK build from the download links on the download page:http://chdk.wikia.com/wiki/Downloads
I don't know why stick isn't working for you (I don't use it) but once the card is set up, you can just extract the files in the zip onto the card using a card reader.
-
Ha, yeah... That would be it. I was downloading from the wrong place I guess. Stick still doesn't work, but as you suggested, I downloaded it from http://chdk.wikia.com/wiki/Downloads (http://chdk.wikia.com/wiki/Downloads) and just unzipped it. I went back to find the link to download page I was using and can't find it now, but it's all I could find yesterday! Some code.google page if I remember correctly.
Anyway, the script works great now! Unfortunately it's totally overcast and windy here this morning. If it clears up in the afternoon I'll do some comparison testing between my old CHDK setup and the script control to see if I can get rid of these dark images.
Thanks SO much for the help, guys! I'll post my results!
-Colin
-
Anyway, the script works great now! Unfortunately it's totally overcast and windy here this morning. If it clears up in the afternoon I'll do some comparison testing between my old CHDK setup and the script control to see if I can get rid of these dark images.
Let me see if I understand this.
- You used the CHDK menu to set the shutter speed (Tv) and ISO setting (Sv) to fixed values.
- You used the CHDK menu to set the ND filter state to "Out"
- You take about 16 pictures in bright light and one or two appear to be 3 f-stops underexposed.
If this is so, then the ND filter code in the port for your camera seems to be broken. Fixing Tv & Sv means the exposure of every shot should be the same. Your camera does not have a variable aperture so Av is fixed by definition for a given zoom position.
The only thing that would cause the exposure change you are seeing is the ND filter moving into position (as I suggested earlier) in response to a bright lighting situation.
-
waterwingz:
That's correct. I had Ev step override at 1/1000 and overrideISO at 100. All pictures were confirmed as being taken at these values.
When I'd take about 16 pictures, one or two would appear to be underexposed (very dark as I would say in my non-technical terms, haha). The only difference from these and the ones that looked good were that the f value would be at 8 instead of 2.7.
At your suggestion, I put two of the exact same cameras, ELPH 110HS, with the exact same build of CHDK on there and all the same values. The only difference was one had "ND filter state Off" and the other "out." pictures were then taken side by side at the same time. All pictures on both cameras were the same, using the same settings, including when the F 8 was used.
To add to that, I just ran the test again, but this time on the second camera I used your KAP UAV script. Giving it a range of very quick shutter values and low ISO, but still having the "Allow use of ND filter?" in the "no" position gave no "dark looking" pictures. It did, however report using F 8 on every picture that the first camera did. The second camera was able to drop the shutter speed though, so the picture still wasn't underexposed.
As far as I can tell, the ND filter control options aren't changing anything. The camera still reports using F8 on all the same pictures as the camera that is not controlling ND filter.
-Colin
-
It did, however report using F 8 on every picture that the first camera did.
How did it report that? In the kap_uav.lua log file? On the Canon OSD? Or in the image exif?
Can you enable logging in the script and post the lot here so that I can tell what the script things it was using?
-
Good point, that was on the Canon OSD.
Here's a log of me just walking around outside, not on a flying machine. There were a few F8's though on the Canon OSD. There were also many more of them than when flying because I was pointing it up at the sky pretty for most of the pictures.
-
Good point, that was on the Canon OSD. Here's a log of me just walking around outside, not on a flying machine. There were a few F8's though on the Canon OSD. There were also many more of them than when flying because I was pointing it up at the sky pretty for most of the pictures.
Well, according to what I see in the log, the camera is in fact trying to insert the ND filter on very bright scenes.
The script ignores that and forces the ND filter out. It seems forcing it out from the CHDK menu is not working though for you. Which is strange as the underlying code is the same.
-
Huh. Yeah looks like my dark frames are good for now. I'm excited to go get this on a craft and do another full survey!
Thanks so much for your help! It's greatly appreciated.
-Colin
-
Well actually, while I've got you here, I can't seem to get the usb triggering correctly.
Your usb control isn't a "trigger" like the normal one is where every time a 5 v input is seen, it snaps a picture? The documentation says it should be pausing the script, which would imply it runs the intervalometer while the usb sees 5V.
Mine does not. When 0V to USB I see nothing. When given 5V to usb, it takes a picture, then the display goes to playback mode and just stays there. The intervalometer does nothing. If given 0V then back to 5V, it takes about 4 full seconds to snap another picture. At that point it goes back to playback mode and displays the picture it just took.
The review is off in my camera and I can't find any reason it would be doing this. Has this question been answered before and I can't find it in the KAP UAV forum?
Thanks a bunch!
-
Well actually, while I've got you here, I can't seem to get the usb triggering correctly.
This is very strange so I'll ask some basic questions.
Does the script start normally ? i.e. do you see the normal startup text displayed in the on screen console when you start the script by pressing the shutter button?
Do you by chance have any of the USB remote options enabled? Things like input device or output device? Shouldn't matter buy I thought I'd ask.
-
Sorry for the delay! I was away for the weekend.
The script seems to start up normally, yes. It says "KAP 2.3 started - press menu to exit" it then lists my camera and CHDK version and the parameters chosen for photos. At the end it says "waiting on USB signal."
Under CHDK's remote settings, I've got "enable remote" enabled, but "switch type" and "control mode" are both on "none."
Thanks!
-
The IXUS125HS has 1.01a firmware....
Great to know There is a fix for Key Power,
Test version in attachment, changes:
- KEY_POWER removed
- KEY_PRINT alias removed
- KEY_ADJUSTABLE_ALT_BUTTON configured with two alternatives KEY_PLAYBACK and KEY_VIDEO
- boot.c and capt_seq.c rewritten using code_gen
If you are willing to test, I can create a new version including extended video time and remote capture.
Please test and report your results.
-
Hello! I have this camera with firmware 1.00D.
Can I use CHDK for 101a? Is it possible to update the firmware to 101a?
-
Hello! I have this camera with firmware 1.00D. Can I use CHDK for 101a?
No. You must use the version of CHDK that matches the firmware in your camera. CHDK is available for the ELPH110 f/w version 1.00D so you should use that.
Is it possible to update the firmware to 101a?
You can only change the firmware on your camera if Canon releases an official update. CHDK does not change anything permanently in the camera - it loads in RAM and goes away each time the camera is turned off. The list of know Canon firmware updates is here : http://chdk.wikia.com/wiki/Official_Canon_firmware_updates (http://chdk.wikia.com/wiki/Official_Canon_firmware_updates)
FWIW, some Canon P&S cameras only have one released firmware version (not necessarily 1.00A either). Others have as many as five or six. Differences are typically small changes in thing like language strings. If there is an actual bug with a camera's firmware, Canon will issue an update. However that is pretty rare.
-
Full newbie question:
Why my ixus 125hs (with last stable CHDK) saves only 4028x3011 DNG (vs 4608x3456 jpg)?
Thanks for reply
-
Full newbie question:
Why my ixus 125hs (with last stable CHDK) saves only 4028x3011 DNG (vs 4608x3456 jpg)?
When I look in the platform_camera.h file for the ixus125, it seems that the DNG resolution should be 4680x3498 ?
-
...my ixus 125hs (with last stable CHDK) saves only 4028x3011 DNG (vs 4608x3456 jpg)?
OK now. Switching to the last Unstable CHDK (ixus125_elph110hs-101a-1.3.0-3462-full_ALPHA)
DNG size is fine 4608x3456, as jpgs.
-
...my ixus 125hs (with last stable CHDK) saves only 4028x3011 DNG (vs 4608x3456 jpg)?
OK now. Switching to the last Unstable CHDK (ixus125_elph110hs-101a-1.3.0-3462-full_ALPHA)
DNG size is fine 4608x3456, as jpgs.
That's odd. Can you upload one of the 'bad' DNGs somewhere?
-
After a deep investigation i've found the guilty of dng downsizing.
"DNG Recover Edges" a little software that i commonly use to recover pixels from my reflex RAWs.
Strangely it downsized my canon crw/dng instead of recover edges.
BTW i confirm that dng are 4680x3498 as expected (without the "DNG Recover Edges" pass)
-
BTW i confirm that dng are 4680x3498 as expected (without the "DNG Recover Edges" pass)
FWIW, there are two sizes defined in the DNG:
1) "default crop", which should be the same size as the largest jpeg
2) "active area", which should be all the pixels that contain image data.
Which one is used depends on the DNG processing software.
Also while the "default crop" is the same resolution as the jpeg, it generally does not contain the same image, for two reasons:
1) The canon firmware may do significant distortion correction on the jpeg, so the final pixels on the jpeg don't correspond exactly to pixels in the raw data
2) CHDK makes the default crop centered on the sensor active area, while the firmware may use a different location.
-
Indeed i use Lightroom 5 to develop Ixus 125 DNGs.
After a bit of troubles, this workflow is fine with me:
-Import DNGs by choosing "Copy" (avoid "Copy as DNG" cause it could resize pictures)
-Apply "DNG Recover Edges (http://labs.adobe.com/technologies/lightroomplugins/)" to imported files to maximize picture size
-Develop DNGs according to your taste.
Here a lens profile (http://www.firedrive.com/file/47825BC40A050870) for IXUS 125 HS (extract to C:\Users\yourname\AppData\Roaming\Adobe\CameraRaw\LensProfiles\1.0)
and two of mine preferred Lightroom develop presets (http://www.firedrive.com/file/D4EBD9A82F89532F) (100 ISO & 800 ISO) (extract to C:\Users\yourname\AppData\Roaming\Adobe\Lightroom\Develop Presets)
just to thank your kind replies ... and make you forgive my bad English :)
-
IXUS 125 HS Lens Profile (http://www.firedrive.com/file/47825BC40A050870) updated.
Now it works fine with longer focal lenghts.
... and Lightroom Develop Presets (http://www.firedrive.com/file/D4EBD9A82F89532F) updated (100 ISO & 800 ISO)
-
The DISP key doesn't toggle RAW capture mode in <Alt> mode. (on last stable CHDK)
Any help?
-
The DISP key doesn't toggle RAW capture mode in <Alt> mode. (on last stable CHDK)
That's because as far as the CHDK for the ixus125 is concerned, there is no DISP key. The ixus125 is one of those cameras where there the is no separate DISP key - the "DOWN" arrow key is used for that purpose. CHDK doesn't handle "virtual" over-mappings very well just assumes there is no DISP key. I think there might have been a thread not too long ago about using the VIDEO button as the DISP key.
-
The DISP key doesn't toggle RAW capture mode in <Alt> mode. (on last stable CHDK)
That's because as far as the CHDK for the ixus125 is concerned, there is no DISP key. The ixus125 is one of those cameras where there the is no separate DISP key - the "DOWN" arrow key is used for that purpose. CHDK doesn't handle "virtual" over-mappings very well just assumes there is no DISP key. I think there might have been a thread not too long ago about using the VIDEO button as the DISP key.
Thanks for reply, waterwingz.
You did suggest in other thread:
"just add
#define CAM_DISP_BUTTON_NAME "Video"
to your platform_camera.h file"
... really i don't know how to ::) ... too newbie.
Would you make it for me?
my CHDK: ixus125_elph110hs-101a-1.2.0-3456-full_ALPHA
-
Would you make it for me?
I'll post something a little later tonight. One complication is that doing so will interfere with the option that lets you change the <ALT> key to "Video".
-
I'll post something a little later tonight. One complication is that doing so will interfere with the option that lets you change the <ALT> key to "Video".
:-*
I'll leave the <ALT> key stable on PLAY button.
Hope that the modded version doesn't exipire.
-
I'll leave the <ALT> key stable on PLAY button. Hope that the modded version doesn't exipire.
I'm leaning towards finding a permanent fix here rather than a "one off" patch for you.
Update : here's a test build > ixus125_elph110hs-101a-1.3.0-3462-full.zip (https://app.box.com/s/y88yffn9vn2yuzeqiq89) . Its exactly the same trick used with the S100 so if it's good enough there, then it should be good enough here. Try it and let me know how it works ?
-
Update : here's a test build > ixus125_elph110hs-101a-1.3.0-3462-full.zip (https://app.box.com/s/y88yffn9vn2yuzeqiq89) . Its exactly the same trick used with the S100 so if it's good enough there, then it should be good enough here. Try it and let me know how it works ?
Thank you, thank you, thank you.
With your patch i can toggle raw finally.
It seems to me that this trick also solves (partially) an Override Subject Distance issue with this porting.
To better explain:
With previous version, when Override SD selected, shooting makes the camera shutting down even if
following the suggested procedure (AFL > Alt mode > UP key > focus value).
Now i can take a shot with Override SD selected without any camera shutdown, but focus doesn't match the choosen value (ie inf.)
But this is another story and I dare not ask to much.
-
greetings everyone,
this is my first post here, so please excuse my noobie question. I have prepared the sd card the way it was described. found my firmware version is 1.01A via camera version application as function/disp button method would not work.
I downloaded the 1.01a Alpha version of the firmware, copied it to the sd card, and was getting all excited to load my firmware. Started the camera with the play button. Alas, there is no "Firm Update" button on my camera. I tried looking through the net, but did not find any relevant post. Am I the only one that could be having this problem? last option under playback is transition, and last option under camera settings is "Reset all".
For the life of me, I cannot locate Firm Update function and was hoping that someone can help on this. Thanks in advance.
-
Same camera here and CHDK works fine.
Try this:
-format your memory card in camera (flag "low level format")
-download CHDK from here (http://mighty-hoernsche.de/trunk/bins/ixus125_elph110hs-101a-1.3.0-3553-full_ALPHA.zip)
-extract the zip to the root of your memory card
-try again the firmware update
-then you can make the card bootable via CHDK menu
;)
-
I downloaded the 1.01a Alpha version of the firmware, copied it to the sd card, and was getting all excited to load my firmware. Started the camera with the play button. Alas, there is no "Firm Update" button on my camera. I tried looking through the net, but did not find any relevant post. Am I the only one that could be having this problem? last option under playback is transition, and last option under camera settings is "Reset all".
For the life of me, I cannot locate Firm Update function and was hoping that someone can help on this. Thanks in advance.
You really are doing this the hard way. The STICK utility will download, format, and install everything for you.
However, if you want to continue with your approach then you need to make sure there is a file called PS.FI2 in the root directory of your SD card for the firmware update method to use. If it is not there, then you will not be able to load CHDK that way.
-
Thanks waterwingz for your reply. I was able to get CHDK loaded. When I cannot locate the Firm update function, I just did it the other way, and copy the folder content entirely to the sd card and boot it off that way, and it ran fine.
But I am interested in what you said about the STICK utility. Can you point me to the right place to give that a try?
Also, I had enabled RAW format shooting on the firmware, but all the pictures came out essentially just a blur. I wonder if there is something wrong with the camera. if I am asking the questions in the wrong thread, please feel free to let me know also. Thanks again.
-
But I am interested in what you said about the STICK utility. Can you point me to the right place to give that a try?
http://zenoshrdlu.com/stick/stick.html (http://zenoshrdlu.com/stick/stick.html)
Also, I had enabled RAW format shooting on the firmware, but all the pictures came out essentially just a blur.
Which pictures? Both the JPG's and the RAW files ? If it was just the RAW files, what software are you trying to use to view them? (You might have more succcess of you save as DNG - most photo processing software will open that correctly while plain CHDK RAW files will not).
-
Thanks for the links. I will check it out for sure.
I was saving the file as DNG, and was trying to view it from Photoshop, as it was the default program associated with the file type. when I am viewing it in PS, I would often see a white image with waves of color stripes across the picture horizontally. Rather bizarre.
-
I got a chance to use the utility, and it went without a hitch. Thanks a lot.
But raw shooting woes continue. The only thing I have checked in setting is shoot as raw, include raw in same directory as jpg, and then under dng, to create bad pixel.bin, as I have read somewhere. I hope I read it correctly. The camera proceeded to take a couple of pictures on its own, then came back and said writing of bad pixel.bin failed, and to please try again. I've tried it a few times thereafter, and still failed.
Images proceeded to be bad still in raw format. jpg turned out ok. but the raw file is distorted, and dis-proportioned in general. and it read the same way view preview and photoshop in Mac OSX. :(
-
I got a chance to use the utility, and it went without a hitch. Thanks a lot.
But raw shooting woes continue. The only thing I have checked in setting is shoot as raw, include raw in same directory as jpg, and then under dng, to create bad pixel.bin, as I have read somewhere. I hope I read it correctly. The camera proceeded to take a couple of pictures on its own, then came back and said writing of bad pixel.bin failed, and to please try again. I've tried it a few times thereafter, and still failed.
You can shoot DNG 1.3 without needing to create badpixel, although depending what software you use to process the resulting files, you might see the bad pixels.
Images proceeded to be bad still in raw format. jpg turned out ok. but the raw file is distorted, and dis-proportioned in general. and it read the same way view preview and photoshop in Mac OSX. :(
If you mean lens distortion, this is normal. The camera does software distortion correction when creating the jpeg. If you want the same correction in a DNG, you have to do it yourself. Generally this is done with a lens profile, which can be created with the adobe lens profile tool if one doesn't already exist for the camera.
You should not expect raw to be a higher quality image that you can just use. It's raw data, which you can process as you choose instead of the way canon frimware chooses. In some situations you may be able to get higher quality, but canons jpeg process is quite good.
when I am viewing it in PS, I would often see a white image with waves of color stripes across the picture horizontally. Rather bizarre.
This sounds like it may be a different problem. If there is no recognizable image at all, then CHDK is probably saving the wrong data to the file. There's a couple different ways this can happen:
1) Raw data isn't available in the shooting mode you are using. On some cameras this happens in auto mode. It also happens in some special low light mode that aren't full resolution (generally an iso3200 or low light scene mode). In this case, every shot in that mode will be bad.
2) The camera uses multiple buffers, and CHDK doesn't always get the right buffer. In this case, some images will be fine and other will be random garbage. It may be more likely to happen if you shoot in continuous mode or shoot quickly. If this is happening, we can probably fix it.
-
If you are willing to test, I can create a new version including extended video time...
Hi nafraf,
a bit late for asking, but passed the first period of CHDK drunkenness, i realized that the EVT would be a nice feature to add to the ixus 125(elph 110) port. Need it for this (http://chdk.setepontos.com/index.php?topic=11897.msg116640#msg116640) script attempt.
Too out of time ?
-
Extended video time test version.
-
Extended video time test version.
1. THANK YOU
2. Your EVT patch works fine with standard videos
3. Also it works fine with "Miniature mode" videos so that i can do "in camera" time lapse, with the above-mentioned script, without blurred bands and the infamous 10 min time limit ... until the overheating* will melt my ixus :)
If no complaints from others dudes, i hope for a definitive patch.
(*) BTW i tested it indoor with a 40 min continuous rec and no "tactile" signs of overheating
-
Extended video time test version.
1. THANK YOU
2. Your EVT patch works fine with standard videos
3. Also it works fine with "Miniature mode" videos so that i can do "in camera" time lapse, with the above-mentioned script, without blurred bands and the infamous 10 min time limit ... until the overheating* will melt my ixus :)
If no complaints from others dudes, i hope for a definitive patch.
(*) BTW i tested it indoor with a 40 min continuous rec and no "tactile" signs of overheating
You could add a little code to your script to monitor and log the temperature sensors in your camera if you are concerned about temperature. You could even set a high temperature shutdown limit that would tell the script to stop recording.
-
You could add a little code to your script to monitor and log the temperature sensors in your camera if you are concerned about temperature.
Make sure you only try to write the log file after recording is finished.
-
You could add a little code to your script to monitor and log the temperature sensors in your camera if you are concerned about temperature. You could even set a high temperature shutdown limit that would tell the script to stop recording.
Thanks for your tips WW and srsa.
I "could" do a lot of things with scripts ... if i only know how to :)
I've to learn a lot about this "dark matter".
-
EVT support included in trunk 3623 (https://www.assembla.com/code/chdk/subversion/commit/3623)
-
EVT support included in trunk 3623 (https://www.assembla.com/code/chdk/subversion/commit/3623)
WOW!
It also overrides the "slow motion movies" time limit.
Surely CHDK stands for Canon Hack Developers Kindness :)
PS
The overheating with EVT seems a false issue (i got 52°C CMOS max temperature after ~ 20 min full HD video
and 48°C CMOS max temperature after 1,5 hours "miniature enhanced" HD video) ... indoor test.
-
Hi everyone,
First of all - Thanks a lot for porting CHDK for this camera.
I am interested in buying a ELPH 110 HS and would like to know if the usb remote / multiple camera (sync) option is working with this build?
Also, if there are any firmware versions that are not compatible at the moment (to not buy them) - I couldn't find a list of officially released firmware versions for this camera unfortunately.
Thanks a lot for your help :) -
Kind regards,
thewer
-
Hi everyone,
First of all - Thanks a lot for porting CHDK for this camera.
I am interested in buying a ELPH 110 HS and would like to know if the usb remote / multiple camera (sync) option is working with this build?
Also, if there are any firmware versions that are not compatible at the moment (to not buy them) - I couldn't find a list of officially released firmware versions for this camera unfortunately.
Thanks a lot for your help :) -
Kind regards,
thewer
- the USB remote works fine on my cam (CHDK 1.3)
- in this thread were not reported firmware versions other than 100d, 100e, 101a.
nice day
-
Hi there -
Thanks a lot for your help! :)
I'll try to get my hands on two ELPH 110 then (interested in stereo photography)
Kind regards,
thewer
-
@Kasius Klej reported (https://chdk.setepontos.com/index.php?topic=12793.msg130313#msg130313) that live PTP view dimensions are incorrect for this port.
I've uploaded test builds for firmware 100d, 100e and 101a to https://app.box.com/s/rwco2rtn4otkesis5dohknkhtuq8ej8e
Please check that the everything visible on the camera display is also visible in the chdkptp live view, for both playback and record mode.
There are likely still problems if the camera aspect ratio is not set to 4:3, and possibly also when 16:9 video is being recorded. I can probably fix these someone can provide some information
1) The PROPCASE_ASPECT_RATIO value, =return get_prop(require'propcase'.ASPECT_RATIO) or for video, the VIDEO_RESOLUTION value.
2) An lvdump taken with the "quick dump" button in the debug tab in the live view area.
-
Please check that the everything visible on the camera display is also visible in the chdkptp live view...
There are likely still problems if the camera aspect ratio is not set to 4:3...
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FHlUxBag.jpg&hash=f9895161f8d890bcc08b3e65b093ea78)
Everything is there in 4:3 aspect ratio. In 16:9 a short strip at the bottom is missing.
-
1) The PROPCASE_ASPECT_RATIO value, =return get_prop(require'propcase'.ASPECT_RATIO) or for video, the VIDEO_RESOLUTION value.
It says:
> =return get_prop(require'propcase'.ASPECT_RATIO)
187:return:1
-
Everything is there in 4:3 aspect ratio. In 16:9 a short strip at the bottom is missing.
Thanks, I've checked this in, so the autobuilds after 4714 should be correct in 4:3 at least.
1) The PROPCASE_ASPECT_RATIO value, =return get_prop(require'propcase'.ASPECT_RATIO) or for video, the VIDEO_RESOLUTION value.
It says:
> =return get_prop(require'propcase'.ASPECT_RATIO)
187:return:1
What I meant was the value in each different aspect ratio, like
0 = 4:3, 1 = 16:9, 2 = 3:2, 3 = 1:1
It will probably be the exact values listed above (unless some don't exist on this camera), but I'd like to confirm.
Same for =return get_prop(require'propcase'.VIDEO_RESOLUTION) in different video settings. I would expect
5=1920x1080, 4=1280x720, 2=640x480, 1=320x240
Again the camera may not support all of these, but the ones that exist should match.
-
Same for =return get_prop(require 'propcase'.VIDEO_RESOLUTION) in different video settings.
I get the same values for photos. For videos, my camera has 3 modes, and the get_prop returns 0 for all of them. I get
0=1920x1080, 0=1280x720, 0=640x480
-
Same for =return get_prop(require 'propcase'.VIDEO_RESOLUTION) in different video settings.
I get the same values for photos. For videos, my camera has 3 modes, and the get_prop returns 0 for all of them. I get
0=1920x1080, 0=1280x720, 0=640x480
The VIDEO_RESOLUTION propcase returns the same value? ASPECT_RATIO is not expected reflect the video resolution.
-
The VIDEO_RESOLUTION propcase returns the same value?
Yes, zero.
By the way, I haven't noticed this way before, because one usually doesn't shoot film in front of a pc screen, but yes, the live view in this wide screen movies is like before with landscape photography.
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FiHWTycX.jpg&hash=ac6647f8c47ce59d5678c7cb7ee4b9e6)
It works all right for standard photos and oldtimer TV sets though.
-
The VIDEO_RESOLUTION propcase returns the same value?
Yes, zero.
Thanks, looks like I used the wrong value for PROPCASE_VIDEO_RESOLUTION in propset 5.
You can try =return get_prop(171)
I've uploaded new test builds (called ixus125_elph110hs-...-1.5.0-4714-reyalp-lv-test-2.zip) to the box folder https://app.box.com/s/rwco2rtn4otkesis5dohknkhtuq8ej8e
This should fix the issues with different aspect ratios, for both and stills and video. It should also show the live view in the correct place in stitch assist mode (though the previous shot will not be shown).
-
First of all, I'd like to thank you all a lot for this development. The developer and those who helped. I've been reading all this thread's pages. I'm new to CHDK. My only camera is an Ixus 125 (elph 110HS) firmw 100e. I use it for video recording. I really need the 10 minutes limit to be removed. I see in the release notes that - "EXT_VIDEO_TIME not implemented", so I assume it still has the 10 minutes limit. But I see you've removed it for v100d some posts ago. Is it possible to remove it for the v100e firmware? I clearly have no money for a camcorder and I need to film more than just 10min. Thanks in advance. Leeam.
-
I really need the 10 minutes limit to be removed. I see in the release notes that - "EXT_VIDEO_TIME not implemented", so I assume it still has the 10 minutes limit.
The notes are out of date, the feature should be supported.
You need to enable it in Video Parameters -> Video without time limit. AFAIK this setting is never saved, you need to enable it each time you power up the camera.
edit:
Since the camera can't record files bigger than 4GB, you may want to look at these scripts too: http://chdk.wikia.com/wiki/Continuous_Video_Scripts
-
I really need the 10 minutes limit to be removed. I see in the release notes that - "EXT_VIDEO_TIME not implemented", so I assume it still has the 10 minutes limit.
The notes are out of date, the feature should be supported.
You need to enable it in Video Parameters -> Video without time limit. AFAIK this setting is never saved, you need to enable it each time you power up the camera.
edit:
Since the camera can't record files bigger than 4GB, you may want to look at these scripts too: http://chdk.wikia.com/wiki/Continuous_Video_Scripts
Oh, really!? Well thank you so much for making that clear and also for the link. I'll download it and try, then! I'll report back if sth isn't working correctly.
-
I've uploaded new test builds (called ixus125_elph110hs-...-1.5.0-4714-reyalp-lv-test-2.zip) to the box folder https://app.box.com/s/rwco2rtn4otkesis5dohknkhtuq8ej8e
I have downloaded this patch in October and I'm using it ever since. It works well for me. There are two bugs however, but they're really not worth mentioning, there is about 2 millimeters missing, not a big issue.
(https://chdk.setepontos.com/proxy.php?request=http%3A%2F%2Fi.imgur.com%2FgcHALJa.jpg&hash=16d39af598e1592e843c35c2ccdb8811)
-
I have downloaded this patch in October and I'm using it ever since. It works well for me.
Are you certain you are using the one I posted in that post (-lv-test-2, built on Oct 29), not the one I posted earlier in the thread?
You can check the output of =return get_buildinfo()
There are two bugs however, but they're really not worth mentioning, there is about 2 millimeters missing, not a big issue.
I prefer not to check in things that known to be broken, so your help is appreciated.
-
Are you certain you are using the one I posted in that post
I'm certain. It says build_date="Oct 30 2016".
-
It says build_date="Oct 30 2016".
Unless that's a typo, I think that isn't the right build, the ones I posted were built Oct 29 (It's just a string, so not affected by your timezone or anything like that)
Please try one from https://app.box.com/s/rwco2rtn4otkesis5dohknkhtuq8ej8e
-
Unless that's a typo, I think that isn't the right build, the ones I posted were built Oct 29 (It's just a string, so not affected by your timezone or anything like that)
Please try one from https://app.box.com/s/rwco2rtn4otkesis5dohknkhtuq8ej8e
I did again. It is unusual how it says build date is 30. October for your files uploaded on 29. October. Do you live in different time zone or something?
:return:table:{platform="ixus125_elph110hs",build_date="Oct 30 2016",build_number="1.4.1",build_time="03:13:15",version="CHDK",platsub="101a",build_revision="4721",platformid=12865,os="dryos",}
-
I did again. It is unusual how it says build date is 30. October for your files uploaded on 29. October. Do you live in different time zone or something?
No, as I said above
It's just a string, so not affected by your timezone or anything like that
Anyway, you are running 1.4.1-4721 which is the latest stable autobuild, not my test build. The build I uploaded was 1.5.0-4714
If you are using Stick to install, make sure you tell it to use the custom build. Or if you aren't using a multi-partition card, just copy the files manually.
-
The build I uploaded was 1.5.0-4714
Thanks for this tip. Now I got the correct build and everything works fine.
-
Thanks for this tip. Now I got the correct build and everything works fine.
Thanks for testing. I've checked the changes in for 1.4 and 1.5, autobuilds 4741 and later.
-
Hi,
I tried the latest build (1.4.1-4772-ALPHA) on my IXUS 127 HS (which I believe to be simply 125 HS with 101a - after all, the model IDs are the same. I was unable to find any information regarding differences between the two models. CHDK_DE Forum plainly states "127 HS is 125 HS". But I digress).
The card is Eye-Fi 8GB Pro X2, and occasionally (probably only upon WiFi status change) the CHDK overlay becomes overwritten (see attachment).
This might have to do with the second buffer address being incorrect, since Snake doesn't seem to work at all (it shows briefly and then just becomes blue). I'm new to CHDK, so please don't be too harsh on me :haha
Thanks!
-
The card is Eye-Fi 8GB Pro X2, and occasionally (probably only upon WiFi status change) the CHDK overlay becomes overwritten (see attachment).
This is pretty much normal. CHDK and the Canon UI do not cooperate. If CHDK writes to the display buffer, nothing prevents the Canon firmware from overwriting it. If there is a way to fix this, we have not discovered it.
Is this simply annoying for you? Or does it prevent you from doing something you would like to do? Snake not working is a bit of a concern.
edit : does Snake work in playback mode? Generally speaking, overwrites of CHDK stuff are a lot worse when the camera is in shooting mode and the Canon UI is updating a lot of stuff on the LCD
-
Thanks for the quick reply!
Is this simply annoying for you? Or does it prevent you from doing something you would like to do? Snake not working is a bit of a concern.
Yes, it's awful. CHDK is utterly useless without Snake :D
does Snake work in playback mode?
Nope.
On a more serious note, there was this one time when the card's WiFi seemed to be erratically switching on and off. That obviously meant CHDK menu being consistently corrupted, which was of concern (at least to me).
-
does Snake work in playback mode?
Nope.
So based your description, I'm guessing this is more to do with a bad choce of colors in the color pallet rather than a buffer issue.
-
So based your description, I'm guessing this is more to do with a bad choce of colors in the color pallet rather than a buffer issue.
I suspect this isn't the palette, since
(it shows briefly and then just becomes blue)
(emphasis added).
-
I suspect this isn't the palette, since
(it shows briefly and then just becomes blue)
(emphasis added).
Agreed. Also, the palette colors seemed pretty correct in the live view debugging earlier in the thread.
The snake thing is odd. If you could post a video or chdkptp lvdump of it happening, we might have a better idea of what is happening.
On a more serious note, there was this one time when the card's WiFi seemed to be erratically switching on and off. That obviously meant CHDK menu being consistently corrupted, which was of concern (at least to me).
This sounds like it's probably normal to me, although it's hard to be sure without seeing it.
-
Well, guess what. I just installed the CHDK_DE build, and Snake works just fine.
-
Well, guess what. I just installed the CHDK_DE build, and Snake works just fine.
This is very strange, it's built from the same source :-[
-
I believe I found the scenario that reliably reproduces the bug.
1. Start Reversi
2. Exit Reversi
3. Start Snake
-
Here's another bug, this time in default.lua (probably applies to other models as well):
1. Change camera language to Russian
2. Run default script
Expected: CHDK language changed to russian
Actual: unknown language id (16)
-
Here's another bug, this time in default.lua (probably applies to other models as well):
Yes, this seems to be another example of propcase values changing between propsets. (https://chdk.setepontos.com/index.php?topic=12918.msg132221#msg132221)
I get the same on elph130. The script can probably be fixed by adding more cases in get_cam_lang.
FWIW, I wasn't able to reproduce the reversi/snake issue on elph130. That doesn't mean it I don't believe you, just that I have less chance of fixing it ;)
-
FWIW, I wasn't able to reproduce the reversi/snake issue on elph130.
Could not reproduce on an S100 or G10 either.
-
I believe this port deserves a BETA status, especially since I myself was unable to reproduce the snake issue with the latest trunk build.