Error -1074360293 (IMAQdx Timeout) after running acquisition for some time

[shb]

My vision application in LabVIEW does several acquisitions and processings successful but then the acquisition (grab) suddenly fails with a timeout error (-1074360293, IMAQdx: Timeout). The error does not happen when only acquiring the images.

After the error happened no acquisition is possible. Even when LabVIEW is closed MAX returns a timeout error. Only rebooting helps.

some Hardware Details:

3 FireWire Controllers (1394a)

3 Cameras connected to the first two controllers, one to the third (7 cameras total)

Mode for all cameras: 1280 x 960 Mono 8 7.50 fps

The bandwidth for a FireWire controller is sufficient. (Three cameras on one controller run without any problem.)

The memory consume of the application is raising short before or after the error occurs. But I did not find out where exactly.

Before the error happens some minutes until one and half an hour pass.

More details will follow.

Is there a specialist in FireWire or in vision who can help?

Greetings,

shb

[Jan_Wagner]

Hi,

it sounds that the application itself is making the trouble and leading to the timeout because acquiring images is working. Therefore it would be good to have a look at your code. The reason for the timeout can be anything. For example if acquiring and processing the images in one loop could be problematic because the processing may need more time than the acquiring.

Greetings

[BlueCheese]

Are you running on Windows 7? Microsoft had several bugs that could cause some memory leaks and other issues under some specific circumstances. There were several fixes implemented in Service Pack 1 as well as an additional hotfix that I could point you to.

Eric

[andrake]

Same thing happens for me in VBAI. I'm using EVS1464 (Windows 7) and when this timeout occurs, the next thing that will happen is the "Blue Screen of death". Reboot.

[BlueCheese]

---

@niceday wrote:

Hi,

it sounds that the application itself is making the trouble and leading to the timeout because acquiring images is working. Therefore it would be good to have a look at your code. The reason for the timeout can be anything. For example if acquiring and processing the images in one loop could be problematic because the processing may need more time than the acquiring.

Greetings

---

No, application code would not be able to cause a timeout error in this manner.

Eric

[shb]

Hello everybody,

thanks for all this replies. Here are some new details.

I was wrong, the problem also occures when I only aquire the images. Sorry for the wrong information. Testing is difficult when a test run takes from 3 minustes to 1.5 hours.

The program (inclusive image processing) runs without any problems with 3.75 fps. After 14 hours I stopped the run.

Eric,

yes it runs on Windows 7. I will check next if SP1 is installed.

Greetings,

shb

[shb]

Eric,

SP1 is installed.

Is it important which FireWire Controller Driver to use? Windows selected "Texas Instruments OHCI Compliant IEEE 1394 Host Controller" (Original Name in German: "OHCI-Konformer Texas Instruments -1394-Hostcontroller")

[shb]

BlueCheese,

could you elaborate a bit? Why is it no error in the application code? What else could it be?

Greetings,

shb

[shb · Accepted solution]

Changing the driver to this one seems to solve the issue:

"OHCI-compliant 1394 Host controller (legacy)" (in German: "OHCI-konformer 1394-Hostcontroller (alt)")

With this driver the test has run for more than 66 hours without throwing an error.

Some related Articles:

http://www.rme-audio.de/forum/viewtopic.php?id=9827

http://www.myvideoproblems.com/ProblemPages/CannotCapture.htm

[shb]

The test has run for more than 200 hours and did not raise an error. The problem is really solved.

Greetings,

shb