f



Re: "Total Data Size" property of running VI in LabVIEW 7.1 doesn't work any more?

Just bumped into this problem and did find the answer in this thread dating back to 2005.  So, is there a way to do this with 7.1 or 7.1.1 or not?
0
x9561 (148441)
7/10/2008 8:40:07 PM
comp.lang.labview 35213 articles. 1 followers. vasusachin24 (1) is leader. Post Follow

6 Replies
653 Views

Similar Articles

[PageSpeed] 29

From the 2005 discussion, the resolution was that in LabVIEW 7.1 and later, you cannot read the memory used by a running VI.
 
I just ran both example programs posted in 2005, and no - you still cannot read the Total Data Size of a VI when it is running.  I ran both programs in LabVIEW 8.5.1.  
 
Kevin S.
Applications Engineer
National InstrumentsMessage Edited by Kevin_S on 07-11-2008  04:53 PM
0
x9561 (148441)
7/11/2008 10:10:05 PM
So, how does one debug potential memory leaks or fragmentations?We have about 2700 VIs written by four or five people, part of two or three "top-level" VIs we call over and over again, and  a very small leak, as far as I can tell by the rate of increase in the execution time and program size/memory/handles.  These are all part of an LV executable we call remotely through a crude TCP interface at the rate of 25k calls per month.  We don't even have LV on that machine.There's got to be a way to find out where the problem is that doesn't imply staring at every single of those VIs.  And divide and conquer is a bit hard at this point, given the amount of code and associated instrumentation. 
0
x9561 (148441)
7/11/2008 10:40:09 PM
I will investigate your options and respond shortly.
 
Kevin S.
Applications Engineer
National Instruments
0
x9561 (148441)
7/14/2008 11:40:05 PM
From what I have learned, there is no direct replacement for the Total Data Size property for use with running VIs.  There are two semi-replacements, but neither one has the complete functionality of the former property node.
First, you can gather system information from the command prompt.&nbsp; However, all LabVIEW information is listed under one item.&nbsp; This <a href="http://digital.ni.com/public.nsf/allkb/B5889EB5349FAC478625723E00090265?OpenDocument" target="_blank">article</a> explains more. 
Second, you can use the memory profiler tool in LabVIEW.&nbsp; Tools � Profile � Performance and Memory
Note that you can also continue to use your LabVIEW 6.1 executable that functions as you want.
I hope this helps,Kevin S.Applications EngineerNational Instruments
0
x9561 (148441)
7/17/2008 7:40:08 PM
Thanks for your efforts.&nbsp; A couple of comments/questions. Using cmd or task manager is so 1990s.&nbsp; One can do so much better with Process Explorer, part of Sysinternals, which recently was acquired by Microsoft.&nbsp; Download that utility and use it instead of the standard task manager (which is an option on one of the pull down menus).&nbsp; Select a process, double click on it, and one can even see usage stats per thread, running threads, etc.&nbsp; Still, it is hard to traceback from a given thread to whatever LV is doing.On 7.1 I don't seem to thave Tools-&gt;Profile-&gt;Performance and Memory, I have Tools-&gt;Advance-&gt;Profile VIs..., which may or not be the same.&nbsp; And how does one invoke such a beast from within an executable?As far as going back to 6.1, I'm not sure we could build our code under 6.1, but it may be possible.
0
x9561 (148441)
7/17/2008 8:40:04 PM
Yes, the monitoring utility I was referring to is available at Tools � Advanced � Profile VIs on LabVIEW 7.1.&nbsp; (The path I specified earlier is for later versions of LabVIEW.)&nbsp; Presently, I know of no way to invoke this utility from inside a LabVIEW&nbsp;executable.&nbsp; If I do learn of how to do this, I can update this post.
&nbsp;
Kevin S.
Applications Engineer
National Instruments
&nbsp;
&nbsp;
0
x9561 (148441)
7/18/2008 5:10:05 PM
Reply:

Similar Artilces:

