Jump to content

Recommended Posts

Advertisement (gone after registration)

Hi all, I have a bit of a weird problem and wondering if anyone has seen this or has any suggestions. I will be doing some additional testing as well, but here is the situation;

I grabbed a few images with my 262 and 50mm Summicron v5. The lens has 6-bit coding on it.  My past captures have correctly inserted the 50mm Summicron lens information in IPTC data. In this set of captures, the lens information says "Tri-Elmar-M 1:4/16-18-21 ASPH." instead of the proper (and previously recorded) "Summicron-M 1:2/50.  Settings were turned to automatic detection. 

I cannot determine why this might have happened, and would prefer it not happen again. At this point my plan is to simply use manual settings. I just have to remember to make the changes. 

Any other suggestions? Has anyone seen this behavior? This body and my limited lens set has performed without issue to this point. 

Thanks in advance for any thoughts or suggestions

Link to post
Share on other sites

Hello Michael,

Welcome to the Forum,

Have you checked to see that the code on the lens flange is still correct?  Are the little enclosures still coded as they should be? If the information picked up by the sensors is inaccurate then the sensors will transfer that wrong information to the camera.

Best Regards,

Michael

Link to post
Share on other sites

It's kind of one bit shift to the left.

a - Maybe the lens is not correctly mounted with the body pin in the lens groove ?

Summicron-M 50mm has code ... 100001

Tri-Elmar-M  16-18-21 has code .010000

 

b - Possible also, if the lens is correctly mounted and "clic".

Or dirt in front of the coding sensor and/or the lens code markings to be cleaned

 

Link to post
Share on other sites

1 hour ago, Michael Geschlecht said:

Hello Michael,

Welcome to the Forum,

Have you checked to see that the code on the lens flange is still correct?  Are the little enclosures still coded as they should be? If the information picked up by the sensors is inaccurate then the sensors will transfer that wrong information to the camera.

Best Regards,

Michael

I looked at a chart of the codes, as well as the lens itself and the camera side connection. Everything seems correct. I will look again for sure. 

 

Thanks you

Link to post
Share on other sites

38 minutes ago, a.noctilux said:

It's kind of one bit shift to the left.

a - Maybe the lens is not correctly mounted with the body pin in the lens groove 

Summicron-M 50mm has code ... 100001

Tri-Elmar-M  16-18-21 has code .010000

 

b - Possible also, if the lens is correctly mounted and "clic".

Or dirt in front of the coding sensor and/or the lens code markings to be cleaned

 

 

All good suggestions and it is interesting that this is one-bit difference.  I believe the lens was properly mounted, but that is something I will pay extra attention to. Obviously a bit concerning if it was not. 

I will check the contacts and cleanliness again. 

 

Thank you 

Link to post
Share on other sites

Well, I have done some additional checking of all connections, code, etc. and everything seems to be good. I've also tested it again and I cannot explain why, but it appears to be working correctly at this time. Very strange. I will keep an eye on things and chase the issue if it appears again. 

Thanks!

 

Link to post
Share on other sites

8 hours ago, microview said:

When I switch o my M262 I tend to press the info button showing mounted lens, battery and SD card status. If wrong lens showing I''d just remove and reclick (or look to see if 'manual' selected from a previous non-coded lens use)! 

Good tip. Thanks. It appeared I had the setting right, but obviously something was not. I also must have missed that the info button shows the lens attached. I will look for that. 

 

Cheers

Link to post
Share on other sites

8 hours ago, jaeger said:

I have never stopped hearing funny things about Leica... 

I bet, it's not the last one 😇

Since I use Leica, some "funny" (not so when those arrived) things happened all the time.

I think I'm not the only one, eh.

Live is "funny" or "boring" or what else depending on how we see/look (at) it.

Edited by a.noctilux
Link to post
Share on other sites

1 hour ago, sblutter said:

Why bother with coding, it doesn't have any effect on DNG's.  I turned it off.  I shoot primarily for print and do a lot of PP, then make jpg's from 'finals' for online galleries

I see some changes with some lenses in DNG files with coded and non coded lenses.

 

As I have more lenses without coding than with, I wanted to "know in my use", what are the impacts of this in my DNG files.

So I experimented with non coded lens with manuel setting to tell the body which lens is mounted,

then for comparing purpose, turned the "coding off" with same lens in DNG of course.

With many lenses in the wide and open wide, the changes are visible in vignetting and even some cured the "magenta/red edge" with wider lenses.

With 50mm upward, only Noctilux 1.0 can have it's profound vignetting corrected to less profound when I tell the M it's 1.0 Noctilux.

Other 50mm, I barely (if not) see some changes in the two DNG "coded" and "non coded".

The other that benefits from coding is Summilux-M 75mm, in vignetting like the Nocti.

Link to post
Share on other sites

On 8/1/2019 at 1:46 AM, a.noctilux said:

Live is "funny" or "boring" or what else depending on how we see/look (at) it.

Seriously I wouldn't feel bored if the M stop having problems.  May I wish you have more fun?  lol

Link to post
Share on other sites

On 8/1/2019 at 8:58 AM, sblutter said:

Why bother with coding, it doesn't have any effect on DNG's.  I turned it off.  I shoot primarily for print and do a lot of PP, then make jpg's from 'finals' for online galleries

I like to have it as searchable metadata.  Sometimes for a specific purpose, sometimes for curiosity, sometimes just for whatever. I fully understand it has no effect on DNG files, but like many other bits of data I think it has a place. 

Link to post
Share on other sites

On 8/1/2019 at 9:16 AM, jaapv said:

If you inadvertently press the release button when mounting the lens, it may well be seated incorrectly.

That is pretty much what I’ve settled on. I’ve grabbed a bunch if images since this and it works as expected. 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...