LabVIEW 2009 supposed to be backward Compatible?

Similar Questions

• Is the tool provided with the works of Labview 2009 with LabVIEW2010

  Hello

  I use currently LABVIEW 2010 want to know about toolkit provided with the dvd of LabVIEW 2009

  is compatible with the labVIEW 2010

  Thank you

  Check out this link.

  http://www.NI.com/support/LabVIEW/lvtool.htm

  If the required toolbox does not "(ou supérieur) ' after the requirement for 2009, or specifies LV2010 it is not compatible."

• LabVIEW 2009 .exe works only with windows 2000

  I created a simple vi with Labview 2009 for resetting a counter in the registry key. I changed it to an exe. The program works well on any machine with XP, but it does not work on the machine, that I need on which is running Windows 2000 SP4. I have installed the runtime of 2009, but I keep getting an error when it starts the vi is not executable and I need the full development to correct errors. But like I said it works everywhere else. I tried other exe wrote in LV2009 on this machine and they work. Is there something in my vi which is not compatible with Windows 2000?

  Thank you

  dkfire wrote:

  If you build an exe on a XP machine, then it will work only on XP.

  You need generate the exe on a Windows 2000 machine to make it work.

  Simply not true - even close to not being not right.

  Chris,

  My guess is that the .NET component is not present on the pc of w2k.

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

• can I open a vi created with labview 2009 on worm Labview 8.5?

  I have a vi created with Labview 2009 and I want to open and run the vi in Labview 8.5.

  It opens to 8.5

  Can I save the vi since 2009 in a format that is compatible with 8.5?

  If you click the file menu in the toolbar of LabVIEW, you should see a "except for the previous version. If your vi does not have all the features that are specific LabVIEW2009, you should be able to save it to 8.5.

  LabVIEW is generally open earlier versions, not the other way around. I say generally because there are a few points that have changed drastically, such that you have to use an intermediate version to make the vi up to a more recent version.

