Jump to content

M adaptor L on SL


arvin

Recommended Posts

Perhaps I didn't explain it properly. My apology.

 

The adaptor doesn't rotates or move, it's the join between the lens and the adaptor.

I was using the Noctilux 50/1 when this happened. If I try to rotate the lens, the camera will prompt for the message. 

I didn't really move or rotated it, it's just sometimes when I try to focus, I accidentally rotates the lens instead of the focus ring and therefore caused the movement a little bit.

 

I didn't experience this when I was using other lens. My 90/2.8 is not coded and didn't have this problem. However, I never really try anyway.

Link to post
Share on other sites

I've seen it before in a slightly different situation, where my leica-m lens that is a 25 years old cron 90 that is not 6-bit coded yet would pop up messages like you mention. This is related to the fact there is a screw on the lens mount, where the optical reader on the adapter tries to read the coding. Wiggling the lens in the mount by just a little, as little like a tiny fraction of a mm, may cause wrong readout. This is most likely happening to your leica-m lens when you move it a little by holding or even focussing. Different adapters optical readers respond differently with different tolerance of precision as I saw in my case by trying that cron on a few different adapters.

Link to post
Share on other sites

Advertisement (gone after registration)

The problem is the alignment of the black and white coding dots on the lens flange with relation to the sensors on the adapter (or the M body).

 

There is some variation on the amount of 'slack' when the lens is mounted and around the point it 'clicks' into place...... with some you can over-rotate by a few degrees and it is enough to confuse the sensor on the adapter/camera. 

 

Due to the black/white coding over 6 positions this is more of an issue with some lenses the others. 

 

I have a number of lenses which work fine on some cameras and regularly fail to register on others ...... it's all just a product of the rather flakey system Leica adopted to identify M lenses on their digital bodies. 

 

I doubt if you will find any 'fault' as such, but a change of adapter may solve it as no two are exactly the same..... but the problem is the coding of the 50/1.0 ...... which must have been added at some later stage as it pre-dates coding at manufacture. 

  • Like 1
Link to post
Share on other sites

The problem is the alignment of the black and white coding dots on the lens flange with relation to the sensors on the adapter (or the M body).

 

There is some variation on the amount of 'slack' when the lens is mounted and around the point it 'clicks' into place...... with some you can over-rotate by a few degrees and it is enough to confuse the sensor on the adapter/camera.

 

Due to the black/white coding over 6 positions this is more of an issue with some lenses the others.

 

I have a number of lenses which work fine on some cameras and regularly fail to register on others ...... it's all just a product of the rather flakey system Leica adopted to identify M lenses on their digital bodies.

 

I doubt if you will find any 'fault' as such, but a change of adapter may solve it as no two are exactly the same..... but the problem is the coding of the 50/1.0 ...... which must have been added at some later stage as it pre-dates coding at manufacture.

Thanks.

 

Most of my old M lens has no 6 bit code coded. So yeah.....I was just curious why it does to one but not the other. :)

 

 

my name is Arvin and I am not a photographer. :)

Sent from my iPhone using Tapatalk

Link to post
Share on other sites

  • 7 months later...

I'm reviving an old thread, it appears, but I may have encountered a similar problem with the M adapter-L on the new CL.  My 35mm v4 f2 Summicron, coded, and working fine on M bodies auto-codes as 35mm pre-Asph Summilux f1.4.  Has anyone else encountered a situation in which the lens codes improperly, only if used iwht the adapter?  What was the fix?  Any of you SL owner own a CL, now?

Edited by norm_snyder
Link to post
Share on other sites

I'm reviving an old thread, it appears, but I may have encountered a similar problem with the M adapter-L on the new CL.  My 35mm v4 f2 Summicron, coded, and working fine on M bodies auto-codes as 35mm pre-Asph Summilux f1.4.  Has anyone else encountered a situation in which the lens codes improperly, only if used iwht the adapter?  What was the fix?  Any of you SL owner own a CL, now?

 The 6 bit coding on for the 35/2 and 35/1.4 is sufficiently different that the 'over-rotation' issue cannot explain it. 

 

Perhaps one of the 6 sensors on adapter is a bit dodgy ....... but it is hard to tell where the issue lies until someone else with a coded 35/2 tries it with an adapter on the CL ...... or you try someone elses adapter......

 

At the moment there are too many variables to pinpoint where the problem lies ....

Link to post
Share on other sites

I have my SL, 24/90, and the Leica M-L adapter for about a month. I can mount the 24/90 just fine with just a normal twist. But, the M-L adapter requires much more force.  Is this what your experience is with the M-L adapter?

Edited by myuen888
Link to post
Share on other sites

I have my SL, 24/90, and the Leica M-L adapter for about a month. I can mount the 24/90 just fine with just a normal twist. But, the M-L adapter requires much more force.  Is this what your experience is with the M-L adapter?

 

 

Same here - I think this is how it is supposed to be from Leica's side. Possibly different materials used for the SL-lenses (including being water sealed) versus the Leica M-L adapter? I cannot check since I have neither with me now.

Link to post
Share on other sites

same as meerec described already but with a uncoded Summilux 75mm. Send the lens recently to Leica for coding, since then did not appear again.

When using my Voigtländer 16mm Heliar with the M-L adapter this "unknown lens" occured always, was not possible to really work with that lens. Bought then a Novoflex M-L adapter (w/o optical sensors) and no problem anymore.

 

cheers

thua

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

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