Mirror lockup on Canon 600D

[rtemen]

I have an unmodifyed 600D.
I have BYE 3.1.13 premium edition.

I want to take 200 bias shots and would feel better if the mirror would stay locked up during all these shots.

I cannot find out how to accomplish this.
It looks like some people say it can be done, but when I try to do it, it will not work.
So, is it possible or not?

If so, could you send me the settings both in BYE and maybe in the camera as well.

Thanks,

Rich

[astroman133]

My T5i has a mirror lock setting in the Custom Functions menu. When I enable this option I press the shutter once to lock up the mirror and then press the shutter a second time to take a picture. After the picture is taken, the mirror flips down. The only gain is the delay between the first and second shutter presses can be such that any vibration from mirror flip has settled down.

It does not seem as though this is what you want. I am guessing that you want to avoid the wear and tear on the mirror mechanism when taking all those bias frames. Vibration should not be an issue because no light is reaching the sensor during bias frames.

I don't even use bias frames. This is because I use dark frames with both my lights and my flats. This makes bias frames unnecessary.

Since the camera can't do what you want, it is unlikely that BYE can do what you want.

I am not expecting upgrading from your 5 year old version of BYE will provide the desired behavior. In fact I am pretty sure that it will not. However, getting support for software that was released in 2017 and has been updated many times since then is unlikely. You should strongly consider updating to 3.2.2, which is itself over a year old.

[admin]

As mentioned above, you can't accomplish what you are seeking to do. Mirror lock up, by design, is only per single exposure, and you'll end up with the same number of shutter actuation. This is not a software issue, this is a physical limitation of how the internal camera mechanics works, it's built into the camera firmware, not external firmware, and there is no API to circumvent this behavior sadly.