suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras) - page 2 - General Discussion and Assistance - CHDK Forum

suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)

  • 77 Replies
  • 10961 Views
Re: suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)
« Reply #10 on: 28 / September / 2017, 06:04:04 »
Advertisements
reyalp, thanks for your earlier comment.

Phil, please let me take care of a slight hangover & then i'm right on it  ;)

*

Offline reyalp

  • ******
  • 12218
Re: suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)
« Reply #11 on: 28 / September / 2017, 12:51:53 »
Comments in the makefile.inc suggest this port had little free memory, so it would be a good idea to check the CHDK memory info (or =return get_meminfo() in chdkptp) with Philmoz' build.
Don't forget what the H stands for.

Re: suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)
« Reply #12 on: 29 / September / 2017, 04:23:40 »
Having connected to all 16 cameras I used:
Code: [Select]
!savecon=con for lcon in mc:icams() do con=lcon cli:print_status(cli:execute('mup C:/CHDKPTP/PHILMOZ-DEBUG A/')) end con=savecon
to update to Phil's build. Apart from starting the uploads very quickly then slowing to a crawl for one or two cameras - no issues.

Then, using the chdkptp gui with a single camera:
Code: [Select]
> =return get_meminfo()
2:return:table:{chdk_start=63589344,free_size=204824,chdk_size=134224,allocated_size=1473528,free_block_count=12,name="combined",allocated_count=1582,chdk_malloc=true,free_block_max_size=202584,allocated_peak=1543784,total_size=1678408,}


Minor (?) teething problem - having then restarted multicam, what I think is the Alt helpscreen is (randomly) causing multicam to report script as not running on those cameras on which it is displayed. Two screenshots and a clitrace hopefully describe that.

Is there some lua code  I could use in multicam to turn that off (it's a relatively major exercise to do anything individually on all the cameras) and do any balance in the GUI:
Code: [Select]
___> !mc=require('multicam')
___> !mc:connect({list='C:/CHDKPTP/listfile'})
+ 1:Canon PowerShot SX150 IS b=\\.\libusb0-0001--0x04a9-0x3234 d=bus-0 s=9A95243
8E0A647E9AC0179DDC30582D5
+ 2:Canon PowerShot SX150 IS b=\\.\libusb0-0002--0x04a9-0x3234 d=bus-0 s=689D500
5104943C09E988E4EA8301E22
+ 3:Canon PowerShot SX150 IS b=\\.\libusb0-0003--0x04a9-0x3234 d=bus-0 s=E21B7D7
37E5D4291B5DD048230963CF6
+ 4:Canon PowerShot SX150 IS b=\\.\libusb0-0004--0x04a9-0x3234 d=bus-0 s=449A58C
8297A4CCDAD05327C6BDD6FC2
+ 5:Canon PowerShot SX150 IS b=\\.\libusb0-0005--0x04a9-0x3234 d=bus-0 s=A42727D
40A154E39945D810173405135
+ 6:Canon PowerShot SX150 IS b=\\.\libusb0-0006--0x04a9-0x3234 d=bus-0 s=6C13E0E
B6FF04FEF9D0F50BFAB5B9420
+ 7:Canon PowerShot SX150 IS b=\\.\libusb0-0007--0x04a9-0x3234 d=bus-0 s=F5C3101
2304A49F4B4D84B8736A8714C
+ 8:Canon PowerShot SX150 IS b=\\.\libusb0-0008--0x04a9-0x3234 d=bus-0 s=52358FA
70E8940F9B145A6C7053BB251
+ 9:Canon PowerShot SX150 IS b=\\.\libusb0-0009--0x04a9-0x3234 d=bus-0 s=3AE0C06
EB29A4819B9E48764D58B9E2D
+ 10:Canon PowerShot SX150 IS b=\\.\libusb0-0010--0x04a9-0x3234 d=bus-0 s=D10AC1
5E25614FEBB5AF36C058AE46E1
+ 11:Canon PowerShot SX150 IS b=\\.\libusb0-0011--0x04a9-0x3234 d=bus-0 s=774F38
7C25634767917D45F411CF1C0C
+ 12:Canon PowerShot SX150 IS b=\\.\libusb0-0012--0x04a9-0x3234 d=bus-0 s=FE454C
0413DA4B4F8B00FC8B52DD2853
+ 13:Canon PowerShot SX150 IS b=\\.\libusb0-0013--0x04a9-0x3234 d=bus-0 s=31DD97
F7523B4654B55781E96DE9D38E
+ 14:Canon PowerShot SX150 IS b=\\.\libusb0-0014--0x04a9-0x3234 d=bus-0 s=9E5157
ABAF954861A345B6C0775E14BE
+ 15:Canon PowerShot SX150 IS b=\\.\libusb0-0015--0x04a9-0x3234 d=bus-0 s=82AF4B
BBDDE74EC69EB783057889B66E
+ 16:Canon PowerShot SX150 IS b=\\.\libusb0-0016--0x04a9-0x3234 d=bus-0 s=2C638E
36A31242B8B600ED3341D91884
WARNING: missing cam 45:78FF059B30614728892637799CB908C8
___> !mc:start()
___> !mc:cmd('id')
id
WARNING: 1: send id cmd failed: no script running
WARNING: 5: send id cmd failed: no script running
WARNING: 6: send id cmd failed: no script running
___>

Edit:
in case it could be useful, I have an A2500 (described as beaten but 100% functional) arriving soon if that could help in testing anywhere.

Edit2: so, I set the Alt helpscreen to off in one camera then copied (via multicam) the cfg files from it to the other 15. That got rid of the Alt helpscreen appearance but not the "no script running" message (on 2 cameras) which I had assumed was connected to the occurrence of the Alt helpscreen. Will provide further update asap. 
« Last Edit: 29 / September / 2017, 10:52:38 by andrew.stephens.754365 »

Re: suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)
« Reply #13 on: 29 / September / 2017, 12:50:18 »
This feedback is, I think, quite strange so not sue what (if any) comment to expect. This is the first experience of anything like this.

