Ignored Triggers during Image Acquisition using Firewire Camera

[Gambit]

I am currently developing a program to acquire images of ~36 wells over 24 hours in Labview.  I am using a Sony Xcd-V50 camera and triggering it with a falling TTL signal using Trigger mode 0.  I am controlling the triggers using Compumotor Motion Planner Software, such that my robot moves to a well, triggers the camera, waits 0.3 seconds, and then moves to the next.   It then comes back around after a minute and takes another picture of the same well.  These images are saved in a folder together, and are of the same well. 

When I start a run, infuritatingly after a couple hours or about ~160 frames of the movie, an image of the next well is saved into each well's folder as if the camera is ignoring the TTL signal saved to it.  The camera is working pretty slowly, but the IMAQ Write File 2 command could be causing it to slow down.  In response to this, I made a Consumer/Producer loop that puts each image in a Queue so that it will save when it has time.  However, my camera still seems to be missing Triggers. 

Is there a way I can setup my intial buffers so that I am using my memory more efficiently?  Has anyone come across this problem before? 
Attached is my VI.
Thank you in advance for any help!

Namita

Hardware/Software:
Labview 8.2.1/IMAQdx 3.1.2/Firewire 800 Sony XCD-V50/Intel Pentium Core 2 Dual Processor with Vista

[chris.b]

Hi Namita!

Right now it looks like you are only allocating one buffer.  Allocated more than more buffer in a sequence-style architecture may work better for your application.  In the LabVIEW Example Finder, Hardware Input and Output » IMAQdx » Low Level there is a Low-Level Sequence.vi example.  This VI shows how to allocate multiple buffers in one for loop, and write to them in another.  You could implement this in your code in the inner for loop of your producer while loop.  This may be a better way to allocate memory for your application.

[chris.b]

Message Edited by CXB on 08-11-2008 05:56 PM