LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

change of resolution with logitech 920 USB camera

I checked the available resolutions and framerates in MAX, and I get an error when programmatically changing to the desired resolution.

 

After reviewing several posts, the result from the LabVIEW example "Getting Started with Attributes.vi" using IMAQdx Enumerate Attributes indicates that "AcquisitionAttributes::Height" is not writable.

I suspect this is an issue with the camera (Logitech C920). Is that correct?

 

If so, how can I determine if programmatic resolution changes are possible before purchasing another camera?

Additionally, in MAX, I can set and save the resolution. How is this change applied?

 

labmaster_0-1749199971769.png

 

labmaster.

 

================

The video mode appears as writable, but even when trying to change the video mode with the code below, it doesn't work. No error occurs at the property node, but right after passing through Configure Grab.vi, I get -2147220969, an undefined error, which makes it even more difficult.

 

labmaster_0-1749201368628.png

 

 

0 Kudos
Message 1 of 6
(477 Views)

The spec says that it should be able to change to these resolutions: 

Image Capture (16:9 W) 2.0 MP, 3 MP*, 6 MP*, 15 MP*

 

If you use the vi called "IMAQdx Enumerate Video Modes.vi" you will be able to see the available video modes in the camera. I use this to populate a ring and then I can change the ring value to change the camera settings. 

aeastet_0-1749210346076.png

 

Tim
GHSP
Message 2 of 6
(446 Views)

You will also need to end the session of the current camera set up the camera again start the session and then set the video mode again.

aeastet_0-1749210450465.png

 

Tim
GHSP
0 Kudos
Message 3 of 6
(442 Views)

@labmaster wrote:

 

If so, how can I determine if programmatic resolution changes are possible before purchasing another camera?


If you want to use NI's IMAQ drivers it's probably best to pick a camera that follows one of the specific standard supported by the driver like USB3 Vision or GigE Vision.

 

I may be mis-remembering the details but I thought USB 2.0 cameras would work through DirectShow and, for some reason, not all the properties are always exposed through that API.

0 Kudos
Message 4 of 6
(424 Views)

I have integrated many different USB cameras into my camera software. I believe that this was one of the cameras I have used. You should be able to do all of what you want to do. Every USB camera that I have plugged into my software works great. I do not think you need to go to an expensive camera like gig E unless you really want to. Not sure about what you are using it for but I can tell you that this camera that you are asking about can be controlled using the IMAQdx code. You will have to build the camera loop to do everything that you want.

Tim
GHSP
0 Kudos
Message 5 of 6
(411 Views)

aeastet,

It was the same method you used.
Upon closer inspection after posting, I noticed that "unknown" was included among the possible modes, and I accidentally selected this mode, causing the error.
After filtering the possible modes and creating the ring, the issue was resolved.

 

labmaster.

0 Kudos
Message 6 of 6
(370 Views)