Re: QR codes and camera disappearing - camera not found

mattfrompoland · ‎01-19-2021

I put up with the lack of wifi, (I used external photoresistor to mesure light from LCD to chcek if gopro is still operating) but my gopro stops after couple of hours and I don't know why?!

qr.bin

mPNeAfWtrcGwNi1S0sLoW1>06:00<21:00!180S~!06:00S!R

grlog.txt

[2021-01-19 12:57:34 100% 27c] Read QR:mPNeAfWtrcGwNi1S0sLoW1>06:00<21:00!180S~!06:00S!R
[2021-01-19 12:57:36 100% 27c] true 12:57 >= 06:00:>06:00<21:00!180S~!06:00S!R
[2021-01-19 12:57:36 100% 27c] resume after > with:<21:00!180S~!06:00S!R
[2021-01-19 12:57:36 100% 27c] true 12:57 < 21:00:<21:00!180S~!06:00S!R
[2021-01-19 12:57:36 100% 27c] resume after < with:!180S~!06:00S!R
[2021-01-19 12:57:40 100% 27c] Shutdown and Sleep:150 seconds
[2021-01-19 13:00:14 100% 28c] QRShouldIWake:01
[2021-01-19 13:00:14 100% 28c] Woke with Alarm:[13:00:36]!S~!06:00S!R
[2021-01-19 13:00:15 100% 28c] Woke with Command:[13:00:36]!S~!06:00S!R
[2021-01-19 13:00:15 100% 28c] Start in:21 seconds
[2021-01-19 13:00:37 100% 28c] Timer wake command:!S~!06:00S!R
[2021-01-19 13:00:43 100% 28c] true 13:00 >= 06:00:>06:00<21:00!180S~!06:00S!R
[2021-01-19 13:00:43 100% 28c] resume after > with:<21:00!180S~!06:00S!R
[2021-01-19 13:00:43 100% 28c] true 13:00 < 21:00:<21:00!180S~!06:00S!R
[2021-01-19 13:00:43 100% 28c] resume after < with:!180S~!06:00S!R
[2021-01-19 13:00:47 100% 28c] Shutdown and Sleep:150 seconds
[2021-01-19 13:03:21 100% 28c] QRShouldIWake:01
...
[2021-01-19 16:10:21 100% 27c] QRShouldIWake:01
[2021-01-19 16:10:21 100% 27c] Woke with Alarm:[16:10:43]!S~!06:00S!R
[2021-01-19 16:10:22 100% 27c] Woke with Command:[16:10:43]!S~!06:00S!R
[2021-01-19 16:10:22 100% 27c] Start in:21 seconds
[2021-01-19 16:10:44 100% 27c] Timer wake command:!S~!06:00S!R
[2021-01-19 16:10:50 100% 27c] true 16:10 >= 06:00:>06:00<21:00!180S~!06:00S!R
[2021-01-19 16:10:50 100% 27c] resume after > with:<21:00!180S~!06:00S!R
[2021-01-19 16:10:50 100% 27c] true 16:10 < 21:00:<21:00!180S~!06:00S!R
[2021-01-19 16:10:50 100% 27c] resume after < with:!180S~!06:00S!R
[2021-01-19 16:10:54 100% 27c] Shutdown and Sleep:150 seconds
[2021-01-19 16:13:29 100% 27c] QRShouldIWake:01
[2021-01-19 16:13:29 100% 27c] Woke with Alarm:[16:13:50]!S~!06:00S!R
[2021-01-19 16:13:30 100% 27c] Woke with Command:[16:13:50]!S~!06:00S!R
[2021-01-19 16:13:30 100% 27c] Start in:20 seconds
[2021-01-19 16:13:51 100% 27c] Timer wake command:!S~!06:00S!R
[2021-01-19 16:13:57 100% 27c] true 16:13 >= 06:00:>06:00<21:00!180S~!06:00S!R
[2021-01-19 16:13:57 100% 27c] resume after > with:<21:00!180S~!06:00S!R
[2021-01-19 16:13:57 100% 27c] true 16:13 < 21:00:<21:00!180S~!06:00S!R
[2021-01-19 16:13:57 100% 27c] resume after < with:!180S~!06:00S!R
[2021-01-19 16:14:01 100% 27c] Shutdown and Sleep:150 seconds
[2021-01-19 16:16:36 100% 27c] QRShouldIWake:01
[2021-01-19 16:16:36 100% 27c] Woke with Alarm:[16:16:57]!S~!06:00S!R
[2021-01-19 16:16:37 100% 27c] Woke with Command:[16:16:57]!S~!06:00S!R
[2021-01-19 16:16:37 100% 27c] Start in:20 seconds
[2021-01-19 16:16:58 100% 27c] Timer wake command:!S~!06:00S!R
[2021-01-19 16:17:04 100% 27c] true 16:17 >= 06:00:>06:00<21:00!180S~!06:00S!R
[2021-01-19 16:17:04 100% 27c] resume after > with:<21:00!180S~!06:00S!R
[2021-01-19 16:17:04 100% 27c] true 16:17 < 21:00:<21:00!180S~!06:00S!R
[2021-01-19 16:17:04 100% 27c] resume after < with:!180S~!06:00S!R
[2021-01-19 16:17:08 100% 27c] Shutdown and Sleep:150 seconds
[2021-01-19 16:29:03 100% 25c] Woke with Command:[16:20:04]!S~!06:00S!R
[2021-01-19 16:29:08 100% 25c] Shutdown and Sleep:24000 seconds

