visionrouge

No, No need to do anything

It's very simple.
Canon do a very simple calculation.
When camera is running, a counter is setup. When the counter reach a certain level, you have a warning logo.
If you keep recording, the Log will become a shut down. This raise a flag that I will call "Fake Overheating flag"

At each of these step Canon is writing the exact time this occurs. Let's call it the "overheat start time".
This is done in an eeprom that is kept even if you remove the battery. The writing occurs when you shut down with the power button. This is the mistake right there.

There are only one way of getting the camera to work again is to wait extra time.
Canon do a simple calculation between "actual time" and "overheat start time". This way, even if the camera is off without battery, they can keep the time running with the help of the RTC.
It's a way of doing coding something very fast.

They also put a conditional test on "Fake Overheating flag" to make sure changing the time during the overheat mode will not change this calculation. My best guess is that they modify the "overheat start time" with the same value the camera time is shifted in this condition only. So each tentative to play this way is not working.

But I have the impression that the new "overheat start time" is written ONLY when the camera is power down. The new real time is written immediately.
So by dropping the battery, you are avoiding the "overheat start time" to be written and only the last one is in the memory.

When the power is restored, there is the calculation to see if you have been waiting enough. But based on the old "overheat start time", not the one shifted by the time modification. BOOOOM.

So the flag is now remove and the camera can start.
Even better, The camera is writing this new "Fake Overheating flag" value into the EEprom. So you can turn off the right way and it will restart without any problem.

You can now shift the time back, there is no check for a possible "overheat start time" cause we are not supposed to be in overheating mode.

So whatever card you are using, whatever R5 or R6, whatever firmware... it's working.
That was my idea at first when I noticed that the battery drop do not save all parameters. An yes, it works so beautifully.

No, No need to do anything

It's very simple.
Canon do a very simple calculation.
When camera is running, a counter is setup. When the counter reach a certain level, you have a warning logo.
If you keep recording, the Log will become a shut down. This raise a flag that I will call "Fake Overheating flag"

At each of these step Canon is writing the exact time this occurs. Let's call it the "overheat start time".
This is done in an eeprom that is kept even if you remove the battery. The writing occurs when you shut down with the power button. This is the mistake right there.

There are only one way of getting the camera to work again is to wait extra time.
Canon do a simple calculation between "actual time" and "overheat start time". This way, even if the camera is off without battery, they can keep the time running with the help of the RTC.
It's a way of doing coding something very fast.

They also put a conditional test on "Fake Overheating flag" to make sure changing the time during the overheat mode will not change this calculation. My best guess is that they modify the "overheat start time" with the same value the camera time is shifted in this condition only. So each tentative to play this way is not working.

But I have the impression that the new "overheat start time" is written ONLY when the camera is power down. The new real time is written immediately.
So by dropping the battery, you are avoiding the "overheat start time" to be written and only the last one is in the memory.

When the power is restored, there is the calculation to see if you have been waiting enough. But based on the old "overheat start time", not the one shifted by the time modification. BOOOOM.

So the flag is now remove and the camera can start.
Even better, The camera is writing this new "Fake Overheating flag" value into the EEprom. So you can turn off the right way and it will restart without any problem.

You can now shift the time back, there is no check for a possible "overheat start time" cause we are not supposed to be in overheating mode.

So whatever card you are using, whatever R5 or R6, whatever firmware... it's working.
That was my idea at first when I noticed that the battery drop do not save all parameters. An yes, it works so beautifully.

No, No need to do anything

It's very simple.
Canon do a very simple calculation.
When camera is running, a counter is setup. When the counter reach a certain level, you have a warning logo.
If you keep recording, the Log will become a shut down. This raise a flag that I will call "Fake Overheating flag"

At each of these step Canon is writing the exact time this occurs. Let's call it the "overheat start time".
This is done in an eeprom that is kept even if you remove the battery. The writing occurs when you shut down with the power button. This is the mistake right there.

There are only one way of getting the camera to work again is to wait extra time.
Canon do a simple calculation between "actual time" and "overheat start time". This way, even if the camera is off without battery, they can keep the time running with the help of the RTC.
It's a way of doing coding something very fast.

They also put a conditional test on "Fake Overheating flag" to make sure changing the time during the overheat mode will not change this calculation. My best guess is that they modify the "overheat start time" with the same value the camera time is shifted in this condition only. So each tentative to play this way is not working.

But I have the impression that the new "overheat start time" is written ONLY when the camera is power down. The new real time is written immediately.
So by dropping the battery, you are avoiding the "overheat start time" to be written and only the last one is in the memory.

When the power is restored, there is the calculation to see if you have been waiting enough. But based on the old "overheat start time", not the one shifted by the time modification. BOOOOM.

