thedirektor Posted October 11, 2016 Share #1 Posted October 11, 2016 Advertisement (gone after registration) I have a new 262 and a 50mm Summarit 2.4 lens Normally when I hit the info screen the lens is recognized a 2.4// 50. However something after switching on the info screen shows as unregistered. Does anyone else have this problem and is there a solution to this problem ? What I do now is just pop the battery or uncouple and recouple the lens. But it's a hassle. Any help would be much appreciated. It's my first Leica and I'm new to the M . Thanks. Link to post Share on other sites More sharing options...
Advertisement Posted October 11, 2016 Posted October 11, 2016 Hi thedirektor, Take a look here M262 Lens stops being recognised. I'm sure you'll find what you were looking for!
jaapv Posted October 12, 2016 Share #2 Posted October 12, 2016 simplest case: are you keeping the lock button pressed when mounting the lens and thus over rotating it? It should click in positively. Having the battery out will probably not do anything. Another possibility might be that the paint in the dots is damaged/dirty. Or-unlikely- that there is some problem with the six code sensors in the mount. Link to post Share on other sites More sharing options...
brill64 Posted October 12, 2016 Share #3 Posted October 12, 2016 ..also, clean the six-bit reader on the camera's lens flange? Link to post Share on other sites More sharing options...
thedirektor Posted October 12, 2016 Author Share #4 Posted October 12, 2016 Thank you verŷ much all for the ongoing advice. What is strange is that the lens is recognized for days and then one day I switch on and it is not recognized. Could this happen with a dirty six bit reader ? I.E. That the lens is recognized for some time and then not ? Link to post Share on other sites More sharing options...
Rus Posted October 12, 2016 Share #5 Posted October 12, 2016 Thank you verŷ much all for the ongoing advice. What is strange is that the lens is recognized for days and then one day I switch on and it is not recognized. Could this happen with a dirty six bit reader ? I.E. That the lens is recognized for some time and then not ? Was the lens always mounted on the camera during all that time when it switched from recognised to unrecognised? If that was the case then it was a bit curious indeed, as it seems unlikely that the code reader or the coded patch on the lens mount can be suddenly so smudged while mounted. If the lens was mounted and unmounted every now and then then it is quite possible that cleaning both the code reader and the coded patch will improve the situation. Bottomline is a 50mm does not necessarily need the correction enabled by the coding. And if EXIF data is what you are after, you can always just manually select the lens in the camera and save it to a profile. Link to post Share on other sites More sharing options...
Gregm61 Posted October 12, 2016 Share #6 Posted October 12, 2016 My M262 always recognizes the lens but often displays the incorrect aperture in the EXIF data, such as f2.4 instead of f2, etc.....the cost of such an analog system. Just manually code the lens in. When that becomes a problem is when you start working with multiple lenses. The first set of lenses I used with my M9 were all uncoded and about half the frames I shot displayed the incorrect lens in the EXIF data because I'd change a lens for forget to manually recode the camera for several frames. Frustrating. If I were a little less anal I'd just turn the coding system off and not think about it. Right, like that's happening.... Link to post Share on other sites More sharing options...
jaapv Posted October 12, 2016 Share #7 Posted October 12, 2016 Advertisement (gone after registration) The variation in aperture in exif has nothing to do with this. It is a known quirk since 2006. As there is no way that the camera can read out the aperture set on the lens it is an estimate. Sometimes way off. Link to post Share on other sites More sharing options...
Gregm61 Posted October 12, 2016 Share #8 Posted October 12, 2016 I'm having a ball with that 18mm Super Elmar, Jaapv. Wonderful lens. Link to post Share on other sites More sharing options...
thedirektor Posted October 13, 2016 Author Share #9 Posted October 13, 2016 Was the lens always mounted on the camera during all that time when it switched from recognised to unrecognised? If that was the case then it was a bit curious indeed, as it seems unlikely that the code reader or the coded patch on the lens mount can be suddenly so smudged while mounted. If the lens was mounted and unmounted every now and then then it is quite possible that cleaning both the code reader and the coded patch will improve the situation. Bottomline is a 50mm does not necessarily need the correction enabled by the coding. And if EXIF data is what you are after, you can always just manually select the lens in the camera and save it to a profile. Yes Rus the lens was always mounted and it just went from showing the lens to info to the uncoded thing. So very strange. Now I know that I don't need the lens info for a 50mm and the camera will still function but it's just strange. And it's a very expensive camera ! Link to post Share on other sites More sharing options...
Steve Ricoh Posted October 14, 2016 Share #10 Posted October 14, 2016 I have a new 262 and a 50mm Summarit 2.4 lens Normally when I hit the info screen the lens is recognized a 2.4// 50. However something after switching on the info screen shows as unregistered. Does anyone else have this problem and is there a solution to this problem ? What I do now is just pop the battery or uncouple and recouple the lens. But it's a hassle. Any help would be much appreciated. It's my first Leica and I'm new to the M . Thanks. The obvious way to fault find is to mount another 6 bit lens - return to the dealer, they should have loads. It's ok having a work-around, but 6 bit recognition is a feature. It should work, and should be resolved. Link to post Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.