Crash motionvector with long running script (split from A3300 porting)

  • 20 Replies
  • 3367 Views
Advertisements
Just a note to document that my A3300IS stops at random intervals (2hrs to 2 days) while running the selective interval script.  Multiple power supply options have been tried.  I have 4 other cameras running with no issues to document a construction project at my home.  The camera simply shuts down without retracting the lens.  Power draw goes to zero.  No permanent damage to the camera occurs.

I'm running a3300-100d-1.3.0-4169.  CHDK is started using the firmware update method.

Sadly, this is the best of my cheap craigslist cameras, but this issue renders it useless for the project.

This note is here in case someone else can confirm this as a bug and not a single camera issue.  Unfortunately, it'll be a tough one to find if it is.
« Last Edit: 25 / August / 2015, 16:11:34 by reyalp »

*

Offline reyalp

  • ******
  • 11583
Re: Re: port for A3300IS / what reference port to use?
« Reply #1 on: 20 / August / 2015, 23:49:11 »
Just a note to document that my A3300IS stops at random intervals (2hrs to 2 days) while running the selective interval script.  Multiple power supply options have been tried.  I have 4 other cameras running with no issues to document a construction project at my home.  The camera simply shuts down without retracting the lens.  Power draw goes to zero.  No permanent damage to the camera occurs.

I'm running a3300-100d-1.3.0-4169.  CHDK is started using the firmware update method.
Check if the camera generates a crash log: http://chdk.wikia.com/wiki/Debugging#Camera_crash_logs_.28romlog.29 and post here if it does.
Don't forget what the H stands for.

Re: Re: port for A3300IS / what reference port to use?
« Reply #2 on: 20 / August / 2015, 23:50:50 »
Did you try dumping a ROMLOG using the CHDK debug menu and looking to see if the date / time in the log matched the time the camera stopped?.  If so, can you attach the ROMLOG to a post here?
Ported :   A1200    SD940   G10    Powershot N    G16

Re: Re: port for A3300IS / what reference port to use?
« Reply #3 on: 21 / August / 2015, 18:00:39 »
romlog dump: 

