Can you show me your lens profiles?

[crons]

Advertisement (gone after registration)

Hello. If you have an up to date M10R, can you take a picture of your lens profiles here and let me see how yours looks where it says 35f2 ASPH

This is firmware v20.20.47.37 

Thanks. 

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!

[Advertisement]

The Leica Q3 is available for pre-order at B&H Photo Video and Adorama

[crons]

2 minutes ago, Al Brown said:

Mine looks exactly identical to yours on my M10-R BP with latest FW.

Where is the 11673? In another separate entry?

[crons]

5 minutes ago, Al Brown said:

If there is no 11673 it means ALL 11673 are CODED and you cannot choose the 6-bit code for a coded lens.

Seems like it's a common issue with some 11673 not being recognized automatically. It's fine. 

https://www.l-camera-forum.com/topic/276285-m-10-not-recognising-my-summicron-352/#comments

Edited June 3, 2024 by crons

[crons]

15 minutes ago, Al Brown said:

In the previous Cron 35 (ASPH V1) later ones were coded and earlier were not, so there still is an option to select this lens from the menu in case you get an uncoded sample.
Not so with Cron 35 II (ASPH V2).

Yes the ASPH V2 11673. Not being recognized. So I choose the 11879 manually. 

[crons]

3 minutes ago, Al Brown said:

Don’t stress too much about coding for 35 Cron ASPH. It does not do any magical wonders or miracles, just some slight vignette corrections and perhaps other very minor things like EXIF data (no effect on the image with the latter).

Doesn't seem to be any hardware issues with the camera. For some reason a lot of people here reported the same issue of the coded 35 cron Asph not being recognized by their M10, while other coded lenses are auto recognized no problems. 

[lct]

Not sure how the camera could recognize the lens as 35/2 asph v2 given that it has the same code as the asph v1 (011110). I suspect there is no lens profile for v2 then, but the v1 profile should be recognized automatically. The OP might wish to check that the flange of the lens and the lens mount are clean enough to avoid coding errors. Just a guess as i have no experience with M10 cameras.

[crons]

Advertisement (gone after registration)

2 hours ago, lct said:

Not sure how the camera could recognize the lens as 35/2 asph v2 given that it has the same code as the asph v1 (011110). I suspect there is no lens profile for v2 then, but the v1 profile should be recognized automatically. The OP might wish to check that the flange of the lens and the lens mount are clean enough to avoid coding errors. Just a guess as i have no experience with M10 cameras.

There no dirt. Lens is brand new. Camera is clean. Other coded lenses are recognized. It's an issue with this lens that I am now just aware of. If you have an M10 your 35 asph may not be recognized. It's a mystery. 

[crons]

2 hours ago, Al Brown said:

This is of no real help but just to mention I have had zero problems with M10-R and recognition of 35 Crons.

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!

The only thing for me to try is update the firmware which I don't want to do. No guarantee that will fix it plus it may bring other issues I didnt have. 

Mine also comes up as 35 summicron because I left it chosen in the manual menu. So there it stays. 

This thread died so it makes me think the most recent firmware updates might have fixed the issue 

 

 

Edited June 3, 2024 by crons

[crons]

I asked Chatgpt to search the internet for this issue. It says it is likely outdated firmware. So now the dilemma. Update or leave it in manual. Here is what it said 

 

The issue of the Summicron 11673 lens not being auto-detected on the Leica M10-R has been noted by several users. This problem generally arises because the M10-R's firmware may not include this particular lens in its database, thus preventing both automatic detection and manual selection. Users on Leica forums have reported similar issues with other lenses, suggesting that some lenses might have been inadvertently left out of the firmware updates [[❞]](https://www.l-camera-forum.com/topic/376073-m10r-not-auto-detecting-24-lux/) [[❞]](https://www.l-camera-forum.com/topic/324505-voigtlander-35mm-f2-apo-lanthar-asph-or-leica-35mm-f2-summicron-m-11673/).

 

