CHDK for longtime timelapse - page 7 - General Help and Assistance on using CHDK stable releases - CHDK Forum

CHDK for longtime timelapse

  • 98 Replies
  • 6168 Views
Re: CHDK for longtime timelapse
« Reply #60 on: 30 / September / 2021, 09:52:08 »
Advertisements

Unfortunately the G1x has only 28 mm :(

mea culpa!!

Quote
Could you post a picture? I am very interested in that…

I am no longer on site. But I can show a picture of the webcam monitoring the camera.
I just positioned an old weak servo that was lying around with a small servo arm on the camera so that it pushes the on-off button. The servo is connected to an Arduino Nano that was also lying around, and this is connected to the time-lapse laptop.
The Arduino listens to the serial port and a power shell script writes to the same port. That's it.
If you want, I can share the few lines of code.

Quote

In direct sun I would always turn on the built-in ND filter.

Thanks!, the ND filter is always on If the exposure is shorter than 1/10sec
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

Re: CHDK for longtime timelapse
« Reply #61 on: 30 / September / 2021, 10:40:01 »

I have good results with just a cardboard box taped to the inside of a double glazed window.
it isn't even black and still, when it is folded closed it prevents light reflection from inside (my biggest problem) and blocks most sunlight that would hit the cam.
the reason I cut a lot of the box away is to give me easy access to the buttons of the cam,
but if you are doing everything via a computer you might not need to remove this much material.

Thanks! I will definitely try this next time out.
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 Caefix

  • *****
  • 638
  • Sorry, busy deleting test shots...
Re: CHDK for longtime timelapse
« Reply #62 on: 30 / September / 2021, 12:22:05 »
the webcam monitoring the camera.
... could have a click_on manual telelens.   8)
All lifetime is a loan from eternity.

*

Offline c_joerg

  • *****
  • 1157
Re: CHDK for longtime timelapse
« Reply #63 on: 30 / September / 2021, 12:32:21 »
And every 3 to 5 days the camera crashes...
Do you know when the camera crashes?
During the time you do time lapse or in between?

I would run a script when the camera is not recording, which writes the temperature, supply voltage and time to a file.

You could also do a reboot after every time lapse ...
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


*

Offline Caefix

  • *****
  • 638
  • Sorry, busy deleting test shots...
Re: CHDK for longtime timelapse
« Reply #64 on: 30 / September / 2021, 13:16:41 »
Don´t be too shy to ask the sky whether the clouds are dry...  :-*
Code: [Select]
--[[--
@title cafu_test
V0.4.1
--]]--

print("get_focus()",get_focus())
print("get_focus_mode()",get_focus_mode())
print("get_focus_ok()",get_focus_ok())
print("get_focus_state()",get_focus_state())
print("get_IS_mode()",get_IS_mode())
print("get_shooting()",get_shooting())
print("get_zoom()",get_zoom())
print("get_zoom_steps()",get_zoom_steps())
print("get_sd_over_modes()",get_sd_over_modes())
print("get_mode()",get_mode())
print("get_av96()",get_av96())
print("get_bv96()",get_bv96())
print("get_ev()",get_ev())
print("get_iso_market()",get_iso_market())
print("get_iso_mode()",get_iso_mode())
print("get_iso_real()",get_iso_real())
print("get_nd_present()",get_nd_present())
print("get_nd_current_ev96()",get_nd_current_ev96())
print("get_nd_value_ev96()",get_nd_value_ev96())
print("get_user_av_id()",get_user_av_id())
print("get_min_av96()",get_min_av96())
print("get_max_av96()",get_max_av96())
print("get_user_av96()",get_user_av96())
print("get_current_av96()",get_current_av96())
print("get_sv96()",get_sv96())
print("get_tv96()",get_tv96())
print("get_user_tv_id()",get_user_tv_id())
print("get_user_tv96()",get_user_tv96())
print("get_current_tv96()",get_current_tv96())
print("get_current_delta_sv96()",get_current_delta_sv96())
print("get_current_base_sv96()",get_current_base_sv96())
print("get_live_histo()",get_live_histo())
print("get_flash_mode()",get_flash_mode())
print("get_flash_params_count()",get_flash_params_count())
print("get_flash_ready()",get_flash_ready())
print("get_movie_status()",get_movie_status())
print("get_prop(prop)",get_prop(prop))
print("get_propset()",get_propset())
print("get_vbatt()",get_vbatt())
print("get_video_button()",get_video_button())
print("get_disk_size()",get_disk_size())
print("get_exp_count()",get_exp_count())
print("get_jpg_count()",get_jpg_count())
print("get_image_dir()",get_image_dir())
print("get_free_disk_space(n)",get_free_disk_space(n))
print("get_partitionInfo()",get_partitionInfo())
print("autostarted()",autostarted())
print("get_autostart()",get_autostart())
print("get_day_seconds()",get_day_seconds())
print("get_tick_count()",get_tick_count())
local c="D"; print("get_time(c)",get_time(c))
print("get_draw_title_line()",get_draw_title_line())
print("get_gui_screen_width()",get_gui_screen_width())
print("get_gui_screen_height()",get_gui_screen_height())
print("get_raw()",get_raw())
print("get_raw_count()",get_raw_count())
print("get_raw_nr()",get_raw_nr())
print("get_raw_support()",get_raw_support())
print("get_canon_raw_support()",get_canon_raw_support())
print("get_canon_image_format()",get_canon_image_format())
print("get_alt_mode()",get_alt_mode())
print("get_buildinfo()",get_buildinfo())
local id=8; print("get_config_value(id)",get_config_value(id))
print("get_histo_range(n1,n2)",get_histo_range(n1,n2))
print("get_usb_power()",get_usb_power())
--[[--
print("",)
print("",)
print("",)
print("",)
--]]--
All lifetime is a loan from eternity.

