Jump to content

Dodgy mount registering/not registering 6 bit coding


huckles

Recommended Posts

Advertisement (gone after registration)

I have read this before but it was to do with not reading a 6 bit code in 3rd party lenses. However, I have noticed this annoyance with my Noctilux that if you mount the lens as usual and lock it in, it comes up with the Noct profile fine, but if you 'slightly' twist it (even adjusting the focus) can do this.. it then becomes 'uncoded'... but again, slight twisting it back brings the Noct profile back up. Although not a game breaker, it is very very annoying.. is it because of the weight of the lens? :S

Link to post
Share on other sites

  • Replies 45
  • Created
  • Last Reply

Ditto with 50/0.95 , and 75/2

 

It is not clear why the registration is so sensitive to a tiny misalignment.

 

Those that have returned their M because of it have had the flange with the sensor replaced.

 

There is no user 'fix' possible. I suspect tinkering will just make it worse.

 

For now I am just careful to check it registers when I attach the lens and periodically ensure it is turned fully clockwise....

Link to post
Share on other sites

Thanks for the reply.. it is soo frustrating that gear this expensive has some of the most 'annoying' traits... really shouldn't be there.

 

Although it doesn't affect picture quality as of course there are profiles in LR, it is rather rediculous this is even comes up.. :S

Link to post
Share on other sites

I have the same problem with the Noctilux 0.95. Mount and twist till it clicks into place and the code's not recognised., mount and twist hard until it clicks and the code is recognised. The amount of play in the mount is very small, only a fraction of a mm and not discernible by eye. I've had no success at getting third party coded adapters etc. to work reliably. Why the M240 coding sensor array should be so sensitive to misalignment is a mystery.

 

Bob.

Link to post
Share on other sites

I have the same problem with the Noctilux 0.95. Mount and twist till it clicks into place and the code's not recognised., mount and twist hard until it clicks and the code is recognised. The amount of play in the mount is very small, only a fraction of a mm and not discernible by eye. I've had no success at getting third party coded adapters etc. to work reliably. Why the M240 coding sensor array should be so sensitive to misalignment is a mystery.

 

Bob.

 

So do we live with this or send it back? :S

Link to post
Share on other sites

Advertisement (gone after registration)

I have the same problem with the Noctilux 0.95. Mount and twist till it clicks into place and the code's not recognised., mount and twist hard until it clicks and the code is recognised. The amount of play in the mount is very small, only a fraction of a mm and not discernible by eye. I've had no success at getting third party coded adapters etc. to work reliably. Why the M240 coding sensor array should be so sensitive to misalignment is a mystery.

 

Bob.

 

probably because the original array of sensors was straight ..... and the current one is curved ...... although common sense would make you think that would be more accurate at reading the coding pits rather than less........ :rolleyes:

Link to post
Share on other sites

I had the same issue with my Noctilux-M 50/0.95 Asph ... on the M9. Leica Customer Care fixed it, free of charge, under warranty. As far as I understand it, they replaced the lens' bayonet mount. Now the issue is gone, and the lens is properly and reliably recognised also on the new M.

Link to post
Share on other sites

Same problem with teh 0.95 and when time allow, Leica will get the camera in to fix it.

 

