I got two log files and both show "ASSERT!! MotionVector.c Line 133" a search indicates that MotionVector is from the original firmware
In case of a crash, the camera tries to record debugging information (function of the original firmware). When you request a romlog, you always get the information about the latest recorded crash event (watch the timestamp to see whether a new crash has happened).
In some cases the camera's operating system fails to catch the event and the crash doesn't leave a trace.
and the times stamps don't match the times when the camera actually stopped.
Are you sure? Your current log shows a fresh timestamp with about 78 minutes uptime (the 8 digit numbers in the second half of the log show the elapsed milliseconds).
If your camera crashes again, try to get another romlog.
I had another couple crashes.
To recap - I am taking a picture every 15 min during daylight times.
The camera just stops working randomly, sometimes after 2 hours sometimes after as much as 3 days.
RomLog4
- worked correctly for 1 hour 15 min, or 6 pictures.
- Last picture taken was 07:00
- Occured Time 2012:04:04 06:00:38
RomLog5
- worked correctly for almost two days.
- Last picture taken was 10:30
- Occured Time 2012:04:07 09:30:40
I have a third log that is also off by one hour. If the time stamp is off by an hour the crashes are happening right after taking a picture.
I will update to beta 3 and continue my time-lapse.
If these logs do not help narrow down the problem is there something in particular I should be looking for or missing in the log file that will help narrow down the problem?
Jim
