09-19-2008 10:52 PM
Hello,
I'm a newbie of NI products and evaluating which to choose Vision Builder or Vision Assistant.
As I don't have enough time to learn LabView, I'd like to call the vision components from my C++
application at the moment.
1) If the script file of Vision Assistant is possible to load and execute from my application
(i.e. the change of a script is reflected without rebuild of my application), I'd like to choose
Vision Assistant(Vision Development Module).
Is it possible?
2) My application will process finite number of images (e.g. 100 frames) and the processing
time of a frame may be longer than the trigger period. But I don't want to wait until the last frame's
transfer to start the first frame's inspection.
Is Vision Builder possible to implement smartly in this case?
Best regards,
09-22-2008 10:49 AM
09-22-2008 08:08 PM
Hello Patrick,
Thank you for the code 🙂
I thought Vision Builder is possible to access via ActiveX, but interface is so limited.
Vision Builder seems easy to reflect changes of algorithm, but seems difficult (impossible?)
to control threads and should need to call custom VI for my application.
So I think I should use Vision Assistant.
I wish Vision Assistant were possible to generate DLL instead of C codes...
09-23-2008 10:03 AM
Unfortunately I don't know much about ActiveX and Vision Builder. Not something I've tried yet.
I don't see a way to create a .dll directly from Vision Assistant. But I wonder if you used Vision Assitant to create LabVIEW code, if you couldn't then save that code in .dll you could call from your application.
I've found some documentation about creating .dll's here:
http://digital.ni.com/public.nsf/allkb/70995EC2CA1B523386256DD4004F3DE6
http://zone.ni.com/devzone/cda/tut/p/id/3927
I'm sure there's much more information that that. But a C programmer such as yourself would probably have a better idea of what to search for.
Good luck with your project.
09-24-2008 01:36 AM
Dear Patrick,
It's a really good news to me.
Thank you!