ni.com is currently undergoing scheduled maintenance.
Some services may be unavailable at this time. Please contact us for help or try again later.
11-28-2008 05:04 AM
12-09-2008 09:28 AM
Hello,
Did you set continuous buffered acquisition, Continuous=1, bufferCount=21? If so and the behaviour is what you presented, there might be a problem with the transfer from the buffer, therefore try with a larger buffer or give the system enough time to process ( small time delay in a loop that you are using) and see if the number of un-acquisioned images is the same, again, with the dimension of buffer.
Regards,
Mircea
12-09-2008 11:00 AM
Hello!
Yes I have set up parameters as it is described in previous mails. I acquire image on every 13 seconds, so this shouldn't be a problem or do you mean anything elese?
Is the new version of NI Image driver in triger mode still operating the same way that it is looping or is there any progress in new versions?
Regards!
12-10-2008 03:06 AM
What version of IMAQ driver are you using? Are you using the version for IEEE1394 cameras?
Also, write me your e-mail so that we can discuss easier.
Regards,
Mircea
12-10-2008 03:09 AM
I think it is 2.1 version of driver from NI. Regards!
12-10-2008 05:08 AM
Can you please be more explicit and try to cover all the questions I asked?
Mircea
12-10-2008 05:20 AM
Hello!
Ok, now more acurate. I'm working with NI IMAQ 1394 2.0. The problem with this driver in Triger mode was that
while we were waiting for new event the system(VB aplication) was looped and in time betwen two events
on triger program was not responding to user actions!
Regards!
01-19-2009 02:55 AM
No info, can anyone help?
Regards!
03-08-2009 03:51 PM
Hello!
Please, help me on thi issue!
Regards!
Dan
03-10-2009 06:08 AM
Hi danilo,
This is Marton from National Instruments.
My understanding is that:
-You are familiar with Vision and tiggering
-Your application works fine
-The problem is that waiting for trigger hangs your application.
With this you can try the following things:
-Set a relatively low timeout value. If a timeout happens you clear the error and continue
-The other option is more VB than NI related. You could try to have multiple threads, so when clicking Stop you kill the thread waiting for the trigger.
About threads you van find information for exampe here: http://www.freevbcode.com/ShowCode.Asp?ID=4029
In fact the latter one is a bit complicated one so I suggest you use it if you are really interested in going deep into VB.
Regards,
Marton