LabView error code 1940

I have created a LabView VI to take some Sound and Vibration toolkit measurements on a PXI-4461 card. I've created a .exe and a .dll out of the VI and both give me a 1940 error code (source = SVT Unit Conversion (Complex)(1 Ch).vi) the first time the VI is run, but I don't receive any errors after that. I've attached my VI, does anybody know what my issue is?
Thanks,
Luke
Attachments:
PXI_4461_THD_FIR_1st.vi ‏84 KB

Hi Luke,
Error 1970 is a warning and you can find out more about it here: http://forums.ni.com/ni/board/message?board.id=100&message.id=1206&requireLogin=False
Usually errors come with a description in the error cluster. This seems to be more or less on the VI rather than something inherent to the built distribution. If you're getting 1970 in your application, you should also be getting it in your VI.
Yes, you can set the different ways a VI runs when built. This can be set in the VI properties under the File menu, programatically using VI property nodes under the application control palette, and some limited options are also in the build specifications. one thing you can try is to discard that error during your first loop iteration and therefore you can move along. Since this is a warning and due to the nature of it, I imagine that this would only happen upon first run.
My overall recommendation is that you don't have a problem with your build but that you need to look through the VI, like what Chris said. These are warnings dealing with configuration mismatches so you'll want to make sure that your weighting settings and bandwidth settings are set properly.
PBear
NI RF

Similar Messages

Labview error code 11

I have a LV in 6.0. I am trying to change it to a LV6.1. However my attempts fail. I get the following message.
An error occurred loading VI write to digital port.vi. Labview load error code 11: VI version (6.0) cannot be converted to the current labview version(6.1) because it has no block diagrams.
In my LV6.1, under the functions menu the entire DAQ section is missing?
Is my problem due to a faulty LV6.1 CD? I have attached the file concerned.
Attachments:
USCORRECTAPRIL2005 23 April 2005 Rev 2.vi ‏420 KB

Most likely, the subVI in question was saved without block diagram. This prevents it from being converted to a newer LabVIEW version and you're out of luck. Do you have a backup copy with block diagram?
Try to contact whoever made the original VI to either get a version with block diagram or in a different LabVIEW version.
It is typically a bad idea to remove the block diagram for reasons that should now be obvious. If you want to protect your code from inspection or modification, place a strong password on the diagram. This way, the VI can still be upgraded.
LabVIEW Champion . Do more with less code and in less time .

LabView Error Code -200072

Hello! Does anybody know where I can find the description for Error Code -200072 or all error codes in general? The error is caused during the creation of virtual channels using Create Virtual Channel.vi in a Frame Sequence within a While Loop. Many thanks for your input.

Error Code: -200072
"Duplicate channels in the list of physical channels are not supported by this device."
The above error occurs when you create multiple tasks within MAX and do not change the names created by default. The best way to do this is not to create any tasks at all within MAX and leave the Create Virtual Channel.vi to create its own physical channels and clear them using Clear Task.vi.

LabVIEW Error Code -63040 on sbRIO 9632

Hello.
I'm trying to run the roaming VI on my NI Robotics Platform 2.0 kit and it's giving me the error -63040 which is a communications error. This is not the first time I try to run roaming, as I've been able to do it before successfully (on a different computer) but now it's giving me that error. I've searched around for different ways to fix it, including verifying it's IP, making sure that the PC and robot are on the same network, and even formating the sbRIO board and reinstallling the software but nothing seems to work. I can't find any other way online to fix it.
The code seems to compile right, but then the robot does not move. In the attached image, i've highlighted the process so you guys can see what I"m talking about.
Any help on this would be appreciated!
Solved!
Go to Solution.
Attachments:
Screenshot_2.png ‏44 KB

Software on the sbRIO is Screenshot_6.png, while the other two are all the software installed on the host.
Everything seems to match the software on the host.
Thank you so much for your help.
Attachments:
Screenshot_6.png ‏119 KB
Screenshot_7.png ‏126 KB
Screenshot_8.png ‏115 KB

What is LabView load error code 34?

I'm using the 30 day evaluation version 7. I created a very basic instrument I/O .vi to test the capabilities of the software. The .vi works fine on the development machine, but when I try to open it on a different machine, which has the LabView 7 Reader installed, I get the above error. I'm guessing it's because it is a trial version, but I want to make sure I'm not missing anything.
Thank you.
Jack Remiasz
Industrial Measurement Systems, Inc.

Karra,
I believe that the following Knowledge Base entry answers this question:
"LabVIEW Error Code 34 when opening a VI in the LabVIEW Player"
Any VI that we open in the LabVIEW Player must be signed. Error 34 will pop up when we try to run a non-signed VI. We can sign our VIs by using the LabVIEW Professional Development System 7.x and the LabVIEW Player VI Creation Toolkit. Please refer to the link above for more information. Hope that helps!
Craig H.
NI Applications Engineering

