LabVIEW on Windows 7

Similar Questions

• Install LabVIEW on Windows 7 X 64

  I try to install LabVIEW in NI Developer Suite third quarter 2009 on Windows 7 X 64 machine. The Setup program ends with an unexpected error. I can install LabWindows/CVI the same DVD on this machine.

  I resolved to myself. The solution is to run setup.exe on the installation disc is Windows Vista compatibility mode.

• How to read video clips with LabVIEW in Windows 7?

  I already had the opportunity to play a video clip of my LabVIEW program.  Now, with the same program in the two operating systems, Windows XP and Windows 7, both versions work, but the version of Windows 7 will not be saved.  Trying to save it, I get the following error message: "generic error of LabVIEW.  Cannot save VI... LabVIEW Save 3 error code: FP bunch. "A 2010 version with this problem sampling program is attached. Any help would be appreciated.

  Try this VI.

  It seems that you have a video ActiveX component is corrupted.

• Migration to Mac Book to LabView 6i (Windows 98)

  Hello! I have a question to know if its possible to migrate a project to LabView 6i running on a Windows 98 computer to a new version of LabView and Mac OS X.

  The project reads the data from FP-I-110 (http://sine.ni.com/nips/cds/view/p/lang/es/nid/2185)

  With Windows 98 machine connects using a FP-I-110 RS-232 serial cable.

  Thanks for your time!

  I have no idea on the support of current FieldPoint software.  I never used it.  If someone else does not meet this topic in the day or two, you could start a new one with FieldPoint in the subject.  A call to your representative of NEITHER, you should also get the answer.

  Lynn

• How to set programmatically a LabVIEW exe * Windows * priority?

  I have an executable of LabVIEW that makes data acquisition to 10 kHz on an ongoing basis and under certain conditions of dumps of these data to a CSV file that is viewable in Excel.  We noticed if the file becomes unusually large and someone tries to open this file so that DAQ'ing is always in course (but does not connect), Excel will monopolize the CPU long enough such that the exe of LabVIEW does not have enough time CPU to extract data from data acquisition until the data in its circular buffer gets replaced.  I could try to simply increase the size of the buffer DAQ, but really, the solution is to have this executable LabVIEW have "priority" over other executables non-LabVIEW (such as Excel.)    Looking at properties VI--> execution--> set the priority seems to only define the priority between other threads LabVIEW but says nothing about how a thread LabVIEW is prioritized to another non-LabVIEW exe.   I have confirmed this by setting the LabVIEW execution property to 'critical moment' and then in the Task Manager and windows reports still his priority as "normal".   How can I set the * Windows * priority of an executable of LabVIEW without having to do it manually via the Task Manager?

  Thank you

  Ninja Edit:

  I should mention that I am building the executable is nothing else than a "master GUI" which generates four LabVIEW modules in sub-panels using static VI refs and displays important data from these four modules persistent "dashboard".   Modules to do all the boring tasks such as DAQ'ing and display data in charts.  Because I am compiling my code in a single executable using the GUI 'master' as the boot VI, set the priority in properties of VI flow down to the modules I load in sub-panels or will only the priority of the Master GUI be changed?  On a related note, should I set four enforcement system 'Data acquisition' modules, then the master GUI to ' User Interface?

  You can try calling the next VI. It sets the priority for the current process and has worked for me in the past on XP.

• Need link to download LabVIEW 2011 Windows 32-bit SP1

  I looked up the link to download LabVIEW 2011 SP1 32-bit Windows for an hour.  I thought it might be incorporated in the version SP1f2.  Nope. SP1f1 version. Nope.  Research of ni.com do not, Google does not find it, I'm stuck.

  How about this?

  LabVIEW 2011 SP1 (32-bit)

• LabVIEW: Null window... stopped to stranger on the block diagram

  Hello

  I have a pretty important program that has been written in Labview 6.0. Recently, we have upgraded to Labview 9.0 and this program has been exported to an executable file with the new version.

  When you run the executable file, I sometimes have the following error as seemingly random places. I was not able to crash when not to use the executable file. LabVIEW: Window zero. The first level VI ".vi" stopped to stranger on the block diagram of ".vi".

  

  I apologize for having empty on the names of vi, but I can't give names of vi, say what is the software or code. I can tell it uses NI USB-6212 IO cards, interfaces with the instruments of Rhode and Swartz and uses a lot of file i/o.

  I was hoping someone could give me a hint on how to debug such a mistake. I noticed that when this error occurs, the memory usage almost doubles.

  Thank you

  James

  
  

• How to with Labview startup window hidden when Teststand start loading

  I have Teststand development enviroment and Labview development environment installed on my computer, my use of Labview teststand adapter applications. It is every time when I start the application being Teststand, Labview, window pop auto-start - up, I wish to customize this behavior to let Labview just show in the taskbar.

  When you distribute applications, everything has to run in the runtime engine (RTE). It should not require development environments (Dev Env) must be installed on the machine at all.

  That being said, I recommend you configure the TS LV adapter to run the screw into the TEN. Which will automatically get rid of dialog to launch like this is part of the Env of Dev of LV.

  Norbert

• LabVIEW dev. window broken? (2012)

  Hey all,.

  Yesterday, I was testing and abandonment live normally when my window of development decided to break up. I have nothing abnormally (that I know), it just happened. I rebooted and the problem still persists. Note the horizontal scroll bar and the black bar below the main toolbar. Has anyone else seen this problem or knows how to fix this? Thank you!

  

  EDIT: I forgot to mention, save the VI it will appear like this with a double toolbar (when not in use).

  

  After looking at it, looks just like that a VI has been corrupted somehow. I copied the block diagram for a new VI and everything worked as expected. Weird.

• LabVIEW: Null error window in an application?

  Hello

  I just built an app from a vi and I encounter an error:

  LabVIEW: Null window.

  The first level VI 'name1.vi '.

  was arrested in stranger on the block diagram of the 'name2.vi '.

  The application runs smoothly until the user selects a few keyboard shortcuts to open a simple Subvi briefly while running to check on a file path.  This key combination works perfectly when the normal vi works and the Subvi displays information, then closes and continues execution of vi.  Why it wouldn't work when it was built as an application?

  Thanks for any help you can provide!

  Solved my problem - should have dug a little deeper before posting - sorry!

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

• By using Labview 7.1 created EXE in Windows Mobile 6.0

  Can I use my edition of the profeesion of 7.1 to create EXE files to run on Windows Mobile 6.0?  I created EXE files and then run directly on touch screen XP embedded without special Touchscreen Mobule.  I was wondering if this is possible under Windows Mobile 6.0?

  This does not work for various reasons. First XP Embedded is just XP with more control on which modules to install and what not. Second reason, it also only works on Intel/AMD x 86 processors. So if you create an executable in LabVIEW for Windows, it will run under XP embedded too, provided that you do not access system services that have not been installed on your XP embedded system.

  Laptop (or as it was earlier called Windows CE) is built in the same way as the Windows API but is not the same. Applications are only (with many limits) source compatible between laptop and normal Windows, but absolutely not binary compatible. Also all Mobile PC systems running on a RISC CPU as the ARM architecture. For these processors has compiled executable for the x 86 CPU architecture is simply a waste of bytes no meaning whatsoever.

  As says altenbach that LabVIEW PDA module to create executable files for Mobile PC systems. But beware, portable PC systems are not at all comparable to desktop systems. The performance of your hardware is magnitudes less, Windows CE (laptop) API is much narrower than on the Windows desktop and PDA module also for this reason has its own limitations. Do not expect a sign before be worn flawlessly to your PDA. There is much less control to choose and also the limited screen real estate is another severe limitation on applications of port Office seamlessly to a PDA.

• Excel 2007 to carry forward when called LabVIEW v9 in Windows 7

  I'm building a dual system using LabView and Excel 2007 v9, Windows 7.  The original system used Windows XP, Excel 2007, and LabView v8.6.  The problem is that the original system has been able to bring forward to Excel when it is called LabVIEW by using the node property - application-> visible.  This new configuration is running Excel, loads the data, run macros, but does not Excel forward.  The icon flashes in the bar of tasks Win7 and when selected displays at the top of LabView.  If I reduce the window of Labview, Excel is here.  This brings me to the conclusion that Excel is visible, as requested but will not come forward until this that selected in the taskbar.  The only differences, not to mention the versions, is used the extension .xls in model of original system files was performed in Excel in compatibility mode.  At the request of customers, the new system uses on model files Excel .xlsm extension.  I tried to use application.visible = True in the macro as well.  Could be a setting in Labview?  Could be a setting in Excel? Could be .xls vs. .xlsm? Or a problem with Windows 7 and the latest version of Labview.

  HP workstation - Labview v9 - Windows 7 - Excel 2007 sp2

  Thanks in advance

  Stephen

  SFM - dss says:

  I'll try the windowstate change.  Were these done successively? (i.e., property node-> property-> property node node) Or have they done along the way like the open call ActiveX and a property node then in a spreadsheet etc editing area, so there was some time between calls?

  

  I just use something like this in any place where I normally just would make excel visible. Works for me on Win7 x 64 even though I don't really know why.

  On Windows XP, I never had no problem with just using the visible property, with a change unique windowstate or even without one.

• LabVIEW 8.5 on Windows Vista

  Hello

  LabVIEW 8.5 is Windows Vista compatible? Also I have problems with devices and hardware drivers DAQ - mx? I use NO-USB6008.

  Thank you

  Have you tried a search? This question has been asked a number I don't know how many times. No, wait, don't bother, let me you type words into the search bar for you...

  Compatibility of the versions of Windows with LabVIEW

  NOR-DAQ and LabVIEW (for Windows) version compatibility

  EDIT: I see that LV_Pro had already posted the same answer.

• 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

• Hi, I have labview 8.6.1 for windows, but I switch to a Mac.

  Hello

  I have labview 8.6.1 for windows, but I go to a Mac desktop PC.  Can I transfer the license to a Mac version?

  Best,

  Eric Berkenpas

  Lead engineer-National Geographic Society

  Hi Eric,.

  The license for LabVIEW for Windows, Mac, and Linux are all separate, so you will not be able to transfer the license from a Windows machine to a Mac computer.

  Thank you