Home Community Idea Exchange Additional NI Software Ideas Idea

Additional NI Software Idea Exchange

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Kira_T

INI Variables in VBAI not dependent on Ethernet IP toolkit when migrating to LabVIEW

Submitted by Member on ‎03-11-2012 02:08 PM 1 Comment (1 New)
Status: New

When using the Read/Write Variables to INI File step in VBAI and not selecting the Ethernet option the code that is generated still includes this step and therefore requires the Ethernet IP toolkit to run the code.  I suggest that when the box is uncheck then the generated code not require this toolkit becuase the VIs are going unused.  

View All (2)
1 Comment
Brad
Active Participant
Active Participant
‎03-12-2012 08:42 AM
‎03-12-2012 08:42 AM

Unfortunately it's difficult to selectively exclude dependencies. The only way to do this is either by calling the VI dynamically, so it won't result in broken VIs if one of the dynamically called VIs is never loaded, or using conditional disable structures. The conditional disable structure isn't possible to have it based on a run time checkbox selection, and the dynamic VI calling method is possible, but a fair amount of work. Another option that we are recommending for users that want to have a Vision Builder AI engine do the image analysis and integrate this with a larger LV application is to use the new Vision Builder API that installs a set of VIs to LV for controlling VBAI, loading inspections, running them, and getting results and images back into LV. I'd be interested to hear if this approach doesn't work for your application so we can better understand how people want to integrate VBAI with LV. Some of the advantages of this approach include:

- ability to control VBAI engines running on Remote targets and have your LV app running on windows

- ability to control multiple VBAI engines (local or remote).

- ability to synchronize when an iteration of the VBAI instection runs

- ability to easily change the inspection in the VBAI envirnment without having to migrate your inspection to LV each time you change something in the VBAI inspection.

- Important for you....doesn't require the ethernet/IP toolkit to be installed. Since the inspection is run in a VBAI engine and not generated LV code, you don't need any of the toolkits VBAI has built into it in your LV install.

 

Hope this helps,

Brad

0 Kudos