frogcement
tetu_024
Could a large speaker magnet cause this issue?Like electro magnetic interference? Because now i recall that the camera bag was near a Sub Woofer. From there onwards the images started to get like that. Is there a way to degauss the cmos? or else discharge it totally ?
Thanks
I was looking at your posted photo again, were there any high power lines around where you were shooting this? And the obvious dumb question, does it still look like this when you take pictures at home?
thaibv
I checked your CR2 file and found out that you shot at ISO 100 and it also have alot horizoltal lines, but image info show that you apply Dust Delete Data. Dont you try to turn Dust delete data off? May be it could help.
Zibri
thaibv: any progress on firmware feature additions?
loopfst
Hello, thaibv. Thanks for your work.
We can restore the original CMOS? (unTESTFIR.FIR)
"The test.fir change boot flags in your cam's cmos rom, so your cam can boot up from card."
Canon Eos Utility not working properly to me. CFcard is 8Gb Fat32.
Changes work well, but EOS Utility and USB blocks the camera. The reading light blinks once, then stops and locks the camera. We must remove the battery to reset.
AUTOEXEC.BIN also causes a slight delay when turning, that's not very important, but I want to go back in time.
thank you very much.
(sorry,i speak little English)
thanos
This is the most fantastic firmware hack ever. Just made my 400D compete easily with the 40D. 🧑🎄
The 3200ISO images can easily be cleaned with DPP and/or noise ninja.
Many thanks for the superb work and waiting to see what comes next.
thaibv
Hi,
loopfst
We can restore the original CMOS? (unTESTFIR.FIR)
"The test.fir change boot flags in your cam's cmos rom, so your cam can boot up from card."
Canon Eos Utility not working properly to me. CFcard is 8Gb Fat32.
Changes work well, but EOS Utility and USB blocks the camera. The reading light blinks once, then stops and locks the camera. We must remove the battery to reset.
I will check camera USB connection. If you wan to go back, simply format your CF card.
SoNic
I did have problems with Canon Utility (not seeing the camera) but after I did reinstall it and apply the patches from Canon site it is working. USB was fine all the time.
One of the guys that tried this reported that his camera slowed down more and more while he was using the hack - I didn't shoot a lot of pics with it so I cannot tell if it is true.
I wonder if the camera in this mode isn't writting constantly some info in the internal memory? Like a debug file? If yes, can it be turned off?
Also, formating the card is not what he asked, but setting the flags in the firmware back on the same condition (as in not booting rom CF cards). Like the "bootflag" utility existing for 350D.
thaibv
Hi again,
Zibri
thaibv: any progress on firmware feature additions?
Sorry, no time so no progress
SoNic
One of the guys that tried this reported that his camera slowed down more and more while he was using the hack - I didn't shoot a lot of pics with it so I cannot tell if it is true.
I wonder if the camera in this mode isn't writting constantly some info in the internal memory? Like a debug file? If yes, can it be turned off?
Also, formating the card is not what he asked, but setting the flags in the firmware back on the same condition (as in not booting rom CF cards). Like the "bootflag" utility existing for 350D.
I didnt shoot very much too, but if the hack slowed down your Cam you should turn it of and back on. If you dont go into Fatory menu and press DP to turn debug mode on, your cam dont write anything to CF card
Flashing boot flags is a dangerous routine. if it fail you will have an expensive paper weight. So fomat CF card to force your cam boot from original rom is risk-free.
I checked usb connection (copy image, transfer image) and shot in EOS utility found no problem (Sorry, i don't have 8GB card for test).
loopfst
I tested with a 4GB card to them. Check the USB cable and probe on two computers.
With many images on the card, EOS Utility crashes the camera. (Freeze).
So best not to touch the boot flags, ok.
Within my abilities as an amateur, I wanted to find the source of the problem. I like the EOS Utility, but will have to work with a USB CF reader. No problem. I prefer the current improvements and future to arrive.
Where can I find information about "FACTORY MENU? Specifically AF CK.
Thanks for your time.
Vathek
loopfst
Where can I find information about "FACTORY MENU? Specifically AF CK.
There's a thread for Factory Menu on 400D
https://chdk.setepontos.com/d/4171
Actually I didn't try the AF CK because I don't like to get messy with failed tests, but someone (Zibri, I guess) already tried the AF CK.
Before starting to test the factory menu I'd prefer to have a way for restoring the factory results (all passed) in the rom.
In fact the tests write some flag in the FLASH memory, so if you can't pass some tests, the "failed" flag will be written in the flash and actually I have not found a way to restore the "success" flag. The only way is to pass the test but sometimes they're quite cryptic.
frogcement
Hello to all, Just an update on my usage. I have done some pixel peeping, and i can see no advantage to any ISO below 100. OTOH 3200iso work wonderfully and all the mid iso's are great, ability to fine tune exposure with iso is nice. I have all my cards working 1gb 2gb 4gb 8gb and 16gb the 8 and 16 were a bit tricky but work well. As far as the USB issues, i can report no trouble at all even remote shooting with the EOS utility work fine 'UNLESS' i leave spot metering or ISO3200 on before pluging it in to USB. So, make sure metering is in a normal "un-hacked" setting and ISO also.
So far this is working great, thanks for this great project!
Take Care . . . .
--
lightAddict
I have to say i am loving the changes to my rebel
amazing job thaibv
i was reading strobist today and he was talking about having a camera that would calculate the white balance of a scene and display the coresponding gel combination of gels to match the flash to the scene. from one of the comments there it semed that the calculations involved may be a little complex for the rebel to do so i was also wondering if it would be possible to get the white balance in Kelvin to display on the camera in some way. i was thinking it could be possible to display the value of the custom white balance when you set it or having it replace something from the third playback display option
i have some coding skills not really enough for this kind of work but i would be willing to try if someone could help get me started
Zibri
Vathek
Actually I didn't try the AF CK because I don't like to get messy with failed tests, but someone (Zibri, I guess) already tried the AF CK.
Yep.. I did it.. but I see no problem in having a failed test.. it's failed because it's not completed. That doesn't change the camera functionality.
And I just wanted to explore the menu..
ashinkizer
Hi all,
First of all, many thanks for this hack, love it.
The main reason I installed CHDK is to run those uBasic scripts. Specifically I want the intervalomter:
http://chdk.wikia.com/wiki/UBASIC/Scripts:_Ultra_Intervalometer
Is there any way to do this with the 400D or is this only possible with the P&S cameras?
Ash
Zibri
yep.. I agree.. scripting is a killer app for cameras
zuNN
intervalometer is a great feature to add.... anyway great job!!!
Gull_Code
To Foldesa/Seklth/thaibv:
Thanks for that great hack ! I love the spot metering && adjustable iso range ! It's reallya great 400D improvement.
I am also offering some times && competences. I don't know how high should my programming skills be to help you.
I have no real ability in ASM or ARM. On the contrary, I think I am as good at C than I am bad @ASM (never tried, except a few things with SSE/MMX)
If you come back there, I really would love having a talk with you, and see if I can help in any way.
I'll send you my mail in a PM just after that post.
Keep up the good work !
Gull_Code
Ok, I feel a little bit more comfortable with the code.
I noticed that 16,32,64,80, well, all iso < 100 does not work as expected. I may have to do some little research.
I'll try to play a little with my own autoexec.bin and see what happens.
Zibri
gull: play? meaning? what tests are you going to make?
Gull_Code
I have a good programming experience, but C/C++. I've never got into firmware/anythingelse hacking before.
By playing I mean cleaning the code (mainly adding comments for my understanding), and try to enlarge the shutter speed adjustment.
I know Foldesa is trying to play with auto-iso mode, and that he already started some research on the shutter speed.
Don't worry, if ever I complete anything, I'll post it right there.
