While out shooting sports for a newspaper, I started getting Error 30 on my 7D. When I turned on the camera, my battery on the LCD was flashing empty. I re-seated the battery a few times, and the camera came back on. It then gave me error 30 multiple times.
I think something about the weather may cause the problem to flare up.
Back in the middle of July, I was shooting an E-session with my 24-105L. I live in East Texas, and it had just rained and was over 100 degrees. I tried to do a fast sequence using the high FPS setting. I got some error...I'm not sure which one it was though. I didn't allow myself to think about it, because I was working...didn't want the couple to lose faith in me or see me flustered. I finished the job with my backup body (a 30D).
I left to go on a trip to Colorado the next day. I met a friend half way, and he let me borrow a new CF card and a battery grip. It was hot for Colorado (highs in the 90s), but there was no humidity. I did A LOT of shooting at a skate park...high fps and everything, and it worked fine.
I gave my friend his stuff back on my way home. I've only used the camera a handful of times, running 50 or more shots through it each time.
Tonight, on the third shot, the error popped up. I was using a 300/4L. It wasn't as hot...only 99 at game time, but I had just brought it out from air conditioning (my thought is that condensation could have triggered it?).
I kept checking the 7D, but it kept giving me the error. I'd take out the batteries and let it sit for 10 mins or so. About an hour into the game, the camera started working right. The error never came back.
I bought my 7D in Nov 2009. The warranty is obviously expired. I doubt there's over 10K clicks...I know the shutter is rated for 150K, but I'm sure I'll have to pay something.
Anybody else have a story about Err 30? How did you fix it? DId you have to send it in? If it wasn't covered under warranty, how much was it to fix? I'm a part time youth minister/husband/daddy of 2/grad student, and money is pretty tight. I'm just trying to brace myself for what may be down the road.
I'm pretty sure the smartest thing is to send it in...I can't assume that its fine. Thats what I did today, and I had to go back home for my backup.
I got this last night when shooting my sons football game. I also purchased in Nov 2009. I have about 30K clicks on the shutter and the error seemed to be intermittent. Last night I took the advice on one of the forums to disable liveview and guess what I took a ton of shots last night without a single issue. I am just trying to make it through the month and then off to Canon.
I just joined CPS last night. I'm sending it in on Tuesday. I've got a buddy who was letting me borrow a lens, and he is sending me his backup 7d to use, as next Saturday I'm covering 2 games for 2 separate people (newspaper and a school). I'll update when I hear something
I sent in my 7D in June after getting intermittent Error 30's. It was also around the 30k shutter count. Ended up costing me $126 with the CPS discount. The description of the repair work was as follows:
Your product has been examined and it was found that the part was not properly connected causing error 30 to be displayed from time to time. Repaired mirror box mech, adjusted exposure & focus, cleaned C-mos and checked all factory specs. Update firmware.
I never found out what "the part" was. Whatever they did, it's been working fine ever since.
After reading that response about a part not being properly connected, I guess I need to send in my MK3.
I got the error 30 several times while on vacation last July. Luckily, I had my MK2N as backup. Took out the battery on the MK3 every time I got the error and finally got it working again. Have shot about 5,000+ frames since the error and it hasn't come up again. I might not be as lucky as I think.
FWIW - I started getting Error 30 problems on my 5DII last year @ 13,000 clicks. Sent it in for repair. The work order said they replaced "main bottom fpc", "front fpc ass'y" and "bottom pcb ass'y". I think these are circuit boards, but don't really know. Has worked fine ever since.