So the flag is now remove and the camera can start.
Even better, The camera is writing this new "Fake Overheating flag" value into the EEprom. So you can turn off the right way and it will restart without any problem.

You can now shift the time back, there is no check for a possible "overheat start time" cause we are not supposed to be in overheating mode.

So whatever card you are using, whatever R5 or R6, whatever firmware... it's working.
That was my idea at first when I noticed that the battery drop do not save all parameters. An yes, it works so beautifully.

Thanks for finally put my words in video.
Do you mind if In put this one into my post?
https://www.visionrouge.net/canon-r5-overheating-hack-solved/
 

No, No need to do anything

It's very simple.
Canon do a very simple calculation.
When camera is running, a counter is setup. When the counter reach a certain level, you have a warning logo.
If you keep recording, the Log will become a shut down. This raise a flag that I will call "Fake Overheating flag"

At each of these step Canon is writing the exact time this occurs. Let's call it the "overheat start time".
This is done in an eeprom that is kept even if you remove the battery. The writing occurs when you shut down with the power button. This is the mistake right there.

There are only one way of getting the camera to work again is to wait extra time.
Canon do a simple calculation between "actual time" and "overheat start time". This way, even if the camera is off without battery, they can keep the time running with the help of the RTC.
It's a way of doing coding something very fast.

They also put a conditional test on "Fake Overheating flag" to make sure changing the time during the overheat mode will not change this calculation. My best guess is that they modify the "overheat start time" with the same value the camera time is shifted in this condition only. So each tentative to play this way is not working.

But I have the impression that the new "overheat start time" is written ONLY when the camera is power down. The new real time is written immediately.
So by dropping the battery, you are avoiding the "overheat start time" to be written and only the last one is in the memory.

When the power is restored, there is the calculation to see if you have been waiting enough. But based on the old "overheat start time", not the one shifted by the time modification. BOOOOM.

So the flag is now remove and the camera can start.
Even better, The camera is writing this new "Fake Overheating flag" value into the EEprom. So you can turn off the right way and it will restart without any problem.

You can now shift the time back, there is no check for a possible "overheat start time" cause we are not supposed to be in overheating mode.

So whatever card you are using, whatever R5 or R6, whatever firmware... it's working.
That was my idea at first when I noticed that the battery drop do not save all parameters. An yes, it works so beautifully.

Confirmed by dellfonic user on magic lantern.
This is the final refinement on my hack.
You have the right time for your recordings!

Thanks for finally put my words in video.
Do you mind if In put this one into my post?
https://www.visionrouge.net/canon-r5-overheating-hack-solved/
 

Confirmed by dellfonic user on magic lantern.
This is the final refinement on my hack.
You have the right time for your recordings!

Well, one tester is not enough, please try to do the experience if you have a R5.
The procedure is explained here.
https://www.visionrouge.net/canon-r5-overheating-hack-solved/

In short:
- Power the camera with a external battery and close the door beside the R5 (you can also do the screw trick if you like)
- Record video until you see the overheating logo, or even until the camera shut down.
- Turn off the camera by using the power button so your recording parameters (ISO and so one) are saved.
- Turn back on the power.
- Go to the menu, Change the time of the day to +3 hours at least (or add a day)
- Drop the power by disconnecting the external battery
- wait 30 seconds
- Put back the external battery. the overheat issue should be gone.
(if not, you may actually be in real overheat situation), try in 10mn...
Please share your findings.

Confirmed by dellfonic user on magic lantern.
This is the final refinement on my hack.
You have the right time for your recordings!

Hey Andrew. Just to give a small correction. The original test was performed on my R6. Not the R5. But I've seen in comments that it's working on the R5 too

Well, one tester is not enough, please try to do the experience if you have a R5.
The procedure is explained here.
https://www.visionrouge.net/canon-r5-overheating-hack-solved/

In short:
- Power the camera with a external battery and close the door beside the R5 (you can also do the screw trick if you like)
- Record video until you see the overheating logo, or even until the camera shut down.
- Turn off the camera by using the power button so your recording parameters (ISO and so one) are saved.
- Turn back on the power.
- Go to the menu, Change the time of the day to +3 hours at least (or add a day)
- Drop the power by disconnecting the external battery
- wait 30 seconds
- Put back the external battery. the overheat issue should be gone.
(if not, you may actually be in real overheat situation), try in 10mn...
Please share your findings.

Ok, my trick works apparently. Tested by yourboylloyd on Magic Lantern Forum

Record as you wish.
When overheat occur. stop recording. Change the date.
Drop the power (using the screw story or dumb battery)
Put it back.
Timer is gone!
All camera parameters are saved. No need to open the camera, no need to lose your clip.
BOOOMMMMM
https://www.magiclantern.fm/forum/index.php?topic=24827.msg230515#msg230515

 

