Not enough memory for image aquisition of gigE Camera

[tobetz]

Dear all,


System spects:
Labview 8.5
MAX 4.7.1f8
Vision acquisition Software August 2010
Intel Xenon 3GHz
3GB Ram


I recently installed a gigE Camera (Allied Vision Manta), and after that I run into sever memory problems.
I have a NI network card, running on the NI driver, with Jumbo packets activated as described in the manual.
MAX detects the camera, and I can aquire 8 Bit images on the MAX. Image size is only 780x580, so pretty small.
Already trying to record in MAX with 12bit gives a "Not enough memory" error.
When I use my previous programs, where I allocate memory for data generation, I run into severe problems on the memory size. Once I had this problem on the Labview program, returning to MAX shows that now even a image grap on MAX is not possible anymore. Closing Labview and MAX does not help, only a restart. Even restarting all ni program via the services.msc program did not help.

Interestingly, a snap works fine, only the grabs don't work. Also the system resources do not show that a process is occupying all the memory if Labview was closed.

Somehow, the gigE driver is eating up all my memory (without showing it on the systems recourses...), and does not even free it once NI and MAX is closed.

Unfortunately, I can't even go back to my old programs since they have the same memory problems, even when the Camera is not used...

Is there any way to find where the problem builds up?  Do you have suggestions to trace down what happens? I already updated MAX and Vision aquision, but this seems to have made the problem even worse...

Any suggestion is wellcome,

all the best

[mehdi.afif]

Hello.

Do you mean that the memory leak always occurs first in LabVIEW, and then MAX can't wrok properly anymore after that?

Do you use any VI t free memory in your application?

Best regards

[tobetz]

Dear Afif,

the error is quite confusing, since the more I use the camera, the more problem I have, and after a couple of runs, even basic hardware I/O can not allocate any memory anymore, while the system resources are ok.

In general the error occurs once I read from the camera. But even when the camera is not connected I run into memory problems, but not as severe ones.

I played a lot these days, and when I remove the Intel 1000 Pro card, everything runs smoothly, so I can at least go back to the old analog camera aquisition.

Apparently there are some driver problems. I do not know what happens, but whenever I have the card in the computer Labview runs int 'not enough memory' problems.

I will now buy an PCIe card (the one I had was a PCI), hoping that this will help.

Best,

Timo

[mehdi.afif]

Hi Timo.

This is amazing. Did you test the another PCI network card?

Best regards

[tobetz]

No yet, I figured it out this morning...

I will try the card in another computer to see if it is the card or some problem with the computer itself...

Took me just some time to get the problem...

I will keep the progress posted..

Timo

[mehdi.afif]

This is a link that may help you to troublshoot the issue you have, in the case it's not a hardware issue:

http://zone.ni.com/devzone/cda/tut/p/id/5846#toc2

Best regards

[BlueCheese]

Are you booting the system with the /3GB flag? On 32-bit Windows, this flag makes the kernel only have access to 1GB of virtual memory space. Specific types of memory within that pool are even further constrained. This can cause drivers that need to reserve kernel memory (such as the GigE Vision driver) to fail to allocate the memory they need. You may want to look into upgrading to a 64-bit version of Windows Vista or 7 or else try to reduce the amount of other devices/drivers loaded on the system.

Eric

[tobetz]

Dear Eric,

I tried with and without the /3G flag, same effect...

But I think it would be anyway a good occasion to upgrade to a 64 bit system since sooner or later I am running into performance trouble.

I am continously generating and recording data at 500kHz, while saving images, and in the next step I will need to process the read data and feedback that on the generation. So far I needed to be carefull in writing the preograms, otherwise I run into buffer problems...

I also played with the NI driver for the card and with the Intel driver, and always got problems...

Best,

Timo