TriggerSource: Software timeout in VBAI

[test_man]

I am using Vision builder with prosilica GC1350 GigE camera. When I select TriggerSource to Software I get timeout error. It only works when TriggerSource is Freerun.

My vision application is not fast at all. I need to grab one image every 2 minutes. What is the best way to do this so that I don't have alot of network traffic for 1 minute and 59 sec and CPU usuage?

I am using VBAI 3.0.1 with Vision Acq software version 8.5.

Message Edited by test_man on 09-21-2007 02:50 PM

[Brandon M]

test_man,

Can you set up your inspection with an acquisiton step and then a delay step (leaving it in Freerun mode)?

How are you triggering this with software?  What type of signal does the camera expect in Freerun mode?

[test_man]

I can try your first suggestion.

I setup trigger software in my first step of VBAI. Acquire Image (Attributes tab\Trigger source) Here I select software from dropdown menu. I do not use any external trigger. No signal is connected to camera. All I want camera to do is acquire image when I run Acquire Image step and then stop acquiring image after that step. Currently I see network traffic and CPU usage even if when VBAI is idle. (Not acquiring image)

What is software trigger means?

[BlueCheese]

Hi TestMan,

The TriggerSource attribute is a feature the camera exposes. It should have a complementary SoftwareTrigger (possibly a different wording, I'd need to look it up) command attribute that will fire a software trigger when you set it. Unfortunately VBAI currently does not natively support setting command-type attributes, though the IMAQdx API does. I am guessing they should become available at some point. However, in the meantime you could create a simple Call VI step that simply fires the command. There may actually be a knowledgebase item with an example.

Another option might be to change to frame rate really, really slow. This will eliminate a lot of the extra bandwidth being used.

-Eric

[test_man]

Hi BlueCheese,

I am not sure how calling a VI would work because I would be calling VI after my Acquire Image step timeout.

My first step is acquire image and then second step is call VI to trigger. Second step won't execute until first step timeout.

[BlueCheese]

Hi TestMan,

You'd call the VI to fire the trigger command before the Acquire Image step. It should be running a continuous acquisition in the background and so the trigger should work and an image should be available in the next step. I'm not a VBAI expert but I believe this should work.

Hope this helps,

Eric