However, it is currently unclear, to me, whether the usbhub reorganisation is solely responsible for the improved results or whether that and the smaller footprint of CHDK_LIGHT was responsible.
IMO this is unlikely for several reasons:
FWIW, I'm very unlikely to spend any of my time debugging CHDK_LIGHT or supporting it in any other way.
___> !return mc:cmdwait('preshoot')preshoot=true,{ [1]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [2]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [3]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [4]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [5]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [6]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [7]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [8]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [9]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [10]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [11]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [12]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [13]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [14]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [15]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, }, [16]={ failed=false, done=true, status={ status=true, cmd="preshoot", }, },}___> !return mc:cmdwait('usb_sync_wait')usb_sync_wait=true,{ [1]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [2]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [3]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [4]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [5]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [6]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [7]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [8]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [9]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [10]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [11]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [12]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [13]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [14]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [15]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, }, [16]={ failed=false, done=true, status={ status=true, cmd="usb_sync_wait", }, },}___> !mc:download_images({lastimg=1,fmatch='JPG$'})ERROR: call failed:I/O error___> !mc:camstatus()#1 connected#2 NOT connected#3 connected#4 connected#5 connected#6 connected#7 connected#8 connected#9 connected#10 connected#11 connected#12 connected#13 connected#14 connected#15 connected#16 connectedSummary: 16 cameras (15 connected, 1 disconnected)___>
With Phil's latest build (thankfully uploaded to all cameras using existing chdkptp):Test was: lock_ptp_commsswitch to recordrepeat x 8preshoot->usb_sync_shoot->open 5V switch->download to PC->delete camera imagewas successful.On the 9th cycle, at download an I/O error occurred and cam2 made the usb disconnect sound.romlog attached (date is as per camera).
I haven't read the entire thread in detail - is there a script (or set of steps) that I could run (on a single camera) to try and replicate what you are doing?
!mt=require'extras/msgtest'!mt.test{size=100,sizemax=100,count=1000,busy=true}gives me an exception vextor 0x10 in PTPSessionTA0 within a few hundred iterations.
Just tried this on the G12 - 10,000 iterations and no error
I wonder if it is dependant on amount of free memory - i.e. could be a memory leak. G12 has > 4MB free.
Quote from: philmoz on 06 / October / 2017, 03:50:18Just tried this on the G12 - 10,000 iterations and no error Double check you are using the correct version of extras/msgtest.lua file? The same command I posted would run with previous versions, but only the version I checked in last night has the "busy" test that triggers the crash for me.
Started by superfly Feature Requests
Started by artanim Creative Uses of CHDK
Started by indian22 « 1 2 3 4 5 » General Discussion and Assistance
Started by ghust10 RAW Shooting and Processing
Started by amavroidis « 1 2 ... 5 6 » General Discussion and Assistance
