I just had one 3D-printed and coded my Voigtländer 35mm f1.5 and 75mm f1.9 as Summilux 35 and APO-Summicron 75 respectively - both show up correctly with my TTartisan 6-bit adapter on the Zf!
One thing that was a bit fiddly is that the notch is not very well pronounced on my adapter and relatively easy to slip past. So one has to take some care correctly aligning the template. Maybe that's due to the print quality and/or the material I chose (used PA12-CF and the company uses FDM printers - whatever any of this means ).
The pen I used was an Edding 780.
Well, I guess I have to buy that Voigtländer 21mm 3.5 now to complete the trinity..
Vetteman wrote:
I uploaded the file that @yukosteel@@ generously shared with us to Xometry.com on Friday 4/26/24. Creating the order was simple and straightforward. The cost for the part was $8.50 + $.51 tax for a total cost of $9.01. This included FedEx Priority Overnight Shipping
The part was printed on 4/30/24 and shipped the same day. It was delivered this morning.
What about the printed piece? It's perfect! I placed it on a 28mm Elmarit to check alignment of the codes and it is spot on perfect.
@yukosteel@@ thanks for taking the time to design the part and for sharing it with us. And a great experience with Xometry.com!
I had this one printed by Xometry. It lines up better than the previous one I had downloaded and printed by Print a Thing but it is not as tight, that might be the material used, I don't know. I am thinking a 3D printer is in my future so I can make my own adjustments and material choices.
Thanks for the effort!
For what it's worth, I could slice and print V1 with BambuLab's slicer. V2 was another matter: everything was fine and rather better than V1 except that the fourth bit counting from the index stayed closed whatever parameters I tried. Obviously others have printed V2 without a problem so I don't know where the problem comes from.
I ended up drawing a V2 more or less clone from scratch with OpenSCAD and it prints properly with the bit holes looking exactly the same. I still have to test if the codes are read properly by the camera.
fjablo wrote:
One thing that was a bit fiddly is that the notch is not very well pronounced on my adapter and relatively easy to slip past. So one has to take some care correctly aligning the template. Maybe that's due to the print quality and/or the material I chose (used PA12-CF and the company uses FDM printers - whatever any of this means ).
Thank you for that note! Thanks to extra research performed by Fred on various Leica lenses the V2C_II model has slightly wider pin, which fits Leica mount sizing but may be not be perfect fit on Voigtlander lenses. I included 3D model version V2C with 0.2mm thinner lock pin - it should precisely fit Voigtlander lenses and better tolerate print precision variations.
Thury wrote:
Thanks for the effort!
For what it's worth, I could slice and print V1 with BambuLab's slicer. V2 was another matter: everything was fine and rather better than V1 except that the fourth bit counting from the index stayed closed whatever parameters I tried. Obviously others have printed V2 without a problem so I don't know where the problem comes from.
I ended up drawing a V2 more or less clone from scratch with OpenSCAD and it prints properly with the bit holes looking exactly the same. I still have to test if the codes are read properly by the camera.
One thing I'm still fighting with Cura slicer is to force model print not form the socket holes, because it always put extra material first on my Neptune 3 Pro first, which is annoying. One thing is helping - adding extra holes in the model, so print starts form them and smoothly moving to the 6bit sockets and printing them better.
Another thing is to find compromise between print speed and print time. If speed is too slow - material may expand from the head, if it's too quick - 6bit socket edges geometry is slightly distorted.
Thanks for the extra effort on cloning the design, I can share my original .blend file if that helps, or export it to other fotmat compatible with OpenSCAD, just let me know.
Stimulated by these tools to code lenses, I've been trying to update my list of 6 bit codes and have had a surprise.
If I understand it correctly, each combination of different "optical formula, name, focal length, aperture" gets one code. 6 bit coding provides for 64 combinations.
My list of lenses with different codes is 62 items long. I'm sure that I miss some and suspect that 4 or 5 may share the code of another lens of same name, focal length and aperture.
My question is: is the 6bit system going to be obsolete pretty soon ?
I've tested the templates with several Leica, Voigtlander, and Zeiss ZM lenses.
Among them, "V2C_II" stands out as the best version because it securely locks onto the mount's "Pin" without any play for Voigtlander and ZM lenses, both manufactured by Cosina. While there's a slight play when used with Leica lenses, it's less concerning since we aren't 6-bit coding them.
It's noteworthy that there's variation in the precise location of the 6-bit code within Leica lenses. I've tested 7 Leica 6-bit coded lenses, and the code's position varies slightly by a very small measurement (e.g., 0.1mm).
I successfully 6-bit coded 3 Voigtlander lenses and 1 Zeiss ZM lens with the "V2C_II" version, achieving a 100% success rate with Leica correctly reading the intended code.
My printer settings were default, except for the following:
Layer Height: 0.1mm (default is 0.2mm)
Line Width: 0.3mm
Initial Layer Line Width (90%)
Wall Line count: 3
Infill Density: 15%
Print Speed: 30mm/s
We've experimented with V2C III versions, which appeared to be better suited for aligning with a couple of Leica lenses. However, they didn't perform satisfactorily with Cosina lenses. Hence, currently I think that V2C II is more precise for our specific intention.
Would V2C III be an option to use for coding “non-codable” Leica lenses? Namely the 50mm Summicron pre-ASPH v3 and 35mm Summilux pre-ASPH (early V2 infinity lock)? Or do they need to have the flange replaced (or template modified) to allow for coding with this template?
Any risk or experience of the permanent ink/paint washing off the lens mount on to the 6 bit reader? I would hate to damage my M11 to get exif capability.
J Peterman wrote:
Would V2C III be an option to use for coding “non-codable” Leica lenses? Namely the 50mm Summicron pre-ASPH v3 and 35mm Summilux pre-ASPH (early V2 infinity lock)? Or do they need to have the flange replaced (or template modified) to allow for coding with this template?
V2C_II should work for coding, the main challenge is if mount surface is flat - there is no way for paint to stay, it will be scratched off when mounting. Voigtlander lenses have mount groove which helps to address that.
tzhang4284 wrote:
Any risk or experience of the permanent ink/paint washing off the lens mount on to the 6 bit reader? I would hate to damage my M11 to get exif capability.
That's a good question. It looks visually that Leica 6bit sensor of M10/M11 is covered with glass with some sort of coating. Unless the paint is abrasive or has some glue in it it should be safe for 6bit sensor, but you may experiment with applying paint to inexpensive lens filter, then wiping it with isopropyl alcohol or acetone to see the impact on the coating.
Technically if thin layer is applied into Voigtlander mount groove, you should be able to mount/dismount without paint interacting with 6bit sensor. If paint migrate to mount edges it's important to wipe it out, then use Leica lens cap first, and then to double check paint is not touching camera mount by mounting it first away from 6bit sensor.
That's 62 lines including 7 unknown codes and 6 known duplicates. The 7 unknowns break down into at most 3 new duplicates and at least 4 new unique codes. That's 53 to 56 of the 64 possibilities already used. I'd say that the life expectancy of the 6 bit code system might be something like 5 years...
IDK about the firmware update limitations, but few ways to solve it past 64 codes in use would be to:
- allow custom re-mapping of codes
- make new Leica lens with 6bit code of its closest matching correction profile and detect it by default, allow to choose in settings to use new/legacy code mapping
In that changes 6bit system can live much longer. Perhaps Leica engineers already solved this question while designing next group of lenses.
yukosteel wrote:
Updated list based on 6bit codes I found on eBay listings of corresponding lenses (marked in orange above).
New list now has 6bit number marked in green indicating duplicates with similar lens, and orange indicating duplicate with very different lens
Your table is much nicer than my text list.
I have not yet found good pictures of the Thambar and Summarit 90mm/2.4 codes and have no clear idea how the same code applied to 2 wildly different lenses could work on a M240 or on TTArtisan's adapter. Possibly as the M cameras get the 6bit code info and the frame selection info, it could be possible to have the same 6bit code applied to different lenses if the frame selection is different but 28 and 90 bring the same frame lines set in the viewfinder so this would not work with the Summarit 90/2.4 - Summicron 28/2(II). It might open 3*64 possibilities. Maybe... Not sure that older M bodies would work with that. The Leica M to L and the TTArtisan adapters surely would not.