Compatibility of LabVIEW 2009-2012

Similar Questions

• LabVIEW 2009 linux crashes when editing a control, or a constant of resources VISA

  Linux crashes when I click on a constant resources VISA (block diagram) or control (front).  This happens on LabVIEW 2009 SP1 32-bit for Linux on CentOS (similar to RedHat 6.3) 6.3.  I have updated drivers VISA 5.1.2 and that did not help.  Thanks in advance for any ideas of five Linux guys out there.

  Hello Jason,

  My problem has been resolved with LabVIEW 2012.  To answer your question, LabVIEW would crash only trying to select another device in the list.  Thanks for your help.

  Kind regards

  Marvin

• Install the LabVIEW DSP Module on Labview 2009 Professional

  I have LabVIEW 2009 professional and I try to install the LabVIEW DSP Module on it. I have LabVIEW DSP Module 8.6, and I think that this is the final version. However, when I tried to install it, it says you should have LabVIEW 8.6 on your system.

  What should I do?

  Hello Brandon,.

  I did run the LabVIEW 8.6 DSP module, you must have LabVIEW 8.6 (compatibility table), which can be installed and run in parallel with LabVIEW 2009. I apologize for the inconvenience, but 8.6 is the latest version of this module, so you'll need to buy LabVIEW 8.6 for use.

  Kind regards

  Deborah Y.

• MathScript node: an error internal mathscript: 64-bit LabVIEW 2009

  Hi people.

  I have an installation now LabVIEW 2009 9.03f, Vision and Advanced Signal Processing Toolkit, all 64-bit versions on a new computer, so that I can convert a code from 32 to 64-bit.

  I tell myself that I will address the errors one by one and this is the first.  I have a VI with mathscript node and the VI, who instructed and ran very well in the 32-bit environment, is now broken and giving the error "mathscript node: a mathscript internal error."  My main concern - is mathscript unsupported in LabVIEW 64-bit right now?

  I enclose the VI.  Any ideas are appreciated.  I need to get this working.

  In addition, NEITHER is there a special forum of 64-bit we should publish in the future, or create to post on?

  Sincerely,

  Don

  2009 help

  LabVIEW MathScript is a language based on text that you can use to write scripts and functions. You can process the scripts using LabVIEW MathScript in the Window of LabVIEW MathScript or a MathScript node. When you create a LabVIEW MathScript, you use data types supported.

  The MathScript syntax is intuitive and logical syntax essentially based on the standard mathematical and computer programming terms, mandate of widespread and common use truncation or descriptive abbreviations and concatenations of standardized terms. The Window of LabVIEW MathScript and MathScript nodes are able to process files that you create using the MathScript current syntax and, for backward compatibility, files that you created using legacy MathScript syntaxes. The Window of LabVIEW MathScript and nodes MathScript can also process some of your files using other textual syntaxes, such as files that you created by using the MATLAB® software. Because the MathScript RT Module engine is used to treat the scripts in the Window of LabVIEW MathScript and MathScript node, and the MathScript RT Module engine can't stand any of the syntaxes, not all existing text scripts are supported.

  (64-bit LabVIEW) LabVIEW MathScript is not supported in LabVIEW (64-bit).

• LabVIEW 2009 x 64 and generator application

  Hello

  My organization has just got a license for LabVIEW, so I just installed 2009 x 64.

  My question is this:

  If I build applications written using LabVIEW 2009 x 64, they only work on 64 bit computers? I would like to test this, but my two computers are 64-bit computers. I had a brief look through the construction specifications, but it doesn't seem to be something on the 32/64-bit compatibility.

  Thank you.

  J

  Does that help?

  http://digital.NI.com/public.nsf/allkb/71E9408E6DEAD76C8625760B006B6F98

  Can q. I run an executable built with LabVIEW 64-bit on a 32-bit computer?
  A. you cannot run the executable or LabVIEW 64 - bit, Run-Time Engine development system on a 32-bit computer.

  Can q. I run an executable built with LabVIEW 32-bit on a 64-bit computer?
  A. Windows can run executables for 32 bit on a 64-bit computer. Therefore, the development system LabVIEW 32 - bit Run-Time Engine and executable can be run on 64-bit Windows.

  Can q. I have the 32-bit LabVIEW and LabVIEW 64 bit installed on the same 64-bit machine?
  A. Yes.

  Can Q: I build a 32-bit version of an executable file for the 64-bit LabVIEW application builder?
  A. currently isn't an option to create a 32-bit version of an executable file from the 64-bit LabVIEW application builder.

