Timelapse program failed (Logs attached)

[Espusen]

Hi David
3'rd failure I have had this week. Two cameras on the same site:

Code: mPdP>08:00<17:00!S+!1N+!299RQ!3600RQ
https://drive.google.com/drive/folders/1IZMHiWWS-n4OgAahBjHBW9ssxgQcVLoc?usp=sharing

[Espusen]

Got another here for you.
Done with the debug program as well
Failed after 3 days running this script: mPdP>08:00<17:00!S+!1N+!299RQ!3600RQ
https://drive.google.com/drive/folders/1jW-nuwGnmRn__6ZTCP7-6_3v1wsM-v8S?usp=drive_link

[kojak357]

Anyone else from GoPro to help with these issues? Doesn't look like David is around to help.

[Zergo333]

What is your question?

I just have the same issue with camera waking & have no idea how to prevent failure. Sorry i'm new for labs firmware & github also.
I'm also tried with battery installed & camera isn't starting timelapse, just isn't woking up immediatly afted QR code is activated.
My current code lokks like that https://gopro.github.io/labs/control/set/?cmd=!74NQmPN!S!1R&title=Extra%20Long%20Timelapse

Most time I tried to use this one. Maybe you see something that I'd tried last time. Here is the script generated by default extra long timelapses code generator

[dnewman-gpsw]

That script could be revisited. The camera has evolved, those scripts are 3-4 years old. I'm just looking for potential point of failure, which I'm not experiencing.

[Zergo333]

Hello again. Nothing new, it's still failing
qrlog.txt

[dnewman-gpsw]

Can you please try with Trust USB disabled (use *TUSB=0), this seems to disabling the battery monitoring in your logs. I don't see 00% is my testing. With a battery you shouldn't need TUSB.

[2024-09-27 04:28:10-delayed ] wake reason:RTC_ALARM 
[2024-09-27 04:28:11 100%  ] Woke with Alarm:[04:28m01]!NQmPN!S!1N!9R 
[2024-09-27 04:28:11 --%   ] Labs:Display Messages 
[2024-09-27 04:28:11 --%   ] Labs:Main Start 
[2024-09-27 04:28:11 --%   ] Labs:H23.01.02.20.72 
[2024-09-27 04:28:11 --%   ] Labs LCD ID:195 
[2024-09-27 04:28:11 --%   ] Naked when 0:1 
[2024-09-27 04:28:12 --%   ] Labs:Initialize 
[2024-09-27 04:28:12 --%   ] Bat Temp.:0 
[2024-09-27 04:28:12 --%   ] Woke with Command:[04:28m01]!NQmPN!S!1N!9R 
[2024-09-27 04:28:12 --%   ] Start Now:Past by 12 seconds 
[2024-09-27 04:28:12 --%   ] Countdown:complete 
[2024-09-27 04:28:12 --%   ] Timer wake command:!NQmPN!S!1N!9R 
[2024-09-27 04:28:12 --%   ] ACTION:!NQmPN!S!1N!9R 
[2024-09-27 04:28:12 00%   ] token:PN 
[2024-09-27 04:28:12 00%   ] CAMMODE token:PN 
[2024-09-27 04:28:12 00%   ] ACTION:!S!1N!9R 
[2024-09-27 04:28:13 00%   ] STARTCAPTURE:0 
[2024-09-27 04:28:17 00%   ] ACTION:!1N!9R 
[2024-09-27 04:28:18 00%   ] delay:end 
[2024-09-27 04:28:18 00%   ] ACTION:!9R 
[2024-09-27 04:28:29 00%   ] ACTION:!85NQmPN!S!1N!9R 
[2024-09-27 04:28:32 00%   ] Shutdown and Sleep:80 seconds 
[2024-09-27 04:28:33 00%   ] sleep:80 

All those 00% battery reports are confusing me, it should not be doing that.

[Zergo333]

