Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

Why do I get Error 0xBFF60493 when snapping a color Image from a AVT Stingray 145C connected to a Compact Vision System?

Solved!
Go to solution

I have a AVT Stingray 145C connected to a NI-1455. I want to acquire images in Format 7 Mode 0 (1388 x 1038). The only Pixel Format that allows me to snap an image from the cameras is “Mono 8”. Any other Pixel Format results in error 0xBFF60493.  The attached PNG (MAX screenshot) shows a successful acquisition of a Mono8 image and the error message when trying to acquire a color image.
I have seen on ni.com/camera that the Compact Vision System is regrettably not mentioned in the list of compatible NI devices.
Is there a chance to support the acquisition of color images?

 

Regards, Guenter

0 Kudos
Message 1 of 8
(7,770 Views)

Hi Guenter,

 

I'm looking at replicating this error and determining the cause. The CVS should certainly support color cameras. Out of curiosity, if you put the Pixel Format to Mono8 (which you said did acquire correctly) but then go to the Bayer tab and force bayer decoding, does it show the same error?

 

Thanks, 

Eric 

 

 

0 Kudos
Message 2 of 8
(7,762 Views)
Hi Eric.
When selecting "Mono 8", the Bayer Patterns "Use Hardware Value" and "None" result in a monochrome acquisition without errors.
Any other Bayer Pattern results in the error mentioned before.
Thanks for your help, Guenter
0 Kudos
Message 3 of 8
(7,758 Views)

Bump.   No news on this channel ?

Regards, Guenter

0 Kudos
Message 4 of 8
(7,711 Views)
Solution
Accepted by topic author GuenterMueller

Hi Guenter,

 

I was able to replicate this here. What is happening is that when you click Snap/Grab in MAX we also display the acquired image on the VGA port on the CVS. For some reason the video driver on the CVS is reporting that the video mode we are trying to switch to is not valid. This seems to be a related to a combination of resolution and color format. To compound the problem, for some reason this is being reported as a fatal error.

 

For the time being, the easy workaround is to go to the remote image options configuration in MAX (Tools->NI Vision->Remote Image Options...) and turn off the option to "Display images on remote monitor." You'll still see images in MAX and you can still use the CVS's VGA port from within LabVIEW and Vision Builder AI (both have you select the video mode instead of trying to choose one automatically like MAX is doing).

 

Sorry you ran into this, but I've opened an issue for this item and hopefully it should be fixed in an upcoming release.

 

Eric 

Message 5 of 8
(7,709 Views)
Great, Eric.  In fact, I did not try any of the options you have mentioned.
I will have a discussion with my colleagues and decide how to go further. We are preparing a quotation for a vision system that will check three products, each with one camera. The CVS is a perfect match for this application's demands.
We intend to connect 3 Stingray 145C to the CVS. Application development might be done in LabVIEW or VBAI - the decision is open. Color images are very welcome as we intend to identify parts by color.
Thanks for your support, Guenter
0 Kudos
Message 6 of 8
(7,693 Views)

Guenter,

 

For any use cases besides clicking Snap/Grab in MAX with the remote display option enabled, there are no problems. A more detailed explanation of the issue is below:

 

The CVS's video memory has always only supported displaying up to 1280x1024 at 24bits. Lower resolutions can be supported at 32-bits. The difference between 32-bit and 24-bits is irrelevant to the user usually, because the extra 8-bits is an unused alpha channel. The difference internally is that Vision Development Module's RGB image format is natively 32-bit so it is usually faster to display 32-bits than re-arranging it into a 24-bit framebuffer (at a cost of more memory).

 

When you Snap/Grab in MAX the default for displaying color images on the VGA monitor was apparently changed to 32-bits, which works fine on newer hardware than the CVS and works on the CVS at resolutions under 1280x1024. So since your camera is high-resolution and color, it chooses the unlucky combination of 1280x1024x32bpp to display which fails on the CVS. The fix will be making MAX smarter about automatically choosing the best resolution based on the hardware it is using and its limitations. 

 

Since you mentioned details about your system, one thing to be careful about is that with 3 of those high-res color Stingrays, the memory demands on the system might be fairly high. You didn't mention whether your cameras are expected to acquire and process sequentially or simultaneously. If you are going to acquire the images simultaneously, I would guess the CVS might not be the best choice due to the memory footprint of those 3 cameras (especially in VBAI) and you might want to look at the EVS instead. If you are using them sequentially, you might be ok if you code in LabVIEW because you have fine-grained control over keeping only one camera configured at a time so they don't all allocate resources simultaneously. The current versions of VBAI tend to keep resources allocated for all cameras in an inspection, so you might run low on memory regardless of how you structure your inspection (unless you use multiple inspections and toggle between them).

 

Eric

Message 7 of 8
(7,681 Views)

Thanks for the valuable and appreciated comments, Eric.

I have not discussed this with my colleagues yet and your comments have reached me in time.

Regards, Guenter

0 Kudos
Message 8 of 8
(7,651 Views)