get_tick_count overflow after 24 days - page 4 - Script Writing - CHDK Forum supplierdeeply

get_tick_count overflow after 24 days

  • 60 Replies
  • 8924 Views
*

Offline Mlapse

  • ****
  • 361
  • S95 S110
Re: get_tick_count overflow after 24 days
« Reply #30 on: 22 / April / 2019, 03:37:57 »
Advertisements
the reason why i have not pursued testing reboot with my m10 is that i lack sufficient size sd cards to let it run for a month or longer in an interval that makes sense to me.

so for me it might be a year or 2 before i am getting really large sd cards that makes the reboot function within reach on my m10.
however, i ordered a card that could test a lengthy run with one of my S95's....does stick under windows make dual boot cards >32GB ?



« Last Edit: 23 / April / 2019, 15:43:04 by Mlapse »
frustration is a key ingredient in progress

Re: get_tick_count overflow after 24 days
« Reply #31 on: 23 / July / 2021, 15:18:08 »
What will CHDK LUA get_tick_count() return after 24+ days?

Negative values ;)

Yes, if you do another one of these it would definitely be good to know what happens.
 

My camera has been running for over 24 days now. The tick counter became negative (line 7174 in the log file). Otherwise, the script continued and took pictures.

@srsa_4c
I notice one problem. Cancel of retract timer does not work anymore. This can be seen in the focal length in the penultimate column which goes from around 50mm to 24mm.

My Canon G1X was now running for 25 days non stop (which can be considered a success) and the camera also had a int overflow in the tick value. It jumped form max int to min int value.
Why did I notice it at all?

The rawopint.lua intervalometer was not working anymore, it shoot about 60 pics/min instead of 4 pics/min :/
I read the hole topic and the best approach would still be to restart the camera?
On my camera there are no photos anyways.

What I will do is code a new scheduled task, that will run every 24 days which runs the chdkptp file:

Code: [Select]
reboot -wait=5000
exec sys.sleep(1000)
rec
exec sys.sleep(5000)
clock -sync
exec sys.sleep(1000)
luar set_zoom(28)
luar set_mf(1) --set focus to manual
luar set_focus(-1) --set focus distance to infinite
luar set_capture_mode(4) --set to AV mode
luar set_user_av96(416) --set AV value
luar set_ev(-128) --set EV value
luar set_lcd_display(0) --switch of display during taking photos
exec sys.sleep(1000)
« Last Edit: 23 / July / 2021, 15:19:48 by dolomiti_timelapse »
If you want to see a sunset or sunrise of Dolomiti Val Gardena shot with CHDK visit
Instagram: dolomiti_timelapse
YouTube: https://www.youtube.com/channel/UCEJHg--ujxLkjMrevJXh-Gw

*

Offline c_joerg

  • *****
  • 1157
Re: get_tick_count overflow after 24 days
« Reply #32 on: 24 / July / 2021, 02:20:46 »
My camera has been running for over 24 days now.

I would be interested in the rawopint log file over this period, especially the temperatures.

I read the hole topic and the best approach would still be to restart the camera?

Maybe two more hints about rebooting:
If there are a lot of pictures on the SD card and you were not in playback mode before, the reboot can take a long time. If the card is empty then that shouldn't be a problem.
The new setting of zoom and focus can lead to the fact that the crop is not always exactly the same. But shouldn't be a problem for 25 days.
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

Re: get_tick_count overflow after 24 days
« Reply #33 on: 24 / July / 2021, 05:57:13 »
My camera has been running for over 24 days now.

I would be interested in the rawopint log file over this period, especially the temperatures.

I read the hole topic and the best approach would still be to restart the camera?

Maybe two more hints about rebooting:
If there are a lot of pictures on the SD card and you were not in playback mode before, the reboot can take a long time. If the card is empty then that shouldn't be a problem.
The new setting of zoom and focus can lead to the fact that the crop is not always exactly the same. But shouldn't be a problem for 25 days.

The camera does run for 24 days non stop but it only shoots the sunset and sunrise, so the log files are limited to the time the camera captures photos...
Still I attached the rawopint logfiles for ~30 consecutive sunset and ~50 consecutive sunrises for you.