*

Offline reyalp

  • ******
  • 13435
Re: CHDK for longtime timelapse
« Reply #65 on: 30 / September / 2021, 15:24:31 »
Don´t be too shy to ask the sky whether the clouds are dry...  :-*
What is the point of this? How is it relevant to dolomiti_timelapse's project? If it doesn't address some specific issue raised in the thread, why are you posting it here? Random snippets of untested code without explanation are not helpful.

I can tell it's untested (or not well tested), because several of those calls won't work or do anything useful. Others less familiar with CHDK might not know that, and waste a bunch of time thinking they are doing something wrong.

Please, if you are going to post, use simple sentences to explain specifically whatever it is you want to communicate. If it's code, explain what it does, and whether you've tested it. A little humor is fine, but it's not a substitute for clear communication.
Don't forget what the H stands for.

Re: CHDK for longtime timelapse
« Reply #66 on: 03 / October / 2021, 07:28:38 »
Do you know when the camera crashes?
During the time you do time lapse or in between?

I would run a script when the camera is not recording, which writes the temperature, supply voltage and time to a file.

You could also do a reboot after every time lapse ...

I have attached 6 ROMLOGs of some of the camera crashes. As I said, they occur every 3-5 days.
The camera never crashed during the rawopint script. The camera never crashed during the waiting time between the time lapses, but always when the camera executes those commands, which are executed before or after the Rawopint script. E.g.: delete the dummy files.

ROMLOG1: no specific information here
ROMLOG2: camera crashed after or during imrm -quiet.
ROMLOG3: same as ROMLOG2
ROMLOG4: camera crashed while running rs "D:/sunrise/input/" -script=D:/DolomitiTimelapse/sourcecode/chdk/rawopint_rs_dummy.lua -shots=720 -int=15, but rawopint script was not started yet.
ROMLOG5: camera crashes when running luar set_focus(-1).
ROMLOG6: same as ROMLOG4

I like the functionality that with exec con:call_function(0xff099f1c) the lens closes the "shutter" and saves power by switching off the sensor but does not retract itself. The disadvantage is stability. If I would just turn off the camera after the time lapse, I would need a servo that works reliably, and the time lapse would not overlap 100% every time with the lens retracting. Or as reyalp wrote, cut the power supply wiht power button pressed....

My observations are: the power supply is extremely robust and reliable (because of the large energy buffer).
The dummy photos are not deleted with imrm -quiet, but only when i delete them manually in the canon menu. so imrm -quiet must be different than the canon menu command. maybe i need to take a longer break after executing imrm -quiet and before turning off the display, because deleting the dummy files in the canon menu does take a relatively long time (up to a minute)
Since the camera lasts some time without hanging up, maybe some timer or buffer got full? For example that the old dummyfiles are not deleted correctly or so?

I would be very happy if someone of you can read the ROMLOGs and find a cause :)

Also, the green light of the camera flashes when the camera is in "standby", which might be caused by exec con:call_function(0xff099f1c) .
In general, what does the flashing of the green light mean that a script is running?

Do you have a script for recording temperatures and voltage during timelapse? I have not searched for such a script up to know to be honest.  :-[
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: CHDK for longtime timelapse
« Reply #67 on: 03 / October / 2021, 08:41:22 »
Thank you for this information. A very detailed description of the error.

I would be very happy if someone of you can read the ROMLOGs and find a cause :)

Unfortunately, that is beyond my capabilities ... ;)

