Pages: [1]   Go Down

Author Topic: MFDB jam: what #$%@! happened?  (Read 1665 times)

lowep

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 568
    • http://sites.google.com/site/peterlowefoto/
MFDB jam: what #$%@! happened?
« on: July 21, 2011, 01:54:29 pm »

I took my eMotion75 with Contax 645 out this afternoon to snap a few test shots before heading out of town. Much to my surprise I got a red warning screen advising me the back had a communication problem with the camera; after I turned the camera off and on again the warning screen disappeared; but when I fired the next test shot a nasty red dot appeared in the place of the green OK button on the MFDB and everything froze.   :o

As you can imagine I was happy when I turned the MFDB back off and on again that everything seemed to be working as usual - until I took another test shot and the MFDB jammed again; refusing to respond to any menu buttons or to switch off though this time the green OK button remained lit.  >:(

When I opened the battery/CF card door on the side of the MFDB the red light that indicates the back is writing to the CF card was lit. Not being made of stone I was VERY tempted to just remove the battery and reboot until I checked the instruction manual that says: "When an image is being recorded on the CF card, the CF card symbol lights up in red. The CF card must not be removed from the Sinarback eMotion while the CF card symbol is lit up in red" so instead decided to do nothing and see if anything happened.  ???

After a few minutes the red light went off, the menu buttons unfroze and I was able to turn the MFDB off normally via the power switch on the back of the unit. Now I just took another shot and everything appears to be working normal again.  :)

Fortunately this happened on home turf during a test rather than out in the field. Just not sure what happened? Could this problem be corrupt firmware, loose connection of MFDB to camera, corrupt CF card, all of the above, or...?
« Last Edit: July 21, 2011, 01:57:00 pm by lowep »
Logged

revaaron

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 333
Re: MFDB jam: what #$%@! happened?
« Reply #1 on: July 21, 2011, 01:56:33 pm »

side note: shooting a wedding 2 weekends ago BOTH of my partner's camera's had the same part fall out with in 1hr of each other. (canon 5d mirror).

lowep

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 568
    • http://sites.google.com/site/peterlowefoto/
Re: MFDB jam: what #$%@! happened?
« Reply #2 on: July 21, 2011, 02:31:24 pm »

So did they agree to repeat their wedding for you?
« Last Edit: July 21, 2011, 02:51:52 pm by lowep »
Logged

TH_Alpa

  • Full Member
  • ***
  • Offline Offline
  • Posts: 214
Re: MFDB jam: what #$%@! happened?
« Reply #3 on: July 21, 2011, 05:16:14 pm »

I don't think this is a serious issue, rather a mishandling in connection with CF card recording.

Thierry

Could this problem be corrupt firmware, loose connection of MFDB to camera, corrupt CF card, all of the above, or...?
Logged

Graham Mitchell

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 2281
Re: MFDB jam: what #$%@! happened?
« Reply #4 on: July 21, 2011, 05:58:51 pm »

It's worth trying a new CF card.
Logged

revaaron

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 333
Re: MFDB jam: what #$%@! happened?
« Reply #5 on: July 21, 2011, 06:11:04 pm »

So did they agree to repeat their wedding for you?
heh, I was there with 3 nikons so it was all good.

Jack Varney

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 413
    • http://
Re: MFDB jam: what #$%@! happened?
« Reply #6 on: July 21, 2011, 10:40:15 pm »

I live near the ocean in Florida and find it necessary to frequently clean the contacts between the P45+ back and the Mamiya to which it is attached. Even though these contacts are gold plated it is not a guarantee against poor continuity. Perhaps this is your problem.
Logged
Jack Varney

lowep

  • Sr. Member
  • ****
  • Offline Offline
  • Posts: 568
    • http://sites.google.com/site/peterlowefoto/
Re: MFDB jam: what #$%@! happened?
« Reply #7 on: July 22, 2011, 05:43:01 am »

thanks for the reassuring feedback - looks like one of those paranormal black hole/glitch/bad-hair-day thingies. Just reformatted the CF card, rubbed the gold contacts with a microfiber cleaning rag, sacrificed three chooks and everything seems to be working ok.

Just in case this ever happens again am contemplating investing in 3 nikons and a partner with 2 canon 5ds as back up (given the weight maybe 5 M9s instead?) -- though have not made this jump yet.
Logged

bcooter

  • Guest
Re: MFDB jam: what #$%@! happened?
« Reply #8 on: July 22, 2011, 05:49:31 am »

With the Contax, it 's rock solid if prior to every shoot you take all the lenses, prisms, backs and polish the contacts.  Not just clean them or rub them with a solution, but really polish them with a lint free towel like your polishing a jewel.

Then as long as the prisnm mounts securly your good to go.

If you live next to a costal area, or shoot on the beach you have to do this more often.

The one and only one glitch with the Contax is it's easy to break to mounts that hold the prism onto the body, which will result in movement and erratic performance.

You can get extra pins from ToCAD but the best way to avoid this is to travel with the prism off the body and never pick up the camera by the prism.

Other than that the Contax is dead solid forever.

IMO

BC

Logged
Pages: [1]   Go Up