Jump to content
Sign in to follow this  
BobHamburger

USB Image Acquistion

Recommended Posts

I just purchased a Logitech Quickcam for Notebooks Deluxe. The drivers from Logitech install smoothly and the camera works great. However, I cannot make this work through LabVIEW. I've tried four approaches that seem equally frustrating:

1. Downloaded NI's IMAQ for USB API. Nice, familiar VI's, but I can't get past the IMAQ USB Init.vi -- it kicks out one of those "An exception occurred within the external code..." error messages.

http://forums.lavag.org/index.php?act=attach&type=post&id=6006

2. I tried using Peter Parente's Webcam 1.4 utilities. These run, but neither produce any image nor return any errors!

http://forums.lavag.org/index.php?act=attach&type=post&id=6007

3. Tried downloading Chris Relf's Quickcam drivers, but the version that I found (on info-labview) seems too old to work. Broken arrows everywhere, and all of the ActiveX methods seem to be invalid.

4. I searched the forums here using the terms IMAQ and USB. I found lots and lots of postings, but I can't seem to read any of the thread replies! I can get to the original postings, with a tree of replies underneath. Clicking on any of the links to replies goes nowhere.

http://forums.lavag.org/index.php?act=attach&type=post&id=6008

Right now I feel like an idiot, and I don't like feeling like an idiot.

Share this post


Link to post
Share on other sites

QUOTE(BobHamburger @ Jun 4 2007, 02:30 PM)

Hmmm - this is, by far, your best option, and I'm really surprised it's not working for you. I don't have a USB cam on hand, but I'll try it tomorrow.

QUOTE(BobHamburger @ Jun 4 2007, 02:30 PM)

2. Peter Parente's Webcam 1.4 utilities.

Old and unsupported - in fact, they were just an experiment of Pete's to begin with and were never really meant to be anything more than that - I wouldn't persue this option.

QUOTE(BobHamburger @ Jun 4 2007, 02:30 PM)

Ugh! I thought I'd put those to bed a loooooong time ago :o These drivers are for Logitech's QuickCAM 3000 only (many years ago).

QUOTE(BobHamburger @ Jun 4 2007, 02:30 PM)

4. I can get to the original postings, with a tree of replies underneath.

I can't solve the threading problem, but click on "Options" at the top right of the threads and select "Display Modes>>Switch to: Standard" - that should inline all the posts so you can see them all at once.

QUOTE(BobHamburger @ Jun 4 2007, 02:30 PM)

Right now I feel like an idiot, and I don't like feeling like an idiot.

We've all been there :)

Share this post


Link to post
Share on other sites

QUOTE(crelf @ Jun 4 2007, 12:52 AM)

Old and unsupported - in fact, they were just an experiment of Pete's to begin with and were never really meant to be anything more than that - I wouldn't persue this option.

Yeah, but what I really liked about this potential approach was that it doesn't require NI IMAQ, with its incumbent licensing issues...

Share this post


Link to post
Share on other sites

Here's a VI that I created for a project, it uses the NI IMAQ USB library, I've used a Logitech QuickCam IM with this and it works. I think the problem in your original implementation was the "USB Camera Name" input might not have been right, this VI selects the name from a list.

http://forums.lavag.org/index.php?act=attach&type=post&id=6012

Share this post


Link to post
Share on other sites

If you are using Windows you should also be able to use Microsoft DirectX library .NET interface that provides API for webcam connectivity. LabVIEW allows you to interface any .NET API using .NET nodes.

Share this post


Link to post
Share on other sites

Hello,

Please try out IVision LabVIEW toolkit:

http://www.hytekautomation.com/Products/IVision.html

It contains not only video acquisition, video mixing functions, as well as image processing functions. You can ask question in IVision forum if you get any.

http://forum.hytekautomation.com

If you just want video recording, display without processing it, then you may also check out iUSBDAQ - U1208LOG, this is a USB data acquisition module with video functions, you get both fast speed USB DAQ plus video plus logger , here is the link:

http://www.hytekautomation.com/Products/IUSBDAQLog.html

should be available soon.

Irene

QUOTE(Tomi Maila @ Jun 4 2007, 07:44 AM)

If you are using Windows you should also be able to use Microsoft DirectX library .NET interface that provides API for webcam connectivity. LabVIEW allows you to interface any .NET API using .NET nodes.

Managed directX (directX for dot net) has very limited support for directshow, there are some functions in .net for supporting avi playback, I doubt it has even support for webcam at all in .net and I read somewhere that Microsoft is not going to do so for a reason that it's hard to do it in .net.

Irene

Share this post


Link to post
Share on other sites

QUOTE(Irene_he @ Jun 4 2007, 06:45 PM)

Managed directX (directX for dot net) has very limited support for directshow, there are some functions in .net for supporting avi playback, I doubt it has even support for webcam at all in .net and I read somewhere that Microsoft is not going to do so for a reason that it's hard to do it in .net.

It's very very hard to beleave that this still applies to DirectX 10

Tomi

Share this post


Link to post
Share on other sites

QUOTE(Tomi Maila @ Jun 4 2007, 12:07 PM)

It's very very hard to beleave that this still applies to DirectX 10

Tomi

Sometimes you just have to take it even it's very hard to believe.

:)

That said, if there is really anything you want to do in dot net for webcam, you have to do it in C++.net which then is unmanaged code, then you have to wrap up for C# or VB.net to be used in managed directx...

Irene

Share this post


Link to post
Share on other sites

QUOTE(Karissap @ Jun 4 2007, 02:42 AM)

This one did the trick. Although I had run the IMAQ USB Enumerate Cameras.vi in order to get the name, I blithely just looked at the indicator and typed the name into a string constant on my diagram rather than wiring it in... thus missing the 0x00 at the end of the name (either a terminator or device 0, I'm not sure). Either way, the name was indeed wrong. I think that this little piece of code should be posted to the Code Repository; if it can prevent heartburn in one other situation it's worth it.

Everybody, thanks for the input and insight..

Share this post


Link to post
Share on other sites

QUOTE(BobHamburger @ Jun 5 2007, 04:20 AM)

I blithely just looked at the indicator and typed the name into a string constant on my diagram rather than wiring it in... thus missing the 0x00 at the end of the name

Ahhhhh bugger! I'm glad you've got it up and running.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.