"LabVIEW load error code 3" USB drive

Hi Folks,
      I'm not expecting any solution here, though it would be nice...
Twice, recently, I've lost a top-leve VI due to the error below.  I suspect the problem is related to working off a new USB drive - a 2G Lexar Firefly.  For two or three years a Lexar Jumpdrive Elite (256M) served me flawlessly, after moving to the Firefly ~2 weeks ago, this error has happened twice.  BTW, the Firefly is also extremely slow - amazingly slow, considering how much newer it is.
If any wiz-kids have dissected the VI binary well enough to, possibly, identify/repair problems, it would be very much appreciated!
<img src="http://forums.ni.com/attachments/ni/170/291448/1/LoadErrorCode3.JPG"> 
Cheers!Message Edited by tbd on 12-19-2007  09:45 PM

x9561 (148438)
12/20/2007 4:10:11 AM
comp.lang.labview 35210 articles. 1 followers. vasusachin24 (1) is leader. Post Follow

2 Replies

Similar Articles

[PageSpeed] 33

Hi Phillip,
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Thanks for the heads-up re:&nbsp;background-apps slowing-down drive.To be honest, I don't know how to find/disable such apps. but now know to look.
Re:&nbsp;Lexar Firefly - it's&nbsp;slow by design, though there's no warning on the package when you buy it.&nbsp; Here's the response from their Customer Support:
" Jumpdrive Firefly is a non-speed rated Jumpdrive and is made of MLC technology.
MLC stands for Multiple Level Cell technology. It is a technology that allows each memory cell in flash media to store two bits instead of one in each memory cell. In SLC (Single Level Cell) technology, a 0 is assigned to one voltage level, and a 1 is assigned a different voltage level. But in MLC, the binary numbers 00, 01, 10, and 11 are all assigned progressively higher voltage levels. The MLC technology is lower in cost because it can store twice as much in each cell. It is also significantly slower than SLC technology, because it takes more processing to decode the information in each cell.
Hmm, I thought "MLC" stood for Mutton, Lettuce and Cheese! ;^)
Anyway... because the VI corruption has bitten me twice in the relatively short time since switching to the Firefly,&nbsp;it or Firefly-specific SW&nbsp;seems responsible.&nbsp; Experimenting now with a 2G replacement (not a Lexar.)
The size of the corrupted&nbsp;VI, on disk, looks normal as if it's largely intact - too bad it's inaccessible!
Thanks again,
x9561 (148438)
12/20/2007 6:40:07 PM
tbd wrote:

Hmm, I thought "MLC" stood for Mutton, Lettuce and Cheese! ;^)

That makes me think of Wallace and Grommit (and their friend Shaun). Did I put on the right trousers today?! :smileyvery-happy:
x9561 (148438)
12/27/2007 2:40:11 PM

Similar Artilces:

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

&quot;Invalid Drive&quot; error while installing LabVIEW
&nbsp; Installing LabVIEW 6.1 on an NT4 machine with administrator previldeges. &nbsp; Comes up with error "Error 1327 : Invalid drive H:\"&nbsp; ....Dialog Box 1 &amp; then "Error 1603 occurred while installing NI LabVIEW 6.1. Continue installing other products ?" ..... Dialog Box2 &nbsp; Same thing happens while installing RunTime Engine 6.1 &nbsp; Error messages included in attached file. &nbsp; Any insights? &nbsp; Thanks &nbsp; &nbsp; &nbsp; Invalid Drive Error While Installing LabVIEW.doc: http://forums.ni.com/attachments/...

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

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

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

Why do I get &quot;error code 3: Could not load front panel&quot; when I run my executable.
I have a LV 8.5 VI that controls only an agilent spectum analyzer. The agilent VIs call DLLs rather than SCPI commands. I created an application and an installer to load on a non LV machine and ran setup which was successful. When I run the EXE I get "error code 3: Could not load front panel" for each of my agilent spectrum analyzer VIs. I have to click "OK" about ten times, once for each VI. (My executable runs fine on all machines that have labview 8.5) The front panel does load with a broken arrow. The errors listed when the arrow is clicked for all of the Agilent VIs state: Missing subVI AGE444xInitialize.VI (or close.VI or read.VI etc.)There is an AGE444x32.DLL in the data folder with the EXE file so I included as support both the DLL and all of the agilent drivers in the application build. Still no luck. I have built the application and installer about 6 times in various forms. I NEED AIR SUPPORT. Unfortunately I do not have access to the internet at my jobsite so bear with me.Rob I figured it out. The machine without LV on it didn't have NI VISA installed although it did have the run time engine. Once I installed NI VISA it was good to go. Hi V-rob, I'm glad to hear the executable is working now that NI-VISA is installed.&nbsp; Thanks for posting the solution! ...

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

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

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

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