Let me know if the temperatures are high!

I have 0 pictures on the SD.

before each sunset and sunrise the the chdkptp executes this code lines anyways...
Code: [Select]
luar set_zoom(28)
luar set_mf(1) --set focus to manual
luar set_focus(-1) --set focus distance to infinite

so I think if they are called every day they should lead to the same result?
« Last Edit: 24 / July / 2021, 06:00:22 by dolomiti_timelapse »
If you want to see a sunset or sunrise of Dolomiti Val Gardena shot with CHDK visit
Instagram: dolomiti_timelapse
YouTube: https://www.youtube.com/channel/UCEJHg--ujxLkjMrevJXh-Gw


*

Offline c_joerg

  • *****
  • 1157
Re: get_tick_count overflow after 24 days
« Reply #34 on: 24 / July / 2021, 06:21:29 »
Let me know if the temperatures are high!

51 degrees sensor temperature is already high but not a problem. I was already at 70 with my G1x.


Code: [Select]
sunrise_lua_log_files_49days

1) 2021_06_06_lua_log_file.csv; 43; 34; 25;
2) 2021_06_07_lua_log_file.csv; 43; 33; 25;
3) 2021_06_08_lua_log_file.csv; 43; 33; 25;
4) 2021_06_09_lua_log_file.csv; 43; 33; 25;
5) 2021_06_10_lua_log_file.csv; 43; 33; 25;
6) 2021_06_11_lua_log_file.csv; 43; 34; 25;
7) 2021_06_12_lua_log_file.csv; 43; 34; 25;
8) 2021_06_13_lua_log_file.csv; 44; 35; 25;
9) 2021_06_14_lua_log_file.csv; 44; 34; 25;
10) 2021_06_15_lua_log_file.csv; 45; 35; 25;
11) 2021_06_16_lua_log_file.csv; 45; 36; 25;
12) 2021_06_17_lua_log_file.csv; 46; 36; 25;
13) 2021_06_18_lua_log_file.csv; 47; 37; 25;
14) 2021_06_19_lua_log_file.csv; 46; 37; 25;
15) 2021_06_20_lua_log_file.csv; 47; 37; 25;
16) 2021_06_21_lua_log_file.csv; 47; 38; 25;
17) 2021_06_22_lua_log_file.csv; 47; 38; 25;
18) 2021_06_23_lua_log_file.csv; 47; 37; 25;
19) 2021_06_24_sunrise_lua_log_file.csv; 46; 37; 25;
20) 2021_06_25_sunrise_lua_log_file.csv; 46; 36; 25;
21) 2021_06_26_sunrise_lua_log_file.csv; 44; 35; 25;
22) 2021_06_27_sunrise_lua_log_file.csv; 45; 35; 25;
23) 2021_06_28_sunrise_lua_log_file.csv; 45; 36; 25;
24) 2021_06_29_sunrise_lua_log_file.csv; 46; 37; 25;
25) 2021_06_30_sunrise_lua_log_file.csv; 46; 36; 25;
26) 2021_07_01_sunrise_lua_log_file.csv; 44; 35; 25;
27) 2021_07_02_sunrise_lua_log_file.csv; 44; 35; 25;
28) 2021_07_03_sunrise_lua_log_file.csv; 44; 35; 25;
29) 2021_07_04_sunrise_lua_log_file.csv; 44; 35; 25;
30) 2021_07_05_sunrise_lua_log_file.csv; 44; 34; 25;
31) 2021_07_06_sunrise_lua_log_file.csv; 44; 35; 25;
32) 2021_07_07_sunrise_lua_log_file.csv; 45; 36; 25;
33) 2021_07_08_sunrise_lua_log_file.csv; 45; 36; 25;
34) 2021_07_09_sunrise_lua_log_file.csv; 44; 35; 25;
35) 2021_07_10_sunrise_lua_log_file.csv; 44; 35; 25;
36) 2021_07_11_sunrise_lua_log_file.csv; 45; 36; 25;
37) 2021_07_12_sunrise_lua_log_file.csv; 44; 35; 25;
38) 2021_07_13_sunrise_lua_log_file.csv; 45; 36; 25;
39) 2021_07_14_sunrise_lua_log_file.csv; 44; 35; 25;
40) 2021_07_15_sunrise_lua_log_file.csv; 43; 34; 25;
41) 2021_07_16_sunrise_lua_log_file.csv; 43; 34; 25;
42) 2021_07_17_sunrise_lua_log_file.csv; 43; 34; 25;
43) 2021_07_18_sunrise_lua_log_file.csv; 43; 35; 25;
44) 2021_07_19_sunrise_lua_log_file.csv; 44; 35; 25;
45) 2021_07_20_sunrise_lua_log_file.csv; 44; 35; 25;
46) 2021_07_21_sunrise_lua_log_file.csv; 45; 36; 25;
47) 2021_07_22_sunrise_lua_log_file.csv; 46; 37; 25;
48) 2021_07_23_sunrise_lua_log_file.csv; 45; 36; 25;
49) 2021_07_24_sunrise_lua_log_file.csv; 46; 37; 25;

