LabVIEW 9.0f2

Similar Questions

• LabVIEW 13.0f2 crashes when text cut of some free labels on the block diagram

  While reviewing the documentation of a VI, I faced a LabVIEW crash. I can reproduce it in LabVIEW 13.0f2 with the following code.  Can anyone confirm that the content 'def' Cup free label and trying to stick to the free label with "ghi" produce error 0xBC0BF185?

  I can't reproduce this problem by any other cut and paste between the free labels on the left side of the BD.  The accident occurred only when 'def' cutting and trying to stick to the "ghi".

  

  Hi all

  I looked into this, and it is more general than just the madness in the label. I dropped the CAR 442743 for this behavior. It's an accident that can occur when cut and paste text between the free labels in 2013 of LabVIEW with the disabled automatic tool. This is related to the CAR 408955 (deadlock occurs when deleting a comment with the automatic tool off) that has been corrected in the Patch of f1 2013 LabVIEW. This case was not covered by that fix and will be fixed in a later version.

  Thank you

  Jeff Peacock

  Product Support Engineer | LabVIEW R & D | National Instruments

• Problem with LabVIEW 9.0f2 and VISA 5.0 on Mac OS x 10.6

  Hello

  I'm using MacOSX 10.6 and Labview 9.0f2. I installed the lates VISA (5.0.0) drivers, as they are the only support OSX 10.6.

  Now, I try to run the "basic series write and read" example and get the following error:

  Error 1073807343 has occurred to the property node (arg 1) visa set up a Serial Port (Instr) .vi-> basic series writing and Read.vi

  Possible reasons: VISA: information about insufficient localization (Hex 0xBFFF0011) or the device or resource is not present in the system.

  As I am a newbie to Labview, I'd appreciate any help on this...

  Thank you

  Daniel

  Hello

  You do not have a device series on behalf of resource, you use to write and read and take?

  Did you check with Max OR and log on to this device.

• VI version (13.0b0) is too old to convert to the latest version of LabVIEW (13.0f2)

  Trying to generate an executable in LV 2013 SDS using the specifications to build > installation script I've used in the past.

  LabVIEW version is 32-bit 13.0f2 (windows XP)

  It works fine until the user tries to run the application installed on the 64-bit Windows 7 machine.

  This results in the following error message:

  

  I tried to compile mass the folder in which the highest level VI is located in the source distribution, nothing helps.

  I even installed it on my development machine and the same message pop up it when I run the executable file.

  Any suggestion?

  I found the reason of my troubles after a few exchanges with the support of NEITHER: me!

  In short, I forgot that when you choose 'install' like build specifications and then 'building' the installation program, it must point to a source file that is the desired executable.

  But first, he must create a build specification that builds this AND build executable as executable (at least the way I go about it). I just forgot to do this step (I do not generate installers that often) and the installer was just reuse an old exectable I had created during the beta.

• 'error' is not like a sub - VI

  Hi people:

  It's probably more a basis LavView coding problem. I'm having a strange problem where Labview 13.0f2 is not my 'mistake' sub vi as output to continue my bus error string. I have attached the .vi for all who want to take a look and state the obvious for me. Keep in mind, I'm a n00b LavView so be gentle. It is a sub .vi who wrote in data acquisition, and I try to bring to DAQ - mx. Feel free to make any comment about the .vi as a whole.

  Thank you.

  Andrew

  You just right-click on the icon.  You right-click on the part of the connector.  From there on, spending Patterns and the 4x2x2x4 pane is in the bottom row, third from the right.  You will then want to reorganize where your controls and indicators are connected on the side of the connector.  It is recommended that your error is in the lower left corner, and your error is on the lower right corner.  Then on the left, outputs on the left.

• Creating application builder error

  After installing Labview 9.0f2, is no longer possible to build the application

  Depending on the anti-virus, an exclusion zone should be created on the directory where the exe file are created.

