Can anyone comment on a fast (or perhaps an automated) method to install the libusb drivers for a large camera count on
- a single machine
- the same cameras on multiple machines
To "...Change USB Device Name reported "BY" the Host..."
I am still using the same basic method for about 4++ years now.
YES it could be "Automated" by AutoIT or similar .... But is it really worth the effort.
## Since my multiple cameras are usually ebay cheapies they tend to be delivered at
different and random times also Canon's USB iSerial Numbers are also random. So the
only practical solution is to "Test" and "Customize" the libusb camera drivers on a
as "Delivered" time scale.
## Canon's USB iSerial Numbers are then used to:-
"...Change USB Device Name reported "BY" the Host..."
by way of a "Custom" WDM Driver that also is LibUsb compatible.
## Windows is very "Unreliable" with multiple Usb devices of the same type...
An Example: My OLDER SanDisk USB Sticks are continually not recognized
by all versions of windows and it wants to "Re-Format" them [!@#$%^&*()]
## So if you have 64 Canon P&S cameras there are 64 versions of "LibUSB00.sys"
[to LibUSB63.sys] running as 64 "Separate" and "Unique" windows "Services".
Also I change the GUID from the one used by libUsb to something like:-
F000....A495....0000 for a Canon A495 camera so each camera model has a
"Unique" GUID as far as I can tell the F000......000 GUID is also "UN-Used" by windows.
## These 64 "Separate" and "Unique" windows "Services" also have "Customized" windows
friendly "Names" and windows "Messages. An Example:- Ixus_125 camera number 64
friendly "Name" could be "Ixus 125 #64" etc... etc... this is also synce'd with W-W's
large font so that that camera will also display "Ixus 125 #64" to keep track of every thing
just put a text file "Ixus_125_#64.txt" in the root of that camera's SD Card it can contain
any note's that you like. You can also make temporary changes to any file by changing
the 8.3 "Fat 12/16/32" "Names.DOS" to "Names~DOS" Examples:- "Ixus_125_#64.txt"
to "Ixus_125_#64~txt" 0r "Ixus_125_#64&txt" and even DISKBOOT.BIN to DISKBOOT~BIN
## Once the "Individual" libusb camera drivers are created its then a fairy quick and
easy process to then create further different versions that DO NOT require "INSTALLING"
Instead they are "MERGED" into the windows Registry it takes less than a second to do.
I have had NO problems and driver conflicts with "Merging" if you have the right privileges
you are then able to change any windows "Restricted" privileges without a system crash.
## Some of the libusb camera drivers have "Dummy" values, that windows will create when a
Camera in the Multi-Camera Array is connected. An Example is the Usb-2 Hubs, so if it is
blank that camera has never been connected to that Usb-2 Hub. etc....etc...
## Another important but UN-posted change I sometimes make is that I change the CHDK "SLEEP"
values from the standards that are suitable for the "CHDK Legacy Cameras" to one more suitable
for the much faster and newer Dig!c 4 and Dig!c 5 cameras, from memory sometimes this value is
as small as "1" sleep. This change will make a big difference when trying to control 64 cameras.
[i.e. Experiment with the sleep values.]
I think that the "Sleep" values could also be another problem in mphx's recent post:-
"....But with 64 cameras , things change...." Reply #325 on: 24/September/2015
Re: Multi-camera setup project. « Reply #327 on: 25/September/2015 http://chdk.setepontos.com/index.php?topic=11667.msg124821#msg124821
@@ As this is a very complex subject it's ONLY worthwhile doing for large and complex
Multi-Camera Arrays and the LibUsb Camera Custom Drivers are always developed
and tested on a PE or RE version of windows run totally in Ram, one simple typo will
result in a system crash.
@@ Also in accordance with forum rule "Number 5" to use the PE or RE version of windows you will
need to check the license compliance. I used the "Preview Versions" which have a much simpler
and unrestricted Licence.