35f2 Summicron-M ASPH v1 vs v2

[crons]

Advertisement (gone after registration)

Am I correct in thinking you could use the 11879 in camera lens profile for the 11673 since they're optically the same? 

[crons]

1 hour ago, Al Brown said:

Do you have an uncoded 11673 Summicron V6?

No. The camera firmware doesn't have it in the profiles. So if I don't want to update the camera, is it the same just choosing the 11879 profile. 

[crons]

@Fred Miranda

Do you know if i understand this correctly that the 11879 profile would work with the 11673 just the same? 

[lct]

Unsure what is a Summicron v6 but Summicrons 35/2 asph v1 (11879, 11882) and v2 (11673, 11674) have apparently the same code (011110). I have no experience with v2 though.

[crons]

6 minutes ago, lct said:

Unsure what is a Summicron v6 but Summicrons 35/2 asph v1 (11879, 11882) and v2 (11673, 11674) have apparently the same code (011110). I have no experience with v2 though.

So then choosing the 11879 in camera profile with the 11673 attached should be just fine. The profile should work for both lenses?

[lct]

1 minute ago, crons said:

So then choosing the 11879 in camera profile with the 11673 attached should be just fine. The profile should work for both lenses?

Sounds logical but i have no experience with the 11673.

[crons]

Advertisement (gone after registration)

33 minutes ago, lct said:

Sounds logical but i have no experience with the 11673.

Ok. Attaching the 11673 to a camera without that profile just defaults to M instead of auto. So I chose 11879

 

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 3, 2024 by crons

[crons]

Does that mean on the new firmware it shows

35 f/2 ASPH. 11673/11879/11882

? If anyone can show me it would be great. If it is then it's using the same profile for all of them so updating for it doesn't matter unless you use a lot of lenses and prefer that it switches automatically. 

Yea the code is 011110. 

Edited June 3, 2024 by crons

[lct]

46 minutes ago, crons said:

Attaching the 11673 to a camera without that profile just defaults to M instead of auto [...]

It should not, unless you did not update firmware i suppose, but again i have no experience with this lens.

[crons]

20 minutes ago, lct said:

It should not, unless you did not update firmware i suppose, but again i have no experience with this lens.

Yes. I do not want to update the firmware. So the 11673 isn't listed.

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!

This is M10R firmware v20.20.47.37

If the 11673 was just added to the profile that is already in my camera then this isn't reason enough for me to update the firmware. 

Edited June 3, 2024 by crons

[trisberg]

23 hours ago, crons said:

Yes. I do not want to update the firmware. So the 11673 isn't listed.

I think it is not listed since they are all 6-bit coded and should bring up Auto lens selection. That's what mine does, and I don't get an option to manual selection. Maybe your 6-bit code reader is not detecting the lens code.

-Thomas

[crons]

30 minutes ago, trisberg said:

I think it is not listed since they are all 6-bit coded and should bring up Auto lens selection. That's what mine does, and I don't get an option to manual selection. Maybe your 6-bit code reader is not detecting the lens code.

-Thomas

It's not detecting that particular lens and I believe the problem is the outdated firmware. My choices are to update the camera firmware or select 11879 manually. 

If the resulting correction is the same whether I manually select 11879 or update the camera so that it auto detects the 11673, then I prefer just leave it selected as 11879. 

Edited June 4, 2024 by crons

[Casey Jefferson]

The 35/2 ASPH V2 (2016) predates Leica M10 (2017), so logically it should include the profile in firmware since M10 bodies. That only means they share the same profile. There's some update to the V2 optics but I've read reviews that they're basically the same except on hi-red bodies the v2 can resolve more details.

[lct]

6 hours ago, crons said:

It's not detecting that particular lens and I believe the problem is the outdated firmware.

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]

1 hour ago, Casey Jefferson said:

The 35/2 ASPH V2 (2016) predates Leica M10 (2017), so logically it should include the profile in firmware since M10 bodies. That only means they share the same profile. There's some update to the V2 optics but I've read reviews that they're basically the same except on hi-red bodies the v2 can resolve more details.

I thought the same. My old firmware is from 2021. My lens is manufactured 2018. Why would it not be included. Leica replied to me and told me to update the firmware. I didnt want to but I did anyway. It seems to have gone fine, but the lens is still not auto detected. So it's not a firmware issue. It's not a camera hardware issue either and the lens just came out of a brand new sealed box. Another poster had the same thing and the Leica Store got him a new lens and the new one did the same. 

Edited June 4, 2024 by crons