10-20-2008 06:58 PM
Hi,
I'm trying to get raw images from a Prosilica GigE color camera. If I have the camera set into the Bayer8 mode, everything works fine. My camera also has a Bayer16 mode (although all that is available in IMAQdx is Bayer12). If I chose the Bayer12, or if I explicitly set the camera into Bayer16 using vendor provided software I get an error when I try to call "Configure Acquisition". The error is :
Error -1074370302 occurred at IMAQdx Configure Acquisition.vi
Possible reason(s):
NI-IMAQdx:(hex 0xBFF69012) Attribute value is out of range.
Does anyone have any ideas how to resolve this?
Thanks!
10-20-2008 08:31 PM
10-21-2008
06:03 PM
- last edited on
09-11-2025
12:19 PM
by
Content Cleaner
I looked at the IMAQdx User Manual and it explains that the driver can handle 16-bit bayer raw camera output. Are you sure that the camera does not do 12 bit and take up 2 bytes? The camera information that IMAQdx uses in Measurement and Automation Explorer (MAX) and LabVIEW is stored on the camera so if the 16 bit option is not showing up in MAX that is an indication that the camera cannot do it. But at the same time it should not give you an error.
I have not found any documentation on this error. Does it give you the same error in MAX or just LabVIEW? Also, what do you mean by 'non-color version'?
10-22-2008 02:19 PM
Prosilica’s GE1650, mono16 (mono12 in NI) and GE1650C, bayer16 (bayer12 in NI) pixel formats are supported by the NI ImaqDx driver. Prosilica has used NI’s camera validation utility to verify this. Please review the attached test results.
We did manage to duplicate the reported issue within the NI Measurement and Automation Explorer. The following work around seems to resolve the problem.
1) Configure the camera in 8Bit mode and snap or grab at least one image
2) Set the image format to the desired >8Bit mode and start grab again.
Make sure, not to unconfigure the camera after these steps, every new initialization seems to require these steps.
Hope this helps,
Prosilica support.
10-22-2008 08:12 PM
Thanks Oliver,
That seems to work. I have yet to try it with Labview, but I have found a workaround where I set the attributes individually and then use the low level routines. As I learn more I'll post it here.
Thanks again,
Christy Lancaster
VisionGate