Eos 400d ( Rebel XTI )

PhilHornby

2

Re: Transcend WiFi SD access

« Reply #1800 on: 01 / October / 2013, 16:46:56 »

Advertisements

Quote from: me on 25 / September / 2013, 12:52:36

Maybe there's a mechanism in Linux to force the OS's view of the file system to be refreshed? ... the only thing I could think of, was to umount /dev/mmcblk0p1 and then re-mount it (on /mnt/sd). Unfortunately, every time I try it, the IP connection drops. Sometimes the link comes back up, without having to power-cycle, but I've not seen the mount command work yet (it gives "Invalid argument").

It turns out that there's a script on the card that runs once a minute - that does indeed dismount and re-mount the card. It uses non-default options on the mount command, so it succeeds more often than my manual attempt (though not 100%

) In any case, this is reliant on the other party doing something similar in order to ensure that it's reading up-to-date information.

The following links have some interesting insights into this card and its software:-

https://forum.openwrt.org/viewtopic.php?id=45820
http://dmitry.gr/index.php?r=05.Projects&proj=15&proj=15.%20Transcend%20WiFiSD

http://www.fernjager.net/post-8/sdcard

Logged

repeater

22

Re: Eos 400d ( Rebel XTI )

« Reply #1801 on: 02 / November / 2013, 06:53:26 »

Can anyone help me with a problem I am having?

I am finding that when I use the EAEB script, the camera runs indefinately rather than using the number of frames set. I have it setup as follows...

2s delay - yes
frames - 3
step - +2
direction - +/-
Bulb min 1/4000
Bulb max 15"

I would expect this to take 3 shots - 1 at the base exposure and then 1 each side of it at +2 and -2. However the camera just continues to fire well beyond the 3 frames.

I am sure this is not a bug but operator error but can anyone help me with what I am doing wrong? I am using the last release build 20131404-04.

Thanks!

Logged

eduperez

426

Re: Eos 400d ( Rebel XTI )

« Reply #1802 on: 02 / November / 2013, 19:39:54 »

Quote from: repeater on 02 / November / 2013, 06:53:26

Can anyone help me with a problem I am having?

I am finding that when I use the EAEB script, the camera runs indefinately rather than using the number of frames set. I have it setup as follows...

2s delay - yes
frames - 3
step - +2
direction - +/-
Bulb min 1/4000
Bulb max 15"

I would expect this to take 3 shots - 1 at the base exposure and then 1 each side of it at +2 and -2. However the camera just continues to fire well beyond the 3 frames.

I am sure this is not a bug but operator error but can anyone help me with what I am doing wrong? I am using the last release build 20131404-04.

Thanks!

I just tried the EAEB script, using the same parameters, and it took 3 shots, as expected.
Could you post what parameters (AE mode, shutter speed, aperture, ...) where you using, please?

Logged

hadede

3

Re: Eos 400d ( Rebel XTI )

« Reply #1803 on: 07 / November / 2013, 02:03:28 »

Hello,
I have recently purchased a Sigma Contemporary 17-70 F2,8-4 DC and I have some problems with it. I try to rule out all possible causes, and one of them might be the custom firmware... Is it possible that the 400plus firmware has anything to do with it?

Here is my problem description:
Usually the camera CF led blinks on insert battery / closing CF door / attaching lens. This also happens if the cam is turned off. In this case it's the only action of the cam which remains turned off. (With 400plus firmware on the CF card the blue led blinks as well)
If I attach my new lens the led(s) blink, then I hear a dim noise (which seems to be the image stabilizer of the lens) and then it seems the cam "restarts", because the leds blink again and the noise is there again and this happens in an infinite loop until the battery is dead...
If I turn the camera on, the lens works as expected, but on turning it off, the same looping starts again. But in this case, the ON-led of the camera stays and the camera does not react on any input, so only removing the battery helps.

