LabVIEW 2009 installation, one of MS Office Excel VI is broken

Similar Questions

• LabVIEW 2009: Installation of scripts VI after Servicepack 1 - no effect

  Hello

  I installed VI Scripting for LabVIEW 2009 after applying on LabVIEW 2009 Service Pack 1 and I don't know how to access the nodes beautiful blue property...

  Thank you

  Peter

  It seems that the XP version of 2009,1 script tools are now available here.

• Is there an Excel to TDM plugin for LabVIEW 2009

  I downloaded the Excel to TDM plugin and could not run. Dialog error usiReg said "this configuration file was created with a new version of the ICU and can not be used with the software you have installed." I installed LabVIEW 2009 SP1 and the .net version is 4.0. Y at - it another version of the 9

  the plugin I can use? Is there something else I can do, or am I just out of luck, until I update?

  Hello

  the functionality to open Excel files has been added to the ICU starting with version 1.8. However, the ICU in the manner described above upgrade you will register to use ExcelTDM and make it available through the _openWithRoot.vi in LabVIEW 2009. Simply install or DIAdem 2010 NI LabVIEW 2010 as a demo version.

  Please see also the comments from readers on the page of ExcelTDM use, a client has requested the use of using Excel in older versions of DIAdem:

  ExcelTDM use

  Greetings,

  Uwe

• LabView Run - Time Engine 2009 installation failure

  Hello

  I have problem to install Labview Run - Time Engine 2009.

  This error occurs:

  Die Installation von NI VC2008MSMs x 86 ist auf Grund of the following Fehlers fehlgeschlagen.

  Auf den Windows-Installationsdienst konnte nicht rarely werden.

  Die kann occurrence, wenn Sie Windows im abgesicherten Modus implement oder der

  Windows-install extension installed ist nicht. Wenden Sie sich an den Support, um Hilfe zu receive.

  (The installation of the NC is VC2008MSMs x 86 has failed due to the following error.

  The Windows Installer Service could not be accessed. That may occur when you run

  Windows in safe mode or Windows Installer is not correctly installed.

  Contact your support team.)

  I tried to reinstall and reregistrate program windows installation, I tried to upgrade the installer from windows to version 4.5

  I installed Microsoft Visual C++ 2008 Redistributable-x 86.

  IM runing Windows XP Service Pack 3

  (Microsoft Windows Version 5.1 (Build 2600.xpsp_sp3_gdr.100427 - 1636_ Service Pack 3))

  I have no problem installing other programs, for example, can I install runtime labview 7.1.1.

  So my question is:

  How do to solve this problem, how can I make a Labview Run-Time Engine 2009 installation on this computer which gives me the error described at the beginning?

  Best regards

  Simon

  Now I have solved my problem.

  The solution was to raise and to build my code in Labview 2010.

  But the question of the installation contains yet to install LabView Run-Time Engine 2009.

  I don't think it's associated Windows Installer, because I can install everything on my computer in addition to LabView Run-Time Engine 2009.

  I can even install LabView Run - Time Engine 7.1.1 and LabView Run-Time Engine 2010.

  So, my solution was to jump using LabView 2009 and install LabView 2010.

  Best regards

  Simon

• Even police "Tahoma: pt 8 looks different in LabVIEW 2009 and MS Word (EXcel, Windows, the Menu bar".

  I developed a LabVIEW 2009 application, that uses only the "Application Font" for each where block and front panel. LabVIEW.ini I'm goon to set appFont = "Tahoma" 8

  Because when I look at my computer, display properties > appearance > advanced > Item = Menu then it seems it use Tahoma 8pt.

  But when I look in the Windows Menu and my LabVIEW Application, the two are very different with respective police.

  Could someone try this answer this question?

  How can I do the same two in appearance?

  Is LabVIEW has different fonts defined and setting than Windows?

  Concerning

  Hemant

  [email protected]

  Good thing, never think of this before...

  In any case here table of differences: (MS Write vs LabVIEW):

  

  Andrey.

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

