louiedi Posted May 13 Share #1 Posted May 13 Advertisement (gone after registration) I installed Firmware 2.2.2 into my Leica M11 and M11 Mono. Everything seemed to be working fine until I attached my 35mm Summicron-M f/2 V4. My Lens Detection on both cameras now read my 35mm version 4 Summicron as a "1.2 35mm" My f/2 doesn't even have 6 bit coding. When I transfer a photo taken with my f/2 Summicron to the app FOTOS my photo lists my f/2 Summicron as a NOCTILUX-M 1:1.2/35 ASPH. Has anyone else noticed this apparition? Has Leica tipped its hand? Welcome, dear visitor! As registered member you'd see an image here… Simply register for free here – We are always happy to welcome new members! 1 Link to post Share on other sites Simply register for free here – We are always happy to welcome new members! ' data-webShareUrl='https://www.l-camera-forum.com/topic/421237-firmware-222-and-my-35mm-summicron-m-f2-v4/?do=findComment&comment=5801694'>More sharing options...
Advertisement Posted May 13 Posted May 13 Hi louiedi, Take a look here Firmware 2.2.2 and my 35mm Summicron-M f/2 V.4. I'm sure you'll find what you were looking for!
sandro Posted May 13 Share #2 Posted May 13 As I learned from Jaap this may be caused by the position of a screw so the camera reads it as a lens code. I have this with my Summicron-M 2/35mm and Tele-Elmarit-M 2.8/90mm. Although neither is coded the camera sometimes recognizes these lenses corectly, sometimes erroneously recognizes the Tele-Elmarit-M as a 2.8/21mm. Therefor I edited the list of available lenses so I can more easily manually choose the correct one. Lex Link to post Share on other sites More sharing options...
hdmesa Posted May 13 Share #3 Posted May 13 (edited) Interesting. That's not available in the manual list of M lenses in the M11M, so it must be there in the firmware just hidden for now. I would report your finding via email to info [at] leica-camera [dot com]. Your next lens without 6-bit coding being given the same profile is normal. Uncoded lenses always get the lens profile of the last used lens – you must turn lens detection off or manually choose a different lens profile after attaching the uncoded lens. Edited May 13 by hdmesa 1 Link to post Share on other sites More sharing options...
DadDadDaddyo Posted May 13 Share #4 Posted May 13 9 minutes ago, hdmesa said: Your next lens without 6-bit coding being given the same profile is normal. Uncoded lenses always get the lens profile of the last used lens – you must turn lens detection off or manually choose a different lens profile after attaching the uncoded lens. This comes up often. I don't have the manual in front of me to check (and maybe folks don't read manuals these days anyway), but this is such fundamental information about the system's behavior that a way ought to be found to highlight it. Link to post Share on other sites More sharing options...
louiedi Posted May 13 Author Share #5 Posted May 13 12 minutes ago, hdmesa said: Interesting. That's not available in the manual list of M lenses in the M11M, so it must be there in the firmware just hidden for now. I would report your finding via email to info [at] leica-camera [dot com]. Your next lens without 6-bit coding being given the same profile is normal. Uncoded lenses always get the lens profile of the last used lens – you must turn lens detection off or manually choose a different lens profile after attaching the uncoded lens. I turned off Lens Detection but it keeps coming back on and defaulting to AUTO. Link to post Share on other sites More sharing options...
louiedi Posted May 13 Author Share #6 Posted May 13 23 minutes ago, sandro said: As I learned from Jaap this may be caused by the position of a screw so the camera reads it as a lens code. I have this with my Summicron-M 2/35mm and Tele-Elmarit-M 2.8/90mm. Although neither is coded the camera sometimes recognizes these lenses corectly, sometimes erroneously recognizes the Tele-Elmarit-M as a 2.8/21mm. Therefor I edited the list of available lenses so I can more easily manually choose the correct one. Lex When I attached my Summicron I have always input it manually. And it was working perfectly until firmware 2.2.2 Link to post Share on other sites More sharing options...
sandro Posted May 13 Share #7 Posted May 13 Advertisement (gone after registration) Can you still manually choose the lens? I just checked with the Tele-Elmarit-M which again was recognized as a 21mm lens, but I could manually correct it. I had this before I updated the firmware to 2.2.2. so I am not sure if is caused by the firmware update. Lex Link to post Share on other sites More sharing options...
louiedi Posted May 13 Author Share #8 Posted May 13 3 minutes ago, sandro said: Can you still manually choose the lens? I just checked with the Tele-Elmarit-M which again was recognized as a 21mm lens, but I could manually correct it. I had this before I updated the firmware to 2.2.2. so I am not sure if is caused by the firmware update. Lex No I cannot select the Summicron manually. I can only select OFF or AUTO. Link to post Share on other sites More sharing options...
sandro Posted May 13 Share #9 Posted May 13 I was afraid of that, since I have this as well with the Summicron 2/35mm, but that is not a problem since the camera seems to recognize the lens and detects it correctly. What I never understood is that with lens detection once it is AUTO it also says OFF. And when I use an uncoded lens like the Tele-Elmarit-M I can choose Manual M in the menu, but the Lens detection will say OFF. But that doesn't help you any further. Lex Link to post Share on other sites More sharing options...
lct Posted May 13 Share #10 Posted May 13 The 35/1.2 code has been added by firmware 2.2.2 i suspect and your 35/2 v4 must have a screw head in the way of the 6-bit sensor. Just a guess as my copy of the 35/2 v4 has a 6-bit coded flange so i cannot check anymore. I have no idea about the code of the 35/1.2 lens anyway. Link to post Share on other sites More sharing options...
IMAGEPOWER Posted May 13 Share #11 Posted May 13 vor 12 Minuten schrieb lct: The 35/1.2 code has been added by firmware 2.2.2 i suspect and your 35/2 v4 must have a screw head in the way of the 6-bit sensor. Just a guess as my copy of the 35/2 v4 has a 6-bit coded flange so i cannot check anymore. I have no idea about the code of the 35/1.2 lens anyway. The new Noctilux 1.2/35 will be presented this summer and the lens code has already been implemented. see https://leicarumors.com/2025/05/07/is-this-the-rumored-leica-noctilux-m-35mm-f-1-2-lens.aspx/ 2 Link to post Share on other sites More sharing options...
hdmesa Posted May 14 Share #12 Posted May 14 2 hours ago, louiedi said: I turned off Lens Detection but it keeps coming back on and defaulting to AUTO. Attaching a 6-bit coded lens always reactivates lens detection when you attach it. It does not revert to being off when you remove the 6-bit coded lens and use an uncoded lens. It’s terrible firmware logic on Leica’s part, but that’s how it works. Link to post Share on other sites More sharing options...
hdmesa Posted May 14 Share #13 Posted May 14 2 hours ago, DadDadDaddyo said: This comes up often. I don't have the manual in front of me to check (and maybe folks don't read manuals these days anyway), but this is such fundamental information about the system's behavior that a way ought to be found to highlight it. More than that, these are very poor firmware choices by Leica, and the firmware should be rewritten so that lens detection works more logically. Off should mean off and lens detection should not turn back on when attaching a coded lens. Or if lens detection is going to automatically turn on when attaching a coded lens, it should automatically turn off when removing the lens (provided the lens detection was set to off to begin with). 4 Link to post Share on other sites More sharing options...
lct Posted May 14 Share #14 Posted May 14 25 minutes ago, hdmesa said: Or if lens detection is going to automatically turn on when attaching a coded lens, it should automatically turn off when removing the lens (provided the lens detection was set to off to begin with). Exactly what it does on my early M11 provided lens detection is set to off before attaching the uncoded lens. Link to post Share on other sites More sharing options...
louiedi Posted May 14 Author Share #15 Posted May 14 3 hours ago, lct said: The 35/1.2 code has been added by firmware 2.2.2 i suspect and your 35/2 v4 must have a screw head in the way of the 6-bit sensor. Just a guess as my copy of the 35/2 v4 has a 6-bit coded flange so i cannot check anymore. I have no idea about the code of the 35/1.2 lens anyway. Yep… there is a screw head that falls directly on the 6 bit sensor. Hmmmmm. Wondering if there is a solution or workaround besides replacing the lens mount. 1 Link to post Share on other sites More sharing options...
lct Posted May 14 Share #16 Posted May 14 19 minutes ago, louiedi said: Yep… there is a screw head that falls directly on the 6 bit sensor. Hmmmmm. Wondering if there is a solution or workaround besides replacing the lens mount. The lens can be coded by Leica. Link to post Share on other sites More sharing options...
adan Posted May 14 Share #17 Posted May 14 1 hour ago, louiedi said: Yep… there is a screw head that falls directly on the 6 bit sensor. Hmmmmm. Wondering if there is a solution or workaround besides replacing the lens mount. No guarantees, but you can try applying a little Wite-Out™ correction fluid to the guilty lens screwhead. Which normally sits in a drilled-out "pit" just deep enough to 1) catch grime that can make it appear dark enough that the camera thinks it is a "black coding dot," but 2) protect the "whitener" so it won't rub off during lens changes once applied. https://www.walmart.com/ip/BIC-Extra-Coverage-Correction-Fluid-White-2-Count/186368725?classType=REGULAR Wite-Out™ has advantages over true "paints" in that it comes with its own little applicator-wand (no brush needed), dries very fast, and once powder-dry, can be scraped off with a fingernail where "overpainting" occurs, leaving only the embedded whiteness down in the depressed "pit" and in the screwdriver slot/cross of the screw itself. I have used it when, for example, an uncoded 28mm screwhead with some grime tries to persuade my digital M's that I have mounted a 90mm TE (they share the same framelines, so that is a common effect when the M compares both indicators to ID the lens). Also handy for patching minor scratches in my white photo frames (very useful stuff, which is why it is still around years after typewriters and wet-photocopy machines mostly faded away! 🤪 ) 1 Link to post Share on other sites More sharing options...
Steve Ash Posted May 14 Share #18 Posted May 14 (edited) Sent the lens back to Leica and claim the correct lens that matches the coding… Edited May 14 by Steve Ash 4 Link to post Share on other sites More sharing options...
lct Posted May 14 Share #19 Posted May 14 13 hours ago, IMAGEPOWER said: The new Noctilux 1.2/35 will be presented this summer and the lens code has already been implemented. Would you know this code by chance? Just curious. 1 Link to post Share on other sites More sharing options...
jakontil Posted May 14 Share #20 Posted May 14 Wow… the greatest leak in 2025… 1 1 Link to post Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now