LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

build including high number of subVI

Hi,

So the dll problem is for me I have a driver that I access through dll provided with the sdk (Microscope toolBox for Zeiss Axiovert 200M). There is definitely nothing done for labview in this SDK. So This one usually crashes labview itself probably accessing memory in a wrong location. Moreover loading the dll through opening the VI before sending the afxOleInit make this problem worse! There is of course the way to load dll through a piece of C code (LoadLibrary function), nevertheless, I am not fond of writing this. So some part of this dll are under the form of ActiveX (unfortunately non documented) so I open one of these, forcing in this way the afxOleInit() then I load the SubVI in Vi Server and execute it. The dll called by the subVI are loaded only at the time I load dynamically the SubVI (according NI doc); of course if I call the subVi in the usual way, everything is loaded when the top (main) Vi is loaded. I assume that when I close the refnum related to the subVI, dll are unloaded, but I'm not sure and I don't remember any statement about such a point in the doc. There is an exemple in the doc of Labview 7.1.1 about doing that.

Of course I tryied to add my subMain.VI as dynamically loaded Vi in the builder, but then it does not add automatically the SubVIs of SubMain (I can build but executing SubMain fails). I use version 7.1.1 Which version are you using to allows subVis to be loaded? Or is it an option I have to switch to have the proper behaviour?

Thanks in advance for the help

0 Kudos
Message 11 of 11
(329 Views)