No crashes with no logs are much better. It is good that they do log crashes as computers have been doing for years.Yeah, ie were there logs?
Crashes with logs are good!
Upvote
0
No crashes with no logs are much better. It is good that they do log crashes as computers have been doing for years.Yeah, ie were there logs?
Crashes with logs are good!
ha ha that's true!No crashes with no logs are much better. It is good that they do log crashes as computers have been doing for years.
Punctuation is all important. There is a book "Eats, shoots and leaves", which means something quite different from "Eats shoots and leaves".ha ha that's true!
Actually had to read first sentence twice, first time i read it as...
"No, crashes with no logs are much better."
Punctuation is all important. There is a book "Eats, shoots and leaves", which means something quite different from "Eats shoots and leaves".
You could try uncustomising the buttons one at a time and shooting 2000 shots each time, which by the time you have done 100,000-200,000 shots you should know. Or, as a more practical solution, uncustomise all for 2000 shots, then if that doesn't cure the situation, it's the camera. If it does cure, recustomise half to see if returns . If it still works you know it is in the other half etc. I have done relatively little customisation, just two buttons BBF for animal eyeAF and centre point AF as I like keeping things as simple as possible.Another update: I've taken the R5 out the last 2 days to photograph the starling murmurations that have been occurring in our area recently in the evening. The first night I probably shot 1500+ pics using low speed mech shutter and no crashes. Yesterday I shot about the same or less and was using high speed mech shutter and had 2 freezes. I must state further that I extensively customize the R5 and basically custom set every button and dial for my convenience. I have the camera set for 2 back button focus buttons, one for animal face detection and one for zone focusing. I am now wondering if this extensive customization is causing a software crash in certain shooting situations. Ugh!
Catherine
Well, I'm moving in that direction--I've uncustomized all the dials except for two which I switched. I've uncustomized the buttons and set up a single back button focus and customized one other button to change the drive mode otherwise the buttons are unchanged. We'll see if this changes any of the crashes. But I was never changing any of my focus settings when the camera froze--it was always while I was actively shooting.You could try uncustomising the buttons one at a time and shooting 2000 shots each time, which by the time you have done 100,000-200,000 shots you should know. Or, as a more practical solution, uncustomise all for 2000 shots, then if that doesn't cure the situation, it's the camera. If it does cure, recustomise half to see if returns . If it still works you know it is in the other half etc. I have done relatively little customisation, just two buttons BBF for animal eyeAF and centre point AF as I like keeping things as simple as possible.
I have a similar setup (spot focus instead of zone) and had read it may be related. I did not had a crash on two shoots since, and the only change is that I am shooting from a window mounted gimbal instead of a bean bag. I suspect it was a intermittent disconnect between the lens and camera, as I did see an error 01 once (and a crash shortly after). I suspect I would see this problem handheld if I had the strength to still do that. I use ProGrade Coblat CF cards. I wonder if their is a FW update for my 16 year old lens...Another update: I've taken the R5 out the last 2 days to photograph the starling murmurations that have been occurring in our area recently in the evening. The first night I probably shot 1500+ pics using low speed mech shutter and no crashes. Yesterday I shot about the same or less and was using high speed mech shutter and had 2 freezes. I must state further that I extensively customize the R5 and basically custom set every button and dial for my convenience. I have the camera set for 2 back button focus buttons, one for animal face detection and one for zone focusing. I am now wondering if this extensive customization is causing a software crash in certain shooting situations. Ugh!
Catherine
Another update: I've taken the R5 out the last 2 days to photograph the starling murmurations that have been occurring in our area recently in the evening. The first night I probably shot 1500+ pics using low speed mech shutter and no crashes. Yesterday I shot about the same or less and was using high speed mech shutter and had 2 freezes. I must state further that I extensively customize the R5 and basically custom set every button and dial for my convenience. I have the camera set for 2 back button focus buttons, one for animal face detection and one for zone focusing. I am now wondering if this extensive customization is causing a software crash in certain shooting situations. Ugh!
Catherine
In other news, I just had my second lockup today. This time using the RF 35mm f1.8 and Sandisk 512gb CF Express card. The first time this happened the screen just went black. This time I got an 'Error 70' message telling me to remove the battery. Has anyone else had the Error 70? Is it a seperate issue to the freezing do you think? or one and the same?
I never get a warning message associated with my lockups--the screen just freezes and the camera is inoperable and no button or dial functions until I remove and reinsert the battery.
Catherine
Unfortunately not. People are still having this issue even with the very latest firmware.Has firmware 1.2 released last November resolve this problem?
This time I got an 'Error 70' message telling me to remove the battery. Has anyone else had the Error 70? Is it a seperate issue to the freezing do you think? or one and the same?
I have had the error 70 msg after trying to use the canon connect app.Sorry to hear that. Given that they have replaced the motherboard of the camera we would have to assume this is some sort of software error right? Really hoping the next firmware release fixes this freezing.
In other news, I just had my second lockup today. This time using the RF 35mm f1.8 and Sandisk 512gb CF Express card. The first time this happened the screen just went black. This time I got an 'Error 70' message telling me to remove the battery. Has anyone else had the Error 70? Is it a seperate issue to the freezing do you think? or one and the same?
Thanks for letting us knowI have had the error 70 msg after trying to use the canon connect app.
FYI, My update from Canon...
"Many thanks for your response.
If you are using an LPE6NH battery (as opposed to an LPE6N or an LPE6), you will need to log a job at (Link) and send the unit in to our Camera Service team for testing and possible repair.
There's a possibility that the main circuit board is faulty. However, the unit will need to be booked-in for assessment by our service technicians. They need to physically inspect and test the camera.
Please ensure the camera is securely packaged to avoid any damage that could occur during transit. In the box with your camera please include a printed copy of your proof of purchase / sales receipt, the Canon Warranty Card and the Canon Camera Repair form, found here:"