delay.bin

[16:20:04]!S~!06:00S!R

Everything seams to be good and suddenly after 16:17:08 it didn't wake up.

[2021-01-19 16:13:29 100% 27c] QRShouldIWake:01
[2021-01-19 16:13:29 100% 27c] Woke with Alarm:[16:13:50]!S~!06:00S!R
[2021-01-19 16:13:30 100% 27c] Woke with Command:[16:13:50]!S~!06:00S!R
[2021-01-19 16:13:30 100% 27c] Start in:20 seconds
[2021-01-19 16:13:51 100% 27c] Timer wake command:!S~!06:00S!R
[2021-01-19 16:13:57 100% 27c] true 16:13 >= 06:00:>06:00<21:00!180S~!06:00S!R
[2021-01-19 16:13:57 100% 27c] resume after > with:<21:00!180S~!06:00S!R
[2021-01-19 16:13:57 100% 27c] true 16:13 < 21:00:<21:00!180S~!06:00S!R
[2021-01-19 16:13:57 100% 27c] resume after < with:!180S~!06:00S!R
[2021-01-19 16:14:01 100% 27c] Shutdown and Sleep:150 seconds
[2021-01-19 16:16:36 100% 27c] QRShouldIWake:01
[2021-01-19 16:16:36 100% 27c] Woke with Alarm:[16:16:57]!S~!06:00S!R
[2021-01-19 16:16:37 100% 27c] Woke with Command:[16:16:57]!S~!06:00S!R
[2021-01-19 16:16:37 100% 27c] Start in:20 seconds
[2021-01-19 16:16:58 100% 27c] Timer wake command:!S~!06:00S!R
[2021-01-19 16:17:04 100% 27c] true 16:17 >= 06:00:>06:00<21:00!180S~!06:00S!R
[2021-01-19 16:17:04 100% 27c] resume after > with:<21:00!180S~!06:00S!R
[2021-01-19 16:17:04 100% 27c] true 16:17 < 21:00:<21:00!180S~!06:00S!R
[2021-01-19 16:17:04 100% 27c] resume after < with:!180S~!06:00S!R
[2021-01-19 16:17:08 100% 27c] Shutdown and Sleep:150 seconds
[2021-01-19 16:29:03 100% 25c] Woke with Command:[16:20:04]!S~!06:00S!R
[2021-01-19 16:29:08 100% 25c] Shutdown and Sleep:24000 seconds

There was no QRShouldIWake:01 but why?

At 16:29:03 I pressed the power button, and it says wait 23,7h till next shot.

Why something like this happened?

Is there any other option to ex. wake up GoPro using USB-C cable (not the power button) to prevent such behavior and in worse case loose 24h instead of not waking up at all?