My powering device isn't working without tusb enabled, & also camera is not working with this commands with internal battery & extarnal power plugged simultaneously. Now camera is busy by this command !85NQmPN!S!1N!2R pending with only internal battery. Still waiting

[Espusen]

Thank you David.
It is troubling that it was so reliable and steady for the first few months of testing for me, then it is now back to Hero9 failure rates.
Also for my clients that are attempting to use it.
I am still waiting for the "smoking gun" that will resolve it..

[Espusen]

Had another failure today. Never woke up after the 25'th
https://drive.google.com/drive/folders/1fX1V9y_7Y9aDpEoVCHU0HO_9wwXZPjBV?usp=sharing

[dnewman-gpsw]

That camera is running two generations older firmware (HERO12 firmware from Dec '23), was that intentional? But I have also found that to be reliable firmware, as I that that is the version I have run for 9 months timelapse now.

[Espusen]

No not intentional.
I reset the camera to factory settings before this test. I forgot to update firmware.
Labs is up to date tho?

[dnewman-gpsw]

I did a simple test with an approximate 60 second interval, running six cameras under internal batteries only, all ran until the batteries where flat. 4 - HERO13s, 2 - HERO12s. So I think the issue is only under extern power. Do more of that testing now.

[Zergo333]

I tried QC powerbank device to charge cam & have the same result. Powerbank is connected to simple usb led for avoiding sleep mode after fully charging intermal battery & have the same result. Internal battery is have too small capacity for my task.

[Zergo333]

Here we go again lol
Sadly but no difference internal battery is plugged, or external... here is the new log files all that i have & bak file really don't know what is it.

qrlog.txt
delay.txt

[dnewman-gpsw]

Please don't sending google drive link that require permission. I will just stop look at those. Please try the new builds so I can have consistent debugging messages.

[Zergo333]

Please don't sending google drive link that require permission. I will just stop look at those. Please try the new builds so I can have consistent debugging messages.

Oops sorry for link.

[dnewman-gpsw]

As I doing much of my testing on the next releases, here are some experimental updates and potential improvements added back to the current Labs releases:
HERO13 1.12.71: https://www.dropbox.com/scl/fi/kmy88gxrldtir5yj8gwds/LABS_HERO13_01_12_71.zip?rlkey=7s1r2d2lvjyvemqf2whx7a5e2&dl=1
HERO12 2.20.73: https://www.dropbox.com/scl/fi/a9dojmtj7itmedcq012pl/LABS_HERO12_02_20_73a.zip?rlkey=oa62bqsgcc0elsbfwu3qdkheg&dl=1

[dnewman-gpsw]

There is more I need to learn about your camera. Is it naked? Rehoused? Without the LCD? Third party interval battery? As this is what much of your log says.

This is the log of the last working interval on your camera:

[2024-09-29 23:30:03-delayed ] wake reason:FRW_POWER_BOOT_REASON_RTC_ALARM
[2024-09-29 23:30:04 100% ] Woke with Alarm:[23:30m01]!NQmPN!S!1R
[2024-09-29 23:30:04 --% ] Labs:Display Messages
[2024-09-29 23:30:04 --% ] Labs:Main Start
[2024-09-29 23:30:04 --% ] Labs:H23.01.02.20.73
[2024-09-29 23:30:04 --% ] Labs LCD ID:0 ------ Says there is no LCD
[2024-09-29 23:30:04 --% ] Naked when 0:0 ------ Says it is naked
[2024-09-29 23:30:04 --% ] Labs:Initialize
[2024-09-29 23:30:04 --% ] Bat Temp.:0 ------ Reports the battery is not factory
[2024-09-29 23:30:04 --% ] Woke with Command:[23:30m01]!NQmPN!S!1R
[2024-09-29 23:30:04 --% ] Start Now:Past by 4 seconds
[2024-09-29 23:30:04 --% ] Countdown:complete
[2024-09-29 23:30:04 --% ] Timer wake command:!NQmPN!S!1R
[2024-09-29 23:30:04 --% ] ACTION:!NQmPN!S!1R
[2024-09-29 23:30:05 --% ] token:PN
[2024-09-29 23:30:05 --% ] CAMMODE token:PN
[2024-09-29 23:30:05 --% ] ACTION:!S!1R
[2024-09-29 23:30:05 00% ] STARTCAPTURE:0 ------ 00% - suggests the battery is not factory
[2024-09-29 23:30:06 00% ] ACTION:!1R
[2024-09-29 23:30:09 00% ] ACTION:!47NQmPN!S!1R
[2024-09-29 23:30:13 00% ] Shutdown and Sleep:42 seconds
[2024-09-29 23:30:15 00% ] sleep:41

There is nothing wrong if this is your configuration, but let me know, as I'm not sure it is as on the last run:

[2024-09-29 23:30:58-delayed ] wake reason:FRW_POWER_BOOT_REASON_RTC_ALARM
[2024-09-29 23:30:59 100% ] Woke with Alarm:[23:30m01]!NQmPN!S!1R
[2024-09-29 23:30:59 --% ] Labs:Display Messages
[2024-09-29 23:30:59 --% ] Labs:Main Start
[2024-09-29 23:30:59 --% ] Labs:H23.01.02.20.73
[2024-09-29 23:30:59 --% ] Labs LCD ID:195 ------ Says there is an LCD model 195
[2024-09-29 23:30:59 --% ] Naked when 0:1 ------ Says the camera is not naked
[2024-09-29 23:30:59 --% ] Labs:Initialize
[2024-09-29 23:30:59 --% ] Bat Temp.:0 ------ Reports the battery is not factory
[2024-09-29 23:31:11 00% ] GP2 Temp.:30
[2024-09-29 23:31:31 00% ] GP2 Temp.:31
[2024-09-29 23:31:51 00% ] GP2 Temp.:32
[2024-09-29 23:32:21 00% ] GP2 Temp.:33

This is log form my HERO12. Nice the battery reports temperature and percentage consistently.

[2024-09-30 08:43:32-delayed ] wake reason:FRW_POWER_BOOT_REASON_RTC_ALARM
[2024-09-30 08:43:33 100% ] Woke with Alarm:[08:43:42]!R
[2024-09-30 08:43:34 ->--% ] Labs:Display Messages
[2024-09-30 08:43:38 ->89% ] Labs:Main Start
[2024-09-30 08:43:38 ->89% ] Labs:H23.01.02.20.73
[2024-09-30 08:43:38 ->89% ] Labs LCD ID:193 ------ Reports a different LCD model
[2024-09-30 08:43:38 ->89% ] Naked when 0:1
[2024-09-30 08:43:38 ->89% ] Labs:Initialize
[2024-09-30 08:43:38 ->89% ] Bat Temp.:37 ------ Reports a working battery
[2024-09-30 08:43:38 ->89% ] Woke with Command:[08:43:42]!R
[2024-09-30 08:43:38 ->89% ] Start:4 seconds
[2024-09-30 08:43:43 ->89% ] Countdown:complete
[2024-09-30 08:43:43 ->89% ] Timer wake command:!R
[2024-09-30 08:43:43 ->89% ] ACTION:!R
[2024-09-30 08:43:43 ->89% ] token:P
[2024-09-30 08:43:43 ->89% ] CAMMODE token:P
[2024-09-30 08:43:43 ->89% ] token:0
[2024-09-30 08:43:43 ->89% ] RES token:0
[2024-09-30 08:43:43 ->89% ] ACTION:!N!S!1N!56R
[2024-09-30 08:43:43 ->89% ] ACTION:!S!1N!56R
[2024-09-30 08:43:44 ->89% ] STARTCAPTURE:1
[2024-09-30 08:43:45 ->89% ] ACTION:!1N!56R
[2024-09-30 08:43:47 ->89% ] delay:end
[2024-09-30 08:43:47 ->89% ] ACTION:!56R
[2024-09-30 08:43:51 ->89% ] Shutdown and Sleep:40 seconds
[2024-09-30 08:43:51 ->89% ] sleep:40

[Zergo333]

It's default 12 black, not naked, very strange to see this reports. Yes it's not factory battery just power supply that has only +/- contacts, not smart charging device. Cam display is working well than camera is shooting. The script that I used is from web page of extra long timelapses, I remember what you told about out of date of this code, but tried to use this one.
Upd: now I'm sure about one of my external batteries is not enough for powering camera. Not the previous battery, the second one. Switching it to native power bank with QC module. Testing

[dnewman-gpsw]

This is odd. Differing LCD model is normal, but not detecting is an issue. Add more logging, and I now test the LCD a second time, to confirm its presence.

https://www.dropbox.com/scl/fi/jjarstbuboc32xj0ilys7/LABS_HERO12_02_20_73b.zip?rlkey=frerc1k58cxwp1x3wy6rj95g2&dl=1

[amerikiwi93]

2 x HERO12 and 2 x HERO13, with internal and external power, running flawlessly for two days with a ~60s interval.

What command and camera settings are you using to get 60s intervals for 2 days?

[dnewman-gpsw]

!60NQmP!N!S!1R

[dnewman-gpsw]

I have not seen any failures unrelated to power. There it still something happening random when the external powerbank goes flat, not every time. I had one HERO12 and one 13 stop with internal battery change, but the external was exhausted in each case. This might be hardware issue, of the timing of when power goes out. When changing out a powerbank, I always power the camera on (if it didn't automatically), this will force the capture script to continue.

[dnewman-gpsw]

Please explain: "but the timer is reseting to current time not every time."

[Zergo333]

When the camera is restarted manually, after a failed wake-up, it does not always show the correct time to continue shooting and because of this, shooting does not start. More often, the camera displays the shooting time from the moment the wake-up system failed.
But I think it's normal when battery is flat, but battery is almost fully charged most time it's happened

[Zergo333]

Hello David. Here is a new log. I have manually turned off camera at last events in log file, ignore it please. Everything working fine now. But i keep testing cause the last session is stopped by me because SD card is almost get full

qrlog.txt

[Espusen]

Zergo, are you getting stable running now?

[Zergo333]

Hi! I need a few more days for final tests cause my cam is on rally racing now. I think the info is comes before October 11
What about h13, is it stable? I'm thinking about to buy one more camera for upcoming project.

[Espusen]

Hi David
Testing mPdP>05:00<21:30!S+!1N+!299RQ!3600RQ
Camera will not switch off between shots so remains on. What is wrong with the code please??
This is with the new firmware you gave me.

[dnewman-gpsw]

In standard photo both HERO12 and 13 worked. If you have Superphoto or Raw enabled, the finishing of the !S command can take longer.

Try mPdP>05:00<21:30!S+!2N+!298RQ!3600RQ

It is sort of a bug, but it is also by design. So many of the new scripts benefit from speed, all Labs code runs faster. The !S command used to have a include 2 second sleep, now it is only 1s. So !S!300R will often not shutdown, as the camera can't be put to sleep as it still processing the photo. This is what !1N or !2N, allow up to include the need processing delay. It is also bug, as Labs should be able to detect the camera's processing states, but that never been reliable. You can also do *STDL=3000 for start delay in milliseconds, that way you can skip adding !2N.

[Espusen]

Any clue as to what has gone on here? Camera stays on between shots.
[2024-10-11 17:01:17 !!100%] sleep:3595
[2024-10-11 17:01:23-delayed ] wake reason:FRW_POWER_BOOT_REASON_USB_INSERT_PWROFF_REJECT
[2024-10-11 17:01:25 ->--% ] labs_wake_delay:3575
[2024-10-11 17:01:34 ->--% ] sleep:3556
[2024-10-11 18:00:53-delayed ] wake reason:FRW_POWER_BOOT_REASON_RTC_ALARM

[dnewman-gpsw]

All shots? Or between which times. That all seems to be working.