ASSERT!! MotionVector.c Line 339
Occured Time  2015:08:20 13:15:10
Task ID: 23330866
Task name: LiveImageTas0
SP: 0x0031B1D0
StackDump:
0x00000000
0xFF91AE98
0x00000153
0x000A10B4
0x000020D0
0x00005854
0x00002710
0x00000000
0x00000004
0x40546B80
0x19980218
0xFF91B118
0x00000000
0x0031B268
0x000020D0
0x00000000
0x0000229C
0x00000000
0x00000004
0xFF8526DC
0x0000083B
0x0009EB60
0x00004FC4
0x00105003
0x19980218
0x19980218
0x19980218
0x19980218
0x19980218
0xFF8FA4C8
0x00000004
0x00000001
0x02000000
0x00000009
0x19980218
0xFFB7A474
0x00000168
0x000000F0
0x000002D0
0x000000F0
0x0009EB60
0x00000000
0x00005068
0xFF8FDA14
0x00000004
0x00005068
0x00000000
0x19980218
0x19980218
0xFF8FDB7C
0x0009EB10
0x002F30A4
0x19980218
0xFF816B78
0x19980218
0x19980218
0x00001008
ShootConDump:
00 00 0f 00 0f 20 00 0f 00 0f 60 00 0f 00 0f 70
00 0f 00 0f 80 00 0f 00 0f 80 00 0f 00 1f 80
CameraConDump:
07 0a 02 0d 09 01 0f 0f 0f 0f
70445940: UI:ShootSeqToUI:0x2001:adr:0,Para:0
70445940: UI:DSIC:46,0
70445950: UI:ShootSeqToUI:0x201e:adr:0x101e,Para:4126
70445950: UI:ShootSeqToUI:0x2029:adr:0x101e,Para:4126
70445950: UI:ShtCon_EnableReviewHold:IsPressSwTwo:0
70445950: UI:ShtCon_EnableReviewHold:IsAvailableShots:1
70445950: UI:DSIC:4c,0
70445950: SS:StopRev
70445950: UI:ScreenLock
70445980: UI:PB.RefPB
70445990: UI:PB.DrawI
70446000: UI:ShtCon_EnableReviewHold:IsPressSwTwo:0
70446000: UI:ShtCon_EnableReviewHold:IsAvailableShots:1
70446000: SS:NextAvail(7),ReviewAvail(5)
70446200: UI:DSIC:48,0
70446340: UI:LogicalEvent:0x3204:adr:0,Para:0
70446340: UI:PB.DcdCBR
70446340: UI:PB.RfrsI
70446360: UI:DispSwCon_MuteOffPhysicalScreen
70446360: UI:Window Reduce MuteOff
70446360: UI:ScreenUnLock
70446370: UI:Window Re MuteOff
70446370: UI:MuteOffPhysicalScreen
70446380: UI:DisplayPhysicalScreenCBR
70448010: UI:LogicalEvent:0x311e:adr:0,Para:0
70448010: UI:ShtCon_StopReview
70448010: UI:StopRecReviewController
70448010: UI:PB.StopR
70448010: UI:ScreenLock
70448020: UI:ScreenUnLock
70448020: UI:LogicalEvent:0x3120:adr:0,Para:0
70448020: UI:ShootState:0x83
70448020: UI:ShootState:0x74
70448030: UI:ShtAutoShutterLib_IsActivateSmileShutter:0
70448030: UI:ShootState:0x80
70448030: UI:ShootState:0x70
70448030: UI:ShtCon_ExitSequenceState
70448030: UI:_ExitSequenceWithoutSw1Check
70448030: UI:_ExitActionReview
70448030: SS:CancelPre
70448690: SS:ChargeComplete
70448690: UI:DispSwCon_MuteOffPhysicalScreen
70448690: UI:Window MuteOff
70448690: UI:MuteOffPhysicalScreen
70448690: UI:ShtCon_Deactivate
70448690: UI:DSIC:14,0
70448690: UI:DSIC:60,0
70448690: UI:DispSwCon_TurnOnDisplayDevice
70448690: UI:ScreenLock
70448770: UI:ScreenUnLock
70448770: UI:DispSw: Unlock
70448770: UI:DispSwCon:Unlock
70448770: SS:IsQ=1
70448770: UI:TerminateDeliverToZoomController
70448790: UI:ScreenLock
70448790: UI:ScreenUnLock
70448800: UI:OPTICAL_ZOOM_POS
70448800: UI:UnpressZoomLever
70448800: SS:IsQ=1
70448800: UI:ScreenLock
70448800: UI:Reduce ScreenUnLock
70448800: UI:ScreenLock
70448800: UI:Reduce ScreenUnLock
70448800: UI:ShtCon_EntryIdleShoot
70448810: UI:ShootState:0x0
70448810: UI:DisplayPhysicalScreenCBR
70448810: UI:Re ScreenUnLock
70448810: UI:Reduce ScreenUnLock
70448810: UI:DisplayPhysicalScreenCBR
70448810: UI:Re ScreenUnLock
70448810: UI:Reduce ScreenUnLock
70448810: UI:DisplayPhysicalScreenCBR
70448810: UI:Re ScreenUnLock
70448810: UI:ScreenUnLock
70448830: UI:DisplayPhysicalScreenCBR
70449150: UI:ScreenLock
70449150: UI:ScreenUnLock
70449160: UI:DisplayPhysicalScreenCBR
70452850: UI:ScreenLock
70452860: UI:ScreenUnLock



*

Offline reyalp

  • ******
  • 11583
Re: Re: port for A3300IS / what reference port to use?
« Reply #4 on: 21 / August / 2015, 21:28:01 »
romlog dump: 

ASSERT!! MotionVector.c Line 339
Occured Time  2015:08:20 13:15:10
Task ID: 23330866
Task name: LiveImageTas0
Thanks. CHDK doesn't intentionally do anything with this task, so it doesn't provide much information. That doesn't mean CHDK isn't ultimately to blame, it just doesn't give us much to go on.

Are you using the script from http://chdk.wikia.com/wiki/Selective_Intervalometer ? If your are using another variant, please give a link to the specific script.

If you can find any pattern to what the camera is doing when the crash happens (does it happen right when it tries to shoot, or in between shots, or randomly) that might provide some clue.