&quot;Save measurement to file&quot;-VI doesn't obey the &quot;Use next avaible file name&quot; setting
I'm using this express VI to store data. In it's properties, there's the "If a file already exists: Use next avaible file name" radio box which does not work. Instead, it appends everything to the one file it created on the first run. My VI has a while-loop with an embedded flat sequence with the writing-VI being in the last frame of the flat sequence. LV 8.5, Linux Hi There. Could You make a screendump of Your VI? I tried using the Express VI on both LV7 Express (Base,Win), and LV8.5 (Base, Win) , and it works perfectly.... &nbsp; I've attached my VI. Currently, the save-VI gets it's file name from some other VIs, but I do that because it doesn't work otherwise. When I clear the "Filename"-input, it starts appending. Messapplikation ganz anders.vi: http://forums.ni.com/attachments/ni/170/313764/1/Messapplikation ganz anders.vi Hi ReBoot I think i've found the Source of Error......When You generate the filepath You use a Concatenate strings with a Constant stating "Files/file" the problem her is the "/". It might be that it should be a Backslash "\"...... Try it.... Best Regards BCL &nbsp; No no, everything's fine as it is. The problem starts when I remove the Filename-input from the Save-VI. Then the Save-VI refuses to take the next avaible file name. However, I'd like to be able to remove all this filename-code and let the Save-VI handle all the file naming. Hi ReBoot, how...

Error Code &quot;1097.....this might corrupted LABVIEW's memory..........&quot; appears after exit the labview and re-start labview
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I have a probelm when I use the "tool/import shared library(.dll)" wizard&nbsp;to generate the&nbsp;API from C. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The API &nbsp;works correctly when I complete the wizard, but after I exit labview and re-start labview to run&nbsp;the API&nbsp;again. The error 1097 code "......this might corrupted LABVIEW's memory.............."appears. &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The only solution now is to re-generate or update the wizard to&nbsp;generate the API. &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;I try to find the answer in &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a href="http://digital.ni.com/public.nsf/allkb/58596F5D41CE8EFB862562AF0074E04C?OpenDocument" target="_blank">http://digital.ni.com/public.nsf/allkb/58596F5D41CE8EFB862562AF0074E04C?OpenDocument</a>&nbsp; &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The paragraph in above article shows ........................... &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; "LabVIEW does not crash until it is closedThe most likely problem is that the DLL function being called has corrupted th...

plug-in &quot;not installed&quot; in my LabVIEW project's &quot;Build Specifications&quot;
I moved my LabVIEW project from one computer to another, now when I click on any item under the project's "Build Specifications", I get an error reading "The plug-in for the selected item is not installed on your system." Does anybody know how to fix this? I have no idea what this "plug-in" is.Attached is a screenshot. plug-in error.PNG: http://forums.ni.com/attachments/ni/170/222664/1/plug-in error.PNG ...

VI &quot;FindInstrumentDrivers.vi&quot; was stopped at node &quot;&quot; at a call to &quot;IDF_WsIdOpen.vi&quot;
This what I get trying to download Instrument Drivers in LabVIEW 8.2. LabVIEW 8.6 doesn't succeed either. any ideas? Could just be an intermittent server problem. Does this happen all the time? At what point does it fail? When you first launch it, after you login? The network traffic indicates that it uses port 3339. Is this being blocked by your firewall? ...

How can I modify the &quot;Type definitions&quot; of &quot;Function Prototype&quot; if I want build a DLL in Labview 8.5.1.?
Hello,We have a library with several VIs (API - Interfaces to our Real Time Target). This VIs we provide to our customer to generate own VIs to control the Real Time Target.Now we want to provide the functionality of this VI-library as DLL to our customer. The problem is, that labview use self definite name of type definitions. Also if I use "strict Type definition".Example:void GetOutputValues(VARIANT *Scale_In, int32_t ModelNr, uint16_t SignalID[], TD1:smileymad: *errorIn, VARIANT *Scale_Out, TD2 *Data, TD1 *errorOut, int32_t len)It is possible to modify "TD1" and "TD2"? I want to give useful names.GreetingsSteffen Hi Steffen, &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Try&nbsp;editing the .h file as follows: CHANGE FROM: typedef struct {&nbsp;LVBoolean status;&nbsp;long code;&nbsp;LStrHandle source;&nbsp;} TD1; CHANGE TO: typedef struct {&nbsp;LVBoolean status;&nbsp;long code;&nbsp;LStrHandle source;&nbsp;} TD1; typedef struct {&nbsp;LVBoolean status;&nbsp;long code;&nbsp;LStrHandle source;&nbsp;} LVErrorCluster; then your GetOutputValues prototype becomes: void GetOutputValues(VARIANT *Scale_In, int32_t ModelNr, uint16_t SignalID[], LVErrorCluster *errorIn, VARIANT *Scale_Out, TD2 *Data, LVErrorCluster *errorOut, int32_t len) If your source-code doesn't refer to "TD1", then&nbsp;you probably won't need to keep the TD1 prototype! Cheers. ...

