Collecting "freeze" data for 7D bodies running V2 firmware

Hey Ray

Sounds like you are another Auckland 7D user?

Along with mine, it looks like Canon NZ now have 2 freezing 7D bodies to play with since yesterday. I guess that puts little ole NZ at the centre of the global effort to understand the issue!

Fingers crossed they can work out a solution. I asked them today whether they could wipe my firmware v2.0.0 and reinstall v1.2.5 as a temporary solution until Canon work out a fix i.e. v2.0.1. Just to get my camera working and back to me?

Keep you posted.
arby157 wrote:
What URL did you use to pull the firmware? [Canon NZ]
Can you trigger the freeze at will?: [Yes, except for a few hours after being turned off over night.]
As best you can, please describe events that lead to freeze and what you do to recover?: [My 7D will be 2 years old in Oct. and has preformed faultlesly till the V2 update on the 23rd August. The download and install instructions were followed exactly, this is my 5th Canon camera from the G3. Except for the short time it behaved normally after the over night rest I could make it freeze up any time just by having the Auto Power Off set to 1 min. and it would freeze every time it went into sleep mode at the end of the 1 min. To stop it locking up I just set APO to OFF. I didnt do a lot of testing of diferent combinatons and just sent it back to Canon in Auckland yesterday (27th) after first ringing them and the tech guy said they may have to roll firmware back???. I hope not as I liked the new firmware, except the freezing bit lol. ]

Regards, Ray........another unhappy V2.0 updater
 
Wanted to mention also, that I went out today and snapped off about 400 clicks. My OOF ratio was amazingly disgusting!!! I can't believe it, but I was only getting about 1:4 sometimes 2:6 shots coming in focus... I have taken advantage of my MFA on my 7D and it was almost like getting new lenses and a new camera!

Now I am experiencing excessive OOF shots since upgrading FW. Not sure if it's related or not, but I'll be pulling out the stops and taking a new look at my mfa adjustments, tethering to my computer within the next 48 hours...

I've read that some folks had some type of AF issues after the upgrade, I really couldn't see how. I'll post my results back if anyone is interested in that data as well...

All the best,
Ken
I am very interested in your results with adjustments.

Please post back, Ken! Good luck!
--
Yogi

When you get down to the nuts and bolts of photography, the results depend on the 'nut' behind the camera!

See the 'Gear List' in my 'Profile' for my current equipment.

Check out WilbaW's beginner FAQs at - http://snipurl.com/RebelFAQ
 
Data: 7D s/n 1570803
Lexar Pro 400x32gb, formated in camera.
Installed from CF Card
Download from US site
Raw files
Auto PowerOff 30s
Lens: Canon 70-300L Is
Upgraded, and shot a few images.
Settings: AV, iso 400

First real outing with this camera was at the "America's Cup" in San Francisco, I had set the camera for high speed captures, and within a few burst shots, camera frooze, unable to power off and correct, unable to change setting, so I opened and re-installed battery, presto.. works again, but only briefly before it freezes again... this numerous times, sometimes at critical moments during the race.. apparently Canon did not test firmware enough.
 
That is awful! I do not understand what is happening, but I hope you can get it corrected OK. By the way, how do you set the auto poweroff to 30 seconds? The lowest I can set mine is 1min. 30 sec sounds quite useful.
Data: 7D s/n 1570803
Lexar Pro 400x32gb, formated in camera.
Installed from CF Card
Download from US site
Raw files
Auto PowerOff 30s
Lens: Canon 70-300L Is
Upgraded, and shot a few images.
Settings: AV, iso 400

First real outing with this camera was at the "America's Cup" in San Francisco, I had set the camera for high speed captures, and within a few burst shots, camera frooze, unable to power off and correct, unable to change setting, so I opened and re-installed battery, presto.. works again, but only briefly before it freezes again... this numerous times, sometimes at critical moments during the race.. apparently Canon did not test firmware enough.
--
kind regards
Dale
 
Hey Ray

Sounds like you are another Auckland 7D user?
Hi AC1,

No Im down in Christchurch and wishing I was in Auckland! or somewhere else nice and quite away from all the mess here...
Im looking forward to hearing back from Canon and will keep you all posted.
Good luck with your firmware problems.

Ray
 
OK, let's keep in touch then.
Hey Ray

Sounds like you are another Auckland 7D user?
Hi AC1,

No Im down in Christchurch and wishing I was in Auckland! or somewhere else nice and quite away from all the mess here...
Im looking forward to hearing back from Canon and will keep you all posted.
Good luck with your firmware problems.

Ray
 
Update. Just had a call from Canon and they confirm that they have identified a problem with the firmware v2.0.0 freezing issue.

From the 2 bodies given the Canon NZ by me and the other kiwi poster here (Ray), Canon NZ have obviously been able to recreate the freezing problem and confirmed it's for real.

They tell me that they expect Canon will issue an update to v2.0.0 ASAP but no date given.

Meanwhile, the good news is that the other Err 30 & 40 problems I have been having were unrelated - they found and fixed a screw that had come lose internally. That makes sense, it was a bad co-incidence of timing.

Meanwhile, anyone who has installed v2.0.0, it sounds like we are all now carrying faulty firware but if you disable APO you should be OK as an interim measure until an update is issued.

And all the nay-sayers who denied that there was ever a problem (just because they had not experienced it personally), go eat a big dose of humble pie!

Finally, Canon will not be charging me for either the investigation into the firware freezing problem (which is only fair) or for fixing the unrelated problem of the lose screw (which is a nice gesture).
 
AC1, thanks for being the guinea pig on behalf of everybody and patiently working with Canon service to get the problem identified. Great news!

I agree with you that it's time for the naysayers to eat humble pie :-)