• Problems after update IV calls AudioMaster step

  I'm about to deploy the system to my test, and I ran into several frustrating problems.  After trying to update VI calls, I'm more able to run my Audiomaster steps.  I also can not change the treatment of signals, change the graph limits or change the key settings in the AudioMaster steps.  I am able to change the configuration.

  I have attached an error one of the AudioMaster steps.

  Error running substep "function Keyparameter".
  Open in mxLT VI reference is measured in Teststand.vi-> mxLT function of key parameters for TestStand.vi-> mxLT function key for TestStand.vi.ProxyCaller parameters
  Error loading VI ' mxLT vector result viewer envelope.vi.
  LabVIEW support 10 error code: version VI (8.2) is too old to convert the last version of LabVIEW (10.0f2).

  The VI path: C:\Program Files\microLEX Systems\Common Files\PrivateCommon\mx
  LabVIEW: Version VI is still too early to convert the last version of LabVIEW.

  6.2 AudioMASTER (current version) is built in a dll, except the plugin LimiTEST (parameter Key, signal processor, limiter chart) that must run in LabVIEW 8.2 (Run Time). In the next version AudioMASTER 6.3 (projected release 4th quarter 2011) LimiTEST is included in the dll (build in LabVIEW 2009).

  The trick in Teststand deployment is to build the application (the operator + sequence interface) on the developer machine without including the AudioMASTER components in the build, then installing the sequence and AudioMASTER (using Installer AudioMASTER) on the target computer. This will ensure that the correct registry on the target computer settings for AudioMASTER.

  AudioMASTER Vi should not be compiled LabVIEW 2010.

• remote panel

  Hello

  I have a server and two clients connected to the server through remote façade. I want to reduce the waiting time to the order of a customer to another. I changed the "time limit command" field in web server under Labview options. When a client request time-out control starts correctly (I see the situation since the remote control panel Connection Manager) but when he finished 1: contdown restarts it. The same problem is described in this http://forums.ni.com/t5/LabVIEW/Remote-Panel-Connection-timeout-problem/td-p/405544discussion, but actually I'm with Labview 15.0f2. Any suggestions?

  Thank you

  Gimondi Alex

  In the end I managed to handle the problem.

  Play with the nodes of property I noticed that control release property do not work with the VI in a project if a customer has control, indeed the property work if the server has the control. Fortunately, lock control property works on the side of client (giving property the control on the server).

  With the Vi simple attached, I look at if a client has requested control and in this case, the server hangs and unlock the control so the customer waiting eventualy receive control.

  Hope this can help someone!

• Import the chain programmatically to reentrant VI

  I'm working on a multi-language application that includes a reentrant VI. I managed to import a file of strings not reentrant screw, but seem to have problems with import of channels in a reentrant VI. I'm basically calling the VI environment dynamically in a loop (opened VI ref, import a file string, run VI). The first iteration is error-free, but after that it returns the error code 1000.

  I know that the import of channels function does not run when the VI works and that's why I get this error, but my VI is returning and a set of pre-allocate clone for each instance. This behavior is expected when using the import of channels function while repeatedly calling a reentrant VI? If so, is there a work around this issue?

  Thank you

  Cristian

  (With the help of LabVIEW 9.0f2)

  
  

• Problems with the implementation of 32 or 64-bit DLLs in LabView 2013 13.0f2

  Dear Sirs and Madams,

  I try to order a motorized device (MGZ30-WORD thorlabs) with LabView 2013 (32 bit), product version 13.0f2 on a PC under Windows 7 64-bit. Unfortunately, there is no support of LabView for the WORD MGZ30, which means that there are no libraries or VIs for LabView.

  First of all, I want to describe the component or rather its functionality. It is connected to the PC via USB and managed by the v5.0.2153.1 Trinamic Virtual Serial Port Driver. If you wish, for example, adjust the position of the device, there is a small program (written in C++ by the seller). There are 2 different folders for 32 and 64-bit, each containing a .exe, .dll two (a ThemeControl.dll called, who apparently does not have the feature described in the h.file, I want to talk about later, and a ThorZStepper.dll called), a .lib (ThorZStepper.lib) file and an .xml file (ZStepeprSettings.xml, which contains the used COM Port and baud rate information). In addition, there is a folder that contains the driver and a folder called "SDK", that contains the subfolder with a .h file, samples and once more the files mentioned before.

  To use your device, you must modify the COM - ID in the .xml file and run the 64-bit .exe as administrator.

  First of all, I tried to use the VISA-USB-controls, which worked well with another device. However, he did not for the WORD MGZ30 as I did not have the possibility of obtaining the necessary chains of command although I used a sniffer port. Observed communication seems to be more complex than I expected and I was unable to extract the relevant information. To add, the device seems to communicate constantly with the PC even if it is inactive.

  The next idea, which came to my mind was to put in place the .dll files. Therefore, I used the import via Tools/Import/SharedLibrary function and the only h-file that I found in the file and the dll file which stood next the .exe in the folder of 64 bit. LabView created a file .lvlib and I got access to a few screws, which have also been described in the header file. The problem is that I can't run these screws because the .dll file is 64-bit while LabView is only 32-bit (at least, LabView suggests that this is the error.

  After that, I tried the same thing using the same header file (there is only one), but using the .dll file located in the folder of 32 bits. When I now try to run the files, execution of works, but I get an error message "call library function Node in ThorZStepper32.lvlib:Find Devices.vi. There are also a few screws, which do not generate this error, but will not work.

  My next test was to use the "call library function Node", as well as documentation in the .h file, but it didn't work. I don't know if I missed something or the 32-bit .dll file does not work on 64-bit operating system. Could you please help me to use the "call library function node" to investigate the weather that the 32-bit dll does not work properly?

  Please find the file h., (html.zip) documentation of the h.file and the VI, it must indicate the position, attached.

  Best wishes and thanks in advance!

  
  