edit:
It would also be useful to know if you get the same romlog every time it crashes. You can just look for the
Quote
ASSERT!! MotionVector.c Line 339
If you see something different, post it.
« Last Edit: 21 / August / 2015, 21:57:11 by reyalp »
Don't forget what the H stands for.

Re: Re: port for A3300IS / what reference port to use?
« Reply #5 on: 22 / August / 2015, 05:56:32 »


Are you using the script from http://chdk.wikia.com/wiki/Selective_Intervalometer ?


It hangs using that script.  The romlog I posted was using a slight modification to that script (it shuts the display off immediately after each shot.)  I'll switch back to the one above for future debugging.

The crash appears random and not associated with actual shooting, as far as I can tell.  I recall (perhaps incorrectly) it dying in in the night while not taking pictures.  I was focused on possible power supply issues and not on CHDK or script execution at the time.  I'm traveling for the next few days so updates may be delayed.

Re: Re: port for A3300IS / what reference port to use?
« Reply #6 on: 22 / August / 2015, 11:11:58 »
I had one more thought, I checked the timestamp on the pictures taken before the crash associated with the previously listed romlog.  The camera was taking pictures once a minute, and the timestamps were occurring at the change of minute (windows properties of modified at :00 and created at :01.)  The last created at 13:15:01, which is 9 seconds before the romlog listed crash time of 13:15:10.  It would appear this is not related to shutter activation.

*

Offline srsa_4c

  • ******
  • 3725
Re: Re: port for A3300IS / what reference port to use?
« Reply #7 on: 22 / August / 2015, 13:46:00 »
@davedude

Try deactivating anything that is related to face detection or tracking:
- blink detection
- servo AF
Set AF frame to center and use P mode.

Despite all this, the issue will probably persist - the cause is unknown and I'm not aware of a solution.


Re: Re: port for A3300IS / what reference port to use?
« Reply #8 on: 22 / August / 2015, 20:13:59 »
@davedude

Try deactivating anything that is related to face detection or tracking:
- blink detection
- servo AF
Set AF frame to center and use P mode.

blink detection is off
servo - unknown, no longer at camera location
AF frame is center
mode is P

I've left the camera running  for the next few days in alt mode with the script _not_ running to see if it related to script execution or not.

Re: Re: port for A3300IS / what reference port to use?
« Reply #9 on: 24 / August / 2015, 21:55:15 »
Updating..  Servo is off.

The camera ran 2+ days without crashing in alt mode without a script running.  Not definitive, but perhaps indicative.

However, another one of my cameras which was running over the weekend crashed in a similar manner.   This looks like it is not a specific port issue.

This camera is running ixus115_elph100hs-100c-1.3.0-4169

Same settings (no servo, no blink, AF frame center...)

Last photo taken: 2015:08:23 06:22:04

Romlog:

ASSERT!! MotionVector.c Line 339
Occured Time  2015:08:23 06:22:12
Task ID: 24379444
Task name: LiveImageTas0
SP: 0x0039A7D0
StackDump:
0x00000000
0xFF930778
0x00000153
0x000A7120
0x0000216C
0x00005CBC
0x00002710
0x00000000
0x00000004
0x40684900
0x19980218
0xFF9309F8
0x00000007
0x0039A868
0x0000216C
0x00000000
0x0000233C
0x00000007
0x00000004
0xFF8544E0
0x0000083B
0x000A44A0
0x00005370
0x00105003
0x19980218
0x19980218
0x19980218
0x19980218
0x19980218
0xFF909DF4
0x00000004
0x00000000
0x02000000
0x00000001
0x19980218
0xFFBB933C
0x00000168
0x000000F0
0x000002D0
0x000000F0
0x000A44A0
0x00000000
0x0000542C
0xFF90D824
0x00000004
0x0000542C
0x00000000
0x19980218
0x19980218
0xFF90D9AC
0x000A4450
0x0037314C
0x19980218
0x19980218
0x19980218
0xFF816B78
0x19980218
0x19980218
0x00001408
ShootConDump:
01 02 07 08 09 0a 0c 0b 00 00
CameraConDump:
07 0a 02 0d 09 01 0f 0f 0f 0f
120759190: UI:Reduce ScreenUnLock
120759200: UI:LogicalEvent:0x311f:adr:0,Para:0
120759200: UI:ShootState:0xC
120759200: SS:ExitShoot
120759200: UI:DisplayPhysicalScreenCBR
120759200: UI:Re ScreenUnLock
120759200: UI:ScreenUnLock
120759220: UI:DisplayPhysicalScreenCBR
120759300: UI:DSIC:47,0
120759300: UI:DSIC:46,0
120759310: UI:ShootSeqToUI:0x201e:adr:0x24e7,Para:9447
120759310: UI:ShootSeqToUI:0x2029:adr:0x24e7,Para:9447
120759310: UI:_EnableReviewHold:IsPressSwTwo:0
120759310: UI:_EnableReviewHold:IsAvailableShots:1
120759310: UI:RecReviewCon_SetMode:0x0003
120759310: UI:DSIC:4c,0
120759310: SS:StopRev
120759310: UI:ScreenLock
120759340: UI:PB.RefPB
120759360: UI:PB.DrawI
120759360: SS:NextAvail(2),ReviewAvail(5)
120759360: UI:_EnableReviewHold:IsPressSwTwo:0
120759370: UI:_EnableReviewHold:IsAvailableShots:1
120759450: UI:DSIC:48,0
120759500: UI:LogicalEvent:0x3204:adr:0,Para:0
120759510: UI:PB.DcdCBR
120759510: UI:PB.RfrsI
120759520: UI:DispSwCon_MuteOffPhysicalScreen
120759520: UI:Window Reduce MuteOff
120759520: UI:ScreenUnLock
120759530: UI:Window Re MuteOff
120759530: UI:MuteOffPhysicalScreen
120759540: UI:DisplayPhysicalScreenCBR
120761380: UI:LogicalEvent:0x311e:adr:0,Para:0
120761380: UI:_EntryPrepareRecreviewOff
120761380: UI:ShootState:0xB
120761380: UI:ShtCon_StopReview
120761380: UI:StopRecReviewController
120761380: UI:PB.StopR
120761380: UI:ScreenLock
120761390: UI:ScreenUnLock
120761400: UI:LogicalEvent:0x3120:adr:0,Para:0
120761400: UI:_ExitSequence
120761400: UI:Sht_CancelStrobeChargeTimer
120761400: UI:DSIC:4c,0
120761400: UI:_ExitActionReview
120761400: SS:CancelPre
120761950: SS:ChargeComplete
120761950: UI:DispSwCon_MuteOffPhysicalScreen
120761950: UI:Window MuteOff
120761950: UI:MuteOffPhysicalScreen
120761950: UI:ShootState:0x0
120761950: UI:ShtCon_Deactivate
120761950: UI:DSIC:14,0
120761950: UI:DSIC:60,0
120761950: UI:DispSwCon_TurnOnDisplayDevice
120761950: UI:ScreenLock
120762050: UI:ScreenUnLock
120762050: UI:DispSw: Unlock
120762050: UI:DispSwCon:Unlock
120762050: UI:TerminateDeliverToZoomController
120762060: UI:ScreenLock
120762060: UI:ScreenUnLock
120762060: UI:OPTICAL_ZOOM_POS
120762060: UI:UnpressZoomLever
120762070: UI:ScreenLock
120762070: UI:Reduce ScreenUnLock
120762070: UI:ScreenLock
120762070: UI:ScreenUnLock
120762070: UI:_EntryIdleShoot
120762070: UI:ShootState:0x0
120762080: UI:DisplayPhysicalScreenCBR
120762080: UI:DisplayPhysicalScreenCBR
120762080: UI:DisplayPhysicalScreenCBR
120762090: UI:DisplayPhysicalScreenCBR
120762540: UI:ScreenLock
120762540: UI:ScreenUnLock
120762570: UI:DisplayPhysicalScreenCBR
120766080: UI:ScreenLock
120766080: UI:ScreenUnLock
 

I will run the standard selective interval script tomorrow in the A3300 and see what happens.

I also had an A3000 stop over the weekend during an overnight.  The romlogerr.txt says: Log is not Saved.  Might just be a power glitch, let's stay focused on the motionvector issue for now.


 

Related Topics