Well, one tester is not enough, please try to do the experience if you have a R5.
The procedure is explained here.
https://www.visionrouge.net/canon-r5-overheating-hack-solved/

In short:
- Power the camera with a external battery and close the door beside the R5 (you can also do the screw trick if you like)
- Record video until you see the overheating logo, or even until the camera shut down.
- Turn off the camera by using the power button so your recording parameters (ISO and so one) are saved.
- Turn back on the power.
- Go to the menu, Change the time of the day to +3 hours at least (or add a day)
- Drop the power by disconnecting the external battery
- wait 30 seconds
- Put back the external battery. the overheat issue should be gone.
(if not, you may actually be in real overheat situation), try in 10mn...
Please share your findings.

Ok, my trick works apparently. Tested by yourboylloyd on Magic Lantern Forum

Record as you wish.
When overheat occur. stop recording. Change the date.
Drop the power (using the screw story or dumb battery)
Put it back.
Timer is gone!
All camera parameters are saved. No need to open the camera, no need to lose your clip.
BOOOMMMMM
https://www.magiclantern.fm/forum/index.php?topic=24827.msg230515#msg230515

 

This is primary tested by one user, he put all his camera details as reference. Please wait to get backed and test with the Firmware 1.1 also.

1) I really don't see why the card format should have any impact there as the camera is not recording during the shut down. This time, this is just the date/stmap that is modified and not read at this specific boot.

2) Yes, at each time your camera is displaying the overheat logo, you need to increment to the next day, hours, month, year. But if your camera, during lunch break is able to cool down by itself anyways, you can put back any date. The idea is to trick the timer only when overheating flag is on. The camera at boot look at (current time - overheat warning time). if it's more than the predefined "fake recover time" you are good to go.

Ok, my trick works apparently. Tested by yourboylloyd on Magic Lantern Forum

Record as you wish.
When overheat occur. stop recording. Change the date.
Drop the power (using the screw story or dumb battery)
Put it back.
Timer is gone!
All camera parameters are saved. No need to open the camera, no need to lose your clip.
BOOOMMMMM
https://www.magiclantern.fm/forum/index.php?topic=24827.msg230515#msg230515

 

Ok, my trick works apparently. Tested by yourboylloyd on Magic Lantern Forum

Record as you wish.
When overheat occur. stop recording. Change the date.
Drop the power (using the screw story or dumb battery)
Put it back.
Timer is gone!
All camera parameters are saved. No need to open the camera, no need to lose your clip.
BOOOMMMMM
https://www.magiclantern.fm/forum/index.php?topic=24827.msg230515#msg230515

 

Ok, my trick works apparently. Tested by yourboylloyd on Magic Lantern Forum

Record as you wish.
When overheat occur. stop recording. Change the date.
Drop the power (using the screw story or dumb battery)
Put it back.
Timer is gone!
All camera parameters are saved. No need to open the camera, no need to lose your clip.
BOOOMMMMM
https://www.magiclantern.fm/forum/index.php?topic=24827.msg230515#msg230515

 

Ok, my trick works apparently. Tested by yourboylloyd on Magic Lantern Forum

Record as you wish.
When overheat occur. stop recording. Change the date.
Drop the power (using the screw story or dumb battery)
Put it back.
Timer is gone!
All camera parameters are saved. No need to open the camera, no need to lose your clip.
BOOOMMMMM
https://www.magiclantern.fm/forum/index.php?topic=24827.msg230515#msg230515

 

Someone suggested that the overheat icon should be changed with a middle finger on a future firmware... I love this idea!🖕
 

Thanks for sharing.
It's look like they tweaked the recovery time and add new functionality to the infamous counter that now include the length of previous recording in the balance.
If you shoot short clip,s you can shoot more of them (from 22 to 96 now in his testing)
Recovery time is about 2 minutes wait for 1 minute recovery, or one minute wait for one minute recovery inside a fridge.
Still a bit far from the graph I can see on this post threat. Recovery temperature look way faster than this.

Bye the way; 0 apology from Canon so far.
The best sentence is:
"We have and will continue to be transparent about recording limits for the EOS R5" 😂

Like you can't shoot any HQ mode after 60 picture during an hour inside a fridge...
Transparency? Please Canon, let me know where in your manual you explain this?

The max recording time is reset if you remove the battery cause we don't check temperature at boot but be assured we are very conservative on temperature management.


 

Someone suggested that the overheat icon should be changed with a middle finger on a future firmware... I love this idea!🖕
 

Someone suggested that the overheat icon should be changed with a middle finger on a future firmware... I love this idea!🖕
 

Someone suggested that the overheat icon should be changed with a middle finger on a future firmware... I love this idea!🖕