LabView error code 1940

[brantdwight]

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

[Chris_K_]

Hi, I am unable to recreate the error that you are getting when I compile your code, into an EXE or a DLL.  Error 1940 states that the VI was reset because the weighting changed.  This might be helpful to you as you have a better understanding of what is going on in your VI.  Since I am not able to get that error when I run your program, it might be associated with your system.  What version of LabVIEW are you using, and what version of the SVT toolkit are you using?  When you run this as a VI do you get the error?  How are you running the EXE and the DLL? Are you running multiple instances of them? 

Let me know and we can continue to trouble shoot.

Chris K

[brantdwight]

Hi Chris,

Thanks for the reply.  I'm using LabView v8.2 and v3.1 of the Sound and Vibration toolkit.  I haven't tried running this as a VI because I don't have LabView on the machine that I'm running it on.  I'm running this on a PXI-8105 controller with 1 GB or DDR2 RAM, in a PXI-1045 chassis, and a PXI-4461 sound acquisition & generator.

I'm not running multiple instances of the program. I only get the error when I first launch/call the .exe or .dll. I don't receive the errors after the first run. I've also seen error 1970, what's the description for this? Where can I find the descriptions for error codes? When compiling the VI into an .exe, is there a way to make it not automatically run (play button is engaged) when it's opened? Could that be part of my issue?

Thanks,

Luke

[PBear]

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.