Eos 400d ( Rebel XTI )

nxb

2 things well maybe 3.

1. Latest nightly build and I don't see the DOF calculator on the scripts page. I scroll and it just goes back to the beginning.
2. Long exposure calculator doesn't let me change any of the settings. I tried the wheel and left/right, I have a feeling I'm doing something wrong.

I already tried to delete the settings file but no change.

I checked out spot metering and it doesn't follow the AF points, just stays in the center. Seems like you can file selective spot metering along with multi spot metering. If that gets solved I think moving the spot will be trivial to implement. I got a 45deg screen and it works much better than the 180.

Also, sergei... file factory never has any free download spots. Can you mirror it somewhere else.

Sergei

Here is another link:
http://localhostr.com/file/qIR4fSx/400d_firmware_hack_2012-04-05.zip

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.

Super awesome. I always liked your versions of the firmware. They've always remained very clean.
You integrated the boot flag removal for the hack? Love it.

The menus in 400plus are just way too crowded and there's just too much going on for me.

nxb

Ok got the DOF calculator after trying sergei's version. Long exposure still baffles me.

The quick shutter was great. Wish it was the * button instead of set as that button is useless and set is a little hard to reach.

Sergei

Yes, * button would be great. But this button doesn't generate any events when pressed, so it's impossible to make hook to it. Maybe Eduperez or 0xAF know how to get this button working in firmware.

0xAF

Sergei,
if i understood correctly, you are looking for these:
(400Plus main.h)

          GUI_BUTTON_ZOOM_IN_PRESS       = 0x819,
          GUI_BUTTON_ZOOM_IN_RELEASE     = 0x81A, // DISP_RELEASED // idle handler shows them w/o a reason, could be disp_release
          GUI_BUTTON_ZOOM_OUT_PRESS      = 0x81B,
          GUI_BUTTON_ZOOM_OUT_RELEASE    = 0x81C, // DISP_RELEASED // idle handler shows them w/o a reason, could be disp_release

as the comments show and if i remember correctly - 0x81A and 0x81C can be seen without a obvious reason in the log file... we need to understand what they mean, besides the names we gave them.

as for the 0x819 and 0x81B - they seems to work as expected.
the Star Button should be 0x81B.

just one thing i found long time ago, the GUI_MODE (GUIMode) matters... if you are in the "wrong" GUIMode, the codes are different... for now we are using GUIMode == 0xFF, and these codes should work.

Edu will correct me if I'm missing something, or if I forgot something...

EDIT:
BTW I think we catch them in the menu_event_handlers. These are the handlers that you give to CreateDialogBox().
I'm not sure if they can be hooked in the Intercom handler.

EDIT2:
Now I realized that this will not help you if you want to hook the star button at the main screen (OLC)

eduperez

nxb
1. Latest nightly build and I don't see the DOF calculator on the scripts page. I scroll and it just goes back to the beginning.

DOF calculator was added in release r1194; you'll need nightly preview 400plus-20120408-r1199.zip or later.

nxb
2. Long exposure calculator doesn't let me change any of the settings. I tried the wheel and left/right, I have a feeling I'm doing something wrong.

Not all fields in the long exposure calculator can be edited; please have a look to the user guide preview: http://code.google.com/p/400plus/wiki/UserGuidePreview#Long_Exposure_Calculator.

nxb
I checked out spot metering and it doesn't follow the AF points, just stays in the center. Seems like you can file selective spot metering along with multi spot metering. If that gets solved I think moving the spot will be trivial to implement. I got a 45deg screen and it works much better than the 180.

400plus just activates spot metering, then it works as designed by Canon; if the camera does not make it follow the AF points, then we will probably not be able to make it work that way.

sizzlincok
The menus in 400plus are just way too crowded and there's just too much going on for me.

We're already aware of that; perhaps you would like to add your voice here: http://code.google.com/p/400plus/issues/detail?id=202.

nxb
The quick shutter was great. Wish it was the * button instead of set as that button is useless and set is a little hard to reach.

The * button is used to control the AF, if you set C.Fn-4 to anything other than the default "AF/AE lock".

Sergei

0xAF
as for the 0x819 and 0x81B - they seems to work as expected.
the Star Button should be 0x81B.

just one thing i found long time ago, the GUI_MODE (GUIMode) matters... if you are in the "wrong" GUIMode, the codes are different... for now we are using GUIMode == 0xFF, and these codes should work.

Yes, you're right. Also, if GUIMode is MENU_MODE, Zoom-in (0xA7) and Zoom_out (0xA😎 buttons can be seeing in IntercomHandler. And you can check if those buttons were pressed in or released. What I like to find, what enables or disables buttons for current GUIMode. Or at least what sends them to IntercomHandler.

0xAF

Sergei
What I like to find, what enables or disables buttons for current GUIMode. Or at least what sends them to IntercomHandler.

I tried to find what enables/disables the buttons in the different GUI_MODEs, and what assigns them different codes ...
no luck so far ... perhaps i should try to find them again.
As for what sends them to the intercom:
We have the MainCtrl (MC) task reversed: http://code.google.com/p/400plus/source/browse/trunk/mainctrl.c#109
the task calls MC_T_1_5() for all events of type 1 to type 5, the buttons are type 2.
http://code.google.com/p/400plus/source/browse/trunk/mainctrl.c#139

so we our button handler assigned to type 2 (MC_BUTTON)
http://code.google.com/p/400plus/source/browse/trunk/mainctrl.c#14
from there you can catch some important events like:
MC_BUTTON_BATTERY_DOOR_OPEN
MC_BUTTON_CARD_DOOR_OPEN
MC_BUTTON_POWER
MC_BUTTON_HALF_SHUTTER
MC_BUTTON_FULL_SHUTTER
MC_BUTTON_JUMP
MC_BUTTON_TRASH