The .NET assembly expected to be at &quot;&quot; was loaded from &quot;NULL&quot;
Hello, &nbsp; I use NET Components in a LabVIEW 8.2.1. VI and all work very fine. Now I convert it to LabVIEW 8.5 and I always get a warning, when open it. The Warning is : &nbsp;The .NET assembly expected to be at "" was loaded from "NULL". As example I add my CallbackVI in the Attachment. If somebody has an idea to remove this warning I would be thankful. &nbsp; Thanks in advance TE_NET_ToolStrip.ClickCallback.vi: http://forums.ni.com/attachments/ni/170/304243/1/TE_NET_ToolStrip.ClickCallback.vi Oh I was glad to early. The problem was only solved one time. When I changed something and saved again, I had again the troubles. &nbsp; I will recreate the VIs now. I already done, but it didn't helped. Now I read, that old one should be closed. ...

Labview crashes on loading &quot;missing&quot; subvi
Now that I'm confortable with Labview 8.5's&nbsp; projects explorer, I've been cleaning up my old vi's, and putting them into projects and library's.&nbsp; This meant that many vi's got renamed or moved, so I had to update those locations in some programs. &nbsp; During moving in the project explorer, I had a few unexpected crashes.&nbsp; It seems that moving/renaming doesn't always work properly...&nbsp;&nbsp; I've solved those issues by hand, didn't try to search for a reproducable error condition... &nbsp; But now I'm updating the toplevel vi's that make use of those renamed and moved subvi's,&nbsp;and I'm getting more crashes...When loading the top level vi, it asks for the location of the renamed/moved vi's.&nbsp; So I browse to it, and select the correct vi's.&nbsp;&nbsp; Works for about a dozen vi's, and then Labview suddenly crashes.&nbsp; I've tried ignoring that missing vi, but then it crashes somewhere else.&nbsp; So I decided to simply ignore all missing vi's.&nbsp; That worked,&nbsp;it then loads without crashing, and ofcourse shows lots of missing vi's with questions marks.&nbsp; I then manually, replaced the ?-vi's with the correct ones.&nbsp;&nbsp; Took a little, but now the program works.&nbsp;&nbsp; I can run it without problems, so I saved it, and thought I was ready.&nbsp;&nbsp; &nbsp;...

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

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

Error -50150 &quot;Cascade Failure&quot;: LabVIEW Bug?
Hello, &nbsp; I'm new to the forums here, so I apologize in advance for breaches of etiquette or various other newbie actions. ;) &nbsp; While using the DAQmx Create Channel VI in conjuction with my own custom unit scale, I keep running into a -50150 error for various combinations of slope and y-intercept. I've pared my problem down to the attached VI. As you can see, I'm setting up the linear scale with a slope and y-intercept, and then scaling the original +/- 10V range for&nbsp;an appropriate&nbsp;maximum and minimum. Upon running this VI as-is, I get the -50150 "cascade failure" error. However, changing the y-intercept value to an arbitrarily different value, say 6, causes the program to run fine. &nbsp; I've noticed that other combinations of slope-intercept also crash the program, and that these combinations usually have a pattern. For example, the (m, b) combinations of &nbsp; (100,5); (100,20); (100,30); (100,45); (100,55); (100,70); and so on, with the 10-15-10-15 pattern repeating &nbsp; cause the program to throw -50150 as well. I have not found any values of the y-intercept that cause the program to crash that are not&nbsp;multiples of 5 (although obviously I cannot say conclusively that there are none). I realize that it is all very well for me to claim that this is a software bug and not my fault, but I cannot see any good reason for this to be happening in such an odd way. &nbsp; I am running LabVIEW...

LabVIEW crashed when openning XControl Facade, and Init VI
XControl_Fatal error.PNG: http://forums.ni.com/attachments/ni/170/261642/1/XControl_Fatal error.PNG XControl_Fatal error1.PNG: http://forums.ni.com/attachments/ni/170/261642/2/XControl_Fatal error1.PNG ...

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

