Acquisition issues with Logitech C910 Webcam and Vision Builder 2009

[Ed388]

Hello all,

We have a Logitech C910 HD webcam (USB interface) configured for use with Vision Builder 2009. 

The acquired images when editing the 'Acquire Image' step are perfect- great exposure and detail!

Using the Acquire Single Image and Acquire Multiple Images buttons, we can capture a single image, or cycle continuously.

We can also edit the camera settings (focus, exposure, white balance etc) during the edit step.

However when I execute the acquisition by running an inspection, the step fails and I don't get an image.

The C910 is a Directshow device, and we're unsure about who to ask to help solve the issue.

One possible clue to the issue is the blue 'camera operating' LEDs on either side of the lens- they don't appear to turn on when the image should be being acquired.

Can anyone help with a solution which allows us to capture images?

Also, is it possible to use multiple USB cameras within a single inspection?

Thanks for your attention.

Ed

[Z'atari]

Hey Ed,

Do you have some sort of error code or snapshots that you can send our way so we can help you more efficiently...

Yes, it should possible to use multiple USB cameras on a single inspection.

Regards,

A. Zaatari

[Ed388]

Thanks for the reply Z'Atari,

I resolved the issue by rebooting the system (not hust the VBAI software). Since then I haven't seen the issue reappear.

Regarding the use of 2 USB cameras, I understand the Logitech software doesn't allow the use of 2 C910 cameras on the one PC.

Q/ Do you think this limitation will limit the use of two C910s using Vision Builder?

I guess the easy way to find out is to buy another C910, however I'd like to hear your opinion first.

Cheers

Ed

[Brad]

For USB cameras, the ni-imaqdx driver calls the camera manufacturer's driver, so any bugs/limitations with their driver won't be fixed by ours. So if their driver doesn't allow multiple cameras at the same time, I don't think it will work.  I think that camera may be recognized by Windows built-in drivers...not sure if they get around this limitation, but thought I'd pass that along.