Importing Labview DLL in TCL

[elkapitann]

Hi, I am building an ATE system that requires some integration between TCL scripting and Labview VI functions. What I need help with is getting a vi that has been exported as a shared library (dll) to load properly in TCL. Initially, I got an error in TCL because I didn't have a pkg_init file. I am a little fuzzy on the structure of how this file is used and what all needs to be in it. I built one which is PkgInit.c, and TCL recognizes it, but still can't load the Pkg.dll because it states it is missing a dependant library. Anybody know what I am asking? I believe that I am missing something in this init file.

Any bilinguals out there know much about integrating LabVIEW/TCL?

For backgound roughly on my delimma is that I am using Labview in a very large ATE setup. I have a particular interface that uses TCL, but it loads a package that takes about 12 seconds, then I run some commands in LV and go back to TCL and it takes another 12 seconds. The going back and forth creates an unreasonable delay. The LV commands I initiate between the TCL commands are very simple GPIB commands that I'd like to just put in TCL so I can run one long script, with one package load, then back to LV.

Any help would be greatly appreciated.

[smercurio_fc]

You might want to check to see if the dependent libraries it's complaining about are LabVIEW libraries, such as the advanced analysis library. If one of your VIs is using a function from that library when you compile your application into a DLL you will need to lvanlys.dll library as well. As for moving the GPIB call into TCL you might want to take a look at this:
GPIB-Tcl

Note: I have no experience with this - I just did a search on these discussion forums and then a quick google search when a link in one of the messages was obsolete.