Why do I receive a &quot;Fatal internal error: &quot;fpsane.cpp&quot; line 399&quot; when saving?
Why do I receive a&nbsp; "Fatal internal error: "fpsane.cpp" line 399" when saving my VI? &nbsp; Thank you. Gustavo Hi Chris, But I could not solve the error that way. Actually, Labview is crashing with this error at any time when I am writing my VI. It simply crashes even if the VI is not running. I think the problem is not in my VI, because&nbsp;it runs normally in another machine, but must be with the Labview installation. I have reinstalled Labview three time already and the error continues. Any other ideas? Thanks, Gustavo hum... not yet. &nbsp; I reinstalled LAbview 8.2 for the 3rd time... nothing happened. The VI I am trying to run is the example 4128.vi we can find in the forum. It is still crashing with the same error when I try to save or save as... or sometimes before the VI starts to run when I do any alteration. I think the error might be related to saving the VI. The problem happens to other VIs as well, but only those that are using IMAQ. &nbsp; Hope you can help me... Tks, Gustavo I am agree with <a href="http://forums.ni.com/ni/view_profile?user.id=91046" target="top"> gutoassi</a> , even though labview 8.2.1 releases are very useful, it still have something to be depurated, my VI is ok and I have the same error fpsane.cpp line 399. In order to give a clue with this issue, I am working with CINs and visual C++, some times it just work fine but in a very inconsistent way it crashes som...

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

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 to change &quot;ASRL2:... &quot; to &quot;COM1&quot;?
Dear All, &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I have used com port in my vi. And When I run it in edit mode,&nbsp;the selection of com displays "COM1,COM2,LTP1". &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; But when I build it, and run it in another PC, it displays "ASRL2:...". &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; How can I modify my vi to make it display COM1... in another PC? &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; And If I only want to display all serial port such as COM1,...

Programmatic &quot;undo&quot; for &quot;FitControlToPane&quot; ?
Howdy neighbors!, (using LV8.2)&nbsp; I'm trying to develop a GUI that lets the user toggle a Tab-control between "Full Pane" and a&nbsp;reduced size/position - sorta-like&nbsp;the "Full Screen" option on many Video apps.&nbsp; The effect of the&nbsp;invoke-node method "FitControlToPane" is perfect (- :smileyhappy: -), but how to undo that effect?&nbsp; After&nbsp;FitControlToPane,&nbsp;"Scale Object with Pane" is selected in the IDE, yet I can't find a "property" for it. :smileysad:&nbsp; FitControlToPane also changes the visibility of vertical and horizontal scroll-bars - are these [VI Properties] programmatically settable? &nbsp; Cheers! &nbsp; &nbsp; &nbsp; follow up... FitControlToPane also changes the visibility of vertical and horizontal scroll-bars - are these [VI Properties] programmatically settable? Feel kinda silly now, having advised someone else to search LabVIEW's HELP first! :smileytongue: &nbsp;- found Scrollbar Visibility can be set via (LV8.2)\ VI \Panel(reference)\Panes[0].HorizScrollbarVisibility. <img src="http://forums.ni.com/attachments/ni/170/239318/1/ScrollBar.JPG"> Still hunting for an&nbsp;elusive "Set Scaling Mode" method... (The&nbsp;Tab Control's&nbsp;"AutoGrow?" property doesn't seem to do anything!?)Message Edited by tbd on 04-03-2007 12:56 AM ScrollBar.JPG: ht...

How to interface the Labview and Simulink (Matlab) without using the &quot;NI LabVIEW Simulation Interface Toolkit&quot;?
Hello, I've been using the Labview for the data aquisition. And I also developed a controller in the Simulink (Matlab) environment. I'd like to control my application using both&nbsp;programs. How&nbsp;could I&nbsp;interface the Labview and Simulink (Matlab) without using the "NI LabVIEW Simulation Interface Toolkit"? thank you, Kostya. Hi Kotsya, Thank you for posting to the National Instruments Discussion Forums. If you are not using the Math Interface Toolkit, you may be interested in using the MATLAB� Script Node. This allows you to call MATLAB� commands using ActiveX and I you can call your Simulink model from MATLAB� that way. Here are some resources on how you can do this: <a href="http://zone.ni.com/reference/en-XX/help/371361B-01/gmath/matlab_script_node/" target="_blank">MATLAB � Script Node LabVIEW 8.2 Help</a> <a href="http://digital.ni.com/public.nsf/websearch/4475BC3CEB062C9586256D750058F14B?OpenDocument" target="_blank">How Can I Resolve MATLAB� script node and Xmath Script Node Issues in LabVIEW?</a> Hope this helps! Hi, Abhinav, thank you for your reply. I will try to explore the option with the Script Node. regards, Kostya. &nbsp; &nbsp; ...

Web resources about - &quot;LabVIEW load error code 3&quot; USB drive - comp.lang.labview

Resources last updated: 3/19/2016 12:34:18 PM