Description:

I added this to multicam:
Code: [Select]
function mc:camstatus()
local cn=0
local nc=0
    for lcon in mc:icams() do
        if not lcon:is_connected() then
            nc=nc+1
            printf('#%s NOT connected\n',lcon.mc_id)
        else
            cn=cn+1
            printf('#%s connected\n',lcon.mc_id)
        end
    end
    printf('\nSummary: %d cameras (%d connected, %d disconnected)\n',cn+nc,cn,nc)
end

After successfully connecting to all cameras I confirmed connection via camstatus() . I then (attempted) to start the remote script's and display camera ID on each camera LCD. After this the cli reported that command having failed on Cam5&10 as no script was running. Executing camstatus() again revealed all 16 cameras as still connected (& unsurprisingly, there had been no usb disconnect sound throughout the test).

Screenshot of cam10 at test end attached.

This behaviour seems (to me) to have no natural link to any previously described issues but I can't currently imagine what this problem could be as a result of (other than the script not getting copied over and starting to execute, of course!). 

clitrace:
Code: [Select]
___> !mc=require('multicam')
___> !mc:connect({list='C:/CHDKPTP/listfile'})
+ 1:Canon PowerShot SX150 IS b=\\.\libusb0-0001--0x04a9-0x3234 d=bus-0 s=3AE0C06
EB29A4819B9E48764D58B9E2D
+ 2:Canon PowerShot SX150 IS b=\\.\libusb0-0002--0x04a9-0x3234 d=bus-0 s=D10AC15
E25614FEBB5AF36C058AE46E1
+ 3:Canon PowerShot SX150 IS b=\\.\libusb0-0003--0x04a9-0x3234 d=bus-0 s=774F387
C25634767917D45F411CF1C0C
+ 4:Canon PowerShot SX150 IS b=\\.\libusb0-0004--0x04a9-0x3234 d=bus-0 s=FE454C0
413DA4B4F8B00FC8B52DD2853
+ 5:Canon PowerShot SX150 IS b=\\.\libusb0-0005--0x04a9-0x3234 d=bus-0 s=31DD97F
7523B4654B55781E96DE9D38E
+ 6:Canon PowerShot SX150 IS b=\\.\libusb0-0006--0x04a9-0x3234 d=bus-0 s=9E5157A
BAF954861A345B6C0775E14BE
+ 7:Canon PowerShot SX150 IS b=\\.\libusb0-0007--0x04a9-0x3234 d=bus-0 s=82AF4BB
BDDE74EC69EB783057889B66E
+ 8:Canon PowerShot SX150 IS b=\\.\libusb0-0008--0x04a9-0x3234 d=bus-0 s=2C638E3
6A31242B8B600ED3341D91884
+ 9:Canon PowerShot SX150 IS b=\\.\libusb0-0009--0x04a9-0x3234 d=bus-0 s=9A95243
8E0A647E9AC0179DDC30582D5
+ 10:Canon PowerShot SX150 IS b=\\.\libusb0-0010--0x04a9-0x3234 d=bus-0 s=689D50
05104943C09E988E4EA8301E22
+ 11:Canon PowerShot SX150 IS b=\\.\libusb0-0011--0x04a9-0x3234 d=bus-0 s=E21B7D
737E5D4291B5DD048230963CF6
+ 12:Canon PowerShot SX150 IS b=\\.\libusb0-0012--0x04a9-0x3234 d=bus-0 s=449A58
C8297A4CCDAD05327C6BDD6FC2
+ 13:Canon PowerShot SX150 IS b=\\.\libusb0-0013--0x04a9-0x3234 d=bus-0 s=A42727
D40A154E39945D810173405135
+ 14:Canon PowerShot SX150 IS b=\\.\libusb0-0014--0x04a9-0x3234 d=bus-0 s=6C13E0
EB6FF04FEF9D0F50BFAB5B9420
+ 15:Canon PowerShot SX150 IS b=\\.\libusb0-0015--0x04a9-0x3234 d=bus-0 s=F5C310
12304A49F4B4D84B8736A8714C
+ 16:Canon PowerShot SX150 IS b=\\.\libusb0-0016--0x04a9-0x3234 d=bus-0 s=52358F
A70E8940F9B145A6C7053BB251
___> !mc:camstatus()
#1 connected
#2 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 connected

