f



LabVIEW 8.5.1 "The build was unsuccessful"

When attempting to build my executable in LabVIEW 8.5.1 I get the following dialog:
 
<img src="http://forums.ni.com/attachments/ni/170/338657/1/Build%20Errors.PNG"> 
&nbsp;
I've tried recreating my build specification, reinstalling LabVIEW, commenting out sections of my code and nothing seems to help.&nbsp; Has anyone encountered this before?&nbsp; Any ideas NI?Message Edited by FlamingYawn on 07-08-2008  11:24 AM


Build Errors.PNG:
http://forums.ni.com/attachments/ni/170/338657/1/Build Errors.PNG
0
x9561 (148440)
7/8/2008 4:40:07 PM
comp.lang.labview 35213 articles. 1 followers. vasusachin24 (1) is leader. Post Follow

12 Replies
859 Views

Similar Articles

[PageSpeed] 46

Hi,
&nbsp;
Are you building a .exe application? In that case, please verify that all your startup and always included VIs exist in the same path and have been properly compiled. You can try Tolls&lt;VI Analyzer&lt; Mass Compile. Also are you using DSC or shared variables in your code?
&nbsp;
Ipshita C.
0
x9561 (148440)
7/9/2008 6:40:08 PM
Hi Ipshita,
&nbsp;
Thanks for responding.&nbsp; 
&nbsp;
Yes, this is "a .exe application."&nbsp; 
&nbsp;
My startup path is correct, and I tried building with all my "always included" VIs removed.&nbsp; Same error.
&nbsp;
I've mass compiled several times.
&nbsp;
I'm not using DSC or shared variables.
&nbsp;
I'm able to build the executable on another computer with the exact same project and code (we use source code control), so something must be different about my environment or setup.
&nbsp;
Thanks,
&nbsp;
Robert
0
x9561 (148440)
7/9/2008 7:10:05 PM
I have seen this error before, but when I was using 8.20 and the Touch Panel module (compliling a CE .exe).&nbsp; The build error tells you absolutely nothing about how to resolve it :smileymad:.&nbsp; However, after some trial and error I found the problem (in my case) was that labview was having trouble overwriting the .exe from a previous build.&nbsp; That is, the target destination for the build already had a .exe from a previous build and it would not replace it.
If you have any files in the target destination for the build, try deleting them and then run the build.&nbsp; Typically you don't have to do this.&nbsp; Usually can do a rebuild into the same directory and LV will replace the old build.&nbsp;Message Edited by StevenA on 07-09-2008  01:54 PM
0
x9561 (148440)
7/9/2008 8:10:12 PM
Thanks for responding, Steven.
&nbsp;
I've seen the problem you mention as well.&nbsp; Especially when dealing with source code control.&nbsp; However that's not the problem in this case.&nbsp; I cleaned out the destination directory to make sure that wasn't the problem.
&nbsp;
Thanks,
&nbsp;
Robert
0
x9561 (148440)
7/9/2008 8:40:08 PM
I wonder if it could still be related if for some reason LV cannot get the folder access rights it needs.&nbsp;
0
x9561 (148440)
7/9/2008 9:40:07 PM
When I diagram disable all of my code, the executable builds fine.&nbsp; So that would seem to rule out folder rights.
I uninstalled all NI software and drivers from my computer, reinstalled them, and I still get the error.
NI, what conditions cause the dialog to be blank as shown above?Message Edited by FlamingYawn on 07-09-2008  04:44 PM
0
x9561 (148440)
7/9/2008 10:10:05 PM
Figured it out.&nbsp; What's causing it, at least.&nbsp; Not why.
&nbsp;
I added 2 GB of RAM a little while back, upping my memory to 4 GB.
&nbsp;
I didn't know WIndows had a problem using the full 4 GB; it was only using 3 GB, but that's another issue.
&nbsp;
One of the fixes I read had me add "/PAE" (Physical Address Extension, or something like that) to c:\boot.ini.&nbsp; It didn't help, but I left it there.
&nbsp;
When I removed it, the build worked.
&nbsp;
Maybe NI can figure out why.
0
x9561 (148440)
7/9/2008 10:40:09 PM
That is really strange.&nbsp; I'm interested to see if NI can determine why.
0
x9561 (148440)
7/10/2008 5:10:08 PM
Removing /PAE isn't enough, now.&nbsp; I need to have /3GB in order to build.
0
x9561 (148440)
7/11/2008 5:40:08 PM
Hi Robert,
Please let me know the answers to the following questions:
1. The operating system that you are using--is it 64-bit or 32-bit?
2. The exact amount of physical memory that you have--please give me the number shown in System Information.
3. Any additional installers that you are using--NI-488.2, NI-DAQmx etc. 
If you are running a 32-bit installation OS on your computer but have 4GB of memory, that is indeed a reason for your build error. Labview being a 32-bit installation maxes out at 4GB and therefore, the threshold RAM is set to 3GB. You do not need to have PAE enabled as that is used only for 64-bit installations or for a 64-bit memory. Please have a look at <a href="http://digital.ni.com/public.nsf/allkb/49C3316C0FFC23C286256E4B006FB6A4?OpenDocument" target="_blank">this</a> knowledgebase article for more information. Enable PAE only if you have 64-bit memory addressing. Otherwise, the only workaround is to use 3GB of RAM. Hope this helps. 
Ipshita C.
0
x9561 (148440)
7/14/2008 8:40:08 PM
1.&nbsp; 32 bit
2.&nbsp; 3.00 GB (it displayed this before I took out my 4th 1 GB stick, as well)
3.&nbsp; DAQ, GPIB, VISA, CAN, Serial
I lowered my RAM to 3 GB and removed the '/PAE'.&nbsp; I was still getting the build error until I added '/3GB'
0
x9561 (148440)
7/14/2008 10:40:05 PM
Hi Robert,
Even after you removed your 1GB stick the boot.ini file does not update automatically. Also, are you using SP3? In that case, it is necessary to specify /3GB as a boot.ini switch. Hope that answers your question.
Ipshita C.
0
x9561 (148440)
7/15/2008 5:40:04 PM
Reply:

Similar Artilces:

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. ...

why it keeps on asking &quot;NI LabVIEW 8.5.1&quot; distribution when building installer?
Hi, I am building an installer for one image processing application. For addtional installers, NI Labview runtime engine 8.5.1NI vision runtime engine 8.5NI IMAQdx 3.1.2NI VISA runtime 4.3When building, it keeps on asking "NI LabVIEW 8.5.1" distribution even though I put the CD into CD room, saying it needs to copy a component installed or updated by the distribution to continue building the installer.If&nbsp; NI-IMAQ dx 3.1.2 not checked, it is OK. BUT, I need it.Thanks a lot for any help.Anne Zuo What is a "CD room"? or CD driver. sorry for my language.&nbsp; Take a look at this <a href="http://forums.ni.com/ni/board/message?board.id=170&amp;view=by_date_ascending&amp;message.id=210032#M210032" target="_blank">link</a> and see if it helps. &nbsp; Also, if it doesn't like disk 1, put in disk 2 instead, if not disk 2, then try disk 3.&nbsp; Perhaps it is looking for the driver it needs, but the actual files it is looking for is on the 2nd or 3rd CD. &nbsp; Ultimately, it may be best to copy all of the CD's to your hard drive and have it point to them there. ...

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 ...

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.. :) ...

LabVIEW RT 8.5.1 &quot;reboot due to system error&quot;
I'm running my app on a quad core RT desktop target.&nbsp; The executable runs anywhere from a few minutes to a few hours before the machine reboots.&nbsp; About half the time I get the "reboot due to system error" and the "software state: safe mode" messages.&nbsp; rtlog.txt has no record of the reboot. &nbsp; Is there any way to get LabVIEW to log any useful data when this happens? &nbsp; What actions can I take to track this down (other than disabling portions of my code to see what part might be causing it)? Connect up a display to&nbsp; the RT chassi to see if you get any message there. In addition, watch your memory useage. If you run out of memory,&nbsp;RT will just STB. :smileysurprised: Ben Hey Ben, Thanks for responding. I do have a display hooked up to my RT desktop, but when it reboots, it reboots.&nbsp; Screen goes blank.&nbsp; No messages. How do you watch the memory usage on the RT target? What does STB mean? Thanks, In LV 8 and up I believe there is a property under the RT target inside the project. STB = "Sh#$ The Bed" Ben You can go to Tools --&gt; Real-Time Module --&gt; System Manager ...