Load error code 3 unable to load front panel

Hi all,
Wrote a vi in 8.6 and saved it for 8.5 for collaborators. When they run it up pops the error code 3 unable to load front panel. Memory full. see attached picture.
Has anyone any suggestions as to how to fix this?
Regards,
leeser
Attachments:
labview error code 3.png ‏51 KB

Hi guys,
Thanks for the comments,
Attached is the code (zipped). Excuse the bulkiness of the block diagrams. It basically controls a rotation stage and makes an avi at specific times/angles. The motor stage is ActiveX controlled.
As I don't have access to the hardware I am writing semi-blind. However, when I did visit them and had a quick look at the code I could get it to work by quickly including the subvis into a new main vi and obviously compiling it in 8.5. (may be onto something here!)
Different versions of the labVIEW -> doing a group a favour; I have v8.6 they have v8.5, wrote it in v8.6 saved it for v8.5. I don't have v 8.5. I also have v 8.2.1 on a different machine. Saved it for v8.2.1 and it opened no problem in 8.2.1. Will send this version on and see how they get on. More likely to be forward compatible???
I agree that the optimal situation is 1) use the same version of labview and/or
2) they get someone to do their coding on-site!!!!
I think the corrupt front panel object could be true given that I could get it to work when the subvis were included in a new main vi on-site.
so versions 8.6, 8.5 and 8.2 attached.....
regards,
Leeser
Attachments:
rotation_control.zip ‏178 KB
rotation_control_v8.6.zip ‏60 KB
NCLA_rot_usb_v8.5 Folder.zip ‏141 KB

Error code message not appearing

Hi,
I tried to create a set of labview error codes codes using tools-> edit error codes. A created a few test errors and saved the file in
C:\Program Files\National Instruments\LabVIEW 2009\user.lib\errors
The file called test-errors.txt appears as follows:
<?xml version="1.0" encoding="ISO-8859-1"?>
<nidocument>
<nicomment>
First error code file Sean
</nicomment>
<nierror code="5000">
Device unstable
</nierror>
<nierror code="5001">
Device Critically Unstable
</nierror>
<nierror code="5002">
Press Stop or device will begin countdown to destruction
</nierror>
<nierror code="5003">
Destruction Countdown Commenced, all organic life will be destroyed with a 2 mile radius in t - 10 minutes
</nierror>
</nidocument>
I then designed a simple VI to test the error codes, see the attachment. However the error message do not appear in the error out source box.
Does anyone know why LabVIEW is not recognising my error codes?
Rgds,
Sean
Solved!
Go to Solution.
Attachments:
test.vi ‏12 KB

Hi Sean,
OK - i took another look at your test VI and probing on the error out wire shows the description, but you are right it is not shown in the control. I have attached a VI that should solve the problem (I have tested it and i works ok)
All I have done is to use the general error handler, which returns the error code and description, write the description to the error cluster and set the general error handler to 'no dialogue' so that the message is not displayed.
Like i say, it works but if there is a better solution let me know!
David
David
www.controlsoftwaresolutions.com
Attachments:
Error cluster from error code (with description).vi ‏13 KB

Using error codes.txt and error rings don't allow parameter inputs like custom error rings?

The error ring is very useful, especially with its parameterized inputs you can specific with %s, %f and %d parameters. I'd like to do the same thing in my fixed error codes using the error ring so that I can localize them into mulitple languages, but it seems that LabVIEW error codes from project text files never detect or support the parameter inputs, you get a error ring, but no input parameters. If you use the same string in a customer error code, it gives you the parameter input but then its hardcoded and you can't localize it. What gives?
Is there some other way to configure the error rings to use a project file for the error codes but still support the parameter inputs?
Solved!
Go to Solution.

Hi Mike_King
Here is a VI snippet that I created with two different approaches, in the first one I used the format into string, the second one the function search and replace.
Here are some links with information about the functions that I used.
Format Into String Function - LabVIEW 2011 Help
Search and Replace String Function - LabVIEW 2011 Help
Regards
Esteban R.
Attachments:
Generate error code.png ‏34 KB

FieldPoint error codes list missing

Hi everybody,
   Here
       http://zone.ni.com/reference/en-XX/help/371361A-01/lverror/error_code_ranges/
   you can find a list of LabVIEW error codes; in the list, the FieldPoint error code section is missing.
   Opening Extended Optomux VIs, opening SerialHandler (VISA).vi, I reached a point containing error codes, which ranges from 32896 to 33026 (or something like that......).
   On Field Point Programmer reference, optomux errors goes from 00 to 8C.
   What am I getting in "error code" field of error out