• Tap the Navigation Palette missing in LabVIEW 2009 Panel

  Hello

  I developed an application using LabVIEW 8.6 with the touch panel module and a TPC-2012 (Windows CE). I've now upgraded to LabVIEW 2009 and I'm trying to run my code in a TPC-2512 (XP Embedded), but the 'Touch Panel Navigation Palette' I used previously to be found in the new facility. In my view, there is a new range of "Navigation controls" in 2009, but I would like to avoid having to re - design my app with new controls.

  8.6 navigation controls are no longer supported in LabVIEW 2009 or have I missed something? The TPC is displayed in the Project Explorer and MAX, and I'm able to deploy and run applications on it. But the old vi navigation do not work and as I mentioned before, the palette is not even appear when you try to change the vi on the development computer.

  Any help would be appreciated.

  Thank you

  Hello

  The navigation screw touch panel are not displayed to the top, because you are currently using the TPC-2512. If you take a look in the Help file on the Navigation, it states: 'installed with: Touch Panel Module.» This topic can not match its corresponding palette in LabVIEW depending on your operating system, or the licensed products and the target. "I checked this with both LabVIEW 8.6 and LabVIEW 2009 targets. Due to the different architectures, you get a different set of palette (Windows CE vs XP Embedded).

  -Zach

• LabVIEW 2009 32 bit does not not on xp 64-bit

  Hi all

  I tried to upgrade to LabVIEW 2009 LabVIEW 8.6 on the XP machine 64-bit windows. After about a deletion of 2 hours of installation 8.6 and later of LV 2009 it turns out that the device drivers are not compatible with a 64-bit computer. At the launch of LabVIEW 2009 (32-bit), an error box is displayed indicating that it is corrupt or missing files and to fix this using the control panel etc. I tried this and still the same error occurs and LV refuses to start.

  All license files are correct and the components are enabled.

  Someone knows how to fix this? Or do I go back to 8.6 and cancel my subscription?

  Second, I use a firewire camera and was informed that neither IMAQ legacy are more supported and go to ni.com/ifo and enter legacy1394 to see how to download drivers for that etc. I find myself on a page that says no "authorized".

  Any help appreciated gratefully.

  Dear Leeser

  Since 2006, National Instruments has annually released a new version of LabVIEW each month of August in order to establish a more predictable release schedule. This allows users to better plan the new developments and improvements for future versions of LabVIEW. In addition, this year, NOR changed the name of the product to LabVIEW + year (for example, LabVIEW 2009) reflecting the year of the release and setting the stage for future annual editions of LabVIEW. Please see the following site for more information on this:

  http://www.NI.com/LabVIEW/product_lifecycle.htm

  What about Windows XP 64-bit it is not officially supported by hardware or software drivers. For a list of drivers who have been known to work, please see the link below:

  http://Joule.NI.com/nidu/CDs/fn/p/SN/N19: Windows.7809/lang/en

  Now with Windows Vista x 64 is a 32-bit compatibility of excellent "windows on windows" mode which allows our drivers work correctly. In regards to LabVIEW 2009, there is now a dedicated 64-bit version is recommended for use with 64-bit operating systems. Yet once Windows XP 64-bit is not officially supported.

  More details on the compatibility of Windows XP x 64 is located in the following article:

  http://digital.NI.com/public.nsf/allkb/C4EC0C87B6D70AA886256E61006568C8?OpenDocument

  I hope this helps to clarify some things.

  Kind regards

• LabView 2009 (64-bit) IMAQ GetScreenSize?

  Hello

  No one attempted to use of the vi in LabView 2009 64-bit GetScreenSize yet?

  Is not executable more? We have replacements?

  Thank you

  Hello

  IMAQ GetScreenSize is obsolete. Refer to KB: compatibility library when upgrading from old Versions of Module Vision Development.

  Instead of this function, you can use Display.Primary Workspace or Monitors Display.All property node.

  Andrey.

• Impossible to find the field read and write VI in labview 2009

  where is the field point to read and write VI in labview 2009

  According to the version of LV, BT pallets can be sensitive to the context. Try to create a project and add a fieldpoint target to the project.  Right-click on the target of FP in your project and select new > vi.  Now FP functions should appear

• Switch Executive stops working after LabVIEW 2009 installed.

  I just installed LabVIEW 2009 and now Switch Executive 3.0 does not work.

  NISE open session vi returns 0 instead of the valid session ID. It does now with LabVIEW 8.6.1 too.

  Everything looks OK in MAX.

  Any suggestions?

  Hi Pirkola,

  I'll try to replicate that.  I understand it is a returned 0 for a session ID.  Is there an error returned as well?

  Thank you!

  Chad Erickson

  Switch Product Support Engineer

  NOR - USA