• Bug: Call from the DLL Windows 7 to disable the monitor message block 10.0f2 LabVIEW

  Hello

  I wanted to connect this bug on the forum. I already connected this with the support of the United Kingdom NOR: CAR # 286873

  I was trying to find a way to turn off an LCD laptop during the measurements. I tried to reproduce this

  http://codereflect.com/2009/04/03/how-to-programmatically-turn-onoff-your-monitor/

  who uses windows messaging.

  I found the joint monitor - 1(vi) somewhere on the forum that seems to of the foregoing. However when I run the VI it blocks 10.f2 LabVIEW on Windows 7 32 bit.

  see you soon

  David

  take the stdcall calling convention

• Signal Express version unknown problem with Labview VI

  Hi all

  I am trying to run 2010 Labview Signal Express VI. It gives me "unknown version" problem. When I checked for Labview versions, he said 10.0f2 and Signal Express can read the version of LabView 2010. I don't understand this. 10.0f2 is not just a patch for version 10.0? I will appreciate if someone can help me with this.

  Kind regards

  Kanu

  Hi Kanu,

  I tried to write a simple VI and its importation to the Express Signal and I have not had any problems. I use 32-bit LV2010f2 and Signal Express 2010. I have attached the VI I used so that you can try it yourself. I followed the instructions of this KB to create a distribution of the source file. If you follow this KB and still can't make it work, can you please post the VI?

  Thank you

• LabVIEW VI 2013 crashes on opening

  I made a small change to this VI and now I get "Exception: exception Noncontinuable (0xC0000025) to EIP = 0x00000000 Version: 13.0f2 (32 bit)" whenever I open it directly or by project. I was poised to deploy and am really under the gun. I tried to move location so he was looking for his sub - vi, but it still does not work. Tried with a PC of colleagues as anything does not. Tried to save it as the previous version, but it hangs when I try to do. Compilation of mass I tried, but it hangs when I try it as well.

  Can anyone else open it?

  I was able to open it, but missed me one of the kits of tools you use. I have attached a re-recorded version of the VI that I opened.

  Kind regards

  Jeff Peacock

  Product Support Engineer | LabVIEW R & D | National Instruments | Certified LabVIEW Architect

• LabVIEW hangs with in the intensity chart

  Twice this morning, LV2010 weighed ("program is not repsonding") when I tried to put a graphic on my front intesity.  In one case, I copied the graphic in an example program OR my VI.  When I tried to reposition the chart on my forehead panael, LV unresponsive.  Same thing happened when I tried again; the second time, I have the graph of the intensity of the palette of tables and graphs.  I LV 2010, version 10.0f2 and windows XP.  Thank you.

  Hello!

  The following KnowledgeBase explains why this could happen.

  http://digital.NI.com/public.nsf/allkb/9A8FB888BFCED9658625721500434A31

  Basically, this table might contain a large amount of data, and when you move, LabVIEW must reorganize all this information in RAM as you move the chart. You can write smaller data, or save all data in a separate table in the table at the end of the execution so you can save it. If you want to view a chart later, simply enter it in a graph.

• LabVIEW 2009 freezes when recording vi

  Hello

  My LabVIEW 2009 v 9.0f2 (64-bit) crashes 20 seconds every time he saves vi.

  Has anyone seen that?

  Is there a fix for it?

  Thank you

  Pawel

  Pawel says:

  This time LabVIEW does not quickly record charts with some data in it.

  Sorry, could you clarify:

  • You have graphics with huge amounts of data by default?
  • You have graphics with sizes of the big story?