terminal of extended optomux VIs? Is there a list with complete
errors?
   More: what is the link between Status word (the one
obtained from "Write discrete with status") and error codes? Is it
simply "1" when some error is detected?
   It's quite important to have a deep knowledge of errors when you build an embedded critical application.....
   Thank you for helping me!
graziano.

Hi AlessioD,
    If you expand all the sub-VIs, starting from, say, (!J)Read Discrete (VISA).vi, that is an optomux VI, you'll reach Serial Handler (VISA).vi. There you find the error generation. The numbers assigned to errors seems not to be like constants defined in FP-1000 Programmer Reference Manual.
   In FP-1000 Programmer Reference Manual, for example, E_PUCLR_EXP error (power up clear expected error) has an Error Number (Hex) 00 (page 2-2).
   In the picture below, it seems that a Power up clear error has an error 32896 (resembles much a VISA error code...).
    Is there an utility to get Optomux error codes from General errors? I mean, errors reported from optomux VIs.
   Thanks!
graziano
Attachments:
forum_0.JPG ‏132 KB
optomux VI_1.JPG ‏7 KB

Spartan 3E with Labview 2012 (32 bit) on WIndows 7 64-bit - Error Code: -310602 NI-COBS: Unable to communicate with device over communication cable.

Thanks for the info, Kyle. I will probably try to find an older 32-bit XP machine. VM is just not an option for me right now.

Hello everybody,
I am trying to use the DIgilent Spartan 3E board with Labvew 2012 SP1 32 bit. I am able to compile the example code for LED shift. I am however unable to transfer code to the FPGA. I get the following error message:
Error Code: -310602
NI-COBS: Unable to communicate with device over communication cable.
Please verify that the cable is connected to a supported device and that the appropriate drivers are installed.
My system configuration is as follows:
Windows 7 (64 bit) on Dell XPS laptop.
Labview 2012 SP1 (32 bit)
Labview FPGA 2012 SP1
Labview 2012 FPGA support for Spartan3E
Xilinx 13.4 tools
DEFB LV FPGA 2012sp1 support installer
Xilinx USB cable driver v1.3 installed.
I took all the precautions mentioned by others on this forum and others, mainly that the cable must be disconnected before installing the Xilinx cable driver. All software and drivers were installed correctly. I even uninstalled and reinstalled the entire Labview software set I had. I still get the same error.
A few other questions:
1. Is the Xilinx cable different from a regular USB cable of the same configuration ?
2. When I program the FPGA I only have the USB cable connected between my computer and the Spartan 3e board. Should any other cable be connected ?
3. What should be the correct jumper settings for J1 - JP30 (especially J30, J11, JP9, JP6, JP7, etc) ?
I have been at this or over 3 days trying to figure it out. Any help will be greatly appreciated.

When Trying to Install Labview 8.6.1 on Windows 7 Get Error Code -12

When Trying to Install Labview Deveopment Suite 8.6.1 on Windows 7 Get " *** Error: Windows SDK Function Returned an Error (Error Code -12)"
I assume a compatability issue will Labview installer and Windows 7. Is there a work arround?

