Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

0xBFF69037

 

Hello Ni,

 

We are using the NI-MAX and want to see the image from our USB3 vision Camera..

The image format to be set is YUV422_unpacked..

There is the error

Error 0xBFF69037 - No decoder available for selected pixel format..

 

Regards,

Nick.

0 Kudos
Message 1 of 26
(5,624 Views)
If that is the actual name the camera is describing the pixel format as then it is not following the USB3 Vision specification for how pixel formats are to be named. There is no decoder that IMAQdx has that matches this name. It is likely that this is still a format that IMAQdx can decode, but it has to be using a standard name. You should contact your camera vendor on this issue.
0 Kudos
Message 2 of 26
(5,589 Views)

Can you support the YUV422_unpacked?

 

Regards,

Nick.

0 Kudos
Message 3 of 26
(5,524 Views)
It depends on what that format actually is, because that name does not conform to any names defined by GigE Vision or the Pixel Format Naming Convention used by other standards. I would suspect that it is supported, but you would need to modify the name to match the various applicable standards that the driver knows about. It might be as simple as changing it to "YUV422"...
0 Kudos
Message 4 of 26
(5,519 Views)

YUV422_Unpacked type is defined by the GigE vision.. YUV422_8 :  0x02100032

The pixel format of thecamera is YUV422_8.

 

Regards,

Nick.

0 Kudos
Message 5 of 26
(5,513 Views)

@Nick1976 wrote:

YUV422_Unpacked type is defined by the GigE vision.. YUV422_8 :  0x02100032

The pixel format of thecamera is YUV422_8.

 

Regards,

Nick.


If the camera sets the name of that format to "YUV422_8", it will work then, as this is a supported format.

0 Kudos
Message 6 of 26
(5,507 Views)

Edit a bit to my above post, as I sanity checked the info in our implementation and the specs:

 

The GigE Vision 1.2 spec specifiies the following format that uses the ID you specified:

 

GVSP_PIX_YUV422_YUYV_PACKED -  “YUYVPacked” - 0x02100032

(Note that this has a different component ordering than the standard YUV format names)

 

This was renamed to the "YUV422_8" name in the GEV 2.0 spec that follows the Pixel Format Naming Convention.

 

We do support that format, but I think this name wasn't specified by the GEV spec until later on (1.1) and there were a few non-standard names going around that IMAQdx implemented. The various names IMAQdx matches to this format are:

YUY2

YCbCr422_8

YUV422_YUYV_Packed

YUV422_YUYVPacked

 

We also support these other YUV 422 formats with a different ordering:

YUV422Packed

YCbCr422_8_CbYCrY

 

 

Assuming your format matches the YCbCr422_8 format, which I suspect it does, then you could try changing the name to one of the above formats. I'm opening a request to consider adding aliases for YUYVPacked and YUV422_8 to match as well.

0 Kudos
Message 7 of 26
(5,500 Views)

OK. I'll try to do that...

 

Thanks,

Regards,

Nick.

0 Kudos
Message 8 of 26
(5,485 Views)

 

YUY2

YCbCr422_8

YUV422_YUYV_Packed

YUV422_YUYVPacked

 

I'm searching the same format in the GiGE V2.0, U3V v1.0. the format is YCbCr422_8 . other formats are not existing..

so the format(YCbCr422_8) is changed. but NI-MAX is not working.

 

Regards,

Nick..

0 Kudos
Message 9 of 26
(5,443 Views)

Hi Nick, 

 

Are you saying that you changed the format to YCbCr422_8 and it still isn't working?

If so, what steps did you take to change it? And is NI-MAX still giving the exact same error?

 

Thanks,

Katie

 

 

0 Kudos
Message 10 of 26
(5,419 Views)