06-11-2004 07:21 AM
06-12-2004 05:52 PM
Hello,
These are DSC's system VIs which will be always running. You (normally) won't be able to stop them (unless you stop DSC).
However, you should not be including these VIs in your build, in the first place. DSC executables still require the run-time system (which is different from LabVIEW's run-time engine). This DSC run-time system will install all the required VIs and files, etc. So, you should not include any of the DSC specific VIs. See the following for an example of creating executable for a DSC application:
http://zone.ni.com/devzone/devzoneweb.nsf/Opendoc?openagent&26C7582A8BA3B21386256A7A0069313E
Hope this helps,
Khalid
06-14-2004 11:46 AM
09-20-2006 01:02 PM
Hi Kristi:
I am not using the DSC module, but have the same problem. I am unable to build an application because several vis are in memory. These VIs are not running. How do I close them? How do I find them? I looked at the Hierarchy Window and found those VIs. But how do I get them out of the memory? Any help is appreciated. Thanks in advance.
KM
09-21-2006 05:12 PM
KM hello.
What version of LabVIEW are you using? What are some of the names of the VIs that are "in memory?" Are they LabVIEW VIs or your own subVIs? Do you dynamically call VIs in your application.
Try ending the LabVIEW process running and re-starting LabVIEW, running only the top-level VI (if version is less than 8.0) or open just the project (if version is 8.0 and above) and building the executable.
EfosaO.
NIAE
09-22-2006 09:06 AM
Hi Efosa,
I am using LV 7.0 and I am not calling any vis dynamically. have several subVIs in the application that run in the background and feed data back to the top level VI. I have closed the LV process and also tried with the top level VI running.
The VIs that are in memory include: 1D Array to String__ogtk.vi,Untitled 2,DialogType.ctl,Configure.vi,Open File+.vi,Find First Error.vi,Close File+.vi,Read File+ (string).vi,whitespace.ctl,Trim Whitespace.vi,Clear Errors.vi,eventvkey.ctl,ErrWarn.ctl,Search and Replace Pattern.vi,Find Tag.vi,Set Bold Text.vi,Format Message String.vi,Convert property node font to graphics font.vi,Get Text Rect.vi,Longest Line Length in Pixels.vi,Three Button Dialog CORE.vi,Three Button Dialog.vi,GetHelpDir.vi,BuildHelpPath.vi,DialogTypeEnum.ctl,Details Display Dialog.vi,Not Found Dialog.vi,TagReturnType.ctl,Check Special Tags.vi,Error Code Database.vi,General Error Handler CORE.vi,General Error Handler.vi,Read Characters From File.vi,Generate List.vi
I'd appreciate any suggestions. Thank you in advance.
km
09-25-2006 02:31 PM
Hi Km,
Ary any of your top level VIs set to run when opened? Perhaps you uncheck this selection so that you could build the exe.
Regards,
Steve B.
09-26-2006 11:47 AM
Hi Steve:
I am not sure if I understand your question. How do i check if my top level vis are set to run? I went to the subvi node set up option, and i don't see the option similar to "not setting the VIs to run" . All the boxes are unchecked though. Am I missing something?
Thank you.
Regards,
KM
09-27-2006 10:47 AM
KM,
Let me clarify what I was thinking a little better. When you have a VI opened go to File > VI Properties and then chose Excution in the Category drop down menu. On the left hand side there is a Run When Opened selection box. If its possible for you to post your application on this site I would like to see if I was able to build an exe as well.
regards,
Steve B.
09-27-2006 11:09 AM
Hi steve,
thanks for the response. I checked out the Execution property and my the Run When Opened box is unchecked. I will post my VI as soon as I am done with it for you to try. Thanks again
km