Thank you for this information. A very detailed description of the error. Quote from: dolomiti_timelapse on 03 / October / 2021, 07:28:38I would be very happy if someone of you can read the ROMLOGs and find a cause Unfortunately, that is beyond my capabilities ... Quote from: dolomiti_timelapse on 03 / October / 2021, 07:28:38Do 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.
I would be very happy if someone of you can read the ROMLOGs and find a cause
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.
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.
As c_joerg said, rawopint records this in rawopint.csv. The columns are vbatt, tsensor, topt and tbatt
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.
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.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.
In the camera log for these, I see a lot of lines with "SS:SetFace".
Strange, the AF was and is set to FlexiZone. Normally the camera is set to AF-mode after a restart. Sometimes if I remember I do change the AF to MF in the Canon UI manually which I think is better.
Maybe the question is then: Why does it take so long to delete the evident non existing files during executing photo erase in the canon menu? If I do it a second time it is actually very fast. But in the first run it seems to delete a ton of pictures.
Hmm.. in summary, the ROMLOGs unfortunately did not bring to light the cause of the error I was looking for.
#1, #5 and #6 are allCode: [Select]ASSERT!! MotionVector.c Line 338I 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.#4Code: [Select]ASSERT!! LiveImageTask.c Line 523Occured Time 2021:08:24 05:10:19ISR : vector=10Which 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".
ASSERT!! MotionVector.c Line 338
ASSERT!! LiveImageTask.c Line 523Occured Time 2021:08:24 05:10:19ISR : vector=10
ASSERT!! LiveImageTask.c Line 523
has not occurred anymore after sending click"shoot_half". This may have solved the problem.
Code: [Select]ASSERT!! MotionVector.c Line 338on the other hand keeps crashing the G1X. My workaround for now is to test if the camera is connected and if not switch the camera on with the servo-arduino "package".
Yesterday I had a new issue: only after I manually delete alle dummy files on the camera, the camera after a restart connected again to the PC, only a restart was not enough. Before deleting manually the photos the camera printed a network connection error on display when powering on.
I found this https://chdk.setepontos.com/index.php?topic=12523.22 and it seems to be the same issue regarding MotionVector.c. @srsa_4c suggests: "Moving the hooks around seems to have been enough."What does he mean with moving the hooks around? what are hooks and how do I move them around?
Since the error does not happen during rawopint (I assume that rawopint was programmed correctly in this respect),
is there a way to send the camera in sleep mode for some hours and to terminate the ptp connection shortly after the sleep command for continuing the photos conversion on the pc in the mean time?
Started by RaduP
Started by LukeSkaff
General Help and Assistance on using CHDK stable releases
Started by 7dforlife
Creative Uses of CHDK
Started by nahuel_89p
Completed and Working Scripts
Started by artfolio
Creative Uses of CHDK