This routine is rewrite of the original one, and we added code only for the JUMP button (and some debug maybe).
so when this routine finish, it calls MC_T_Button(), which in turn sends the button codes to Intercom. So if you are looking for who sends the buttons to the intercom, these should be a good start.

note: Please be aware that comments and debugs starting with "AF:" does not mean AutoFocus, they mean 0xAF 😀 (sorry for this confusion)

Sergei

We must talking about different IntercomHandlers. I always thought IntercomHandler (0xFFA5D3E0) sends codes and data to MC. I could be wrong. Thanks for the info. I will check it sometimes later today.

0xAF

Sergei
We must talking about different IntercomHandlers. I always thought IntercomHandler (0xFFA5D3E0) sends codes and data to MC. I could be wrong. Thanks for the info. I will check it sometimes later today.

Hmm... i was talking from my memories, and i may be totally wrong about who sends to whom the message ...
so you are right i guess... MC sends to IC.

Sergei

Looks like SendToIntercom sends messages to outside unit (maybe MPU) and IntercomHandler receives messages from that unit.
I see you got "jump" and "trash" buttons in MC_T_Button function. Can you still use those buttons when cammera in OLC mode?

eduperez

Sergei
Looks like SendToIntercom sends messages to outside unit (maybe MCU) and IntercomHandler receives messages from that unit.
I see you got "jump" and "trash" buttons in MC_T_Button function. Can you still use those buttons when cammera in OLC mode?

Yes; in fact, latest version can configure an action on the JUMP button.

0xAF

Sergei
Looks like SendToIntercom sends messages to outside unit (maybe MPU) and IntercomHandler receives messages from that unit.
I see you got "jump" and "trash" buttons in MC_T_Button function. Can you still use those buttons when cammera in OLC mode?

From what I see there, the SendToIntercom writes some data into specific memory addresses, which are not in MMIO area.
So it seems it does not directly talk to another MCU/DSP/whatever, only writes to the memory, which seems to be an OS memory (VxWorks), not the Canon's software... Though there are some other MPU related stuff which are calling the SendToIntercom().
It could be that some interrupts reads and writes to that memory. The debug strings shows that the module which is in control of this memory is named "virtualSTATE", which only confirms that this is software based emulation... but what writes and reads in that memory i could not find either.

BTW, do you know what is this FlyingKeeper thing ?

Sergei

No, I don't know what the FlyingKeeper is.
The task_MainCtrl receives "Jump" and "Trash" buttons from SendButtonToMC all the time regardless GUI_Mode. But "Zoom_in" and "Zoom_out" comes from IntercomHandler when camera is not in OLC mode. So I guess it's impossible to make hooks to those buttons in OLC mode without knowing what operates IntercomHandler.

scharrow

welcome. is it possible to do more than 250 pictures in the Time-lapse I tried several memory cards of 1GB and 4GB but still remained a number of photos the same.

eduperez

scharrow
welcome. is it possible to do more than 250 pictures in the Time-lapse I tried several memory cards of 1GB and 4GB but still remained a number of photos the same.

250 is the maximum of "limited" shots 400plus will do (*), regardless of card capacity; you can also select "No limit" as the number of shots, and the camera will fire endlessly (until manually stopped or card runs out of space).

(*) 250 shots is a self-imposed limit, nothing prevents us from raising it; please, add a "feature request" at http://code.google.com/p/400plus/issues/entry if you feel that limit should be larger.

scharrow

I did not notice this before with ,,no limit''. but I think I could use more than 250 frames. I've tried to deal with time-lapse, unfortunately, only when connected to a computer. solution would be a good opportunity to set a larger number of frames or time the camera would work. thanks

eduperez

Good evening, ladies and gentlemen.

We have a new release ready for consumption; but before we make the official announcement, we would like to let a couple of days pass, so people can test it. Below you can find the list of enhancements and new features; the updated user guide can be found at: "http://code.google.com/p/400plus/wiki/UserGuidePreview", and the most updated version at "http://code.google.com/p/400plus/downloads/list?q=label%3ANightlyBuild".

We hope you enjoy it!

* Usability improvements
Â· New language system: now 400plus can be translated to languages not supported by the camera.
Â· Menus have been reordered, everything should be easier to find now.
Â· JUMP and TRASH buttons are now configurable (on the main dialog).
Â· DISP button can be used to change brightness in small increments.
Â· Use UP to display current ISO in the viewfinder (without changing it).

* New scripts
Â· Long exposure script, with long exposure calculator included.
Â· Depth-of-field and hyperfocal calculator.
Â· ISO and Flash AEB.

* Enhancements to scripts
Â· Strict scheduling and time-lapse calculator added to the intervalometer.
Â· Bracketing direction configuragle for EAEB.
Â· LCD brightness and blinking LED during scripts are now configurable.
Â· Restore camera before shut down, and check for card space before each shot.

* New and updated translations
Â· Finnish.
Â· Russian.
Â· Polish.
Â· The translation procedure has also been made easier.

eduperez

Here you are... release 20120415-0 (aka "Easter Release") is out:

First of all, A Word of Warning (that everybody should read) at http://code.google.com/p/400plus/wiki/AWordOfWarning.
Source at http://400plus.googlecode.com/files/400plus-20120415-0.src.zip.
Binary at http://400plus.googlecode.com/files/400plus-20120415-0.bin.zip.
Updated user guide at http://code.google.com/p/400plus/wiki/UserGuide.
And the list of changes: http://code.google.com/p/400plus/wiki/ChangeLog.

Thanks to everybody involved!

« Previous Page Next Page »