horshack

Here's a Canomate script for automatically setting the camera's clock +1 day and then back:
https://www.magiclantern.fm/forum/index.php?topic=24827.msg230542#msg230542

Well, well - actually I did test it with my R5. Firmware 1.1.0 - and guess what: it works like at charm.
Let the camera overheat in the 120fps mode. Camera gets really warm. I guess I had something like 20 minutes in total (had to erase the clips from my card again and again). Anyway, after the camera overheated I opened the battery door, blocked the little latch to make the camera think it was closed. Went into the menue, forwarded the date by one full day. Confirmed. Took the battery out, waited some 15 seconds. Put the battery back in, closed the battery door. And here it was: Camera still warm after a short pause of 2 minutes (the time it took to go through the procedure) and what do I see in the display: Full recording time, no overheating sign. LOL. Canon, You've got a loophole there. Does the camera even bother to measure zhe temperature at all?!
Say thank you to yourboylloyd on Magic Lantern Forum.
Chris

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

 

Canon admitted to Gordon Laing the camera uses a timer in coordination with its temperature sensors https://www.youtube.com/watch?v=3bOeoYI6EYs#t=51s

I've just published a utility that allows for the automation of camera functions on newer Canon cameras like the R5/R6. It can be used to automate the thermal tests. Here's my thread on Dpreview with all the details:
https://www.dpreview.com/forums/post/64307212

I've just published a utility that allows for the automation of camera functions on newer Canon cameras like the R5/R6. It can be used to automate the thermal tests. Here's my thread on Dpreview with all the details:
https://www.dpreview.com/forums/post/64307212

I've just published a utility that allows for the automation of camera functions on newer Canon cameras like the R5/R6. It can be used to automate the thermal tests. Here's my thread on Dpreview with all the details:
https://www.dpreview.com/forums/post/64307212

Battery pull thermal timer workaround still works.

on it now.

I updated the firmware this morning then repeated old external test.
Recorded 4K HQ externally for over an hour with no card in camera. 
After 1hr 16 minutes passed I stopped the external recording, and inserted CFexpress card.
Once the R5 booted back up the counter said 20 minutes. Showed 25 minutes after shut down for less than 5 minutes.
So it seems the external recording is still good.

FYI, I started a new dpreview thread about all the experiments here, which is a continuation of my original thread here.

Let's hope Canon was already too far along in the testing/release cycle to plug the battery-pull hack in this V1.1.0 release.

Let's hope Canon was already too far along in the testing/release cycle to plug the battery-pull hack in this V1.1.0 release.

Let's hope Canon was already too far along in the testing/release cycle to plug the battery-pull hack in this V1.1.0 release.

Some said the HDMI w/o card long-recording workaround was a bug. I didn't believe it. Looks like they were right. Shaking my head. This also implies the thermal management isn't to protect the cards, otherwise why would they still throttle the camera without cards installed (assuming this update throttles both with and without cards).

According to TechRadar, the firmware doesn't address the overheating and actually engages it when using an external monitor:
"Canon has today released the EOS R5’s first firmware update and it’s available to download from the camera maker’s regional websites around the world. However, if you were expecting the firmware to improve on the current video limitations the R5 suffers from (as previous reports indicated it would), you’re going to be sorely disappointed.
The EOS R5 firmware version 1.1.0 only brings a couple of minor upgrades – it improves image stabilization for video recording, while also improving the combined stability of the camera’s in-body image stabilization system when paired with a stabilized lens, specifically the RF 100-500mm f/4.5-7.1 L IS USM telezoom.
According to Canon, the update also ensures that the overheat control on the EOS R5 doesn’t get disabled when using an external monitor or recorder. It will also improve the accuracy of the video time display when recording several short clips back to back.
None of these are quite what we were expecting but Canon has said there’s more to come."

Thanks for the .CSV data. Here's your data plotted. The running elapsed time was calculated from the EXIF timestamps:

