Code gets stuck in imgSessionStatus

[SripadRam]

Hi Patrick,

The camera configuration file is not being used by my program.

The various acquisition parameters are set using the imgSetAttribute command.

To verify that the various parameters are in fact being properly set, I use the imgGetAttribute command to poll for binning (and other parameter) and write these values to a file. This is done everytime I run the code.

In this way I know for sure that the binning and other parameters are being properly set.

Regards,

Sripad

[Pcorcs]

As it appears that you have been able to verify the software operation through multiple methods; i.e., the software is functioning as it was designed to. I believe we need to turn attention to the camera operation. Where you able to benchmark the fps of the camera on a continuous acquisition to verify its operational speed with the attributes you have defined? 

Are there a separate specifications for triggered operation for exposure than continuous grabbing? 

Cheers, 

[Pcorcs]

Along the same lines, I found a bit more information on triggered hardware control with the IMAQ driver. I believe this document captures the behavior you are seeing with respect to triggers close to the desired frame rate:

Why Am I Not Acquiring Images at the Expected Frame Rate of My Camera?

http://digital.ni.com/public.nsf/allkb/96CB1A25EFF49A3C86256F80005B8EB1?OpenDocument

Cheers,