Re: PCDig and JAI CV-L103 colour camera

["M.Stein" <matthias@gom.com>]

On Wed, 26 Apr 2000, Will Lockhart wrote:

> 
> I can't work out from reading the PCDig hardware reference whether the 
> LUTs are even used when the pixel size is greater than 16 bit.
>

I'm not sure, but I think so - manual page 2-6:

	The LUT's support 8-bit pixel data (1-4 taps)...

> Well, this is where things get interesting. It certainly looks as if
> the data is three bytes per pixel, because when I display an RGB
> image, interpreting the bytes as you suggest above, I get an image of
> the correct width, but with incorrect colours. On closer inspection,
> it appears that in the first row the B byte is always zero, on the
> second row the R byte is always zero and on the third row the G byte
> is always zero.
>

No idea at the moment. What happens, if you use the p4b4tn00.exo file.
Perhaps with this the byte order is

	XRGBXRGBXRGB	with X means zero.

> Even more strangely, when I grab a 2048x2048 image, I get three copies 
> of the same image arranged vertically, each one is horizontally offset 
> from the previous one. It almost looks as if the R, G and B planes
> have been separated (the PCDig is capable of doing this), but then
> that doesn't explain why the image width is correct.
>

Yes, but for color seperation, the OCT have to be programmed in another
manner. At the moment a 1:1 transfer between onboard and main memora is
the only supported behavior. Very curious...
 
> More seriously, I'm finding that my machine keeps locking up when I
> grab (or snap) images and I have to reboot it.
>

How often?

>
> Will
> 

						matthias