Can confirm that the time was set correctly.
OK, that strongly points to a script error. Since this is on the new version of the script, there's a good chance it's a bug, so if we don't track it down before your shoot, you might want to stick to the old version.
You can try to reproduce it using the same settings and (if possible) similar scene, and then check the console for script errors without shutting down.
You can also make the log save after every shot, which might narrow down the conditions when the error occurs, but this will likely reduce shooting right, and could potentially affect whatever was triggering the bug in the first place. To do this, remove the initial -- from the line (around line 1811, under log = xsvlog.new)
-- buffer_mode='sync', -- for crash debugging, save every line
so it looks like
buffer_mode='sync', -- for crash debugging, save every line
That said, I'd suggest trying to reproduce without doing that first, since I suspect the console error will be more informative.
Camera was being run on an extrenal power supply.
While I suspect this is a script bug, one thing that is notable is that your previous runs were rock solid at 4.769 volts, while this one was bouncing around between 4.4 and 4.7. Was it the same powerbank based power supply, or something different?
I also see a partial run at the start of the log, which starts at 4.769 and then drops slightly.
If it's the same supply, that might be worth investigating. A powerbank will likely try to provide a fixed voltage until it's low, and then cut off, so the script (and Canon firmware) low batter detection would not function. Also, if the Canon firmware thinks it's on external power, the Canon low battery logic may be disabled in any case (I'm not sure if cameras like sx520 detect external power specifically, some cameras do.)