• Imaging Source DFG/SV1 acquisition card is not correctly recognized in LabVIEW 2009

  I have an Imaging Source DFG/SV1 frame grabber/capture card (I think that this example uses a Bt878 chip) that I am using with LabVIEW 2009 (Fall edition 2009 academic Site license), including elements of acquisition of vision (NEITHER Vision, NOR-IMAQ (4.3) OR-IMAQdx (3.4), etc.). I have all the latest sources of imagery support drivers and software for the Board of Directors (http://www.theimagingsource.com/en_US/products/grabbers/dfgsv1/ drivers: v6.0.3.0, IC Software v2.1 and IC Imaging Control v3.1) with drivers being compatible DirectShow. The DFG/SV1 is detected in MAX under devices NOR-MAQdx / DFG/SV1 / cam0 and I can grab and preview images, however to 320 x 240 resolution, I have a higher resolution camera and know that the jury is capable of greater resolution using IC software manufacturing and also via TWAIN with ImageJ software drivers. Interesteingly, if I try to acquire an image of the card purchase using the Vision Assistant, the DFG/SV1 card is not recognized as a card acquisition, but listed under IEEE 1394 or GigE peripheral, revealing with it being direct device that I can't understand. Despite this I can acquire images, but I am limited to 320 x 240 format and change the type of image (RGB, UYVY etc) causes an error. Once again, oddly enough, I can use "enter and select mode example VI" which should only be compatible with IEEE 1394 cameras.

  I'm not sure why LabVIEW is not seen this card properly, I contacted Imaging source who were also intrigued by the fact.

  Any information on how this could be resolved would be much appreciated.

  Thanks in advance.

  Hi OCastell,

  With this Council Imaging Source, the only interface supported with drivers of NI Vision Acquisition is through using IMAQdx DirectShow interface. It is possible that their DirectShow driver does not properly support all of the capabilities of their Council. Given that ICR software and TWAIN support can be routed to a different implementation of one of the DirectShow support, you can see the different features available. Unfortunately, you probably go through Imaging Source to determine why their DirectShow driver does not support the full resolution. You can confirm that it isn't IMAQdx this limiting trying other software such as Windows NetMeeting or AMCAP DirectShow and see what capture resolutions are listed.

  Because the DirectShow interface is managed by IMAQdx driver, it will not be detected as a framegrabber IMAQ using the IMAQ driver. This is expected since it fits in the same category as firewire and GigE Vision cameras and is supported with the IMAQdx driver instead.

  The "Grab and select the Mode" example VI isn't really specific FireWire, although he was certainly intended to highlight the various video modes that generally expose FireWire cameras. Since the DirectShow devices are similar and have several selectable video modes, it's why he's probably working. In any case, IMAQdx abstracts usually differences between all supported camera types and in general a single VI can run on all cameras IMAQdx-taking in charge unless you rely on buses or the camera-specific features.

  Regarding Vision Assistant marking the camera as 'IEEE 1394 or GigE', I think it's just an aesthetic issue (which may already be fixed in new versions). When IMAQdx was out, these are the supported types of cameras and so Vision Assistant was trying to say clearly what driver was used for the type of device. Now that IMAQdx supports a multitude of new interfaces (including DirectShow and some IP cameras) that the label is inaccurate.

  Finally, looking at the specs for this capture card, it looks like a standard reference BT878/848 model and then you could try potentially replace your Imaging Source driver with one here:

  http://BTWinCap.sourceforge.NET/

  I used this with a with IMAQdx BT878 capture card and can get it to capture an image full resolution (but of course, your results may vary...). It goes without saying that this solution using DirectShow is much more limited than using an industrial camera on 1394/firewire or a framegrabber IMAQ.

  Hope this helps,

  Eric

• LabVIEW 2009 + Labview 8.6 vision = work not...

  Hello

  At my University, I got a license for Labview 2009 + Module Vision 8.6... Now, I installed Labview first of course. And when I was done I installed the vision module. The two facilities went very smooth. Now when I run labview I do not have access to any labview vi vision that must be provided.

  Like what I have read here http://www.ni.com/support/labview/lvtool.htm#vision_development the module must be compatible with labview 2009... If someone can explain to me why it is not appear in labview 2009?

  Hi Wouter,

  Please visit the following link: http://digital.ni.com/public.nsf/allkb/244E6DDF9A92A6CD8625730100629047?OpenDocument

  The NI Vision Development Module is not compatible with LV 2009.

  With sincere friendships.

  Casper

• 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

• Java7/JDBC 4.1 not backward compatible - DataSource getParentLogger()

  I tried to upgrade to Java 7 and had a nasty surprise. Java 7 is NOT backward compatible! After more than 15 years making the Java, this is the first time I encounter such a thing.
  
  The new 4.1 JDBC, now included in Java 7 requires that implement data sources:
  
  java.util.logging.Logger getParentLogger() launches SQLFeatureNotSupportedException
  
  It broke the a custom data source I use. The solution seems simple at first, implement getParentLogger. But I have encountered the following problems:
  
  (1) the documentation for this method sucks. It does not say much.
  
  (2) intuition makes me think that the simplest implementation is to just throw SQLFeatureNotSupportedException and JDBC will probably catch the exception and ignore any logging expected at this level. But we don't know if it is actually what he does.
  
  (3) another option would be to return a parent logger... except that I use jBoss 5.x and jBoss uses log4j for its record, not JUL. A real implementation would come back somehow a java.util.logging.Logger benefiting somehow a log4j logger. Someone suggested looking at slf4j, but it is not clear to me how I would use it for this task.
  
  Since Java 7 has been out for some time, I hope I'm not one to encounter this problem with the sources of data and logging log4j. Probably should already be advised on how to handle this.
  
  Can someone point me to a solution?

  I asked someone better than me and got:

  If an application does not support, or if the implementation of the data source is not
  use java.util.logging, a SQLFeatureNotSupportedException must be lifted and the
  the caller is supposed to handle this.

• 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