19:02:22,00006996.MP4,47.5475,28
19:03:10,00006997.MP4,47.5475,32
19:03:58,00006998.MP4,47.5475,34
19:04:45,00006999.MP4,47.5475,36
19:05:33,00007000.MP4,47.5475,37
19:06:20,00007001.MP4,47.5475,39
19:07:08,00007002.MP4,47.5475,40
19:07:55,00007003.MP4,47.5475,41
19:08:43,00007004.MP4,47.5475,42
19:09:30,00007005.MP4,47.5475,43
19:10:18,00007006.MP4,47.5475,44
19:11:05,00007007.MP4,47.5475,45
19:11:53,00007008.MP4,47.5475,46
19:12:41,00007009.MP4,47.5475,47
19:13:28,00007010.MP4,47.5475,48
19:14:16,00007011.MP4,47.5475,48
19:15:03,00007012.MP4,47.5475,49
19:15:51,00007013.MP4,47.5475,50
19:16:38,00007014.MP4,47.5475,50
19:17:26,00007015.MP4,47.5475,51
19:18:13,00007016.MP4,47.5475,52
19:20:28,00006996.MP4,47.5475,48
19:21:16,00006997.MP4,47.5475,51
19:22:03,00006998.MP4,47.5475,52
19:22:51,00006999.MP4,47.5475,52
19:23:38,00007000.MP4,47.5475,53
19:24:26,00007001.MP4,47.5475,53
19:25:13,00007002.MP4,47.5475,54
19:26:01,00007003.MP4,47.5475,54
19:26:48,00007004.MP4,47.5475,55
19:27:36,00007005.MP4,47.5475,55
19:28:23,00007006.MP4,47.5475,56
19:29:11,00007007.MP4,47.5475,56
19:29:59,00007008.MP4,47.5475,56
19:30:46,00007009.MP4,47.5475,57
19:31:34,00007010.MP4,47.5475,57
19:32:21,00007011.MP4,47.5475,57
19:33:09,00007012.MP4,47.5475,57
19:33:56,00007013.MP4,47.5475,58
19:34:44,00007014.MP4,47.5475,58
19:35:31,00007015.MP4,47.5475,58
19:36:19,00007016.MP4,47.5475,58
19:38:32,00006996.MP4,47.5475,55
19:39:20,00006997.MP4,47.5475,57
19:40:07,00006998.MP4,47.5475,58
19:40:55,00006999.MP4,47.5475,58
19:41:42,00007000.MP4,47.5475,58
19:42:30,00007001.MP4,47.5475,59
19:43:18,00007002.MP4,47.5475,59
19:44:05,00007003.MP4,47.5475,59
19:44:53,00007004.MP4,47.5475,59
19:45:40,00007005.MP4,47.5475,60
19:46:28,00007006.MP4,47.5475,60
19:47:15,00007007.MP4,47.5475,60
19:48:03,00007008.MP4,47.5475,60
19:48:50,00007009.MP4,47.5475,60
19:49:38,00007010.MP4,47.5475,60
19:50:25,00007011.MP4,47.5475,61
19:51:13,00007012.MP4,47.5475,61
19:52:01,00007013.MP4,47.5475,61
19:52:48,00007014.MP4,47.5475,61
19:53:36,00007015.MP4,47.5475,61
19:54:23,00007016.MP4,47.5475,61
19:55:11,00007017.MP4,47.5475,61
19:56:53,00006996.MP4,47.5475,58
19:57:41,00006997.MP4,47.5475,60
19:58:28,00006998.MP4,47.5475,60
19:59:16,00006999.MP4,47.5475,60
20:00:03,00007000.MP4,47.5475,61
20:00:51,00007001.MP4,47.5475,61
20:01:39,00007002.MP4,47.5475,61
20:02:26,00007003.MP4,47.5475,61
20:03:14,00007004.MP4,47.5475,61
20:04:01,00007005.MP4,47.5475,61
20:04:49,00007006.MP4,47.5475,62
20:05:36,00007007.MP4,47.5475,62
20:06:24,00007008.MP4,47.5475,62
20:07:11,00007009.MP4,47.5475,62
20:07:59,00007010.MP4,47.5475,62
20:08:46,00007011.MP4,47.5475,62
20:09:34,00007012.MP4,47.5475,62
20:10:22,00007013.MP4,47.5475,62
20:11:09,00007014.MP4,47.5475,62
20:11:57,00007015.MP4,47.5475,62
20:12:44,00007016.MP4,47.5475,62
20:14:50,00006996.MP4,47.5475,58
20:15:38,00006997.MP4,47.5475,60
20:16:26,00006998.MP4,47.5475,61
20:17:13,00006999.MP4,47.5475,61
20:18:01,00007000.MP4,47.5475,61
20:18:48,00007001.MP4,47.5475,61
20:19:36,00007002.MP4,47.5475,61
20:20:23,00007003.MP4,47.5475,62
20:21:11,00007004.MP4,47.5475,62
20:21:58,00007005.MP4,47.5475,62
20:22:46,00007006.MP4,47.5475,62
20:23:34,00007007.MP4,47.5475,62
20:26:21,00006996.MP4,47.5475,57
20:27:09,00006997.MP4,47.5475,59
20:27:56,00006998.MP4,47.5475,60
20:28:44,00006999.MP4,47.5475,60
20:29:31,00007000.MP4,47.5475,61
20:30:19,00007001.MP4,47.5475,61
20:31:06,00007002.MP4,47.5475,61
20:31:54,00007003.MP4,47.5475,61
20:32:41,00007004.MP4,47.5475,61
20:33:29,00007005.MP4,47.5475,61
20:34:16,00007006.MP4,47.5475,61
20:35:04,00007007.MP4,47.5475,62
20:35:52,00007008.MP4,47.5475,62
20:36:39,00007009.MP4,47.5475,62
20:37:27,00007010.MP4,47.5475,62
20:38:14,00007011.MP4,47.5475,62
20:39:02,00007012.MP4,47.5475,62
20:39:49,00007013.MP4,47.5475,62
20:40:37,00007014.MP4,47.5475,62
20:41:24,00007015.MP4,47.5475,62
20:42:12,00007016.MP4,47.5475,62
20:42:59,00007017.MP4,47.5475,62
20:43:47,00007018.MP4,47.5475,62
20:44:35,00007019.MP4,47.5475,62
20:45:22,00007020.MP4,47.5475,62
20:46:10,00007021.MP4,6.423083333,62