This happens regardless of any custom firmware on the CF card (without it it's of course only the CF led blinking). AFAIK the hack installed in the camera is only a hook to dynamically load custom firmware. So I assume, that it has nothing to do with it, but I just want to make sure. I also tried reflashing the 1.1.1 Firmware, but it seems the hook is not removed by this, so I do not know if it would work with stock firmware.

The lens works normal on a newer EOS model which I had the chance to try it on. The local Sigma service suggested trying it on other 400Ds (but I don't know anyone with this model) and trying other stabilized lenses on my camera, as he said the camera might have issues with stabilized lenses. Other than that I can only send it to the service (or return it, as it's new... but I really would like to keep this lens as it fits my needs...).

Sorry for the elaborate post and thanks in advance for any answers.
Best Regards

Logged

0xAF

220

Re: Eos 400d ( Rebel XTI )

« Reply #1804 on: 07 / November / 2013, 03:02:07 »

Quote from: hadede on 07 / November / 2013, 02:03:28

Hello,
I have recently purchased a Sigma Contemporary 17-70 F2,8-4 DC and I have some problems with it. I try to rule out all possible causes, and one of them might be the custom firmware... Is it possible that the 400plus firmware has anything to do with it?

As far as I know, there are other Sigma lens that have problems with Canon DSLRs and in particularly with 400D.
From what you've described, my opinion is that the lens are somehow incompatible with your 400D.
If you have problems without the CF card too, then this has nothing to do with the hack itself.
The so called reversing if the boot hook will do nothing more for you and I believe it will not resolve the issue.

For the time I've been around the hack, I've seen some 400D's that are somehow different than others... my guess is that the hardware somehow differs and the software handles it a bit different. Thought you cannot see any difference as a user, there were some single reports of strange things on some particular camera.
If I'm right in my believes, then it is the same for the Lens... some 400D's can have troubles with a particular lens and others can work with the same lens.

Logged

// AF

hadede

3

Re: Eos 400d ( Rebel XTI )

« Reply #1805 on: 07 / November / 2013, 03:44:52 »

Thank you for your reply!
It was my assumption as well, that this is not related to the 400plus SW. With a blank CF card only the boot hook is left, which should not really affect anything. (BTW. Is removing the boot hook even possible? I tried flashing firmware 1.1.1 (which isn't available on my local canon website any more, had to find it on canon.jp...) but the boot hook stayed, and the 400plus page also notes that reversing is not possible.)

So my options are quite limited:

if it's the camera's fault, a replacement will not work.
lens defect can probably be ruled out, so the replacement will be identical and service will not detect any problems
if it's just incompatible for whatever strange reason, it won't work either. hoping for a sigma firmware update is no option as sigma isn't aware of any problems and will probably not care about some old 400Ds which have strange problems.

I think the only option is to return it...
Best Regards

Logged

0xAF

220

Re: Eos 400d ( Rebel XTI )

« Reply #1806 on: 07 / November / 2013, 03:50:11 »

Quote from: hadede on 07 / November / 2013, 03:44:52

(BTW. Is removing the boot hook even possible? I tried flashing firmware 1.1.1 (which isn't available on my local canon website any more, had to find it on canon.jp...) but the boot hook stayed, and the 400plus page also notes that reversing is not possible.)

It is possible, you should be able to find some older versions of autoexec.bin here in this thread which can undo the hook (IIRC). On the other hand, we can put such option in 400Plus, but I believe it was discussed before and it seems such option can bring more troubles than benefits.

Logged

// AF

hadede

3

Re: Eos 400d ( Rebel XTI )

« Reply #1807 on: 07 / November / 2013, 04:50:34 »

the only thing I found is:
http://chdk.setepontos.com/index.php?topic=3290.msg67715#msg67715
but the link is already dead and I doubt my problem is related to 400plus

I've also now created a log file via the 400plus dev menu, but as I don't know what all that stuff means, I cannot tell if there's anything relevant in there... There are some sequences which are repeating, maybe you can spot sth suspicious?

log000.log (15.06 kB - downloaded 28 times.)

Logged

0xAF

220

Re: Eos 400d ( Rebel XTI )

« Reply #1808 on: 07 / November / 2013, 06:22:09 »

I do not see anything important in the log file.

Logged

// AF

Sergei

114

Re: Eos 400d ( Rebel XTI )

« Reply #1809 on: 10 / November / 2013, 20:47:13 »

Quote from: hadede on 07 / November / 2013, 04:50:34

the only thing I found is:
http://chdk.setepontos.com/index.php?topic=3290.msg67715#msg67715
but the link is already dead and I doubt my problem is related to 400plus

If you still want to remove the boot flag you can use this autoexec file:
https://hostr.co/vG9VL8Gd5IxO
This file also has a option to enable shutter release on "any" IR remote if anybody wants to try it out.

Logged