Summary: 16 cameras (16 connected, 0 disconnected)
___> !mc:start()
___> !mc:cmd('id')
id
WARNING: 5: send id cmd failed: no script running
WARNING: 10: send id cmd failed: no script running
___> !mc:camstatus()
#1 connected
#2 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 connected

Summary: 16 cameras (16 connected, 0 disconnected)
___>


*

Offline reyalp

  • ******
  • 12218
Re: suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)
« Reply #14 on: 29 / September / 2017, 13:16:35 »
Code: [Select]
> =return get_meminfo()
2:return:table:{chdk_start=63589344,free_size=204824,chdk_size=134224,allocated_size=1473528,free_block_count=12,name="combined",allocated_count=1582,chdk_malloc=true,free_block_max_size=202584,allocated_peak=1543784,total_size=1678408,}

200k is marginal, but may be sufficient to test.

Had the camera been switched to rec at this point? The camera will use some additional memory the first time it switches to rec.

You could keep lua memory usage at a minimum by putting
collectgarbage('collect') in the main loop of the camera side script, right before

local msg=read_usb_msg(mc.msg_timeout)

Quote
That got rid of the Alt helpscreen appearance but not the "no script running" message (on 2 cameras) which I had assumed was connected to the occurrence of the Alt helpscreen. Will provide further update asap.
Yeah, the help screen shouldn't have anything to do with the script not running message. It's possible you might see something in the CHDK console (using "show last console" in the menu) of the cameras where the script isn't running.
Low memory could cause the script to exit.
Don't forget what the H stands for.

Re: suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)
« Reply #15 on: 29 / September / 2017, 15:04:58 »
Had the camera been switched to rec at this point? The camera will use some additional memory the first time it switches to rec.

No (oh dear).

You could keep lua memory usage at a minimum by putting
collectgarbage('collect') in the main loop of the camera side script, right before

