EF 16-35mm f/2.8L II USM not working with EOS R5

[aox]

Hi,

I've had a 16-35L parked on my 6Dm1 for eight years. It's an incredible lens that has never failed me and I take care of my gear despite its proven durability. I've taken hundreds of thousands of frames with this lens all over the world in all conditions (besides severe cold). The contact pins are IMO pristine:

They are not bent and there is absolutely no gunk or goo on any of them. I bought a R5 this week and keep getting the Eror 01 notification. I have both the Canon EF-R mount and a Viltrox 3rd party EF-R mount. Regardless of the mount, I still get the error on both of them, and even before I turn the camera on, the motor in the lens is going nuts once I screw it onto the mount. My other five lenses work perfectly with both mounts on the R5. Sometimes after using a different lens for a while, I can sneak the 16-35 onto the R5 and it will work for a short undetermined time before it goes back to Eror 01 and the motor begins going nuts again (for the brief time it works on the R5, it works perfectly). I placed the 16-35 back onto my 6D and a 60D, and it works just fine with no issues on both bodies. I have certainly used a wet dry cloth and rubbed down the pins. Why is my new R5 rejecting this lens?

I've never had lens problems so I am not sure what to do here or if there is some trick I am missing in my Google search. Do I need to get this serviced? I assume there is a decent place in NYC so I don't have to mail this in? Is there anything I am missing?

Thanks for your help or advice in advance. 

[ebiggs1]

You already have your answer. The OP said Canon confirmed they needed to check it out for possible repairs.  "He said that I needed to ship my lens, the RF mount, and my new R5 back to Canon and let them diagnosis it and maybe they could repair it. 

[moschu88]

Thanks. I read it. It's not a solution to me.

My curiosity went beyond this information: Was Canon able to fix it? Does it work reliably after repair? Did they give any details about what was wrong? Maybe the OP was even able to gather more info over the years about this issue.

[Waddizzle]

---

@moschu88 wrote:

Thanks. I read it. It's not a solution to me.

My curiosity went beyond this information: Was Canon able to fix it? Does it work reliably after repair? Did they give any details about what was wrong? Maybe the OP was even able to gather more info over the years about this issue.

---

You should start a new thread for your issue.  This thread is several years old.  

[moschu88]

Same issue, same set-up. To me it makes sense. My intention was to reach the originator. Maybe he would get an email notification upon my response to this thread.