'&&&&a'="&&&&a."
I need a data step that is equivalent to data _NULL_; file print; put '&&&&&&a=' "&&&&&&a"; run; Yet the number of & is a variable, I need to write a Macro, so far I got only half of the code('&&&&&&a.='), I don't know how to put the other half ("&&&&&&a.") into Macro Thanks. %Macro R(k); data _NULL_; file print; put %do i= 1 %to &k.; '&' %end; 'a=' ; run; %mend; %R(10); ==================================================...

Labview 8.5.1's MathScript window failed running imread with an error &quot;A problem occurred in a subVI call.&quot;
Hi, I am trying to port a Matlab program into a MathScript script.&nbsp; Following is the first few lines of the script:clear;image1=imread('C:\LV_VertAlign\DSC_0104.jpg','jpg');image_double1=im2double(image1);image_gray11=rgb2gray(image_double1);In the first line, imread is supposed to read in a photo taken from a DSLR camera, so I think it's a 32-bit image.&nbsp; And this is the error I got when trying to run this script in the Labview 8.5.1's Mathscript windows:"Error in function imread at line 2.&nbsp; A problem occurred in a subVI call."What is the problem here?&nbsp; and why does it complain about a subVI call?Thanks for any help to point me in the right direction.-Anh Hi Anh, &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; We have documentation on many of the MathScript functions available in LabVIEW.&nbsp; You can look at a document <a href="http://zone.ni.com/reference/en-XX/help/371361D-01/lvtextmath/msfunc_imread/" target="_blank">here</a> that describes how to use the imread function.&nbsp; This is searchable from ni.com by entering the function name.&nbsp; If you read this document you will see the second parameter of the function only accepts the following arguments : 'BMP', 'JPEG', 'PNG'.&nbsp; If you change your line 2 to : image1=imread('C:\LV_VertAlig...

&quot;self reference&quot; vi labview 7
I'm searching in Labview 7.1 for a "this vi" reference node but can't find it. I know that it is possible to create one, i once did it. In higher versions of Labview it is available from the palettes. Do you know a solution for Labview 7.1? Hi vlipje, you don�t need it. You can right click on the property node and select "Select class -&gt; VI Server -&gt; VI -&gt; VI". This should also work. Mike To get the reference to the current VI: File I/O &gt;&gt; File Constants &gt;&gt; Current VI Path wired to Application Control &gt;&gt; Open VI Reference. This reference can be passed to a subVI over a VI Refnum control. For working with the same VI the method of MikeS81 is prefered. Thanks Mike, this is a nice and clean solution, even better than what i had in mind.. Indeed MikeS81 solution was what i was searching for. This one is also an nice solution, thanks ...

&quot;VI was stopped at node &quot; &quot; at a call to &quot;In Port Old 6.x.vi&quot;&quot;
Hi. I am having problems with&nbsp;a VI&nbsp;that was initially developed for LABView 6i. I have upgraded to LABView 8.2 but whenever I run the program in LABView 8.2 I get the error message that my VI was stopped at node&nbsp; " " at a call to "In Port Old 6.x.vi". The VI generally aquires data from a measurement instrument via an RS232 COM port. I have searched the forum and the only reference to this problem mentioned that it can be solved by making "minor modifications" to the polymorphic In Port VI in LABView 8.2 but I have no idea how to do this. &nbsp; I would be most grateful if anyone can help me to do this. I am a newbie to LABView programming so I would require as much detail as possible. Thanks. &nbsp; tronix Hello, &nbsp; Have you followed the guidelines found on this document? &nbsp; <a href="http://digital.ni.com/public.nsf/allkb/39129B46944215B686257069006CEC4E?OpenDocument" target="_blank">http://digital.ni.com/public.nsf/allkb/39129B46944215B686257069006CEC4E?OpenDocument</a> &nbsp; Contains information on how to proceed and how you can change the VI's needed to new ones. &nbsp; Hopes this helps! Hello. Thanks for your response. I did see the link. Part of the document says: tronix wrote: Hi. I am having problems with&nbsp;a VI&nbsp;that was initially developed for LABView 6i. I have upgraded to LABView 8.2 but whenever I run the program in L...

Re: VisualBasic &quot;Show &amp; Hide&quot; equivalents in LabView
Hi, I want to show/hide the Labview Help programatically. (Just on the click on single button) How it can be done? Do i have to use event structure on Ctrl + H buttons???:smileyindifferent: Please suggest some solution. Thanks There's a help palette with a primitive called Control Help Window, which should do what you want (assuming you want the context help). <img src="http://forums.ni.com/attachments/ni/170/336539/1/untitled5.PNG"> Message Edited by mathan on 07-01-2008 07:07 AM untitled5.PNG: http://forums.ni.com/attachments/ni/170/336539/1/untitled5.PNG Hi Tst, Thanks. i know that there is a Context Help Window where you can see the help for all the functions or Labview help. i want to show/hide this window programatically. Is it possible? Thanks. Thanks Mathan, This is what i wanted. Thanks. Hi Dev, the first of those functions ("context help window") is what you need - as you can read in the context help window for that function!!!:smileyvery-happy: Yes, i got it. thanks . ...

Adding an &quot;IMAQ Image.ctl&quot; to the &quot;Display State.ctl&quot; of an XControl prevents LabVIEW from creating a probe of &quot;Display State.ctl&quot;
I am working on an extended IMAQ Display control using LabVIEWs XControl capabilities. &nbsp; I need a copy of the original image passed to add some overlays which must not affect the original image. To achieve this I am creating a backup image in the "Init.vi" and deleting it in the "Uninit.vi". I am storing the reference&nbsp;of this image&nbsp;in the "Display State.ctl" which is part of every XControl. &nbsp; As soon as I am adding an "IMAQ Image.ctl" to the Display State cluster, it is no longer possible to generate a probe of the Display State cluster for debugging purposses. I am always getting the message: "Failed to load or create probe." Deleting the "IMAQ Image.ctl" from the cluster makes the probe working again. &nbsp; Is it a bug or am I doing something wrong? &nbsp; I am working with LabVIEW 8.5 and Vision 8.5. &nbsp; Regards &nbsp; Ingo Bartsch Hello Mr. Bartsch, is it possible for you to post a small example to reproduce the behaviour? It would be helpful to get a description in which way you use the typedef files. I found a example/knowledge base where some informations were included to XControl and LV but not with Vision. <a href="http://digital.ni.com/public.nsf/allkb/1DC1ADD2A136DA298625712C00635758?OpenDocument" target="_blank">http://digital.ni.com/public.nsf/allkb/1DC1ADD2A136DA298625712C00635758?OpenDocument</a> Best wishes Ja...

how to connect &quot;IMAQ Get Buffer.vi&quot; output terminal of &quot;Image Out&quot; to the input terminal of &quot;Image&quot; of &quot;IMAQ ColorImageToArray.vi&quot;
Hi, Thanks a lot for helping me till this stage.I am again stuck up with some problem.Please help me this time also. Actually i am making changes in already existingblock diagram and also i am new to this labview programming.And also time is very crucial. So i want to know if there is any way to connect the output of Image out terminal of IMAQ Get Buffer.vi to the input terminal of Image of IMAQ ColorImageToArray.vi. In the actual block diagram the output of Image out terminal of IMAQ GetBuffer.vi is connected to the input terminal of Image of IMAQ ImageToArray.vi. I want to change this becos i want to take RGB image as input and seperate R, G, B components. Please explain in terms of bloack diagram. ...

Why doesn't &quot;Compare Hierarchies&quot; work?
I have two versions of a LabView project that I wish to compare.&nbsp; I know that I made some changes to one of the versions (from the other) and I want to do the compare because I've forgotten what changes I made and I wanted to document them.&nbsp; However, when I do the compare (as I've done dozens of times with another project) the top VI shows up with a slashed circle icon next to it and the message "VIs have not been compared."&nbsp; And, below it, all the remaining VIs in the hierarchy of the VI in memory are shown as "added" VIs with a "plus" icon next to them.&nbsp; (Note, when I do it with another project, I see the dialog showing the hierarchy being loaded into memor when I select the second Hierarchy.&nbsp; I don't see this with my problem project--except when I accidentally selected a version of the working project by accident as my second hierarchy. &nbsp; My problem project&nbsp;is a Labview project that I have "inherited" from someone else.&nbsp; It was originally created in LabView 5 or 6.&nbsp; I have brought it up in&nbsp;8.2 then&nbsp;created a LabView project (.lvproj) and created 8.2 libraries (.lvlib) files.&nbsp; (This is slightly different from the other project that works, the ".llb" files were not "converted" to ".lvlib" files in the project that will compare.&nbsp; Somehow that seems to be the issue.)&nbsp; The ...

&quot;function icon doesn't work&quot;
I using the Labview Database Connectivity Toolset with Labview 8.5 Developer Suite.&nbsp; When I click to add the "Database Variant to Data" function to my function window, my cursor doesn't turn into the hand symbol and Windows (XP) simply dings.&nbsp; With context help on, it shows ??? for a title when I hold my cursor over the "Database Variant to Data" icon.&nbsp; I tried reinstalling my toolsets but that didn't fix it.&nbsp; Is there some way to fix this in my functions menu?&nbsp; For now, I found this function in one of the examples and was able to copy it into my VI.&nbsp; Hi mysticfree, very nice phrase: "Windows simply dings" :smileyvery-happy:Sorry, no help to offer... Do you have more than 1 version of LabView on that machine? You could try uninstalling the toolkit and then reinstalling. Hi mysticfree, This is a known issue. You can find the details and the fix <a href="http://digital.ni.com/public.nsf/allkb/CEE92D0FB321402586257193005DF125?OpenDocument" target="_blank">here</a>. Hope this helps! Hi GerdW!&nbsp; I was going to say "windows simply dings and I silently curse" but I thought that might be redundant ....&nbsp; :smileyvery-happy: Hi GovBob, I did a reinstall but that didn't help.&nbsp; :smileysad: Thanks, Hillary, for that link.&nbsp; After I replaced dir.mnu as directed, all is well!&nbsp; Thank you so very much!! ...

&quot;re-entrant&quot; &quot;file I/O&quot; &quot;QSM_State Machines&quot;
&nbsp; &nbsp; I have trouble with writing (appending) to text file in a QSM that is in an "occurence mode" of operation whereby the queue waits for outside engueue to go ahead and do a task. The task is simply to write to a file a line of text. &nbsp; Outside producers give the queue its go ahead and data is sent along etc... &nbsp; WHat I am seeing in the logging functions are multiple errors (Error 1) Somehow Labview&nbsp;is not noticing that the reference is valid or it is invalidating the reference. &nbsp; Q is Should I just let the QSM loop to keep it alive and would that work? &nbsp; What is the rule concerning queue waiting for an event? Does the VI get flagged as idle and is that why the ref appears to be dropped?&nbsp; THere is no reason I can think of for the ref to be dropped. It is opened in the init frame then kept in a shift register. and available at each iteration in the QSM. &nbsp; The example works in a simple loop but not a loop that is waiting on an occurence.&nbsp; Why? &nbsp; The only work around I can manage is to use the path and open the reference when it is not valid which feels kind of&nbsp; silly if you get my drift &nbsp; Anyone seen this before? &nbsp; Thank You &nbsp; &nbsp; &nbsp; ...

How do I disable the Dialog Box Pop Up when using the &quot;Open/Create/Replace File&quot; VI?
I would simply like to write data in real-time to a file without the operator being prompted by a Dialog Box. Please see attachment for the code I used. &nbsp; Thank you! LabVIEW_Write To File Code.doc: http://forums.ni.com/attachments/ni/170/243833/1/LabVIEW_Write To File Code.doc Try putting the entire path including the file name (and not just the folder) as a path constant (and not use the string to path function) to the file path input. &nbsp; <img src="http://forums.ni.com/attachments/ni/170/243916/1/Open_Create_Replace.PNG"> Message Edited by Dennis Knutson on 04-25-2007 01:37 PM Open_Create_Replace.PNG: http://forums.ni.com/attachments/ni/170/243916/1/Open_Create_Replace.PNG Dennis Knutson wrote: Try putting the entire path including the file name (and not just the folder) as a path constant (and not use the string to path function) to the file path input. Dennis, Good lesson for me ! :smileyhappy: I m also not familiar with this thing of putting the entire path of a file, even if I wire a False to the Advisory Dialog inout. I thought that it is the maximum feasibility in LV. You opened my eyes &amp; brain. :smileywink: ...

what the difference between &quot;Wait Until Next ms Multiple&quot; and &quot;wait&quot; vi's ?
Hi all. &nbsp; 1) What the difference between "Wait Until Next ms Multiple" and&nbsp; "wait"&nbsp;&nbsp; vi's ? 2) If i put thos vi's inside state machine, for example, inside state number 3, when the program reach to this state, the delay will ganerate&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; before or after the execution of other component in this state&nbsp; ? &nbsp; &nbsp; thanks :) Both will start in parallel to all the other nodes in the same frame but they still have different finctionality.&nbsp;You cannot guarantee&nbsp;what starts first.&nbsp;The main differences show up if you have other slow tasks in other frames of the same state or the slow task starts before the wait. &nbsp; Wait next ms multiple: This is only useful in a loop, because it tries to keep the same time frequency, irrespective of how long other nodes take. The first call might be way off. &nbsp; Analogy: Do something always 10 minutes after the hour. (If you start working on the hour, the first wait will only take 10 minutes, but then all further tasks will be spaced exactly one hour.) &nbsp; Wait(ms) Wait a give amount of time before continuing. &nbsp; Analogy: do something, take a 1 hour break, do something, take another 1 hour break, etc. The repetition rate will somewhat depend on the lenght it takes to do the other tasks. &nbsp; Here's a nice write-up by NI: &nbsp; <a href="htt...