How to remove the &quot;int len&quot; of my return string on the DLLS header when building a DLL on LabVIEW 8.5
Hi all. I'm building a DLL on LabVIEW and I choose a string as an output on the terminals connectors. But LabVIEW creates another output, the lenght of the return string. This is a problem because I have other DLLs and&nbsp;I need them to be compatible. How do I remove this length from the header? What is the difference between Pascal String and C string and String Handle Pointer? String Handle Pointer removes the length from the header but I don't know the difference between this data types. Thanks in advance for the help. &nbsp; Daniel Coelho Portugal &nbsp; Daniel Coelho wrote:Hi all. I'm building a DLL on LabVIEW and I choose a string as an output on the terminals connectors. But LabVIEW creates another output, the lenght of the return string. This is a problem because I have other DLLs and&nbsp;I need them to be compatible. How do I remove this length from the header? What is the difference between Pascal String and C string and String Handle Pointer? String Handle Pointer removes the length from the header but I don't know the difference between this data types. Thanks in advance for the help. &nbsp; Daniel Coelho Portugal &nbsp;C string pointer is a pointer to a memory location whose string information is terminated by a 0 byte. Pascal String Pointer is a pointer to a memory location where the first byte specifies the number of bytes to follow. This obviously allows only for strings up to 255 character length.LabVIEW String Hand...

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...

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...

