Problem With T3I And 3.1.1

[Grampa_Jim]

I have what appears to be a serious issue with 3.1.1 premium and the T3i.  When setting up to do some exposures on comet Lovejoy, I went to Frame & Focus mode, then set the exposure and iso for a suitable brightness, say 2 seconds and 3200.  Going back to the Preview page, the camera info still showed 2" Tv and iso 3200, which is normal.  Then I set a bulb exposure of 30 secs. and 1600 in the exposure plan to get ready for a series of exposures.  Nothing changed in the camera info box, again normal.  BUT, when I either did a preview or started a capture series, the camera used the old setup (2" Tv and 3200) instead of switching to bulb mode and new iso.  The camera info still showed 2" Tv and 3200.  The info on the right counted down as if doing the bulb exposure, but the camera took a 2" exposure.

Further experimentation shows that once I take an exposure at anything other than bulb in any mode (Preview, Frame&Focus, Planetary), it will not subsequently accept a change to bulb.  I can set anything other than bulb in preview mode and it behaves normally (i.e. doing a preview or capture sets the camera appropriately), but it won't process a change to bulb.  The only way to get back to bulb is to unhook the camera and set it to bulb manually.  Then firing up 3.1.1 again, I can get a bulb exposure, but once I do an exposure at anything else it won't go back to bulb.   It seems that the software will not accept a change to bulb after setting the camera to anything else.

The problem does not occur when using the same camera in 3.0.3 premium, and it does not occur for an XSi for either 3.0.3 or 3.1.1, so it is exclusive to the T3i and 3.1.1.

The cameras, of course, were set on "M" mode.  I am using Windows 7 on a Dell Latitude E6410.

 

Any ideas?

Jim Knapp

 

[admin]

Guylain,

 

Well... this is embarrassing.    Clearing the cache fixed the problem.  I should have tried that immediately, as I now vaguely recall a previous problem a few years ago that also cleared up when I cleared the cache.  Getting senile in my old age, I guess.

 

Thanks for all your work on this great program.

Jim

 

Glad it worked.

[admin]

Odd for sure.  I remember about 6 months ago a similar behavior by one other user and I don't remember the outcome

 

Delete the cache folder in BackyardTEMP\cache and turn the camera on and make sure the camera is set to M on first start up after deleting the cache.

 

Send me the log files.

 

Regards,

[dts350z]

For what it's worth, I have two t3i and BYEOS 3.1.1 is rock solid in both one and two camera instances.

[Grampa_Jim]

Guylain,

 

Well... this is embarrassing.    Clearing the cache fixed the problem.  I should have tried that immediately, as I now vaguely recall a previous problem a few years ago that also cleared up when I cleared the cache.  Getting senile in my old age, I guess.

 

Thanks for all your work on this great program.

Jim