Do you have a script for recording temperatures and voltage during timelapse? I have not searched for such a script up to know to be honest.  :-[
During the time lapse, rawopint records everything. I once attached a script that records the values without shooting.
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


*

Offline reyalp

  • ******
  • 13435
Re: CHDK for longtime timelapse
« Reply #68 on: 03 / October / 2021, 17:19:44 »
The dummy photos are not deleted with imrm -quiet, but only when i delete them manually in the canon menu.
Do you mean the files themselves are not removed (still visible with the chdkptp ls command, for example) or that they continue to appear in the Canon UI as "unknown file" or whatever? The latter is normal, CHDK only removes them from the file system. If the files still appear in ls, something is broken.

Quote
so imrm -quiet must be different than the canon menu command.
Yes, as above, imrm only deletes the files. They will generally continue to appear in the Canon UI, until a reboot or perhaps a rec/play transition.

Quote
maybe i need to take a longer break after executing imrm -quiet and before turning off the display, because deleting the dummy files in the canon menu does take a relatively long time (up to a minute)
Wouldn't hurt to try.

Quote
Also, the green light of the camera flashes when the camera is in "standby", which might be caused by exec con:call_function(0xff099f1c) .
In general, what does the flashing of the green light mean that a script is running?
This sounds like Canon firmware behavior, unrelated to CHDK script running. CHDK might blink the led once during certain operations (like saving raw) but it does not set it to continuously blink.

Quote
Do you have a script for recording temperatures and voltage during timelapse? I have not searched for such a script up to know to be honest.  :-[
As c_joerg said, rawopint records this in rawopint.csv. The columns are vbatt, tsensor, topt and tbatt

Quote
I would be very happy if someone of you can read the ROMLOGs and find a cause
From an initial look, there seems to be several quite different things:

#1, #5 and #6 are all
Code: [Select]
ASSERT!! MotionVector.c Line 338
I think we've seen this one before, but search didn't turn much immediately useful. It is likely something sensor / live view related. I have a romlog from c_joerg with this one on g1x too, but I don't remember the circumstances.
It was previous seen in https://chdk.setepontos.com/index.php?topic=11078.msg108983#msg108983 related to focus override.

In the camera log for these, I see a lot of lines with "SS:SetFace". If the Canon menu AF setting is set to something Face, AiAF, or Tracking, I'd suggest trying setting it to Center instead.


#2 and #3 are
Code: [Select]
ASSERT!! CobjSearch.c Line 1485
This is related to files somehow.  Seems familiar, but again no obvious results.

#4
Code: [Select]
ASSERT!! LiveImageTask.c Line 523
Occured Time  2021:08:24 05:10:19
ISR : vector=10
Which I don't recall seeing before, but again seems sensor / live view related.

On thing that can cause sensor related crashes is if the sensor is turned off when CHDK calls functions that expect it to be on. This could be an issue if you have the screen off setting enabled in the canon firmware. To make sure the cameras is "woken up" before setting focus or running rawopint, you could send a =click"shoot_half".

I'll look a bit more later into where in the firmware the crashes actually happen to see if that provides any clues.

edit:
Nothing really jumps out looking at the firmware. The MotionVector.c assert is based on the result of TryReceiveMessageQueue at ff169f7c

The LiveImage.c assert is from TryPostMessageQueue result at ff134e68. Doesn't appear to be the same message queue as the previous one, but nearby in memory, so likely related code.

The CobjSearch.c assert is from result of function ff199538 called at ff336288.

None of these appear to be a result of code *directly* called by CHDK, they all come from tasks the CHDK doesn't touch. This doesn't mean CHDK isn't the cause (it almost certainly is) but it's not a simple matter of us calling a function with the wrong parameters or something like that.
« Last Edit: 03 / October / 2021, 18:49:57 by reyalp »
Don't forget what the H stands for.

*

Offline Caefix

  • *****
  • 638
  • Sorry, busy deleting test shots...
Re: CHDK for longtime timelapse
« Reply #69 on: 04 / October / 2021, 13:49:30 »
My latest MotionVector Romlog was...  :haha
https://chdk.setepontos.com/index.php?topic=14294.msg145635#msg145635

An Update of lib.c
Code: [Select]
// camera appears to use 240 when Fisheye mode, 480 otherwise
int vid_get_viewport_yscale() {
    if (camera_info.state.mode_play) { return 2; }
    if (is_video_recording()) { return 2; }
    if (camera_info.state.mode_shooting == MODE_FISHEYE) { return 1; }
    return 2;
}
related functions at least beautified it, as on some other cams...
https://chdk.setepontos.com/index.php?topic=14302.msg147100#msg147100  :-* was my checklist while working on https://forum.chdk-treff.de/viewtopic.php?f=7&t=3540&start=30#p31956
Now it´s good for c&p what´s good for script or Forum research...
(That´s the loupe symbol in the headline.)

Similar c&p from Ix265´s lib.c approach, could hopefully verify it tomorrow...
(maybe continued at ...)

Very new Romlog:
Code: [Select]
ASSERT!! ../RecLFunc/RecLFunc.c Line 2095appears when pressing <Set> in fisheye.
my_lib.c crashes a step later :( without Romlog...
« Last Edit: 05 / October / 2021, 15:16:22 by Caefix »
All lifetime is a loan from eternity.

 

Related Topics