Canon R6 II R6 MklI body returned from CPS, they can not fix the problem and apologize.

[Chris Summers]

I finally got my camera back from Canon. They were able to replicate my issue with the camera firing after I take my finger off the shutter button as described in previous posts. The repair ticket states under Service Details:

"Your product was examined. We are aware of the issue accruing with the shutter and is being investigated. Currently there is no fix for this issue, we are working to provide a solution. We are deeply sorry for any inconvenience this issue may have caused. Thank you for your patience."

The service advisor I spoke with said that it will most likely require a firmware update from Canon USA and Canon Japan. Not holding my breath. The R6 MkIII is supposed to debut later this year so I doubt they will do much more work on the M6 MkII.

 

[MikeZ]

Sorry to hear that, Chris, but a firmware fix seems appropriate irrespective of a new model on the horizon. This is not the absence of a feature but a defect that effects EVERY R6 MkII so a fix is warranted (in my opinion, anyway).

 

[chipman]

With the MkIII on the way they may take an extra hard look at your problem since they won't want it to show up on the new model.
I wonder if some condition makes the camera run slow, maybe 28 fps instead of 30 fps, so the camera keeps shooting to fill the extra frames.
Ex. - You hold the button for 3 seconds, telling the camera you want 90 frames. But the camera is only doing 28 fps, giving you 84 frames when you release the button, so it adds 6 frames after the release to make the 90 frames.
Just a WAG, but maybe there's some way you could check if the camera is doing 30 fps when this happens?

 

[TwoWheeler]

“We have updated the user manual to include the Post Capture feature, so camera is working as intended”

 

[ShipleyNW]

With the MkIII on the way they may take an extra hard look at your problem since they won't want it to show up on the new model.

Yep. The MkIII will probably contain about 80% of untouched code from the previous model. They won't want to push bad code forward, especially bad code that's already been identified. This bug doesn't sound too complicated. Getting it on somebody's list and letting it percolate to the top of the list is the biggest hurdle to getting it fixed. If the bug is in the code moving to the new model, that will bump up its priority for a fix on the previous model.

 

[timm]

I would ask for my money back, or a 100% credit towards another camera.

 

[Photofarmer]

Exactly How many cameras have to show a problem before they decide on a fix?
Be good business to give a credit how hard is it for ONE customer?

 

[TwoWheeler]

I would ask for my money back, or a 100% credit towards another camera.

You are such a small-time thinker.

I would ask for both.

 

[ShipleyNW]

Have you looked for workarounds? Did your CPS guy say if they'd figured out the exact problem; the combination of settings that trigger that post-release firing? (Let's call it PRF for short.)

I mentioned somewhere that I'd seen this problem with my R7. It only happened when I used H+ with the electronic shutter. When I stopped doing that, the problem went away. I stopped shooting 30 FPS because that's too fast for anything I shoot. The benefits of possibly getting that One Shot weren't enough to counteract having to cull thousands of nearly-identical images. So that's why I stopped, but coincidentally, the PRF problem stopped as well. Do those 2 things alone -- H+ and Electronic Shutter -- cause PRF, or are there other settings involved?

Since Canon didn't seem to know about the PRF until you brought it to their attention it makes me think that you and I stumbled into some combination of settings that no one else really tries. This whole mirrorless thing is pretty new to me so I wouldn't be surprised to find out I set something stupid. Happens all the time.

Personally, I didn't think the PRF was anything more than odd. It wasn't costing me shots. I'd already made 90 frames at the far turn, so that extra half dozen, or whatever, while I was dismounting from the pan, were tacked on at the end and I could just skip over them in post while thinking, that was weird when that happened. What was that about?

But if you find it annoying, that's a valid beef. Maybe they can find you something that's a little less annoying, if not exactly your first choice. Heck, maybe they'll have you change a setting you didn't even know you set and won't miss at all. Buy you some time until they get the fix into a firmware release.

 

[chipman]

There's a section in the owner's manual that lists the things that could slow down burst rates. Maybe the 'PRF' is a side effect of those occurrences.
Be glad it's not a Harley. Their standard answer is "They all do that."

 

[Bryan Conner]

I am considering buying an R6 Mark II in the fall. I prompted Google Gemini to investigate this problem and it returned the following info:

Yes, there are indeed other reports of Canon EOS R6 Mark II cameras continuing to take photos after the shutter button is released. This appears to be a known, though not necessarily universal, issue that has been discussed in various online forums.