It's truly unreliable and worthless. I try the couple of different days and I can stop suddenly at random time

0dan0 · ‎01-19-2021

I have observed this behavior, although more on the H7 than on H8, H9 or MAX. I have no idea why the wake timer isn't 100% reliable on all cameras, although it practically is on many cameras (just not H7.) See video demo: https://www.dropbox.com/s/sgjmcnjhmw08070/RTCWake.mp4?dl=1

That demo was on internal battery and all the H8s lasted until the battery depleated. I've done USB powered tests and not had a failure, but that is not to say it couldn't happen, I've only run those tests for a week or so. Labs can't be fully tested to all its extremes. I've also had a camera running for a year, 3 photos a day. But that is only 3x365 starts (and 6-7 battery changes.) On internal battery the wake timer seems effectively reliable, external power is either making the timer less reliable, or providing enough run time to show the failures.

Several things to try:

1) a different H8 or H9.

2) Why not use a timelapse mode in camera, having that start at 6am and stop 9pm each day automatically. A two minute interval would be very close to your need. Your command could be:

<06:00!06:00R>21:00!06:00R~mTPp.120trwNi1S0sL!S!21:00E!R

Mathematically that will be 300x more reliable.

mattfrompoland · ‎01-19-2021

Hi,

I run this tests for months with very different results.

Internal battery was almost at all conditions reliable but not always.

Internal battery with external USB power (constant) was a nightmare.

Only external power supply was very different. It could last for 2 weeks without a problem and then 3 times in a row it didn't wake up after 3h.

Why not time-lapse mode, because of power consumption, its almost 5x greater on time-lapse than photo mode.

This is my notes:

qr code:

mTNp.120eAfWtwNi1sLg0vq0dTNoV0D4CS1W1!06:00S!21:00E!R

power consumption:

4862mAh for 17:40:26 (one full cycle)
9860mAh for 44:45:02 (second full cycle)

qr code:

!SAVEshoot=mTNp.120eAfWtwNi1sLg0vq0dTNoV0D4CS1W1!06:00S!21:00E!Lwait

!SAVEwait=mPNeAwNi1M1sLoW1!05:59N!Lshoot

!Lshoot

power consumption:

4972 mAh for 30:03:30 (one full cycle)
7909 mAh for 45:47:33 (second full cycle)

qr code:

mPNeAfWtrcGwNi1S0sLoW1>06:00<21:00!180S~!06:00S!R

power consumption:

836mAh for 12:06:08 (half cycle)
1572mAh for 19:45:45 (one full cycle)

0dan0 · ‎01-19-2021

Correct. It is best not to combine internal and external power, that should be noted on all the long timelapse pages.

You would have even better power usage with !180SQ then !180S. Just less time precision (within a couples seconds.)

So: >06:00<21:00!180SQ~!06:00S!R would use less power still.

But the trade off is power usage versus reliability. If a hardware wake timer doesn't wake the camera, not much software can do about it. The power saving are because the camera is completely off, no code is running.

I don't understand the "one full cycle" notation. What is a cycle?

Have you tried on a HERO9? I've haven't personal done long-form TL with power on H9 yet.

mattfrompoland · ‎01-19-2021

Yes, the Q option will save some additional mAh.
What kind of a hardware clock is responsible for waking up the GoPro?
Maybe it's something with low voltage consumption stuff? That's not working well on external power supply like step down DC converters as I'm using right now.
The full cycle is from 06:00 to 21:00 operating. I wasn't always able to start the test before 6, the the working hours are not the same.

0dan0 · ‎01-19-2021

No idea on the hardware details.

I understand the cycle now, what about the 30 vs 45 hours?

mattfrompoland · ‎01-19-2021

It's for how many hours I was reading the consumption but if I start at 10:00 it will be only 11h before deep sleep, and if I start at 23:00 it will count mAh of sleep till 6:00 and then real photo cycle
It's confusing but still for more than 24h I can still estimate the consumption per cycle more or less.

mattfrompoland · ‎01-19-2021

1. It's 1st reading after 30h
2. It's 2nd reading after another 15h so 45h of the same test