11-10-2011 10:43 AM
Hi Rick,
It sounds like your apprach of polling the serial numbers would be the correct approach. For more information on how to programmatically acquire camera serial numbers please see the Knowledge Base article located here.
There are also some potential issues with using multiple low end USB cameras. Please see the last post in this forum. As JasonS describes, you may not be able to programtically locate a USB device if it does not uniquely identify itself to Windows. You will have to manually identify the camera since the camera does not identify itself. However If it does uniquely identify itself, you should be able to programtically recognize it using either camera name, or serial number and then direct the information gathered from it accordingly.
David A.
11-21-2011 08:37 AM
Thanks for the input and links. I think we are going to be in good shape here since on the final machine that the application is running on, we have tight control over which cameras are plugged into which USB ports. We added an internal 4-port USB card and the user will be unable to move the cameras. Each camera is assigned a dedicated port on the PCI card and cannot be physically moved. I named each camera in MAX and over the last week none of the cameras has 'moved' in heavy testing and numerous reboots.
Interestingly these are Microsoft cameras so serial numbers *should* be unique and reported (they're not high-end but they are not exactly 'toys' or off-brand) and identify themselves properly to Windows.
I think some of the problem was that the USB hub I was using before is very low-end (dollar store!), good for real basic use but not good for something advanced like this, and I have multiple identical cameras that were being moved around further confusing the USB hub. Keeping them in the same place on a dedicated USB hub right on the bus seems to be keeping things straight.
11-21-2011 10:28 AM
Hello Rick J.,
Thank you for sharing your solution. I'm glad to hear your system is running reliably!
David A.