1424 does not pass diagnostics after running program

[CoandaEng]

Hello, we are using the PCI-1424 card with a Dalsa linescan camera, and are having trouble trying to do ring acquisitions with different buffer sizes. The camera either times out or always returns the number of lines that it is first set to, ie; if the original number of lines is 100, and the number of lines is then set to 1000 (and confirmed using imgGetAttribute(DisplaySid, IMG_ATTR_ACQWINDOW_HEIGHT, &nBufSize);).

I've noticed that the 1424 board does not pass 2 of the diagnostic tests in MAX. The details it returns are:

--------

Advanced Control Circuitry failed
Configuration could not be written to when Confwren bit was set. [F1.5]

Timing Circuitry failed
Counter configuration could not be loaded. [T1.0
]

-------

Is this a programming error on my part? I am closing the session and the interface, which in my opinion should be all that is needed to reset the board to the default settings. This does not work, even the snap acquisition in MAX fails.

[JR_A.]

I'm not surprised at the behavior that you are seeing. When the acquisition is started the board is programmed with the acquisition size and when you change that it has to reprogram the board while it is acquiring, so either it will timeout or it just won't do it and you will only see the first size. I'm not sure why the diagnostics are failing but it sounds like you can reboot and that resolves the issue. I would recommend looking into a couple of alternatives. Variable Height Acquistion uses a hardware signal to indicate how many lines should be in an image. If you didn't have a signal you could generate one with a DAQ card or you could programmatically assert
and deassert one of the trigger lines on the 1424 but that would not be the most accurate depending on your line rate. The other alternative would be to set the image size to the largest size and then just crop the images.

Regards,

JR A.
Application Engineer
National Instruments

[CoandaEng]

Thanks for the reply. I noticed that we weren't calling the imgSessionAbort() function, so the camera wasn't stopping the acquisition. Duh.

Now I just need to find out why the other camera can't acquire odd width ROI's... as explained in my other post.