It took me over one hour to write this post. Then I wanted to post it. Then I was logged out and the hole message was gone :'( very frustrating!
So this is the second attend and no longer so detailed
It would be helpful to know exactly when this crash happens in the sequence of running scripts, shooting etc. If you can post the full batch file and modified rawopint that might also help, at this point I don't really have a clear idea what your using of all the stuff we've discussed in various threads.
I was able to generate 8 ROMLOGS "ASSERT!! MotionVector.c Line 338" but only form 2 time lapse log files I have accurate information what happend.
1)
The log file says:
display off
taking photos
ERROR: I/O error
ERROR: error on line 38
attempted to close non-present device bus-0:\\.\libusb0-0001--0x04a9-0x3233
The chdkptp code before line 38 is like:
!print'taking photos'
rs "D:/sunset/input/" -script=D:/DolomitiTimelapse/sourcecode/chdk/rawopint_rs_dummy.lua -shots=720 -int=15
<<<--- THIS IS LINE 38exec sys.sleep(1000)
no pictures have been taken that run.
2)
The log file says:
set focus to manual
set focus to infinity
ERROR: I/O error
ERROR: error on line 24
attempted to close non-present device bus-0:\\.\libusb0-0001--0x04a9-0x3233
The (older) chdkptp code around line 24 is like:
!print'set focus to infinity'
luar set_focus(-1) --set focus distance to infinite
luar sleep(1000)
luar set_capture_mode(5) --set to manual mode
luar set_user_av96(416) --set AV value
<<<--- THIS IS LINE 24luar set_tv96_direct(-360) --set TV value to 6.3s
luar set_iso_mode(800) --set ISO 800
luar set_raw_nr(1) --dark frame: 0=Auto 1=OFF, 2=ON
!print'display off'
I added all the fiels to a zip file:
FIRMWARE: g1x-100e-1.6.0-5910-full
downloaded from here:
https://forum.chdk-treff.de/download_dev.phpI use the DE version because this compilation keeps certain settings like "Enable Lua Native Calls" even after a reboot or normal power off and on. So I can create remote ROMLOGs for example.
RAWOPINT.LUA: rawopint-0.25
downloaded
https://chdk.fandom.com/wiki/Lua/Scripts:_Raw_Meter_Intervalometer#LinksThe changes I made are:
411 timeout = 30000 -> timeout = 1000 --display should get darker sooner.
660 'draw_gauge_y_pct', 'smooth'} do -> 'draw_gauge_y_pct', 'smooth', 'filter_intensity'} do --for moving average filter
684 self.meter_y_count = self.meter_height / self.meter_step -> self.meter_y_count = self.meter_height / self.meter_step * 5 / 10 -- crop of final time lapse video
932 -> local last_ev_change_decimal -- added for moving average filter
936 -> last_ev_change_decimal = self.ev_change_decimal -- added for moving average filter
944 -> last_ev_change_decimal = 0 -- added for moving average filter
1120-1141 replaced with ->
log:set{
d_ev_raw = ev_change
}
-- smooth out rapid changes exponential moving average implemented
if self.smooth then
local ev_change_smooth = (last_ev_change * 10 + last_ev_change_decimal) * self.filter_intensity +
(10 - self.filter_intensity) * ev_change * 10
ev_change = ev_change_smooth / 100
last_ev_change_decimal = (ev_change_smooth % 100) / 10 -- not sure if modulo works this way in lua
end
self.ev_change = ev_change
self.ev_change_decimal = last_ev_change_decimal
1697 'over_frac', 'over_weight', 'under_frac', 'under_weight', 'bv_ev_shift', 'd_ev', 'desc'}, -> 'over_frac', 'over_weight', 'under_frac', 'under_weight', 'bv_ev_shift', 'd_ev', 'd_ev_raw', 'desc'}, --log purpose
1809 -> filter_intensity = ui_filter_intensity, --changing filter intensity over powershell script
2003 -> -- in cont release shoot full as soon as the final shot starts
-- to avoid extra shots and delays
if cont and i == ui_shots then
release('shoot_full')
end
2066 ->
--create dummyfile for avoiding freezing when changing form play to rec after long time
rlib_shoot_filedummy()
I used
https://www.textcompare.org/ I think that is the better way than the list I provided above to see the differences.
RAWOPINT_RS_DUMMY.lua: see the custom setting in the file
CHDKPTP: in the zip file I added the sunset configuration
As you may notice I use the button commands to navigate through the menu to delete the dummy files, because "imrm -quiet" seems not to do the job.
Powershell: calling chdkptp via
chdkptp -c -e"source path/to/sunset_chkd_dummy.chdkptp"Did it say "CONNECTION ERROR" alone? Or did it actually mention "network"? Edit: Or "COMMUNICATION ERROR", which is the message I was thinking of.
"CONNECTION COMMUNICATION ERROR" is documented in the Canon manuals as a USB related error that happens when the camera thinks it has lots of images on the card. The manual typically says this happens when there are 1000 or more, but in my experience it usually a lot more (I just downloaded 2233 images from my elph130 without getting that error.)
If the camera crashed and the dummy files are still present, the camera might think there are enough files to trigger it though.
Have the full sequence of what your script does would help here too.
Yes you are 100% right. It was COMMUNICATION ERROR. Your explanation seems to describe exactly the situation that night, where I first had to delete alle dummy files on camera before being able to connect the camera to the PC via USB.