Is &quot;write to digital line.vi&quot; compatible in LabVIEW 7.0
I developed a LabVIEW program to change the logic state of a digital line using the "write to digital line.vi". This was first done in labVIEW 6.1. The version was later upgraded to LabVIEW 7.0 later and the VI doesn't seem to perform the function correctly, meaning when I tried to change the line state from "low" to "high", it doesn't seem to be doing anything. Is this because of compatibility issue of "write to digital line.vi" with LabVIEW 7.0? Thanks! There should be no problem using the traditional DAQ driver in 7.0. After installing 7.0, did you reinstall traditional DAQ? Does the traditional DAQ driver show up in MAX? Do you get any error when you run the VI? Yes, the traditonal NI-DAQ still shows up in MAX under software as well as the Devices and interfaces (because I have traditional NI-DAQ (legacy) devices). Can I have both the traditional NI-DAQ and the NI-DAQmx on my computer? When we first ran it, it did come up with a error message. But after we installed the legacy NI-DAQ (I guessed it is the traditional Ni-DAQ), the error goes away. Could you read anything from it? Thanks a lot! The two can coexist though it has been quite a while since I've had to do it. The thing to make sure is that if the card is supported by both drivers, that the driver you want to use is the active one. You can check and reset it in MAX. ...

error 7 in &quot;application builder&quot; for LabVIEW 8.5.1
Hello, &nbsp; I am getting an error while building a project for making EXE file. &nbsp; below is the displayed message. &nbsp; Error 7 occurred at Copy in New VILibrary.vi-&gt;AB_Dest_LLB.lvclass:Create_Destination.vi-&gt;AB_Build.lvclassLCreate_Destinations.vi -&gt;AB_Build.lvclasss:Build.vi-&gt;AB_EXE.lvclass:Build.vi-&gt;AB_Engine_BUild.vi-&gt;AB_Build_Invoke.vi-&gt;A B_Build_Invoke.vi.ProxyCaller &nbsp; ============================NI-488: Non-existent GPIB interface. C:\ProgramFile\NationalInstruments \LabVIEW8.5\vi.lib\Utility\libraryn.bin &nbsp; thanks, &nbsp; You can force LabVIEW to recompile the entire VI hierarchy in your project with CTRL+SHIFT+Run Button. Have you imported some old VI's into the project?&nbsp; From a previous version? Did you add files since creating the build parameters?&nbsp; You may want to delete the build parameters and create a new one. RayRMessage Edited by JoeLabView on 07-02-2008 08:35 AM Also, check the path of the reported missing file and make sure it really isn't missing. Thanks George...&nbsp; :) Especially if code moved around (Copy / Paste to another folder / backup, etc..) Thanks Ray and George, I was using VIs of 7.1 version for 8.5 builder. I deleted the previous build parameters and created a new one, it was sucessful. - sriveni &nbsp; Glad it worked.. :) ...