local msg=read_usb_msg(mc.msg_timeout)

Not exactly sure when i'll get the next bash at this but will try that and get back.

Thanks for suggestion and comment.

Re: suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)
« Reply #16 on: 30 / September / 2017, 04:21:58 »
Having added collectgarbage, cli reports script not running on 4 (still connected - Cams 4,5,6&12) cameras:
Code: [Select]
___> !mc=require('multicam')
___> !mc:connect({list='C:/CHDKPTP/listfile'})
+ 1:Canon PowerShot SX150 IS b=\\.\libusb0-0001--0x04a9-0x3234 d=bus-0 s=3AE0C06
EB29A4819B9E48764D58B9E2D
+ 2:Canon PowerShot SX150 IS b=\\.\libusb0-0002--0x04a9-0x3234 d=bus-0 s=9A95243
8E0A647E9AC0179DDC30582D5
+ 3:Canon PowerShot SX150 IS b=\\.\libusb0-0003--0x04a9-0x3234 d=bus-0 s=D10AC15
E25614FEBB5AF36C058AE46E1
+ 4:Canon PowerShot SX150 IS b=\\.\libusb0-0004--0x04a9-0x3234 d=bus-0 s=689D500
5104943C09E988E4EA8301E22
+ 5:Canon PowerShot SX150 IS b=\\.\libusb0-0005--0x04a9-0x3234 d=bus-0 s=774F387
C25634767917D45F411CF1C0C
+ 6:Canon PowerShot SX150 IS b=\\.\libusb0-0006--0x04a9-0x3234 d=bus-0 s=E21B7D7
37E5D4291B5DD048230963CF6
+ 7:Canon PowerShot SX150 IS b=\\.\libusb0-0007--0x04a9-0x3234 d=bus-0 s=FE454C0
413DA4B4F8B00FC8B52DD2853
+ 8:Canon PowerShot SX150 IS b=\\.\libusb0-0008--0x04a9-0x3234 d=bus-0 s=449A58C
8297A4CCDAD05327C6BDD6FC2
+ 9:Canon PowerShot SX150 IS b=\\.\libusb0-0009--0x04a9-0x3234 d=bus-0 s=31DD97F
7523B4654B55781E96DE9D38E
+ 10:Canon PowerShot SX150 IS b=\\.\libusb0-0010--0x04a9-0x3234 d=bus-0 s=A42727
D40A154E39945D810173405135
+ 11:Canon PowerShot SX150 IS b=\\.\libusb0-0011--0x04a9-0x3234 d=bus-0 s=9E5157
ABAF954861A345B6C0775E14BE
+ 12:Canon PowerShot SX150 IS b=\\.\libusb0-0012--0x04a9-0x3234 d=bus-0 s=6C13E0
EB6FF04FEF9D0F50BFAB5B9420
+ 13:Canon PowerShot SX150 IS b=\\.\libusb0-0013--0x04a9-0x3234 d=bus-0 s=82AF4B
BBDDE74EC69EB783057889B66E
+ 14:Canon PowerShot SX150 IS b=\\.\libusb0-0014--0x04a9-0x3234 d=bus-0 s=F5C310
12304A49F4B4D84B8736A8714C
+ 15:Canon PowerShot SX150 IS b=\\.\libusb0-0015--0x04a9-0x3234 d=bus-0 s=2C638E
36A31242B8B600ED3341D91884
+ 16:Canon PowerShot SX150 IS b=\\.\libusb0-0016--0x04a9-0x3234 d=bus-0 s=52358F
A70E8940F9B145A6C7053BB251
___> !mc:camstatus()
#1 connected
#2 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 connected

Summary: 16 cameras (16 connected, 0 disconnected)
___> !mc:start()
___> !mc:cmd('id')
id
WARNING: 4: send id cmd failed: no script running
WARNING: 5: send id cmd failed: no script running
WARNING: 6: send id cmd failed: no script running
WARNING: 12: send id cmd failed: no script running
___> !mc:camstatus()
#1 connected
#2 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 connected

Summary: 16 cameras (16 connected, 0 disconnected)
___>

