Problem while using Hamamatsu c9100-13 camera with ni-1428 frame grabber.

[Feldmarshall]

Hi

I'm building a system which is going to use Hamamatsu Image-M c9100-13 camera with NI-1428 frame grabber and I run into problem. When I installed everything and run MAX, the camera was working, but image was shifted and shift was slowly changing with every frame. It looked like data was one line longer and with every next frame shift changed one line, resulting in bottom of the picture from camera moving up in preview window (quite like desynchronized movie in cinema). It works good with Hamamatsu framegraber and software though.

I'm using .icd file from NI, MAX 4.6.2, and NI-IMAQ 4.4.

Incidentally - if anyone had list of serial commands for this camera, I would appreciate if he would share with me where to get them - I wrote and called Hamamatsu, but there is no answer from them...

Thx

[BruceAmmons]

I have had similar problems in the past.  I am pretty sure I fixed them by reducing the image height by just a pixel or two in MAX.

Bruce

[wojciechsommer]

Feldmarshall,

Did you check recommended by Bruce reducing the image height by one of two pixels?

Thanks,

Wojciech.

[Feldmarshall]

Hi

I tried changing image height, and problem remained as it was.

But when I looked thru the file I noticed option ''NonContLineEnables". When I changed it from (No) to (Yes) image stopped floating.

Now I wish I knew what I've changed ;).

[kellam]

Hi Feldmarshall,

The ''NonContLineEnables" tells the frame grabber that the line enable (aka LVAL) signal stops strobing when the frame enable (aka FVAL) is deasserted.  Most area-scan cameras run LVAL continuously, and most NI framegrabbers were built assuming that there would be a continuous LVAL signal.  The frame grabber counts the LVAL pulses to acquire from the correct ROI.  When the LVAL isn't continuous, the frame grabber ends up counting wrong.  When we started seeing cameras with non-continuous LVALs, we adjusted our driver to accommodate.  Unfortunately, just using the change would make us count wrong for framegrabbers with continuous LVALs.  That's why the camera file has the option - we need to be told which way to count.

I hope that somewhat explains the setting you changed.

-Jeff