max sensor = 47
max opt = 37
max bat = 25


sunset_lua_log_files_30days
   
1) 2021_06_06_lua_log_file.csv; 46; 36; 25;
2) 2021_06_07_lua_log_file.csv; 45; 36; 25;
3) 2021_06_08_lua_log_file.csv; 45; 35; 25;
4) 2021_06_09_lua_log_file.csv; 45; 36; 25;
5) 2021_06_10_lua_log_file.csv; 46; 37; 25;
6) 2021_06_11_lua_log_file.csv; 46; 37; 25;
7) 2021_06_12_lua_log_file.csv; 47; 37; 25;
8) 2021_06_13_lua_log_file.csv; 47; 38; 25;
9) 2021_06_14_lua_log_file.csv; 48; 38; 25;
10) 2021_06_15_lua_log_file.csv; 48; 39; 25;
11) 2021_06_16_lua_log_file.csv; 49; 39; 25;
12) 2021_06_17_lua_log_file.csv; 49; 40; 25;
13) 2021_06_18_lua_log_file.csv; 50; 40; 25;
14) 2021_06_19_lua_log_file.csv; 51; 41; 25;
15) 2021_06_20_lua_log_file.csv; 50; 41; 25;
16) 2021_06_21_lua_log_file.csv; 51; 42; 25;
17) 2021_06_22_lua_log_file.csv; 50; 41; 25;
18) 2021_06_23_lua_log_file.csv; 49; 40; 25;
19) 2021_06_24_sunset_lua_log_file.csv; 48; 38; 25;
20) 2021_06_25_sunset_lua_log_file.csv; 47; 37; 25;
21) 2021_06_26_sunset_lua_log_file.csv; 48; 39; 25;
22) 2021_06_27_sunset_lua_log_file.csv; 48; 39; 25;
23) 2021_06_28_sunset_lua_log_file.csv; 47; 39; 25;
24) 2021_06_29_sunset_lua_log_file.csv; 47; 38; 25;
25) 2021_06_30_sunset_lua_log_file.csv; 47; 38; 25;
26) 2021_07_01_sunset_lua_log_file.csv; 47; 38; 25;
27) 2021_07_02_sunset_lua_log_file.csv; 47; 38; 25;
28) 2021_07_03_sunset_lua_log_file.csv; 47; 38; 25;
29) 2021_07_04_sunset_lua_log_file.csv; 46; 37; 25;
30) 2021_07_05_sunset_lua_log_file.csv; 48; 39; 25;

max sensor = 51
max opt = 41
max bat = 25

Quote from: dolomiti_timelapse link=topic=13714.msg146717#msg146717date=1627120633
so I think if they are called every day they should lead to the same result?

Maybe that's not a problem with infinity. When setting the focus in the close range, there is greater jitter.
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

Re: get_tick_count overflow after 24 days
« Reply #35 on: 24 / July / 2021, 06:39:32 »


51 degrees sensor temperature is already high but not a problem. I was already at 70 with my G1x.


okay at the moment the sun is not shining directly into the camera...

what I find strange is, that the sensor temperature is already high at the start of the timelapse.  ???

What could be reasons for that? Is the senor read from the camera the hole time even though the display is switched off?