Edit1:
Of some interest, on a second test, scrpt initially failed to start on 2 cameras (oddly perhaps, these 2 cameras (Cam4&5) were two of the four which failed to start in the first test?) but another attempt to start script on all cameras (which includes clobbering those already running) was successful:

Code: [Select]
___> !mc=require('multicam')
___> !mc:connect({list='C:/CHDKPTP/listfile'})
+ 1:Canon PowerShot SX150 IS b=\\.\libusb0-0001--0x04a9-0x3234 d=bus-0 s=9A95243
8E0A647E9AC0179DDC30582D5
+ 2:Canon PowerShot SX150 IS b=\\.\libusb0-0002--0x04a9-0x3234 d=bus-0 s=3AE0C06
EB29A4819B9E48764D58B9E2D
+ 3:Canon PowerShot SX150 IS b=\\.\libusb0-0003--0x04a9-0x3234 d=bus-0 s=689D500
5104943C09E988E4EA8301E22
+ 4:Canon PowerShot SX150 IS b=\\.\libusb0-0004--0x04a9-0x3234 d=bus-0 s=D10AC15
E25614FEBB5AF36C058AE46E1
+ 5:Canon PowerShot SX150 IS b=\\.\libusb0-0005--0x04a9-0x3234 d=bus-0 s=E21B7D7
37E5D4291B5DD048230963CF6
+ 6:Canon PowerShot SX150 IS b=\\.\libusb0-0006--0x04a9-0x3234 d=bus-0 s=774F387
C25634767917D45F411CF1C0C
+ 7:Canon PowerShot SX150 IS b=\\.\libusb0-0007--0x04a9-0x3234 d=bus-0 s=449A58C
8297A4CCDAD05327C6BDD6FC2
+ 8:Canon PowerShot SX150 IS b=\\.\libusb0-0008--0x04a9-0x3234 d=bus-0 s=FE454C0
413DA4B4F8B00FC8B52DD2853
+ 9:Canon PowerShot SX150 IS b=\\.\libusb0-0009--0x04a9-0x3234 d=bus-0 s=A42727D
40A154E39945D810173405135
+ 10:Canon PowerShot SX150 IS b=\\.\libusb0-0010--0x04a9-0x3234 d=bus-0 s=31DD97
F7523B4654B55781E96DE9D38E
+ 11:Canon PowerShot SX150 IS b=\\.\libusb0-0011--0x04a9-0x3234 d=bus-0 s=6C13E0
EB6FF04FEF9D0F50BFAB5B9420
+ 12:Canon PowerShot SX150 IS b=\\.\libusb0-0012--0x04a9-0x3234 d=bus-0 s=9E5157
ABAF954861A345B6C0775E14BE
+ 13:Canon PowerShot SX150 IS b=\\.\libusb0-0013--0x04a9-0x3234 d=bus-0 s=F5C310
12304A49F4B4D84B8736A8714C
+ 14:Canon PowerShot SX150 IS b=\\.\libusb0-0014--0x04a9-0x3234 d=bus-0 s=82AF4B
BBDDE74EC69EB783057889B66E
+ 15:Canon PowerShot SX150 IS b=\\.\libusb0-0015--0x04a9-0x3234 d=bus-0 s=52358F
A70E8940F9B145A6C7053BB251
+ 16:Canon PowerShot SX150 IS b=\\.\libusb0-0016--0x04a9-0x3234 d=bus-0 s=2C638E
36A31242B8B600ED3341D91884
___> !mc:camstatus()
#1 connected
#2 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 connected

Summary: 16 cameras (16 connected, 0 disconnected)
___> !mc:start()
___> !mc:camstatus()
#1 connected
#2 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 connected