Build error after upgrading from 8.2.1 to 8.5 &quot;Error 1055 occurred at Invoke Node...&quot;
After upgrading to 8.5, I'm getting the following error when trying to build an EXE: &nbsp; Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference: Error 1055 occurred at Invoke Node in AB_Source_Library.lvclass:Close_Reference.vi-&gt;AB_Build.lvclass:Copy_Files.vi-&gt;AB_Application.lvclass:Copy_Files.vi-&gt;AB_Build.lvclass:Build.vi-&gt;AB_EXE.lvclass:Build.vi-&gt;AB_Engine_Build.vi-&gt;AB_Build_Invoke.vi-&gt;AB_Build_Invoke.vi.ProxyCaller Possible reason(s): LabVIEW:&nbsp; Object reference is invalid. I have been building this application for both Windows and Mac OS, and I even get the same error when building the&nbsp;.app&nbsp;on an Intel Mac. Things that I've already tried: *&nbsp;Mass-compiling all my code * Created the project from scratch * Enabled each panel of the "diagram disable structure" one at a time&nbsp;and compiled again &nbsp; Any ideas? I think I saw that in LV 8.2.1 after upgrading from LV 8.2 I did a repair on the nistall and that cleared up the problem. You may want to try that. Ben You mean a repair of the NI installation of LV8.5?&nbsp; But I had the same trouble on a Mac OS machine too.&nbsp; Seems unlikely that an installation glitch could explain the problem on such different platforms.&nbsp; (For the record, I tried on both a Win2K machine and an XP machine--a total of 3 different ...

Memory is full during &quot;Save As&quot; of LabVIEW 8.5 project
Good Morning All, &nbsp;&nbsp;&nbsp;&nbsp; Have run into a weird issue while trying to rename a LabVIEW 8.5 project. I've got two projects that ended up having the same names (one by me, one by another engineer). I want to open both at the same time, so I figured I'd open the one and do a "save as", or a "rename". The first time it started processing, doing file loads, and then hung looking for a sub-vi, with the search address pointing to the .llb in the LV 8.5 directory where I manually located it. Once that was resolved, and the original project saved I tried again. This time it did a bunch of loading and then gave me an error box with the message:&nbsp; "LabVIEW:&nbsp; Memory is full.&nbsp; Cannot save project 'original project name.lvproj'" This isn't a big project, the machine is a new HP Compaq dual core 2.8GHz with 1.5Gb of ram, so I don't really think that it should be generating anything that big. This happens with either a "save as" or "rename". I ended up just changing the names of the .lvproj .aliases files to the one I needed and it seems to load ok, but it would be nice to understand what is happening here. &nbsp; &nbsp; This is interesting behavior, since NI actually ensured that you would now have the ability to Save As and Rename a project with the <a href="http://www.ni.com/pdf/manuals/371780c.pdf" target="_blank">release ...

Labview 8.5 error on save: &quot;Cannot load help information of [filename].&quot;
Hi all, &nbsp; &nbsp;I was working on a VI in Labview 8.5 when the program (Labview) crashed. When I relaunched Labview it asked me if I wanted to recover the VI&nbsp;I was working on,&nbsp;I said yes and the recovered VI runs fine, but I cannot save it. When&nbsp;I try to Save or Save As I receive the following error message: "Cannot load help information of [Filename]" and my only option is "Cancel Save". If I click "Cancel Save" Labview returns a "File not Found error". Until the recovery, I could and did save the file with no problems. It now seems that I am locked out of the file. &nbsp; &nbsp; I have a backup, but it is does not contain the 2-3 hours of work I put in before the crash. Does anyone have a work-around, or know the source of this error? This is the second time I have seen it on a recovered file (the first time I had a fresh backup, so it wasn't a big issue). &nbsp; Here is a dump of the "Referencing files in the project or its dependencies" from the Save As dialog: &nbsp; [Project Name].lvprojreplay2-offsets.vi:Instance:6replay2-offsets.vi:Instance:5replay2-offsets.vi:Instance:3replay2-offsets.vi:Instance:2replay2-offsets.vi:Instance:4replay2-offsets.vi:Instance:1replay2-offsets.vi:Instance:0 &nbsp; Thank you, Tim I'm having the same problem. I came here to see if there was any information about this problem, and found the previous message. Lucky for me, I&#...

How can I convert the &quot;AI one pt&quot; symbol from LabVIEW 6.3 to LabVIEW 8.0?
Hi, &nbsp; I've got an assignment with LabVIEW and&nbsp;I work with LabVIEW 8.0. The program I work with is written in LabVIEW 6.3 and had to be converted&nbsp;to LabVIEW 8.0. That went very well, except for one symbol. The "AI one pt" symbol (see&nbsp;enclosed figure) turned into an empty box (question mark). My question to you is how can I overcome this problem, or how can I simulate this symbol with LabVIEW 8.0? &nbsp; With kind regards, &nbsp; Sander Smeets &nbsp; <img src="http://www.ese.upenn.edu/rca/software/Labview/labview41/inputoutput/AISamplechannel.gif"> Hello, Graziano is right about this. To make it completly clear: The block you refer to as a symbol is a VI belonging to the Traditional NI-DAQ driver. Currently there are two drivers for DAQ boards: DAQmx (the new one) and Traditional NI-DAQ (the old one). Since your VI was written in LabVIEW 6.x (6.3 never existed) the VI uses the old driver. What you need to do is: install Traditional NI-DAQ on your PC to get the support VI's for the driver in LabVIEW. This Traditional NI-DAQ installer&nbsp;should be on the driver CD which was delivered along with LabVIEW 8.0 or you can download it here: <a href="http://joule.ni.com/nidu/cds/view/p/id/586/lang/en" target="_blank">http://joule.ni.com/nidu/cds/view/p/id/586/lang/en</a> There is one good point though which Graziano already mentioned: Which DAQ board are you using? I...

Error 1047 in LabVIEW 8.2: LabVIEW failed to send variable to the script server. Server:&quot;&quot;
I am working with the evaluation version of labVIEW as well and I have run into another error.&nbsp; I am using a MATLAB script node within a for loop and attempting to pass the for loop counter variable into the script.&nbsp; When I run the code it brings up a 1047 error and says "LabVIEW failed to send variable to the script server. Server:"" ".&nbsp; I looked up the error online which seems to have roots in a failed auto initialization of MATLAB.&nbsp; Is there something that I can do in labVIEW to fix the problem or is it strictly a MATLAB error? &nbsp; I really appreciate your help. Hi Patsenat, &nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; We have a knowledgebase document on our system referring to this issue.&nbsp; Try reading through <a href="http://digital.ni.com/public.nsf/allkb/2B3FF46C8512C4F786256CF30071BE53?OpenDocument" target="_blank">this</a> and attempting what it says.&nbsp; If you still have problems, please post again. ...

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 ...

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...

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 . ...

Labview &quot;Fatal Internal Error &quot;memory.cpp&quot; line 1038
Hi, &nbsp; This is an example file provided by NI and can be found in Labview 8.2\examples\instr\niHSDIO: Dynamic Generation.lib. Inside this library, there is a file called "Dynamic Generation.vi". If I copied "Dynamic Generation.vi" to other place, the labview will crash. Error message: &nbsp; "Fatal Internal Error. "memory.cpp". Line 1038. Labview version 7.1.1. You will lose any unused work, please contact NI, etc, etc" &nbsp; In the mean time, the Windows freeze. Mouse right click no response. No status bar at the bottom of the screen. The whole desktop is blank. All icons on the desktop disappeared. I have to log-off and re-login to re-active everything. &nbsp; I also tried to copy&nbsp;other VI's in other library files. Same thing happened. &nbsp; Thanks, Jing I&nbsp;was using Labview 8.2.1 when I had this crash, though I have Labview 7 installed in the same computer. When I "copy the file to some other place", I mean: Click the *.vi file, ctrl-c and ctrl-v to some other directory. Thanks, Jing ...

&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; ...

&quot;filewatcher labview&quot;
Hallo &nbsp; Hat jemand von Euch bereits einen filewatcher (ein Programm das nachsieht ob ein anderes Programm Daten in ein file schreibt, und mir dann den zugriff auf diese Daten erm�glicht.) Ich ben�tige ein sollches Programm dringend Version 7.1 bis 8.2 vorhanden. &nbsp; Vielen Dank Werner Hallo Thanks for info! To you have a ready program for checking an activity on a file. How could i give a notice for a good answer! Thanks Werner &nbsp; Thanks Gerd nice day ...

Installer &quot;Source file settings&quot;, &quot;VI Settings&quot; problem in 8.2
I have just upgraded from LabVIEW 8.0 to 8.2 and it seems the Installer "Source file settings", "VI Settings" check boxes no longer have any affect on the built application. &nbsp; For example, if I un-check the "Show Menu Bar" boxes for my Main.vi and build, when I run the built application the Main.vi Menu Bar is visible. &nbsp; It seemed to work as expected with 8.0 though. &nbsp; Any help and suggestions are much appreciated. &nbsp; Aaron Hi Seamus, Thanks for that and I look forward to hearing from you again Aaron ...

Labview 8.20
Hi, &nbsp; I have multiple loops/parallel&nbsp;tasks&nbsp;with&nbsp;various communication buses in an RT system which need to write data to its own individual&nbsp;log file which is using an Binary format. What kind of benefits will I get in terms of performance by using the TDM Streaming?&nbsp; The only benefit I foresee is the consolidation of data into an XML type structure and store data into an universal file versus 4 individual ones.:smileysurprised: &nbsp; Are TDMS being handled differently in RT for disk IO&nbsp;management? because each write will take upto 8-9 ms.The goal is to reduce disk IO and improve performance.:smileyindifferent: &nbsp; Any advice? &nbsp; Ashm01Message Edited by ashm01 on 10-30-2006 11:46 PM Hey Bill, Is your application in RT? I would appreciate if you have some benchmarks on this. I am about to convert the binaries to TDMS and was wondering if anyone had any favorable performance gains. Thanks, Ashm01 Hi Ashm01, &nbsp; The TDMS API was developed to facilitate streaming data to disk at high rates, while maintaing the same descriptive information you would find in a TDM file. You might find the following information interesting from an article on Developer Zone (<a href="http://zone.ni.com/devzone/cda/tut/p/id/3539" target="_blank">Introduction to LabVIEW TDM Streaming VIs</a>): &nbsp; Unlike the TDM files, which have a strictly required XML-based header file, T...

Using &quot;To-upper-case&quot; on cluster with Enum (LabVIEW 8.2)
Hi folks, &nbsp;&nbsp;&nbsp;&nbsp; The following example won't compile on my installation of 8.2 ! &nbsp; &nbsp; <img src="http://forums.ni.com/attachments/ni/170/225670/1/ClusterErr.jpg"> &nbsp; Cheers.Message Edited by tbd on 01-23-2007 09:21 PM ClusterErr.jpg: http://forums.ni.com/attachments/ni/170/225670/1/ClusterErr.jpg ClusterErr.vi: http://forums.ni.com/attachments/ni/170/225670/2/ClusterErr.vi It fails the same way under LabVIEW 8.0. Clearly something is not handled properly. (Of course I don't quite see the general&nbsp;usefulness to use "to uppercase" on a simple&nbsp;enum. ;)) altenbach wrote: (Of course I don't quite see the general&nbsp;usefulness to use "to uppercase" on a simple&nbsp;enum. ;)) (tbd momentarily ponders: "Why does it seem there's always something Altenbach doesn't quite see?") &nbsp; Oh, gee,&nbsp;do it (enum to upper-case) all the time&nbsp;when I forget and type enumerated-case-values in all upper-case. :smileywink: &nbsp; &nbsp; <img src="http://forums.ni.com/attachments/ni/170/225670/1/ClusterErr.jpg"> &nbsp; Indeed it doesn't compile.&nbsp; But the To Upper Case VI handles numbers as ASCII codes.&nbsp; How would converting an enum value of 97 to 65 be useful to you?&nbsp; Are you trying to capitalize the strings in the enum's typedef?&nbsp; A case structur...

OpenG &quot;LabVIEW Data Tools&quot; library v2.8 released
Hello Everyone,There is a new version (2.8) of the OpenG "LabVIEW Data Tools" library (oglib_lvdata package) available. This library contains several routines manipulating LabVIEW data (variants and type descriptors).<img src="http://forums.ni.com/attachments/ni/170/255217/1/lvdata.png"> This release...1) release adds minor performance improvements.See <a href="http://forums.openg.org/index.php?s=&amp;showtopic=281&amp;view=findpost&amp;p=1574" target="_blank">here</a> for more info. You can download+install this package using <a href="http://jkisoft.com/vipm" target="_blank">VI Package Manager</a> . Just press the "Check the Network for Available Packages" button to refresh your package list.Thank you,-Jim KringMessage Edited by Jim Kring on 06-25-2007 10:39 PM lvdata.png: http://forums.ni.com/attachments/ni/170/255217/1/lvdata.png ...