That is the CSV data, so have at it 😉

Apparently a firmware update is coming tomorrow.
https://www.dpreview.com/forums/post/64300120
 

Coping an almost full 512 Sandisk CFE USB-C reader to internal M2 SSD did go in trothing mode after around 400 GB.... 7 time slower.. was all Canon RAW video files

My external battery has cut the test short unfortunately, 40 minutes into the test. The R5 gave the message to charge or replace the battery. I will repeat the test that I posted on youtube, tonight, running for over an hour this time, using two Sandisk 128GB SD cards in FAT32. Showing the clock again, and connecting the Ninja for the low-res 😉 4K Prores backup, and the thermal camera, and copying over all MP4 files in between, for proof. Just now I did not have time to copy the first run of MP4 files of the card. So tonight, or this afternoon if I have time.

Fantastic, that's a working solution for SD then. Canon might have removed the legacy FAT32 support starting with CFE since it's an easy technology inflection point to do so. 
Could I ask a big favor? Could you possibly run 8K recording for an hour, using battery pulls as necessary? Also, after you reach the hour could you immediate take a photo? I'll post a batch file that will extract the EXIF temperatures from all the files and put them into a .CSV file I can graph with Excel. Typing on my phone right now so don't have access to my computer this moment. Thanks again!
The data rate for 8K is about 162 MB/s so you may need to copy the files halfway through so you don't run out of card space. 

4K 30p FINE All-I works too:
 

I will now try to create a FAT 32 partition on the CFexoress with similar specifications as on the working SD card. Fingers crossed!

IT WORKS!!!
This is with a Sony UHS-II card, R5 recording 8K 23.98p IPB in roughly 680Mbps. I will try some other modes next, but I trust this will work in any mode available on SD. Pity that RAW does not work with this neatest of tricks. You guys are geniuses!
 

After a 6 minute run just now, it gives me 15 minutes again. As I am writing this the R5 is recording a 15 minute run. Will report back in 15 minutes 😉 No, I have two 1TB Integral Ultima CFE cards, and one Sandisk 512GB card. The Integrals run colder by the way. None of those 3 gave me an error or other disappointing behaviour, ever, for over a month now with the R5, a month full of abuse and power interruptions, hats off to those cards, the R5, and you and the others coming up with the FAT32 idea. Thanks a lot!