I don't think so, as the power consumption is about 1W when the camera is not taking pictures and about 3-4W when the camera is taking a picture?

Is there a command for a "deep sleep" to kind of switch off the sensor, or at least not read it the hole time when the camera is not used? I know I can reboot the camera and also shot it down, but than I can't switch it on from chdkptp anymore?!
If you want to see a sunset or sunrise of Dolomiti Val Gardena shot with CHDK visit
Instagram: dolomiti_timelapse
YouTube: https://www.youtube.com/channel/UCEJHg--ujxLkjMrevJXh-Gw

*

Offline c_joerg

  • *****
  • 1157
Re: get_tick_count overflow after 24 days
« Reply #36 on: 24 / July / 2021, 06:57:43 »
What could be reasons for that? Is the senor read from the camera the hole time even though the display is switched off?
Yes, the sensor is always read out, even if the display is switched off. With rawopint the cam is always half pressed. This leads to the constant reading and the temperature increase.

Is there a command for a "deep sleep" to kind of switch off the sensor, or at least not read it the hole time when the camera is not used? I know I can reboot the camera and also shot it down, but than I can't switch it on from chdkptp anymore?!
I know two solutions:
Between the recordings, you go into the playback mode as with the ultimate intervalometer. But that doesn't work with rawopint.

Unfortunately, my preferred solution only works with EOS M.
https://chdk.setepontos.com/index.php?topic=13956.0

M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

Re: get_tick_count overflow after 24 days
« Reply #37 on: 24 / July / 2021, 08:17:17 »
What could be reasons for that? Is the senor read from the camera the hole time even though the display is switched off?
Yes, the sensor is always read out, even if the display is switched off. With rawopint the cam is always half pressed. This leads to the constant reading and the temperature increase.

I know two solutions:
Between the recordings, you go into the playback mode as with the ultimate intervalometer. But that doesn't work with rawopint.

Unfortunately, my preferred solution only works with EOS M.
https://chdk.setepontos.com/index.php?topic=13956.0

I read your post in the link. Interesting... Thank you!

rawopint is actually not running the hole day, but only during sunset and sunrise. I could set the camera into playback mode after each timelapse.  And before each timelapse change to rec mode again... ;)

Do you know if this is possible without retracting the lens each time? ??? I actually don't know how many lense-retractions this camera can handle (also here a m lens would be better..)
Also I have some kind of dust cover over the lens which I had to take off every time... :(

If you want to see a sunset or sunrise of Dolomiti Val Gardena shot with CHDK visit
Instagram: dolomiti_timelapse
YouTube: https://www.youtube.com/channel/UCEJHg--ujxLkjMrevJXh-Gw


*

Offline c_joerg

  • *****
  • 1157
Re: get_tick_count overflow after 24 days
« Reply #38 on: 24 / July / 2021, 09:06:23 »
Do you know if this is possible without retracting the lens each time? ???
Yes it ist possible
https://chdk.setepontos.com/index.php?topic=13737.0
M100 100a, M3 101a, G9x II (1.00c), 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd

Re: get_tick_count overflow after 24 days
« Reply #39 on: 24 / July / 2021, 09:39:11 »
Yes it ist possible
https://chdk.setepontos.com/index.php?topic=13737.0

Thank you very much!  :D

Okay haha, this seem a little bit to difficult for me to implement it in either rawopint or chdkptp  :-[

As far as I unterstand this feature has still to be included in the next firmware?

Maybe I have to set it only once when the camera reboots in chdkptp with a lua command?

Do you have any code snippets you use on your G1X you can share?

On forum.lrtimelapse.com you wrote "für eine bestimmte Zeit automatisch in den Shutdown schicken kann" do you have any code snippets how to code that? I could set the camera to shutdown for some hours as a quick fix..
« Last Edit: 24 / July / 2021, 10:10:57 by dolomiti_timelapse »
If you want to see a sunset or sunrise of Dolomiti Val Gardena shot with CHDK visit
Instagram: dolomiti_timelapse
YouTube: https://www.youtube.com/channel/UCEJHg--ujxLkjMrevJXh-Gw

 

Related Topics