jslabovitz Posted June 24, 2023 Share #1 Posted June 24, 2023 Advertisement (gone after registration) Here's a strange one... I use an M10-D with a Summaron-M 28mm (in black) and a Visoflex 020. This setup works well. I ordered a Voigtlander 40mm/f2.8 Heliar in black paint as a companion lens. However, once I mount the the Heliar, the Visoflex display is either completely blank or displays a message saying 'No lens mounted!' The camera does seem to be happy to take a shot. I suspect this has something to do with the fact that not only is there no 6-bit lens coding on the Heliar, the rear lens flange is *completely* black, versus the typical chrome/steel used on most lenses. I reckon that the code is being interpreted as six black dots (111111), which doesn't seem to map to any known lens from my quick research. Has anyone else used this particular combination of gear and made it work? If not, then sadly I think this is going to have to go back for a refund... Link to post Share on other sites More sharing options...
Advertisement Posted June 24, 2023 Posted June 24, 2023 Hi jslabovitz, Take a look here M10-D + Voigtlander 40mm Heliar + Visoflex == blank screen. I'm sure you'll find what you were looking for!
jslabovitz Posted June 24, 2023 Author Share #2 Posted June 24, 2023 (Replying to my own post...) I see there's a mention of a related issue in the dedicated thread for this lens: ...but because my camera is an M10-D without a menu function, I can't turn off lens detection, and hence can't follow this suggestion. It appears the "solution" is to replace the M-mount version with an LTM version, and use an LTM/M adapter which is chrome and is coded either 35mm or 50mm. Link to post Share on other sites More sharing options...
AndreasG Posted June 24, 2023 Share #3 Posted June 24, 2023 Try to place a small piece of thin Aluminum foil between lens flange and housing to simulate "000000", if it works, next step would be to remove the black coating in the detection area of the flange. 1 Link to post Share on other sites More sharing options...
jslabovitz Posted June 24, 2023 Author Share #4 Posted June 24, 2023 14 minutes ago, AndreasG said: Try to place a small piece of thin Aluminum foil between lens flange and housing to simulate "000000", if it works, next step would be to remove the black coating in the detection area of the flange. Thanks so much for the quick response! Your trick did indeed work — now the Visoflex shows an image, and a lens of "R-Adapter", which I've seen before with an unrecognized lens. Given that I just purchased this, I don't think I'll be attempting to remove the coating. More likely it will go back and I will then decide whether I want to try again with the LTM version plus an appropriate adapter. Link to post Share on other sites More sharing options...
AndreasG Posted June 24, 2023 Share #5 Posted June 24, 2023 vor 2 Stunden schrieb jslabovitz: LTM version plus an appropriate adapter Caveat: Some LTM adapters have a cut out at the sensor location, look for one without the cut out, otherwise it will fail. 1 Link to post Share on other sites More sharing options...
PhoToad Posted June 26, 2023 Share #6 Posted June 26, 2023 The silver version of the heliar should work with the M10-D (i.e. no need to go for the LTM). Link to post Share on other sites More sharing options...
ramarren Posted July 2, 2023 Share #7 Posted July 2, 2023 (edited) Advertisement (gone after registration) On 6/23/2023 at 10:18 PM, jslabovitz said: Here's a strange one... I use an M10-D with a Summaron-M 28mm (in black) and a Visoflex 020. This setup works well. I ordered a Voigtlander 40mm/f2.8 Heliar in black paint as a companion lens. However, once I mount the the Heliar, the Visoflex display is either completely blank or displays a message saying 'No lens mounted!' The camera does seem to be happy to take a shot. I suspect this has something to do with the fact that not only is there no 6-bit lens coding on the Heliar, the rear lens flange is *completely* black, versus the typical chrome/steel used on most lenses. I reckon that the code is being interpreted as six black dots (111111), which doesn't seem to map to any known lens from my quick research. Has anyone else used this particular combination of gear and made it work? If not, then sadly I think this is going to have to go back for a refund... Can't you just turn off "Lens Detection" so that the camera ignores the lens identification code gizmo when you're using that lens? G Edited July 2, 2023 by ramarren Link to post Share on other sites More sharing options...
jslabovitz Posted July 7, 2023 Author Share #8 Posted July 7, 2023 On 7/2/2023 at 7:46 AM, ramarren said: Can't you just turn off "Lens Detection" so that the camera ignores the lens identification code gizmo when you're using that lens? Perhaps that's an option on the M10, but apparently not on the M10-D. I looked through the manual, and there's no way on the camera itself to access this setting (unsurprisingly, given the minimalism of the D). I also connected through the Fotos app, and I can't see anything in the Camera Settings that would relate. So it seems to me this is not a function of the M10-D. Even if it was, I wouldn't want to lose the ID function for the other lenses I use quite reliably which either have factory-set codes or ones on which I've fitted custom flanges with codes. Link to post Share on other sites More sharing options...
ramarren Posted July 8, 2023 Share #9 Posted July 8, 2023 Interesting. I have the Lens Detection command set at the top of my Favorites screen on both the M10-M and M10-R so that I can disable it whenever I'm using an uncoded lens (like the MS Optics 24/2 or M-Rokkor 90/4) and switch it back on for lenses that are coded or that I have manual codes I know work. Very odd to hear that the M10-D doesn't support the function! G Link to post Share on other sites More sharing options...
jslabovitz Posted July 9, 2023 Author Share #10 Posted July 9, 2023 19 hours ago, ramarren said: Very odd to hear that the M10-D doesn't support the function! Not so odd if you consider that the D has no screen, and hence no menus and no functions! There is a single multifunction button on the top, and a focus button on the front, both of which do very little unless you have a Visoflex 020 mounted — and neither allows changing the lens profile setting. Not that I'm complaining, save this lens-coding issue — I continue to adore the M10-D's minimalism. Link to post Share on other sites More sharing options...
rramesh Posted July 23, 2023 Share #11 Posted July 23, 2023 (edited) Doesn't the lens have a coding groove, and if so, can you not paint the 6-bit code (black and white bars)? Edited July 23, 2023 by rramesh Link to post Share on other sites More sharing options...
jslabovitz Posted July 25, 2023 Author Share #12 Posted July 25, 2023 On 7/22/2023 at 5:24 PM, rramesh said: Doesn't the lens have a coding groove, and if so, can you not paint the 6-bit code (black and white bars)? I suppose someone could try if they *really* wanted this lens to work. But I bought the lens new and there's no way I'm going to paint in some unreliable codes on a brand-new lens that I may yet return, just to see if I'd want to keep it. (Indeed, I ended up returning the lens.) As mentioned above, the best solution seems to buy the black LTM version and a properly coded LTM-M adapter flange. Or buy the chrome M version and deal with an uncoded lens. Link to post Share on other sites More sharing options...
graphlex Posted July 31, 2023 Share #13 Posted July 31, 2023 I’ve used uncoded lenses (Leica and Zeiss) on the M10D without this problem. Link to post Share on other sites More sharing options...
jslabovitz Posted July 31, 2023 Author Share #14 Posted July 31, 2023 5 minutes ago, graphlex said: I’ve used uncoded lenses (Leica and Zeiss) on the M10D without this problem. Yes, so have I, with general success — as long as the rear flange is silver or chrome! The problem here is that I bought the all-black version of the lens, and the flange is entirely black. That seems to cause the sensor to read the lens code as an error, instead of the usual 'unknown lens' status. If I put my programmer's hat on, I'd say it's reading 000000 (silver/white) as 'unknown lens,' but 111111 (black) as 'error.' (Maybe I'm flipping 0/1, but you get the point.) 1 Link to post Share on other sites More sharing options...
Steve Peck Posted February 29, 2024 Share #15 Posted February 29, 2024 I also could not get live view on my M10R. I put some foil over the 6-bit sensor as suggested in one of the posts and the I had live view and no Lens error messages. I simply sanded off a bit of the black paint in the correct position as shown in the image, and the problem was solved permanently. Kind of an oversight by Voigtlander, but those designers made one pretty lens, so they get a pass. 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! 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/378719-m10-d-voigtlander-40mm-heliar-visoflex-blank-screen/?do=findComment&comment=5063242'>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