kcnarf1 Posted May 6, 2017 Share #1 Posted May 6, 2017 Advertisement (gone after registration) My Noctilux F/.95 will not set to automatic detection on my new M10, received yesterday. That lens does set to automatic detection on my M240, and my WATE lens sets to automatic detection on both cameras. What is the problem with my Noctilux F/.95 on my new M10? What to do? As a temporary solution, I have manually set my new M10 for the Noctilux F/1. Is that recommendable for fine performance? I thankfully welcome all advice on this matter. Quote Link to post Share on other sites More sharing options...
Advertisement Posted May 6, 2017 Posted May 6, 2017 Hi kcnarf1, Take a look here nocti .95 won't set to auto detect. I'm sure you'll find what you were looking for!
jdlaing Posted May 6, 2017 Share #2 Posted May 6, 2017 Setting it in the menu will work the same. You just have to remember to change the setting when you mount a different lens. Check that the little window and the paint on the six bit codes are both clean. Quote Link to post Share on other sites More sharing options...
kcnarf1 Posted May 6, 2017 Author Share #3 Posted May 6, 2017 I can't set the Nocti F/.95 in the menu as you advise, because it is not listed in the menu. That's why I set it for the Nocti F/1, which is listed in the menu. Is that manual setting also sufficient for the Nocti F/.95? Quote Link to post Share on other sites More sharing options...
jdlaing Posted May 6, 2017 Share #4 Posted May 6, 2017 That question I cannot answer. I didn't know it had been eliminated from the M10. It should be okay. Maybe others can advise. 1 Quote Link to post Share on other sites More sharing options...
jaapv Posted May 6, 2017 Share #5 Posted May 6, 2017 That question I cannot answer. I didn't know it had been eliminated from the M10. It should be okay. Maybe others can advise. It hasn't been eliminated. Lenses that exist in 6-bit coded versions only are not listed in the manual menu. There are two possibilities for this problem: either the coding is dirty or damaged, or one of the detection sites in the flange is faulty. The third possibility: overrotating the lens by keeping the release button depressed can be ruled out for an experienced user. 2 Quote Link to post Share on other sites More sharing options...
kcnarf1 Posted May 6, 2017 Author Share #6 Posted May 6, 2017 Dear Jaap: In your opinion, is setting manual detection to the Nocti f/1 a good temporary solution? Thanks again for your attention. Quote Link to post Share on other sites More sharing options...
digitalfx Posted May 7, 2017 Share #7 Posted May 7, 2017 Advertisement (gone after registration) My .95 Noctilux is recognized as it should...are you sure your lens is coded? Also verify the the lens is fully mounted. Quote Link to post Share on other sites More sharing options...
kcnarf1 Posted May 7, 2017 Author Share #8 Posted May 7, 2017 All Noctiluxes F/.95 are coded, plus (as I've already said) it sets as auto detected on my M240. It is fully mounted. To be sure, I've remounted it several times. Quote Link to post Share on other sites More sharing options...
Stef63 Posted May 7, 2017 Share #9 Posted May 7, 2017 All Noctiluxes F/.95 are coded, plus (as I've already said) it sets as auto detected on my M240. It is fully mounted. To be sure, I've remounted it several times. This will not help you much but I can confirm that my Noctilux 0.95 shows up correctly on my M10. Quote Link to post Share on other sites More sharing options...
jaapv Posted May 7, 2017 Share #10 Posted May 7, 2017 Dear Jaap: In your opinion, is setting manual detection to the Nocti f/1 a good temporary solution? Thanks again for your attention. It will show up in EXIF and I doubt whether there are any significant corrections made for either lens. At most a bit of vignetting correction. Quote Link to post Share on other sites More sharing options...
digitalfx Posted May 7, 2017 Share #11 Posted May 7, 2017 All Noctiluxes F/.95 are coded, plus (as I've already said) it sets as auto detected on my M240. It is fully mounted. To be sure, I've remounted it several times. have you verified that the code on the noctilux is clean and that the reader on my10 is as well? Which firmware are you on? 1 Quote Link to post Share on other sites More sharing options...
Rob L Posted May 7, 2017 Share #12 Posted May 7, 2017 I have a coding issue with my M10 that I brought up in the Bug thread. Mine thinks my Summicron 35 IV is a 35 1.4 Summilux. My other bodies read it correctly. Problem is I can't set it to manual coding because it reverts back to 6 bit detection (Summilux) every time it goes to sleep or gets shut off. My M10 lens detection functions as intended with all of my other lenses both coded and not. Quote Link to post Share on other sites More sharing options...
Rob L Posted May 7, 2017 Share #13 Posted May 7, 2017 I forgot to add that I tried this lens on another M10 and it worked fine. Quote Link to post Share on other sites More sharing options...
jaapv Posted May 7, 2017 Share #14 Posted May 7, 2017 That would suggest that one six-bit detector does not function. It has happened before. Quote Link to post Share on other sites More sharing options...
Rob L Posted May 8, 2017 Share #15 Posted May 8, 2017 Perhaps, except that the code for the 35 Summicron and 35 Summilux are not even similar, way different. Also mine reads all 7 of my other lenses properly. Quote Link to post Share on other sites More sharing options...
digitalfx Posted May 8, 2017 Share #16 Posted May 8, 2017 Might be helpful if those with issues state which FW they have on their cameras. Quote Link to post Share on other sites More sharing options...
ing_rippi Posted May 20, 2017 Share #17 Posted May 20, 2017 Hello from Germany, since I had an issue with the 6-bit Coding of my brandnew M10 Body, I thought I let you know about it. In my case my first M Lens is the Summarit 35mm f 2.4 which was not detected correctly by the M10. Firmware was 1.3.4 Since I live only 100 km away from Wetzlar, I dropped the camera at the customer care. Finally they exchanged the body. Regards Harald Quote Link to post Share on other sites More sharing options...
CJJon Posted May 20, 2017 Share #18 Posted May 20, 2017 None of my lenses are coded. I pick whatever is closest in the manual menu. I have not noticed any issue at all even when I forget to change settings. I highly doubt there is a difference between f/1 and f/0.95 that would be perceptible to human beings. Quote Link to post Share on other sites More sharing options...
chris_tribble Posted May 25, 2017 Share #19 Posted May 25, 2017 Whether coding and the information / adjustments it offers are useful is neither here nor there. I should work whatever. Check the body with other lenses. If it's not picking up the coding, check that you've set AUTO on the menu - MANUAL will block identification. If everything's correctly set up and lenses are not being identified get an exchange or a fix via your dealer. Lens detection SHOULD work. If it doesn't it might indicate other issues with the camera's electrics. Quote Link to post Share on other sites More sharing options...
Rob L Posted May 25, 2017 Share #20 Posted May 25, 2017 Setting the camera to Manual detection does not change any of this on the M10. As soon as the lens detects a 6 bit code it reverts to auto detect the next time it wakes from sleep or is turned on from being powered off. So my camera detects a Summicron 35 V4 as a Summilux 35. It does not detect my Summarit 35 at all, and reverts to the setting in manual detect, unfortunately there is no option to set this lens manually as it is only available as 6 bit and is not listed. I don't think this is an issue with the reader, but I'm no engineer. Quote Link to post Share on other sites More sharing options...
.thumb.jpg.453e29217325d25605a012f22452719b.jpg)
Recommended Posts
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.