Message Edited by GerdW on 07-20-2007 10:43 AM
Can any body help me regarding the below issue.
1. In one of the toolkit example, i have used RF RIO instr. library(VST).
2. When ever i am opeing the example, its takes very long time to load the VIs.
3. These driver RF RIO VIs have so many tyedef inside one other, due this typdef inside one other is the problem for long loading time or something different...(Not able to figure out what is the issue)
Can anyone help me regarding this issue.
Thanks in advance.
As hinted in the above posts this is likely an issue with the location of the VI's that your example is calling. If for some reason they are not in the expected location then it will spend time looking for the VI's. You can try to run a force reinstall of the driver you are having issues with. This will help correct any issues with the examples and libraries the examples call. Refer to the following link on how to run a force reinstall.
Also, it may be helpful to open a new forum chain for your issue if this does not help. This forum is very old and few people will see it. By making a new forum post it will gain better visibility.
NI Applications Engineer
I will do the try as you have suggested and update the result in forum soon.
One more question.
Is Non-reentrant, Shared Clone Reentrancy,Preallocated Clone Reentrancy affect the memory consumption by LabVIEW.
Suppose i have a VI having Non-reentrant, Shared Clone Reentrancy,Preallocated Clone Reentrancy and calling a vi in two different loaction in another vi.. which behaviour(Non-reentrant, Shared Clone Reentrancy,Preallocated Clone Reentrancy) will take the more or less LabVIEW memory.
Actually when i am opening my SFP code then due to some large VI the LabVIEW memory is becoming full more about 1GB and after that loading of others vis become slow(as i have understood from the issue).
Can you please help me in the above issue.(I will do the way you have sugggested and update the results soon.)
-First of all, hfar2 suggested you to start new thread instead of posting in some old thread: Start new thread.
-You haven't posted your VI or Project, without which it is difficult to help you: So when you start new thread attach your VI/Project.
- Check Why Do I Get a "Memory is Full" Error in LabVIEW? and the links provided.
- Choosing Which Type of Reentrant Execution to Use