• 2009 Installer files on C drive

  I'm building an application (EXE) using LabVIEW 2009. Subsequently, I create an installer that is successfully done. The question I have is:

  In LabVIEW 7.1, I've been able to add an action to install (INI) in the Setup, files in a specified folder, for example, copy the files to C:\Parts\. With LabVIEW 2009, I see that there is no option for this.

  If I missed anyone can show me how or point to a solution?

  ThanksNAdvance!

  FredTest

  You must do two things:

  1. ensure that your media files are added to your LabVIEW project

  2. you can choose to include these files in your Setup program to specific locations by using the section of the source files for the installer:

  

  Note: 'Windows Volume' will normally be C, but has the advantage of adapting to cases where the boot hard drive is not C odd-ball (I thought it was possible before I came across a request for assistance from one of my clients saying that my application doesn't work)

• Remove labview 2009 without using Add/Remove program

  Hi all

  I have problem with the removal of LabVIEW 2009.

  I deleted some folders in the C drive, folder OR.

  Now I can't start my LabVIEW 2009 and it does not appear in my Add/Remove Programs list.

  I tried to delete all the folders and files in the C drive under folder OR, but the pop out error message shows that I don't have the authority to do so.

  So, how can I remove it completely?

  I had intended to reinstall LabVIEW 2009 after that I have completely removed.

  Very much appreciate your help.

  That's why I say try to reinstall LabVIEW. He could just do a repair of your installation. Then, you can use Add/Remove programs to uninstall completely.

  But when you uninstall completely there will be folders OR remaining. These are things like user.lib.

  Have you tried to reinstall the runtime?

  One last thing. I don't know how you got your installation so messed up, but remember that if you build a Setup program you should not install on a system with the development environment. There are so many things that can go wrong.

• 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 Build Path problem

  [Cross posted from LAVA]

  I got a code that worked fine on my home PC, when I moved to work, the exe would not build due to errors.

  Return errors are not good to explain the problem

  Until I got this one:

  

  Look at the path of the error:

  C:\Users\Developer2\Desktop\User group Meeting\LabVIEW 2009 new features\code\02 intermediate\01 build specifications\build file executable application. exe\LabVIEW 2009\vi.lib\addons\_ICON Library\String\_icon_lib_string.llb 9.0\my paths\dist\application

  This path refers to a VI inside of my executable!

  Maybe it's a bigger problem than I first thought

  So my question is:

  If a path inside my building that would be compared to the executable and LabVIEW must resolve, could fail, this process, depending on where the exe is located in a folder hierarchy?

  I guess it could have happened before? but it would be more probable now due to longer paths!

  Cross post solution

• Can I build an application with Labview 2009 for Windows 7?

  Hello

  I use Labview 2009 SP1 and the application builder 2009 SP1. If I install the app on win7 this message:

  Engine run LabVIEW depends on failure to upgrade (...) version 9.0.301, language {} code that is not in the distribution.

  Is it a problem with Windows 7, having two records of installation of 32 bit (C:\Program Files (x 86)) and 64 bit (C:\Program Files)?

  I had an application built on a XP machine and installed on a Windows 7 computer that was looking for the files in C:\Program Files when they were actually installed in C:\Program Files (x 86) - because it was 32-bit application.  After the installation I had to move the files to 1 place to another to make it work.

• LabVIEW 2009 SP1 crashes when moving large selection with the arrow key

  If I select a lot (10 or 15) diagram components and try to move some distance with the arrow button, I'm often a program crash.  Because a reduced number of components seems to hang after a longer distance traveled, it looks like some sort of buffer overflow error.  I don't see this problem when you use the mouse to move selections.

  I checked to make sure I have the latest version of the video driver for my NVIDIA Quatro FX570.  I also tried to work with no hardware acceleration and no handset, written.  What happens on Windows XP SP3 with all current updates.

  It became so bad that I have to do a save as every fifteen minutes to avoid losing data.

  Why not use my mouse for all movements?  Because it is not as specific and not so easy to limit to only one dimension of the movement.   My hand is not as stable as it once was.

  I'm hoping someone will have a suggestion that will clear up this problem.

  As I have indicated, I had the same problem with 8.5 and just DID a new install of Labview 2009.

  Since it is possible that my three monitors configuration, which of course requires more memory video, may be at the origin of the problem, I am satisfied with workaround by dragging the objects closer to their final destination and then using the arrow keys.

  Three monitors are ideal for the front, block and help/Internet/probe damaged.  When I got to work in the field with a single monitor, I felt severely handicapped.

  You can consider the issue closed.

  Thank you for trying to reproduce the failure.

• 6 error when generating an executable in Labview 2009

  I am trying to build an executable that uses the Spectral Measurements Toolkit vi.  I have been able to build a source distribution that allows me to call my application using a runtime engine so I know that all the dependencies are correct in the project file.  However, if I try to build this as an executable file, I get the following message:

  An error occurred during the recording of the following file:

  C:\Program NIUninstaller Instruments\LabVIEW 2009\vi.lib\addons\Spectral measures Toolset\LVSupport\SMT niScope Utilities\SMT niScope Dependent\SMT Config niScope for .vi spectrum (auto)

  Invoke the node in AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_EXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_Frmwk_Build.lvclass:Build.vi-> AB_UI_FRAMEWORK.vi-> AB_Item_OnDoProperties.vi-> AB_Item_OnDoProperties.vi.ProxyCaller
  
  Method name: Save target: Instrument

  The details of the message are:

  Visit ni.com/ask support request page to learn more about the resolution of this problem. Use the following as a reference:

  Error 6a held at AB_Source_VI.lvclass:Close_Reference.vi-> AB_Build.lvclass:Copy_Files.vi-> AB_Application.lvclass:Copy_Files.vi-> AB_EXE.lvclass:Copy_Files.vi-> AB_Build.lvclass:Build.vi-> AB_Application.lvclass:Build.vi-> AB_EXE.lvclass:Build.vi-> AB_Build.lvclass:Build_from_Wizard.vi-> AB_UI_Frmwk_Build.lvclass:Build.vi-> AB_UI_FRAMEWORK.vi-> AB_Item_OnDoProperties.vi-> AB_Item_OnDoProperties.vi.ProxyCaller

  Possible reasons:

  LabVIEW: File generic i/o error.
  =========================
  NOR-488: IO abandoned operation.

  I tried mass, the vi in the compilation of... \vi.lib\addons\Spectral Measurements Toolset\LVSupport\SMT niScope Utilities\SMT niScope Directory depending on, but for some reason any installer still tries to save to this place during construction and fails.

  Any ideas on what is happening here?

  Kind regards

  David

  Hi David,

  I built an executable with the VI, and I could not reproduce the problem.  Have you searched and found the VI in the specified directory?  A couple of things to try:

  -Use the LabVIEW 8.x file structure.  This lie in the advanced the Build menu.

  -Try and build an executable with just that VI.  Who will tell us if it is a symptom or a cause.

  Nick keel

  Engineering applications

  National Instruments

• 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

• Use the DAQCard 1200 with LabVIEW 2009 map

  Hi, I have a DAQCard 1200 and LabVIEW 2009 card. Can I use this device with this version of Labview? Is there anyway to make it work? Thank you.

  Hello ACTS,

  There is a difference betweenmx and traditionalDAQ DAQ!

  Installation of NI - DAQ6.9.3 is ok as outlined in this KB entry link above.

  But: you will find all of the DAQmx like this "DAQ Assistant" features! (Btw. why you insist on the use of ExpressVIs?)

  You must use the TraditionalDAQ functions instead. (There should be a few examples too...)

  Yes, DAQmx does not support your DAQCard1200. But TraditionalDAQ6.9.3 will do...