Jump to content

Wrong code detection is it a firmware problem?


FMB

Recommended Posts

Advertisement (gone after registration)

:( Scott, meanwhile you wrote it I was doing the test. Here yoo are, 5 diodos instead of 6.

 

Thank you all again.

 

 

Francisco

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

Mark, your comments as usual are excellent. Thank you for advising me about how to proceed for making my complaint. Something so complicate to repair means that the camera would be almost re-builded and, of course, checked with an special care. I'll ask for a new camera.

 

Francisco.

Link to post
Share on other sites

Couple of further thoughts.

 

First, Scott is entirely correct that the fact the LEDs are working doesn't mean the photodiodes and the transistors which amplify the signal back from them are.

 

Second, The M9 may be different from the M8 which was looking for a lens any time the camera was powered so that the focal length selection menu for the WATE could pop up as soon as one is mounted. That may not be true of the M9.

 

[For new readers: whereas the original Tri-Elmar ("MATE") coupled the selected focal length to the camera to select the required framelines, this is not true of the 16-18-21 Tri-Elmar ("WATE") which is wider than any of the built-in framelines. However, Leica discovered too late that the camera needed to know the selected focal length anyway for IR filter vignetting correction which is why there is a manual selection required when using the WATE].

 

This is how is in the M8, likely identical in the M9:

 

[ATTACH]184740[/ATTACH]

 

Mark's post reminded me of something odd that I noticed back when we were determining the limits of Sharpie coding non-Leica lenses to impersonate Leica lenses. You can hold the frame lever in the 50 or 28/90 position while a 35mm lens is mounted and the M8 firmware will know that the wrong frame is showing, interfering with recognizing the lens (or helping you if you wanted to make a 35 look like a 28). But if you mount a 28 mm lens and pull the frame lever back to the 50 or 35 mm positions, the firmware doesn't seem to notice. Mark's picture explains why. The lens code is really an 8-bit code, the extra two bits coming from the two microswitches that are in contact with the metal lever in the picture. That lever is held by a spring in contact with the lug on the lens mount whose length determines whether the 35mm (short lug), 50 mm (medium lug), or 28/90 mm (longest lug) frames are brought up. The second lever, which you see underneath in the picture, seems to be attached to the frame lever on the front of the camera. It can pull the first lever away from the mounting lug, but only in the direction of the 28/90 position.

 

And in answer to Mark's question, yes, the M9's lens id circuitry goes into action as soon as the camera is switched on. Francisco's picture of five lights shows this, but I did a simpler test. I installed a 35 mm lens on my M9 and switched the camera on. The info panel tells me that I have a 35/2.0 lens. I push the frame lever to the 50 mm position, and now I have an "uncoded lens." But if I mount a 28mm lens, it is recognized as 28 mm regardless of what I do with the frame lever.

 

So the innards of the M9 in this area seem to be exactly the same as in the M8.

 

scott

Link to post
Share on other sites

I have an occasional problem which is a bit different. Until now, it has affected my 28mm Summicron and the 35mm Summilux ASPH, both coded 'after the fact', but by Leica. Sometimes when the lens has just been mounted, and sometimes after it has just come on after sleep, it fails to recognize the lens and produces a shot with "lens uncoded" in the EXIF data, and very obviously without any correction of vignetting. The next shot however comes out right.

 

Strangely, my self-coded 18mm Distagon and 25mm Biogon never fail ... The 50mm Summilux ASPH, also 'retro-coded' by Leica, is also reliable.

 

The old man from the Age when Codes Were About Neckties

Link to post
Share on other sites

Advertisement (gone after registration)

I have an occasional problem which is a bit different. Until now, it has affected my 28mm Summicron and the 35mm Summilux ASPH, both coded 'after the fact', but by Leica. Sometimes when the lens has just been mounted, and sometimes after it has just come on after sleep, it fails to recognize the lens and produces a shot with "lens uncoded" in the EXIF data, and very obviously without any correction of vignetting. The next shot however comes out right.

 

Strangely, my self-coded 18mm Distagon and 25mm Biogon never fail ... The 50mm Summilux ASPH, also 'retro-coded' by Leica, is also reliable.

 

The old man from the Age when Codes Were About Neckties

 

The problem might be affecting only one of the LEDs, and in an intermittent form.

Link to post
Share on other sites

Hmm, Lars, that is kind of thought-provoking, I was just looking at a series of shots from last week, and one of the groups failed to name the hand-coded lens, the shots before and after did name the lens.. here is the funny part, the software did give up the guess F.stop, so the camera must have recognized the coding, but did not record the lens... go figure. never happened on the M8. ha ha.

 

.

Link to post
Share on other sites

I have the same problem. The first position seems to be the problem. My M8 camera is at Solms for repair (she likes Solms very much). The reliability of these cameras is a serious problem.

 

I think we are suffering all the old problems that the small companies have in this days (decades): If no succeed with a product red numbers, if succeed and have to increment the production the quality degrades and the supply terms grew. The small companies are always fighting with the rigidity of their dimension.

 

We should not buy a new camera till a year from the launch has past. It`s a pity!

 

Saludos,

 

Francisco.

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...