One user highlighted that even though the lens has 6-bit coding, it is not recognized by the camera. Cleaning the contacts on both the lens and the camera did not resolve the issue. It appears that the lens was not listed in the camera's internal database, and contacting Leica customer service confirmed that the fault lies with the camera's firmware, not the lens itself [[❞]](https://www.l-camera-forum.com/topic/376073-m10r-not-auto-detecting-24-lux/).

 

For those experiencing this problem, it's recommended to check for any available firmware updates for the Leica M10-R and to contact Leica customer support for further assistance. They might offer a more specific solution or plan an update to address this issue in the future [[❞]](https://www.l-camera-forum.com/topic/376073-m10r-not-auto-detecting-24-lux/) [[❞]](https://www.l-camera-forum.com/topic/324505-voigtlander-35mm-f2-apo-lanthar-asph-or-leica-35mm-f2-summicron-m-11673/).

[lct]

Not sure if my aging HI can compete with AI but i can only repeat what i asked in another thread below.

« Sorry but there is something i don't understand here. The 35/2 asph v2 cannot be detected as such since it has the same 6 bit code as the v1 of this lens. So the mystery is not there IMHO. It is why v1 is automatically detected by the camera and not v2 given that they have the exact same 6 bit code and the camera has not other means to recognize them. Too bad i don't own a v2 as i would check it on my M11. Did you ask M11 users what they think of this? Just curious. »

Edited June 4, 2024 by lct

[crons]

2 hours ago, lct said:

It is why v1 is automatically detected by the camera and not v2 given that they have the exact same 6 bit code

Don't know. I have the v2. The 50 summicron is detected without issues. This problem has been discussed here since 2017 about the 11673 not being detected on some M10 cameras. 

I will just leave it selected as 11879. Other than sending it to Leica for months just because one lens isn't detected out of all the coded lenses.

At this point I have no idea why this is an issue. Leica knows since they've fixed it once we send the cameras to them.  

Updating the firmware does nothing. 

Edited June 4, 2024 by crons

[lct]

7 minutes ago, crons said:

Updating the firmware does nothing. 

As somewhat expected since there is no specific profile for the v2 of this  lens. Would be interesting to know if it is detected on the M11. I suspect it is, since my v1 is detected with the exact same coding on M11. It could mean that M10 series are more sensitive to possible errors in painting or otherwise locating coding pits on the lens. Just a guess.

[crons]

36 minutes ago, lct said:

As somewhat expected since there is no specific profile for the v2 of this  lens. Would be interesting to know if it is detected on the M11. I suspect it is, since my v1 is detected with the exact same coding on M11. It could mean that M10 series are more sensitive to possible errors in painting or otherwise locating coding pits on the lens. Just a guess.

This is an M10 issue. No need to ask M11, M240 or M9 users.

It only happens with this 35 summicron. All other lenses are detected just fine. One thread the guy went back to the store and the manager unpacked another brand new 35 cron and it didn't detect that one either. But on the M10 at the store it would.

This issue makes no sense. 

I received a PM from a poster who had to send it in and they fixed it. What they did I don't know. 

Since it only happens with this particular lens I will keep it with the 11879 profile selected on Manual and leave it like that. I don't think this is reason enough to send a camera back to Leica. I shouldn't have updated it either. Curiosity killed the cat. I decided to follow their logic (even though it makes no sense since the lens was released 2 years before the version of the firmware I had. 

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!

Edited June 4, 2024 by crons

[lct]

"Older firmware versions do not know lenses that have not been developed.." It is not exactly the point here since v1 and v2 are the same lens as far as 6 bit coding is concerned. Anyway i should have the opportunity to test v2 on the M11 in a near future and will report if i find something interesting, which would surprise me as i'm pretty sure v2 will be detected automatically the same way as v1 is on the M11.

Edited June 4, 2024 by lct

[crons]

On 6/3/2024 at 11:31 PM, Al Brown said:

ATTENTION!!! Latest firmware for M10-R is 30.22.23.34
 

I updated the firmware. Good news is nothing bad happened to the camera. But it does nothing to address this issue. 

Seems to me the only option is sending the camera to Leica. No way. 

But i am curious to find out what the problem is and why this particular lens. Comparing the coding between this and the 50 cron the paints used seem to be identical ro me eyes. And why it works in some cameras and not others. If the Lena detection was faulty in my camera it would be every lens. What is it about this particular lens. 

Edited June 4, 2024 by crons

[BradS]

On 6/4/2024 at 11:07 AM, crons said:

.... If the Lens detection was faulty in my camera it would be every lens. What is it about this particular lens. 

 

Brainstorming ... maybe there is something about the way that the pits are shaped? Maybe the bottom of one or more of the pits is not flat enough or is tilted a bit? 

 

It would be really helpful (but I realize probably not possible) to know what the camera thinks it sees when the problematic lens is mounted. If we knew the code that the camera thinks it is reading then it might be a valuable clue.

 

[lct]

27 minutes ago, BradS said:

[...] It would be really helpful (but I realize probably not possible) to know what the camera thinks it sees when the problematic lens is mounted. If we knew the code that the camera thinks it is reading then it might be a valuable clue.

If any code were detected the exif data would tell the corresponding lens ID i guess or, more probably, no code is detected in which case the exif data should say "uncoded" or something like that. Just a guess as i have no experience with M10 cameras but knowing the exif data would help i suspect.

[crons]

1 hour ago, BradS said:

 

Brainstorming ... maybe there is something about the way that the pits are shaped? Maybe the bottom of one or more of the pits is not flat enough or is tilted a bit? 

 

It would be really helpful (but I realize probably not possible) to know what the camera thinks it sees when the problematic lens is mounted. If we knew the code that the camera thinks it is reading then it might be a valuable clue.

 

Not sure because when the same lens is mounted on an M240 or M9 they work. Another poster had the store try  2 brand new ones and they didn't work on his M10, but they did on the store's M10. His other lenses worked just fine. 

I'm chucking it to my M10R doesn't like the 35f2 ASPH so I choose it manually. I bet if I sell it to you your camera will detect it. It's a very strange issue. I explained it to Leica and they didn't say anything about it. It has been going on for years so surely they must know. 

The replies I got from them was update the camera firmware and when that didn't work it was just pick it manually. 

I wrote Leica singapore which is my main Leica point of contact. Anything that goes to Germany from Asia must go through Leica Singapore first. Their email support is miles better than Leica Germany from what I've experienced so far. 

Leica Germany I can't even reply because it gets denied as "soam" so I have to reply to them through the website and each time I get someone different. 

Leics Singapore you get one contact and they stay with you until your issue is fixed. 

Edited June 7, 2024 by crons

[Advertisement]

Hallo,

Look here: Leica M

[dugby]

Ahhh …. Singaporean Leica owners are secretly being marketed-to, with such a strong SGP dollar ,

you’re supposed to get fed up with your old 35-cron not 6-bit registering and thus go out and replace it with a 35-APO …. That’s what Mr Kiasu would surely do ?

Edited June 8, 2024 by dugby

[crons]

On 6/8/2024 at 7:31 AM, dugby said:

Ahhh …. Singaporean Leica owners are secretly being marketed-to, with such a strong SGP dollar ,

you’re supposed to get fed up with your old 35-cron not 6-bit registering and thus go out and replace it with a 35-APO …. That’s what Mr Kiasu would surely do ?

I don't know it's happening because it's already set to the 35 cron. It switches back and forth by itself between it and the 50.  

I've already had one experience with Leica singapore and they're awesome. They deal with Wetzlar on your behalf and the emails come back in polite clear English instead of the two emails I've gotten from Germany which go between apathy and rudeness.  

I don't live in Singapore so I don't know anything about them other than that.