I figured as much, but maybe if enough peole are interested NI will be pushed to a solution.
It's not that the programm won't run, it's that the installer fails before it even gets installed.
I am using Windows 7 RC Build 7100. It installs and runs just fine in Virtual XP Mode on Virtual PC for windows 7 (http://www.microsoft.com/windows/virtual-pc/download.aspx) which I find works better than compatability mode.
Thanks for your help.

What can I do about "LabVIEW load error code 38: Failed to uncompress part of the VI."

While attempting to load an executable LabVIEW application for LabVIEW 2009 SP1 on a Windows-XP machine when the following pop-up message occurs. "LabVIEW: Memory or data structure corrupt. An error occurs in loading VI 'NI_Gmath.lblib: Backward Bracket Search.VI'. LabVIEW load error code 38: Failed to uncompress part of the VI. The VI is most likely corrupt." What seems odd is that the same LabVIEW application loads fine when logged on as a privileged user account, but fails to load on a private user account.
Attachments:
2012-07-18 LabVIEW Load error code 38.jpg ‏1314 KB

Here's a thought:
So when something is decompressed, a temp folder is often used.
I have no idea why LabVIEW would be decompressing anything, but I suspect it is trying to put the decompressed file into a temp folder where the user does not have write permissions.
In the .ini file for your executable, you can add a line that specified the location of the temp folder to use:
tmpdir=C:\Temp
On my Win7 machine, the location is:
C:\Users\MyUserName\AppData\Local\Temp
On WinXP, it is probably:
C:\Documents And Settings\YourUserName\local settings\temp
Try changing the tmpdir key in your ini file to something to C:\Temp and see if that helps.
- john

Labview: resource not found error code 24 when building executable using 8.20 and dsc module

I am trying to build an executable and I keep getting and error and cannot seem to figure out what is wring. The whole error is "LabVIEW: resource not found. An error occured loading "interface 3.vi" Labview load error code 24: this vi cannot be loaded because it is broken and has no block diagram."
I am using LV 8.20 and DSC 8.2. I am trying to create an executable that has the web server running for using remote panels, i have netowrk published shared variables, connecting to a fieldpoint unit, and I am using the NI system tray icon vis to load the program to the system tray.
I have my shared variable library added as a support file, as well as the lvdsc.ini, and the tray icon files. I have sleected "Enable Enhacned DSC run time support" in the app builder, did not remove any type def,etc.
I cannot get the .exe to run on my development machine or another machine, I get the same error. I tried creating an installer that installed the 8.2 runtime, dsc,fieldpoint, variable engine and manager and MAX.
I could not find anything in the help files on the dsc, maybe someone else has some hints. thanks
Kenny

Hi Kenny,
I hope you are doing well today! What is interface 3.vi? Is it possible for you to post your project over here? Also, I would recommend creating a simple DSC application; and would like you to build it. Do you still get errors?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Installer LV7.1 - LabVIEW load error code 21: An external subroutine required for execution could not be found.

Bonjour,
Je cherche à créer un installer portatif utilisant les drivers NI-DAQmx 8.7.1 et NI-CAN 2.6.0.
Je dispose d'un code LV 7.1 et j'ai installé l'application builder 7.1.
Mais une fois l'application installé sur un PC vierge de Labview, j'obtiens le message suivant:
load error code 21: An external subroutine required for execution could not be found.
Ce message est répété plusieurs fois (pour différents VIs) puis le programme ne se lance pas.
J'ai bien veillé à installer les drivers NI-CAN et NI-DAQmx correspondant au préalable sur la machine cible.
En chercant sur le forum, plusieurs pistes m'ont été proposé:
La version NI-DAQ
L'intégration du Run time Engine
Un problème de DLL
J'ai vérifié ces 3 points mais cela n'a pas règlé mon problème.
Résolu !
Accéder à la solution.

Bonjour,
Merci de ta réponse.
En fait, j'ai bien inclu le runtime engine de Labview qui était effectivement la source de l'erreur.
L'installation de NI-DAQmx v 8.7.1 provoque la mise à jour de la version du runtime engine (passage de 7.1 à 7.1.1).
J'ai donc désinstallé Le runtime engine 7.1.1 (ce qui a provoqué la désinstallation de labview et NI-DAQ).
Puis je suis passé par une version plus ancienne de NI-DAQ (7.2) que j'ai adapté (inclusions de DLL et de VIs).
Les messages d'erreurs ont alors tout simplement disparus!

Is there a LabView example in the use of user defined error codes?

Specifically, I have a VI that tests four arrays of data against various high/low limits. I have pass/fail outputs for 18 tests. I'd like to combine these into an 'error out' cluster with appropriate error codes and messages, for which I've created an x-errors.txt file.
My first question must be trival - how do I just set the 'status' bit of the error stream to let the general error handler then look up the error desription from the file?
Secondly - I can't find an example of this in the technical resourses, amI missing something?
Thanks,
Mike
Mike Evans
TRW Conekt
N.I. Alliance Member, UK
http://www.Conekt.net

There is no example program. There is extensive help on how to do this. Here's the basics.
1) There are two ways to define user error codes in LV6.1. If you are using LV6.0 or earlier, only one method is possible.
2) The 6.0 method involves wiring arrays of error codes and arrays of error code strings to the General Error Handler.vi. These codes will be used to explain any error code which is undefined in LV's internal error code database. Error codes reserved for users which are guaranteed not to be used by NI are from 5000 to 9999.
3) The 6.1 method allows you to create a specially formatted error code file on disk that will be merged with the LV error code database each time LabVIEW launches. For help on this, go to LV's online help, and in t
he Index tab, type
"user-defined error codes, in text files"
(without the quote marks)
4) If you want to set an error into the error cluster, use the General Error Handler.vi again. Wire your error code value to the Error Code terminal (the leftmost-topmost corner terminal). Wire the name of your VI to the Error Source terminal, and wire "No Dialog" to the Type of Dialog terminal (left-side, near the bottom). The error code cluster that comes out of this VI will either be the error in (if one was set) or a new error code cluster with your error and the status bit set to TRUE.
5) The attached demo is written in LV6.0.
Attachments:
Error_Demo.vi ‏37 KB

LabView error code 1940

Similar Messages

Maybe you are looking for