&quot;IDDCO ERROR&quot; for Labview 8.0 and Keithley 6487 picoameter
Hi all, I have a 6487 keithley picoameter and I would like to take current mesurements using labview 8.0. What I tried to do is to built a very simple vi with two instrument I/O assistants (one for configuring the picoammeter and another to take measurments as it changes voltage). I have accompliced the same thing in Visual Studio with C#. The problem is that although some times I do get correct measurements there is always one, two or three IDDCO ERROR idications which I do not know what they mean.&nbsp; I can only tell that this does not happen at the same voltage value but it seems rather random. What is wrong? I have attached the vi if anyone is interested. Thanks in advance for any helpAndreas V_bias_test.vi: http://forums.ni.com/attachments/ni/170/324015/1/V_bias_test.vi According to <a href="http://www.keithley.com/search?searchType=general&SearchableText=IDDCO" target="_blank">Keithley</a> , "This error means the instrument received an Illegal Device-dependent Command Option.". I have not used this model Keithley or DDC. One thing you should do is wire the error out of the initialize Instrument Assistant to the for loop to assure that is actually runs before the for loop. ...

Web resources about - LabVIEW 8.5.1 &quot;The build was unsuccessful&quot; - comp.lang.labview

Resources last updated: 3/19/2016 9:03:23 AM