Now I will use another Arduino to cut and close the USB cables too.
does
(i) setting up all cams via chdkptp then
(ii) disconnecting usb powered hub network from PC then
(iii) power-off usb hub network [to trigger chdkusbremote]
followed by
(iv) reconnection and chdkptp SD card download
not fit your use case?
It may save a lot of soldering.
Have you carefully considered voltage discharge timing that user Hardware Hacker has referred to elsewhere?
With regards to CHDK I don't understand, I am sorry. When using CHDK it is no problem to switch between all the cameras within one instance. You are right, one instance can only communicate with one camera, uniquely. But instead of starting 100 instances of CHDKPTP I wonder if it isn't better to have SOME instances that each will have their set of cameras they serve for. I can't imagine that say 100 instances running at the same time would be of advantage for stability and speed.
While my hope is that many instances of chdkptp will prove stable I fear you are correct and that eventually I [or somebody else] must develop the multicam module further to allow for unique bus/id control.
While I know your code doesn't do that i'd be interested to read your lua single chdkptp implementation - might you please upload to this thread?
With regards to your light solution: I use an Arduino that switches a very cheap wireless power switcher you use in household, like these. This way the lights are turned of by the system, then everything that needs to be done in darkness is done in darkness, and afterwards the system switches the light back on. :-)
Thanks for the link.
I wasn't aware you are using dark conditions - is that for everything & using flash? if so, might you comment further on your requirement for chdk usbremote precision sync [rather than just longer exposure times]?