IMAQ property node

[Rob_Ward]

taroK,

If possible, can you please change the bitstream in your camera file.  You should try changing the following line: AcquisionBitstream(.dat) to any one of these;

CL_TC1T64_RGB-Class07.dat - Ten, 12, 14, and 16-bits per color plane RGB tap configurations. Only one tap.
CL_TC10T8_1X10-Class07.dat - Eight bit, with ten zones in X, and one tap per zone, such as the Basler A504k (most common for ten-tap tap configurations)
CL_TC10T8_1X10_Alt1-Class07.dat - Eight bit, with ten zones in X, and one tap per zone, but with the Vosskuehler bit mapping, such as the Vosskuehler CMC-1300 or CMC-4000, or Allied Bonito CL-400B/C (very rare)
CL_TCxT8_1Xx-Class07.dat - Eight bit, with one zone in X
CL_TCxT16_1Xx-Class07.dat - Ten, 12, 14, and 16-bit, with one zone in X
CL_TCxT8_xX1-Class07.dat - Eight bit, with multiple zones in X, but only one tap per zone
CL_TCxT16_xX1-Class07.dat - Ten, 12, 14, and 16-bit, with multiple zones in X, but only one tap per zone
CL_TCxT8_2XxE-Class07.dat - Eight bit, with two zones in X, one or two taps per zone, and a line-ends extraction direction in X.
CL_TCxT16_2XxE-Class07.dat - Ten, 12, 14, and 16-bit, with two zones in X, one or two taps per zone, and a line-ends extraction direction in X.
CL_TCxT8_1X1_xYx-Class07.dat - Eight bit, with one zone in X, one tap per zone in X, and either multiple taps in Y, or multiple zones in Y.
CL_TCxT8_xXE-Class07.dat - Eight bit, with an even number of zones in X, one tap per zone, and a line-ends extraction direction in X
CL_TCxTx_Base-Class07.dat - Supports all Base tap configurations (24 data bits, one Camera Link cable)
T_TCxT8_1Xx-Class07.dat - Eight bit, with one zone in X. Uses the internal TestImage instead of the Camera Link pins
T_TCxT16_1Xx-Class07.dat - Ten, 12, 14, and 16-bit, with one zone in X. Uses the internal TestImage instead of the Camera Link pins.

This might expose different behaviors than the hang. There is a long list of .dat files in NI Camera File Generator.ini available which you can also try.  Failing that, could you please switch DVALMode(1) to DVALMode(0) and give this a try also.  Please let me know how it goes, and if you have made any progress on your end.

I know that camera files have to be quite specific so it may be quite tedious but this is the most likely source of the problems you are having.

Regards,

[taroK]

Sorry for the late reply. I finally tried all of the dat files, and they did not make any diffenrence.. DVALMode did not change anything, either. I am going to ask the camera company about the camera file.

[taroK]

I am sorry, but I realized I changed a wrong line in the camera file. I changed the settings for ni-1429, not ni-1433.

Then, I just tried to change the AcquisitionBitstream setting from Class07.dat to others, but MAX complained that it did not find them..

[taroK]

The camera company suggested this may have something to do with the driver of the frame grabber. I imagine the program runs 32 bit even though I am using 64-bit Labview?? I installed the latest IMAQ and it supports 64-bit Windows 7, but the whole issue does suggest some memory problem.

[Rob_Ward]

Dear taroK,

That information is very helpful.  You should be using LabVIEW 64-bit, because it has a maximum memory limit of 192GB, whereas 32-bit has only 4GB ( http://www.ni.com/white-paper/10339/en ).  The ActiveX controls are configured in 32-bit, so generally it is advisable to use 32-bit unless you are getting through insane amounts of data - which you are doing.

The IMAQ is a native 64-bit driver precisely for the kind of application you are performing, and the framegrabber has a 512MB FIFO with 850MB/s bandwidth and you are generating 669.6MB/s through your camera.  Personally; I thought all the memory calculations worked out, which was why I thought it is something else such as the camera file settings.  But the fact that your program slows down when toy change from 1 second to 6 seconds of acquisition definitely points to it being a memory issue.

Was there an option when you installed the IMAQ drivers/ NI Vision of the option 32- or 64-bit?

Regards,