I am baffled by the folks who were insisting that somehow the problem was due to improper FW installation, despite no evidence. And even more baffled by the folks who were encouraging people to waste their time with superstitious activities like "reset all your settings", continuing to ignore the evidence that it had no effect.

Glad to hear the issue is identified, and hopefully resolved soon.
Update. Just had a call from Canon and they confirm that they have identified a problem with the firmware v2.0.0 freezing issue.

From the 2 bodies given the Canon NZ by me and the other kiwi poster here (Ray), Canon NZ have obviously been able to recreate the freezing problem and confirmed it's for real.

They tell me that they expect Canon will issue an update to v2.0.0 ASAP but no date given.

Meanwhile, the good news is that the other Err 30 & 40 problems I have been having were unrelated - they found and fixed a screw that had come lose internally. That makes sense, it was a bad co-incidence of timing.

Meanwhile, anyone who has installed v2.0.0, it sounds like we are all now carrying faulty firware but if you disable APO you should be OK as an interim measure until an update is issued.

And all the nay-sayers who denied that there was ever a problem (just because they had not experienced it personally), go eat a big dose of humble pie!

Finally, Canon will not be charging me for either the investigation into the firware freezing problem (which is only fair) or for fixing the unrelated problem of the lose screw (which is a nice gesture).
 
I agree.

Which is why my position was "I should not need to spend hours and hours troubleshooting this issue on the basis of well-meaning but fact-free advice from other users!"

Hence I decided to short-cut the rumour and speculation and go direct to the experts. I am lucky to live so close to Canon NZ service centre that I can almost see it from home. And of course being kiwis, they are a very friendly and approachable bunch of people who were only too keen to have the opportunity to lay their hands on a camera for analysis.

So now we know.

All we do now is hurry up and wait (for a fix)!
AC1, thanks for being the guinea pig on behalf of everybody and patiently working with Canon service to get the problem identified. Great news!

I agree with you that it's time for the naysayers to eat humble pie :-)

I am baffled by the folks who were insisting that somehow the problem was due to improper FW installation, despite no evidence. And even more baffled by the folks who were encouraging people to waste their time with superstitious activities like "reset all your settings", continuing to ignore the evidence that it had no effect.

Glad to hear the issue is identified, and hopefully resolved soon.
 
Sounds very credible: Canon NZ within hours of receipt of your camera determine it's a firmware issue and fix a loose screw.
 
...quite some time = the evidence was quite compelling :) - very good
news for the whole 7d community - thank you :D,

jpr2
Update. Just had a call from Canon and they confirm that they have identified a problem with the firmware v2.0.0 freezing issue.

From the 2 bodies given the Canon NZ by me and the other kiwi poster here (Ray), Canon NZ have obviously been able to recreate the freezing problem and confirmed it's for real.

They tell me that they expect Canon will issue an update to v2.0.0 ASAP but no date given.

Meanwhile, the good news is that the other Err 30 & 40 problems I have been having were unrelated - they found and fixed a screw that had come lose internally. That makes sense, it was a bad co-incidence of timing.

Meanwhile, anyone who has installed v2.0.0, it sounds like we are all now carrying faulty firware but if you disable APO you should be OK as an interim measure until an update is issued.

And all the nay-sayers who denied that there was ever a problem (just because they had not experienced it personally), go eat a big dose of humble pie!

Finally, Canon will not be charging me for either the investigation into the firware freezing problem (which is only fair) or for fixing the unrelated problem of the lose screw (which is a nice gesture).
--
~
street candids (non-interactive):
http://www.flickriver.com/photos/qmusaget/sets/72157609618638319/
music and dance:
http://www.flickriver.com/photos/qmusaget/sets/72157600341265280/
B&W:
http://www.flickriver.com/photos/qmusaget/sets/72157623306407882/
wildlife & macro:
http://www.flickriver.com/photos/qmusaget/sets/72157600341377106/
interactive street:
http://www.flickriver.com/photos/qmusaget/sets/72157623181919323/

Comments and critique are always welcome!
~
 
Yea great news AC1,

puts my mind at rest! I can put my credit card away now. Maybe Canon tried to ring me too but Ive been out all afternoon.

Perhaps they will roll the firmware back for us till they get a fix for the new V2.0. thats what he said to me when I rang them on Monday.

Ray
 
Don't shoot the messenger, I'm just telling you want Canon told me.

They had it more than a few hours, it was at least 2 full days (and nights if they were looking at it urgently). And they found the lose screw early on, have spent the rest of the time on the firware issue. Along with the other body they had that didn't have a lose screw.
Sounds very credible: Canon NZ within hours of receipt of your camera determine it's a firmware issue and fix a loose screw.
 
I have a feeling that when Canon posts the fixed firmware online, this guy is going to claim Canon's home page was hacked, and the new firmware is fake. :-)
They had it more than a few hours, it was at least 2 full days (and nights if they were looking at it urgently). And they found the lose screw early on, have spent the rest of the time on the firware issue. Along with the other body they had that didn't have a lose screw.
Sounds very credible: Canon NZ within hours of receipt of your camera determine it's a firmware issue and fix a loose screw.
 
This guy will wait for some sort of confirmation from Canon. But maybe AC1 has some written records from his camera's trip to Canon. Something like a service report?
 
This guy will wait for some sort of confirmation from Canon. But maybe AC1 has some written records from his camera's trip to Canon. Something like a service report?
That's a good point, when I pick the camera up tomorrow or Fri I'll be very interested to see what the official service report says.
 
Looks to me like AC1 has "acknowledged" the issue in a different forum, not Canon. But today is Friday in NZ and we should see the repair report from his camera soon.
 

Keyboard shortcuts

Back
Top