&quot;This VI or function runs normally only if no error occurred before this VI or function runs&quot; any good work arounds?
I have a couple of applications where data is collected and files are saved several times during it's operation.&nbsp;&nbsp; I would like to just simply collect any errors and display them at the end of the run,&nbsp;but both Visa and File read write vis will not allow that.&nbsp; If the error cluster isn't wired then an error message will pop up and operation stop until somebody clicks on continue.&nbsp;&nbsp; That doesn't work well for my operation either since it's mostly running without any attendence.&nbsp; &nbsp; In case of a Visa operation I input a dummy error cluster and collect a dummy error cluster at the output.&nbsp; Any error messages created by the Visa vis is lost.&nbsp; I guess that's not so bad, but sure is a pain.&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; ...

Re: Help, rather stuck: Should it take 22 ms to (via Visa) write &quot;ISET 2&quot; then &quot;ISET 0&quot; to an instrument? (to a Kikusui electronic load if you're curious)
Dennis hi: I hope you are able to gime a hand with KIKUSUI PLZ-30F electronic load. 1. I'm talking to the instrument via GPIB and it communicates. 2. It doesn't respond on a settings commands - change from CC to CR mode, etc. 3. There are 3 modules in a frame - one master and two slaves. 4. I'm suspicious I'm missing something, and... this company does not have techsupport...??? 5. Their drivers have entirely different format from SCPI and I have no use to them. 6. There is an IVI driver - but I didn't try it yet. &nbsp; Best, Oleg Finodeyev ...

'Serial Port Init.vi' problems between versions 6.1 &amp; 7.1 of Labview
Hi there, &nbsp; I created a Card Test Program using Labview 6.1 in 2003, it now requires changes to be carried out. &nbsp; My company is now using Labview 7.1, however, once I have created an executable from the vi's and attempt to run it on the target system&nbsp;I get an Error 37 with the 485 card, labview device not found. Yet if the changes are made within Labview 6.1 it runs fine (but as we are now using labview 7.1 it is preffered that I use that. &nbsp; I presume this is an issue with the 'Serial Port Init.vi' that I am using, everything else works fine, except any of the vi's that are used to initialise, communicate with and close a 485 port. Is there any differences between the ?Serial Port Init.vi? that comes with Labview 6.1 and that which comes with Labview 7.1. Any help gratefully appreciated. &nbsp; Regards &nbsp; Simon Snoddy It is the old serial functions that I am using. The data is being sent directly from an FPGA, I therefore have to use the 'Type Cast' function to convert the string into binary so that I can manipulate it, but at the moment, using Labview 7.1 I can't even initialise the 485 ports. Any help would be gratefully appreciated. Cheers Simon Hello Simon, The issue that you are seeing is due to the fact that serial communications methods in LabVIEW were changed between LabVIEW 6.1 and LabVIEW 7.x. The serial compatibility vi's that you were using were modified to make use of VIS...

Where can I get example code &quot;Row Col to Range format.vi&quot; for LabVIEW 5.1?
In the example code section, there is a VI called Row Col to Range format.vi, but it is for LabVIEW version 8 and will not work with Version 5.1 that I have.&nbsp; Somehow, we have misplaced this VI and I cannot change the existing .EXE that uses this VI without it. Thanks for your help. Hi tater Here's a copy of Row Col to Range Format.vi in LabVIEW 5.1.&nbsp; (I changed the name to reflect that it is in this specific version.&nbsp; You will need to change it back.) Best of luck,Kevin S.Applications EngineerNational Instruments Row Col To Range Format, v5-1.vi: http://forums.ni.com/attachments/ni/170/347310/1/Row Col To Range Format, v5-1.vi ...

Can't &quot;show terminal&quot; in tcp i/o properties in VBAI 3.5.1
I'm trying to debug my tcp communication but am not able to see the terminal. The "show terminal" button is grayed out in the tcp I/O properties. I have installed the 3.5.1. update. Anybody know why this would be? Dear BAM787, Is the "TCP Communication Terminal" also grayed out in the VBAI Tools menu? Are other items in the tools menu grayed out?I would try repairing VBAI from the Windows Add/Remove Programs menu. This should find any missing comonents and install them. Please let me know if this helps!~Nate ...

Web resources about - Re: &quot;Total Data Size&quot; property of running VI in LabVIEW 7.1 doesn't work any more? - comp.lang.labview

Resources last updated: 3/19/2016 8:57:06 AM