I have no doubt they will fix it, but in Australia (I'm not sure about the rest of the world)... it is a quoted 3 month fix everytime something needs to be sent away.. which in my books for service delivery time... dreadful. In the professional world, this timing is everything. Luckily, this 'problem' doesn't affect image quality or I would be through the roof! :(

Link to post
Share on other sites

Frankly, I don't understand why Leica haven't set up a fast flow repair line with pickup service directly from the customers. I keep hearing the troubles in Australia, and even in the US.

 

I think London may be the place I have heard the most good things about as they seem to ship continuously every week.

 

I have told a few people dealing with Leica US and waiting for months to get a simple adjustment made, that they should send their camera directly to Solms because Leica will send it back at their expense. So all you are looking at is the shipping to Solms, probably 400 AUD minus the 30% discount you can usually get with DHL or UPS if you ask for a code.

 

Usually, contacting Customer Service in Solms and talking to a person (or mailing them) will ensure the spare part and time is in place, and you can alert them the shipment is coming, and later send them the tracking information and follow up with the same person. Though usually you get a quote as acknowledgement (stating the price or that it is free of charge) the day they receive the parcel, and that will enable you to track the repair also online.

 

If a repair is booked it doesn't take three months. Shipping to Solms is 2-3 days, repair or adjustment is hours or days, and return snipping is 2-3 days.

 

Which leave the you with the question, what is happening the other 70-80 days I am waiting three months for my camera ...

Link to post
Share on other sites

Frankly, I don't understand why Leica haven't set up a fast flow repair line with pickup service directly from the customers. I keep hearing the troubles in Australia, and even in the US.

 

I think London may be the place I have heard the most good things about as they seem to ship continuously every week.

 

I have told a few people dealing with Leica US and waiting for months to get a simple adjustment made, that they should send their camera directly to Solms because Leica will send it back at their expense. So all you are looking at is the shipping to Solms, probably 400 AUD minus the 30% discount you can usually get with DHL or UPS if you ask for a code.

 

Usually, contacting Customer Service in Solms and talking to a person (or mailing them) will ensure the spare part and time is in place, and you can alert them the shipment is coming, and later send them the tracking information and follow up with the same person. Though usually you get a quote as acknowledgement (stating the price or that it is free of charge) the day they receive the parcel, and that will enable you to track the repair also online.

 

If a repair is booked it doesn't take three months. Shipping to Solms is 2-3 days, repair or adjustment is hours or days, and return snipping is 2-3 days.

 

Which leave the you with the question, what is happening the other 70-80 days I am waiting three months for my camera ...

 

Ah! lol, thanks for the response... my personal issue is having $$$$ gear in transit and of course the time it is away from me, sure I have the D4, D800e, D800 etc, but for such highend gear, anytime it goes down or what not... it just breaks your heart that the process is so convoluted. Nikon not only has me covered within days, but always a loaner, always everything at their expense. And to be totally honest... My D3, D4 series cameras have NEVER gone down and I use those 95% of the time... just saying. :)

Link to post
Share on other sites

My M had to be sent back because of this issue. It's ready to be collected from Mayfair. Took about 2 working weeks. Apparently they've replaces the camera 6-bit reader and the lens coding (I sent the lens too)

 

I may be wrong but perhaps there is actually another problem with the M's that is a manufacturing defect (like the lugs) but they're not issuing a recall until people notice and they will send them back for repair.

 

Also - is it usual they have the relevant part in stock or do they expect a flurry of units to be sent back for repair?

Link to post
Share on other sites

Rick, is the problem still there or is it fixed.

Leica sent me an email to take the body to camera clinic in Melbourne (8 hour drive)... to see if they can adjust the bayonnet so that it mount's tighter. Failing that, I guess it will be sent to Solm...

 

I'll let everyone know how it goes... or doesn't go...

 

What a waste of time!

 

I'm this close to pulling the pin on Leica.

Link to post
Share on other sites

Its not fixed - they have suggested I send it back again.. my issue with this is that the problem is easy to demonstrate - it's not something that is hard to manifest itself again and again.. so they sent it back without properly testing it - and its not fixed.

 

I want to insist on a replacement. It is 100% a camera fault.

Link to post
Share on other sites

After a 16 hr round car trip from Canberra to Melbourne and back.... It has to go to Solms.... Can't begin to tell you guys how infuriated I am...

 

At the moment - I'm awaiting a response from Leica about getting my camera replaced.

I had a long chat with them - and they've been onto the forums quoting my posts - which is fine - but I have a feeling it's going to be a little of an uphill struggle.

 

Since I've had the 'repair' back - the coding/uncoding is back to as it was before I sent it away. I honestly am really annoyed Solms sent the unit back to me clearly not testing it properly. They say that 'it was made better' but a week after I have it, it's the same.

 

I've made a video of what's happening to show Leica.. rather than me having to trek to the store again for no reason...

 

coding/uncoding issues on Vimeo

Link to post
Share on other sites

I see this issue (to wit, where a slight wiggle counterclockwise on a mounted lens takes the lens detection from a correct state to "uncoded", where "slight wiggle" means just the amount possible due to the mechanical compliance and fit of the lens on the camera when latched) but only with lenses that bring up the 50/75mm frames.

 

Hypothesis: whereas the lens detection relies on two inputs, which are the six bit code and the frame line actuator, perhaps the issue is with recognition of the frame line actuator rather than the 6-bit code. Further, perhaps the issue of frame line actuator recognition only arises for 50/75. Note that the frame line actuator acts both mechanically (to position the correct frame line illumination mask) and electronically (to provide input to the lens detection algorithm). The electronic actuation is presumably by means of a three position switch which is actuated by the same mechanical interface that sets the frame line mask. If the actuation of such switch was "borderline" (barely within tolerance) for 50/75 frame lines, that could explain the issue. Maybe there is some amount of adjustability to the position of the switch and the problem can be corrected through that.

 

 

If the M240 had a frameline selector lever this hypothesis might be easy to test, but that's not the case. If the incantation to get to the "service menu" were known that would also presumably allow investigation, since it would (one would hope anyway) reveal what the camera electronics see in terms of both the six-bit code and frame actuation.

 

Anybody know the incantation to get to the M240 service menu?

Link to post
Share on other sites

Further note that there are two main versions of the coded lens flanges, one for the current generation lenses (6 screws) and one for older lenses (where only 5 screws are used since the sixth would have a required a hole in the region of the six-bit code).

 

I've only observed the "dodgy behavior" on 50/75 mm flanges of the new (6 screw) variety. Perhaps they are very slightly different in the some subtle way involving the frame line actuator and/or six bit code?

 

What other lenses have people observed this behavior with? So far only newer lenses with 50/75 frame lines have been mentioned (50/0.95, 75/2).

Link to post
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...