Eos 400d ( Rebel XTI )

0xAF

Sergei
Great job, 0xAF! I guess you can draw anything on the screen now. New dialogs, help windows... Do you know if default GUI updates screen so often or there is no problem with it?

Basically this means, we can now draw whatever we want, just like in ML, and the basic idea was to use a ML style of menus/dialogs, as the canon's (which we use now) are not good enough for our needs.

In the video you can see the normal start of the camera and after few seconds i paint the whole VRAM in yellow, then "Hello World!" is written. As you can see a part of the screen is being redrawn by gui task, thought it's not everytime and not so often, but in this video it's visible.
Then i do nothing, i wait for a regular event which redraws the screen, so you can see how much time it takes before a regular redraw happens... of course if you press a button or force some screen change, the redraw will happen sooner.

I already knew that ML has a way to block redraws, and i was thinking to block the GUI task (atleas the redraw event).
As Alex explained, we will probably look for the ML's way of blocking the redraws.

0xAF

eduperez
In our "gui.c" we intercept the GUI_IDLEHandler routine, to detect when the main dialog has been updated (event GUI_START_OLC_MODE), and change some of the info displayed (like the spot metering icon, for example). I have played very little with that code, but looks like a nice starting point to look for events to block.

Yes, I was thinking the same ... gui task is a good candidate.
Probably we should do the handlers in one task too (if it's possible), this would be more clean to maintain i guess...

a1ex
I have played a bit with IDLEHandler events, but wasn't able to handle them without causing stability problems.
I'm even thinking to move all menu button handlers into gui_main_task (instead of dialog API).

Alex, have you investigated if you can catch everything you need in the GUI task?
I was thinking for the MainCtrl task, but i'm not sure we can catch every button press there...

a1ex

There are some buttons which can't be seen from gui_main_task (like scrollwheels in main photo mode). But at least what works, works well.

MainCtrl task looks pretty low level, and doesn't seem to handle more buttons.

Mirfak

Currently I use the JUMP button in shooting mode for AEB. Is there a reason why we can't have finer steps for each button press, like we can when setting AEB through the camera menu (e.g. +/-1/3 EV)?

Flash AEB would be another useful option for the buttons. I have a few presets that I use with flash (if necessary).

Sergei

Speaking of buttons, I found two buttons: jump in *(int*)(0xC0220134) and trash in *(int*)(0xC0220130). When button is pressed value of an address will be 0x20 and 0x21 when button isn't pressed. Good for exiting a loop in a script.
Or can be used to prevent loading of autoexec.bin at startup.
if(*(int*)(0xC0220130)==0x20)InitializeIntercom(); //if trash button pressed at startup load default IntercomHandler.
else my_InitializeIntercom();

Probably best place is in my_romStart:

void my_romStart(int startType)
{
  unknown_cache(&cache_0xFFB602F0, &addr_0x1900, 0xC6B0>>2);
  if(*(int*)(0xC0220130)!=0x20)my_usrInit(startType); // if trash botton is not pressed.
  else usrInit(startType);
}

eduperez

Mirfak
Currently I use the JUMP button in shooting mode for AEB. Is there a reason why we can't have finer steps for each button press, like we can when setting AEB through the camera menu (e.g. +/-1/3 EV)?

Flash AEB would be another useful option for the buttons. I have a few presets that I use with flash (if necessary).

I do not see any reason why these two features could not be implemented.
Please, open a couple of "feature requests" here, and we'll have a look at them later; thanks!

eduperez

Sergei
Speaking of buttons, I found two buttons: jump in *(int*)(0xC0220134) and trash in *(int*)(0xC0220130). When button is pressed value of an address will be 0x20 and 0x21 when button isn't pressed. Good for exiting a loop in a script.
Or can be used to prevent loading of autoexec.bin at startup.
if(*(int*)(0xC0220130)==0x20)InitializeIntercom(); //if trash button pressed at startup load default IntercomHandler.
else my_InitializeIntercom();

Probably best place is in my_romStart:
[code]
void my_romStart(int startType)
{
unknown_cache(&cache_0xFFB602F0, &addr_0x1900, 0xC6B0>>2);
if(*(int*)(0xC0220130)!=0x20)my_usrInit(startType); // if trash botton is not pressed.
else usrInit(startType);
}
[/code]

Another great finding, Sergei! And many thanks for sharing!

0xAF

Sergei
Speaking of buttons, I found two buttons: jump in *(int*)(0xC0220134) and trash in *(int*)(0xC0220130). When button is pressed value of an address will be 0x20 and 0x21 when button isn't pressed. Good for exiting a loop in a script.
Or can be used to prevent loading of autoexec.bin at startup.
if(*(int*)(0xC0220130)==0x20)InitializeIntercom(); //if trash button pressed at startup load default IntercomHandler.
else my_InitializeIntercom();

Probably best place is in my_romStart:
[code]
void my_romStart(int startType)
{
unknown_cache(&cache_0xFFB602F0, &addr_0x1900, 0xC6B0>>2);
if(*(int*)(0xC0220130)!=0x20)my_usrInit(startType); // if trash botton is not pressed.
else usrInit(startType);
}
[/code]

GREAT,
i was looking for mem address of any button fo so long time.
since i've ported the bmp stuff now, i was going to make the memspy work with realtime displaying, so i can find btn addresses.
it seems you already found a way to catch them, thanks for sharing 😉

preventing the loading of the hack is why i wanted it...

EDIT:
http://code.google.com/p/400plus/source/detail?r=1344
Thanks Sergei !

EDIT2:
Sergei, just saw the canon's service manual and it seems only these 2 buttons are connected to the digic processor, so i guess you wont find the other button addresses unless they are mmap'ed from the MPU (which i doubt). Just to let you know, if you're trying to find the other buttons.

Sergei

Thanks 0xAF. Yes I did try to find more buttons with no luck. It explains why.

koswix

Hi,

First of all thanks for the brilliant work on the firmware, my 400D is now even more fun.

Secondly, I have looked through this entire thread and can't see the answer, so apologies if I've missed it somewhere.

I've been playing with the intervalometer for the passed week or so, and today I decided to do something a bit longer-term with it: namely filming a flower decomposing over 2-3 weeks. Ideally I'd like to take 1 shot every hour, so that at 24FPS the video will be a second a day. But lo', the intervalometer only goes up to 5 minutes!

Is this for a technical reason, or just because? And is it possible to change this? I notice that the display is in the format mm:ss so I'd just assumed I could go up to 99:59 as the maximum.

Thanks.

P.S. If anyone is interested in the time lapse videos I've done so far they can be found on my youtube page, http://www.youtube.com/user/koswix?feature=mhee

eduperez

No, there is no other technical reason that we had to set a limit, and five minutes seemed long enough. While raising the limit is quite easy, the behavior of the menu will probably have to be modified first: changing the value up to one hour, second by second, can be very boring for the user. Please, open a "feature request" here, so it gets registered.

Then, there is the issue of powering the camera for that period of time, but that is clearly outside the scope of this project.

koswix

Hi,
Thanks for the response. I did have a quick look at the source code to see if I could change the limit, but then I remembered I haven't done C++ for over ten years, and I wasn't very good at it then!

I'll put a feature request in - a friend who has a plug-in timer manages to get over 24 hours out of a battery doing one shot an hour, so battery life isn't that much of a problem. I've got a DC adapter on order anyway, though.

Thanks

0xAF

Canon's adapter is way too expensive. Unless you find a second hand one or a china one, OR:
I've made 2 adapters for car (12V) and for wall-socket (220V).
I've used one dead battery as a plug to the camera.
Total cost - not more than 4-5 EUR.

power supply for EOS 400d
Battery disassembled, 3 wires soldered to the connector pads (though 2 were needed, the central one is not connected)
The battery modules and the PCB are removed from the body.

power supply for EOS 400d
One capacitor connected, just in case (though it's not needed)

power supply for EOS 400d
The battery body with a cable and plug,
The car adapter and the wall-socket adapter, which can be plugged to the battery body.

Important note: The both adapters are 7.2V-7.4V and 1.5A (atleast). The power-up of the camera is hungry.
One of my colleges made the changes to the adapters (some resistor), so they are 7.2V.

guffster

0xAF
Canon's adapter is way too expensive. Unless you find a second hand one or a china one, OR:
I've made 2 adapters for car (12V) and for wall-socket (220V).
I've used one dead battery as a plug to the camera.
Total cost - not more than 4-5 EUR.

power supply for EOS 400d
Battery disassembled, 3 wires soldered to the connector pads (though 2 were needed, the central one is not connected)
The battery modules and the PCB are removed from the body.

power supply for EOS 400d
One capacitor connected, just in case (though it's not needed)

power supply for EOS 400d
The battery body with a cable and plug,
The car adapter and the wall-socket adapter, which can be plugged to the battery body.

Important note: The both adapters are 7.2V-7.4V and 1.5A (atleast). The power-up of the camera is hungry.
One of my colleges made the changes to the adapters (some resistor), so they are 7.2V.

What a cool idea. Never thought about doing such a hack with a used dead battery. Thanks for sharing... I must try this. 😀

bosznai.istvan

Hi!

I have a problem, the 400plus menu enters automatically to the Parameters menu, if I click the Av button, it exists, but only for a brief time, than it enter it again. If I go to a sub-menu item in the Parameters menu, like AutoISO it behaves normally.
I'm using the latest stable release, 400plus-20120415-7

eduperez

bosznai.istvan
Hi!

I have a problem, the 400plus menu enters automatically to the Parameters menu, if I click the Av button, it exists, but only for a brief time, than it enter it again. If I go to a sub-menu item in the Parameters menu, like AutoISO it behaves normally.
I'm using the latest stable release, 400plus-20120415-7
I made a video of this behavior, it is a low quality video, sorry for that.
[...]

From the User Guide:

"
400plus features a multi-page menu, where each page is dedicated to a certain task. To navigate the pages, use the front wheel or the ZOOM IN / ZOOM OUT buttons (notice the << and >> at the header). There is also a method to quickly access any page: press and hold the AV button down, then a list of all available pages will appear; now then use the front dial to select a page, and release the AV button to jump into it.
"

Hope this helps.

sizzlincok

Sergei
Hello, everyone.
Just want to share my latest code:
http://www.filefactory.com/file/1wdg7fpyeg8z/n/400d_firmware_hack_2012-04-05_zip
Additional functionalities, which this AUTOEXEC.BIN provide, are listed in Readme.txt file.
Mainly new things are: "preset white balance" - camera can save up to 5 custom wb measurements, and EAEB script now can be started with shutter release button.

Please note this bin doesn't have all the features of 400plus firmware.

I have a small minor suggestion.

Would you be able to code it to be possible to change the ISO via DP button when the eye is in the viewfinder, or when the screen is off?

I still use one of the old releases of the 400plus before the design, and I'm able to press the DP button to change the ISO when I'm looking through the VF.
I find it to be very convenient for a quick ISO jump, rather than spend the time to look or turn on the screen just to change the ISO.

I want to keep using your version of this, but I miss the ability to change ISO while the camera is up to my eye.

Sergei

sizzlincok, i need more info. Right now you can change ISO with right and left buttons when you look through viewfinder. DP button was used for jumping through intermediate ISOs. Do you want to use DP button for intermediate ISO when screen is off or you talking about be able to see ISO in viewfinder?

Sergei

Here is new AUTOEXEC with ISO in Viewfinder.
http://lh.rs/UDLk5xjEXMLo

Sergei

Another variant of AUTOEXEC with ISO in Viewfinder:
http://lh.rs/kiDQ5Catx5bl
This time it uses burst counter to display ISO.
1 is 100
2 is 200
4 is 400
8 is 800
6 is 1600
3 is 3200

And it works in P, Tv, Av, M and A-DEP modes.

« Previous Page Next Page »