Summary: 16 cameras (16 connected, 0 disconnected)
___> !mc:cmd('id')
id
WARNING: 4: send id cmd failed: no script running
WARNING: 5: send id cmd failed: no script running
___> !mc:start()
WARNING: 1: attempting to stop running script
WARNING: 2: attempting to stop running script
WARNING: 3: attempting to stop running script
WARNING: 6: attempting to stop running script
WARNING: 7: attempting to stop running script
WARNING: 8: attempting to stop running script
WARNING: 9: attempting to stop running script
WARNING: 10: attempting to stop running script
WARNING: 11: attempting to stop running script
WARNING: 12: attempting to stop running script
WARNING: 13: attempting to stop running script
WARNING: 14: attempting to stop running script
WARNING: 15: attempting to stop running script
WARNING: 16: attempting to stop running script
___> !mc:camstatus()
#1 connected
#2 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 connected

Summary: 16 cameras (16 connected, 0 disconnected)
___> !mc:cmd('id')
id
___>
 

Edit2:
subsequently, with all scripts running:
  • lock ptp comms "on" was successful on all cameras
  • switch to record caused Cam 12 to crash (usb disconnect sound)  - no romlog.
« Last Edit: 30 / September / 2017, 05:57:59 by andrew.stephens.754365 »

*

Offline reyalp

  • ******
  • 12218
Re: suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)
« Reply #17 on: 30 / September / 2017, 16:37:27 »
check free memory after switching to rec.
check for messages in the CHDK console on the cameras that fail with "script not running"
Don't forget what the H stands for.


Re: suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)
« Reply #18 on: 02 / October / 2017, 17:09:35 »
To test memory, I added the following to cameraside multicam:
Code: [Select]
function cmds.memory_stats()
    --e.g. to run !return mc:cmdwait('memory_stats')
    local memory_amount ={}
    memory_amount = get_meminfo()
    write_status(serialize(memory_amount), 'memory_details')
end

After connecting to all 16 cameras and attempting to start the remote script's, Cam5 reported as not running. Apart from lack of ID the camera display was the same as all other cameras (OK 0x3cc5830 / DEFAULT SCRIPT <ALT>)

Attempting to start the script's for a second time was successful on all cameras and the ID   displayed on all. Function memory_stats followed by lock_ptp_comms executed on all cameras without fail but then switch to record caused Cam 12 to crash (usb disconnect sound) without romlog.

Having turned off all cameras and then connecting to Cam12 with the GUI provided pre & post record memory as:
Code: [Select]
> =return get_meminfo()
2:return:table:{chdk_start=63589344,free_size=204152,chdk_size=134224,allocated_size=1474200,free_block_count=11,name="combined",allocated_count=1584,chdk_malloc=true,free_block_max_size=202280,allocated_peak=1544416,total_size=1678408,}
> =return get_meminfo()
4:return:table:{chdk_start=63589344,free_size=203536,chdk_size=134224,allocated_size=1474832,free_block_count=7,name="combined",allocated_count=1607,chdk_malloc=true,free_block_max_size=203272,allocated_peak=1544416,total_size=1678408,}

Ths cli trace is attached.
« Last Edit: 02 / October / 2017, 17:11:25 by andrew.stephens.754365 »

*

Offline reyalp

  • ******
  • 12218
Re: suba threading bug (was Re: 3D scanner with multiple IXUS160 cameras)
« Reply #19 on: 02 / October / 2017, 18:10:01 »
After connecting to all 16 cameras and attempting to start the remote script's, Cam5 reported as not running. Apart from lack of ID the camera display was the same as all other cameras (OK 0x3cc5830 / DEFAULT SCRIPT <ALT>)
Did you check "Miscellaneous -> Console -> Display last console" on the failed camera?

From your cli output, most cameras show free_block_max_size as only ~30kb, which is not nearly enough for stable operation.

Code: [Select]
[5]={
  failed=false,
  done=true,
  status={
   msg="memory_details",
   cmd="memory_stats",
   status="{chdk_start=63589344,free_size=87840,chdk_size=134224,allocated_size=
1590264,free_block_count=181,name=\"combined\",allocated_count=2427,chdk_malloc=
true,free_block_max_size=30984,allocated_peak=1671536,total_size=1678408,}",
  },
 },

Interestingly, camera 14 shows free_size=459712 and free_block_max_size=218592. I wonder if that camera is still running the old build?
Don't forget what the H stands for.

 

Related Topics