Here's a summary of what the reports indicate:

• Common Scenario: The problem most frequently occurs when shooting in High-Speed Continuous (H or H+) mode, especially when using the Electronic Shutter and Back Button Focus (BBF). Users describe the camera continuing to fire for several extra frames (sometimes 10-15 or more) even after their finger has been lifted from both the shutter button and the BBF button.
• Triggering Factors:
  
  • High-Speed Burst Modes (H/H+): This seems to be the primary commonality. The camera's ability to shoot at very high frames per second (e.g., 30fps with electronic shutter) appears to play a role.
  • Electronic Shutter: While some reports don't explicitly state it, the electronic shutter is often implied or mentioned in conjunction with the high frame rates where this occurs.
  • Back Button Focus (BBF): Many users experiencing this issue also utilize back button focus, and some describe it as a "quirk" when quickly "blipping" or modulating the BBF and shutter buttons simultaneously.
  • Sporadic Nature: The problem is often described as sporadic and difficult to consistently reproduce, making it challenging for users and even Canon service centers to diagnose.
• User Experiences and Theories:
  
  • Not a "Stuck" Button: Most users report that the physical shutter button is not actually stuck. Instead, it seems to be a digital or processor issue.
  • Buffer/Lag: Some theories suggest it might be related to the camera's buffer trying to clear or a lag in communication between the autofocus system and the shutter in high-speed scenarios.
  • Firmware Bug: A strong theory, supported by some users, is that it's a firmware bug. One user even reported that a Canon Professional Services (CPS) agent hinted that Canon Japan might need to get involved, suggesting it could eventually be addressed in a future firmware update.
  • SD Card Speed: While less commonly cited as the cause of continuous firing after release, slow SD cards are mentioned in relation to overall camera lock-ups or delays in processing, which could potentially exacerbate buffering issues. However, the "continues to fire" issue specifically seems to go beyond a simple buffer-full delay.
• Repair Attempts and Outcomes:
  
  • Several users have sent their cameras to Canon for repair. Some have had components like the shutter mechanism or motherboard replaced, with mixed results (fixed for some, not for others).
  • One particularly notable case involves a user who sent their R6 Mark II to CPS multiple times for this issue. They eventually received a loaner camera, and the loaner also exhibited the same behavior, strongly suggesting a widespread firmware or design flaw rather than an individual camera defect.

Where to Find These Reports:

The issue is discussed on various photography forums, including:

• Canon Community Forums (USA): Several threads directly address "High Speed drive - doesn't stop taking photos after releasing shutter button" and similar topics.
• RF Shooters Forums: Users have detailed their experiences and troubleshooting attempts on this dedicated forum.
• Reddit (r/canon): You can find discussions there as well.
• Fred Miranda Forums: This is another popular platform where photographers discuss gear issues.

In conclusion, the problem of the Canon EOS R6 Mark II continuing to take photos after the shutter button is released is not an isolated incident. It has been reported by multiple users, primarily in high-speed electronic shutter modes with back button focus, and appears to be a software or system-level quirk that Canon is aware of, though a definitive public solution (like a specific firmware fix) is still awaited by some users.

 

[ShipleyNW]

• One particularly notable case involves a user who sent their R6 Mark II to CPS multiple times for this issue. They eventually received a loaner camera, and the loaner also exhibited the same behavior, strongly suggesting a widespread firmware or design flaw rather than an individual camera defect.

I wonder who that could have been?

 

[Bryan Conner]

I wonder who that could have been?

I think I have an idea. Maybe Chris will read this and offer his opinion. Along with maybe an update.

 

[Chris Summers]

The camera was returned, basically all they did was a factory reset and told me if they come up with a solution they will let me know. The camera dropped out of warranty while they had it so, I think the CP rep said they would consider anymore issues related to this to be under a 6 month repair warranty or something.

To be honest, it's summertime here in SE Texas so too hot and humid for much in the way of fast moving imaging like birds or kids on the soccer field. I'll start back with that stuff in the fall, I guess I will just live with the extra shots my camera decided to take. Overall, I still love this camera and don't plan to replace it with the III model when it arrives. Being retired now, the wife and I try to live on a budget we can afford.

 

[ShipleyNW]

When they do fix it and get it into firmware, I'm still going to call that the Chris Summers fix. Even AI knows about you. Damn.

I just looked at the release notes from the firmware that came out yesterday. Doesn't look like we made the cut on 1.6.0. Maybe 1.7. Probably some time next year.