• Failed to retrieve the DIAdem DataFinder research data, using data-finder toolkit LabVIEW 2009

  I am facing problem to retrieve the DIAdem Datafinder data.

  At first, I developed this project in LabVIEW 2010. But because of a problem that I met in LabVIEW 2010, I thougth to work on the project in LabVIEW 2009.

  Then, I reused the project that I created using LV 2010 using option economy for the previous version.

  When I tried to retrieve the data from the tiara using data finder toolkit. I got a 305505 warning. Please see the attached message of Warninig.

  But I have not seen this warning while I was working in LabVIEW 2010 and also, I was able to get the data from the tiara.

  Please suggest me a way to solve this problem.

  Hi Nanda,
  There is a bug when using the SDK use in combination with DataFinder Toolkit 2009.
  This bug is already fixed in LabVIEW 2010 and use SDK 2010. But as you said there is another question in LabVIEW 2010, forcing you to LV 2009.
  I suggest you use LabVIEW 2009 with use SDK 2009 and DataFinder Toolkit 2009 and instead to use the "Waveform.vi results" to read the search results, I would recommend to use the screw storage. I spread your example VI and it attached to this message. You will still see the dialog box to search for "lvStorage.dll" but it will automatically disappear and the VI works anyway because in this case LabVIEW will find the dll itself.
  My extended VI uses the '_openWithRoot.vi' to open a file with a different use than CT or PDM. This VI is also described in the following knowledge base article: http://zone.ni.com/devzone/cda/epd/p/id/4181
  With LabVIEW 2010 use support has been enhanced and fully integrated in the standard palette of storage screws. So in LabVIEW 2010, you can replace the "_openWithRoot.vi" with the 'Open Data Storage.vi' standard but with LabVIEW 2010, you can also use "Waveforms.vi results" to read the search results.

  I hope this helps.

  Kind regards
  Eva

• LabView 2009 Service Pack 1 does this cause a problem with the MAthScripts for lo

  All,

  I just installed Service Pack 1 for Labview 2009.  All of my code that loops in my MathScripts now lets my MathScripts does not compile.  Have a clue what I do?

  Thank you

  Rich

  Windows XP (32-bit)

  LabView 2009 uninstalled, reinstalled after you have removed all files related to 2009.  SP1 installed, then applied for LabView and MathScript.

• LabVIEW 2009 Crash when record for previous

  I'm having a problem when you try to save a VI in LabVIEW 2009 to a previous version of LabVIEW, in this case 8.2, but itseems crashing no matter which version I chose.  I've narrowed the problem down to this:

  If the vi contains a structure of event I get the following error: unrecoverable internal error: 'MemoryManager.cpp', line 547

  If I remove the structure of the event, she records very well.  I even go the error if I create a vacuum vi and drop an empty event on the diagram structure.  No control, no other code.

  Is this a known issue?  Is this a problem with my copy of LV?  Is there a solution?  Removal of the structure of the event in the present application is not an option.

  Thank you

  Rob

  So the solution is to save to LV 8.6, then open in 8.6 and save here to earlier versions.  It works, I have not tried to save 8.6 initially.

  Rob

• Narrow ARM of SPI VI reference works do not for me LabVIEW 2009.

  I use LabVIEW 2009 Embedded for ARM in collaboration with the Council of development of LM3S8962 and the MCP3008 10 - bit ADC chip. I'm trying to use the base screws of SPI to communicate with the MCP3008 - see the attached excerpt from VI to my current attempt. I can initialize the SPI reference, read two bytes of data from the ADC, but when I try to close the reference, the application crashes. If I am the narrow ARM of SPI reference VI in a diagram to disable, the program terminates normally, and I get to see my two bytes of data printed on the OLED. Any ideas?

  Thanks in advance,

  Stuart

  Thank you!

  Who takes care of the immediate problem. I really appreciated the quick response!

  Stuart

• MCB2400 LabVIEW 2009 Embedded build error

  Hello

  I am evaluating MCB2400 with embedded LabVIEW 2009. Whenever I try to compile the application (even with a VI empty, no code block diagram), I get the following error:

  "" [15:35:15] status: error ""
  which connects...
  .\Obj\LabVIEW.axf: error: L6047U: the size of this image (16802097 bytes) exceeds the maximum allowed value for this version of the linker
  Target not created

  Status: Build failed. »

  I do not know whythe size exceeds even if I tried no code at all (white VI)!